Starting and Stopping Application Services

After the applications are installed successfully, the application services are deployed when the services are started.

Manually starting services

If you did not start the applications on the Install page, you can see the Deploying Applications page for information on the services that are created and how to start them.

The display name for Windows contains IBM WebSphere Application Server V8.5. For example, the Windows service name of the Emptoris Sourcing primary service is displayed as IBM WebSphere Application Server V8.5 – primary.

Service names

The following service names are created on the servers on which applications are installed.

Table 1. Emptoris Services
Service Name on Red Hat Enterprise Linux machines	Service name on Windows machines	Module
EmptorisHttpProxy	EmptorisHttpProxy	EmptorisHttpProxy
Emptoris Sourcing
primary_was.init	IBMWAS85Service – primary	Primary server
batch1_was.init	IBMWAS85Service - batch1	Batch server 1
batch2_was.init	IBMWAS85Service - batch2	Batch server 2
batch3_was.init	IBMWAS85Service - batch3	Batch server 3
proxy_was.init	IBMWAS85Service – proxy	Proxy server
event1_was.init	IBMWAS85Service - event1	Event server 1
event2_was.init	IBMWAS85Service - event2	Event server 2
event3_was.init	IBMWAS85Service - event3	Event server 3
Emptoris Contract Management
ecm1_was.init	IBMWAS85Service - ecm1	Emptoris Contract Management server 1
ecm2_was.init	IBMWAS85Service - ecm2	Emptoris Contract Management server 2
ecm3_was.init	IBMWAS85Service - ecm3	Emptoris Contract Management server 3
ecm4_was.init	IBMWAS85Service - ecm4	Emptoris Contract Management server 4
ecm5_was.init	IBMWAS85Service - ecm5	Emptoris Contract Management server 5
Not Applicable	IBM CM Document Server	Contract Document server
cognos1_was.init	IBMWAS85Service - cognos1	Cognos server
solr1 zookeeper-1	solr1 zookeeper-1	Search Server 1
solr2 zookeeper-2	solr2 zookeeper-2	Search Server 2
solr3 zookeeper-3	solr3 zookeeper-3	Search Server 3
solr4 zookeeper-4	solr4 zookeeper-4	Search Server 4
solr5 zookeeper-5	solr5 zookeeper-5	Search Server 5
solr6 zookeeper-6	solr6 zookeeper-6	Search Server 6
solr7 zookeeper-7	solr7 zookeeper-7	Search Server 7
Emptoris Spend Analysis
spendPrimary_was.init	IBMWAS85Service - spendPrimary	Spend primary server
plinthosnode1_was.init	IBMWAS85Service - plinthosnode1	Reporting server 1
plinthosnode2_was.init	IBMWAS85Service - plinthosnode2	Reporting server 2
plinthosnode3_was.init	IBMWAS85Service - plinthosnode3	Reporting server 3
plinthosdbCopyNode_was.init	IBMWAS85Service - plinthosdbCopyNode	Database copy node (only when OLF is enabled)
Emptoris Strategic Supply Management Platform and Emptoris Program Management
gateway_was.init	IBMWAS85Service – gateway	Primary server
SSMIndexServer_was.init	IBMWAS85Service - SSMIndexServer	Index server
Emptoris Supplier Lifecycle Management
slm_was.init	IBMWAS85Service – slm	Primary server

Note: Depending on the servers you choose for installation, you may not see all the services listed in the table.

Order of starting services

Immediately after the installation, the Emptoris Strategic Supply Management Platform and the Emptoris Sourcing Proxy Server (if installed) are automatically started.

Use the following order to start the services of Emptoris products.

Stop and restart the Emptoris Strategic Supply Management Platform
Sourcing Primary (If Emptoris Sourcing is installed)
All other Emptoris services can be started concurrently
Start the EmptorisHTTPProxy service last to ensure that the environment is accessible only after all modules are started.

Starting applications on Windows

You can start and stop applications using the Windows service manager application or by using the Windows sc command.

To start the applications when services are not installed, use the following command.

<WAS_HOME>\AppServer\bin\startServer <server_name> -profileName<profile_name>

When running from the profile directory of a product, do not specify the profile.

<emptoris_install_dir>/perm/...../<profile>/bin/startServer<server_name>

For Emptoris Sourcing, you must start the sourcing_spa1 service of the primary server before starting any other Emptoris Sourcing service.

Starting applications on Linux

If the application is installed as a service use the service start/stop command to start and stop the application.

service gateway_was.init start

You may need root or sudo privileges to run this command.

Note: For Emptoris Sourcing, you must start the sourcing_spa1 service of the primary server before starting any other Emptoris Sourcing service.

Starting the EmptorisHTTPProxy service

If you cannot start the EmptorisHTTPProxy service, check whether SELinux is enabled. If it is enabled, you must configure it to allow Apache to run as the emptoris user in the installation directory configured by the install process. Please consult your operating system documentation for details.