This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Troubleshooting issues connecting to the AR System server

The most common method of connecting to the BMC Remedy AR System server is using the AR System API. Many clients and integrations use this method to connect. Clients or integrations that connect with CMDB API also use the same parameters and path to reach the server.

Connection to the AR System server or CMDB Server requires:

  • Fast, reliable, bidirectional TCP/IP network connectivity
  • A server name that resolves to the correct IP address to reach the AR System server
  • Correct value for the TCP port (if the AR System server is not registered with portmapper or the client is unable to reach portmapper)
  • Correct values for user authentication, including user name, password, and in some cases, authentication string

To confirm the account credentials and server availability, log on with a client such as BMC Remedy Developer Studio. To test the connectivity from a remote system, the client should be installed on the system that will connect to the AR System server.

Related topic

Running arconnect

Was this page helpful? Yes No Submitting... Thank you