User Guide > UserInterface > System Overview > Quarantine

 Quarantine

Internal messages control processing based on objects and their settings. Thus, checking their contents is of high importance.

Invalid messages which cancel a server processThe core of the component Automation Engine. Different types are available: communication, work and dialog processes, as well as nonstop processes. are intercepted and displayed in this area of the System OverviewThe UserInterface window that contains information about the Automation Engine system.. Your AE system is therefore protected since these messages do not affect the server processes.

Contact Automic Support; these messages are helpful for further analyses.

By default, the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. checks internal messages. On UNIX, this can have a negative impact on performance. The administrator can deactivate this functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… with the parameter exception= in the Automation Engine's INI file.

Column

Description

Message number

Number of the message

Status symbol

Status of the message

"1" - May be released after prior contact with Automic Support
"2" - Has been logged for analysis reasons but cannot be released
"3" - Has successfully been processed and can be deleted

Occurrence time

Time when the message was quarantined

Reason for failure

Additional information about the failure reason

Replays

Number of releaseReleases combine a set of activities and a set of packages as well as other release artifacts under a timeline (a plan including milestones and phases), which can be planned, baselined and tracked. attempts

XML Stream

Message sections (if retrievable) for analysis

Reaction to Invalid Messages

The following steps are initiated if an invalid message has been detected:

  1. The message is put into quarantine.
  2. All databaseA database is an organized collection of data including relevant data structures. modifications made by this message are canceled.
  3. Further message information is written to the Automation Engine's log file.
  4. A trace file of the following name is created:

    UC4Dump_name of the Server process_RunIDShort for "run number". It is a number that provides unique information about a task's execution. The RunID can include 7 to 10 digits. It is assigned by the Automation Engine component ._time stamp.txt

    Example:
    c:\AUTOMIC\server\temp\UC4Dump_UC2T#WP002_40373135_20060406144901543.txt
  5. A dump is created if possible.
  6. The ServiceManagerA program that facilitates the starts and stops of Automation Engine components. restarts the aborted server process.
  7. If the administrator has defined the key EXECUTE_ON_EXCEPTION in the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_SYSTEM_SETTINGS, the specified objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task starts.

The UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."] displays the symbol to authorized users if there are quarantine messages.

 This area of the System Overview and the symbol in the UserInterface are only displayed when the User object or user groupA group of users who have a common profile of rights. A particular object type in the Automation Engine. User groups are an organizing construct to help you better manage users because you can grant user groups access rights the same way that you grant various access rights to a single user. All users in the user group are automatically given those access rights. This makes managing users not only more efficient but also more secure because working with user groups gives you a better overview of what rights are assigned. has the privilege "Create diagnostic information" and a modification right for server processes. Obtain further information from your administrator.

Releasing Messages

Only release messages upon prior contact with Automic Support.

Highlight the message and open the context menu command "Release". A dialog opens in which trace options can be set. Select the server process to be used for reprocessing the message.

Only the primary work processIt is responsible for the execution of Automation Engine-internal tasks and work processes. executes PWP messages.

Specified trace options are deactivated after the execution attempt. If the message could be processed without failure, it remains in the listShows entities in a grid view but can be deleted with a context menu command.

Context Menu

The following actions are possible:

Command

Description

Receipt

Flags the message as noted

The alarm statusThis represents the condition of a task (such as active, blocked, generating). shown at the upper right edge of the UserInterface is no longer shown when all invalid messages have been noted.

Delete

Removes a message from the list which could be reprocessed without failure

Release

Releases a taskAn executable object that is running. Tasks are also referred to as activities. which can then be reprocessed

Show message

Shows the message's internal technical information

 

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH