| Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 (11.1.1.5.0) Part Number E10224-09 |
|
|
View PDF |
| Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 (11.1.1.5.0) Part Number E10224-09 |
|
|
View PDF |
This chapter describes how to use Oracle JDeveloper to create a SOA composite application. This overview is intended to guide you through the basic steps of composite creation, along with describing key issues to be aware of when designing a composite application.
This chapter includes the following sections:
The first steps in building a new application are to assign it a name and to specify the directory where to save source files. By creating an application using application templates provided by Oracle JDeveloper, you automatically get the organization of the workspace into projects, along with many of the configuration files required by the type of application you are creating.
You first create an application for the SOA project.
Note:
In order to create and deploy SOA composite applications and projects, you must install the Oracle SOA Suite extension. For instructions on installing this extension for Oracle JDeveloper, see the Oracle Fusion Middleware Installation Guide for Oracle JDeveloper.To create an application:
Start Oracle JDeveloper Studio Edition Version 11.1.1.5.0.
If Oracle JDeveloper is running for the first time, specify the location for the Java JDK.
Create a new SOA composite application, as described in Table 2-1.
Table 2-1 SOA Composite Application Creation
| If Oracle JDeveloper... | Then... |
|---|---|
|
Has no applications For example, you are opening Oracle JDeveloper for the first time. |
In the Application Navigator in the upper left, click New Application. |
|
Has existing applications |
From the File main menu or the Application menu:
|
The Create SOA Application wizard starts.
In the Name your application page, you can optionally change the name and location for your web project. If this is your first application, from Application Template, select SOA Application. Accept the defaults for the package prefix, and click Next.
Notes:
Do not create an application name with spaces.
Do not create applications and projects in directory paths that have spaces (for example, c:\Program Files).
On a UNIX operating system, it is highly recommended to enable Unicode support by setting the LANG and LC_All environment variables to a locale with the UTF-8 character set. This action enables the operating system to process any character in Unicode. SOA technologies are based on Unicode. If the operating system is configured to use non-UTF-8 encoding, SOA components may function in an unexpected way. For example, a non-ASCII file name can make the file inaccessible and cause an error. Oracle does not support problems caused by operating system constraints.
In a design-time environment, if you are using Oracle JDeveloper, select Tools > Preferences > Environment > Encoding > UTF-8 to enable Unicode support. This setting is also applicable for runtime environments.
In the Name your project page, you can optionally change the name and location for your SOA project. By default, Oracle JDeveloper adds the SOA project technology, the composite.xml that generates, and the necessary libraries to your model project. Click Next.
Note:
Composite and component names cannot exceed 500 characters.A project deployed to the same infrastructure must have a unique name across SOA composite applications. The uniqueness of a composite is determined by its project name. For example, do not perform the actions described in Table 2-2. During deployment, the second deployed project (composite) overwrites the first deployed project (composite).
Table 2-2 Restrictions on Naming a SOA Project
| Create an Application Named... | With a SOA Project Named... |
|---|---|
|
|
|
|
|
|
The Project SOA Settings page of the Create SOA Application wizard appears.
In the Configure SOA Settings page, click Empty Composite, and click Finish.
From the File main menu, select Save All.
When you create a SOA application, Oracle JDeveloper creates a project that contains all the source files related to your application. Oracle JDeveloper automatically adds the following libraries needed for your SOA project:
SOA Design time
SOA Runtime
BPEL Runtime
Oracle Mediator Runtime
MDS Runtime
You can then use Oracle JDeveloper to create additional projects needed for your application.
Figure 2-1 shows the SOA Composite Editor for the OrderBookingComposite project contained within the WebLogicFusionOrderDemo application of the Fusion Order Demo.
Figure 2-1 New Workspace for a SOA Composite Application
Table 2-3 describes the SOA Composite Editor.
Table 2-3 SOA Composite Editor
The composite.xml file displays as a tab in the designer and as a file in the Application Navigator. This file is automatically created when you create a new SOA project. This file describes the entire composite assembly of services, service components, and references. There is one composite.xml file for each SOA project.
When you work with the composite.xml file, you mostly use the designer, the Structure window, and the Property Inspector, as shown in Figure 2-1. The designer enables you to view many of your files in a WYSIWYG environment, or you can view a file in an overview editor where you can declaratively make changes, or you can view the source code for the file. The Structure window shows the structure of the currently selected file. You can select objects in this window, and then edit the properties for the selection in the Property Inspector.
If you create a SOA-MDS connection in Oracle JDeveloper, expand the connection, and attempt to open the composite.xml file of a composite from the Resource Palette, the file may not load correctly. Only open a composite from the Application Navigator.
For information about the Oracle Metadata Services (MDS) repository, see Oracle Fusion Middleware Administrator's Guide.
Once you create your application, often the next step is to add service components that implement the business logic or processing rules of your application. You can use the Component Palette from the SOA Composite Editor to drag and drop service components into the composite.
To add a service component:
From the Component Palette, select SOA.
From the Service Components list, drag a component into the designer.
Figure 2-2 shows a BPEL process being added to the designer.
Figure 2-2 Adding BPEL Process to Composite
A specific dialog for the selected service component is displayed. Table 2-4 describes the available editors.
Table 2-4 Starting Service Component Editors
| Dragging This Service Component... | Invokes The... |
|---|---|
|
Create BPEL Process dialog to create a BPEL process that integrates a series of business activities and services into an end-to-end process flow. |
|
|
Create Business Rules dialog to create a business decision based on rules. |
|
|
Create Human Task dialog to create a workflow that describes the tasks for users or groups to perform as part of an end-to-end business process flow. |
|
|
Create Mediator dialog to define services that perform message and event routing, filtering, and transformations. |
|
|
Create Spring dialog to create a spring context file for integrating Java interfaces into SOA composite applications. |
Configure the settings for a service component. For help with a service component dialog, click Help or press F1. Click Finish.
Figure 2-3 shows the BPEL Process dialog with data entered to create the OrderProcessor BPEL process for the WebLogicFusionOrderDemo application of the Fusion Order Demo. The process is selected to be asynchronous. The Expose as a SOAP Service option directs Oracle JDeveloper to create this service component automatically connected to an inbound web service.
Click OK.
The service component displays in the designer. Figure 2-4 shows the OrderProcessor BPEL process added to the composite.xml file. A SOAP service binding component called orderprocessor_client_ep in the left swimlane provides the outside world with an entry point into the SOA composite application. If the Expose as a SOAP Service option was not selected in the Create BPEL Process dialog, the orderprocessor_client_ep service would not display. Section 2.3.1, "How to Add a Service Binding Component," describes how you later add a service.
You can more fully define the content of the service component now or at a later time. For this top-down example, the content is defined now.
From the File main menu, select Save All.
Note the following details about adding service components:
Create a service component from either the SOA Composite Editor or the designer of another component. For example, you can create a human task component from the SOA Composite Editor or the Oracle BPEL Designer.
Use the Resource Palette to browse for service components defined in the SOA Composite Editor, and those deployed.
Note the following details about deleting service components:
You can delete a service component by right-clicking it and selecting Delete from the context menu.
When a service component is deleted, all references pointing to it are invalidated and all wires are removed. The service component is also removed from the Application Navigator.
A service component created from within another service component can be deleted. For example, a human task created within the BPEL process service component of Oracle JDeveloper can be deleted from the SOA Composite Editor. In addition, the partner link to the task can be deleted. Deleting the partner link removes the reference interface from its .componentType file and removes the wire to the task.
You modify a service component to define specific details about the service component.
To edit a service component:
Double-click the service component in the designer to display the appropriate editor or designer, as described in Table 2-5.
Table 2-5 Starting SOA Service Component Wizards and Dialogs
| Double-Clicking This Service Component... | Displays The... |
|---|---|
|
BPEL Process |
Oracle BPEL Designer for further designing. |
|
Business Rule |
Business Rules Designer for further designing. |
|
Human Task |
Human Task Editor for further designing. |
|
Mediator |
Oracle Mediator Editor for further designing. |
|
Spring Context |
Spring Editor for further designing. |
To return to the SOA Composite Editor from within any service component, double-click composite.xml in the Application Navigator or single-click composite.xml above the designer.
For help with a service component editor, click Help or press F1.
Click Finish.
Modify the settings for a service component. For help with a service component editor or designer, click Help or press F1.
Click Finish.
In the Application Navigator, double-click composite.xml or single-click composite.xml above the designer.
This action returns you to the SOA Composite Editor.
From the File main menu, select Save All.
You add a service binding component to act as the entry point to the SOA composite application from the outside world.
Notes:
This section describes how to manually create a service binding component. You can also automatically create a service binding component by selecting Expose as a SOAP Service when you create a service component. This selection creates an inbound web service binding component that is automatically connected to your BPEL process, human task service, or Oracle Mediator service component.
You cannot invoke a representational state transfer (REST) service from the SOA Composite Editor.
You can use the Component Palette from the SOA Composite Editor to drag and drop service binding components to the composite.
To add a service binding component:
From the Component Palette, select SOA.
From the Service Adapters list, drag a service to the left swimlane to define the service interface.
Figure 2-5 shows a web service being added to the designer.
Figure 2-5 Adding Web Service to Composite
A specific dialog for the selected service displays. Table 2-6 describes the available editors.
| Dragging This Service... | Invokes The... |
|---|---|
|
Create Web Service dialog to create a web invocation service. |
|
|
Adapter Configuration Wizard to guide you through integration of the service with database tables, database queues, file systems, FTP servers, Java Message Services (JMS), IBM WebSphere MQ, BAM servers, sockets, or Oracle E-Business Suite applications. |
|
|
Create ADF-BC Service dialog to create a service data object (SDO) invocation service. |
|
|
B2B Wizard to guide you through selection of a document definition. |
|
|
Create EJB Service to create an Enterprise JavaBeans service for using SDO parameters or Java interfaces with Enterprise JavaBeans. |
|
|
Create HTTP Binding Wizard to create HTTP binding. This wizard enables you to invoke SOA composite applications through HTTP POST and GET operations. |
|
|
Create Direct Binding Service dialog to invoke a SOA composite application and exchange messages over a remote method invocation (RMI) in the inbound direction. |
Configure the settings for the service. For help with a service editor, click Help or press F1.
Click Finish.
Figure 2-6 shows the Web Service dialog with data entered to create the orderprocessor_client_ep service for the OrderProcessor BPEL process.
Click OK.
The service binding component displays in the left swimlane. Figure 2-7 shows the orderprocessor_client_ep service binding component added to the composite.xml file.
Select Save All from the File main menu.
As described in Section 2.3.1, "How to Add a Service Binding Component," a web service is a type of binding component that you can add to a SOA composite application. You must select the WSDL file for the web service.
To add a WSDL for a web service:
In the Component Palette, select SOA.
From the Service Adapters list, drag a Web Service to the left swimlane.
This invokes the Create Web Service dialog shown in Figure 2-6.
Enter the details shown in Table 2-7:
Table 2-7 Create Web Service Dialog Fields and Values
| Field | Value |
|---|---|
|
Name |
Enter a name for the service. |
|
Type |
Select the type (message direction) for the web service. Since you dragged the web service to the left swimlane, the Service type is the correct selection, and displays by default:
Since this example describes how to create an entry point to the SOA composite application, Service is selected. |
Select the WSDL file for the service. There are three methods for selection:
To the right of the WSDL URL field, click the first icon and select an existing WSDL file from the local file system (for this example, OrderProcessor.wsdl is selected). Note that File System in the list at the top of the dialog is automatically selected. Figure 2-8 provides details.
To the right of the WSDL URL field, click the first icon and select Resource Palette from the list at the top of the dialog, as shown in Figure 2-9. This action enables you to use existing WSDL files from other applications.
Figure 2-9 Use of Existing WSDL files from Other Applications
To the right of the WSDL URL field, click the second icon to automatically generate a WSDL file from a schema. Figure 2-10 shows the Create WSDL dialog. Default values for the WSDL file name, directory location, namespace, port type, operation name, and interface type are displayed. If the specified directory is not the subdirectory of the current project, a warning message is displayed. If the specified directory does not exist, it is automatically created.
You can modify the default values.
Figure 2-10 Automatic Generation of WSDL File
Click the Add icon above the Input table to display the Add Message Part dialog to add a new WSDL message part. If the WSDL file contains multiple messages, you can add a message part for each one. You can select XML schema simple types, project schema files, and project WSDL files for a message part.
For more information, click Help.
Click OK to return to the Create Web Service dialog.
Note the additional details described in Table 2-8:
Click OK.
From the File main menu, select Save All.
You can view all schemas used by the interface's WSDL file and, if you want, choose a new message schema for a selected message part in the Update Interface dialog.
To view schemas:
Double-click the small arrow handle that appears on the specific binding component or service component. Figure 2-11 provides details.
Figure 2-11 Selection of Inbound Interface Handle
The Update Interface dialog shown in Figure 2-12 displays all schemas currently used by the WSDL file.
If you want to select a new message schema, click Help or press F1 for instructions.
After initially creating a service, you can edit its contents at a later time. Double-click the component icon to display its appropriate editor or wizard. Table 2-9 provides an overview.
Table 2-9 Starting Service Wizards and Dialogs
| Double-Click This Service... | To... |
|---|---|
|
Web service |
Display the Update Service dialog. |
|
Adapters |
Reenter the Adapter Configuration Wizard. |
|
ADF-BC Service |
Display the Update Service dialog. |
|
B2B |
Reenter the B2B wizard. |
|
EJB Service |
Display the Update Service dialog. |
|
HTTP Binding |
Reenter the HTTP Binding Wizard. |
|
Direct Binding |
Reenter the Update Service dialog. |
Note the following detail about adding services:
When a new service is added for a service component, the service component is notified so that it can make appropriate metadata changes. For example, when a new service is added to a BPEL service component, the BPEL service component is notified to create a partner link that can be connected to a receive or an on-message activity.
Note the following detail about deleting services:
When a service provided by a service component is deleted, all references to that service component are invalidated and the wires removed.
You add reference binding components that enable the SOA composite application to send messages to external services in the outside world.
You can use the Component Palette from the SOA Composite Editor to drag and drop reference binding components to the composite.
To add a reference binding component:
From the Component Palette, select SOA.
From the Service Adapters list, drag a service to the right swimlane.
Figure 2-13 shows a web service being added to the designer.
Figure 2-13 Adding Web Service to Composite
A specific dialog or wizard for the selected reference displays. Table 2-10 describes the available editors.
Table 2-10 Reference Editors
| Dragging This Service... | Invokes The... |
|---|---|
|
Create Web Service dialog to create a web invocation service. |
|
|
Adapter Configuration Wizard to guide you through integration of the service with database tables, database queues, file systems, FTP servers, Java Message Services (JMS), IBM WebSphere MQ, BAM servers, sockets, or Oracle E-Business Suite applications. |
|
|
Create ADF-BC Service dialog to create a service data object (SDO) invocation service. |
|
|
B2B Wizard to guide you through selection of a document definition. |
|
|
Create EJB Service dialog to create an Enterprise JavaBeans service for using SDO parameters with Enterprise JavaBeans. |
|
|
Create HTTP Binding Wizard to create HTTP binding. This wizard enables you to invoke SOA composite applications through HTTP POST and GET operations, and invoke HTTP endpoints through HTTP POST and GET operations. |
|
|
Create Direct Binding Service Dialog to invoke an Oracle Service Bus (OSB) flow or another SOA composite application. |
Configure the settings for the reference binding component. For help with a reference editor, click Help or press F1.
Click Finish.
Figure 2-14 shows the Create Web Service dialog with data entered to create a reference.
Click OK.
The reference binding component displays in the right swimlane. Figure 2-15 shows the StoreFrontService reference added to the SOA composite application.
From the File main menu, select Save All.
Note the following detail about adding references:
The only way to add a new reference in the SOA Composite Editor is by wiring the service component to the necessary target service component. When a new reference is added, the service component is notified so it can make appropriate changes to its metadata. For example, when a reference is added to a BPEL service component, the BPEL service component is notified to add a partner link that can then be used in an invoke activity.
Note the following details about deleting references:
When a reference for a service component is deleted, the associated wire is also deleted and the service component is notified so it can update its metadata. For example, when a reference is deleted from a BPEL service component, the service component is notified to delete the partner link in its BPEL metadata.
Deleting a reference connected to a wire clears the reference and the wire.
A WSDL file is added to the SOA composite application whenever you create a new component that has a WSDL (for example, a service binding component, service component (for example, Oracle Mediator, BPEL process, and so on), or reference binding component. When you delete a component, any WSDL imports used by that component are removed only if not used by another component. The WSDL import is always removed when the last component that uses it is deleted.
When a service or reference binding component is updated to use a new WSDL, it is handled as if the interface was deleted and a new one was added. Therefore, the old WSDL import is only removed if it is not used by another component.
If a service or reference binding component is updated to use the same WSDL (porttype qname), but from a new location, the WSDL import and any other WSDL reference (for example, the BPEL process WSDL that imports an external reference WSDL) are automatically updated to reference the new location.
Simply changing the WSDL location on the source view of the composite.xml file's import is not sufficient. Other WSDL references in the metadata are required by the user interface (see the ui:wsdlLocation attribute on composite and componentType services and references). There can also be other WSDL references required by runtime (for example, a WSDL that imports another WSDL, such as the BPEL process WSDL).
Always modify the WSDL location though the dialogs of the SOA Composite Editor in which a WSDL location is specified (for example, a web service, BPEL partner link, and so on). Changing the URL's host address is the exact case in which the SOA Composite Editor automatically updates all WSDL references.
If a BPEL process has multiple WSDL messages declared in its WSDL file and one or more messages have their parts defined to be of some type, whereas other messages have their parts defined to be of some element, runtime behavior can become unpredictable. This is because these WSDLs are considered to have mixed type messages. For example, assume there are multiple copy actions within an assign activity. These copy actions attempt to populate an output variable that has multiple parts:
Part 1 is declared as an xsd:string type.
Part 2 is declared as an xsd:int type.
Part 3 is declared as an element of a custom-designed complex type.
This behavior is not supported.
A WSDL URL that does not contain a revision number is processed by the default composite application. This action enables you to always call the default revision of the called service without having to make other changes in the calling composite.
Select the default WSDL to use in the Resource Palette in Oracle JDeveloper.
In the Create Web Service dialog, click the icon to the right of the WSDL URL field to invoke the SOA Resource Browser dialog.
Select Resource Palette from the list at the top.
Expand the nodes under the Application Server connection or WSIL connection to list all deployed composites and revisions. The default revision is identified by the word Default in the title. For example, OrderBookingComposite [Default].
Select the appropriate default endpoint and click OK.
You wire (connect) services, service components, and references. For this example, you wire the web service and service component. Note the following:
Since a web service is an inbound service, a reference handle displays on the right side. Web services that are outbound references do not have a reference handle on the right side.
You can drag a defined interface to an undefined interface in either direction (reference to service or service to reference). The undefined interface then inherits the defined interface. There are several exceptions to this rule:
A component has the right to reject a new interface. For example, an Oracle Mediator can only have one inbound service. Therefore, it rejects attempts to create a second service.
You cannot drag an outbound service (external reference) to a business rule, because business rules do not support references. When dragging a wire, the user interface highlights the interfaces that are valid targets.
You cannot wire services and composites that have different interfaces. For example, you cannot connect a web service configured with a synchronous WSDL file to an asynchronous BPEL process. Figure 2-16 provides details.
Figure 2-16 Limitations on Wiring Services and Composites with Different Interfaces
The service and reference must match, meaning the interface and the callback must be the same. If you have two services that have different interfaces, you can place an Oracle Mediator between the two services and perform a transformation between the interfaces.
You can wire a service binding component to a service component from the SOA Composite Editor.
To wire a service and a service component:
From a service reference handle, drag a wire to the service component interface, as shown in Figure 2-17.
If the service component is a BPEL process, double-click the BPEL process and note that the service displays as a partner link in the left swimlane, as shown in Figure 2-18.
Figure 2-18 Display of the Service as a Partner Link in the BPEL Process
Select Save All from the File main menu.
You can wire a service component to a reference binding component from the SOA Composite Editor.
To wire a service component and a reference:
In the Application Navigator, double-click composite.xml or single-click composite.xml above the designer.
From the service component, drag a wire to the reference, as shown in Figure 2-19.
Figure 2-19 Wiring of a Service Component and Reference
If the service component is a BPEL process, double-click the BPEL process and note that the reference displays as a partner link in the right swimlane, as shown in Figure 2-20.
Figure 2-20 Display of the Reference as a Partner Link in the BPEL Process
Select Save All from the File main menu.
In the Application Navigator, select the composite.xml file.
Click the Source tab to review what you have created.
The orderprocessor_client_ep service binding component shown in Example 2-1 provides the entry point to the composite.
<service name="orderprocessor_client_ep"
ui:wsdlLocation="oramds:/apps/FusionOrderDemoShared
/services/orderbooking/OrderBookingProcessor.wsdl">
<interface.wsdl interface= "http://www.globalcompany.example.com/ns
/OrderBookingService#wsdl.interface(OrderProcessor)"
<binding.adf serviceName="OrderProcessorService" registryName=""/>
<callback>
<binding.ws port="http://www.globalcompany.example.com/ns
/OrderBookingService#wsdl.endpoint(orderprocessor_clientep/OrderProcessorCallback_
pt)"/>
</callback>
</service>
The OrderProcessor BPEL process service component is shown in Example 2-2:
Example 2-2 Service Component
<component name="OrderProcessor"> <implementation.bpel src="OrderProcessor.bpel"/> </component>
A reference binding component named StoreFrontService is shown in Example 2-3. The reference provides access to the external service in the outside world.
Example 2-3 Reference
<reference name="StoreFrontService"
ui:wsdlLocation="oramds:/apps/FusionOrderDemoShared
/services/oracle/fodemo/storefront/store/service/common/serviceinterface/StoreFron
tService.wsdl">
<interface.wsdl
interface="www.globalcompany.example.com#wsdl.interface(StoreFrontService)"/>
<binding.ws
port="www.globalcompany.example.com#wsdl.endpoint(StoreFrontService/StoreFrontServ
iceSoapHttpPort)"
location="oramds:/apps/FusionOrderDemoShared/services/oracle/fodemo/storefront/sto
re/service/common/serviceinterface/StoreFrontService.wsdl"/>
</reference>
In Example 2-4, the communication (or wiring) between service components is described:
The source orderprocessor_client_ep service binding component is wired to the target OrderProcessor BPEL process service component. Wiring enables web service message communication with this specific BPEL process.
The source OrderProcessor BPEL process is wired to the target StoreFrontService reference binding component. This is the reference to the external service in the outside world.
Note the following details about adding wires:
A service component can be wired to another service component if its reference matches the service of the target service component. Note that the match implies the same interface and callback interface.
Adding the following wiring between two Oracle Mediator service components causes an infinite loop:
Create a business event.
Create an Oracle Mediator service component and subscribe to the event.
Create a second Oracle Mediator service component to publish the same event.
Wire the first Oracle Mediator to the second Oracle Mediator component service.
If you remove the wire between the two Oracle Mediators, then for every message, the second Oracle Mediator can publish the event and the first Oracle Mediator can subscribe to it.
Note the following details about deleting wires:
When a wire is deleted, the component's outbound reference is automatically deleted and the component is notified so that it can clean up (delete the partner link, clear routing rules, and so on). However, the component's interface is never deleted. All Oracle SOA Suite services are defined by their WSDL interface. When a component's interface is defined, there is no automatic deletion of the service interface in the SOA Composite Editor.
If you want to change the service WSDL interface, there are several workarounds:
In most cases, you just want to change the schema instead of the inbound service definition. In the SOA Composite Editor, click any interface icon that uses the WSDL. For example, you can click the web service interface icon or the Oracle Mediator service icon. This invokes the Update Interface dialog, which enables you to change the schema for any WSDL message.
If you are using an Oracle Mediator service component, the Refresh operations from WSDL icon of the Oracle Mediator Editor enables you to refresh (after adding new operations) or replace the Oracle Mediator WSDL. However, you are warned if the current operations are to be deleted. If you change the WSDL to the new inbound service WSDL using this icon, the wire typically breaks because the interface has changed. You can then wire Oracle Mediator to the new service.
In many cases, a new service requires a completely new Oracle Mediator. Delete the old Oracle Mediator, create a new one, and wire it to the new service.
If you are using a BPEL process service component, select a new WSDL through the Edit Partner Link dialog.
See Section 2.3.3, "How to View Schemas" for details about the Update Interface dialog.
As you create your SOA composite application, you can secure web services by attaching policies to service binding components, service components, and reference binding components. For more information about implementing policies, see Chapter 39, "Enabling Security with Policies."
Deploying the SOA composite application involves creating a connection to an Oracle WebLogic Server and deploying an archive of the SOA composite application to an Oracle WebLogic Server managed server. For more information about deploying SOA composite applications, see Chapter 40, "Deploying SOA Composite Applications."
You can invoke other deployed SOA composite applications from your SOA composite application. The other applications must be deployed.
To invoke other composites:
Create a web service or partner link through one of the following methods.
In the SOA Composite Editor, drag a Web Service from the Component Palette to the External References swimlane.
In Oracle BPEL Designer, drag a Partner Link from the Component Palette to the right swimlane.
Access the SOA Resource Browser dialog based on the type of service you created.
For the Create Web Service dialog, click the Find existing WSDLs icon.
For the Edit Partner Link dialog, click the SOA Resource Browser icon.
From the list at the top, select Resource Palette.
Expand the tree to display the application server connection to the Oracle WebLogic Administration Server on which the SOA composite application is deployed.
Expand the application server connection.
Expand the SOA folder. Figure 2-21 provides details.
Figure 2-21 Browse for a SOA Composite Application
Select the composite service.
Click OK.
As you build and deploy a SOA composite application, you manage and test it using a combination of Oracle JDeveloper and Oracle Enterprise Manager Fusion Middleware Control.
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 > Connections > Application Server Connection to create a connection.From the View main menu, select Application Server Navigator.
Expand your connection name (for this example, named MyConnection).
The SOA folder appears, as shown in Figure 2-22. 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-22 provides details.
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-23.
Figure 2-23 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-11 provides details.
Table 2-11 SOA Composite Application Options
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-24 provides details.
For more information, see the following documentation:
Chapter 40, "Deploying SOA Composite Applications" for details about creating a deployment profile and a configuration plan and deploying an existing SOA archive
Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle BPM Suite for details about managing deployed SOA composite applications from Oracle Enterprise Manager Fusion Middleware Control.
After you deploy a SOA composite application, you can initiate a test instance of it from the Test Web Service page in Oracle Enterprise Manager Fusion Middleware Control to verify the XML payload data. For more information about initiating a test instance, see the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle BPM Suite.
In addition to creating a test instance, you can also simulate the interaction between a SOA composite application and its web service partners before deployment in a production environment. This helps to ensure that a process interacts with web service partners as expected by the time it is ready for deployment to a production environment. For more information about creating a unit test, see Chapter 41, "Automating Testing of SOA Composite Applications."
|
 Copyright © 2005, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
