1. From the Process Tracking tab page, select a process instance.

   The details of that instance appear.

2. From the Actions list, select Alter Flow and Suspend.

   If you select a single process instance, then the Alter Flow dialog box appears as shown in the example in Figure 11-1.

   Figure 11-1 Altering the Flow of a Process Instance

   
   Description of "Figure 11-1 Altering the Flow of a Process Instance"

   By default, the Alter Flow dialog box shows only the Process and Project data attributes. When you select one of the open activities, it shows the data objects within the context of that open activity. For example, if the open activity is a subprocess, then the Alter Flow dialog box displays any subprocess level data objects.

3. In the Alter Flow dialog box, you can do any or all of the following:

   • View the list of current activities in a running process instance in the Open Activities table.

     You can select the new activity where you want to move the token. Note that the New Activity list includes only those locations to which a token can be moved validly.

   • Include the correlation keys in the list of data objects as shown in Figure 11-1. The correlation keys are visible only if the process is using correlation.

     To do this, select Show correlation key. If you select a correlation key, then the details section shows the correlation property that comprises the key. To reset the correlation key, select Reset correlation key.

     For information about correlation keys, see Oracle Fusion Middleware Developing Business Processes with Oracle Business Process Management Studio.

   • Include process instance attributes in the list of data objects as shown in Figure 11-1.

     To do this, select Show instance attributes. To display the details of a particular instance attribute, select the attribute. Note that only those instance attributes that can be modified appear as editable. Others are read-only.

   • Add any comments in the Comments field.

4. Click one of the following:

   • Resume to move the token to another activity and return the process to a running state.

   • Save to suspend the process instance. You can return to it later to alter its flow and resume it.

   • Cancel to return the process instance to its last saved state. The process continues in the running state.

1. Select one or more process instances. From the Actions list, select Migrate.

   The Migrate dialog box appears. The elements in this dialog box depend on your selection. If you select Migrate as is, then only the Comments field is available. If you select a single instance and then select Make changes and migrate, then the Migrate dialog box appears as shown in Figure 11-2.

   Figure 11-2 Migrating a Process Instance

   
   Description of "Figure 11-2 Migrating a Process Instance"

   If you select Make changes and migrate, you can do any or all of the following:

   • In the Open Activities table, you can view the activities where the token is currently running, and you can select the new activity where you want to move the token.

     Note that the New Activity list includes only those locations to which a token can be moved validly.

     Note:

     • For a pending migration instance to resume, all removed activity tokens must be moved to new activities.

     • If you select more than one activity from the Open Activities table, then the Data Objects tab does not appear, and you are not able to modify the payloads.

   • Include the correlation keys in the list of data objects.

     To do this, select Show correlation keys, then, in the Data Objects tab, select Show as tree and expand the data object. If you select a correlation key, then the details section shows the correlation property that comprises the key. To reset the correlation key, select Reset.

     For information about correlation keys, see Oracle Fusion Middleware Developing Business Processes with Oracle Business Process Management Studio.

   • Include process instance attributes in the list of data objects.

     To do this, select Show instance attributes, then, in the Data Objects tab, select Show as tree, then expand the data object, then expand Instance Attributes. To display the details of a particular instance attribute, select the attribute. Note that only those instance attributes that can be modified appear as editable. Others are read-only.

   • Add any comments in the Comments field.

2. Click one of the following:

   • Save to keep the process in the pending migration state.

   • Migrate to migrate the process and put it in the running state.

   • Cancel to return the process instance to its last saved state.

1. From the Pending Components panel, select the component you want to resume.

   The Resume Component dialog box appears as shown in the example in Figure 11-5. It tells you how many instances are pending migration for that component.

   Figure 11-5 Resume Component Dialog Box

   
   Description of "Figure 11-5 Resume Component Dialog Box"
2. In the Resume Component dialog box, choose whether you want the pending migration process instances to be:

   • Migrated as is

   • Suspended

   If there are instances that cannot be migrated-as-is, and you want to resume the component, then select Leave non-migrated instances as suspended. If you do not select this option, and there are instances that cannot be migrated as-is, then the component cannot be resumed.

3. Click Resume.

   The component is resumed and it no longer appears in the Pending Components panel. A Resume Component Confirmation dialog box tells you the result and how many instances are suspended. A new process instance can now be initiated and its requests are processed.

   Note:

   You can initiate a process instance even if a component is suspended. In this case, however, the requests are queued and are not processed until the component is resumed.

These are important considerations you must take into account before performing a migration:

• The same constraints apply when migrating as when performing instance patching.

  For example, you cannot move tokens to a non-interrupting boundary event.

• During migration, composite revision of a source instance is suspended so instances of that revision do not process incoming requests.

• This feature is implemented by using Ant commands.

  These commands require the following artifact that is part of your installation:

  /AS11gR1SOA/bin/ant-composite-instance-migration.xml.

  Note that this artifact requires wlfullclient.jar in the following directory:

  $FMW_HOME/wlserver_10.3/server/lib

  To generate the Oracle WebLogic Server client library:

  cd $fmw.home/wlserver_10.3/server/lib
  java -jar wljarbuilder.jar
  

1. Identify the scope of instances to be migrated and create the composite filter to specify them.
2. Run the migration feasibility report for the specified instances and review the output.

   The output report includes which instances can be automatically migrated, which require a plan to accomplish the migration (for example, an active activity was removed), and which instance cannot be migrated.

3. Develop the migration plan.
4. Run the migration and review the output.

The composite compatibility depends on the components defined inside the composite. If the change to any component is not compatible, then the composite is not eligible for instance migration. Only compatible changes in BPEL, BPMN, Human Workflow, and Business Rules are accepted. Changes in any other components make the composite ineligible for instance migration.

This section describes the restrictions you must consider for each component. It includes the following topics:

• BPEL Components

• BPMN Components

• Human Task Components

• Business Rules Components

• Mediator Components

The elements of the Ant Tasks are (see Figure 11-7):

• CompositeInstanceFilter: specifies the criteria to migrate the instance and defines the scope of the migration. This scope is determined by filtering composite instances based on:

  • compositeDN

  • domainName

  • compositeName

  • revision

  • label

  • ecid

  • conversationId

  • compositeInstanceId

  • tenantId

  • title

  • maxCreationDate

  • minCreationDate

  • maxModifyDate

  • minModifyDate

  • like

  • pageStart

  • pageSize

• Task to run feasibility report: The results are Not Possible, Automatic, or Manual. You can review the report and change the criteria to reduce or remove some of the instances from the migration by modifying the CompositeInstanceFilter.

• Task to run migration.

The migration elements are:

• Migration Report: describes the feasibility of migrating the proposed composite instances. The migration report includes:

  • Composite Instance Details

    • Name: Component instance name

    • ID: Component instance Id

    • State: Composite instance state

    • Migrate-ability: Automatic, Migration Plan required (and the required change plan, where applicable)

    • Component Instance Data: Associated component instance details

  • Summary Data:

    • The target revision

    • Total number of matching composite instances

    • Number of composite instances that can be automatically migrated

    • Number of composite instances that cannot be automatically migrated

• Migration Result: describes the outcome of migrating composite instances:

• Migration Plan: provides the XML description of what to do with non-trivial composite or component changes. The migration plan is based on the MigrationPlan XML schema.

  Migration Plan objects are created using MigrationPlanFactory.