This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

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

Configuring the appquery plugin for a private RPC server queue

To assist with improving performance, you may choose to create a private RPC server queue and configure the appquery plugin to support it:

To create a private RPC server queue

  1. In your browser, open the AR System Administration Console and select System > General > Server Information.
  2. Select the Ports and Queues tab.
  3. Use the private RPC program number from one of the following ranges (for example, 390685):
    • 390621 - 390634
    • 390636 - 390669
    • 390680 - 390694

      Note

      Ensure that the selected RPC program number is not already in use by referring to the list of private RPC queues that have already been created in the Ports and Queues tab.

  4. Change Min Threads to 4 and Max Threads to 6.
    Min Threads and Max Threads can be configured based on server load and the number of concurrent users. Use the preceding values to start. These parameters can be tuned later by the administrator depending upon the load.
  5. After the Private RPC number is added, click Apply.
  6. Confirm that the ar.cfgcontains the RPC program number that you just added:
    1. Open the ar.cfg file using a text editor. The default path for ar.cfg is C:\Program Files\BMC Software\ARSystem\Conf\ar.cfg.
    2. Look for the RPC program number that you just added (for example, 390685) in the ar.cfg file.
    3. If the corresponding changes are not reflected, add them manually using the text editor and by referring to the screenshot below.

      Click the screenshot to expand it. 

To configure the appquery (conquery) plugin

  1. Stop the BMC Remedy AR System server.
  2. Open the pluginsvr_config.xml file. The default path for this file is C:\Program Files\BMC Software\ARSystem\pluginsvr\ pluginsvr_config.xml.
  3. Change the Private-RPC-Socket value so it is the same as the RPC program number in step 3 of the previous procedure.

    <plugin>
    
          <name>REMEDY.ARDBC.APPQUERY</name>
    
          <type>FilterAPI</type>
    
          <code>JAVA</code>
    
          <filename>C:\Program Files\BMC Software\ARSystem\pluginsvr\qry\conquery.jar</filename>
    
          <classname>com.bmc.itsm.conquery.ardbc.conquery.Query</classname>
    
          <pathelement type="location">C:\Program Files\BMC Software\ARSystem\pluginsvr\qry\conquery.jar</pathelement>
    
          <pathelement type="location">C:\Program Files\BMC Software\ARSystem\pluginsvr\foundation_shared\ITSMCommonUtils.jar</pathelement>
    
          <pathelement type="path">C:\Program Files\BMC Software\ARSystem\pluginsvr\qry</pathelement>
    
          <userDefined>
    
            <server_name>vw-pun-asp-pr20</server_name>
    
            <server_port>0</server_port>
    
            <Private-RPC-Socket>390685</Private-RPC-Socket>
    
          </userDefined>
    
       </plugin>
    
      <plugin>
    
  4. Restart the BMC Remedy AR System server.
  5. Verify the private RPC queue:
    1. In your browser, open the AR System Administration Console, and select System > General > Server Information.
    2. Select the Port and Queues tab.

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. Joachim Latzko

    Looks like the 8.1 ITSM installer already configures a private queue for APPQUERY. The port is 390622.

    Dec 13, 2013 07:55
  2. Vivek Patil

    Yes , ITSM 8.1 installer configures a private queue for  APPQUERY i.e. conquery.jar . We also configure rpc queue for DSOConfigurationPlugin.jar . So ITSM 8.1 registers 2 plugins using rpc queue.

    Dec 17, 2013 02:41
    1. Joachim Latzko

      That is why I think it is confusing to describe this in the section 'Configuring after installation' and using a different port. I followed the instructions. Created a private queue first (390685) just to find out that the actual queue was already configured and with a different port number.

       

      Joachim.

       

      Dec 17, 2013 05:38
      1. Bruce Cane

        Thanks Joachim. I'm looking at removing this topic. Do you think the information has any value if we position it differently?

        Dec 17, 2013 10:44