Single step

A SingleStep is the direct link between a runprofile and a specific management agent. The two most important settings for a SingleStep are the management agent name and the runprofile name, without these settings the SingleStep is unable to process.

A SingleStep contains several settings:

General

Management Agent

This reflects the management agent name on the synchronization server. If the management agent is no longer available or the name has changed the SingleStep will fail the validation. This means that the entire sequencer run cannot start.

Note: The management agent list is populated from the synchronization system. Press the refresh button to refresh the entire management agent list.

RunProfile

The runprofile name is the profile name that will be executed when this SingleStep is started. the runprofile will not be validated during the validation process. When the runprofile differs or is no longer available the step result will be "no-start-unknown-profile-name", this error will only occur when the management agent is started (not in dummy run).

The runprofiles are the same runprofiles as you have configured for your management agent within the synchronization server.

Warning: When the IM Sequencer client is used on the synchronization server the drop down list contains the actual runprofiles for this management agent, when the IM Sequencer is connected remotely the runprofiles in the drop downlist are only predefined runprofiles, the runprofile names can differ for you management agents.

Pre processing

Before the step is started you can execute a script or application. This script or application can prepare a text file or inform a external system.

When the application or script is finished (and no error occurred) the Runprofile will be started.

You can press the "..." button to select the pre processing application or script.

Note: When you are using the IM Sequencer remotely the scripts or applications are executed on the computer where the IM Sequencer is currently running not on the remote synchronization Server.

Pre processing arguments

You can define witch arguments should be provided when starting the pre process application or script.
There are 2 arguments that are parsed witch it's actual value:

[AGENT_NAME] - the agent name
[RUN_PROFILE] - the runprofile that will be executed

Post processing

When the step is finished you can execute a script or application. This script or application can notify an external system or copy result files if necessary.
When the application or script is finished (and no error occurred) the step will continue.

You can press the "..." button to select the post processing application or script.

Note: When you are using the IM Sequencer remotely the scripts or applications are executed on the computer where the IM Sequencer is currently running not on the remote synchronization Server.

Post processing arguments

You can define witch arguments should be provided when starting the post process application or script.
There are 3 arguments that are parsed witch it's actual value:

[AGENT_NAME] - the agent name
[RUN_PROFILE] - the runprofile that will be executed

[RESULT] - the result text from the singlestep

Run even if no imported data is available to be synchronized

When there are no pending imports (add, modifies or deletes) within the specified management agent the step will not start the specified runprofile.

Note: Pending imports are only available after a delta or full import run by the management agent.

Run even if no export data is available to exported

When there are no pending exports (adds, modifies or deletes) within the specified management agent the step will not start the specified runprofile.

Note: Pending export are only available after a delta or full synchronization run by the management agent.

Enable custom filtering

When this option is enabled the IM Sequencer can receive messages from the Custom Filter Agents from the Traxion ILM Framework. The agent used log4net to transfer the messages to the IM Sequencer, more information can be found here.

Single step general settings

Thresholds

Thresholds can be set to protect your metaverse and connected systems. When a threshold is exceeded the run can be aborted and not export or import any information

Import threshold

The import threshold consists of tree separate settings (add, update and delete). The import threshold is checked at the end of each SingleStep.

You can set an absolute threshold value (ie. when 500 deletes are imported stop processing) or you can set a percentage (ie. when 5% of all objects are deleted stop processing)

When the threshold is exceeded the SingleStep will display a warning, depending on the settings the sequencer run can be aborted.

Export threshold

The export threshold consists of tree separate settings (add, update and delete). The export threshold is checked at the beginning of each SingleStep.

You can set an absolute threshold value (ie. when 500 deletes will be exported, stop processing) or you can set a percentage (ie. when 5% of all objects will be deleted, stop processing)

When the threshold is exceeded the SingleStep will display a warning, depending on the settings the sequencer run can be aborted.

Single step threshold settings

Advanced

Continue if this step exceeds the threshold

Indicates if the processing should continue to the next step if this step has exceeded the threshold, if not set the processing will continue, only a warning will be displayed in the report and the steps view.

Note: This only applies to steps that are started in synchronized run mode, when running in ASynchronize mode you need to apply the same setting in the parent MultiStep.

Continue if this step result is not success

Indicates if the processing should continue to the next step if this step result was not success, if not set the processing will continue, only a warning will be displayed in the report and the steps view.

Note: This only applies to steps that are started in synchronized run mode, when running in ASynchronize mode you need to apply the same setting in the parent MultiStep.

Wait minutes

The wait minutes will halt the sequential processing. This means when a step is finished the sequencer run will wait X minutes before the next step will be started.

Note: This setting only applies to steps that are started in synchronized run mode.

Enabled

If this step is disabled, it will not be started. The step will be reported with the status "disabled"

Note: When the parent step is disabled, this step is automatically disabled.

Single step advanced settings

You can find more detail information about how a SingleStep is being executed here.

See here for complete list that contains all Single step results.

Page url: http://www.traxionsolutions.com/imsequencer/help/index.html?create_or_edit_singlestep.htm