What are the steps to deploy the Midtier 9.1.04 patches and hotfixes?
Online Doc link: https://docs.bmc.com/docs/display/brid1808/Applying+a+deployment+package
1. If the D2P package is to be deployed to multiple midtiers, then make sure all the midtiers are listed in the AR System Monitor form.
This form is populated when the File Deployment Settings in the Midtier Config Tool are populated, A restart of the BMC Midtier File Deployer service or process will do a check on the AR System Monitor records. If the midtier is not listed, the record will be created.
2. Confirm that all filedeployer processes are running on all midtiers that will involved with the patch/hotfix deployment before you begin this process.
In Windows, verify the BMC MidTier File Deployer service is started.
In Unix, you may need to execute the /midtier/filedeployer/filedeployer.sh script. Make sure this is executed by an ID that can stop/start your webserver.
3. If a AR Server group is involved, the recommendation is to have the File Deployment Settings for each midtier point to the admin server of the Server group.
Step 1. Import D2P package
Step 2: Deploy package
This will create the individual records as need in the AR System Single Point Deployment Payload form. For example, Patch 002 creates three records for mt_common, mt_unix and mt_windows; however, a midtier hotfix will only create one record.
Popup box displays stating:
This package includes files to be deployed/rolledback. You can monitor the status of the file deployment/rollback by opening the package, selecting the item for file deployment and clicking on the "View Payload Status" button. (ARNOTE 10000)
Step 3 – Initiate the payload from the midtier
When viewing the Payload Status records for multiple midtiers, you will see 'Pending download" for the midtier that is first in the ranking order, "Not Ready" for the midtiers that secondary and beyond on the ranking.
You must remote to each midtier in order of their ranking on the AR System Monitor form to initiate the payload. This is done for security reasons and separation of duty if desired.
NOTE: Midtier payload deployment will restart the Midtier webserver.
Step 4 – Confirming the payload execution
The records will now show a Payload Status of Successful. The next midtier in rank should now show a Pending Download status.
From the file system, you will see backups of the files/directories replaced:
Note: The identification string matches up to the Deployment ID on the AR System Single Point Deployment Payload form.
You will also find the payload zip files under the midtier directory.