Manually tailoring server.xml
If you want to make manual changes to your server.xml, there are some basic configurations you can apply. Your CICS® region user ID needs to have both read and write access to the server.xml file.
Configuring the HTTP endpoint
<httpEndpoint host="winmvs2c.example.com" httpPort="28216" httpsPort="28217"
id="defaultHttpEndpoint"/>
Use a port number that can be opened by the CICS region, either exclusively or as a shared port.
HTTPS is available only if SSL is configured as described in Configuring SSL (TLS) for a Liberty JVM server using a Java keystore.
For more information, see Liberty overview.
Adding features
Add the following features in the <featureManager> list of features.
- CICS feature cicsts:core-1.0. This feature installs the CICS system OSGi bundles into the Liberty framework. This feature is required to start a CICS integrated-mode Liberty JVM server. You must also define a SAF registry.
CICS feature
cicsts:standard-1.0. This feature is required to start a CICS standard-mode Liberty JVM server. The
cicsts:standard-1.0 feature does not have access to CICS resources by default. For more information see CICS standard-mode Liberty: Java EE 7 Full Platform support without full CICS integration.Note: Specify either the cicsts:core-1.0 or cicsts:standard-1.0 feature. You cannot specify both features in server.xml.
- CICS security feature cicsts:security-1.0. This feature installs the CICS system OSGi bundles that are required for CICS Liberty security into the Liberty framework. This feature is required when CICS external security is enabled (SEC=YES in the SIT) and you want security in the Liberty server. To use the cicsts:security-1.0 feature, you must also configure a user registry. For more information, see User registry.
- jsp-2.3. This feature enables support for servlet and JavaServer Pages (JSP) applications. This feature is required by Dynamic Web Projects (WAR files) and OSGi Application Projects containing OSGi Bundle Projects with Web Support that are installed as CICS bundles.
- cicsts:jdbc-1.0. This feature enables applications to access DB2 through the JDBC DriverManager or DataSource interfaces.
<featureManager>
<feature>cicsts:core-1.0</feature>
<feature>cicsts:security-1.0</feature>
<feature>jsp-2.3</feature>
<feature>cicsts:jdbc-1.0</feature>
</featureManager>
For more information, see Liberty features.
CICS bundle deployed applications
<include location="${server.output.dir}/installedApps.xml"/>
The
included file is used to define CICS bundle deployed
applications.Bundle repository
<bundleRepository>
<fileset dir="directory_path" include="*.jar"/>
</bundleRepository>
Global/shared library
<library id="global">
<fileset dir="directory_path" include="*.jar"/>
</library>
The
global/shared libraries cannot be used by OSGi applications in an EBA, which must use a bundle
repository. For more information, see Providing global libraries for all Java EE applications or Liberty: Shared libraries.Liberty server application and configuration update monitoring
<config monitorInterval="5s" updateTrigger="polled"/>
<applicationMonitor updateTrigger="disabled" dropins="dropins"
dropinsEnabled="false" pollingRate="5s"/>
For more information, see Controlling dynamic updates.
JTA transaction log
<transaction transactionLogDirectory="/u/cics/CICSPRD/DFHWLP/tranlog/"/>
CICS default web application
The CICS default web application CICSDefaultApp is a configuration service that validates the Liberty JVM server has started. To make the application available, add the JVM profile option com.ibm.cics.jvmserver.wlp.defaultapp=true to your JVM profile, or if you are not using autoconfigure, add the cicsts:defaultApp-1.0 feature to server.xml. Run the application by using the URL http://<server>:<port>/com.ibm.cics.wlp.defaultapp/.
<featureManager>
<feature>cicsts:defaultApp-1.0</feature>
</featureManager>
User registry
<safRegistry id="saf"/>
For more information, see Configuring security for a Liberty JVM server by using distributed identity mapping or Java Database Connectivity 4.1.
CICS JTA integration
If an XA transaction is used by Liberty, the CICS unit-of-work becomes subordinate to the XA transaction by default. You can opt out of this automatic integration of CICS with JTA by setting the JVM profile option com.ibm.cics.jvmserver.wlp.jta.integration=false. If you are not using autoconfigure, you can manually set the element in your server.xml: <cicsts_jtaIntegration=false>.