Information
This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Updating the AR System server name for BMC Service Request Management


  1. In a browser, open the Application Settings form:
    1. Go to Administrator Console > Application Administration Console.
    2. Click the Custom Configuration tab.
    3. Select Service Request Management > Advanced > Application Settings.
      AppSettings.png
  2. In the Mid Tier Path field, replace the Mid Tier server name with the new Mid Tier server name and the port number (for example, newMidTierServerName:8080/arsys).
  3. Update the server name in the PDL:ApplicationSettings form.
    1. In a browser, open the PDL:ApplicationSettings form.
      AppSettingsHostName.png
    2. In the Hostname field, enter the newServerName.
  4. Update the server name in the Report form.
    1. In a browser, open the Report form.
      ReportServer.png
    2. In the Server field, enter the oldServerName, and perform a search.
    3. Replace the oldServerName with the newServerName.
  5. If you are using advanced interface forms (AIFs), update the Server field in each configuration entry with the new server name.
    ConfigAdvInterface.png

    For existing service request records, when a user views the Process View tab under Service Request Details, the URL for the fulfillment application (see the ID field in the following screenshot) will refer to the old server name specified in the CAI Application Registry. Consequently, the URL will not work. The URL cannot be updated, so the user must open the corresponding fulfillment application manually. New service requests (submitted after the server name was changed) will pick up the updated CAI Application Registry server name, and the URL will work correctly.

    RequestDetails.JPG

 

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

AR System 21.05