WebSphere brand IBM WebSphere Presence Server, Version 7.0

Defining the data sources

Data sources are the resources that provide connections to your relational databases. Use the Integrated Solutions Console to define data sources for the Presence Server database and the Usage Records database.

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
Before you begin, the following steps should be completed:
  • Started the application server
  • 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 databases:

  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.
    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, Creating a JDBC provider.
  4. Under Additional Properties, click Data sources.
  5. Click New.
  6. Type WPS DB DataSource in the Data source name field.
  7. Type jdbc/db in the JNDI name field.
  8. Select database_alias from the Component-managed authentication alias drop-down list, and click Next. database_alias is the authentication alias you created for the Presence Server database in the earlier task, Creating authentication aliases.
  9. DB2 Configure the database properties:
    1. Type database_name in the Database name field. This is the name of the Presence Server database, for example PSDB.
    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.
    5. Click Next.
  10. 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 Presence Server database, for example PSDB
    2. Select Oracle10g data store helper from the Data store helper class name drop-down list.
    3. Click Next.
  11. Verify that the values are correct, and click Finish.
  12. Return to the properties display for the JDBC provider.
  13. Under Additional Properties, click Data sources.
  14. Click New.
  15. Type WPSUR DataSource in the Data source name field.
  16. Type jdbc/ur in the JNDI name field.
  17. Select usageRecords_alias from the Component-managed authentication alias drop-down list, and click Next. usageRecords_alias is the authentication alias you created for the Usage Records database in the earlier task, Creating authentication aliases.
  18. DB2 Configure the database properties:
    1. Type database_name in the Database name field. This is the name of the usage records database, for example PSUR.
    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.
    5. Click Next.
  19. 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)
      • database_sid represents the system identifier for the usage records database, for example PSUR
    2. Select Oracle10g data store helper from the Data store helper class name drop-down list.
    3. Click Next.
  20. Verify that the values are correct, and click Finish.
  21. Click Save to save changes to the master configuration.
  22. Click OK when node synchronization has completed.
  23. Restart the application server, nodes, and deployment manager:
    1. Stop the application server. Click Servers > Server Types > WebSphere application servers, select the name of the server, and click Stop.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    2. Stop each node. Click System administration > Node agents, select all nodes, and click Stop.
    3. Stop the deployment manager. Click System administration > Deployment manager and click Stop.
    4. Start the deployment manager. Run the following command:
      • AIX was_profile_root/bin/startManager.sh
      • Linux was_profile_root/bin/startManager.sh

      Where:

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

      Where:

      • The was_profile_root path contains the name of a federated node profile (for example, Custom01).
    6. Start the application server. Click Servers > Server Types > WebSphere application servers, select the name of the server, and click Start.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.



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