Start Order Sequence of DevTest Components

Products

• Service Virtualization

Issue/Introduction

This article explains the process of starting the DevTest Server with all components available. Use the sequence that is shown to ensure that all components start. Some ways you can start the DevTest processes or services are described following the start process.

Environment

All supported DevTest releases.

Resolution

Start Order Sequence

Start the DevTest Server processes (or services) in the following sequence:

• Start Identity and Access Manager.
• Start the Enterprise Dashboard Server.
• Start each Registry.
• Start DevTest Portal.
• Start the following components in any order:
• Broker
• Coordinator server
• Simulator server that is associated with each coordinator
• Virtual Service Environment
• Virtual Service Catalog
• If used on the DevTest Server, start DevTest Workstation

NOTE: To shut down the server components, use the reverse order.

Ways You Can Start

DevTest Server

Access the DevTest Server processes in one of the following ways:

• (Windows) Click the Start menu and expand DevTest Solutions. Start the processes in start order sequence.

• Go to the LISA_HOME\bin folder. Start the executables in start order sequence.

• (Windows) Go to Services and start the services in start order sequence.

• Open a command prompt as an Administrator or open a terminal window. Go to LISA_HOME\bin, and enter the command to start each process in start order sequence. You can also start the respective services or start the associated vmoptions file. Get help by entering the command name followed by --help.
• Execute the scripts in the LISA_HOME\bin folder. The startdefservers.bat script starts all components except the Enterprise Dashboard in the correct order. The stopdefservers.bat script stops all components

NOTE: IAM is not in the start and stop scripts, so it will need to be started before the scripts are run, or you can modify the scripts to add IAM.

Additional Information

On Linux the script are LISA_HOME/bin/startdefservers.sh and stopdefservers.sh.

 

Documentation provides more information on Running Server Components as Services.