netskink
commented
1 week ago Here is the server.xml
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<server description="CICS Liberty sample configuration">
<!-- Enable features -->
<featureManager>
<feature>cicsts:core-1.0</feature>
<feature>cicsts:defaultApp-1.0</feature>
<feature>jsp-2.3</feature>
<feature>wab-1.0</feature>
<feature>jaxrs-2.0</feature>
<feature>cicsts:security-1.0</feature>
<!-- JFD Added for cicsdev README.md instructions -->
<feature>cicsts:link-1.0</feature>
</featureManager>
<!-- Default HTTP End Point -->
<httpEndpoint host="*" httpPort="16019" id="defaultHttpEndpoint"/>
<!-- The following configuration controls how often server.xml
is scanned for updates. The default is every 500ms which may
cause excessive I/O and CPU cost on z/OS.
The values shown below reduce the overhead while still
providing a relatively timely detection of new applications
that have been installed/removed via a CICS Bundle
(WAR bundlepart). If you use CICS bundles to install Web
Applications (WAR files) do not disable the polling.
-->
<config monitorInterval="5s" updateTrigger="polled"/>
<!-- Further scanning is performed to detect application updates or
addition/removal of applications to the dropins directory. If
you are using CICS Bundles as the vehicle for Application
deployment you should disable the dropins directory as shown.
Further I/O and CPU reduction can be achieved by disabling
the application scan. To effect changes to your applications
while the server is still running, you should disable and
re-enable the CICS bundle that contains the Web application.
The pollingRate is only applicable when the updateTrigger is
set to the 'polled' value.
Consult the WebSphere Application Server Liberty Profile
documentation for further information on these parameters.
-->
<!-- JFD the cicsdev README.md says to reduce z/FS overhead by
reducing config and app polling with the following change:
updateTrigger="disabled"
dropins="dropins"
dropinsEnabled="false"
pollingRate="5s"
-->
<applicationMonitor dropins="dropins" dropinsEnabled="true" pollingRate="5s" updateTrigger="polled"/>
<!-- By default, the cdi-1.2 feature scans all application archives.
The cdi-1.2 feature can increase startup time substantially
and have the most effect on larger applications. Implicit
archive scanning for annotations can be disabled by setting
enableImplicitBeanArchives value to false. This setting skips
the scanning of archives unless they contain a beans.xml.
Even if not explicitly coded, the cdi-1.2 feature might be
enabled through other features, such as the javaee-7.0
convenience feature.
-->
<cdi12 enableImplicitBeanArchives="false"/>
<safRegistry enableFailover="false" id="saf"/>
<dataSource id="defaultCICSDataSource" jndiName="jdbc/defaultCICSDataSource" transactional="false">
<jdbcDriver libraryRef="defaultCICSDb2Library"/>
<properties.db2.jcc driverType="2"/>
<connectionManager agedTimeout="0"/>
</dataSource>
<library id="defaultCICSDb2Library">
<fileset dir="/C/DB2/DB2D10/usr/lpp/db2d10/jdbc/classes" includes="db2jcc4.jar db2jcc_license_cisuz.jar"/>
<fileset dir="/C/DB2/DB2D10/usr/lpp/db2d10/jdbc/lib" includes="libdb2jcct2zos4_64.so"/>
</library>
<include id="cics_auto" location="${server.output.dir}/installedApps.xml" onConflict="IGNORE"/>
<executor coreThreads="6" id="allowCICSconfigure" maxThreads="15"/>
</server>
My setup
I am using the gradle method to build. ie:
The war file is
build/libsusing file namecics-java-liberty-restapp-0.1.0.war.According to the section on building a war file, it specified to modify the
~/U31CIHBH/wlp/usr/servers/defaultServer/server.xmlto have either:or
based upon JEE version. Not knowing which version is used, I tried both. Both failed. My IBM JDK is 17.
I placed the war file in the
~/U31CIHBH/wlp/usr/servers/defaultServer/dropinsfolder. I noticed the jvm modified the~/U31CIHBH/wlp/usr/servers/defaultServer/apps/expandedfolder to have the war file there.In WLPOUT log in sysview in SDSF mode, I have the following messages relative to the sample app:
I don't have any experience with bundles at this point. It was mentioned as an optional step so I did not attempt those sections of the readme.md.
URL TESTING
URL 1
Using this url:
http://ca31.lvn.broadcom.net:16019/com.ibm.cicsdev.restapp/rest/cicsinfo/output
webpage says "Context Root Not Found"
URL 2
Using a variant of what is reported in
WLPOUT:DFHWLP : .AUDIT . CWWKT0016I: Web application available (default_host): http://10.175.79.129:16019/cics-java-liberty-restapp-0.1.0/I modified the URL as:URL 3
Using this url:
http://ca31.lvn.broadcom.net:16019/cics-java-liberty-restapp-0.1.0/rest/cicsinfoFile not found /rest/cicsinfo
Using this url:
ca31.lvn.broadcom.net:16019/cics-java-liberty-restapp-0.1.0File not found /
URL 4
Using this url:
http://ca31.lvn.broadcom.net:16019/cics-java-liberty-restapp-0.1.0/cicsinfoFile not found /cicsinfo