Frequently Asked Questions
Getting started
What do I need before I can set up a connection?
The details depend on the protocol. For most connections, you need:
- The endpoint address (host and port) of the system you're connecting to
- Any credentials required by the external system
- The protocol-specific settings (your Connamara representative or the external system's connectivity team can provide these)
Do I need technical knowledge to use Conncentric?
For most setups, no. You fill in the connection details provided by the external system, and Conncentric handles the protocol. The Pipeline Designer uses plain field names for filtering and transformation. No programming required.
For custom logic, the Plugin SDK is available for developers.
Adapter status
What's the difference between "enabled" and "Active"?
Enabled/Disabled is what you set. It's your instruction to the platform ("run this" or "don't run this").
Active/Inactive/Claiming/Error is what the platform reports. It's the actual live state of the connection.
An adapter can be enabled but show Inactive briefly while it starts up, or Error if something went wrong. See Adapters Overview for the full status explanation.
Why is my adapter stuck on "Claiming"?
Claiming means the platform is trying to start the session but hasn't succeeded yet. Common causes:
- The adapter was just enabled and is still starting up; give it a moment
- No adapter pods are available to run it; contact your administrator
- The adapter is disabled; check the Admin State toggle
If it stays on Claiming for more than a minute, open the adapter and check the Event Log for an error. See Troubleshooting for a full checklist.
My adapter was Active, then suddenly showed Error. What happened?
Open the adapter and look at the Event Log. The entry just before the Error status change will show what went wrong. Common causes are a network drop to the external system, a rejected heartbeat, or a configuration problem. See Event Log Reference for what each event type means.
What does it mean when the status cycles between Claiming and Error repeatedly?
The adapter is trying to connect, failing, and retrying. The Event Log will show the specific error on each attempt. The most common cause is a network or configuration problem: wrong host, wrong port, or a connectivity issue.
Making changes
Can I edit an adapter that's currently running?
Yes. Open the adapter, click Edit, make your changes, and save. The platform will restart the connection to apply the new configuration.
For production connections, consider disabling the adapter first, making the change, then re-enabling. This gives you a cleaner restart.
I made a change but it doesn't seem to have taken effect. What should I do?
Check that you saved the change (the adapter should show a "last modified" timestamp update). If the adapter is running, it needs to restart to pick up the new settings. Disable it, wait for it to show Inactive, then enable it again.
Can I copy an adapter to use as a template for a new one?
Not yet through the Portal UI. Contact your administrator about exporting and re-importing adapter configurations as a workaround.
I deleted an adapter by accident. Can I get it back?
If your team uses IaC bundles, your administrator can re-apply the bundle to restore it. If the adapter was only configured through the Portal with no export, it cannot be recovered.
This is one reason to export and save configurations for any important connection.
Connections
What happens when I disable an adapter? Does it disconnect immediately?
The platform sends a proper disconnect to the external system before closing the connection. The external system will see a clean shutdown rather than an abrupt drop.
Can I have two adapters connecting to the same external system?
It depends on the external system and protocol. Some systems allow multiple simultaneous connections. Others require exclusive access.
From Conncentric's side, you can create as many adapters as you need. Each one manages an independent session.
My adapter connects but no messages are coming through. What do I check?
- Check the Event Log. Are you seeing message receive events? If no messages appear in the log at all, the external system may not be sending any.
- If messages appear in the log but aren't reaching your destination, check your pipeline filters. A filter condition may be dropping them.
- Check with the external system's support team. They may need to enable message delivery for your connection.
What happens to a connection if the server running it crashes?
Another server picks up the session automatically. The exact time depends on your platform's failover configuration. No action is required from you. See Adapters Overview for how redundancy works.
Platform
How many adapters can I run at the same time?
There is no hard limit in the platform. Practical limits depend on the number of adapter pods your administrator has provisioned and how resource-intensive each connection is.
Where is my data stored?
All configuration (adapter settings, plugin files, and reference artifacts like data dictionaries) is stored in the platform's database. The platform does not store certificates or private keys. Message data passes through the platform but is not stored; it is delivered to its destination and the platform retains no copy.
Is there an API I can use to automate things?
Yes. The platform exposes a REST API that the Portal uses. You can integrate with this API for automation. Contact your administrator for API access details.