Troubleshooting
Problem
This document helps you collect and share data required to diagnose Container Customization issues.
Diagnosing The Problem
Collecting the Data
Depending on nature of your issue, provide the requested diagnostics-
- Integrated Developer Toolkit
- Customization runtime
- Generating custom images
- Continuous Integration and Continuous Delivery
- Log4j Issues
Integrated Developer Toolkit
Generic Info -
- OS Version (Recommended Version: RHEL 8.x )
- Database vendor and version details (Include Fix Pack level)
- MQ Version
Issues during the Developer Toolkit(DTK) setup -
- om-compose.properties
- The exact command used to execute the process
- All avaialble log files from <Path>/devtoolkit_docker/compose/logs folder
Issues during customization package build in the DTK environment -
- devtoolkit_extensions.xml
- The exact command used to execute the process and log output
- Example: ./sci_ant.sh -f <path>/devtoolkit_extensions.xml export
- Generated extensions.jar (present in the parent directory of your runtime directory)
Issues during importing the extensions to the DTK environment -
- extensions.jar
- om-compose.properties
- The exact command used to execute the process and log output
- Example:./om-compose.sh update-extn <full_path_to_extensions.jar>
Issues during importing CDT to DTK environment-
Upload the following diagnostics from the Extracted Runtime -
- Exact command used to execute CDT import and corresponding logs
- Example: cdtshell.sh
- ydk_prefs.xml
Issues during agent or integration server run in DTK environment -
- Screen Print of the Agent or Integration server configuration from Applications Manager
- Apply VERBOSE tracing on the related Agent or Integration server and share the logs captured
- MQ .bindings file
Customization Runtime
- The exact command used to create the custom runtime container from the base images.
Example:
docker run -e LICENSE=accept -e LANG --privileged -v <oci-storage-name>:/images \ -v <docker volume or host path>:/opt/ssfs/shared -it --name <container name> <image>
- Upload the diagnostics from the custom container image for issues related to Database connectivity
- DB2 or Oracle:
- /opt/ssfs/runtime/properties/system_overrides.properties
- /opt/ssfs/runtime/properties/sandbox.cfg file
- Logs generated on running ./dbverify.sh
- For Oracle please include:
- AGENTDynamicclasspath.cfg.in
- APPDynamicclasspath.cfg.in.
Generating custom images
Upload the following diagnostics -
- Exact command executed to generate custom Images.
- generateImages.sh logs
Continuous Integration and Continuous Delivery in OpenShift Container platform
Upload the following diagnostics -
- BuildConfig.yaml file
- build.sh script
- build.sh logs
Log4j Issues
Upload the following diagnostics -
- log4jconfig.custom.xml
- resource.jar
- values.yaml
| How to submit diagnostic data to IBM Support |
|
After you have collected the preceding information, and the case is opened, please see: For more details, see: |
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PEW","label":"Sterling Order Management"},"ARM Category":[{"code":"a8m0z000000cy0AAAQ","label":"Install and Deploy"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.0"}]
Was this topic helpful?
Document Information
Modified date:
01 October 2021
UID
ibm16486385