Assigning an RPC program number to DSO


The information in this topic is applicable only for on-premises deployments.

Dedicated (private) remote procedure call (RPC) program numbers are not required by Distributed Server Option (DSO), but you might want to use them in these circumstances:

  • You have a large-scale environment with heavy data traffic.
  • Your environment distributes large amounts of data.

If you dedicate an RPC program number to DSO, it must be one of the following numbers: 

  • 390621 -390634
  • 390636 -390669
  • 390680 -390694 (private queue)

Best practice
We do not recommend assigning the RPC program number 390600 to DSO because the administrative queue is single-threaded.

The DSO server uses the assigned RPC program number for all communication with the associated AR System server. You must allocate at least one thread to the server queue associated with the RPC program number.

If you do not assign a dedicated RPC program number to DSO, the fast and list queues process all distributed operations.

For more information about threads and queues, see AR-System-server-architecture-and-scalability.

To assign an RPC program number to DSOon the local AR System server

  1. Open the AR System Administration: Server Information form for the appropriate AR System server.
  2. Click the Ports and Queues tab.
  3. Verify that the RPC program number that you want to assign to DSOis listed in the Server Queue table.
    If the number is not listed, add it. For more information, see the System requirements.
  4. Click the Connection Settings tab and then click the DSO Server tab.
  5. In the DSO Local RPC Program Number field, enter the appropriate RPC program number, and click OK.
  6. To make the change take effect, restart the AR System server.

If you reassign the RPC program number while running DSO and then restart the AR System server, you do not lose any items in the distributed pending queue.

 

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