Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Cisco Prime Service Catalog 11.1 Installation Guide

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco Prime Service Catalog 11.1 Installation Guide

Chapter Title

WildFly Scripts

Results

Updated:
July 19, 2016

Chapter: WildFly Scripts

WildFly Scripts

Scripts for WildFly Standalone Application Server

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.

 

Table B-1 Scripts for WildFly Standalone Application Server

Scripts
Execute On
Description

startServiceCatalog

VM1

Start Service Catalog on VM1

startServiceLink

VM1

Start Service Link on VM1

stopServiceCatalog

VM1

Stop Service Catalog on VM1

stopServiceLink

VM1

Stop Service Link on VM1

Scripts for WildFly Cluster Application Server

Cluster setup for WildFly can be configured in two VM or four VM topology.

Two VM topology:

  • VM 1 is Domain Controller, Host Controller, and Service Link for Host 1
  • VM 2 is Host Controller for Host 2

Four VM topology:

  • VM 1 is Domain Controller
  • VM 2 is standalone Service Link
  • VM 3 is Host Controller for Host 1
  • VM 4 is Host Controller for Host 2

Table B-2 Scripts for WildFly Cluster Application Server

Scripts
Execute On
Description
2 VM Cluster Topology:
VM1 is Domain Controller, HC1, and Service Link and VM2 is HC2.

startServiceCatalogCluster

VM1

Start the following servers on VM1: a) Domain Controller, b) Process Controller, c) Managed server for Service Link, d) Managed server for Service Catalog.

Note startServiceCatalogCluster script is used to check whether the exploded $JBOSS_HOME/content/RequestCenter.war and $JBOSS_HOME/content/ISEE.war are already available. If yes, then the script will not create the content folder. If not, then it will explode the WAR files from /dist folder and create the content folder under these directories. This is applicable for VM1 and VM2 in two VM topology and for VM 3 and VM 4 in four VM topology.

startServiceCatalogOnHC1

VM1

Start the Managed server for Service Catalog on VM1

startServiceLinkOnHC1

VM1

Start the Managed server for Service Link on VM1.

startServiceCatalogOnHC2

VM1

Start the Managed server for Service Catalog on VM2.

startServiceCatalogOnHC3

VM1

Start the Managed server for Service Catalog on VM3. (Reserved for when user wants to add Host Controller 3.)

startServiceCatalogOnHC4

VM1

Start the Managed server for Service Catalog on VM3. (Reserved for when user wants to add Host Controller 4.)

deployServiceCatalogCluster all

VM1

Deploy the followings: a) ISEE.war, b) RequestCenter.war

deployServiceCatalogCluster RC

VM1

Deploy RequestCenter.war

deployServiceCatalogCluster SL

VM1

Deploy ISEE.war

shutdownAllOnHC1

VM1

Stop the following servers on VM1: a) Domain Controller, b) Process Controller, c) Managed server for Service Link, d) Managed server for Service Catalog.

forceStopAllOnHC

VM1

If for some reasons, the shutDownAllOnHC1 script doesn't work, then execute this script to force stop the following servers on VM1: a) Domain Controller, b) Process Controller, c) Managed server for Service Link, d) Managed server for Service Catalog

stopServiceCatalogOnHC1

VM1

Stop the Managed server for Service Catalog on VM1.

stopServiceLinkOnHC1

VM1

Stop the Managed server for Service Link on VM1.

stopServiceCatalogOnHC2

VM1

Stop the Managed server for Service Catalog on VM2.

shutdownAllOnHC2

VM1

Stop both the Process Controller and the Managed server on VM2.

stopServiceCatalogOnHC3

VM1

Stop the Managed server for Service Catalog on VM3. (Reserved for when user wants to add HC3.)

shutdownAllOnHC3

VM1

Stop both the Process Controller and the Managed server on VM3. (Reserved for when user wants to add HC3.)

stopServiceCatalogOnHC4

VM1

Stop the Managed server for Service Catalog on VM3. (Reserved for when user wants to add HC4.)

shutdownAllOnHC4

VM1

Stop both the Process Controller and the Managed server on VM4. (Reserved for when user wants to add HC4.)

undeployServiceCatalogCluster all

VM1

Undeploy the followings: a) ISEE.war, b) RequestCenter.war

undeployServiceCatalogCluster RC

VM1

Undeploy RequestCenter.war

undeployServiceCatalogCluster SL

VM1

Undeploy ISEE.war

startServiceCatalogCluster

VM2

Start the following servers: a) Process Controller, b) Managed server for Service Catalog.

The script is used to check whether the exploded $JBOSS_HOME/content/RequestCenter.war and $JBOSS_HOME/content/ISEE.war are already available. If yes, then the script will not create the content folder. If not, then it will explode the WAR files from /dist folder and create the content folder under these directories.

forceStopAllOnHC

VM2

Force stop: a) Process Controller, b) Managed server for Service Catalog.
If customer adds another VM as HC3

startServiceCatalogCluster

VM3

Start the following servers: a) Process Controller, b) Managed server for Service Catalog.

forceStopAllOnHC

VM3

Force stop: a) Process Controller, b) Managed server for Service Catalog.

If customer adds another VM as HC4

startServiceCatalogCluster

VM4

Start the following servers: a) Process Controller, b) Managed server for Service Catalog.

forceStopAllOnHC

VM4

Force stop: a) Process Controller, b) Managed server for Service Catalog.
4 VM Cluster Topology:
VM1 is Domain Controller, VM2 is Standalone for Service Link, VM3 is HC1, VM4 is HC2

startServiceCatalogCluster

VM1

Start the Domain Controller on VM1.

startServiceCatalogOnHC1

VM1

Start the Managed server for Service Catalog on VM3.

startServiceCatalogOnHC2

VM1

Start the Managed server for Service Catalog on VM4.

startServiceCatalogOnHC3

VM1

Start the Managed server for Service Catalog on VM5. (Reserved for when user wants to add HC3.)

startServiceCatalogOnHC4

VM1

Start the Managed server for Service Catalog on VM6. (Reserved for when user wants to add HC4.)

deployServiceCatalogCluster RC

VM1

Deploy RequestCenter.war

stopDomainController

VM1

Stop the Domain Controller on VM1.

stopServiceCatalogOnHC1

VM1

Stop the Managed server for Service Catalog on VM3.

shutdownAllOnHC1

VM1

Stop both the Process Controller and the Managed server on VM3.

stopServiceCatalogOnHC2

VM1

Stop the Managed server for Service Catalog on VM4.

shutdownAllOnHC2

VM1

Stop both the Process Controller and the Managed server on VM4

stopServiceCatalogOnHC3

VM1

Stop the Managed server for Service Catalog on VM5. (Reserved for when user wants to add HC3.)

shutdownAllOnHC3

VM1

Stop both the Process Controller and the Managed server on VM5. (Reserved for when user wants to add HC3.)

stopServiceCatalogOnHC4

VM1

Stop the Managed server for Service Catalog on VM6. (Reserved for when user wants to add HC4.)

shutdownAllOnHC4

VM1

Stop both the Process Controller and the Managed server on VM6. (Reserved for when user wants to add HC4.)

undeployServiceCatalogCluster RC

VM1

Undeploy RequestCenter.war

VM1 is Domain Controller, VM2 is Standalone for Service Link, VM3 is HC1, and VM4 is HC2

StartServiceLink

VM2

Start Service Link on VM2.

StopServiceLink

VM2

Stop Service Link on VM2.

VM1 is Domain Controller, VM2 is Standalone for Service Link, VM3 is HC1, and VM4 is HC2

startServiceCatalogCluster

VM4

Start the following servers: a) Process Controller, b) Managed server for Service Catalog.

The script is used to check whether the exploded $JBOSS_HOME/content/RequestCenter.war and $JBOSS_HOME/content/ISEE.war are already available. If yes, then the script will not create the content folder. If not, then it will explode the WAR files from /dist folder and create the content folder under these directories.

forceStopAllOnHC

VM4

Force stop: a) Process Controller, b) Managed server for Service Catalog.

If customer adds another VM as HC3

startServiceCatalogCluster

VM5

Start the following servers: a) Process Controller, b) Managed server for Service Catalog.

forceStopAllOnHC

VM5

Force stop: a) Process Controller, b) Managed server for Service Catalog.

If customer adds another VM as HC4

startServiceCatalogCluster

VM6

Start the following servers: a) Process Controller, b) Managed server for Service Catalog.

forceStopAllOnHC

VM6

Force stop: a) Process Controller, b) Managed server for Service Catalog.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

Related Cisco Community Discussions

About Us
Contact Us
Work with Us