![]() ![]() ![]() ![]() ![]() ![]() ![]() |
This chapter presents an overview of the Process Configuration and Process Instance Monitoring modules of the WebLogic Server Process Edition Administration Console.
You use the Process Configuration module to:
Note: | You must be logged in as a member of the Administrators, IntegrationAdministrators, or IntegrationOperators group to make changes to the configuration for a process or dynamic control. IntegrationOperators cannot modify process security policies. For more information, see About WebLogic Integration Users, Groups, Roles, and Security Policies in User Management in the Worklist Console Online Help. |
You use the Process Instance Monitoring module to:
The following sections provide more information on the Process Configuration and Process Instance Monitoring modules:
You must be logged in as a member of the Administrators, IntegrationAdministrators, or IntegrationOperators group to make changes to the configuration for a process or dynamic control. IntegrationOperators cannot modify process security policies.
The following sections provide an overview of information related to business process administration:
The data generated as process instances execute is initially stored in the run-time database. The monitoring information provided in the console is based on this data. In order to optimize performance, it is important to keep the amount of tracking data stored in the run-time database to a minimum. This is accomplished by:
A combination of system and process properties control the management of tracking data.
For more information, see “Managing Process Tracking Data” under “About Process Configuration” in Process Configuration in Using the WebLogic Integration Administration Console.
To ensure process security, the administrator can configure the following security policies for a process:
The execution policy specifies whether the operations in the process are run as the start user or the caller's ID:
In addition, the administrator configures whether or not a single principal is required. If a single principal is required, then all incoming client requests must come from the same user.
Execution policy controls the identity used to access external or backend resources. It allows the administrator to specify whether a process accesses an external system as the invoking application or as an application that called into the process later. For example, suppose a process listens for a message on a channel and then waits for a client request. The administrator can set the execution policy to use the identity from the client request when the process subsequently accesses SAP.
The role(s) authorized to invoke the process methods (client requests). All methods in the process inherit the role(s) specified in the process authorization policy.
Note: | If the process authorization policy is not defined, everyone is authorized. |
The role(s) authorized to invoke the process methods (client requests). All methods inherit the role(s) specified in the process authorization policy. Additional roles can be added to the authorization policy for the method.
To learn how to set the security policies, see “Updating Security Policies” in Process Configuration in Using the WebLogic Integration Administration Console.
A service level agreement (SLA) specifies a performance target for a process. It is typically an internal or external commitment that a process will be executed within a specified period of time.
To assist you in achieving the SLA for a process, the WebLogic Server Process Edition Administration Console allows you to set the following thresholds:
Process status relative to these thresholds is tracked for each process instance as follows:
This ability to set SLA thresholds allows you to easily identify processes that do not execute within the target time frame. You can then make the changes necessary to meet agreements between suppliers and customers, or to achieve your own performance goals. To learn how to set the SLA for a process, see “Viewing and Changing Process Details” under “About Process Configuration” in Process Configuration in Using the WebLogic Integration Administration Console.
When developers need to modify a deployed process, they must create a new process version and then release it into production along with older versions. When multiple versions are deployed, the system determines which version to use when creating new instances. The administrator controls the release of a process version by:
When creating a new instance, the system selects the version with the most recent activation time from among the enabled versions. (A disabled version is not available for selection.)
When an administrator activates a process by setting its activation time, instances currently running are not affected. Only instances that are created after the new version becomes active are created based on the new version.
If a newly activated version experiences problems, a rollback is easily accomplished by doing one of the following:
To learn more about how to enable or disable a version, or to configure the activation time, see “Managing Process Versions” in Process Configuration in Using the WebLogic Integration Administration Console.
Dynamic controls, which currently include the Service Broker and Process controls, provide the means to dynamically set control attributes through a combination of look-up rules and look-up values. This process is known as dynamic binding. In dynamic binding, the process developer specifies look-up rules, and the administrator defines the look-up values. This design pattern allows control attributes to be reconfigured for a running application, without redeployment.
The look-up or selector values are stored in the DynamicProperties.xml
file, which is located in the wliconfig
subdirectory of the domain root. You can manage the values stored in the DynamicProperties.xml
file from the View Dynamic Control Properties page of the Process Configuration module.
Dynamic binding changes made in the WebLogic Server Process Edition Administration Console override both configuration changes made in the Workshop development environment and static annotations.
For more information about Dynamic Controls, see Process Configuration in Using the WebLogic Integration Administration Console.
The information displayed in the Process Monitoring module is based on the tracking data stored in the run time database. A combination of system-level and process-level properties control the capture and archiving of data. To learn more about how tracking data is managed, see “Managing Process Tracking Data” in Process Instance Monitoring in Using the WebLogic Integration Administration Console.
The following table lists the pages you can access from the Process Instance Monitoring module. The tasks associated with each page are detailed.
For more information, see Process Instance Monitoring in Using the WebLogic Integration Administration Console.
![]() ![]() ![]() |