First startup

When TMS is started for the first time, the following steps are performed.

TMS primary server:

1. TMS datastore is created.
2. Data dictionary is loaded from TMSManifest.dll.
3. TMS performs a discovery of components and configurations on the TMS primary server.
4. TMS primary server starts listening for requests.

All TMS secondary servers:

1. TMS secondary servers attempt to contact the TMS primary.
2. If the connection attempt fails:
   1. The connection is retried every 10 seconds.
   2. An error is logged every 5 minutes until the connection is successful.
3. TMS Datastore is created.
4. Secondary server requests data from the TMS primary server.
5. TMS performs a discovery of components and configurations on the TMS secondary server. Newly discovered items are forwarded to the TMS primary for updating.
6. Secondary server begins listening for requests.

Subsequent startups

1. TMS primary server checks TMSManifest.dll for data dictionary updates.
2. TMS primary server starts listening for requests.

All TMS secondary servers:

1. TMS secondary servers attempt to contact the TMS primary.
2. If the connection attempt fails:
   1. The connection is retried every 10 seconds.
   2. An error is logged every 5 minutes until the connection is successful.
3. TMS Datastore is created.
4. Secondary server requests data from the TMS primary server.
5. TMS performs a discovery of components and configurations on the TMS secondary server. Newly discovered items are forwarded to the TMS primary for updating.
6. Secondary server begins listening for requests.