Introduction to the Lifecycle State of SOA Composite Applications

Introduction and Concepts 1-21 ■ Manage their lifecycle and associated approvals using repeatable processes. ■ Manage their performance in production, and inform prospective consumers of services for better design-time decisions. SOA Governance Suite provides Oracle SOA Suite and Oracle BPM Suite users with options to specify and automate a complete lifecycle for applications and their components for example, planning, design, implementation, testing, staging, production, changes, and retirement. For more information about administering the lifecycle states of a SOA composite application and SOA governance, see the following sections: ■ Section 8.1, Initiating a SOA Composite Application Test Instance ■ Section 8.2, Managing the State of Deployed SOA Composite Applications ■ Section 8.3, Monitoring and Deleting SOA Composite Application Instances from the Application Home Page ■ Section 8.4, Monitoring and Deleting SOA Composite Application Instances at the SOA Infrastructure Level ■ Oracle Fusion Middleware User Guide for Oracle Enterprise Repository ■ Oracle Fusion Middleware Integration Guide for Oracle Enterprise Repository ■ Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository

1.4.3.4 Introduction to SOA Composite Application Automated Testing

You can create, deploy, and run test cases that automate the testing of SOA composite applications. Test cases enable you to simulate the interaction between a SOA composite application and its references before deployment in a production environment. Test suites consist of a logical collection of one or more test cases. Each test case contains a set of commands to perform as the test instance is executed. The execution of a test suite is known as a test run. Each test corresponds to a single SOA composite application instance. Instances generated by the execution of these tests are distinguished as test instances by a little yellow box next to their instance ID, as shown in Figure 1–6 . The test suite framework provides the following features: ■ Uses emulations to simulate the behavior of components with which your SOA composite application interacts during execution. Instead of invoking a specific component, you can specify a response from the component. ■ Uses assertions to validate data during process execution. For information about designing test cases for SOA composite applications, see Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

1.4.3.5 Introduction to Partitioning of the SOA Infrastructure

You can deploy SOA composite applications into separate sections of the SOA Infrastructure known as partitions. Deploying to partitions enables you to logically group SOA composites and perform bulk lifecycle management tasks on large numbers of composites. Partitioning is similar to the concept of domains in the 10.1.x releases of Oracle BPEL Process Manager. However, note that you cannot perform specific configuration tasks on partitions, such as restricting login access to a specific partition or configuring partitions such as configuring threading. At least one partition is required for deploying SOA composite applications. A default partition named default is automatically included with Oracle SOA Suite. 1-22 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite Once you create a partition, you can perform the following tasks: ■ Deploy SOA composite applications into the partition using Oracle Enterprise Manager Fusion Middleware Control, Oracle JDeveloper, WebLogic Scripting Tool WLST commands, or ant commands. ■ Access the partition and its deployed composites through the navigation tree. ■ Perform the following bulk lifecycle management tasks on the composites in a specific partition: – Start all composites – Shut down all composites – Undeploy all composites – Retire all composites – Activate all composites – List all composites For more information, see Section 8.10, Grouping SOA Composite Applications into Partitions.

1.5 Administration for Application Developers

If your role is that of an application developer, manage and test SOA composites using a combination of Oracle JDeveloper and Fusion Middleware Control. See the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite to develop SOA composite applications with Oracle JDeveloper, and refer to the following sections to deploy, monitor, and initiate a test instance of the composite application with Oracle Enterprise Manager Fusion Middleware Control: ■ Chapter 5, Deploying SOA Composite Applications ■ Chapter 7, Monitoring SOA Composite Applications ■ Section 8.1, Initiating a SOA Composite Application Test Instance To create and model business processes using Business Process Management Notation and Modeling BPMN within Oracle Business Process Management, see Oracle Fusion Middleware Modeling and Implementation Guide for Oracle Business Process Management. Note: Partitions are not associated with a particular state such as started, stopped, activated, or retired. Only the composites within the partition are associated with a particular state. Therefore, you cannot start, stop, activate, or retire a partition.