WebSphere Application Server Configuration

The configuration of WebSphere Application Server involves setting up a profile, data source, a number of servers and configuring the JMS and security settings. All these tasks can be performed by executing the configure target provided by the SDEJ.

The profile created by the configure target will take the following defaults unless specifically overridden when calling the target.

profile.name=AppSvr01
cell.name=${node.name}Cell

The command build configure should be executed from the <SERVER_DIR> directory to invoke automatic configuration. This target requires that the files AppServer.properties and Bootstrap.properties exist in the <SERVER_DIR>/project/properties¹directory. See the Cúram Server Developer's Guide for more information on the setup of a Bootstrap.properties. WebSphere Application Server Configuration shows example contents of the AppServer.properties file.

Figure 1. AppServer properties sample

## APPLICATION SERVER PROPERTIES

# Property to indicate WebSphere is installed.
as.vendor=IBM

# The username and encrypted password for admin server.
security.username=<e.g. websphere>
security.password=<encrypted password>

# The name of the WebSphere Node
node.name=MyNode

# The name of the server on which the application will be hosted.
curam.server.name=CuramServer
curam.server.port=2809

#####################################################
## THE FOLLOWING PROPERTIES ARE FOR WebSphere ONLY ##
#####################################################
# The alias that should be used for the database authorization
curam.db.auth.alias=databaseAlias

# HTTP Port for the server on which the client
# will be accessed
curam.client.httpport=9044

# HTTP Port for the server on which the Web services
# will be accessed
curam.webservices.httpport=9082

# Property to set JVM initial and maximum heap size.
curam.server.jvm.heap.size=1024

By default the configure target establishes a Type 4 Universal Driver (XA) data source. However, you may configure a Type 2 Universal Driver (XA) data source by setting the curam.db.type2.required property in the AppServer.properties file.

Also by default the configure target sets the JVM initial and maximum heap size to "1024" MB. However, you can override the default JVM initial and maximum heap size by setting the curam.server.jvm.heap.size property in the AppServer.properties file.

Note:

The setting of the Java heap as described in the WebSphere Application Server Configuration example and set by the configuration scripts is for illustrative purposes. Based on the size of your customized application, deployment strategy, etc. these settings may be too low or too high. The optimum value should be determined by monitoring the memory performance of your server.
Memory issues have been noticed with the WebSphere Application Server wrapped database drivers during the retrieval of large CLOBs and BLOBs (3MB+) from the database. These issues may be worked-around by increasing the Max Heap Size JVM parameter as appropriate on the deployed server.
The configure target cannot be run when H2 database is in use.²

¹ It is possible to override this default location for the properties file by specifying

-Dprop.file.location=<new location> when executing the configure target.

² For more information on H2 database consult the Cúram Third-Party Tools Installation Guide for Windows.