IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing business processes > Building BPEL processes > Create a BPEL process

Defining administration in a BPEL process

When you define administrative rights in a BPEL process, you involve human tasks and grant organizational control over some or all of the BPEL process to a select group of users.

This group of users will be able to interact with the process in the runtime environment through the Business Process Choreographer explorer, and will be able to exercise various levels of control. When we speak of administration in a BPEL process, we are actually talking about control over two different areas of the BPEL process.

Administration over the entire BPEL process

Those with administrative control over a BPEL process have the authority to terminate, suspend, resume, or delete an instance of that process.

Administration over an activity within the BPEL process

Administrative control can be granted over invoke, scope, collaboration scope and snippet activities. With the invoke activity, the administrative authority include the ability to handle faults that may arise, or to force retry or force complete long-running activities. For the collaboration scope and scope activities, the administrative duties include the authority to modify the execution order of the activities nested within the scope activity.


Procedure

  1. To configure administration on a BPEL process:

    1. Select the process as a whole by clicking any empty area on the canvas.

    2. In the Properties area, click the Administration tab.

    3. Create or configure a human task. You will have two options:

      Option Description
      An administrative task for the process Use this task to define the individuals or group that will have administrative rights for the process as a whole.
      A default activity administrative task This task would define the default administration settings for all of the activities within that process.

      For example, if a service call fails an activity may not be completed successfully, the user will need administrative rights to recover the process instance. Although these administrative rights can be given for each activity individually, an activity that does not have an administrator attached will need to be able to fall back to this default administrative task.

    4. Configure the administrators of the Human Task to be the group of people that should have administrative authority over the process. For instructions on how to work with the Human Task editor, see Human task editor, and The building blocks of the human task editor.
  2. To configure administration on an invoke, scope, collaboration scope or snippet activity:

    1. Drop an invoke, scope, collaboration scope or snippet activity onto the canvas.

    2. In the Properties area, click the Administration tab.

    3. Create or configure a human task. For the collaboration scope the administration task is automatically generated. The default setting gives administrative authority to Everybody, which will not be an appropriate setting in most cases.

    4. Configure the administrators of that human task to be the group of people that should have administrative authority over the activity. For instructions on how to work with the human task editor, see Human task editor, and The building blocks of the human task editor.

    Configure administration for an invoke, scope, collaboration scope or snippet activity overrides any default activity administrative task defined for this BPEL process. Other activities in the process will still use the default activity administrative task.

Create a BPEL process