WebSphere brand IBM WebSphere IP Multimedia Subsystem Connector, Version 6.2

Creating WebSphere variables

WebSphere variables define a parameter for the system. To enable communication between the application server and the database, you must create WebSphere variables to specify the path to the JAR files on the database client.

Before you begin
Note: In the previous topic, Creating a JDBC provider, you may have already entered the directory location path to these files because they are in the same location on all of the federated nodes in your cell. If the directory location path was entered, the variable has already been created; skip this procedure and proceed to the following topic, Defining the data source. In the future, updates to the directory location path must be made to the variable from both the cell scope and from each node's scope.
Before you begin, the following software should be installed:
  • A supported version of WebSphere® Application Server Network Deployment

    For a list of required WebSphere Application Server fixes, refer to the readme file, WebSpheresoftwareForTelecomReadme.html, on the QuickStart CD.

  • One of the following supported databases:
    • DB2 IBM® DB2® Enterprise Server Edition
    • Oracle Oracle Database
  • JDBC JAR file or full database client for communicating with the database server
Before you begin, the following steps should be completed:
  • Started the application server
  • Created the database
  • Created JDBC provider
About this task
After you have installed the database client on the server where you installed WebSphere Application Server, you must create a WebSphere variable to enable communication between the application server and the database server.
Important: Install the database client in the same location on each physical server.
  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password. (Omit the password if security is not enabled.)
    3. Click Log in.
  2. In the navigation pane, click Environment > WebSphere Variables.
  3. Select node_name from the Scope drop-down list.
  4. Create the JDBC driver path variable:
    1. Perform one of the following:
      • If the variable is not defined, click New.
      • If the variable is already defined, click its name.
    2. In the Name field, type:
      • DB2 DB2UNIVERSAL_JDBC_DRIVER_PATH
      • Oracle ORACLE_JDBC_DRIVER_PATH
    3. In the Value field, type the path to the database client JAR files. For the path, use the following format where db_client_root is the path where you installed the database client:
      • DB2 /db_client_root/java
      • Oracle /db_client_root/jdbc/lib
      This path is where you would find the following JAR files:
      • DB2 db2jcc.jar and db2jcc_license_*.jar
      • Oracle classes*.jar and ojdbc14*.jar
    4. Click OK.
  5. Repeat steps 3 and 4 for each node.
  6. Click Save to save changes to the master configuration.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.