Share This:

Deploying D2P Package to upgrade Application or to apply Server Hotfix in a Large Server Group environment can be a time-consuming process.

 

From Remedy version 19.02 onwards, you can apply the Deployment Package Simultaneously on all Servers to speed up the upgrade process. This will help to reduce the time each server in a Server Group would need to deploy a package.

 

Warning: You should be careful when using this method as the entire server group might go down when arpayloaddeploymentutil.bat

is executed and AR Servers are restarting. In such a case it’s a good practice to not include Administrator Server as part of simultaneously deployment or rollback.

 

 

Steps to deploy a package Simultaneously across servers in a Server Group

 

  1. Log in to Mid Tier as an Administrator or a package deployer user by using the following URL:
    https://<midTierServerName>:<port number>/arsys
  2. From the IT Home page, select Applications > AR System Administration > AR System Deployment Management Console
  3. In the Deployment Management Console, IMPORT the package example: ITSM 19.08

    Deployement Management console.pngReady to deploy.PNG
  4. Once Package status change to 'Ready to Deploy', don't select the DEPLOY option yet, Open AR System Monitor Form and sort the Host Name based on the Monitor Type
  5. Select the Servers where you want to perform Simultaneous Deployment and update their Rank to Rank 1 or any other Rank which will be the same for all servers. Save the changes.

      AR System Monitor OOB.png

  

   6. Go back to the Deployment Management Console and select the DEPLOY option now for this package. Refresh the panel until the status change to

        'Pending Deploy'

      DeployITSm1908.png

   

    7. Select VIEW on this package entry

    8. Locate the 'Deployment Payload' item type entry and select 'View Payload Status'

      View Payload Status.png

 

    9. Here you will see all the servers from the Server Group with the same Monitor Type, for example, ARServer or  Midtier and they will have the same Rank

and all Host Status will be 'Waiting for Utility Run'. This confirms all servers are ready for deployment.

      All servers same rank.PNG

 

  10. Run the arpayloaddeploymentutil.bat on all servers now which have the Host Status 'Waiting for Utility Run'.

  • Note: You don't have to wait for Server Host Status on Server to change to 'Deployment Success' before running the arpayloaddeploymentutil.bat on another server.

                    Run the utility on all servers and remember to exclude the Administrator Server.

       arpayload bat ran.PNG

 

  11. Use the Administrator Server to login and View the Package one more time. (Step 7 & 8). You will see all the Servers are deploying the payload simultaneously.

      post bat is ran.PNG

 

  12. Navigate back to the Deployment Management Console to confirm that the packages were Deployed Successfully across all servers.

      deployed.PNG

 

 

You can Rollback a D2P package simultaneously as well. Many steps for package simultaneous rollback are similar to package simultaneous deployment. You will see those below.

 

Note: BMC doesn't recommend to rollback a Successfully deployed package. You can choose to Rollback those packages if an issue occurs during the validation of the package;
Or if an error occurs while deploying the package, you can restore the objects on your server to the pre-deployment state.

 

 

Limitation: From Remedy Version 19.02 onwards, we have D2P package rollback criteria to avoid accidental rollback.

  • You can rollback a package within 48 hours of successful package deployment.
  • This interval can increase up to 168 hours. You can increase this only before package deployment.
  • This can be configured using ‘D2P-Rollback-Timeout-Interval’ setting which can be added in the Centralized Configuration under component com.bmc.arsys.server.shared’.

           rollback cri.png

 

Steps to rollback a package Simultaneously across servers in a Server Group

 

  1. Open AR System Monitor Form and search the Servers where you want to perform Simultaneous Rollback. Update their Rank to Rank 1 or any other Rank which will be the same for all servers (See Step.5).
    Save the changes. Remember to exclude the Administrator Server.
  2. Navigate to Deployment Management Console and select 'Rollback' for a package. Refresh the panel until the Status Change to 'Pending Rollback'

        package rollback.PNG

Note: Post 48 hours we will get an error “Rollback Timeline Validation Failed: Rollback is not allowed 48 hours after successful deployment” if this parameter is not set as the default value is 48 hours. For more details, review:  https://communities.bmc.com/docs/DOC-117790

        rollback error.PNG

 

 

  3. Select VIEW on this package entry and locate the 'Deployment Payload' item type entry and select 'View Payload Status'

         pending rollback.PNG

 

   4. You will see the list of Servers with the same monitor type here, all with status 'Waiting for Utility Run'.

        Run the arpayloaddeploymentutil.bat on all servers now which have the Host Status 'Waiting for Utility Run'.

      Note: You don't have to wait for Server Host Status on Server to change to 'Rollback Success' before running the arpayloaddeploymentutil.bat on another server.

        Run the utility on all servers and remember to exclude the Administrator Server.

        arpayload bat ran.PNG

 

   5. Use the Administrator Server to login and View the Package. You will see all the Servers are rolling the payload simultaneously.

       utility ruyn.PNG

 

   6. Navigate back to Deployment Management Console to confirm the packages were changed to Rollback successfully across all servers.

 

 

Reference Information for additional details

 

Communities

 

Document

 

Videos