ITM Agent Insights: JazzSM Admin UI installation failure

Body

When trying to install JazzSM Admin UI only while other component like registry, TCR, WAS were already installed before and failed to add or install UI component only. This blog helps you to resolve the issue of JazzSM Admin UI installation failure in installing UI component only within existing component.

JazzSM version 1.1.2.1. Installation of Admin UI fails constantly with error:

Error during "post-install configure" phase:
  CRIMA1217E: A problem occurred during the execution of the /opt/ibm/JazzSM/JazzSM/install/fsconfig.xml file.

  Explanation: A package has an issue that cannot be resolved by Installation Manager.

  User Action: Identify the package that has the issue by looking at the installation history. In Installation Manager, click File > Installation History. In console mode, enter S: View Installation History. Contact IBM customer support.

  The following error occurred while executing this line:
/opt/ibm/JazzSM/JazzSM/install/fas_ui/fas_ui_config.xml:31: The following error occurred while executing this line:
/opt/ibm/JazzSM/JazzSM/install/fas_ui/fas_ui_config.xml:39: The following error occurred while executing this line:
/opt/ibm/JazzSM/JazzSM/install/fas_ui/fas_ui_tip_config.xml:46: The following error occurred while executing this line:
/opt/ibm/JazzSM/JazzSM/install/fas_ui/fas_ui_tip_config.xml:92: The following error occurred while executing this line:
/opt/ibm/JazzSM/JazzSM/install/fas_ui/fas_ui_tip_config.xml:119: CTGFI3011E: Failed in configuring Administration Services UI. Check /opt/ibm/JazzSM/JazzSM/admin_ui/logs directory for more information. [/opt/ibm/JazzSM/JazzSM/install/fsconfig.xml:270]

To resolve this issue gather Jazzsm pdcollect, check these instructions.

http://www.ibm.com/support/docview.wss?uid=swg21284703

The above error information can be found in the Index.xml file (Index.xml is located into IIM logs directory once you get the pdcollect)

Ant file that is pointing following error right after above error CTGFI3011E into index.xml file which shows the clear issue.

[exec] ADMA5078I: Update of isc has started.
     [exec] ADMA5058I: Application and module versions are validated with versions of deployment targets.
     [exec] ADMA5009I: Extracting application archive to /opt/ibm/JazzSM/JazzSM/profile/wstemp/appmgmt/mbean/AppManagement_1577bd0d7db_1/app_1577bd2f9d0/ext/AdminServicesGUI.war.
     [exec] ADMA5064I: FileMergeTask completed successfully for isc.
     [exec] ADMA5005I: The application isc is configured in the WebSphere Application Server repository.
     [exec] ADMA5005I: The application isc is configured in the WebSphere Application Server repository.
     [exec] ADMA5005I: The application isc is configured in the WebSphere Application Server repository.
     [exec] ADMA0185W: An update application operation failed and the configuration session could not be restored to its state before the operation was initiated.  The configuration session is in an inconsistent state, and changes made in the session should be discarded.
     [exec] ADMA5011I: The cleanup of the temp directory for application isc is complete.
     [exec] ADMA5080E: Update of isc has ended. The update failed.
     [exec] WASX7017E: Exception received while running file "/opt/ibm/JazzSM/JazzSM/install/jython/update-adminui.py"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for isc failed: see previous messages for details.
     [exec] WASX7341W: No "save" was performed before the interactive scripting session exited; configuration changes will not be saved.
     [exec] ant_exec return code is 105
     [exec] Result: 105
     [echo] Result of updating AdminUI app = 105

For error WASX7017E  https://www.ibm.com/support/knowledgecenter/SS7JFU_8.5.5/com.ibm.websphere.zseries.doc/ae/rtrb_wsadminprobs.html

For error WASX7418E: Application update for isc failed: see previous messages for details.

The Solution

Apparently, on AIX (and perhaps other platforms) the maximum Java heap size is set too low. This causes the the WebSphere Application Server (WAS) ejbdeploy script to fail (as show above).

To correct this, update the <WAS install location>/deploytool/itp/ejbdeploy.[sh | bat]
default:

$JAVA_CMD \

-Xbootclasspath/a:$ejbd_bootpath \

-Xms256m -Xmx256m \

....

should be updated similar to:

$JAVA_CMD \

-Xbootclasspath/a:$ejbd_bootpath \

-Xms512m -Xmx1024m \

...

This update to the ejbdeploy script allows you to proceed the installation/upgrade further without any issue.

If you still have issue or question you may open case https://www-947.ibm.com/support/servicerequest/Home.action

Subscribe and follow us for all the latest information directly on your social feeds: