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.

Setting ports and RPC numbers

Use the Ports and Queues tab to set server ports and RPC numbers as needed to communicate with other servers, clients, and services on the network. The Server Queue region on this tab enables you to configure server queues and threads as appropriate for your server, taking advantage of the multithreaded design of BMC Remedy AR System.

Assigning TCP port numbers to AR System servers

You assign one TCP port number for the AR System server. All initial contact with the server is through a single port. If you run multiple servers on the same computer, each server must use a unique port.

Clients must be configured with the server port number to enable server access without the use of a portmapper. If you do not allow the server to register with a portmapper, you must assign a TCP port number for the AR System server. For more information about configuring clients, see Configuring clients for AR System servers.

Do not assign port numbers that conflict with port numbers used by other applications or programs running on your system. If you assign conflicting port numbers, your servers might not start as expected. To find out which port numbers are in use, enter one of the following commands at the command-line prompt:

  • UNIX — rpcinfo -p
  • Windows — netstat -a

Client tools can use ports 0-65535.

Ports 1-1024 are reserved ports; avoid using these ports. On UNIX, port numbers within the range 1-1024 are available only for the superuser, and many of these numbers are reserved.

To set server ports and queues

  1. In a browser, open the AR System Administration Console, and click System > General > Server Information.
    The AR System Administration: Server Information form appears.
  2. Click the Ports and Queues tab.

    AR System Administration: Server Information form--Ports and Queues tab 
    (Click the image to expand it.)
  3. Edit the options as needed:

    Ports and Queues tab fields

    Field Name

    ar.cfg or ar.conf option 

    Description
    Server TCP/IP Port

    TCD-Specific-Port

    Defines the TCP/IP port number for the AR System server. Enables clients to have access to the server without a portmapper. When set to 0, which is the default, the portmapper assigns the port.

    Ensure that you set the same port number as the value of the server_port parameter in the pluginsvr_config.xml file that is located in the <Install Dir>/pluginsvr directory.

    Note: If you set the Server TCP/IP Port field to a value less than 1024, older clients cannot connect.

    Distributed Server RPC Program Number   Obsolete. See Assigning an RPC program number to DSO.
    Alert Outbound Port   The specific TCP port to which the server binds when sending alert messages to registered clients. If multiple alert threads are started, the number represents the starting port number in a consecutive range of numbers available for the alert threads. If no port number is specified or if 0 is entered, the portmapper randomly assigns an available port to the server.
    Register with Portmapper

    Register-With-Portmapper

    Defines whether the AR System server and the plug-in server are registered with AR System Portmapper. If the check box is

    • Selected — They are registered. The server is registered if not previously registered. AR System clients can get the port number of the AR System server and the plug-in server from AR System Portmapper.
    • Cleared — They are not registered. If the server was previously registered, this option removes the registration. AR System clients cannot get the port number of the AR System server and the plug-in server from the portmapper.

    If you are running multiple servers on a single computer, you can select the Register with Portmapper option for one server only.

    Server Queue

    Private-RPC-Socket

    Enables you to define server queues specific to your needs. For most types of server queues, you can specify a minimum and maximum number of threads. For the escalation queue, only the maximum threads number is used, and all threads are started at startup time.

    • If you do not specify a fast queue or specify only one thread, two threads are started to meet the minimum system requirements.
    • If you specify a list queue and specify only one thread, two threads are started to meet the minimum system requirements.
    • If you do not specify a list queue, one is not started.
    • If the server starts more threads than specified to meet system requirements for fast and list queues, it does not change the number specified.
    • For all other types, if you do not specify a number, the system defaults to one minimum and one maximum thread per server queue.

    See Defining queues and configuring threads.

  4. Click Apply.
  5. Restart the server for the changes to take effect.

    Note

    To change the port number that the AR System server uses when communicating with the plug-in server, edit the Plugin-Port option of the ar.cfg (ar.conf) file, and restart the server. See Plugin-Port .

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.

Comments

  1. Jose Leon

    This link is broken on the page:  See Defining queues and configuring threads.

    Thanks, Jose.

    Mar 25, 2015 01:40
    1. Prachi Kalyani

      Hello Jose,

      Thank you for bringing this to our notice. I have fixed the link.

      Thanks,

      Prachi

      Mar 25, 2015 11:01