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:
- Log in to the Integrated Solutions Console:
- 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.
- Enter an administrator user ID and password.
- Click Log in.
- In the navigation pane, click .
- 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.
- Under Additional Properties, click Data
sources.
- Click New.
- Type WPS DB DataSource in
the Data source name field.
- Type jdbc/db in
the JNDI name field.
- 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.
Configure the database
properties:- Type database_name in
the Database name field. This is the name of the Presence Server database,
for example PSDB.
- 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.
- Type server_name in
the Server name field. This is the
fully qualified host name for the DB2 server.
- Type port_number in
the Port number field. This is
the port the DB2 server
is listening on.
- Click Next.
Configure the
database properties:- 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
- Select Oracle10g data store helper from
the Data store helper class name drop-down
list.
- Click Next.
- Verify that the values are correct,
and click Finish.
- Return to the properties display for the JDBC provider.
- Under Additional Properties, click Data
sources.
- Click New.
- Type WPSUR DataSource in
the Data source name field.
- Type jdbc/ur in
the JNDI name field.
- 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.
Configure the
database properties:- Type database_name in
the Database name field. This
is the name of the usage records database, for example PSUR.
- 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.
- Type server_name in
the Server name field. This is the
fully qualified host name for the DB2 server.
- Type port_number in
the Port number field. This is
the port the DB2 server
is listening on.
- Click Next.
Configure the
database properties:- 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
- Select Oracle10g data store helper from
the Data store helper class name drop-down
list.
- Click Next.
- Verify that the values are correct,
and click Finish.
- Click Save to
save changes to the master configuration.
- Click OK when
node synchronization has completed.
- Restart the application server, nodes,
and deployment manager:
- Stop the application server. Click ,
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 .
- Stop each node. Click , select all nodes, and click Stop.
- Stop the deployment manager. Click and click Stop.
- Start the deployment manager. Run
the following command:
was_profile_root/bin/startManager.sh
was_profile_root/bin/startManager.sh
Where:
- The was_profile_root path
contains the name of the deployment manager profile (for example,
Dmgr01).
- Start each node. Run
the following command:
was_profile_root/bin/startNode.sh
was_profile_root/bin/startNode.sh
Where:
- The was_profile_root path
contains the name of a federated node profile (for example, Custom01).
- Start the application server. Click ,
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 .