Troubleshooting data for CMCI JVM server problems

CICS® MustGather for CMCI JVM server problems

The CMCI JVM server runs inside a WUI region or a single CICS region and provides the CMCI REST and CMCI GraphQL APIs through a Liberty instance. Therefore, for errors specific to the CMCI JVM server, see Troubleshooting CMCI JVM server. The advice in Troubleshooting Liberty JVM servers and Java web applications can also help identify some generic Liberty setup errors. However, the CMCI JVM server generally does not need intervention beyond the configuration steps in Converting a WUI region with basic CMCI to use CMCI JVM server or Setting up CMCI in a single CICS region.

Gather the following diagnostic information before contacting the CICS support team to troubleshoot your CMCI JVM server problems.

Required data:

The JVM troubleshooting data, including the material described in point 5 for Liberty servers.

Optional data, for CICS TS 5.5 or later:

If your problem is a functional issue with results obtained within CICS Explorer® or another API client, or a problem triggered by operating a client in a particular way, you can enable functional trace within the Liberty server by using the configDropins technique:

1. Within your Liberty server directory, locate or create the configDropins directory, for example, server_working_directory/wlp/usr/servers/defaultServer/configDropins.
2. Within the directory, locate or create the overrides directory.
3. Create an xml file within the overrides directory with the following content. The file must be UTF-8 encoded and can be named logging.xml.

   <?xml version="1.0" encoding="UTF-8"?>
   <server><logging traceSpecification="*=info:com.ibm.cics.*=FINE"/></server>

This configuration enables function-level logging into the Liberty trace.log file. Your support representative might ask you to alter the logging statement to collect further trace.