Specifying the WebSphere environment variables

You must specify the IBM® WebSphere® Application Server environment variables so that Content Platform Engine can access its databases.

To specify the WebSphere environment variables:

1. Install JDBC drivers on each WebSphere Application Server node where you will deploy Content Platform Engine.
   1. Obtain the JDBC drivers for your database type.

      DB2®

      Access the IBM website and find the version of the Redistributable DB2 JDBC Driver that matches the version of the JDK on the system where WebSphere Application Server is installed.

      Microsoft SQL Server

      Access the Microsoft Support website and find the version of the SQL Server JDBC Driver that matches the version of the JDK on the system where WebSphere Application Server is installed.

      Oracle

      To obtain the JDBC driver file, browse to the web page that pertains to the Oracle Database version that you are using:

      • Oracle Database 11g Release 2 JDBC Drivers: http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-112010-090769.html
      • Oracle Database 12.1.0.1 JDBC Driver & UCP Downloads: http://www.oracle.com/technetwork/database/features/jdbc/jdbc-drivers-12c-download-1958347.html

   2. Extract and copy the JDBC driver file to the following suggested location:

      AIX®, HPUX, HPUXi, Linux, Solaris

      /opt/jars

      Do not copy the file to ...WebSphere/AppServer/lib/ext.

      Windows

      C:\jars

      Do not copy the file to ...WebSphere\AppServer\lib\ext.

2. Start the WebSphere Application Server administrative console and log on to your Content Platform Engine profile as appserver_console_user, the Administrator Console User and complete the following substeps to configure the Content Platform Engine nodes or cluster (if applicable).
   1. Navigate to Environment > WebSphere Variables.
   2. Select Cell scope from the All scopes list.
   3. Set the value of the variable to the JDBC driver path that you specified when you installed the JDBC drivers on the IBM WebSphere Application Server machine. (If the variable does not exist, create it and then set its value.)
   4. Select Node scope from the All scopes list. In a cluster configuration, select Node scope for all the nodes in the Content Platform Engine cluster.
   5. In the table of substitution variables, click the item name in the Name column that corresponds to the JDBC environment variable for your database type in the Database environment variables table below.

      Table 1. Database environment variables

      Database	JDBC Environment Variable
      SQL Server	MICROSOFT_JDBC_DRIVER_PATH
      Oracle	ORACLE_JDBC_DRIVER_PATH
      DB2	(JDBC 4.0) DB2_JCC_DRIVER_PATH

   6. Set the value of the name_JDBC_DRIVER_PATH item to the JDBC driver path you specified (/opt/jars or C:\jars).
   7. Optional: Select Server scope from the All scopes list. This step is not required unless you defined the JDBC_DRIVER_PATH variable at the server scope level.
   8. In the table of substitution variables, click the item name in the Name column that corresponds to the JDBC environment variable for your database type in the Database environment variables table.
   9. Set the value of the name_JDBC_DRIVER_PATH item to the JDBC driver path you specified (/opt/jars or C:\jars).
   10. Save your changes to the master configuration.
3. Navigate to Servers > Application servers > server1 > Java and Process Management > Process Definition > Java Virtual Machine, and set the initial and maximum heap sizes, where server1 is the name of the server where you will deploy Content Platform Engine.
   1. Set the values for the initial and maximum heap sizes:

      Table 2. Values for initial and maximum heap size

      Parameter	Value (in MB)
      Initial Heap Size	At least 512
      Maximum Heap Size	1024 or a size consistent with available RAM on the machine where WebSphere Application Server is installed

   2. Set the following JVM parameters:
      • -Duser.language=en
      • -Duser.region=US
      • -Duser.country=US
   3. Save your changes to the master configuration.
4. Optional: Increase the maximum transaction timeout to prevent administrative processes from failing:
   1. Navigate to the screen containing the Maximum transaction timeout parameter:
      • Click Servers > Server Types > WebSphere application servers > server1 > [Container Settings] Container Services > Transaction Service.
   2. Click the Configuration tab, and set the Maximum transaction timeout parameter value to at least 600 (seconds), and increase the Total transaction lifetime timeout as well.
      Important: If the timeout value is not large enough, some administrative processes (such as adding an expansion product) might fail.
   3. Click Apply and then click Save.
5. Repeat this procedure as needed for any object store that uses a different database type.