WebSphere Application Server Configuration

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

The profile created by the Ant configure target will take the following defaults. When calling the target the cell.name property may be overriden; however, the profile.name property may not have any value other than "default" because that is the only value supported by WebSphere Application Server for z/OS.

The command build.sh 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/properties1directory. See Property Files, and 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.

By default the configure target establishes a DB2 Universal Type 4 Driver (XA) data source. However, you may configure a DB2 Universal Type 2 Driver (RRS) data source by setting the curam.db.type2.required property in AppServer.properties. When using this property you must have the DB2DIR environment variable set to your DB2 for z/OS installation path.

There are a number of possible ways of configuring DB2 for z/OS and WebSphere Application Server for z/OS to support a Type 2 driver. You should review the WebSphere Application Server, Version 7.0 Information Center and the article "DB2 Universal JDBC Driver Support", and related information.

It is possible to configure a Type 2 Universal Driver by passing an optional property curam.db.zos.jcc.propfile, specifying the fully qualified name of a DB2 for z/OS jcc property file that will be set in the servant JVM db2.jcc.propertiesFile property, which may contain various settings such as the subsystem ID.

Figure 1. Sample AppServer properties file
## 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 Cell.
cell.name=mycell

# 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 alias that should be used for the database authorization
curam.db.auth.alias=dbadmin

# 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 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.

For WebSphere Application Server for z/OS you must also include a property cell.name that is equal to the long name of the cell.

Note:
  1. 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.
  2. Memory issues may occur with the WebSphere Application Server for z/OS 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.
Parent topic: Application Server Configuration
1 It is possible to override this default location for the properties file by specifying

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