Installing Instances
Production or production-like environments require an external configuration store and an external CTS token store, both of which are DS servers. The configuration store will act as the CTS token store until you configure an external one.
For more information, see Preparing External Stores.
Install multiple instances to maintain service availability. If one instance is down for any reason, another instance can respond instead. This means that you need some type of component, such as a load balancer or a proxy server, between incoming traffic and AM to route around instances that are down.
AM uses a site for this purpose. In an AM site, multiple AM instances are configured in the same way, and accessed through a load balancer layer.
The load balancer can be implemented in hardware or software, but it is separate and independent from AM. When installed properly, a site configuration improves service availability, as the load balancer routes around AM instances that are down, sending traffic to other servers in the site.
For high-level deployment information, see the Deployment Planning Guide.
The following table provides information to help you install AM instances:
| Task or Requirement | Resources |
|---|---|
| Configure a single instance on a production or pre-production environment. This can be the first instance of a site deployment. | "To Configure an Instance" |
| Configure a site and add a instance to an AM site | "Configuring Sites and Adding Servers to Sites" |
Configure an instance silently | "Installing Silently" |
Tip
If at any point you need to scrap the AM configuration to start again, see "Deleting and Redeploying AM".