Opswise Message Service (OMS)

For Opswise Automation Center 5.2.0, Opswise Message Service (OMS) replaces the Message Hub and Transporter components of the 5.1.0 Outboard as the network communications provider between Opswise Controller and Opswise Universal Agent.

OMS uses similar, message-based communications protocol as the Message Hub and Transporter. It provides fault tolerant, reliable, secure messaging.

OMS is packaged as a component of Opswise Universal Agent, and it is installed and configured just like any other Opswise Universal Agent component.

Security

New Permissions

Added a Virtual resources permission.

Added a Variable permission.

Business Services

Added Member of Business Services to Virtual Resources.

Added Member of Business Services to User-Defined Variables.

New Properties

Added a Virtual Resources Security Enabled property.

Added a Variable Security Enabled property.

Workflow Improvements

Two new commands have been added - Force Finish (Halt) and Force Finish/Cancel (Halt) - that let you:

• Force finish task being monitored by a File Monitor task or FTP File Monitor task without completing the monitoring process.
• Force finish a task without releasing successor tasks in a workflow.

Force finishing a command that does not notify the task monitors would help in cases were you need to force finish the task but you don't want the task monitors to complete; for example, if the task was launched in error.

Force finishing a task without releasing successor tasks in a workflow would help in cases where a task instance - due to a number of possibilities - is stuck in Queued status, and you want to force finish and re-run the task without impacting workflow dependencies.

Trigger on Existence

Added a Trigger on Existence option to Create File Monitor type.

User Mode Install

For UNIX, you can now select the directories where everything gets installed.

Simulated Trigger

The Forecast Information screen indicates if the forecast information is for a simulated trigger.