This documentation supports the 9.1 version of Remedy Action Request System.

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

Setting the component ranking order before deploying a binary payload

Starting with BMC Remedy AR System 9.1.04, you can create a custom binary payload and deploy it across environments. Before you create and deploy a binary payload, you can rank the order in which the components are updated. If you choose not to set the component ranking, BMC Remedy AR System randomly selects the component on which the binary payload is deployed.

When you install or upgrade to BMC Remedy AR System 9.1.04, the File Deployer process automatically creates an entry for each of your AR System components in the  AR System Monitor form. Use the AR System Monitor form to set preferences by adding ranking for deployment between various available components. The ranking is set in an ascending order. 

To set the ranking order for a component

  1. Open the AR System Monitor form.
  2. Click Search and select a component from available options. 
    When you select an option, the form is populated with details for the selected component.
  3. To set the rank, click  the increment or decrements buttons or enter a positive integer value (from 1 to 9999) 
  4. Select a Deployment Mode from the following options: 
    • Automatic (default)
    • Manual
  5. (Optional) If the Manual deployment mode is selected, click Deploy Now to start the payload deployment.
    Deploy Now instructs the AR System Server to start the deployment.
  6. Click Save.

Example: Setting the component ranking order

Consider you have seven components, such as four AR System Servers (ARSvr1, ARSvr2, ARSvr3, and ARSvr4), two Mid Tiers (MT1 and MT2) and one Smart IT server. You have set the following values in the Rank field of the AR System Monitor form:

Component

Rank

ARSvr13
ARSvr22
ARSvr31
ARSvr44
MT1 21
MT222
Smart IT31

In this scenario, ARSvr3 with Rank 1 has the highest preference. It will be updated first when you start the binary payload deployment.

Note

If you have the same ranking or no ranking for multiple servers, the system selects any random server to deploy the payload.

Related topics

Creating and deploying a binary payload

Defining a custom binary payload

Troubleshooting for Binary payload deployment



Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Naresh Gannamaneni

    Can we rank the multiple AR servers with the same rank? Does the same rank for multiple AR servers initiates the deployment concurrently ?

    Mar 16, 2018 11:55
    1. Anagha Deshpande

      Hello Naresh,

      I will check your query with the SME and will write back to you.

      Regards,

      Anagha

      Mar 18, 2018 10:15
    1. Ashish Bhurat

      Yes, You can rank multiple AR Servers with same rank. In such scenario, server will pick up on random basis one by one & not concurrently. Same rank & No rankiing to server is as good as same.

      Mar 18, 2018 11:54
      1. Naresh Gannamaneni

        Is there a way to trigger the concurrent execution of the payload on the multiple servers on the deployment console?

        Mar 19, 2018 01:21
        1. Ashish Bhurat

          Currently there is no way for concurrent execution as if package includes Server restart then all servers will get restarted in once.

          Mar 20, 2018 12:03
  2. Catalin Pana

    What do we do if we have multiple entries, with different Ranks for the same server?

    Feb 07, 2019 01:42
    1. Anagha Deshpande

      Hello Catalin,

      We are working on your query. We will respond soon.

      Regards,

      Anagha

      Feb 07, 2019 09:22
      1. Anagha Deshpande

        Hello Catalin,

        Perform the following steps when you have multiple entries with different ranks on the same server:

        1. Navigate to the following path
          <Install dir>/bmc software/AR System/monitor-ARServer-guid.properties
        2. Open the monitor-ARServer-guid.properties file
        3. Check the following monitor entry monitor.guid=AGGAA5V0HG8ZZAP0HGJCPJ04MTEXEI
        4. Copy the GUID.
        5. Open the AR System Monitor form
        6. In the Monitor ID field, enter the Monitor ID
        7. Click Search
        8. An entry is displayed.
          Retain that entry and delete the other entries

        Hope this helps.

        Regards,

        Anagha

        Feb 07, 2019 11:18
        1. Catalin Pana

          Hi Anagha,

          Thanks for your info. One more question, and one suggestion:

          Question: If we delete the entries which do not match the GUID of the servers, then we have gaps in the Ranks in that form. Does that have any effect when running the payload on each server?

          Suggestion: Add the info you provided as a prerequisite whenever deploying payloads, because having multiple entries will not allow the server to take the binaries from the package (it will do nothing when running the arpayloaddeploymentutil.sh command). Or maybe create a Knowledge Article (if one it not already existing).

          Feb 08, 2019 01:12
          1. Anagha Deshpande

            Hello Catalin,

            Regarding your question, the gaps in rank have no impact when running payload on each server. 

            About your suggestion, the information is added in the Troubleshooting for Binary payload deployment topic.

            Hope this helps.

            Regards,

            Anagha

            Feb 10, 2019 11:08
  3. Pratiksha Rane

    Hi Team,

    We shouldn't be having SmartReporting in the Component Ranking Order, since it is a standalone application and can never be patched using File Deployer.

    Presuming above statement is true, you will have to instead update the doc as AR Server Dedicated For SmartReporting.

    Please update the doc at the earliest.

    Regards, Pratiksha

    May 03, 2019 10:58