Read these instructions completely before you install or update the enterprise agent software.
Robot Schedule Enterprise agents can be installed on the following systems:
Windows 8.1 and Windows 10
Windows Server® 2012, 2012R2, 2016, 2017 and 2019
AIX® 7.1 and higher
Red Hat® Enterprise Linux 4, 5, 6 (and compatible binary systems)
SUSE® Linux Enterprise Server 10 and 11 (and compatible binary systems)
Oracle® Solaris 9, 10, 11 (on SPARC® only)
HP-UX 11v2 and 11v3 (IA-64 only)
Running the agent system as the root user can cause problems. We recommend that you run the agent system as a user other than root.
File and directory event monitors can monitor only those files and directories to which the user you choose normally has access. You must set up permissions for this user on the agent system to be able to monitor any file or file system location that's needed. This may require adding the user to a group that has access to a file or directory that you want to monitor.
If you run the agent system as the root user, be aware that there are no restrictions for files or directories to be monitored with agent event monitors. However, Robot Schedule Enterprise prevents jobs whose agent environment user is root from running on an agent system that is running as root.
Make sure that all of the agent’s installed files can be accessed by the user that you choose. We recommend that you assign file ownership to the user you will run the agent system as. For example, if you run the agent as the user “robot,” you should change ownership of all the agent’s files to “robot.”
The Java Virtual Machine (JVM) is not installed with UNIX and Linux agents. Sun Java 7 or higher is supported.
If the agent system is running a 64-bit UNIX or Linux operating system, the 64-bit version of the JVM is required.
If you are updating an agent and are using the Transponder, you must start up the transponder after the update.
Use the same instructions below for updating agents.
You must install the Robot Schedule Agent Manager in order to set up agents on Windows systems. This can be done as part of the IBM i server download and transfer. For details, see “Installing or Updating Robot Schedule Enterprise.”
If you did not install on your Windows system as you were downloading and transferring the IBM i objects, or if you need to install on multiple Windows systems, you can follow the steps below.
Download the setup-windows-agent2.exe from the Robot Schedule Enterprise download page
Double-click setup-windows-agent2.exe file and follow the onscreen instructions to update the agent service and Robot Schedule Agent Manager GUI.
The setup will now complete. You can run the Agent Manager from your Start menu or by clicking the icon from the Windows tray.
Notes: If you are updating an agent and are using the Transponder, you must start up the transponder after the update.
You can run multiple agents from the same Windows system, and connect them to multiple enterprise servers.
Note: Make sure you use a unique port number for the local agent settings to avoid conflicts when connecting multiple agents.
From the Start menu, go to Programs > Help Systems > Robot Schedule Agent Manger.
Or, from the Windows tray, click the Robot Schedule Agent Manager icon.
Click Add. The Add Agent window displays.
Select Create a new Agent or Create an Agent from a configuration file.
If you selected "Create an Agent from a configuration file," click the Find button to locate the agent configuration file. The Agent Configuration window displays.
Set server information, Enterprise (IBM i) settings, and local agent settings for this agent.
Choose an alias for the agent. It can be anything under 12 characters. Once selected, the Agent Name and Agent Configuration File name will populate. You have the option to change the default Agent Configuration File name.
Choose if you want the agent to start when the service starts, or if you want to start it manually.
Note: A newly created agent will not start automatically, even if you select “Yes, start when the Service starts.” You’ll have to start it manually the first time.
Enter the Enterprise server address and port number (if different from the default).
Review the Local Agent settings. You can test the port number to see if it’s free to use.
Click OK. The new agent is displayed in the list.
Download the unix_schent.tar file from My Downloads page on our website.
Use FTP to copy the unix_schent.tar file in BIN (binary) mode to your home directory on the UNIX or Linux system.
Note: It's very important that you copy the file using BIN mode.
On your UNIX or Linux system, type pwd at the command prompt and press Enter.
The home directory and your username should display as: /home/. If it doesn't display, use the cd command to change to the home directory.
Note: The Solaris home directory may be /export/home/.
Enter the following command to create a directory for the installation:
Note: If you are updating the agent and the agent_install directory already exists, you must remove it before recreating it with the mkdir agent_install command. Use the following command to remove the directory:
rm -rf /xxxx/agent_install
where xxxx is the name of the directory where your previous installation files were stored.
Transfer the unix_schent.tar file from your PC to the agent_install directory that you created on the UNIX or Linux system.
Change to the agent_install directory using the following command:
Unpack the unix_schent.tar archive using the following command:
tar -xf unix_schent.tar
Set the JAVA_HOME environment variable to a JVM version 1.5 or greater using the following commands:
where javalevel is the level of your Java. For example, jre1.6.0_11.
Install the agent software on your system using the following command:
Follow the onscreen instructions to complete the installation. Press Enter to accept the default, which display in brackets.
Start the server using the following command:
Note: You may want to add this command to your server’s startup sequence.
If you choose to assign file ownership to the user to run the agent system as, use the following command:
chown -R robot/opt/helpsystems/schent
where robot is the user you want to run the agent system as.
Note: If you want to run jobs on this agent without requiring a user’s password (run as agent’s user), after the agent is installed and the agent process is started, run the script allownopwd.sh as the root user. You can find the script in the agent directory. Then, see the Robot Schedule Enterprise User Guide for information on the additional setup that’s needed.
After you've added/installed/updated agents, use the Robot Schedule Explorer on your PC to work with Robot Schedule Enterprise.
Still have questions? We can help. Submit a case to Technical Support.