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.
To set the ranking order for a component
- Open the AR System Monitor form.
- Click Search and select a component from available options.
When you select an option, the form is populated with details for the selected component. - To set the rank, click the increment or decrements buttons or enter a positive integer value (from 1 to 9999)
- Select a Deployment Mode from the following options:
- Automatic (default)
- Manual
- (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. - 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 |
---|---|
ARSvr1 | 3 |
ARSvr2 | 2 |
ARSvr3 | 1 |
ARSvr4 | 4 |
MT1 | 21 |
MT2 | 22 |
Smart IT | 31 |
In this scenario, ARSvr3 with Rank 1 has the highest preference. It is updated first when you start the binary payload deployment. If you add a new component and do not explicitly set any value for it in the Rank field, it's rank is set in an ascending order. For example, if you add a new component after the Smart IT component (having the rank 31) and do not explicitly specify any rank for it, the new component is added with the rank 32.
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
Comments
Can we rank the multiple AR servers with the same rank? Does the same rank for multiple AR servers initiates the deployment concurrently ?
Hello Naresh,
I will check your query with the SME and will write back to you.
Regards,
Anagha
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.
Is there a way to trigger the concurrent execution of the payload on the multiple servers on the deployment console?
Currently there is no way for concurrent execution as if package includes Server restart then all servers will get restarted in once.
What do we do if we have multiple entries, with different Ranks for the same server?
Hello Catalin,
We are working on your query. We will respond soon.
Regards,
Anagha
Hello Catalin,
Perform the following steps when you have multiple entries with different ranks on the same server:
<Install dir>/bmc software/AR System/monitor-ARServer-guid.properties
Retain that entry and delete the other entries
Hope this helps.
Regards,
Anagha
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).
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
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