Configure the Automation Server
On this page
The Automation Server runs as a Windows service with the display name Alloy
Automation Server and the service name AlloyAutomationServer. You configure it in the Automation Server Manager: the
Windows account the service runs under, the database it connects to, and its
registration in that database. You start, stop, and restart the service from
the same window.
When two or more Automation Server instances are registered against one database, an administrator who holds the Settings App's right to the Automation Server service chooses the primary instance on the Settings App's High Availability Mode page, and there removes the registration of an instance that is neither primary nor running. In Alloy Navigator Cloud, the Settings App does not show the High Availability Mode node. That page, and the Automation Server's work once it runs, are described in Automation Server.
In the Installer
Installing the Automation Server registers the Windows service but does not start it. On a first installation, configuring and starting the Automation Server is a separate step after you create the database. When you upgrade, the installer restarts the service if it was running before the upgrade.
The evaluation installation is the exception: it starts the service itself once the database exists.
In the Automation Server Manager
Before you begin
- The Alloy Navigator database exists.
- You have the Database Access Key of that database.
Open the Automation Server Manager
You open the Automation Server Manager from the Alloy Control Panel. The Alloy Control Panel is installed with every Alloy Navigator component and lists the tools it finds on the computer, the Automation Server Manager among them. A tool whose program file is missing is not listed. Starting the Alloy Control Panel again brings its open window to the front instead of opening a second one. See Alloy Control Panel.
Starting the Automation Server Manager again on the same computer activates the window that is already open instead of opening a second one.
When it opens:
- If your Windows account does not have the rights to manage the service, the manager shows "You do not have enough permissions to manage the Alloy Automation Server." It still opens.
- If no Database Access Key is stored yet, or an older saved connection cannot be opened, the manager shows "Unable to find a valid Database Access Key. Please import your Database Access Key before configuring the Automation Server." and opens the key import.
The window has these parts:
| Part | What it shows |
|---|---|
| Startup account | The Windows account the service runs under, and Change Account.... |
| Connection | Key: with the name of the imported key, or N/A; Import Key...; SQL Server: and Database:. |
| Registered as: | How this computer's instance is registered in the database: Primary, Failover, or Not registered. |
| Status line | The state of the service and of its registration. Press F5 to refresh it. |
Choose the startup account
The startup account is the Windows account under which the Automation Server runs. It defines the security context for all operations the Automation Server performs.
- Under Startup account, click Change Account.... The Select Account window opens with the account the service uses now already selected.
- Choose one of the following:
- Local System account
- Network Service account
- This account: type the user name and the Password:, or click
Find... to pick a user in the Windows object picker. An account of
the local computer that you pick there is filled in as
.\<name>. The user name box, Password:, and Find... are available only while This account is chosen.
- Click OK.
The service configuration changes only when you changed the choice, the name, or the password. Choosing Local System account also marks the service as interactive. The manager then shows the account name it reads back from the service, and the window counts as changed.
For This account, an empty user name or password is refused. The window can grant the account the Log on as a service right, and it reports whether granting the right succeeded.
When the Automation Server and SQL Server are on separate computers and SQL Server uses Windows authentication only, choose This account and, for security reasons, a dedicated Windows user account rather than a built-in one. That account must have access to the SQL Server that hosts the database and enough rights to reach the network resources Alloy Navigator uses, such as Active Directory and the mail server.
Connect to the database
The Connection group sets how the Automation Server connects to the database.
- Click Import Key... and import the Database Access Key; see Database Access Key and Connections. Key: shows the key's name, and SQL Server: and Database: are filled in from the key. SQL Server: is unavailable while no key is stored, and Database: is also unavailable while SQL Server: is blank. The Database: list shows the databases on that server that are at the current version.
- Click Test Connection. What the test does depends on the key:
- For a key that does not use Windows authentication, the manager connects itself and reports "Test connection succeeded." or "Test connection failed." with the error.
- For a key that uses Windows authentication, the service makes the connection under its startup account. The service must be stopped; otherwise the manager shows "You'll need to stop the Automation Server before you can test the connection." With the service stopped, the manager registers the instance, saves the server and database, starts the service for the test, stops it again, and reports the result.
- Click Apply to save the connection. If the service is running, the manager asks "You must restart the Automation Server to apply the new settings. Restart now?"
Clicking OK while Apply is available saves the changes the same way.
Start the Automation Server
Click Start. The manager first saves any changed settings and registers the instance, as Apply does. It then asks the started service for its state and either reports success or lists what went wrong under "The Automation Server has started with the following error:": a database connection failure ("Database connection failure:"), gaps in the outgoing mail settings, and configuration warnings.
Restart also first saves any changed settings and registers the instance, but it does not ask whether to restart.
If no key is stored, Start and Restart show "No information about database connection provided. You need to obtain and import the database access key."
If the service cannot connect to the database when it starts, it writes the failure to the Windows event log and tries again: five times at 60-second intervals, five times at 10-minute intervals, and then every hour. A job that was due while the service was down runs once as soon as the service is active again.
The buttons follow the state of the service:
| Button | Available when |
|---|---|
| Start | The service is stopped. While the service is paused, Resume takes its place. |
| Stop | The service is started, stopping, or paused. |
| Restart | The service is started or paused. |
| Test Connection | A key is stored. |
| Apply | A key is stored and something has changed. |
The manager has no command that pauses the service.
The status line reads:
| Status line | When |
|---|---|
| Automation Server followed by the instance's status, such as Running (Active) or Running (Failover) | The service runs and its registration in the database reports it running. |
| Running with Errors (status) | The service runs, but its registration does not report it running. |
| Running with Errors (Not registered) | This computer has no registration, and the service is not stopped. |
| The state of the service | In any other case, such as a stopped service. |
| database access error | The manager cannot read the registration: no key is stored, no connection is open, or the query failed. |
| Automation Server is not installed | The service does not exist on this computer. |
Register the instance
The database keeps a list of the Automation Server instances registered against it. The manager registers this computer when you apply its settings, that is, when you click Apply, OK while Apply is available, Start, or Restart, and when you test a Windows-authentication key with the service stopped. Opening the manager registers nothing.
- When no instance is registered yet, the manager registers this computer as the only instance, primary and active, without asking.
- When other computers are registered and this one is not, the manager opens a registration wizard.
When exactly one other computer is registered, the wizard's first page offers Replace Automation Server. It reads "The Automation Server instance is currently registered on another computer (computer)." and offers "Remove the Automation Server registration on computer and replace it with the instance on the local computer." Replacing removes every existing registration and registers this computer as primary.
Choosing Advanced Registration instead leads to a page with two choices. When two or more computers are already registered, the first page is not available and the wizard offers these choices directly:
- "Register the instance on the local computer as primary."
- "Register the instance on the local computer as failover. If the active instance fails, the failover instance will automatically replace it."
When a primary instance is already registered, the first choice goes on to read "The Automation Server instance running on computer will become failover." The wizard itself only adds this computer as primary; it does not change the registration of the instance that is already primary.