Servigistics InService Deployment > Launching Servigistics InService
  
Launching Servigistics InService
To launch Servigistics InService you must first start the following components, in the order listed here:
1. Publisher and Viewer entities. Run the startInService.bat file to start the entities as specified in configurator.xml. To run this file, perform the following steps:
a. Open the command prompt as administrator, and navigate to the folder ..\InService\InS_SW\SW where Servigistics InService is installed.
b. On Windows, run the startInService.bat file. On Linux, open a terminal and run the startInService.sh command.
2. The Windchill Directory Server. However, you must perform these steps only when Windchill Directory Server is installed as part of Servigistics InService setup. To start the Windchill Directory Server use the following procedure:
On Windows, open the command prompt as administrator, navigate to the \InS_SW\SW\System\WindchillDS\server\bat\ folder, and run the start-ds.bat file.
On Linux, navigate to the \InS_SW\SW\System\WindchillDS\server\bin\ folder, open a terminal, and run the start-ds.sh file.
Once these components have been started you can access Servigistics InService using the following URLs:
Shortcut Name
Command or URL
Module
Publisher/Task Manager
http://<hostname>:<port>/TaskManager
Publisher
Viewer
http://<hostname>:<port>/InService/delivery
Viewer
Administration home page
http://<hostname>:<port>/InService/delivery/scadmin.jsp
Viewer
The following scripts and URLs may also be of use to you:
Shortcut Name
Command or URL
Module
Windows: JConsole
UNIX: jconsole
Windows: <SW_DIR>/System/Java/bin/jconsole.exe
UNIX: jconsole
Publisher
Viewer
Windows: JVisualVM
UNIX: jvisualvm
Windows: <SW_DIR>/System/Java/bin/jvisualvm.exe
UNIX: jvisualvm
Publisher
Viewer
User Help Center
http://<hostname>:<port>/InService-HCUSER
Viewer
Administration Help Center
http://<hostname>:<port>/InService-HCADMIN
Viewer
3. Your database.The external database (Oracle, SQL, or PostgreSQL) configured with Servigistics InService must be up and running.
4. Optional: You can also use an advanced option to manually start all the entities services. For Publisher, it starts the Core, Core CMI, and JBOSS services. For Viewer, the entity that you have configured on the Viewer (specified in the configurator.xml file) is launched. For example, if you have configured core1, coreCMI1, and viewer1, then these entities are launched for Viewer instead of JBoss.
To launch the Core Server use one of the following scripts:
Windows: <SW_DIR>/coreServer.bat
UNIX: coreServer.sh
To launch the Core CMI Server use one of the following scripts:
Windows: <SW_DIR>/coreCMIServer.bat
UNIX: coreCMIServer.sh
To launch JBoss use one of the following scripts (only for Publisher):
Windows: <SW_DIR>/jboss.bat
UNIX: jboss.sh
To launch other entities, search for the .bat file that holds the entity name as configured in the configurator.xml file.