Troubleshooting BMC Helix Connector Designer issues
Use the following reference information to understand the common troubleshooting scenarios for BMC Helix Connector Designer.
Additionally, you can use the validation utility to gather information about the issues related to the connector development environment. For more information, see Validating the connector development environment.
Common BMC Helix Connector Designer issues
The following table displays common BMC Helix Connector Designer issues, the possible causes of the issues, and corrective actions that you can perform to resolve the issues.
|Issue||Possible cause||Corrective action|
Cannot start BMC Helix Connector Designer on Microsoft Windows
For information about the prerequisites to use the BMC Helix Connector Designer, see Installing and setting up the connector development environment.
Integration Controller cannot establish connection
|Integration Controller cannot connect to the proxy server|
As part of the BMC Helix Connector Designer installation process, you will have downloaded the rcb.cmd file. For system requirements and installation steps, see Installing and setting up the connector development environment.
Modify rcb.cmd by adding the required environment variables (
Integration Controller does not start
To refresh a site, in the list of sites, click the refresh button for the site that you want to refresh.
Developed connectors are not available in BMC Helix Connector Designer on Microsoft Windows
If you use BMC Helix Connector Designer on Microsoft Windows, you might experience the following Docker issue. When the Docker engine or your laptop is restarted, the containers start before Docker shares the drive. As a result, you cannot see your developed connectors.
BMC Helix Connector Designer logs
For more information about the errors that occur during the BMC Helix Connector Designer usage, check the BMC Helix Connector Designer logs. To access the logs, use the following command:
docker logs <connector-container-name>
For setting the log level for the messages logged to the console, use the following environment variable:
While developing a connector, add the CONSOLE_LOG_LEVEL variable to the runConnector.sh file inside a connector container.