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:
- 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. (Omit the password if security is
not enabled.)
- 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.
- Under Additional Properties, click Data
sources.
- Click New.
- Type Diameter in
the Data source name field.
- Type jdbc/diameter in
the JNDI name field.
- Select diameter_alias from
the Component-managed authentication alias drop-down
list, and 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 database you created
- Select Oracle10g data store helper from
the Data store helper class name drop-down
list.
- Click Next.
Configure the database
properties:- Type database_name in
the Database name field. This
is the name of the database you created.
- 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. (Port 50000 is the
default port.)
- Click Next.
- Select the Use this data source
in container managed persistence (CMP) check box. 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 deployment manager and the node agents.
- Stop the deployment manager. Run
the following command:
was_profile_root/bin/stopManager.sh -username user_name -password password
was_profile_root/bin/stopManager.sh -username user_name -password password
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.
- Stop the node agent on each federated node. Run
the following command:
was_profile_root/bin/stopNode.sh -username user_name -password password
was_profile_root/bin/stopNode.sh -username user_name -password password
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.
- Start the deployment manager. Run
the following command:
was_profile_root/bin/startManager.sh
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 the node agent on each federated node. Run
the following command:
was_profile_root/bin/startNode.sh
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).