WebSphere brand IBM WebSphere IP Multimedia Subsystem Connector, Version 6.2

Defining the data source

Data sources are the resources that provide connections to your relational database. Use the Integrated Solutions Console to define data sources.

Before you begin
Before you begin, the following software should be installed:
  • WebSphere® Application Server Network Deployment, version 7.0.0.7
  • One of the following supported databases:
    • IBM® DB2® Enterprise Server Edition, version 9.5.0.4 or 9.7.0.1
    • Oracle Database, version 11.1.0.7 or 11.2.0.1
  • JDBC JAR file or full database client for communicating with the database server
  • Diameter Enabler base
Before you begin, the following steps should be completed:
  • Started the deployment manager
  • Started the node agents
  • Created the database
  • Created WebSphere variables
  • Created an authentication alias for the database
  • Created the JDBC provider
About this task

Complete the following steps to define the data source to map the connection to the Diameter database:

  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 Resources > JDBC > JDBC Providers.
  3. Click the name of the JDBC provider for which you are configuring the data source, to display its properties. The JDBC provider was created in the previous task.
  4. Under Additional Properties, click Data sources.
  5. Click New.
  6. Type Diameter in the Data source name field.
  7. Type jdbc/diameter in the JNDI name field.
  8. Select diameter_alias from the Component-managed authentication alias drop-down list, and click Next.
  9. Oracle Configure the database properties:
    1. Type jdbc:oracle:thin:@host_name:port_number:database_sid in the URL field. Where:
      • host_name represents the host name of the server where Oracle Database is installed
      • port_number represents the port number used to access the database server (1521 is the default port)
      • database_sid represents the system identifier for the database you created
    2. Select Oracle10g data store helper from the Data store helper class name drop-down list.
    3. Click Next.
  10. DB2 Configure the database properties:
    1. Type database_name in the Database name field. This is the name of the database you created.
    2. Click 4 in the Driver type drop-down list to specify the connectivity type of the data source. This value corresponds with the driver type property in the data source class.
    3. Type server_name in the Server name field. This is the fully qualified host name for the DB2 server.
    4. Type port_number in the Port number field. This is the port the DB2 server is listening on. (Port 50000 is the default port.)
    5. Click Next.
  11. Select the Use this data source in container managed persistence (CMP) check box. Click Next.
  12. Verify that the values are correct, and click Finish.
  13. Click Save to save changes to the master configuration.
  14. Click OK when node synchronization has completed.
  15. Restart the deployment manager and the node agents.
    1. Stop the deployment manager. Run the following command:
      • AIX was_profile_root/bin/stopManager.sh -username user_name -password password
      • Linux was_profile_root/bin/stopManager.sh -username user_name -password password
      • Solaris was_profile_root/bin/stopManager.sh -username user_name -password password
      Note: The user_name and password parameters are required only when security is enabled.

      Where:

      • The was_profile_root path contains the name of the deployment manager profile (for example, Dmgr01).
      • user_name represents your WebSphere Application Server administrator user ID.
      • password represents the password associated with your user_name.
    2. Stop the node agent on each federated node. Run the following command:
      • AIX was_profile_root/bin/stopNode.sh -username user_name -password password
      • Linux was_profile_root/bin/stopNode.sh -username user_name -password password
      • Solaris was_profile_root/bin/stopNode.sh -username user_name -password password
      Note: The user_name and password parameters are required only when security is enabled.

      Where:

      • The was_profile_root path contains the name of a federated node profile (for example, Custom01).
      • user_name represents your WebSphere Application Server administrator user ID.
      • password represents the password associated with your user_name.
    3. Start the deployment manager. Run the following command:
      • AIX was_profile_root/bin/startManager.sh
      • Linux was_profile_root/bin/startManager.sh
      • Solaris was_profile_root/bin/startManager.sh

      Where:

      • The was_profile_root path contains the name of the deployment manager profile (for example, Dmgr01).
    4. Start the node agent on each federated node. Run the following command:
      • AIX was_profile_root/bin/startNode.sh
      • Linux was_profile_root/bin/startNode.sh
      • Solaris was_profile_root/bin/startNode.sh

      Where:

      • The was_profile_root path contains the name of a federated node profile (for example, Custom01).



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