Enterprise Platforms: Autosys and iPE

In TIBCO's iProcess architecture, Integration maps to EAI Plug-Ins and BusinessWorks (both integration technologies), Modeling maps to Business Studio, but iProcess Decisions is a business rules/decision management module - not an integration tool. Therefore C is the incorrect mapping.

The BPM lifecycle phases map to specific iProcess Enterprise modules: Execution (iPE Engine runs processes), Definition (Process Definer creates models), Monitoring (Process Administrator tracks operations), Integration (Process Objects/EAI Plug-Ins connect external systems), and Presentation (Windows Client provides UI). Option B correctly sequences these modules.

In iProcess workflow systems, an addressee (recipient of work items) can be a User, a Group (team/role), or a Field (dynamic value determined at runtime). Option D correctly captures that all three types are valid addressee specifications depending on the workflow design.

TIBCO iProcess Engine supports multiple major database platforms. While Oracle is common in enterprise deployments, iProcess also supports Microsoft SQL Server and IBM DB2, giving organizations flexibility in their database choice. Options A, B, and C are all incorrect because they artificially limit the supported platforms.

RPC stands for Remote Procedure Call, a protocol where one program can execute a procedure/function on another computer across a network. It's about calling procedures (functions), not processes (running programs). The 'C' option correctly identifies the full form.

A node cluster architecture in iProcess involves multiple iProcess Engine server instances (nodes) sharing a single database instance. This allows for load balancing and high availability across multiple physical or virtual servers.

Process Sentinels in iProcess provide comprehensive process management: they ensure proper startup sequence, monitor process health and restart failed processes, and detect error/warning entries to trigger appropriate actions. All three functions are core responsibilities, making 'All of these' the correct answer.

The statement 'Not all data is held in the database & hence we need to stop engine for back-up' is FALSE because iProcess Engine stores all persistent data in the database and supports online/hot backup without requiring engine shutdown. Options A, B, and D describe true iProcess capabilities (event-driven deadline recalculation, EAI retry feedback, and Oracle RAC support).

In TIBCO iProcess Engine (iPE), the Process Sentinels (Worker and Watcher) are responsible for monitoring the health of the engine processes and automatically restarting them if they fail, providing 24/7 self-healing capability.

MoveSysInfo in iProcess is used to synchronize metadata changes (users, roles, lists, procedures) from the temporary staging area to the live working data area. These changes don't take effect until MoveSysInfo is run. Options A and C are incorrect because MoveSysInfo is for metadata (not hardware config) and can be run via GUI tools, not just command line.

ABAP (Advanced Business Application Programming) is SAP's proprietary programming language, designed specifically for developing business applications within the SAP ecosystem. R/3 is SAP's ERP product name, NetWeaver is their technology platform, and Java is a general-purpose language not owned by SAP.

The command 'chk_auto_up' in Autosys is used to verify that both the event processor and the database are operational. This is a diagnostic command that checks the health of critical Autosys components before job processing.

To set a global variable in Autosys, use 'sendevent -E SET_GLOBAL -G' with the variable assignment. Option A correctly sets the variable 'today' to '12/25/2005'. The SET_GLOBAL event type with -G flag is the proper syntax for creating global variables that persist across job runs.

The 'eventor' command is the correct Autosys command to start the event processor. The event processor is the core component that reads the job definition tables and schedules/executes jobs based on their dependencies and time conditions.

To delete a global variable in AutoSys, use sendevent -E SET_GLOBAL with the variable name set to DELETE. Option A incorrectly uses DELETE_GLOBAL which is not a valid event. Option B sets the variable to NULL rather than deleting it. Option D has invalid syntax.

autosys_secure is the AutoSys utility command for security management tasks like editing superusers, changing database passwords, and modifying authentication methods. Options A, C, and D are not valid AutoSys commands.

autoflags -a displays AutoSys version information along with other system flags and configuration details. Options A, C, and D are different AutoSys utilities used for different purposes - not for version retrieval.

JIL stands for Job Instruction Language. It is a scripting language used by CA Workload Automation (AutoSys) to define and manage job scheduling, dependencies, and attributes within the scheduling database.

To answer this question, the user needs to have a basic understanding of Autosys job status. Autosys is a job scheduling tool that allows users to automate and schedule jobs. There are many job statuses in Autosys, including RUNNING, STARTING, SHUTDOWN, and RESTART.

Now, let's go through each option and explain if it is a valid Autosys job status or not:

A. RUNNING: This is a valid Autosys job status. It indicates that the job is currently running.

B. STARTING: This is a valid Autosys job status. It indicates that the job is starting up.

C. SHUTDOWN: This is a valid Autosys job status. It indicates that the job is shutting down.

D. RESTART: This is a valid Autosys job status. It indicates that the job is restarting.

Therefore, all of the given options are valid Autosys job status.

The Answer is: C

sendevent -E CHANGE_STATUS -s SUCCESS -J is the correct syntax to force an AutoSys job to SUCCESS status. Option A is incomplete and missing the event type. Options C and D use incorrect event names - UPDATE_STATUS and STATUS don't exist.