Troubleshooting switch server connectivity

The Agentx file that the switch server uses will need to be replaced if the certificate has expired or is found to have a security vulnerability.

To replace the certificate in this file, complete the following steps:

1. Delete and re-create the switch server by running the following commands, where switchServerName is the name that was assigned to the switch server at the time of its creation, and switch_cr.yaml represents the name of a file to which you want to back up the CRD for the switch server before you delete it:

   oc get switchservers switchServerName -o=yaml > switch_cr.yaml
   oc delete switchservers switchServerName
   oc apply -f switch_cr.yaml

2. Restart the App Connect Designer instance and any integration servers in the same namespace to pick up the new Agentx configuration.
3. If any integration servers are in a different namespace, download the agentx.json from App Connect Designer, as described in Configuring connectivity between a calling flow and a callable flow, and reconfigure those integration servers by following the instructions in the Synchronize your on-premises agent panel.

About this task

If the Callable flows page in your App Connect Designer instance does not display the callable flows that are running on configured integration servers, there might be several reasons for this:

• A switch server has not been created.
• The switch server was created after the App Connect Designer instance was created.
• There is a mismatch between the connectivity agent and switch server files. For example, the switch server might have been re-created, but the integration servers were not configured with a new agentx.json file.

Complete the following steps to try to resolve the issue:

1. Work with your cluster or team administrator to delete and re-create the switch server.
2. Re-create your App Connect Designer instance as follows:
   1. Export all your flows from the App Connect Designer instance. For more information, see Exporting and importing flows.
   2. Work with your cluster or team administrator to re-create the App Connect Designer instance, ensuring that the instance is configured to use the new switch server. For information about deleting, creating, and configuring the instance, see App Connect Designer Authoring reference.
   3. Import your exported flows into the new instance.
3. Re-create any integration servers with callable flows so that they can pick up the new Agentx configuration.

About this task

If a deployed integration server is set up with an Agentx configuration in your App Connect Dashboard instance, but cannot connect to the switch server, there might be several reasons for this:

• There is a mismatch in the configuration between the integration server and switch server.
• The switch server certificate has expired.
• The switch server is not in a Ready state.

Complete the following steps to try to resolve the issue:

1. Work with your cluster or team administrator to delete and re-create the switch server.
2. Re-create the affected integration server so that it can pick up the new Agentx configuration.