Troubleshooting the CICS build toolkit

If you are experiencing problems with the CICS® build toolkit, use these techniques to diagnose the problem.

Building a CICS bundle that references a Dynamic Web Project with a target run time

When you develop a Dynamic Web Project, you might configure the project to compile against a local Liberty server. However, the local Liberty server target run time is not available when you deploy the project to a staging or production environment.

If the project's target run time is not available, the CICS build toolkit performs the following tasks:
  1. Removes references to unsupported target runtimes from the project. The following message is displayed:

    WARNING The following target runtimes are not supported by the CICS Build Toolkit and will be removed: [WebSphere Application Server Liberty] (referenced by: /jaxws-fixme/JAXWSWebSample)

    You can suppress this warning message by manually removing these unsupported target runtimes from the project.

  2. Adds the CICS Liberty libraries class path container to the project, ensuring that the project can access these libraries at run time. The following message is displayed:

    WARNING Automatically added classpath container: 'Liberty JVM server libraries (WLP 16.0.0.2, CICS TS 5.3)' (referenced by: /jaxws-fixme/JAXWSWebSample)

Imports not able to be resolved

The CICS build toolkit might display a message that is related to imports that cannot be resolved, similar to the following message:

The import javax.servlet cannot be resolved

To resolve this issue, you must add the Liberty JVM server libraries to the project's class path. See Creating a for instructions.

Java version too low

The build might fail with a Java™ version error message, similar to the following one:

ERROR Unbound classpath container: 'JRE System Library [JavaSE-1.8]' in project 'com.ibm.cics.example' (referenced by: C:\build\JAT\source\examples)

This message means that the environment variable JAVA_HOME points to a version of Java that is lower than the one required by the project that is being built. To resolve this issue, you need to install the required Java version and set JAVA_HOME to that installation directory. Alternatively you can change the project to require a different Java version.