Sun Microsystems 3 manual Monitoring and Managing Two-Phase Commit Transactions

Managing Process Execution with Conductor Script

Command	Arguments	Function	See…
ShowActivityQueue	process_name,	Display the contents of the specified	page 305
	[queue_name]	queue (or all queues) for the specified
		process in the current engine.
ShowProcess	process_id	Show details of specified process	page 307
		instance, including all activities and the
		values of all process attributes.
ShowTimer	process_id	Show details of the specified timer.	page 313
	timer_name

StartActivity process_id, activity_name session_id

Change the state of the specified activity page 314 from READY to ACTIVE.

StartTimer	process_id	Start the specified timer. Place it in the	page 317
	timer_name	ON state.
StopTimer	process_id	Stop the specified timer. Place it in the	page 319
	timer_name	OFF state.

Monitoring and Managing Two-Phase Commit Transactions

The iIS two-phase commit protocol facilitates the synchronization of iIS process engine operations with application transactions by making it possible to place iIS engine operations in a transactional context. For information on this capability, see “Monitoring and Managing Two-Phase Commit” on page 199.

As a system manager, you can monitor and manage these iIS transactions, as described in the following sections.

Monitoring Two-Phase Commit Operations

You can use Conductor Script commands to monitor the status of in-progress iIS engine operations, as indicated in the table below. These commands print out the transaction ID of any iIS operations that are in a PREPARE phase.

Command	Arguments	Function	See…
ShowActivity	process_id	Indicates any in-progress two-phase	page 304
	activity_id	commit transactions in the activity.

258 iPlanet Integration Server • Process System Guide • August 2001