What Happens When You Create a SOA Application and Project

2-4 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite Figure 2–1 New Workspace for a SOA Composite Application Table 2–3 describes the SOA Composite Editor. Table 2–3 SOA Composite Editor Element Description Application Navigator Displays the key files for the specific service components included in the SOA project: ■ A composite.xml file that is automatically created when you create a SOA project. This file describes the entire composite assembly of services, service components, references, and wires. ■ The business rules service component file rules_ name .decs. Additional business rules files display under the Oracle rules subfolder rules_name.rules. ■ The Oracle Mediator service component file mediator_ name .mplan. ■ The BPEL process service component files process_ name .bpel and process_name.wsdl. ■ The human task service component file task_name.task. ■ The spring service component file spring.xml. ■ The componentType file that describes the services and references for each service component. This file ensures that the wiring you create between components works. ■ Additional subfolders for class files, XSDs schemas, and XSLs transformations. Developing SOA Composite Applications with Oracle SOA Suite 2-5 Designer You drag service components, services, and references from the Component Palette into the composite in the designer. When you drag and drop a service component into the designer window, a corresponding property editor is invoked for performing configuration tasks related to that service component. For example, when you drag and drop the Oracle Mediator service component into the designer, the Mediator Editor is displayed that enables you to configure the Oracle Mediator service component. For all subsequent editing sessions, you double-click these service components to re-open their editors. Left Swimlane Exposed Services The left swimlane is for services, such as a web services or JCA adapters, providing an entry point to the SOA composite application. Right Swimlane External References The right swimlane is for references that send messages to external services in the outside world, such as web services and JCA adapters. Component Palette The component palette provides the various resources that you can use in a SOA composite. It contains the following service components and adapters: ■ Service components Displays the BPEL process, business rule, human task, Oracle Mediator, and spring components that can be dragged and dropped into the designer. ■ Service adapters Displays the JCA adapter AQ, file, FTP, database, JMS, MQ, Oracle Applications, and socket, Oracle BAM binding component, B2B binding component, EJB binding component, ADF-BC binding component, direct binding component, HTTP binding component, and web service binding component that can be dragged into the left or right swimlanes. If the Component Palette does not display, select Component Palette from the View main menu. Resource Palette The Resource Palette provides a single dialog from which you can browse both local and remote resources. For example, you can access the following resources: ■ Shared local application metadata such as schemas, WSDLs, event definitions, business rules, and so on. ■ WSIL browser functionality that uses remote resources that can be accessed through an HTTP connection, file URL, or Application Server connection. ■ Remote resources that are registered in a Universal Description, Discover, and Integration UDDI registry. If the Resource Palette does not display, then select Resource Palette from the View main menu. You select these resources for the SOA composite application through the SOA Resource Browser dialog. This dialog is accessible through a variety of methods. For example, when you select the WSDL file to use with a service binding component or an Oracle Mediator service component or select the schema file to use in a BPEL process, the SOA Resource Browser dialog appears. Click Resource Palette at the top of this dialog to access available resources. Table 2–3 Cont. SOA Composite Editor Element Description 2-6 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite 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.

2.1.3 What You May Need to Know About Opening the composite.xml File Through a SOA-MDS Connection

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 Administrators Guide.

2.2 Adding Service Components

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.

2.2.1 How to Add a Service Component

To add a service component: 1. From the Component Palette, select SOA. 2. From the Service Components list, drag a component into the designer. Figure 2–2 shows a BPEL process being added to the designer. Log Window The Log window displays messages about application compilation, validation, and deployment. Property Inspector The Property Inspector displays properties for the selected service component, service, or reference. If the Property Inspector does not display, select Property Inspector from the View main menu. Application View The Application View shows the artifacts for the SOA composite application. Table 2–3 Cont. SOA Composite Editor Element Description Developing SOA Composite Applications with Oracle SOA Suite 2-7 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. 3. 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. Table 2–4 Starting Service Component Editors Dragging This Service Component... Invokes The... BPEL Process 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. Business Rule Create Business Rules dialog to create a business decision based on rules. Human Task 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. Mediator Create Mediator dialog to define services that perform message and event routing, filtering, and transformations. Spring Context Create Spring dialog to create a spring context file for integrating Java interfaces into SOA composite applications.