In the IDE

After you create your application and project, the Application Navigator and SOA Composite Editor should look like this:

The following BPEL process service component files appear in the Application Navigator:

• emptyBPEL.xsd defines a default schema XSD file for the one-way BPEL process service component.
• composite.xml defines the components and attributes of the SOA composite application.
• emptyBPEL.bpel contains a minimal set of activities based upon the process type you selected (for this example, one-way BPEL process). You add syntax to this file when you add activities, create variables, create partner links, and so on.
• emptyBPEL.componentType describes the services and references for the BPEL process.
• emptyBPEL.monitor describes the meta data for the BPEL process monitors.
• emptyBPEL.wsdl defines the input and output messages for the BPEL process flow, the supported client interface and operations, and other features.
• monitor.config defines the deployment parameters for BPEL process monitors.

Double-clicking the BPEL process service component icon in the SOA Composite Editor invokes the Oracle BPEL Designer. The Oracle BPEL Designer enables you to design the contents of your BPEL process by dragging elements (known as activities) into the process and editing their property pages. You can also integrate technology adapters and services, such as human tasks, transformations, notifications, sensors, and business rules into the process.

The Application Overview page guides you as you build a Fusion Web application, to create files and objects and view the status of them.

Copyright © 1997, 2009, Oracle. All rights reserved.