Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Troubleshooting connection problems

The troubleshooting steps that follow can help you resolve connections issues between the BMC Atrium Orchestrator Development Studio application and the grid.

  • Verify the host name or IP address.
  • Verify that Atrium SSO is running.
  • Verify that the server is running.
  • Verify that the computer that is running BMC Atrium Orchestrator Development Studio can access the server. For example, ping the server.
  • Ensure that BMC Atrium Orchestrator Development Studio and the CDP are running the same version of BMC Atrium Orchestrator.
  • Ensure that BMC Atrium Orchestrator Development Studio is running on a supported platform.
  • Ensure that clocks on the computer that is running BMC Atrium Orchestrator Development Studio and the computer that is running the CDP are in sync. If they are out of sync by several minutes, the connection does not work.

  • Verify that you are using the correct settings for user name, password, peer context, port, and protocol.
     To review the connection settings, open the bao.options file located in the root folder of the CDP.

    Example

    In this example bao.options file, the CDP is installed on vm-w23-xyz010, the peer context is baocdp, the port is 38080, and the protocol is http.

    -P installLocation=C:\Program Files\BMC Software\AO
    -J AO_INSTALL_TYPE=install_new
    -J AO_INSTALLING_FEATURES=CDP,WEBSERVER,OCP
    -J AO_REPOSITORY_URL=http://vm-w23-xyz010:8080/baorepo
    -J AO_CERT_PASSWORD=
    -J AO_CERT_PRINCIPAL=My Company Name
    -J AO_ENVIRONMENT_NAME=ENV1
    -J AO_START_SERVER_ON_SUCCESS=true
    -J AO_OCP_DEPLOYMENT_CONTEXT=baoocp
    -J AO_AM_DEPLOYMENT_CONTEXT=baoam
    -J AO_GRAPH_DEPLOYMENT_CONTEXT=baograph
    -J AO_PEER_NAME=CDP1
    -J AO_PEER_NET_CONFIG_VALIDATE=false
    -J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp
    -J AO_PEER_NET_CONFIG_CDP_HOST=vm-w23-xyz010
    -J AO_PEER_NET_CONFIG_CDP_PASSWORD=
    -J AO_PEER_NET_CONFIG_CDP_PORT=38080
    -J AO_REPOSITORY_HOST=vm-w23-xyz010
    -J AO_REPOSITORY_PORT=8080
    -J AO_REPOSITORY_USER_NAME=admin
    -J AO_REPOSITORY_PASSWORD=
    -J AO_PEER_NET_CONFIG_CDP_USER=admin
    -J AO_PEER_NET_CONFIG_GRID_NAME=GRID1
    -J AO_PEER_NET_CONFIG_PEER_NAME=CDP1
    -J AO_PEER_NET_CONFIG_NEW_PEER_NAME=LAP1
    -J AO_PEER_NET_CONFIG_PROTOCOL=http
    -J AO_SECURITY_ACTIVE=true
    -J AO_SECURITY_COMM_PORT=61616
    -J AO_SECURITY_COMM_PROTOCOL=ssl
    -J AO_SECURITY_WEB_PORT=8080
    -J AO_SECURITY_WEB_PROTOCOL=http
    -J AO_WEBSERVER_SSL_ENABLED=false
    -J AO_WEBSERVER_PORT=38080
    -J AO_WEBSERVER_SHUTDOWN_PORT=8005
    -J AO_PEER_COMM_PORT=8081
    -J AO_WEBSERVER_DETECTED_OLD_SETTINGS=false
    -J AO_SERVER_STOP_SUCCCESSFUL=false
    -J AO_REPOSITORY_PROTOCOL=http
  • A connection problem could occur as a result of some file corruption during a BMC Atrium Orchestrator Platform or Development Studio upgrade.
    If Development Studio has connection problems after an upgrade, uninstall Development Studio and reinstall it, pointing to the same workplace used in the previous installation. You should not lose any data (workflows that you developed).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*