AtriumCore Installer - How to run it in INSTALLER_PAUSE mode to bypass or troubleshoot installation steps. |
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. Legacy ID:KA309507 You can execute the Atrium Core Installer in a PAUSE mode. This allows technical support to put debug libraries and executables in place after the "out of the box" installer copies the Atrium product files into the Atrium Install directory.
The command to start it is (Please remember to run it as Administrator on Windows or as sudo in a shell)
Windows: setup.exe –Dbmc.install.PAUSE_MODE=true -i gui
UNIX: setup.sh –Dbmc.install.PAUSE_MODE=true -i gui
Once the prompts have been entered the installer will extract the files and then an “Installation Paused” popup will be presented. This is when files can be modified or updated as necessary.
Once the stage is completed you can set the _CMDBRuleRuleEngineUpgradeInput.xml to the next stage (see screen cap below) and the installer will continue. It is also possible to add specific break points (pauses) to the the *_CMDBRuleEngineUpgradeInput.xml if specific debugging steps are needed. An example of this syntax is:
<extension_command> <class_name> com.bmc.install.product.atriumfoundation.PauseInstall </class_name> <argument>TRUE</argument> <note>INSTALL_PAUSED</note> </extension_command> <cmdb_driver_command> <file_name>$bmc_cmdb_UPGRADE_DIRECTORY$$/$210patch000$/$upgr-cmd-OSD.txt</file_name> <output>upgr-cmd-OSD.log</output> </cmdb_driver_command> <extension_command> <class_name> com.bmc.install.product.atriumfoundation.PauseInstall </class_name> <argument></argument> <note>INSTALL_PAUSED</note> </extension_command> Here is an example from a live system where this procedure was performed:
Troubleshooting the PAUSE Install:
3. An example for the Product Catalog installation states: Set the pause points in the following file – %TEMP%\Utilities\pct_PCRuleEngineInstallerInput.xml or %TEMP%\Utilities\cmdb\_CMDBRuleEngineUpgradeInput.xml
4. Look for AtriumCore\[ars]\cmdb\en\workflow\upgrade\CMDBRuleEngineUpgradeInput.xml file, search for “stage level="Stage Level “ to find relevant points of the failure root cause. This file is just a template. Please don't edit that file. 5. For example, in AtriumCore_install_log.txt, you may see these failure messages: Core 9.1.00 patch 001 install failed.
-------------------------------------------------------- Feature bmc Atrium cmdb failed com.bmc.smbu.install.common.rule.engine.CommandExecutionException: RIK command (/tmp/Utilities/RIK/RIK appinfo -x arserver -t 0 -u Demo -p <not_displayed> -l /usr/bmc/AtriumCore/ -n cmdb-RIK_PostInstall -f OB00C04FA081BABZlxQAmyflAg1wEA -m 9.1.00 patch 000 stage 1 -i Version -s 0 -o set -L -C) returned an exit code of 90, which was interpreted as a failure com.bmc.smbu.install.common.rule.engine.CommandExecutionException: RIK command (/tmp/Utilities/RIK/RIK loadapp -x arserver -t 0 -u Demo -p <not_displayed> -l /usr/bmc/AtriumCore/ -n BMCAtriumCMDB -f /usr/bmc/AtriumCore/cmdb/fr/workflow/adf_objectstore_1-fr.xml -k 0 -L -c) returned an exit code of 90, which was interpreted as a failure 6. In the example listed above in step 5 you know the failure point is “9.1.00 stage 1”.
This infers that you should set break point CMDBRuleEngineUpgradeInput.xml around code of:
<stage_group name="9.1.00 patch 000 stage 1" dir="$bmc_cmdb_UPGRADE_DIRECTORY$$/$250patch000$/$" env="$bmc_UTILITY_ENVIRONMENT_VARIABLE$"> <stage level="Stage Level 1"> 7. Depending on which module has failed add the following lines after the <stage level="Stage Level 1"> line of _CMDBRuleEngineUpgradeInput.xml.
Please keep in mind that the _%RuleEngine.xml is used to insert the break points and the %RuleEngine.xml is used to resume the installer to bypass that stage.
That said, here are the edits to the rule engine with the underscore (i.e. _CMDBInstallRuleEngine.xml):
<extension_command> <class_name>com.bmc.install.product.atriumfoundation.PauseInstall</class_name> <argument>TRUE</argument> <note>INSTALL_PAUSED</note> </extension_command> You do this to insert the BREAK POINTs only. For example if the Product Catalog has failed then you'd do this in the PCT engine file. If CMDB has failed that you'd this in the CMDB Rule Engine file.
8. At this point the installer will stop specifically at that stage you specified in the rule engine xml file.
This allows you to replace libraries, fix configurations or import files, and executables in the Atrium Install Directory should these changes become necessary.
You will now need a way to resume the installer and bypass that stage. Once the Installer stops there and you were able to make the changes or execute a step that has caused problems in the past, then you'll need to let align the install rule engine with what ARS has been set to in the Share:ApplicationProperties form.
Specifically the Version for the CMDB will be set to something like "9.1.00 stage 2". This string is an example, but what is important is that atriumcore_install_log.txt will be aligned with this stage as well as the CMDBInstallRuleEngine.
Since you do not want this stage to be executed again, then you'll need to update the following section of that stage. Again, this is just an example, we're not saying that all issues are found specifically at stage 5 of the install, so please keep that in mind.
Edit the CMDBInstallRuleEngine.xml file in the %TEMP%\Utilities\ directory and change the relevant section to have the install resume from the break points
Example:
.....
</cmdb_driver_command>
<rik_command>
<subcommand>appinfo</subcommand> <log_dir>C:\Program Files\BMC Software\AtriumCore\cmdb\en\workflow\upgrade\9.1.002\NormalizationRule-import-OSD.txt</log_dir> <log_name>CMDB-RIK_PostInstall</log_name> <guid>OB00C04FA081BABZlxQAmyflAg1wEA</guid> <property_name>Version</property_name> <mode>9.1.00 stage 1</mode> <property_status>0</property_status> <server_info_parameter>set</server_info_parameter> <no_output_to_console /> <no_new_log /> <note>CMDB_VERSION_REGISTRATION</note> </rik_command> To:
...
</cmdb_driver_command>
<rik_command>
<subcommand>appinfo</subcommand> <log_dir>C:\Program Files\BMC Software\AtriumCore\cmdb\en\workflow\upgrade\9.1.002\NormalizationRule-import-OSD.txt</log_dir> <log_name>CMDB-RIK_PostInstall</log_name> <guid>$BMC_CMDB_GUID$</guid> <property_name>Version</property_name> <mode>9.1.00 stage 2</mode> <property_status>0</property_status> <server_info_parameter>set</server_info_parameter> <no_output_to_console /> <no_new_log /> <note>CMDB_VERSION_REGISTRATION</note> </rik_command> And save CMDBInstallRuleEngine.xml
9. Click [OK] in the pop-up box and continue the installation. The installer will bypass that stage and continue.
Related Products:
|