Manually importing Java libraries
When creating your own build scripts, if you want to manually import Java libraries to resolve dependencies instead of using the IBM® CICS® SDK for Java™ or Maven Central artifacts, you can copy the .jar files out of the CICS installation directories.
Note: Copying .jar files manually makes them prone to get out of sync with
updates. You can use the artifacts on Maven Central to
ensure that you always have the correct version of libraries. Otherwise, you must have a mechanism
to refresh the copied .jar files. A full refresh is required when a new release
of CICS is installed.
The .jar files are located within the /lib directory of the CICS installation on z/OS.
The application development .jar files are:
- com.ibm.cics.server.invocation.jar, which provides support for the CICS annotation processor, a Java library that is used to create metadata that enables CICS programs to invoke Java applications in a Liberty JVM server.
- com.ibm.cics.server.invocation.annotations.jar, which provides support for
CICS annotations, a Java library that provides the
@CICSProgramannotation to enable CICS programs to invoke Java applications in a Liberty JVM server. - com.ibm.cics.server.jar, which provides support for the JCICS API.
- com.ibm.record.jar, which contains the Java API for legacy programs that use IByteBuffer from the Java Record Framework that came with VisualAge.