Monitoring SOA Composite Application Recent Instances and Faults

Managing SOA Composite Applications 8-1 8 Managing SOA Composite Applications This chapter describes how to manage SOA composite applications, including initiating a test instance of an application; managing faults, policies, and instance states; and testing SOA composite applications. This chapter includes the following topics: ■ 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 ■ Section 8.5, Recovering from SOA Composite Application Faults at the SOA Infrastructure Level ■ Section 8.6, Recovering from SOA Composite Application Faults in the Application Home Page ■ Section 8.7, Automating the Testing of SOA Composite Applications ■ Section 8.8, Managing SOA Composite Application Policies ■ Section 8.9, Exporting a Running SOA Composite Application ■ Section 8.10, Grouping SOA Composite Applications into Partitions ■ Section 8.11, Disabling and Enabling BPEL and BPMN Business Monitors

8.1 Initiating a SOA Composite Application Test Instance

This section describes how to initiate a test instance of a deployed SOA composite application. To initiate a SOA composite application test instance: 1. Access this page through one of the following options: Note: The procedures in this guide describe how to access Oracle Enterprise Manager Fusion Middleware Control pages from the SOA Infrastructure menu, soa-infra icon in the navigator, SOA Composite menu, and SOA Partition menu. You can also access many pages from the Farm home page. For more information, see Section 2.2.6, Navigating to the SOA Infrastructure or SOA Composite Application Home Page. 8-2 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite

2. If the composite includes multiple services, the Test button has a drop-down list

to select the service to test. The Test Web Service page for initiating an instance appears. This page provides many options for initiating an instance. At a minimum, you must specify the XML payload data to use in the Input Arguments section. The WSDL file and end point URL are populated automatically based on the service you selected to test. The end point URL is derived from the WSDL and can be overridden to invoke that service at a different location. If the service selected has multiple ports, a drop-down list is displayed. Otherwise, the port of the current service is displayed. 3. Accept the default values for these fields or provide values appropriate to your test environment.

4. If you change the WSDL file, click Parse WSDL to reload the WSDL file.

If the WSDL URL does not contain the revision number, it is processed by the default composite application. For example, if there are two revisions of a From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... From the Composite Menu... 1. Select Home. 2. Select the Deployed Composites tab. 3. In the Composite section, select a specific SOA composite application. 4. At the top of the page, click Test. 1. Under soa-infra, select a specific SOA composite application. 2. At the top of the page, click Test. 1. Select Test Service client . Note: The Test button is disabled in the following situations: ■ The SOA composite application revision is stopped or retired. ■ There are no web services available for the application. Only composites having services with web service bindings can be tested from this page.