Introduction:
An administrator can set up manual assignment of InTime jobs to InTime Agent(s) instead of the default auto-assignment by the InTime Server. This feature is only supported by the Private Enterprise license.
Steps:
Example: Start InTime Server with an "-auto off" argument. Then, the InTime Server administrator needs to set the "matchuser" flag to "no" so that InTime Agents started by other users can be used.
$ cd <intimeserver directory> $ ./start_server.sh -auto off -matchuser no
1. Start admin console, check the server license if it is Private Enterprise license.
$ ./admin_console.sh user> .server.lic +------------------+--------------------------+ | KEY | VALUE | +------------------+--------------------------+ | COMPANY_NAME | Plunify.com | | CONCURRENT_USED | 0 | | CONCURRENT_LEFT | 80 | | CONCURRENT_TOTAL | 80 | | START_DATE | 2018-07-01T00:00:00 | | EXPIRY_DATE | 2020-12-28T23:59:29 | | LICENSE_TYPES | EVAL_PRIVATE_ENTERPRISE | | LICENSE_VERSION | 2 | | MAC_ADDRESS | 123456789012 | +------------------+--------------------------+
2. Make sure the AUTO_FLAG is set to OFF.
user> .server.properties +-----+------------+-----------+-------+ | NO. | READ/WRITE | KEY | VALUE | +-----+------------+-----------+-------+ | 1 | R/W | AUTO_FLAG | OFF | +-----+------------+-----------+-------+
3. Next, list the jobs submitted by this user. Jobs with status NEW can be assigned manually by the administrator. In this example the user has submitted only 1 job.
user> .job10 +-----+--------------------+-------+---------+--------+-------+--------+-------------+-----------+ | NO. | CLIENTID | JOBID | P.JOBID | USERID | START | FINISH | TIME | STATUS | +-----+--------------------+-------+---------+--------+-------+--------+-------------+-----------+ | 1 | user1_123456789012 | 61 | 0 | user1 | 02:03 | | 03m:43s | NEW | +-----+--------------------+-------+---------+--------+-------+--------+-------------+-----------+
4. Assign the job to the Agent. In this example, the job is assigned to 1 InTime Agent.
admin> .job.assign=61
Proceed to assign job? ('y' for Yes or 'n' for No) [y]
admin.confirm> y
+--------+--------------------+--------+-----------------+------+---------+----------+--------------+----------+
| INDEX. | CLIENTID | USERID | LAST_HEARTBEAT | CORE | MEM[GB] | DISK[GB] | IP | HOSTNAME |
+--------+--------------------+--------+-----------------+------+---------+----------+--------------+----------+
| 1 | user1_123456789012 | user1 | 02:22 (00m:47s) | 2 | 2.9/3.9 | 20.0 | 10.10.10.1 | host12 |
| 2 | user2_123456789012 | user2 | 01:00 (00m:01s) | 2 | 2.9/3.9 | 20.0 | 10.10.10.2 | host13 |
+--------+--------------------+--------+-----------------+------+---------+----------+--------------+----------+
Enter worker INDEX numbers and/or ranges separated by commas.
For example, 1
admin.job.61> 1
5. Next, check if the InTime Agent has been assigned the job. In this example, the InTime Agent has accepted job 61.
admin> .status +-----+--------------------+-------+--------+--------+-------+--------+--------+-----------------+ | NO. | CLIENTID | JOBID | USERID | STATUS | ALIVE | B.LIST | MARKED | LAST_HEARTBEAT | +-----+--------------------+-------+--------+--------+-------+--------+--------+-----------------+ | 1 | user1_123456789012 | 61 | user1 | BUSY | YES | NO | NIL | 02:23 (01m:37s) | +-----+--------------------+-------+--------+--------+-------+--------+--------+-----------------+
Applies to:
- Linux Operating System
- Windows Operating System
Knowledge Base ID: 201809141 - Last Review: Sep 18, 2018 - Revision: 1.0