The JAMSAgentX software can also be installed manually - this manual installation will require root access.
JAMSAgentX can be found on the JAMS Scheduler machine, in the following directory by default: C:\Program Files\MVPSI\JAMS\Scheduler\Agents\
- Copy the JAMSAgentX file to a directory on the agent server (The location does not necessarily matter, but the recommended/default location is /usr/bin/).
- chmod 755 /usr/bin/JAMSAgentX
Note: chmod is utilized to change the permissions and ownership rights of a file. 755 specifies that a file is to be given “read, write and execute by owner” access, as well as “read and execute by the group and everyone else” access.
It is worth noting that:
- The JAMSAgentX and JAMSWebClient files are executables
- JAMSAgentX does not require a start-up script, and uses the Linux/UNIX SSH daemon on the default port, 22
- After this process is completed, the agent can be defined within the JAMS client GUI, in the Agents shortcut. Deployment option is not needed as this installation has already been performed.
- JAMSAgentX keeps temporary log data. By default, JAMSAgentX stores these files in the directory “.jams” in the home directory. If preferred, these files can be kept elsewhere.
- Upon initial execution, JAMSAgentX will automatically create this directory if it does not yet exist, along with any configuration files that JAMSAgentX requires to run.
- To test that it runs properly, type “JAMSAgentX --verbose” into a terminal. Type “quit” to exit.
- Lastly, Click the "Execution Method" shortcut within the Management group and double-click the SSHAgent Execution method. The Command field is located on the "Execution" tab of the Execution Method.
If JAMSAgentX is located in /usr/bin/ the command should be left as "JAMSAgentX" - otherwise, supply the full path to where JAMSAgentX is installed.
lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
This is a common issue related to an instance of Linux lacking the 32 bit libraries required to run the 32 bit JAMSAgentX.
This can easily be resolved by simply running sudo yum install glibc.i686 OR apt-get install libc6:i386