Manually tailoring server.xml
If you are not using automatic configuration, make the following changes to your server.xml file to tailor it to your environment.
Configuring HTTP endpoint
<httpEndpoint host="winmvs2c.example.com" httpPort="28216" httpsPort="28217"
id="defaultHttpEndpoint"/>
Use a port number that is not in use elsewhere, for example by a TCPIPSERVICE in CICS®.
HTTPS is available only if SSL is configured (see Configuring security for a Liberty JVM server).
For more information, see the WebSphere® Application Server Liberty Profile documentation.
Adding features
Add the following features in the <featureManager> list of features.
- The CICS feature
cicsts:core-1.0
installs the CICS system OSGi bundles into the Liberty framework. This feature is required for the JVM server to start. - The CICS security feature
cicsts:security-1.0
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. - The
jsp-2.2
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. - The
wab-1.0
feature enables support for Web Archive Bundles (WABs) that are inside enterprise bundles (EBAs). This feature is required by OSGi Application Projects containing OSGi Bundle Projects with Web Support that are installed as CICS bundles. - The
cicsts:jdbc-1.0
feature enables applications to access DB2® through the JDBC DriverManager or DataSource interfaces. - The
sessionDatabase-1.0
feature enables Session Database Persistence in CICS Liberty. For further information see Configuring session persistence for the Liberty profile.
<featureManager>
<feature>cicsts:core-1.0</feature>
<feature>cicsts:security-1.0</feature>
<feature>jsp-2.2</feature>
<feature>wab-1.0</feature>
<feature>cicsts:jdbc-1.0</feature>
<feature>sessionDatabase-1.0</feature>
</featureManager>
CICS Bundle deployed applications
<include location="${server.output.dir}/installedApps.xml"/>
The
included file is used to define CICS Bundle
deployed applications. Bundle repository
Share common OSGi bundles by placing them in a directory and referring to that directory in a bundleRepository element. For example:<bundleRepository>
<fileset dir="directory_path" include="*.jar"/>
</bundleRepository>
Global library
Share common JAR files between web applications by placing them in a directory and referring to that directory in a global library definition.<library id="global">
<fileset dir="directory_path" include="*.jar"/>
</library>
The global libraries cannot be
used by OSGi applications in an EBA, which must use a bundle
repository.Liberty server application and configuration update monitoring
<config monitorInterval="5s" updateTrigger="polled"/>
It also scans the dropins directory to detect the addition, update, or removal of applications. If you install your web applications in CICS bundles, disable the dropins directory as follows:
<applicationMonitor
updateTrigger="disabled" dropins="dropins" dropinsEnabled="false"
pollingRate="5s"/>
.
JTA transaction log
<transaction transactionLogDirectory="/u/cics/CICSPRD/DFHWLP/tranlog/"/>