The following terms identify MIMIX processes. Some, like the system manager, are required to allow MIMIX to function. Others, like procedures, are used only when invoked by users.
Replication path - A replication path is a series of processes used for replication that represent the critical path on which data to be replicated moves from its origin to its destination. MIMIX uses two replication paths to accommodate differences in how replication occurs for user journal and system journal entries. These paths operate with configurable levels of cooperation or can operate independently.
The user journal replication path captures changes to critical files and objects configured for replication through a user journal. When configuring this path, shipped defaults use the remote journaling function of the operating system to simplify sending data to the remote system. The changes are applied to the target system.
The system journal replication path handles replication of critical system objects (such as user profiles, program objects, or spooled files), integrated file system (IFS) objects, and document library object (DLOs) using the system journal. Information about the changes are sent to the target system where it is applied.
System manager - System manager processes automatically distribute configuration and status changes among systems in a MIMIX installation. Although often thought of as one entity per system, there are actually multiple system manager processes associated with each system. Each system manager process consists of a remote journal link (RJ Link) that transmits entries in one direction between a pair of systems and system manager processing jobs that apply the entries to MIMIX files on the remote system (or target side) of the RJ link. A high-priority processing job applies entries such as configuration and a low-priority processing job applies entries such as status.
Between each pair of communicating systems, there are always two system manager processes that transmit in opposite directions. In environments with more than two systems, MIMIX restricts which systems can communicate based on their designation as a management (*MGT) or network (*NET) system.
Journal manager - The journal manager is a job on each system that MIMIX uses to maintain the journaling environment on that system. By default, MIMIX performs both change management and delete management for journal receivers used by the replication process.
Collector services - A group of jobs that are necessary for MIMIX to track historical data and to support using the MIMIX portal application within the Assure Unified Interface. One or more collector service jobs collect and combine MIMIX status from all systems.
Cluster services - When configured for use in an IBM i clustering environment, MIMIX uses the cluster services function provided by IBM i to integrate the system management functions needed for clustering. Cluster services must be active in order for a cluster node to be recognized by the other nodes in the cluster. MIMIX integrates starting and stopping cluster services into status and commands for controlling processes that run at the system level.
Target journal inspection - A set of MIMIX processes that read journals on a system being used as the target system for replication. Each target journal inspection process identifies people or processes other than MIMIX that created, changed, or deleted replicated objects on the target system. The list of affected objects and any automatic recovery actions initiated by MIMIX can be displayed in the Objects Changed on Target window within the MIMIX portal application in the Assure Unified Interface. The window can be accessed from multiple portlets and is filtered accordingly.
Procedures and steps - Procedures and steps are a highly customizable means of performing operations. A set of default procedures is shipped with MIMIX for frequently used operations. These default procedures include the ability to start or end replication for an application group, perform pre-check activity for switching, perform a planned or unplanned switch of an application group, perform virtual switch testing, prepare MIMIX for running a backup, and run data protection reports for nodes. Each operation is performed by a procedure that consists of a sequence of steps and multiple jobs. Each step calls a predetermined step program to perform a specific sub-task of the larger operation. Steps also identify runtime attributes that determine how the procedure will start processing the step and how it will respond if the step ends in error.
Log space - A MIMIX object that provides an efficient storage and manipulation mechanism for replicated data that is temporarily stored on the target system during the receive and apply processes.