Invoking References in One-Way SSL Environments in Oracle JDeveloper

6-12 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite To resolve this issue, the callbackServerURL property must be passed at the reference binding level in the composite.xml file. This explicitly indicates the value of the callback URL for the given reference invocation. If the client composite is running in an SSL-managed server, then the callback defaults to SSL. reference name=Service1 ui:wsdlLocation=http:localhost:8000soa-infraservicesdefaultAsyncSecondB PELMTOMBPELProcess1.wsdl interface.wsdl interface=http:xmlns.oracle.comAsyncAsyncSecondBPELMTOMBPELProcess1wsdl .interfaceBPELProcess1 callbackInterface=http:xmlns.oracle.comAsyncAsyncSecondBPELMTOMBPELProce ss1wsdl.interfaceBPELProcess1Callback binding.ws port=http:xmlns.oracle.comAsyncAsyncSecondBPELMTOMBPELProcess1wsdl.endp ointbpelprocess1_client_epBPELProcess1_pt location=http:localhost:8000soa-infraservicesdefaultAsyncSecondBPELMTOM bpelprocess1_client_ep?WSDL wsp:PolicyReference URI=oraclewss_username_token_client_policy orawsp:category=security orawsp:status=enabled wsp:PolicyReference URI=oraclewsaddr_policy orawsp:category=addressing orawsp:status=enabled . property name=callbackServerURLhttp:localhost:8000property . binding.ws . callback binding.ws port=http:xmlns.oracle.comAsyncAsyncSecondBPELMTOMBPELProcess1wsdl.endp ointbpelprocess1_client_epBPELProcess1Callback_pt wsp:PolicyReference URI=oraclewss_username_token_service_policy orawsp:category=security orawsp:status=enabled binding.ws callback . reference

6.7 Configuring Security for Human Workflow WSDL Files

If the WSDL files for human workflow services are not exposed to external consumers, then set the flag that exposes the WSDL to false for each of the services: expose-wsdlfalseexpose-wsdl For more information, see Oracle Fusion Middleware Developers Guide for Oracle Web Services. 7 Monitoring SOA Composite Applications 7-1 7 Monitoring SOA Composite Applications This chapter describes how to monitor instances and faults in SOA composite applications. This chapter includes the following topic: ■ Section 7.1, Monitoring SOA Composite Application Recent Instances and Faults For more information, see Section 1.2.2, Introduction to SOA Composite Applications.

7.1 Monitoring SOA Composite Application Recent Instances and Faults

You can monitor SOA composite application recent instances and faults from the SOA composite application Dashboard page. This page provides a high-level overview of the most recent state of the application. To monitor SOA composite application recent instances and faults: 1. Access this page through one of the following options:

2. Click Dashboard if it is not selected.

The upper part of the Dashboard page displays the following details: ■ A summary of composite lifecycle states at the top of the Dashboard page, such as the number of running instances, total instances, and mode of the composite active or retired. ■ Recent SOA composite application instances, including the instance ID, name, conversation ID, state for example, faulted or completed, and start time. ■ Recent faults and rejected messages, including the error message, whether you can recover from the fault, the time at which the fault occurred, the fault location service, service component, or reference, the instance ID of the SOA composite application, and a link to log files describing the fault. From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... 1. Select Home. 2. Select the Deployed Composites tab. 3. In the Composite section, select a specific SOA composite application. 1. Under soa-infra, select a specific SOA composite application.