Cisco Prime Service Catalog 12.1 Installation Guide

Add Web Server Role for IIS

Step 1 Navigate to Service Manager Dashboard > Manage Tab > Add Roles and Features.

Step 2 Add the role Web Server (IIS) on your Windows Server 2012 R2 operating system.
Make sure you select the ISAPI Extensions and ISAPI Filters role services when adding IIS.

Step 3 After adding the Web Server (IIS) Role, start the World Wide Web Publishing Service.

Step 4 Launch a browser and connect to URL = http://localhost.
You should see the Welcome IIS 8.x page.

Install Tomcat Plugin

Step 1 Download the PSC 11.x software package from cisco.com and extract it.

Step 2 Cd to <PSC_Software_Extract_Dir>\isapi directory.

Step 3 Copy file tomcat-isapi-redirector-v1.2.37.zip to your IIS web server machine and extract it under the C:\inetpub\isapi directory.

Note Create the isapi sub-directory under C:\inetpub first if necessary.

Step 4 Cd to C:\inetpub\isapi and rename the file isapi_redirect-1.2.37-win64.dll to isapi_redirect.dll.

Copy WAR Directories

If you have WildFly installation and your IIS is on a separate machine from WildFly, then perform the following steps to copy WAR directories:

Standalone WildFly Installation

Step 1 On the WildFly machine where the RequestCenter Server is running, cd to the <PSC_Install_Dir>\wildfly-10.1.0.Final\ServiceCatalogServer\deployments directory.

Step 2 Copy the entire RequestCenter.war sub-directory from this machine to the IIS machine and place it under the C:\inetpub\WAR\ directory.

Step 3 On the WildFly machine where the ServiceLink server is running, cd to the <PSC_Install_Dir>\wildfly-10.1.0.Final\ServiceLinkServer\deployments directory.

Step 4 Copy the entire ServiceLink.war sub-directory from this machine to the IIS machine and place it under the C:\inetpub\WAR\ directory.

Clustered WildFly installation with Four VM Topology

Step 1 On the WildFly machine where one of the cluster nodes for RequestCenter is running, cd to the <PSC_Install_Dir>\wildfly-10.1.0.Final\content directory.

Step 2 Copy the entire RequestCenter.war sub-directory from this machine to the IIS machine and place it under the C:\inetpub\WAR\ directory.

Step 3 On the WildFly machine where the ServiceLink server is running, cd to the <PSC_Install_Dir>\wildfly-10.1.0.Final\ServiceLinkServer\deployments directory.

Step 4 Copy the entire ServiceLink.war sub-directory from this machine to the IIS machine and place it under the C:\inetpub\WAR\ directory.

Clustered Wildfly installation with Two VM Topology

Step 1 On the WildFly machine that is the primary cluster node for RequestCenter, cd to the <PSC_Install_Dir>\wildfly-10.1.0.Final\content directory.

Step 2 Copy the entire RequestCenter.war sub-directory from this machine to the IIS machine, and place it under the C:\inetpub\WAR\ directory.

Step 3 On the same WildFly machine, cd to the <PSC_Install_Dir>\wildfly-10.1.0.Final\content directory.

Step 4 Copy the entire ISEE.war sub-directory from this machine to the IIS machine and place it under the C:\inetpub\WAR directory.

Step 5 Rename the folder to C:\inetpub\WAR\ServiceLink.war.

Create Virtual Directories for IIS

Step 1 On the IIS machine, launch Internet Information Services (IIS) Manager.

Step 2 Choose Hostname > Sites > Default Web Site.

Step 3 Right click on the Default Web Site and select Add Virtual Directory.

Step 4 On the pop up window, enter the following values, and then click OK:

Step 5 Right click on Default Web Site and select Add Virtual Directory to add another directory.

Step 6 On the pop up window, enter the following values, and then click OK:

Step 7 Right click on Default Web Site and select Add Virtual Directory to add another directory.

Step 8 On the display window, enter the following values, and then click OK:

Step 9 Click on Default Web Site node. And on the right pane, double click ISAPI Filters.

Step 10 Click Add link under the Actions column on the right pane.

Step 11 On the pop up window, enter the following values, and then click OK:

Step 12 Click on Default Web Site node. And on the right panel, double click Handler Mappings.

Step 13 Click the Edit Feature Permissions link under the Actions column on the right pane.

Step 14 On the pop up window, select all Read, Script and Execute check boxes, and then click OK.

Step 15 Click on the Hostname node. On the right panel, double click on ISAPI and CGI Restrictions.

Note The Hostname node is the parent node of sites.

Step 16 Click the Add link under the Actions column on the right most pane.

Step 17 On the display window, enter the following values, and then click OK:

Modify Plugin Properties

Step 1 Modify the file C:\inetpub\isapi\isapi_redirect.properties as follows:

Step 2 Modify the file C:\inetpub\isapi\conf\uriworkermap.properties as follows:

Step 3 If you have a standalone WildFly installation, then modify the file C:\inetpub\isapi\conf \workers.properties as follows:

The port numbers 8009 and 6009 should be set to the actual ajp port numbers used by the RequestCenter server and ServiceLink server.

Step 4 If you have a clustered WildFly installation (regardless of 4-VM Topology or 2-VM Topology), then modify the file C:\inetpub\isapi\conf\workers.properties as follows:

Note The following is an example for a WildFly installation with 2 cluster nodes of RequestCenter.

• That is there are 2 RequestCenter servers running on two separate VM’s.
• If you have 3 or 4 cluster nodes, you just need to follow this example and add a section for rcnode3 and for rcnode4 appropriately.

Step 5 Restart World Wide Web Publishing Service.

Step 6 If you have a standalone WildFly installation, skip to the section Test IIS.

Note If you have clustered Wildfly installation, continue to the next section Configure instance-id for Wildfly.

Configure Instance-ID for WildFly

For 4 VM Topology

You must perform the following steps for clustered WildFly installation with 4 VM topology:

Step 1 Log on to the WildFly Domain Controller machine, and stop all WildFly servers.

Step 2 Open file <PSC_Install_Dir>\wildfly-10.1.0.Final\domain\configuration\domain.xml and search for the following line:

Replace it with the following value at two places within domain.xml:

Step 3 Log on to the Host Controller 1 for RequestCenter, and stop all WildFly servers.

Step 4 Open file <PSC_Install_Dir>\wildfly-10.1.0.Final\domain\configuration\host1_backup.xml, and search for the following section:

Replace it with the following:

Step 5 Log on to the Host Controller 2 for RequestCenter, and stop all Wildfly servers.

Step 6 Open file <PSC_Install_Dir>\wildfly-10.1.0.Final\domain\configuration\host2_backup.xml, and search for the following section:

Replace it with the following:

Note If you have more than 2 cluster nodes, then repeat Step 5 and Step 6 for each subsequent node. For example,

• On the 3rd node, you need to modify the file host3_backup.xml and add the system-properties for rcnode3.
• On the 4th node, you need to modify the file host4_backup.xml and add the system-properties for rcnode4.

Step 7 Start up Wildfly servers on the Domain Controller machine and on each Host Controller machine.

Step 8 Go to the section Test IIS.

For 2 VM Topology

Perform the steps in this section only if you have a clustered WildFly installation with 2 VM topology:

Step 1 Log on to the WildFly Domain Controller machine, and stop all WildFly servers.

Step 2 Open file <PSC_Install_Dir>\wildfly-10.1.0.Final\domain\configuration\domain.xml and search for the following line:

Replace it with the following value at two places within domain.xml:

Step 3 Open file <PSC_Install_Dir>\wildfly-10.1.0.Final\domain\configuration \hostva_ backup.xml, and search for the following section:

Replace it with the following:

Step 4 Log on to the Host Controller 2 for RequestCenter, and stop all WildFly servers.

Step 5 Open file <PSC_Install_Dir>\wildfly-10.1.0.Final\domain\configuration\host2_backup.xml, and search for the following section:

Replace it with the following:

Note If you have more than 2 cluster nodes, then repeat Step 4 and Step 5 for each subsequent node. For example,

• On the 3rd node, you need to modify the file host3_backup.xml and add the system-properties for rcnode3.
• On the 4th node, you need to modify file host4_backup.xml and add the system-properties for rcnode4.

Step 6 Start up WildFly servers on the Domain Controller machine and on the Host Controller 2 machine.

Step 7 Go to the section Test IIS.

Test IIS

The following section provides information on verifying the connection to Prime Service Catalog.

Step 1 Verify by connecting to the URL http://<IP_Address_of_IIS_Host>/RequestCenter.
If you connected you can see the Login Page of Prime Service Catalog.

Step 2 For clustered WildFly installation with 2 nodes, stop one of the nodes.
And verify that you can still connect to the URL http://<IP_Address_of_IIS_Host>/RequestCenter.