Page History

Forces use of the given Agent for all converted jobs.

Agent definition:

• Expects a JSON value.
• The JSON can be provided as:
  • JSON text
    or
  • JSON include file (relative to the properties file)
• JSON elements:

  • Name	Default	Explanation
    platform	UNIX	Forces use of the UNIX or WINDOWS platform.
    subagentClusterId		Forces use the given subagentClusterId for converted jobs when an agentCluster is used.
    standaloneAgent		See agent-schema.json.
    agentCluster		See clusterAgent-schema.json.

• Examples:
  • {"platform":"UNIX"}
    • Forces use of the UNIX platform for all converted jobs.
  •  {"standaloneAgent":{"url":"http://localhost:4445"}}
    • Forces use of the standalone Agents in all converted jobs with the given url.
  •  {"platform":"UNIX", "standaloneAgent":{"agentName":"forced_agent", "url":"http://localhost:4445"}}
    • Forces use of a standalone Agent forced_agent in all converted jobswith the given url.

Without an Agent being specified the JS1 executes jobs with the Master. In JS7 an Agent has to be used. This setting specifies an Agent that is used for jobs that are executed with a Master in JS1.

The syntax for assignments: see agentConfig.forcedAgent Agent definition.

By default the Converter handles the mapping of Agent Names found in JS1 process classes (<process_class>) like this:

• Agents are determined by the unique URL assigned the Agent in existing process classes.
• The name of a process class is mapped
  • to a Standalone Agent if it includes a single Agent
  • to a Cluster Agent if it includes more than one Agent

The syntax for mapping includes:

<js1-agent-name>=<Agent definition>

<js1-agent-name> is the name of the JS1 Agent.
<Agent definition> see agentConfig.forcedAgent Agent definition..

Example:

js1_agent1={"platform":"UNIX", "standaloneAgent":{"agentName":"primaryAgent", "url":"http://unix:4445"}};js1_agent2={"platform":"WINDOWS", "standaloneAgent":{"agentName":"secondaryAgent", "url":"http://win:4445"}}

• The process class js1_agent1 is mapped to the JS7 Agent with the name primaryAgent that is operated for Unix.
• The process class js1_agent2 is mapped to the JS7 Agent with the name secondaryAgent that is operated for Windows.

or

 js1_agent1=examples/agent_standalone.json; js1_agent2=examples/cluster_agent.json

• The process class js1_agent1 is mapped to the JS7 Agent defined in the examples/agent_standalone.json file.
• The process class js1_agent2 is mapped to the JS7 Agent defined in the examples/cluster_agent.json file.

Any number of mappings are specified separated by a semicolon. This setting can be split across a number of lines by use the "\" line continuation character at the end of each line that should be continued.

With the JS1 a schedule optionally specifies a time zone. With the JS7 a time zone is required for scheduled. This setting specifies the default time zone that is applied if a JS1 schedule does not specify a time zone.

See List of tz database time zones