You can configure multiple Dynamic Workload Console instances
to share a DB2® database as a
common repository instead of a local directory in a High Availability
configuration of nodes.
Before you begin
Note: Exporting data from a Tivoli® Integrated Portal High Availability
configuration directly to a Dashboard Application Services Hub High
Availability configuration is not supported. You must migrate your Tivoli Integrated Portal environment
to a Dashboard Application Services Hub environment
and then enable a High Availability configuration in the new environment.
If you are creating a High Availability configuration
from an existing Dynamic Workload Console instance
that contains custom data, ensure that you have exported its data
before you begin to configure it for High Availability. After it is
configured, you can import the data to one of the nodes in the new
configuration.
Dynamic Workload Console is
installed on a machine using the cell name designated for all console
nodes within the High Availability configuration. Ensure you have
installed and set up a network dispatcher (for example, IBM HTTP Server), DB2, and an LDAP as
explained in Requirements.
Note: Dynamic Workload Console server
must be configured using DB2 without
SSL connection. If you want to configure SSL connection, you can enable
it after having successfully enabled the High Availability configuration.
For more information, see
Enabling SSL for Dashboard Application Services HubServer.
About this task
To implement a High Availability configuration, follow the
procedure:
Procedure
- Ensure you have already created a DB2 database on the computer where DB2 is installed (see Creating databases), and completed the procedure
to the change the Dynamic Workload Console settings
repository from a local file repository to a settings repository on
the database. This database is shared as a common repository for nodes
that will be subsequently joined to the High Availability configuration.
The database administrator must have the ability to create tables.
To create a new database, see Creating databases. To use an existing database,
see Changing settings repository.
- Check that you have the JDBC
driver for DB2 on the computer
where the Dynamic Workload Console is
installed. The JDBC driver must be available at: JazzSM install_dir/lib/db2.
- Configure a data source in the WebSphere Application Server administrative console and for
the Java™ Naming and Directory
Interface (JNDI) name use jdbc/tipds. For
information on configuring a data source in the WebSphere Application Server administrative console, see http://www-01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.base.doc/ae/tdat_ccrtpds.html.
In relation to setting up a data source
for a high availability configuration in Dashboard Application Services Hub, note the following points:
- Create the ${DB2UNIVERSAL_JDBC_DRIVER_PATH} variable in the WebSphere Application Server administrative console.
- From the WebSphere Application Server console, expand Environment and
select WebSphere variables.
- Click the DB2UNIVERSAL_JDBC_DRIVER_PATH variable
from the list of variables in the right pane to edit the value.
- On the Configuration page, enter the path
to the directory that contains the DB2 Universal JDBC Driver in the Value field.
- Click OK to save the changes.
- When creating the new JDBC provider:
- When creating a new data source:
- In the WebSphere Integrated Solutions Console, open .
- Under Scope, select cells:JazzSMCell:nodes:JazzSMNode:servers:server1 and
click New.
- In Step 1, enter the data source and JNDI names and then click Next:
- Data source name: tipds.
- JNDI name: jdbc/tipds.
- In Step 2, select the JDBC provider that you created, for example, DB2
Universal JDBC Driver Provider and click Next.
- In Step 3, enter the specific database properties for the data
source:
- Driver type: 4
- Database name is the database created in DB2, for example, dashdb
- Check the CMP check box.
- Click Next.
- In Step 4, set up any necessary security aliases and then click Next.
Select the DB2 administrator's authentication alias from the Component-managed
authentication alias option.
- In Step 5, the summary of the new data source is provided. Click Finish.
- Click Save to save the changes.
- Create the Global J2C authentication alias using a DB2 user ID
that has permissions to create and modify database tables:
- In the WebSphere Integrated Solutions Console, open .
- From the table, click the data source you just created. Click
the link, do not just select the check box.
- Under Related Items, click JAAS
- J2C authentication data.
- Click New and set the fields Alias, User
ID (the database of the master domain manager), and the
DB2 Password.
- Click Apply and Save.
- Again, open and click your data
source name.
- In Component-managed authentication alias,
select the J2C authentication alias.
- In Mapping configuration alias select DefaultPrincipalMapping.
- Click Apply and Save.
- Stop and restart the Jazz for Service Management
application server.
- In the JazzSM_WAS_Profile/bin directory,
for a server named server1,
run the following command:
- On Windows
- stopServer.bat server1
- On UNIX
- stopServer.sh server1
Note: You are prompted to provide an administrator
username and password.
- In the JazzSM_WAS_Profile/bin directory,
for a server named server1,
run the following command:
- On Windows
- startServer.bat server1
- On UNIX
- startServer.sh server1
Results
The High Availability configuration is created and the
Dynamic Workload Console node
is joined to the configuration as the first node.
What to do next
Next, add (or join) additional nodes to the configuration.