How to Manage Deployed SOA Composite Applications in Oracle JDeveloper

You can manage deployed SOA composite applications from the Application Server Navigator in Oracle JDeveloper. Management tasks consist of undeploying, activating, retiring, turning on, and turning off SOA composite application revisions.

Note:

These instructions assume you have created an application server connection to an Oracle WebLogic Administration Server on which the SOA Infrastructure is deployed. Creating a connection to an Oracle WebLogic Administration Server enables you to browse for managed Oracle WebLogic Servers or clustered Oracle WebLogic Servers in the same domain. From the File main menu, select New > Application > Connections > Application Server Connection to create a connection.

From the Window main menu, select Application Servers.
Expand your connection name (for this example, named MyConnection).

The SOA folder appears, as shown in Figure 2-26. The SOA folder displays all deployed SOA composite application revisions and services. You can browse all applications deployed on all Oracle WebLogic Administration Servers, managed Oracle WebLogic Servers, and clustered Oracle WebLogic Servers in the same domain. Figure 2-26 provides details.

Figure 2-26 Application Server Navigator

Description of "Figure 2-26 Application Server Navigator"
Expand the SOA folder.
Expand the partition in which the composite application is deployed.

Deployed SOA composite applications and services appear, as shown in Figure 2-27.

Figure 2-27 Deployed SOA Composite Applications

Description of "Figure 2-27 Deployed SOA Composite Applications"
Right-click a deployed SOA composite application.

Select an option to perform. The options that display for selection are based upon the current state of the application. Table 2-13 provides details.

Table 2-13 SOA Composite Application Options

Option	Description
Stop	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	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 with the shut down option. A callback to an 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 application is retired.
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 aborted 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).
Set Default Revision	Sets the selected composite application revision to be the default.

If you want to deploy a prebuilt SOA composite application archive that includes a deployment profile, right-click the SOA folder and select Deploy SOA Archive. The archive consists of a JAR file of a single application or a SOA bundle ZIP file containing multiple applications.
You are prompted to select the following:
- The target SOA servers to which you want to deploy the SOA composite application archive.
- The archive to deploy.
- The configuration plan to attach to the application. As you move projects from one environment to another (for example, from testing to production), you typically must modify several environment-specific values, such as JDBC connection strings, hostnames of various servers, and so on. Configuration plans enable you to modify these values using a single text (XML) file called a configuration plan. The configuration plan is created in either Oracle JDeveloper or from the command line. During process deployment, the configuration plan is used to search the SOA project for values that must be replaced to adapt the project to the next target environment. This is an optional selection.
- Whether you want to overwrite an existing composite of the same revision ID. This action enables you to redeploy an application revision.
Figure 2-28 provides details.

Figure 2-28 Deploy SOA Archive Dialog

Description of "Figure 2-28 Deploy SOA Archive Dialog"

For more information, see the following documentation:

Deploying SOA Composite Applications for details about creating a deployment profile and a configuration plan and deploying an existing SOA archive
Administering Oracle SOA Suite and Oracle Business Process Management Suite for details about managing deployed SOA composite applications from Oracle Enterprise Manager Fusion Middleware Control.