Deployment Manual / Version 2101
Table Of ContentsThe service names are defined in the recipe of each service. Although, the name is being set in a variable at the top of the recipe, changing the name will affect notifications and subscription dependencies to or from other resources. By default, there are no such dependencies but renaming should be done with care.
The services log into files named after the service name. That is, for example, the
Content Management Server logs into the content-management-server.log
file.
Note
The CAE Live service has the option to be installed multiple times on the same node, for
each instance an incremental number is suffixed to the name. If only one instance is
installed, the service name is therefore cae-live-1
Component Name | Service Name |
---|---|
Solr Search Engine | solr |
Content Management Server | content-management-server |
Master Live Server | master-live Server |
Workflow Server | workflow-server |
Content Feeder | content-feeder |
User Changes | user-changes |
Elastic Worker | elastic-worker |
CAE Feeder Preview | cae-feeder-preview |
CAE Feeder Live | cae-feeder-live |
CAE Preview | cae-preview |
Studio Rest Server | studio-server |
Headless Server Preview | headless-server-preview |
Headless Server Live | headless-server-live |
Replication Live Server | replication-live-server |
CAE Live | cae-live-1 |
Commerce Adapter IBM WCS | commerce-adapter-wcs |
Commerce Adapter SAP Hybris | commerce-adapter-hybris |
Commerce Adapter Salesforce Commerce Cloud | commerce-adapter-sfcc |
Table 2.1. Service Names