Cisco Cisco Prime Service Catalog 10.0 Installation Guide

1-45

Cisco Prime Service Catalog Installation Guide

OL-31035-01

Chapter 1 Installation and Configuration Guide

Preinstallation Configuration for WebSphere

Figure 1-9

SQL Server Data Source – Custom Properties

Step 26

Click Save directly to the master configuration.

Note

If you have a WebSphere Cluster environment, then you should have created two JDBC Providers, one
for Scope=<Cluster>, and another one for Scope=<Service Link WebSphere Server>. If you just
completed the REQUESTCENTERDS data source for the JDBC Provider where Scope=<Cluster>, then
you must repeat the same procedure to create the REQUESTCENTERDS data source for the JDBC
Provider where Scope=<Service Link WebSphere Server>. This is because the Service Link application,
that is running on the stand-alone <Service Link WebSphere Server>, also needs a JDBC connection to
the RequestCenter database at runtime.

Starting WebSphere Server

You need to restart the WebSphere Server for it to pick up all of the configurations that you have done
in the previous sections.

Note

If you have a WebSphere Cluster environment, then you need to restart the Cluster as well as the “Service
Link WebSphere Server.”

After the WebSphere Server is restarted, verify that the Bus is running:

Step 1

Log on to the WebSphere Administration Console.

Step 2

Choose Service integration > Buses.

Step 3

Click nsbus to open its Configuration panel.

Step 4

Under the Topology section, click the Messaging engines link.

Step 5

Verify that the messaging engine has the status of “Started” (that is, a green arrow as shown in the
screenshot below).