Cisco Cisco Prime Service Catalog 10.0 Guía De Instalación

The "Create Database" feature creates a very basic RequestCenter database that meets the 
minimum requirements for the Service Catalog application to operate. This feature is 
recommended for a Demo or Test system. For a Production system, contact your DBA in 
advance, to create the RequestCenter database which meets all of the product requirements as 
described in the Configuring Databases section, as well as any performance, reliability, and 
security requirements that adhere to your corporate policy.

Click Next to continue.  The installer connects to the database to validate the required settings for the 
database.  If the installer created the database for you, then it would meet all of the required settings, and 
the validation test would pass. If you provided the information for an existing database, then the installer 
may report a validation error if any database setting is missing. (Refer to the 

 section 

in this chapter for the database requirements.) If a database validation error occurs, you can do the 
following:

Close the error dialog and click Cancel to exit the installation wizard, or

Fix the missing database setting on a separate database connection session.  Then come back to this 
screen, close the error dialog, and click Next again.  At this point, the installer will repeat the 
validation test, and if the test passes, it will let you move to the next panel.

If you selected JBoss as the application server, the installation procedure is as follows:

The Choose Java Virtual Machine panel is displayed. This panel displays all the available java 
executable programs on the computer. Select a Java version 1.6.0_x from the list or click the Search 
Another Location button to navigate to the correct location of Java 1.6.0_x on your computer and 
click Next.

You must specify the location of Java for JBoss because the installer will install the JBoss 
Application Server software on your computer, and it will set the JAVA_HOME variable in 
the JBoss configuration to use this particular Java.

On the Request Center Configuration panel, enter the information for the JBoss server where the 
Request Center application (i.e. RequestCenter.war) will be deployed. Refer to the 

 for the description of each field on this panel. Click Next.

On the Service Link Configuration panel, enter the information for the JBoss server where Service 
Link application (i.e. ISEE.war) will be deployed. Refer to the 

 for the description of each field on this panel. Click Next.

For WebSphere or WebLogic, you will not see this panel.  This is because for a Typical 
installation mode for WebSphere or WebLogic, the Request Center application (i.e. 
RequestCenter.war) and Service Link application (i.e. ISEE.war) will be deployed together 
in the same WebSphere or WebLogic server.  Thus, there is no need for the installer to 
prompt for the information of the Service Link server.  However, for a Typical installation 
mode for JBoss, the installer will always create two separate JBoss servers, one for Request 
Center application and one for Service Link application, even though both JBoss servers are 
running on the same machine.

On the Messaging Configuration panel, enter the information for the JMS Queue connection 
Factory, user name and password. Refer to the 

 for the description of 

each field on this panel. Click Next