IBM Cúram Social Program Management Version 6.0.5 Cúram Deployment Guide for WebSphere Application Server
This guide covers the steps needed to build an IBM Cúram Social Program Management application for deployment on the base version of IBM WebSphere Application Server. It explains how to package the server application and web services application into separate EAR files using build targets from the Server Development Environment, including the websphereEAR target and the required WAS_HOME environment variable.
The document also details application server configuration, including security configuration, data sources for DB2 and Oracle, JAAS login module setup, JMS and bus configuration, and manual deployment steps. A separate section covers WebSphere Network Deployment, including creating profiles, federating a node, and deploying on the node. Readers are expected to know the Cúram development environment and have WebSphere Application Server installed.
Run the build target "build websphereEAR" from the root directory of the server project, with WAS_HOME set to the WebSphere installation directory. The EAR file is created in
WAS_HOME must be set to point to the base directory of the base WebSphere Application Server installation, for example d:\WebSphere\AppServer or /opt/WebSphere/AppServer.
No, an EAR file cannot be built for the H2 database. The Cúram Third-Party Tools Installation Guide for Windows has more information on the H2 database.
In the administrative console, go to Servers > Server Types > WebSphere application servers, select the server, then under Logging and Tracing > JVM Logs set the Maximum Number of Historical Log Files field to 30 for both System.out and System.err files.