The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Standalone WildFly deployment includes a ServiceCatalogServer and ServiceLinkServer that can be installed on the same application server or on different servers.
Following are the start and stop scripts available in the installer for Standalone WildFly deployments.
Cluster setup for WildFly can be configured in two VM or four VM topology.
1. Run the GUI Installer for the host controller setup on the subsequent node, vm<N>, where N is the number of the node.
2. Select the Host Controller in the Node Type Selection panel followed by Host1 as the cluster node.
3. Do not run any of the startup-scripts.
Step 1 Rename host1.xml to host<N>.xml. The file, host1.xml is present under the InstallationDirectory/wildfly-8.2.0.Final/domain/configuration directory .
Step 2 Follow the below steps to create a new user:
a. Execute add-user.sh or add-user.bat script from InstallationDirectory/wildfly-8.2.0.Final/bin location.
b. Enter a to select the Management User.
c. Provide HOST<N> as the Username.
d. Provide HOST<N> as the Password.
e. Enter yes to use the entered password.
f. Re-Enter HOST<N> for Password confirmation.
g. Press Enter to pass the management group information
h. Enter yes to add the user 'HOST<N>' for realm 'ManagementRealm'.
i. Enter no for the interconnection of AS process.
Note • The new user needs to be created in the machine having host Controller(host<N>) and domain controller (host1) as well.
Step 3 Perform the following changes in host<N>.xml:
a. Change the name of Host from HOST1 to HOST<N>.location for host<N>.xml. This file is available in the C:\Installation_directory\wildfly-8.2.0.Final\domain\configuration
b. Change the secret value in the <server-identities> section. The secret value can be obtained from the website www.motobit.com :
Enter the URL http://www.motobit.com/util/base64-decoder-encoder.asp
•Enter HOST<N> in the text box (without any extra space or newline).
•Click on Convert the Source Data button.
c. Change the name of the server instance from server-host1-RC to server-host<N>-RC to avoid name conflicts:
d. Change the CONTROLLER_TYPE from host1 to host<N> in setEnv.cmd script in InstallationDirectory/bin directory .
e. Delete the logs and servers directories from InstallationDirectory/wildfly-8.2.0.Final/domain , if exists.
Step 4 The following changes need to be done in startServiceCatalogCluster.cmd script in InstallationDirectory/bin directory .
a. Add the following code snippet in BOLD in the script file:
b. Add the following code snippet in BOLD in the script file:
Step 5 Start the server with startServiceCatalogCluster.cmd or sh and once it is up, verify from the Wildfly admin server console under the domain whether the host<N> is registered.
Step 6 Addition of scripts for both 4-VM Cluster and 2-VM Cluster in the VM-1 machine (machine containing the domain controller)
a. Copy shutdownAllOnHC1.cmd and rename the copied script as shutdownAllOnHC<N>.cmd
b. Copy startServiceCatalogOnHC1.cmd and rename the copied script as s tartServiceCatalogOnHC<N>.cmd
c. Copy stopServiceCatalogOnHC1.cmd and rename the copied script as stopServiceCatalogOnHC<N>.cmd
Note In the Linux platform if new scripts does not have the read/write permission, you should manually assign the read/write permission before executing.
d. Perform the below operations in the stopServiceCatalogOnHC<N>.cmd script file cautiously:
This section provides information on how to configure the plugin for IIS web server (version 8.x) on a Windows Server 2012 R2 machine to redirect to clustered Wildfly application servers (version 8.2.0.Final).
To configure plugin got IIS Web Server:
Step 1 Add Web Server Role for IIS.
Step 2 Install Tomcat Plugin.
Step 3 Copy WAR Directories.
Step 4 Create Virtual Directories for IIS.
Step 5 Modify Plugin Properties.
Step 6 Configure Instance-ID for WildFly.
Step 7 Test 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.
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.
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-8.2.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-8.2.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-8.2.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-8.2.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-8.2.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-8.2.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 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:
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.
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.
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-8.2.0.Final\domain\configuration\domain.xml and search for the following line:
Replace it with the following value:
Step 3 Log on to the Host Controller 1 for RequestCenter, and stop all WildFly servers.
Step 4 Open file <PSC_Install_Dir>\wildfly-8.2.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-8.2.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,
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.
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-8.2.0.Final\domain\configuration\domain.xml and search for the following line:
Replace it with the following value:
Step 3 Open file <PSC_Install_Dir>\wildfly-8.2.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-8.2.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,
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.
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.
Step 1 Log on to the WildFly Admin console (URL example below) with you credentials and click OK. This will take you to WildFly Application administrator console.
http://<hostname>:<port>/RequestCenter
<hostname> = The fully qualified domain hostname or the IP address of the computer where you
installed the WildFly server for Service Catalog.
<port> =The HTTP Port number assigned to the Wildfly server for Service Catalog. The default value
Step 2 Click on Configuration tab to be able to edit and make changes.
Step 3 Click Add to add a new data source.
Step 4 Enter Name: SERVICECATALOGDS and JNDI Name: java:/<Name of the data source>
Step 6 Select driver as “Microsoft” and click Next.
Step 7 Enter the connection URL: jdbc:sqlserver://<db_server>:1433;DatabaseName=VM236_RCDB_RC4
Step 8 Enter your credentials.
Step 9 Fill up the various fields under different tabs as mentioned in the table below:
Minimum size is 20, maximum size is 80 and other values set to False. |
||
Step 10 Click Enable > Confirm.
Note (Applicable only for WildFly cluster) If the datasource is still disabled, set the datasoure to <enabled = true> in domain.xml file and restart the domain.
Step 11 In the Connection Tab test the connection and you will see the confirmation message: “Successfully created the JDBC connection.”
Step 12 Restart the WildFly server.
Step 1 Log on to the WildFly Admin console (URL example below) with you credentials and click OK. Click on Configuration tab to be able to edit and make changes.
http://<hostname>:<port>/RequestCenter
<hostname> = The fully qualified domain hostname or the IP address of the computer where you
installed the WildFly server for Service Catalog.
<port> =The HTTP Port number assigned to the Wildfly server for Service Catalog. The default value
Step 2 Click Add to add a new data source.
Step 3 Enter Name: SERVICECATALOGDS and JNDI Name: java:/<Name of the data source>
Step 5 Select driver as “oracle-thin” and click Next.
Step 6 Enter the connection URL: jdbc:oracle:thin:@//<db_server>:1433;DatabaseName=VM236_RCDB_RC4
Step 7 Enter your credentials.
Step 8 Fill up the various fields under different tabs as mentioned in the table below:
Minimum size is 20, maximum size is 80 and other values set to False. |
||
Step 9 Click Enable > Confirm.
Note (Applicable only for WildFly cluster) If the datasource is still disabled, set the datasoure to <enabled = true> in domain.xml file and restart the domain.
Step 10 In the Connection Tab test the connection and you will see the confirmation message: “Successfully created the JDBC connection.”
Step 11 Restart the WildFly server.