Specifies that cyclic start times of JS1 orders and schedules will be converted to the JS7 - Cycle Instruction.

Consider chapter Cyclic Workflows vs. Cyclic Orders.

The JS1 live folder includes a number of hidden sub-directories that should not be converted. Such directory names typically start with a dot as in .sos-templates, .configuration.

If more than one directory is specified then they have to be separated with a semicolon ";".

Specifies a number of paths in the JS1 live folder that should not be considered for conversion. Typically the live/sos folder holds housekeeping jobs that are not required for JS7.

If excluded paths are specified then this includes not to consider any sub-directories recursively. It is not required to specify individual sub-directories with the parserConfig.excludedDirectoryNames when using excluded paths.

Specifies the default time zone that is added to converted workflows. This time zone for example is applied to JS7 - Admission Times for Jobs.

See List of tz database time zones

Specifies the value of the log_level job argument of JS7 - Job Templates, see JS7 - JITL Common Variables.

Allowed values include: INFO, DEBUG, TRACE. If no log level is specified then JVM Jobs behave as if no log_level job argument is used.

Specifies the number of parallel tasks that a job can be running for, see JS7 - Job Instruction.

JS7 workflows can be operated in a JS1 compatibility mode. If set to true then

• for order variables and workflow variables in shell jobs respective environment variables are created that are prefixed with SCHEDULER_PARAM_ followed by the uppercase variable name.
• for job arguments of shell jobs accordingly environment variables are created.

Consider that environment variables are not added by the Converter but are created on-the-fly by the Controller and Agents.

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 jobs with 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.

Mock levels are used for dry runs of the conversion for JS7 - Job Templates (JITL JVM Jobs). If a mock level is specified then JVM Jobs will not be executed but will log and will optionally check arguments only.

The following values can be specified for this setting:

• INFO: arguments are logged, execution of JVM Jobs is considered successful.
• ERROR: arguments are logged, required arguments of JVM Jobs are checked and errors are raised in case of missing arguments.

Without this setting being specified the JITL JVM Jobs will be executed from the converted jobs.

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 

Specifies the folder where the calendars are generated.

Example:

calendarConfig.forcedFolder = Calendars

This refers to a situation where there is only a JSON definition available for a job stream.

Note: the converter should be restarted if the JS1 <job name>.job.xml files have been created.