For Information on Aspire 3.1 Click Here
The Admin User interface can be used to manage all Aspire servers, including installing new ones. If you are running in a single node environment, you may still want to have separate servers for development, test, and production. You may also want a backup/failover server.
If you are running in a multi-node environment (i.e.. running Aspire in a distributed processing environment with multiple production nodes routing jobs to each other), you will also need to install multiple Aspire servers. For more information on that kind of environment, please also see the rules for distributed processing in Multi-Node Installation.
When you first download Aspire, it will be installed onto whatever server you are working on. If you are simply testing out the Community version of Aspire, that's probably all you will need.
You can use the System Admin interface to stop and start a server (using the red/green button to the far right of the server name) as needed. You can can also use the Debug Console (the link below the startup time/stop time) to do this. Every Aspire server has its own Debug Console, which will show you a more detailed picture of what is running on that server, the general system health, and statistics on usage.
Once you have installed some Aspire applications onto a server, those will appear as "Installed Applications" under the host name of the server (see screen at right).
Installing a New Server
Installing a server creates a new Aspire instance on a remote host by copying the Aspire files to that host. This is what you would do in order to create a Test instance from your Development instance, for example. You would also do this to create a failover instance of a production server.
Optionally, you can register the newly installed server.
If you need to create an Aspire instance on a server without Internet access, see here for instructions.
Registering a Server
When you register a server, it makes the current Aspire instance aware of any other Aspire instances. You must register any server that will be part of a distributed processing scheme.
Enabling Server Detection
If you check the Enable Server Detection box, Aspire will be able to dynamically detect other Aspire instances that are either online or offline. This is done using the broadcast discovery method.
This box will need to be checked in distributed environments in order to allow Aspire to detect which servers are available so that jobs are only routed to available/running servers. This way, Aspire can also re-route jobs as needed between machines. For more information, see the Distributed Processing discussion.