Troubleshooting
Problem
The centralized installation manager (CIM) is a new feature for WebSphere Application Server Network Deployment, Version 7.0 for distributed platforms, Windows and IBM i. Use this feature to shorten the number of steps that are required to create and manage your environments. As an administrator, you can remotely install or uninstall product components and maintenance to specific nodes directly from the administrative console without having to log in and repetitively complete these tasks.
Symptom
If having issues while using centralized installation manager to install updates or product components then the following MustGather will assist you in collecting the critical data that is needed to troubleshoot the issue.
Resolving The Problem
Centralized Installation Manager specific MustGather information:
- Describe the steps to recreate the problem.
- Enable the following trace string on the Deployment manager:
- TraceSpec for CIM commands and runtime:
cimgr=all - TraceSpec for CIM WebUI:
com.ibm.ws.console.cim.*=all - Recreate the problem.
If you are using wsadmin, then follow MustGather: wsadmin problems in WebSphere Application Server to enable trace in the wsadmin.properties file. Note: Traces need to be enabled on deployment manager. | ||
Data required
- Contents from the following directory:
dmgr_profile_root\logs - Contents from the following directory:
dmgr_install_root\properties\cim - The files generated after running the following command on the deployment manager and the target node where the problem was encountered:
dmgr_install_root\bin\versionInfo.bat/.sh <nodeName>.out - Send the directory listing of the CIM repository.
For example:
dmgr_install_root\cimrepos - For the Windows operating system: dir /s >filelist.txt
- For the AIX, Linux, HP-UX, and Solaris operating systems: ls -laR > filelist.txt
- Submit the complete contents of the "descriptors" directory under the CIM repository root.
For example:
dmgr_install_root\cimrepos\descriptors - Submit complete contents of the following directory:
dmgr_install_root\logs - Gather the following content:
dmgr_profile_root\config\cells\cell_name\nodes\dmgr_node_name\node-metadata.properties
AND |
appserver_install_root\bin\versionInfo.bat/.sh <nodeName>.out |
(Note: Capture from all remote nodes where CIM is failing.) Where appserver_install_root is the remote node being updated using CIM. |
If you are unsure where the CIM repository is, then look up the value for the CENTRALIZED_INSTALL_REPOSITORY_ROOT property in the following file: |
dmgr_install_root\properties\cimgr.props |
Note: This property defines the full path to the CIM repository on your deployment manager host. |
dmgr_install_root is the root install directory where WebSphere Application Server V7.0 where deployment manager is created.
dmgr_profile_root is the root directory of the deployment manager profile being used to run CIM.
Follow instructions to send diagnostic information to IBM support.
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21368123