Service names
You can specify unique service names to differentiate the multiple services in a clustered environment.
Each service has a long name and a short name, and in clustered
environments, you can identify certain services with unique service
names. Run the $TOP/bin/go/svc_control.sh --action=list script
to see the full names of all the services that are defined on a server.
The workflow service can only have one instance running in all environments. All services other than the workflow service, can have multiple instance running so you should ensure that each service name is different because a service will not start if another service in the clustered environment shares the same name.
Fixed short names
The admin and appsvr service names are fixed by Product Master:
- Admin service
- admin_machine_name
- Application service
- appsvr_machine_name
Default short names
The service default short names are:
- Event processor
- eventprocessor
- Queue manager
- queuemanager
- Scheduler service
- scheduler
- Workflow engine
- workflow
- RMI registry
- rmiregistry
Long service names
The long names for services are built internally by the system and are based on the short name of each service:
rmi://machine_name:rmi_port/database_user_name/service/service_short_name
- Long service name variables:
- machine_name is your machine name
Examples of long names
- Machine name: server 1
- RMI port: 17507
- Database user name: pauadm
- Service: sheduler
- Service short name: sch1
For the same database user and rmi port, if another scheduler service with short name sch2 is run on another server with machine name server 2, the long name will be: rmi://server2:17507/pauadm/scheduler/sch2.