SOA 11g Composite states and behavior


Useful composite states and the behaviour for reference.

Composites Table

The Composites table enables you to manage the state of a selected SOA composite application. All actions in this table, except Deploy, require you to select a row in the table.

Element Description
Shut Down Shuts down a running SOA composite application revision. Any request (initiating or a callback) to the composite is rejected if the composite is shut down.Note: The behavior differs based on which binding component is used. For example, if it is a web service request, it is rejected back to the caller. A JCA adapter binding component may do something else in this case (for example, put the request in a rejected table).

This option displays when the composite application has been started.

Start Up Restarts a composite application revision that was shut down. This action enables new requests to be processed (and not be rejected). No recovery of messages occurs.This option displays when the composite application has been stopped.
Retire Retires the selected composite revision. If the process life cycle is retired, you cannot create a new instance. Existing instances are allowed to complete normally.An initiating request to the composite application is rejected back to the client. The behavior of different binding components during rejection is the same as described above for the shut down option.

A callback to an already-initiated composite application instance is delivered properly.

This option displays when the composite application is active.

Activate Activates the retired composite application revision. Note the following behavior with this option:

  • All composite applications are automatically active when deployed.
  • Other revisions of a newly deployed composite application remain active (that is, they are not automatically retired). If you want, you must explicitly retire them.

This option displays when the composite application is retired.

Set As Default Sets the selected composite application revision to be the default. Default revisions are indicated by a green dot in the Composites table. If a new request comes in for a specific composite application revision, that composite application revision is invoked. If a new request comes in without specifying a revision, the default revision is invoked. The default revision does not change when a composite application is retired. The default revision is changed automatically when a default composite application revision is undeployed.The default composite revision also changes automatically when you redeploy a composite. The newly redeployed revision automatically becomes the default revision, unless at the time of redeployment you specify to keep the previous default revision unchanged.

Note that inbound adapters are only activated on the default revision.

Deploy Deploys a revision. Deployment activates the composite application in the SOA Infrastructure. Use this selection when you want to deploy:

  • A new SOA composite application for the first time
  • A new revision (for example, 2.0) of a SOA composite application that already has a different revision that is currently deployed (for example, 1.0). This option enables both revisions 1.0 and 2.0 to be deployed at the same time.

If you specify a revision that already exists, you receive an error and must use either a different revision or perform a redeployment to overwrite the existing revision.

Undeploy Undeploys the selected composite application revision. The consequences of this action are as follows:

  • You can no longer configure and monitor this revision of the composite application.
  • You can no longer process instances of this revision of the composite application.
  • You cannot view previously completed processes.
  • The state of currently running instances is changed to stale and no new messages sent to this composite are processed.
  • If you undeploy the default revision of the composite application (for example, 2.0), the next available revision of the composite application becomes the default (for example, 1.0).
Redeploy Redeploys an existing revision of a SOA composite application. The consequences of this action are as follows:

  • A new version of a revision of a currently deployed SOA composite application is redeployed (for example, old version 1.0 is redeployed as new version 1.0).
  • The older, currently-deployed version of this revision is removed (overwritten).
  • If the older, currently-deployed version of this revision has running instances, the state of those instances is changed to stale.
Composite Displays the deployed SOA composite application name. Click a specific revision to access its home page. A green dot indicates a default SOA composite application revision.Note: You occasionally see a red error icon before a composite name. The tool tip says Target not found. If you click the icon, you get an error stating that the composite application revision is not available. This can occur because either the composite has been undeployed or the SOA Infrastructure has not yet loaded this composite application.
Partition Displays the partition in which the SOA composite application is deployed. To bulk manage the deployment life cycle of large numbers of composites, use the Partition Home page and the Manage Partitions page. You create and delete partitions from the Manage Partitions page, which you access from the SOA Infrastructure target menu.A partition is required before you can deploy any composites. If a partition is deleted, this automatically undeploys all SOA composite revisions in the partition.
Status Displays the status of the SOA composite application (either Up (on) or Down (off)).
Mode Displays the mode of the SOA composite application (either active or retired).
Instances Displays the number of instances for each SOA composite application revision.
Faulted Instances Displays the total number of faults in all instances of this revision of the SOA composite application. Each instance can have more than one fault.
Last Modified Date Displays the time at which the SOA composite application was deployed, redeployed, or reconfigured.
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s