Appendix A - Deployment in IBM WebSphere Application server

1 minute read

Required knowledge

This is not an introduction to IBM WebSphere administration, the user must as a minimum know how to:

  • Open and log into the Integrated Solutions Console.
  • Create a JDBC data source and install JDBC drivers.
  • Create JDBC login credentials.
  • Install an Enterprise Application.

Refer to official IBM WebSphere documentation and support for assistance.

  1. Carry out the configuration steps described in section 9 “Configure the SICS Batch Server Environment”. Modifications to web.xml and other files must be carried out in the sbs.war file directly. All file path references in the instructions should therefore be read as the files within sbs.war.
  2. Log in to the WebSphere Integrated Solutions Console.
  3. Create a JDBC datasource for SICS, including JDBC provider if required.
  4. Create JDBC login credentials for the database user used by SICS Batch Server.
  5. Install sbs.war as an Enterprise Application. Make sure to set up the resource reference for the JDBC data source.
  6. Start the Enterprise Application.
  7. After SICS Batch Server is started, verify that SICS Batch Server is correctly started by inspecting the log file and opening the SICS Batch Server Management console.

NB:
If the entry for SICSServerJNDI in sics-database-sources.xml is set up to use parameterized SQL then statement cache size should be set to 0. Statement cache size should instead be set up in WebSphere.

Furthermore if the data source is an Oracle data source in combination with parameterized SQL, then the custom property, connectionProperties must be added and set to fixedString=true, for the Oracle data source. The property should be defined like this in the WebSphere Integrated Solutions Console:

Deploy Procedure with Application Managed Database Connection

  1. Carry out the configuration steps described in section “Configure the SICS Batch Server Environment” and “Application managed database connection”. The JDBC driver jars and modifications should be added/updated directly in sbs.war. All file path references in the instructions should therefore be read as the files within sbs.war.
  2. Log in to the WebSphere Integrated Solutions Console.
  3. Install sbs.war as an Enterprise Application.
  4. Start the Enterprise Application.
  5. After SICS Batch Server is started verify that SICS Batch Server is correctly started by inspecting the log file and opening the SICS Batch Server Management console.