preinstallation configuration for weblogic fileconfiguration for weblogic to prepare your weblogic...

Cisco Prime S

C H A P T E R 5
Installation on WebLogic Application Server
If you choose WebLogic as your application server, you need to install the Oracle WebLogic Application Server software as a prerequisite on your machine. This guide does not contain instructions for installing the WebLogic software. However you will need to follow the instructions in the Preinstallation Configuration for WebLogic to prepare your WebLogic Server for use with Service Catalog. Then after you execute the Cisco Prime Service Catalog installer, come back to the Postinstallation Configuration for WebLogic section of this chapter to complete the rest of the configuration steps.

Preinstallation Configuration for WebLogicThis section contains instructions for configuring the Oracle WebLogic Application Server, prior to installing Prime Service Catalog.

This release of Prime Service Catalog supports the WebLogic Application Server on the following operating systems and Java Development Kit:

Note Oracle JRockit is not supported. Oracle Java SE 8 (i.e. java version 1.8.0_x) is not supported.

It is assumed that you have already installed WebLogic Server 11g (10.3.6) software on one of the supported operating systems. You will follow instructions in this section to create and configure a new managed WebLogic Server, exclusively for the Cisco Prime Service Catalog application.

Table 5-1 Supported Operating Systems and Java

Oracle WebLogic Application Server Operating System Java

Version 11g (10.3.6) Red Hat Enterprise Linux Server 5.9 Oracle JDK 7 Update 55 (or higher Update)

Version 11g (10.3.6) Windows Server 2008 R2 (64-bit), with SP1

Oracle JDK 7 Update 55 (or higher Update)

5-1ervice Catalog 10.1 Installation and Upgrade Guide

Chapter 5 Installation on WebLogic Application ServerPreinstallation Configuration for WebLogic

WebLogic Installation FlowThe following figure illustrates steps to install Prime Service Catalog on Oracle WebLogic Application Server.

Figure 5-1 Installation Flow for Oracle WebLogic Application Server

Install Java

Download PrimeService CatalogSoftware Image

Configure OracleWebLogic Application Server

Executing PrimeService Catalog Installer

Post-installation configurationfor Oracle WebLogicApplication Server

ExtractWAR files

DeployRequestCenter.war

DeployISEE.war

Install customJava libraries

Create ManagedWebLogic Server

ConfigureJMS Server

Configure JDBCData Sources

RestartWebLogic Server

VerifyInstallation

ConfigureWeb Server

3642

05

5-2Cisco Prime Service Catalog 10.1 Installation and Upgrade Guide


Installing JavaAlthough the WebLogic software installation is bundled with some version of JRockit or Oracle Java, you will not use any bundled JRockit or Java. Instead, you need to download and install Oracle JDK 7. In the next section, you will configure your WebLogic Server to use this version of Oracle JDK 7.

Step 1 Access the Oracle JDK 7 download web site to download Oracle JDK 7.

Step 2 Download the correct version of Oracle JDK 7 for your OS platform. See Table 5-1 for the supported Update version of JDK 7.

Step 3 Install Oracle JDK 7 on the same machine where WebLogic software is installed.

Step 4 After Oracle JDK 7 is installed, navigate to the <WL_HOME>\common\bin directory.

Step 5 Modify the following file:

(For Windows) Modify commEnv.cmd as follows:

a. set JAVA_HOME=“<the installation directory for Oracle JDK 7>”

b. set JAVA_VENDOR=Sun

(For UNIX or Linux) Modify commEnv.sh as follows:

a. JAVA_HOME=“<the installation directory for Oracle JDK 7>”

b. JAVA_VENDOR=Sun

Step 6 Copy the unlimited strength JCE policy files to the $JAVA_HOME/jre/lib/security directory, overwriting the existing files. The unlimited strength policy files are "local_policy.jar" and "US_export_policy.jar", which can be downloaded from the following link:

http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html

Step 7 Restart all WebLogic servers, including the WebLogic Administration Server and Node Manager.

Note If you have a WebLogic Cluster environment, perform Steps 3–6 on every node in the Cluster.

Downloading Prime Service Catalog SoftwareYou must first download the Prime Service Catalog software prior to proceeding to the Installing Custom Java Libraries step. For details about the software image download, see Downloading Prime Service Catalog Software Image.

Installing Custom Java LibrariesIn this section, you will copy several Java library files from the <ServiceCatalog_Software_Dir> to the <WL_HOME> directory, and add these jar files to the class paths. Afterward, you need to restart the WebLogic servers in order to pick up the new Java libraries.

Step 1 Under the “<WL_HOME>” directory, create a subdirectory called “cisco”. And under "cisco", create two sub-directories called "endorsed" and "lib".


http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html


Step 2 Copy the following jar files from the “<ServiceCatalog_Software_Dir>\preinstall\weblogic\jre_lib_endorsed” directory to the “<WL_HOME>\cisco\endorsed” directory:

• serializer.jar

• xalan.jar

• xercesImpl.jar

• xml-apis.jar

Step 3 Copy the following jar files from the "<ServiceCatalog_Software_Dir>\preinstall\weblogic\cisco_lib" directory to the "<WL_HOME>\cisco\lib" directory:

• commons-lang-2.4.jar

• geronimo-ccpp_1.0_spec-1.0-beta.jar

• sqljdbc4.jar

• pluto-container-api-2.0.2.jar

• pluto-container-driver-api-2.0.2.jar

• pluto-taglib-2.0.2.jar

• portlet-api_2.0_spec-1.0.jar

• ojdbc7.jar

Step 4 Navigate to the “<WL_HOME>\common\bin” directory and modify the following file:

(For Windows) Modify commEnv.cmd as follows:

a. Search for the line that contains the parameter “set WEBLOGIC_CLASSPATH=”.

b. (If your database is SQL Server) Add the value %WL_HOME%\cisco\lib\commons-lang-2.4.jar;%WL_HOME%\cisco\lib\sqljdbc4.jar; to the beginning of the existing value. Do not forget to include the semicolon characters.

For example, after you modify the WEBLOGIC_CLASSPATH, it may look like this:set

WEBLOGIC_CLASSPATH=%WL_HOME%\cisco\lib\commons-lang-2.4.jar;%WL_HOME%\cisco\lib\sqljdb

c4.jar;%PATCH_CLASSPATH%;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.ja

r;%WL_HOME%\server\lib\weblogic.jar;%FEATURES_DIR%\weblogic.server.modules_10.3.0.0.ja

r;%WL_HOME%\server\lib\webservices.jar;%ANT_HOME%/lib/ant-all.jar;%ANT_CONTRIB%/

lib/antcontrib.jar

c. (If your database is Oracle) Add the value %WL_HOME%\cisco\lib\commons-lang-2.4.jar;%WL_HOME%\cisco\lib\ojdbc7.jar; to the beginning of the existing value. Do not forget to include the semicolon characters.

For example, after you modify the WEBLOGIC_CLASSPATH, it may look like this:

set WEBLOGIC_CLASSPATH=%WL_HOME%\cisco\lib\commons-lang-2.4.jar;%WL_HOME%\cisco\lib\ojdbc7.jar;%PATCH_CLASSPATH%;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%FEATURES_DIR%\weblogic.server.modules_10.3.0.0.jar;%WL_HOME%\server\lib\webservices.jar;%ANT_HOME%/lib/ant-all.jar;%ANT_CONTRIB%/lib/antcontrib.jar

(For Linux) Modify commEnv.sh as follows:

a. Search for the line that contains the parameter “WEBLOGIC_CLASSPATH=”.



b. (If your database is SQL Server) Add the value ${WL_HOME}/cisco/lib/commons-lang-2.4.jar${CLASSPATHSEP}${WL_HOME}/cisco/lib/sqljdbc4.jar${CLASSPATHSEP} to the beginning of the existing value.


WEBLOGIC_CLASSPATH="${WL_HOME}/cisco/lib/commons-lang-2.4.jar${CLASSPATHSEP}${WL_HOME}

/cisco/lib/sqljdbc4.jar${CLASSPATHSEP}${PATCH_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/li

b/tools.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}${WL_HOM

E}/server/lib/weblogic.jar${CLASSPATHSEP}${FEATURES_DIR}/weblogic.server.modules_10.3.

0.0.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${ANT_HOME}/

lib/ant-all.jar${CLASSPATHSEP}${ANT_CONTRIB}/lib/antcontrib.jar"

c. (If your database is Oracle) Add the value ${WL_HOME}/cisco/lib/commons-lang-2.4.jar${CLASSPATHSEP}${WL_HOME}/cisco/lib/ojdbc7.jar${CLASSPATHSEP} to the beginning of the existing value


WEBLOGIC_CLASSPATH="${WL_HOME}/cisco/lib/commons-lang-2.4.jar${CLASSPATHSEP}${WL_HOME}/cisco/lib/ojdbc7.jar${CLASSPATHSEP}${PATCH_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/lib/tools.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic.jar${CLASSPATHSEP}${FEATURES_DIR}/weblogic.server.modules_10.3.0.0.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${ANT_HOME}/lib/ant-all.jar${CLASSPATHSEP}${ANT_CONTRIB}/lib/antcontrib.jar"

Step 5 Restart the WebLogic Administration Server and WebLogic Node Manager. You must restart all WebLogic servers for them to pick up the custom Java libraries that you just installed.

Note If you have a WebLogic Cluster environment, perform Steps 1–5 on every node in the Cluster.

Note If you are upgrading from a previous release of Prime Service Catalog to this release, you must still repeat steps 1 to 5 in this section on your WebLogic environment. This is because:a) You have to overwrite the older version of the Cisco jar files with the newer version shipped with this release of Prime Service Catalog.b) There are new version of JDBC drivers (sqljdbc4.jar and ojdbc7.jar) that are bundled with this release of Prime Service Catalog.

Creating a Managed WebLogic ServerIn this section you will create a new managed WebLogic Server, to be used exclusively for Prime Service Catalog.

Step 1 Log on to the WebLogic Administration Console.

Step 2 If your WebLogic was installed in PRODUCTION mode, click Lock & Edit so that you can proceed to make changes. Otherwise, you can skip this step.

Step 3 Choose Environment > Servers.

Step 4 Click New. The “Create a New Server” panel appears.



Figure 5-2 Create New WebLogic Server

Step 5 Enter a Server Name (for example, “server1”). Enter a port number different from 7001 (for example, 8001), because port 7001 is most likely already used by the WebLogic Administration Server. Choose the No, this is a stand-alone server option.

Step 6 Click Finish. Your newly created WebLogic Server appears on the list.

Step 7 Click the newly created Server “server1” to open its properties.

Step 8 Choose Configuration > General.



Figure 5-3 Configuration – General Settings

Step 9 In the Machine drop-down list, select a machine (i.e. Node Manager machine) where the WebLogic server will run, and click Save.

Step 10 Choose Configuration > Keystores.

Step 11 Click the Change button next to the Keystores field. Select Custom Identity and Java Standard Trust from the drop-down list. Click Save.



Setting the Arguments for Java Virtual Machine

Perform the following steps to set the arguments for Java Virtual Machine:

Step 1 Choose Configuration > Server Start.

Step 2 Enter values for the following parameters:

• Arguments = ‐server ‐Xms2048m ‐Xmx2048m ‐XX:PermSize=256m

-XX:MaxPermSize=256m -XX:NewRatio=2

-XX:ReservedCodeCacheSize=256m

-XX:+TieredCompilation

-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<WL_HOME>/cisco

-Dweblogic.ext.dirs=<WL_HOME>/cisco/lib -Djava.endorsed.dirs=<WL_HOME>/cisco/endorsed

-XX:CompileCommand=exclude,com/newscale/bfw/signon/filters/AuthenticationFilter,doFilter

-XX:CompileCommand=exclude,org/apache/xml/dtm/ref/sax2dtm/SAX2DTM,startElement

-XX:CompileCommand=exclude,org/exolab/castor/xml/Marshaller,marshal

-XX:CompileCommand=exclude,org/apache/xpath/compiler/XPathParser,UnionExpr

-XX:CompileCommand=exclude,org/apache/oro/text/regex/Perl5Compiler,__parseAtom

(where <WL_HOME>/cisco/lib and <WL_HOME>/cisco/endorsed are the directories described in the Installing Custom Java Libraries).

• User Name = weblogic

• Password = <the password for the “weblogic” username>

• Confirm Password = <re-enter the password for the “weblogic” username>

Step 3 Click Save.

Step 4 If your WebLogic was installed in PRODUCTION mode, click Activate Changes. Otherwise, you can skip this step.

Step 5 Open the Control tab.

Figure 5-4 Start WebLogic Server

Step 6 Choose the WebLogic Server named “server1”, then click Start. Wait until you see State=RUNNING.



Your new WebLogic Server has now been configured to use Oracle JDK 7 and the Cisco Java libraries that you installed in this section.

WebLogic Cluster Configuration

The Prime Service Catalog product is comprised of two component applications named “Service Catalog” and “Service Link”. However, the Prime Service Catalog installer does not automatically deploy the Service Catalog and Service Link applications on your WebLogic Server for you. The installer will generate two WAR files (RequestCenter.war for the Service Catalog component application, and ISEE.war for the Service Link component application) which are customized for your WebLogic environment. After you execute the Prime Service Catalog installer, you will need to follow the instructions in a later section of this chapter to manually deploy RequestCenter.war and ISEE.war on your WebLogic Server.

The RequestCenter.war file and ISEE.war file can be deployed together in the same WebLogic Server even though they are two separate component applications. However, if you are setting up a WebLogic Cluster environment with multiple nodes (where each node is a separate computer), you need to perform the additional configurations as follows:

Step 1 Perform the tasks described in the Installing Java and Installing Custom Java Libraries on each node (that is, each computer) in the Cluster.

Step 2 Follow the instructions in the Creating a Managed WebLogic Server to create the WebLogic Server for each node and to set the JVM arguments for each server, before you add these servers to the Cluster.

Step 3 Each WebLogic Server in your Cluster must be configured to use the same port number. For example, your Cluster contains two nodes. If the WebLogic Server on Node 1 is running on port 8001, then the WebLogic Server on Node 2 must also be configured to run on port 8001.

Step 4 RequestCenter.war file is deployed on the WebLogic Cluster. But, the ISEE.war file cannot be deployed in the same Cluster; it must be deployed on a stand-alone WebLogic Server that is not a member of any Cluster. Therefore, if you have a clustered WebLogic environment, then you must create an additional stand-alone WebLogic Server (that is, not a member of the Cluster), to be used for ISEE.war. For the rest of the chapter, this stand-alone WebLogic Server is referred to as the “Service Link WebLogic Server”. For this stand-alone “Service Link WebLogic Server”, the JVM arguments can be set as follows:

Arguments = -server -Xms2048m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:NewRatio=2 -XX:ReservedCodeCacheSize=256m -XX:+TieredCompilation -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<WL_HOME>/cisco -Dweblogic.ext.dirs=<WL_HOME>/cisco/lib-Djava.endorsed.dirs=<WL_HOME>/cisco/endorsed

(where <WL_HOME>/cisco/lib and <WL_HOME>/cisco/endorsed

are the directories described in the Installing Custom Java Libraries).

Step 5 If the stand-alone “Service Link WebLogic Server” resides on another machine, then make sure that you also performed the tasks described in the Installing Java and Installing Custom Java Libraries on that WebLogic machine. If the stand-alone "Service Link WebLogic Server" resides on the same machine as one of the Cluster nodes, then make sure that it is configured with a port number that is different from the port number used by the Cluster.



Configuring JMS ServerIn this section, you will configure a JMS Server and JMS Queues that will be used by Prime Service Catalog.

Note If RequestCenter.war and ISEE.war are deployed together on the same nonclustered WebLogic Server, then the JMS configurations described in this section are performed for that WebLogic Server. However, if you have a WebLogic Cluster environment, then the JMS configurations are performed for the “Service Link WebLogic Server”.

Creating a Persistent Store

Perform the following steps to create a persistent store:

Step 1 On your computer, cd to <WL_HOME>.

Step 2 Create a subdirectory called CiscoFileStore.


Step 4 If your WebLogic was installed in PRODUCTION mode, click Lock & Edit. Otherwise, you can skip this step.

Step 5 Choose Services > Persistent Stores.

Step 6 Choose New > Create FileStore. The “Create a New File Store” panel appears.

Step 7 In the Name field, enter CiscoFileStore.

Step 8 In the Target drop-down list, choose your WebLogic Server.

Step 9 In the Directory text box, enter the full path of the CiscoFileStore directory you created in Step 2 above (for example, /opt/Oracle/Middleware/wlserver_10.3/CiscoFileStore).

Step 10 Click OK.

Creating a JMS Server

Perform the following steps to create JMS server:

Step 1 On the WebLogic Administration Console, choose Services > Messaging > JMS Modules.

Step 2 Click New. The “Create a New JMS Server” panel appears.

Step 3 In the Name field, enter CiscoJMSServer.

Step 4 In the Persistent Store drop-down list, choose the Persistent Store named CiscoFileStore.

Step 5 Click Next.

Step 6 In the Target drop-down list, choose your WebLogic Server. (If you have a WebLogic Cluster environment, click Service Link WebLogic Server.)

Step 7 Click Finish.



Creating a JMS Module

Perform the following steps to create a JMS module:


Step 2 Click New. The Create JMS System Module panel appears.

Step 3 In the Name field, enter CiscoJMSModule. and click Next.

Step 4 Choose your WebLogic Server as the target. (If you have a WebLogic Cluster environment, choose Service Link WebLogic Server.) and click Next.


Step 6 Click the newly created JMS Module named CiscoJMSModule to open its properties.

Step 7 Open the Subdeployments tab and click New.

Step 8 In the Subdeployment Name field, enter CiscoSubdeployment and click Next.

Step 9 Choose the JMS Server named CiscoJMSServer. and click Finish.

Creating Connection Factory

Perform the following steps to create a connection factory:


Step 2 Click the JMS Module named CiscoJMSModule to open its properties.

Step 3 Open the Configuration tab and click New.

Step 4 Choose the Connection Factory option and click Next.

Step 5 In the Name and JNDI Name fields, enter NSConnectionFactory and click Next.

Step 6 Click Advanced Targeting.

Step 7 In the Subdeployments drop-down list, choose CiscoSubdeployment. The screen is refreshed to show that the JMS Server named “CiscoJMSServer” is already selected.


Creating JMS Templates

Perform the following steps to create JMS templates:




Step 4 Choose the JMS Template option and click Next.



Step 5 In the Name field, enter CiscoQueueTemplate and click OK.

Creating Queues

Perform the following steps to create queues:




Step 4 Choose the Queue option.

Step 5 Click Next.

Step 6 In the Name and JNDI Name fields, enter ISEEInboundQueue.

Step 7 In the Template drop-down list, choose the CiscoQueueTemplate that you created and click Next.

Step 8 In the Subdeployments drop-down list, choose CiscoSubdeployment. The screen is refreshed to show that the JMS Server named “CiscoJMSServer” is already selected.


Step 10 Repeat the above steps four more times to create four more JMS Queues with the following names:


Configuring JDBC Data SourcesIn this section, you will configure a JDBC Data Source to point to the ServiceCatalog database that you created in the Configuring the Service Catalog Database.

Use the worksheet that you filled out at the end of the Configuring the Service Catalog Database to retrieve the necessary database information.


Step 2 If your WebLogic was installed in PRODUCTION mode, click Lock & Edit. Otherwise, you can skip this step.

Step 3 Choose Services > Data Sources.

Step 4 Choose New > Generic Data Source.

Name & JNDI Name Template Subdeployments

ISEEOutboundQueue CiscoQueueTemplate CiscoSubdeployment

BEEERequisitionsQueue CiscoQueueTemplate CiscoSubdeployment

BEEEAuthorizationsQueue CiscoQueueTemplate CiscoSubdeployment

BEEEInboundQueue CiscoQueueTemplate CiscoSubdeployment



Update the information for this panel as provided in Table 5-2 and click Next.

Step 5 On the next panel, select one of the following values from the Database Driver drop-down list, then click Next:

– Select "Microsoft's MS SQL Server Driver (Type 4) Version:2005 and later" if your database is MS SQL Server.

– Select "Oracle's Driver (Thin) for Instance connections; Version:9.0.1 and later" if your database is Oracle, using SID to connect.

– Select "Oracle's Driver (Thin) for Service connections; Version:9.0.1 and later" if your database is Oracle, using Service Name to connect.

Step 6 On the next panel, select the "Support Global Transactions" option and the "One-Phase Commit" option, then click Next.

Step 7 Update the information for this panel as provided in Table 5-3 and click Next.

Step 8 Update the information for this panel as provided in Table 5-4 and click Next.

Table 5-2

Field Value

Name SERVICECATALOGDS

JNDI Name field eis/SERVICECATALOGDS

Database Type drop-down list • (For SQL Server), choose MS SQL Server

• (For Oracle), choose Oracle

Table 5-3

Field Definition

Database Name • (For SQL Server), enter the name of the database, for example, "ServiceCatalog".

• (For Oracle), enter the SID if you are using SID to connect to your Oracle database, or the Service Name if you are using Service Name to connect to your Oracle database.

Host Name Enter the database server name or IP address

Port Enter the database port number

Database User Name Enter the name of the db_owner (or schema user) of the ServiceCatalog database (for example, enter CPSCUser).

Password Enter the password for the Database User Name

Confirm Password Re-enter the password for the Database User Name



Caution Do not click the Test Configuration button.

Step 9 Choose your WebLogic Server as the Target.

Table 5-4

Field Definition

Driver Class Name Enter the value (one string)

For SQL Server: “com.microsoft.sqlserver.jdbc.SQLServerDriver”

For Oracle: “oracle.jdbc.OracleDriver”

URL Enter the following value (one string):

For SQL Server:

jdbc:sqlserver://<db_server>:<db_port>;databaseName=<db_name>

(For example, jdbc:sqlserver://mysqlserver.cisco.com:1433;databaseName=ServiceCatalog)

For Oracle SID:

jdbc:oracle:thin:@<db_server>:<db_port>:<SID>

(For example, jdbc:oracle:thin:@myoracle.cisco.com:1521:PROD)

For Oracle Service Name:

jdbc:oracle:thin:@//<db_server>:<db_port>/<service_name>

(For example, jdbc:oracle:thin:@//myoracle.cisco.com:1521/PRODSN)

Database User Name Enter the name of the db_owner (or schema user) of the ServiceCatalog database (for example, enter CPSCUser).

Password Enter the password for the Database User Name.

Confirm Password Re-enter the password for the Database User Name.

Properties For SQL Server, enter the following lines:

userName=<Database User Name>

selectMethod=direct

For Oracle, enter the following line:

user=<Database User Name>

Test Table Name For SQL Server, enter the following value:

SQL SELECT 1

For Oracle, enter the following value:

SQL SELECT 1 FROM DUAL



Note If you have a WebLogic Cluster environment, then choose both the Cluster name and the “Service Link WebLogic Server” as the Targets for this data source.


The newly created data source named “SERVICECATALOGDS” should appear on the Summary of JDBC Data Sources panel.Verify that the JNDI Name and Target information for this data source is correct.

Step 11 Click SERVICECATALOGDS to open its properties.

Step 12 Choose Configuration > Connection Pool.

Step 13 Change the values for the following parameters on the screen:

• Initial Capacity = 20

• Maximum Capacity = 80

• Minimum Capacity = 20

Step 14 Click Save.

Step 15 In Connection Pool tab, at the bottom of the panel, choose Advanced.

Figure 5-5 Connection Pool – Advanced Settings

Step 16 Click the Test Connections On Reserve option.

Step 17 In the Test Table Name field, enter the following value, then click Save:

For SQL Server:

SQL SELECT 1

For Oracle:

SQL SELECT 1 FROM DUAL




Restarting WebLogic ServerYou must restart your WebLogic Server in order for it to pick up the new JMS and Data Sources configurations.

Step 1 Restart your WebLogic Server.

Note If you have WebLogic Cluster environment, restart all the WebLogic servers in the Cluster as well as the “Service Link WebLogic Server”.

Step 2 Once the WebLogic Server is started successfully, navigate to its Configuration > General tab.

Figure 5-6 JNDI Tree

Step 3 Click the link called View JNDI Tree right above the Name field. The JNDI Viewer window appears.

Step 4 In the JNDI Tree Structure on the left hand side, look for the following entries:

eis> SERVICECATALOGDS

BEEEAuthorizationsQueue

BEEEInboundQueue

BEEERequisitionsQueue

ISEEInboundQueue

ISEEOutboundQueue

NSConnectionFactory

Step 5 If you have a clustered WebLogic environment, then the JNDI Tree for your WebLogic Cluster should contain only the following entry:


And the JNDI Tree for the “Service Link WebLogic Server” should contain the following entries:


BEEEAuthorizationsQueue


Chapter 5 Installation on WebLogic Application ServerExecuting Prime Service Catalog Installer

BEEEInboundQueue

BEEERequisitionsQueue

ISEEInboundQueue

ISEEOutboundQueue

NSConnectionFactory

Complete the WebLogic Application Server Information Worksheet, by entering your configuration values in the Value column. The information in that worksheet will be needed when you run the Prime Service Catalog Installation Wizard.

Executing Prime Service Catalog InstallerYour WebLogic environment is prepared. You can proceed to the Installing Prime Service Catalog chapter, and follow the instructions to execute the Prime Service Catalog installer. After you finish executing the Prime Service Catalog installer successfully, come back to this chapter and follow the instructions in the next section "Postinstallation Configuration for WebLogic" to complete the rest of the configuration steps.

Postinstallation Configuration for WebLogicWhen the Prime Service Catalog installation wizard completes, it creates the following WAR files underneath the “<ServiceCatalog_Install_Dir>\dist” directory:

• RequestCenter.war

• ISEE.war

The Prime Service Catalog installation wizard did not automatically deploy these WAR files on your WebLogic Server. You need to follow the instructions in this section to manually deploy these WAR files. See the WebLogic Application Server Information Worksheet that you filled out in Appendix A to get the parameter values needed during the deployment.

Extracting WAR FilesYou must deploy RequestCenter.war and ISEE.war in extracted format. To extract the WAR files:

Step 1 Create a subdirectory called applications underneath the “<ORACLE_HOME>\ user_projects\domain\<your_domain>” directory, if it does not already exist. Note that you perform this task on the computer where the WebLogic Administration Server is running.

Step 2 Create two subdirectories underneath “applications” as follows:

• RequestCenter

• ServiceLink


Chapter 5 Installation on WebLogic Application ServerPostinstallation Configuration for WebLogic

Step 3 Extract the WAR files (generated by the Prime Service Catalog installation wizard) into the new directories that you just created:

a. Unzip file “<ServiceCatalog_Install_Dir>\dist\RequestCenter.war” into the “<ORACLE_HOME>\user_projects\domain\<your_domain>\applications\RequestCenter” directory.

b. Unzip file “<ServiceCatalog_Install_Dir>\dist\ISEE.war” into the “<ORACLE_HOME>\user_projects\domain\<your_domain>\applications\ServiceLink” directory.

Note If the RequestCenter or ServiceLink subdirectory under the “<ORACLE_HOME>\user_projects\domain\<your_domain>\applications” directory is not empty, you must first empty the entire directory before extracting the contents of the new RequestCenter.war or ISEE.war file into it. This is because the unzip utility may only overwrite files with the same names. There may be some “remnants” of old files in your destination directory that may be inadvertently deployed.

Deploying RequestCenter.warPerform the following steps to deploy RequestCenter.war file:


Step 2 Start your WebLogic Server (or WebLogic Cluster) if it is not already running.

Step 3 If WebLogic was installed in PRODUCTION mode, click Lock & Edit so that you can proceed to make changes. Otherwise, you can skip this step.

Step 4 In the left pane, click Deployments.

Step 5 Click Install.

Step 6 Browse to (or enter the full pathname of) the directory “<ORACLE_HOME>\user_projects\domain\<your_domain>\applications.”You should see the two subdirectories called “RequestCenter” and “ServiceLink”.

Step 7 Click the radio button for RequestCenter, then click Next.

Step 8 Choose the Install this deployment as an application option, then click Next.

Step 9 Choose your WebLogic Server (or WebLogic Cluster) as the Target, then click Next.

Step 10 Enter RequestCenter in the Name field. Select the Copy this application onto every target for me option. Click Next.

Step 11 Choose the No, I will review the configuration later option, then click Finish. The progress indicator begins. This may take several minutes to complete.

Step 12 Wait until the screen is refreshed to show that the “RequestCenter” application has State=Active and Health=OK. If your WebLogic Application Server was installed in PRODUCTION mode, then the State may be set to “Prepared” until you click Activate Changes.



Deploying ISEE.warPerform the following steps to deploy ISEE.war file:


Step 2 Start your WebLogic Server if it is not already running (if you have a WebLogic Cluster environment, then start the “Service Link WebLogic Server”. The Service Link application cannot be deployed on a Cluster).

Step 3 If your WebLogic was installed in PRODUCTION mode, click Lock & Edit so that you can proceed to make changes. Otherwise, you can skip this step.

Step 4 In the left pane, click Deployments.

Step 5 Click Install.

Step 6 Browse to (or enter the full pathname of) the directory “<ORACLE_HOME>\user_projects\domain\<your_domain>\applications.” You should see the two subdirectories called “RequestCenter” and “ServiceLink”.

Step 7 Click the radio button for ServiceLink, then click Next.

Step 8 Choose the Install this deployment as an application option, then click Next.

Step 9 Choose your WebLogic Server as the Target. (If you have a WebLogic Cluster, choose the stand-alone “Service Link WebLogic Server” as the Target.) Then click Next.

Step 10 Enter ServiceLink in the Name field. Select the Copy this application onto every target for me option. Click Next.

Step 11 Choose the No, I will review the configuration later option, then click Finish. The progress indicator begins. This may take several minutes to complete.

Step 12 Wait until the screen is refreshed to show that the “ServiceLink” application has State=Active and Health=OK. If your WebLogic Application Server was installed in PRODUCTION mode, then the State may be set to “Prepared” until you click Activate Changes.

Verifying Your InstallationPerform the following steps to verify your installation:

Step 1 Test your installation by opening a new browser window and connect to the following URL:

http://<AppServer_Host>:<Port>/RequestCenter

where <AppServer_Host> = the host name of your WebLogic Server, and <Port> = the port number used by your WebLogic Server.

For example,

http://m1.cisco.com:8001/RequestCenter

Step 2 Log in as the Site Administrator. For a new installation of Service Catalog, the username for the Site Administrator is "admin" and the password is the value you entered on the Service Catalog Administration Configuration panel of the installation wizard.

Step 3 Navigate to the Service Link Module.



Step 4 On the left hand side of the panel, under Service Link Status, verify that the connection has a green status.

You have completed the installation for Cisco Prime Service Catalog on WebLogic.

Configuring Web ServerAt this time, you should configure the plugin for your Web Server to point to your WebLogic Server (or your WebLogic Cluster). The following Web Servers are supported with WebLogic Server:

• Apache 2.4.7

• Apache 2.2.15

• IIS 7.5

This chapter does not contain instructions on how to configure your Web Server Plugin. Any plugin configurations between your Web Server and WebLogic are not handled by the Prime Service Catalog installer program. There is no Cisco library or binary that needs to be installed or configured on your Web Server installation. You should follow instructions provided by either Oracle (for WebLogic Plugin) or by the vendor of your web server.

This section contains only examples of the settings that you may want to add to your web server configuration file.

The following are examples for the settings for Apache 2.4.7 Web Server. Add the following entries to the end of file httpd.conf:

LoadModule weblogic_module modules/mod_wl_24.so

<IfModule mod_weblogic.c>WebLogicHost m1.mydomain.comWebLogicPort 8001</IfModule>

<Location /RequestCenter>SetHandler weblogic-handlerPathTrim /</Location>

The following are examples for the settings for IIS 7.5 Web Server. Add the following entries to file iisproxy.ini:

WebLogicHost=m1.mydomain.comWebLogicPort=8001ConnectTimeoutSecs=20ConnectRetrySecs=5KeepAliveEnabled=trueKeepAliveSecs=20WlForwardPath=/RequestCenter



After you complete the Plugin configuration, you need to restart both the Web Server and the WebLogic Application Server.

Repeat the steps described in the Verifying Your Installation to verify that your Web Server plugin is configured correctly to point to your WebLogic Server. However, this time connect to the following URL

http://<WebServer_Host>:<WebServer_Port>/RequestCenter

where <WebServer_Host> = the host name of your Web Server, and <WebServer_Port> = the port number used by your Web Server (omit the port number if it is set to 80).

For example,

http://webserver.cisco.com/RequestCenter


preinstallation configuration for weblogic fileconfiguration for weblogic to prepare your weblogic...

Documents