This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Portmapper service introduction

A portmapper functions as a "directory" of services and the ports on which those services are running. Processes can opt to register or not register their location with a portmapper. A common reason for not registering with a portmapper is security.

If a BMC Remedy AR System server is registered with a portmapper, your clients do not need to know what port the server is listening on because the clients can identify the port by using the portmapper and direct API calls to the appropriate TCP port. If a server is not registered with a portmapper, you must assign a TCP port number to that server. Otherwise, the system must search for an open port to communicate on each time the server is restarted. Your clients will not know where to find your AR System server because the port might be different if the AR System server is restarted.

Registering with a portmapper and assigning TCP port numbers are not mutually exclusive options. You can do both. If you specify a particular port for a server and register the server with a portmapper, clients within the firewall do not need to be configured to access the specified port number.

If the AR System server is not registered with a portmapper:

  • Client processes must be able to identify the port to communicate on to contact the server. For more information about configuring ports for the client, see Understanding port numbers.
  • Macros that a UNIX User tool runs as part of an escalation or filter run process cannot find the server. To fix this, register the server with a portmapper. You can also use the runmacro utility, which has a command-line port setting.
    See Connecting to AR System at a specific TCP port.
  • The client/server interaction still requires the use of RPC when specific ports are used.

Windows and portmapper services

Because many Microsoft Windows environments do not have a portmapper service, one is provided with the AR System server. If you already have a portmapper, AR System registers with it if requested. If not, you can specify that the AR System Portmapper service needs to be started and used as the portmapper for the system.

No AR System Portmapper exists for UNIX because all UNIX operating systems include a portmapper as a standard feature.


By default, Windows 2008 comes with a portmapper installation. To use the  AR System portmapper, you must uninstall the Microsoft portmapper and then continue with the AR System installation; otherwise, you can continue with the AR System installation without the AR System portmapper.

Connecting to AR System at a specific TCP port

When using an API client on a UNIX server, you can connect to the AR System at a specific TCP port by setting the AR TCP Port variable.

The following strategies require that all servers that the client uses are on the same port.

For the C shell, use the following commands to set ARTCPPORT:

setenv ARTCPPORT <TCPPortNumber> aruser &

For the Bourne shell, use the following commands to set ARTCPPORT:

ARTCPPORT=<TCPPortNumber>; export <ARTCPPORT> aruser & 

For an API program, you can set variables through a shell or from within the program.

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.