JAMS Agent for Windows

The JAMS Agent for Windows runs as a background service that executes JAMS Jobs under the direction of a JAMS Scheduler on a different machine. It is a best practice to use Agents to offload resources to another server other than the JAMS Scheduler. Agents can also be used when JAMS is configured for high availability, so Job execution is not interrupted during a failover event.

You have two options to install the JAMS Agent for Windows:

• Manually install the JAMS Agent for Windows
• Push deploy the JAMS Agent for Windows

Before You Begin

• Ensure the Agent meets the system requirements for the JAMS version. See the JAMS Installation Guide for more information.
• Ensure the user installing the JAMS Agent for Windows has administrator rights.
• Ensure the following ports are open and accessible through the firewall:
  • Port 77 – The JAMS Agent service listens on port 77 to communicate with the JAMS Scheduler.
  • Port 773 - To run Sequence, Workflow, or SQL Jobs on a Windows Agent, this port needs to be open on both the JAMS Scheduler Server and the Agent Server.
• For only the Push Deploy option, Windows RemoteAdmin needs to be enabled and accessible from the JAMS Scheduler server.
• For only the Push Deploy option, the administrator share on the remote server must be accessible from the JAMS Scheduler server.

Manually Installing the JAMS Agent for Windows

The installer package (.msi) sets up an Agent service on the Agent machine called 'JAMS Agent'. A new directory will contain the executable files in C:\program files\MVPSI\JAMS\Agent by default.

1. On the JAMS Scheduler machine, go to Program Files\MVPSI\JAMS\Scheduler\Agents\Windows.
2. Copy the SetupAgent.msi or SetupAgentx64.msi file and paste it onto the remote Agent machine.
3. Double-click the .msi file to run the installer and follow the prompts. When the installation is complete, you will see a Windows service called 'JAMS Agent' running.
4. Define the JAMS Agent for Windows as described below.

Defining a JAMS Agent for Windows

After you install the Agent software, define the Agent within the JAMS Client so it can run Jobs.

1. Click Agents from the Shortcuts menu.
2. Click +.
3. In the Name field, enter a name for the Agent.
4. Click Ok.
5. Click the Properties tab.
6. Verify the Address field is correct.
7. Optional – If you are going to push deploy the Agent, you can set the Deploy Credential on the Agent. If you do not set it on the Agent, you will be prompted to select a Credential when you deploy the Agent.
8. It is recommended that the JAMS Agent Service run as 'Local System'. This is the default option and does not require additional configuration.

Push Deploy the Windows Agent using Local User Accounts

When deploying a remote JAMS Agent to a Windows server, the standard practice is to use a domain account user with Administrator privileges on both the JAMS Scheduler and the remote JAMS Agent machine.

However, if you don’t have an environment that uses domain accounts, there are two alternative options for setting up the remote JAMS Agent software for a Windows server:

• Manually install the JAMS Agent for Windows (see the preceding section).
• To allow the push deployment of the Windows JAMS Agent to a remote server when not using domain user accounts, ensure the JAMS Scheduler and remote Agent server use the same administration level user account and password.

1. Click Agents from the Shortcuts menu.
2. Ensure the Agent has been defined as described above.
3. Right-click the Agent to be deployed, and select Deploy.
4. In the dialog, select the JAMS User to deploy the JAMS Agent.
5. This user should have all necessary permissions to the defined JAMS Agent.
6. Click OK. The Deploy Agent Job runs in the Monitor view.