Online Help for Oracle SOA Suite

1.23 Create Application Wizard - Configure SOA Settings Page

Use to select the service component to include in the creation of the service-oriented architecture (SOA) project of the composite application. Additional service components can be added after creation.

A SOA project can consist of multiple BPEL process, human task, business rule, spring context, and Oracle Mediator service components, and subprocesses. These components are integrated together into an application and communicate with the outside world through binding components such as simple object access protocol (SOAP) web services, HTTP binding, direct binding, REST binding, Oracle Application Development Framework (ADF) Business Components, Java EE Connector Architecture (JCA) adapters, Oracle B2B, and Enterprise JavaBeans (EJBs).

You can also create a SOA composite application from a template. A template is a reusable part of a SOA project for bootstrapping new projects.

After creation, the SOA Composite Editor appears. The composite.xml file is displayed in the editor. This file describes details about the SOA application that you design. You drag service components and binding components (such as web services and adapters) into the SOA Composite Editor from the Components window. More

Element	Description
Composite Name	Enter the SOA composite name, which defaults to the SOA project name. The project consists of services, references, and service components, the details of which are described in the `composite.xml` file.
Standard Composite	Select the type of template for the SOA project. You then design your SOA composite application in further detail by adding additional components and adapters. This is the default selection.
Empty Composite	Creates an empty SOA composite application. This type is selected by default.
Composite With Human Task	Automatically opens the Create Human Task dialog to guide you through creation of an initial human task service component. A human task component enables you to model a workflow that describes the tasks for users or groups to perform as part of an end-to-end business process flow. The tasks are accessed through Oracle BPM Worklist during process runtime.
Composite With BPEL Process	Automatically opens the Create BPEL Process dialog to guide you through creation of an initial BPEL process. A BPEL process enables you to design a business process that integrates a series of business activities and services into an end-to-end process flow.
Composite With Subprocess	Automatically creates a SOA composite application with a subprocess. A subprocess is a fragment of BPEL code that can be reused within a particular processor by separate processes.
Composite With Spring Context	Automatically opens the Create Spring dialog to guide you through creation of a spring context service component. A spring context service component enables you to integrate components that use Java interfaces instead of WSDL files into SOA composite applications. You can also integrate components that use Java interfaces with components that use WSDL files in the same SOA composite application.
Composite With Business Rule	Automatically opens the Create Business Rules dialog to guide you through creation of an initial business rule service component. A business rule enables you to design a business decision based on rules.
Composite With Mediator	Automatically opens the Create Mediator dialog to guide you through creation of an initial Oracle Mediator service component. Oracle Mediator enables you to route events (messages) between different components.
SOA Template	Select to display the list of available custom SOA templates. A template is a reusable part of a SOA project that you can use to bootstrap new projects. A template can contain a SOA composite application, a service component, and part of a BPEL process and related additional resources, such as XML schemas or WSDLs. More
Customizable	Select this checkbox to create a composite that you want to make customizable by others. For example, you create a base composite and deliver it to another applications team that imports it into a SOA project and customizes it for a certain industry (for example, telecommunications). The tailored solution is then sold to a telecommunications customer that further customizes the composite for their specific geographic business needs. Essentially, there is a base composite and several layers of customized composites. At a later time in the composite life cycle, you may deliver the next version of the base composite, which triggers an upgrade cycle for the other applications team and the customer. Note: To use this feature, ensure that you start Oracle JDeveloper in the Default Role mode.