1.2 Naming Conventions

The following naming conventions are used to create physical and logical system names. This document focuses on a single EdgeMail complex installed in a single geographic site. However, complexes are meant to be deployed in several sites to cover all geographic distribution of corporate employees, and system names must allow for them all.

Three elements are used in system names to identify a given complex:

• The geo is the intended geographic coverage of the complex, for example euro for Europe, amer for North America, soam for South America, and asia for Asia.

• The complexName itself, which distinguishes between identical systems in separate locations, for example aedge, bedge, and cedge.

• The network subdomain of the corporate network to which each complex belongs, for example uk.example.com, us.example.com, jp.example.com.

The complex described in this document is bedge in the us.example.com subdomain, serving the amer geographic region.

1.2.1 Physical System Names

Front-end systems have physical names in the following form:

fe-geo-NN.example.com

Where NN is a two-digit number that sequentially numbers the front-end systems of a given complex, for example fe-amer-01.example.com.

Back-end systems have physical names in the following form:

phys-complexNameN-M.subdomain

Where N-M are two digits that identify the cluster number and node number, for example phys-bedge3–2.us.example.com is the second node of the third cluster. Because each node of a cluster is on a separate rack, the two digits also identify the server number and the rack number, for example, the physical name above is also the third system in the second rack.

1.2.2 Logical Service Names

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.