Cisco Cisco Prime Service Catalog 10.0 Installation Guide
1-41
Cisco Prime Service Catalog Installation Guide
OL-31035-01
Chapter 1 Installation and Configuration Guide
Preinstallation Configuration for WebSphere
Note
If you have a WebSphere Cluster environment, then choose the Service Link WebSphere Server from the
Scope drop-down list instead. The Queues you are about to create only need to be visible to the
WebSphere Server where ISEE.war is deployed.
Scope drop-down list instead. The Queues you are about to create only need to be visible to the
WebSphere Server where ISEE.war is deployed.
Step 4
Click New.
Step 5
Choose the Default messaging provider option, then click OK. The New Queue panel appears.
Step 6
Modify only the following settings on the screen:
•
Name = ISEEInboundQueue
•
JNDI Name = ISEEInboundQueue
•
Bus name = nsbus
•
Queue name = ISEEInboundQueue
•
Delivery mode = Persistent
Step 7
Click OK.
Step 8
(Do not click Save yet.) Repeat Steps 4–7 four more times to create four more queues with the following
names:
names:
•
ISEEOutboundQueue
•
BEEERequisitionsQueue
•
BEEEAuthorizationsQueue
•
BEEEInboundQueue
Step 9
Click Save directly to the master configuration after you finish the fifth queue.
Configuring J2C Authentication Data
In the
, you created the RequestCenter database. In this
section, you will add the database user that owns the RequestCenter schema to the J2C Authentication
Data.
Data.
Step 1
On the WebSphere Administration Console, choose Security > Global security.
Step 2
Under the Authentication section in the right pane, click Java Authentication and Authorization
Service.
Service.
Step 3
Click J2C authentication data.
Step 4
Click New.
Step 5
Enter the following values on the screen (replace “RCUser” with the actual ID that you created as the
schema owner for the RequestCenter database):
schema owner for the RequestCenter database):
•
Alias = RCUser
•
User ID = RCUser
•
Password = <Enter the password for the database user RCUser.>
Step 6
Click OK.