Configure WebSphere

Before you start

1. Add Java Cryptography Extension (JCE) to your Java environment. Download the appropriate JCE package for your Java Virtual machine and copy it to the [websphereinstallation]/IBM/WebSphere/AppServer/java/jre/lib/security folder.
2. Install Java SDK 1.7_xx and change the WebSphere java SDK version to the installed version (1.7_xx). Refer to the WebSphere documentation for more information.
3. If the ojdbc7.jar (jar name might differ) does not exist in the WebSphere server classpath, copy it into the WebSphere\AppServer\lib\ext folder. You must use version 12.1.0.1.0 for the ojdbc driver.

Overview

To configure WebSphere, you must:

• Create a new environment variable
• Create a JDBC provider
• Create J2C authentication data
• Create the JDBC Datasources
• Create the shared libraries
• Create the resource environment provider
• Create resource environment entries and custom properties

Create a new environment variable

If the WebSphere environment variable ORACLE_JDBC_DRIVER_PATH exists, just update the value field to ${WAS_INSTALL_ROOT}\lib\ext. Otherwise, follow the procedure below.

Create a new WebSphere environment variable called ORACLE_JDBC_DRIVER_PATH that points to the folder where you placed the ojdbc7 jar:

1. On the Integrated Solutions console, from the left side menu, select Environment > WebSphere variables.
2. In the Websphere Variables screen:
   • Select a scope for your variable from the Scope drop-down menu.
   • In the Preferences section, click New.
3. The new variable Configuration screen is displayed.
4. Fill the general properties for the variable:
   • Value: ${WAS_INSTALL_ROOT}/lib/ext, click
   • Description: The directory that contains the Oracle thin or oci8 JDBC Driver
5. Click Apply.
6. In the Websphere Variables screen, go to the Preferences section and check that your variable appears in the list.
7. The Value field assigned to the variable now displays ${WAS_INSTALL_ROOT}\lib\ext.

Create a JDBC provider

When you create a JDBC provider, the ojdbc7.jar is located at the address specified in the ${ORACLE_JDBC_DRIVER_PATH} variable.

To create a JDBC provider:

1. On the Integrated Solutions console, from the left side menu, select Resources > JDBC > JDBC providers.
2. In the Create a new JDBC Provider screen :
   1. Enter JDBC provider general information and description, and click Next.
   2. For example:
      • Database type: Oracle
      • Provider type: Oracle JDBC Driver
      • Implementation type: Connection Pool Datasource
      • Name: Oracle JDBC Driver
   3. The Enter database class path information screen is displayed.
   2. Enter database Class path information and click Next.
   3. For example, Classpath: ${ORACLE_JDBC_DRIVER_PATH}/ojdbc7-12.1.0.1.0.jar.
   4. The Summary page is displayed.
   3. Click Finish.
3. In the JDBC providers screen:
   • In the Scope section, select the last available Scope option in the combo-box.
     
   • Click the New action.

Create J2C authentication data

To create J2C authentication data to enable Datastore ClientDesigner or Report Server to connect to the database:

1. On the Integrated Solutions console, from the left side menu, select Security> Global security.
2. In the Global Security screen:
   1. In the Authentication section, go to Java Authentication and Authorization Service and click J2C authentication data.
   2. The J2C authentication data screen is displayed.
   2. Click the New action to create new J2C alias.
   3. The New item screen is displayed.
   3. In the General Properties section, enter user name and password for the Datastore Client Database.
3. Click Apply and Save.
4. Repeat the procedure to create an authorization for the Repository database (user name and password ), Designer and Report Server.
   It is assumed that Oracle DB is also used for the configuration repository.

You use the:

• Alias to select the correct authorization from the list.
• User name and password to connect to the database.

Create the JDBC Datasources

To create a JDBC Datasource (Datastore Client, Designer, Report Server and Repositorydatasources):

1. On the Integrated Solutions console, from the left side menu, select Resources> JDBC> Data sources.
2. In the Data sources screen:
   1. Select the Scope.
   2. Click New.
   3. The Create a Datasource screen is displayed.
3. In the Create a data source page:
   1. Enter datasource basic information and click Next.
   2. The Select a JDBC provider screen is displayed.
   3. Example:
   4. For Datastore Client:
      • JNDI Name: jndi/datastorecClientDatasource
      • Datasource Name: datastoreClientDatasource
   5. For Designer:
      • JNDI Name: jndi/designerDatasource
      • Datasource Name: designerDatasource
   6. For Repository
      • JNDI Name: jndi/repositoryDatasource
      • Datasource Name: repositoryDatasource
   7. For Report Server
      • JNDI Name: jndi/reportingDatasource
      • Datasource Name: reportingDatasource
   2. Select Select an existing JDBC provider, choose a provider from the drop-down list, and click Next.
   3. For anOracle setup you can choose the previously created JDBC Provider.
   4. The Enter database specific properties for the datasource screen is displayed.
   3. Fill the required fields and click Next.
      For example, for the Datastore Client URL, you can use: jdbc:oracle:thin:@//localhost:1521/ORCL.
   4. The Setup security aliases page is displayed.
   4. Select the authentication values for the resource and then click Next:
      • Component-managed authentication alias: Use the drop-down list to select the J2C authentication alias previously created.
      • Mapping-configuration alias: select DefaultPrincipalMapping Container-managed authentication alias: None.
   5. The Summary screen is displayed.
   5. Click Finish and Save.
4. Go to the Data sources screen, in the Preferences section:
   1. Select the new datasource.
   2. Click Test connection.
5. Repeat the procedure to create a JDBC datasource for the Configuration Repository with:
   • jndi/configDatasource ws85_220_repositoryDS as JNDI name.
   • ws85_220_repositoryDS as data source name.
6. You must however change the user authorization.

Create the shared libraries

You create the shared library to externalize Datastore Clientor the Designer parameters. For more information, refer to Using resource environment providers in WebSphere application

1. On the Integrated Solutions console, in the left side menu, select Environment > Shared libraries.
2. In the Shared libraries screen:
   1. Enter Scope.
   2. Click New.
   3. The new library Configuration page is displayed.
3. In the new shared library Configuration page, fill the general properties (Name, Classpath)
4. • Name: jndiRes
   • Classpath: D:\\WAS85\jndires\aiservices-commons-jndires-2.x.x.jar (points to a jar named aiservices-commons-jndires-2.x.x.jar located in the WAS85\jndires\ directory.
   • You can find the jar in [InstallP_Path]/Datastore/DatastoreClient/ war\WEB-INF but it is recommended that you copy this jar into a folder of your choice.
4. Click Apply.
   

Create the resource environment provider

1. On the Integrated Solutions console, in the left side menu, select Resources > Resource Environment > Resource Environment Providers.
2. In the Resource environment providers screen:
   1. Enter Scope.
   2. Click New.
   3. The Resource environment providers screen is displayed
3. In the Configuration section of the Resource environment providers screen, enter a name, for example, ResourceEnvironmentProvider, and click Apply.
4. In the Additional Properties section, click Referenceables.
5. The Referenceables screen is displayed.
5. Click New.
6. In the New Referenceable screen, fill the General Properties:
   • Factory class name: com.axway.ais.jndires.factories.ConfigFactory
   • Class name: com.axway.ais.jndrires.AppConfig
7. Click Apply.

Create a TimerManager resource

This step is optional as the Default TimerManager can be used for Datastore Clientor the Designer installation.

1. In the Integrated Solutions console, select Resources > Asynchronous beans > Timer managers.
2. In the Timer Managers screen:
   1. Enter Scope.
   2. Click New.
      
3. In the Configuration section, complete the TimerManager general properties:

4. Field	Description
   Name	Display name for the new resource
   JNDI Name	Java Naming and Directory Interface (JNDI) name for the timer manager. This name is used by asynchronous beans that need to look up the timer manager. Each timer manager must have a unique JNDI name within the cell.
   Number of Timer threads	Maximum number of threads that are used for timers. Usually 2 threads, also used for the default TimerManager, should be enough for an Datastore Clientor the Designer installation.
   Optional fields
   Description and Category	Description and Category for the timer manager
   Service Names	Service Names (J2EE contexts) where you want this timer manager to be made available. Any asynchronous beans that use this timer manager then inherit the selected J2EE contexts from the component that creates the bean. The list of selected services is also known as the "sticky" context policy for the timer manager. Selecting more services than are actually required might impede performance.

4. Click Apply

Create a WorkManager resource

This step is optional as the Default WorkManager can be used for a Datastore Client or the Designer installation.

1. On the Integrated Solutions console, select Resources > Asynchronous beans > Work managers.
2. In the Work Managers screen:
   1. Enter Scope.
   2. Click New.
      
3. In the Configuration section, complete the WorkManagerForm general properties:
   

4. Field	Description
   Name	Display name for the WorkManager
   JNDI Name	Java Naming and Directory Interface (JNDI) name for the work manager. This name is used by asynchronous beans that need to look up the work manager. Each work manager must have a unique JNDI name within the cell.
   Number of Alarm threads	Maximum number of threads to use for processing alarms. A single thread is used to monitor pending alarms and dispatch them. An additional pool of threads is used for dispatching the threads. All alarm managers on the asynchronous beans associated with this work manager share this set of threads. A single alarm thread pool exists for each work manager, and all of the asynchronous beans associated with the work manager share this pool of threads.
   Optional fields
   Service Names	Service Names (J2EE contexts) where you want this timer manager to be made available. Any asynchronous beans that use this timer manager then inherit the selected J2EE contexts from the component that creates the bean. The list of selected services is also known as the "sticky" context policy for the timer manager. Selecting more services than are actually required might impede performance.
   Minimum Number Of Threads	Number of threads to be kept in the thread pool, created as needed.
   Maximum Number Of Threads	Maximum number of threads to be created in the thread pool. The maximum number of threads can be exceeded temporarily if the Growable check box is selected. These additional threads are discarded when the work on the thread is completed.
   Thread priority	Priority to assign to all threads in the thread pool. Every thread has a priority. Threads with higher priority are run before threads with lower priority. For more information about how thread priorities are used, refer to the Javadoc for the setPriority method of the java.lang.Thread class in the Java Standard Edition specification.
   Work timeout	Number of milliseconds to wait before a scheduled work object is released. If a value is not specified, then the timeout is disabled.
   Work request queue size	Size of the work request queue. The work request queue is a buffer that holds scheduled work objects. The thread pool pulls work from this queue. Possible values are: 0 - The queue size is managed automatically. 1 or greater When the queue size is managed automatically, it is computed as the (minimum_number_of_threads + maximum_number_of_threads) / 2. If this value computes to a zero value, a queue size of 1 is used. Large values can consume significant system resources.
   Work request queue full action	Action taken when the thread pool is exhausted, and the work request queue is full. This action starts when you submit non-daemon work to the work manager. If set to FAIL, the work manager API methods creates an exception instead of blocking.

4. Click Apply
5. Save your configuration.