Front-end logical service names are used by customers and should be clear and concise. They have the following form:
service-geo.example.com |
Where the front-end service is one of the following:
mail for Messaging Server
mobile for Wireless
book for AddressBook
access for HTTP and Communications Express
cal for Calendar Server
im for Instant Messaging
An example of a logical service name would be mail-amer.example.com that American employees would use as their mail server.
The back-end names for these logical services that are used by the customer have the following form:
complexNameN-serviceM.subdomain |
For example, first node of second mail cluster in the complex can be accessed as bedge2–mail1.us.example.com.
Back-end logical services not used by the customer have names of the following form:
service-geo-NN.subdomain |
Where the back-end service is one of the following:
ds for Directory Server, and NN is 01 for a Master, and 02 or 03 for a Replica
id for Access Manager and associated Web Server, and NN is 01 or 02, which are load-balanced
For example, ds-amer-01.us.example.com is the master Directory Server for the complex serving the Americas.