Administration Console > Catalog, Reports, and Custom Faults > Viewing Process Definitions
  

Viewing Process Definitions

The Process Definitions page lists all business processes that were deployed to the server. For each, basic process version information is displayed, as shown in the following figure and table.
Process Definitions page
Item
Description
Name
Local part of the process qualified name (qname)
Active Ver.
Version that process instances can attach to or can run to completion. Normally the active version is the current version. However, if the current version reached its expiration date, active processes can run to completion based on the offline pending (expired) version.
Versions
Number of deployed versions stored in the database
Online Pending Ver.
Yes-no field indicating whether a process version has an effective date set to a future date
Group
Group this process belongs to, as added in the PDD file.
Tenant
In a multitenant system, the tenant associated with the process definition.
Process versions can be in one of the following states:
Select a process to display the Deployed Process Version Detail page. For additional information, see Deployed Process Detail Graph and Process Version Life Cycles.
Selection Filters
You can select the following Selection Filters to view a subset of processes:

Deployed Process Detail

This page displays a list of all deployed versions of a process. Actions you can perform are as follows:
The Deployed Process Detail page shows a list of all deployed versions of a process. For details, see Process Version Life Cycles.
Clicking on links within this page tells Process Server to display its page.
Deployed Process Detail
Property
Description
Version
The version number is automatically incremented when a new process version is deployed, unless a version number is specified in the deployment descriptor. The format of the number is N.nn, where N is major and nn is minor.
Plan Id
Id assigned to this version and associated disposition of running processes
Online Date
If an online (effective) date was not specified in the deployment descriptor, the online date is the same as the deployed date. A process is online immediately when deployed, unless an online date is specified.
Offline Date
A process version does not have an offline (expiration) date unless one is specified in the deployment descriptor. By default, a process version automatically goes offline when a newer version comes online.
Deployed Date
Date the process is added to the engine database
Processes
Number of active process instances
Migrated To
Process version that this version migrates to
Status
Online, Online Pending, Offline, Offline Pending

Deployed Process Version Detail

The Deployed Process Version Detail page displays all the details from the process deployment descriptor as well as the process definition. Here's part of this page.
Deployed Process Version Detail
The sections of this page are described in the following topics:
The Deployed Process Version Detail page also shows endpoint reference details and other related details:
Role
Explanation
My Role
My Role partner link endpoint reference details are generated from information in the deployment descriptor. Rest your mouse on the partner link type to view the associated namespace. Select the Service Name link to view the WSDL file for the Web Service exposed by the partner link. . Select View in the Policy column to view any attached policy assertions. See the Process Developer help for information on policy assertions.
Partner Role
Partner Role partner link endpoint reference details are generated from information in the deployment descriptor. Rest your mouse on the partner link type to view the associated namespace. Select a static endpoint type from the Linkage column to view the endpoint definition.
Indexed Properties
Indexed Properties, if any, are displayed.
Logical People Groups
Logical People Groups, if any, are displayed. A Logical People Group is a group of users defined in a human tasks activity. The group consists of identities in the enabled Identity Service. Select a static type from the Linkage column to view the organizational entity definition of the Logical People Group. Select a people query from the Linkage column to view the selection criteria defined for retrieving identities from the enabled Identity Service. For details on people queries, see the Process Developer topics of this help.
Event Filters
Event Filters, if any, are displayed. An event filter specifies process events that are passed to the Event Manager for processing. Event services, deployed to the Catalog, act upon the events.
Resource Usage
Resource Usage shows WSDL, schema, and other files and their target namespace referenced in this process. Select a Resource to view the resource definition.
 

Understanding Process Version Life Cycles

Process versioning allows different versions a process to exist in Process Server. Process versioning allows you to control when processes become effective and for how long. You can also control what happens to processes created by older versions when a new version becomes effective. While multiple versions of a process can exist concurrently, only the latest effective version is capable of creating new process instances.
The latest effective version is in an online state. Other states are:
The process deployment descriptor (PDD) can contain a version element whose attributes describw how a deployment is versioned. These selections are all optional and have default values as described below.
The following example shows the syntax for version information in the .pdd file.
<version effectiveDate="2005-12-12T00:00:00-05:00"
expirationDate="2007-12-12T00:00:00-05:00"
id="1.5"
runningProcessDisposition="migrate"/>
where:

Updating a Process Version

You can view this property on the Deployed Process Version Detail page.
The options for updating a process version are:

Setting a Process Version Offline or Online

You can view this property on the Deployed Process Version Detail page.
The options for setting a process version offline or online are:

Setting the Logging Level

You can set this property on the Deployed Process Version Detail page.
For a more details, see description, see Logging Properties in the Administer section .
You can view or download an execution log for a running or completed process. An execution log provides start and end times for activity execution and helps you troubleshoot faulted processes. The following list describes the different logging levels:
To improve processing speed, perform no logging or minimum logging. Informatica recommends that you use the None or Terse logging levels.

Setting the Process Version Persistence Type

You can set this property on the Deployed Process Version Detail page.
Persistence refers to storage of active processes. By default, when a process runs on the server, all state and variable data is stored in the Process Server database. However, this setting can be changed in the PDD file to increase server performance and reduce database size.
Persistence setting selections are as follows:
Setting
Explanation
Full (default)
For each process instance, all running, faulted, and completed state information is stored. In the event of a server failure, a running process can be fully recovered. The recovery is possible because this setting tells Process Server to maintain a journal (a record of the changes intended for the database).
Note: If the process uses a WS-RM invoke handler for a partner role or a WS-Reliable Messaging policy assertion on a my role, full persistence is required.
Persist
Same storage setting as Full, but without journaling. If processes are running and the server fails, processes are suspended.
The process is recoverable if the system goes down, but needs to be looked at since no journaling was done. This process is marked as suspended.
Final
Stores only the final state of the process (completed or faulted) and process variables. On a server failure, a running process is terminated. This setting makes fewer database writes than the previous two settings, but still allows you to view a graph of the process on the Active Processes Detail page in the Process Console. Here, you can see the execution path and final values of process variables. A process runs only in memory, and the Server Property called Process Idle Timeout has no effect on this persistence level.
Brief
This is the minimum level for process logging. Process Server stores only the start and completion times and the final state (completed or faulted). Also, it stores state and process variables only if the process faults. A process runs only in memory, and the Server Property called Process Idle Timeout has no effect on this persistence level.
None
No process information is stored in the server database when a process terminates. The process instance is not listed in the Process Console’s Active Processes page.

Exception Management Type

You can view this property on the Deployed Process Version Detail page.
According to the WS-BPEL 2.0 specification, a process with an uncaught fault terminates.
On the Server Properties page, you can enable an option to suspend all processes on an uncaught fault to put them in a suspended-faulting state. You can then perform process exception management on the faulting process, followed by retrying or completing the faulting activity or scope.
An individual process can override the engine setting with an entry in the Process Deployment Descriptor (PDD) file. The settings are:
Field
Explanation
System Default
The current engine setting for all processes. The default engine setting is to disable suspension on uncaught fault; however, the current setting may be different.
False
Do not allow this process to suspend on an uncaught fault. The process will terminate abnormally. This setting overrides the engine setting.
True
Suspend this process on an uncaught fault to put it in a suspended-faulting state. You can then perform process exception management on the faulting process, followed by retrying or completing the faulting activity or scope. This setting overrides the engine setting.
See Process Exception Management.

Invoke Recovery Type

You can view this property on the Deployed Process Version Detail page.
For invoke activities that do not complete because of a node failure, you can suspend the process upon recovery. The process is suspended at the pending invoke, and you can perform process exception management.
An individual process can override the engine setting with an entry in the Process Deployment Descriptor (PDD) file. The settings are:
Setting
Explanation
System Default
The current engine setting for all processes. The default engine setting is to disable invoke recovery; however, the current setting may be different.
False
Do not allow a pending invoke activity to suspend upon recovery. The process will terminate abnormally. This setting overrides the engine setting.
True
Suspend a pending invoke on recovery to put it in a suspended-faulting state. You can then perform process exception management on the invoke activity, followed by retrying or completing the faulting activity or scope. This setting overrides the engine setting.

Process Instance Retention

You can view this property on the page.
You can specify how long to keep completed and faulted processes in the Process Server database before deleting them on an automated schedule. This setting is available in the following locations:
The retention setting applies to a process version with a status of online or online pending, not to offline pending or offline versions. The schedule begins on the Completed or Faulted date of each process, as shown on the Active Processes page. For example, if a process instance completes on December 31, and the Retention setting is 30 days, the process instance is deleted from the database on the next scheduled deletion after January 30.
To Set Retention for an Individual Process
  1. 1. In the Process Console, select Catalog > Process Definitions.
  2. 2. Select a deployed process from the list.
  3. 3. If multiple versions exist, from the Deployed Process Detail page, select an online or online pending version to open the page.
  4. 4. In the Process Instance Retention field, specify a number of retention days, hours, or minutes for the process version.
  5. 5. Select Update. The effect is immediate for all completed and faulted processes.
For details about scheduled database maintenance, see Storage.

Deployed Process Detail Graph

The Deployed Process Detail Graph page presents many details about a process instance:
The following illustration shows an example of the Deployed Process Details page.
Deployed Process Details graph