Copyright © Cloud Software Group, Inc. All Rights Reserved

View Service Instance Dialog

The following tabs are available:

•	General Tab

•	BW Processes

•	Tracing Tab

•	Graceful Shutdown Tab

General Tab

General

Displays the following information about a process engine or service instance:

•	Uptime for this component.

•	Process ID for this component.

•	Name of the process.

•	Status of the component. If stopped, click start to start it. If running, click stop to stop it.

•	Name of the machine on which this process engine or service instance is running.

•	Name of the fault tolerant group, if any, to which this component belongs.

Statistics

This pane only displays for process engines.

•	Created Processes — The processes created by the process engine.

•	Suspended Processes — The processes currently suspended.

•	Swapped Processes — The total number of times processes were swapped up to current.

•	Queued Processes — The processes currently queued.

•	Aborted Processes — The processes that were aborted.

•	Completed Processes — The processes that were completed.

•	Checkpointed Processes — The processes currently checkpointed.

•	Total Execution (ms) — Total execution time for all processes. This refers to the total time the process was executing but does not include any wait times.

•	Average Execution (ms) — Average duration for execution of a process.

Active Alerts

Displays information about the active alerts for this component.

•	Date/Time — The date and time at which the alert occurred.

•	Alert Level — The alert level set when the alert was created.

•	Text — Description defined when creating the alert.

BW Processes

This tab displays only for process engines.

Select Active Processes, Process Starters, Process Definitions, Locks, Recoverable Processes, or Blocked Resources.

Active Processes

Displays active process engines. As a rule, this includes process engines that are suspended or waiting. Examples include process engines that contain a Wait activity and are waiting in a loop. All other process engines usually complete before TIBCO Administrator is updated by auto-refresh and are therefore not displayed.

•	Add Search Condition — You can add one or more search condition to narrow the display.

•	Export — Click to export information about the selected process engine to a comma-separated file.

•	Kill — Stops the selected process engine.

•	Suspend — Suspends the selected process engine.

•	Resume — Resumes the selected suspended process engine.

Statistic	Description
Process ID	ID of the running process instance.
Status	Status of the process.
Tracking ID	Tracking ID for the process instance.
Custom ID	Custom ID for the process instance.
Start Time	Time when the process instance started.
Duration (ms)	Elapsed clock time (in milliseconds) since the process instance started.
Process Defn	Name of the process definition.
Current Activity	Name of the currently executing activity in the process instance.
Starter	Name of the process starter that started this process instance.

Process Starters

Displays all process starters in the process engine. You can then select individual process starters and enable or disable them. This can be useful, for example, if you wish to understand the performance impact of one of the process engines.

Process Definitions

Use the search field to limit the display. The * character can be used as a wildcard. Click a process engine to display the process definition details. The following information is displayed.

•	Name — Activity for which throughput is displayed.

•	Called Process — This field only shows information if you’re running a process engine called by another process engine.

•	Execution Count — Number of jobs in which this activity is currently participating.

•	Elapsed Time (ms) — Average time this activity took to complete.

•	CPU time (ms) — CPU time used by this activity.

•	Errors — Number of errors encountered for this activity.

•	Status — Activity status.

•	Function — Name of the activity resource.

•	details — Click details for more detailed information about this particular activity.

Locks

Lock object shared configuration resources are used by Critical Section groups to ensure that only one process engine executes the activities within a Critical Section group at a time. The lock name, wait position, process id and requestor display. You can export lock information to a comma separated file, or kill a lock, if necessary. See the TIBCO ActiveMatrix BusinessWorks Process Design Guide for more information.

Recoverable Processes

Recoverable processes are process instances that have been checkpointed but not restarted. The Recoverable Processes option allows you to manage recoverable processes and either restart or remove them. See Managing Recoverable Process Instances for more information.

Blocked Resources

A process instance can become blocked when resources that it depends upon are unavailable and TIBCO Enterprise Management Advisor blocks their use. For example, a process instance my require a database connection. This option allows you to resume a blocked process instance once the resource becomes available. See Using TIBCO Enterprise Management Advisor for more information.

Tracing Tab

Allows you to view the trace logs for this application. You can create one or more search conditions to narrow the search scope.

To see the default log, leave Where File is <project.component>.log and click Search.

The log may grow quite large, and you are therefore encouraged to add one or more a search conditions before you click Search. The number of lines displayed is governed by tibcoadmin.monitor.traceLogMaxLines in tibcoadmin_<domain>.tra and defaults to 1000.

Graceful Shutdown Tab

Edit

Click to change the parameters under this tab.

Kill Jobs Timeout

Kill Jobs Timeout specifies the maximum timeout in seconds the process engine will wait for jobs to finish before shutting down the engine. A zero (0) value means 0 seconds, which effectively turns the graceful shutdown into an immediate shutdown.

Wait for Checkpoint

When selected, causes the process engine to wait for all jobs to finish (up to the maximum timeout) before shutting down the engine, rather than removing jobs at their next checkpoint.

 

Copyright © Cloud Software Group, Inc. All Rights Reserved