Oracle FTP Adapter Configuring Properties for Oracle JCA Adapters

33-28 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite The following examples show how to specify the endpoint properties in the composite.xml file in Oracle JDeveloper: Table 33–10 Oracle JCA Adapters Endpoint Properties Direction InboundOutbound Property Name Description Inbound activationInstances This property increases the number of polling worker threads for any inbound JCA resource adapter. It is only meant to help increase concurrency scalability for adapters that do not natively support multithreading. Since most of the adapters included with Oracle Fusion Middleware natively support multithreading, this setting is mostly useful to third party custom JCA adapters, which do not natively support multithreading. Set this property to the number of threads required for a particular JCA service endpoint. Inbound UseWorkManager By default, JCA adapters use the standard Oracle Fusion Middleware Oracle WebLogic Server work manager for starting polling worker threads. However, if you want a particular JCA service endpoint to use a custom user-defined work manager, then this property enables you to specify the name of a custom work manager. The work manager is only used to start the JCA Service endpoint for which this property has been defined. Inbound rejectUncorrelatedMes sages When native correlation is used to correlate an inbound asynchronous message with a previous outbound message by way of defining a callback interface for a reference or by a midprocess receive in BPEL, the JCA framework normally tries to post the message to the composite, whether the inbound message can be correlated or not. By setting this property to true, the JCA framework rejects a message, which cannot be correlated when native correlation is active. Inbound jca.retry.count Indicates the maximum number of retries before rejection. Inbound jca.retry.interval Indicates the time interval between retries measured in seconds. Inbound jca.retry.backoff Indicates the retry interval growth factor positive integer. Inbound jca.retry.maxInterval Indicates the maximum value of retry interval; that is, a cap if backoff is greater than 1. Outbound jca.retry.count Indicates the maximum number of retries before throwing a retryable error condition back to the invoking service engine. Outbound jca.retry.interval Indicates the time interval between retries measured in seconds. Outbound jca.retry.backoff Indicates the retry interval growth factor positive integer. Outbound jca.retry.maxInterval Indicates the maximum value of retry intervals; that is, a cap if the backoff is greater than 1. Outbound jca.retry.maxPeriod Indicates the maximum total retry period. Retries do not occur longer than the value specified in this parameter. Configuring Service and Reference Binding Components 33-29 ■ Example 1: Specifying Endpoint Properties - Inbound ■ Example 2: Specifying Endpoint Properties - Outbound Example 1: Specifying Endpoint Properties - Inbound service name=Inbound interface.wsdl interface=http:xmlns...wsdl.interfaceInbound_PortType binding.jca config=Inbound_db.jca property name=jca.retry.interval5property property name=jca.retry.interval1property property name=jca.retry.backoff2property property name=jca.retry.maxInterval6property binding.jca service Notice that the inbound property jca.retry.maxPeriod is not supported like it is in the outbound direction. Example 2: Specifying Endpoint Properties - Outbound reference name=Outbound interface.wsdl interface=http:xmlns...wsdl.interfaceOutbound_PortType binding.jca config=Outbound_jms.jca property name=jca.retry.count5property property name=jca.retry.interval1property property name=jca.retry.backoff2property property name=jca.retry.maxInterval6property property name=jca.retry.maxPeriod30property binding.jca reference

33.1.3 Changing the Endpoint Reference and Service Key for Oracle Service Registry Integration

If a reference binding component of the SOA composite application is integrated with Oracle Service Registry OSR, you can change the endpoint reference and service key in the General section of this page. The UDDI ServiceKey field automatically displays the value of binding.ws property=oracle.soa.uddi.serviceKey from the composite.xml file if you selected to use UDDI for runtime resolution of the endpoint. You can edit the UDDI ServiceKey field after the SOA composite application has been deployed to either: ■ Change the value as needed. ■ Add it to a composite that did not use UDDI for runtime endpoint resolution. The Endpoint Address field represents the endpoint location as defined with the ws.binding endpointURI property in the composite.xml file. The Endpoint Address field is not filled in after the SOA composite application has been deployed, but can override the endpoint location in the concrete WSDL. The endpoint location order of precedence is as follows: ■ Dynamically set the binding oracle.soa.uddi.serviceKey at runtime in the UDDI ServiceKey field. ■ Dynamically set the binding property endpointURI at runtime in the Endpoint Address field. 33-30 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite ■ Use the binding property value for oracle.soa.uddi.serviceKey in the composite.xml file viewable and editable in Oracle Enterprise Manager Fusion Middleware Control. ■ Use the binding property value for endpointURI in the composite.xml file viewable and editable in Oracle Enterprise Manager Fusion Middleware Control. ■ Use the location specified in the concrete WSDL. Figure 33–1 provides shows both fields. Figure 33–1 Endpoint Reference and Service Key Properties

1. In the UDDI ServiceKey field, change the service key to use during runtime.

2. In the Endpoint Address field, enter the endpoint address to use during runtime.

You can edit both fields. The value for one field is selected and used based on what you selected in the UDDI Deployment Options dialog during design time. The changes to these fields are persisted in the composite.xml file during runtime. For information about design-time tasks such as how to publish a business service, create a connection to the UDDI registry, and configure a SOA project to invoke a service from the registry, see Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. For information about how to set the inquiry URL during runtime, see Section 3.1, Configuring SOA Infrastructure Properties.

33.1.3.1 Configuring Caching of WSDL URLs

Caching of endpoint WSDL URLs occurs by default during runtime. If an endpoint WSDL URL is resolved using the orauddi protocol, subsequent invocations retrieve the WSDL URLs from cache, and not from OSR. You can increase the amount of time that the endpoint WSDL URL is available in cache for inquiry by the service key with the UddiCacheLifetime property. This property invalidates the cache at specified time intervals. The default value is 86400 seconds. The minimum value is 300 seconds. To configure endpoint caching of WSDL URLs: Configuring Service and Reference Binding Components 33-31

1. From the SOA Infrastructure menu, select Administration System MBean

Browser .

2. Select Application Defined MBeans oracle.as.soainfra.config Server: soa_

server1 SoaInfraConfig soa-infra Attributes. 3. Click the UddiCacheLifetime property on the right side of the page. 4. Enter a value.

5. Click Apply.

33-32 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite 34 Monitoring Service and Reference Binding Components 34-1 34 Monitoring Service and Reference Binding Components This chapter describes how to monitor service and reference binding components included in SOA composite applications. This chapter includes the following topics: ■ Section 34.1, Monitoring Binding Component Instances and Faults ■ Section 34.2, Monitoring Binding Component Rejected Messages For more information, see the following documentation: ■ Section 1.2.5, Introduction to Binding Components for conceptual details about binding components ■ Part XII, Administering Oracle B2B for details about Oracle B2B ■ Oracle Fusion Middleware Developers Guide for Oracle SOA Suite

34.1 Monitoring Binding Component Instances and Faults

You can monitor instances and faults for all binding components included in SOA composite applications. To monitor binding component instances and faults: 1. Access this page through one of the following options:

2. Click Dashboard if it is not selected.

3. Select a specific service or reference in the Services and References section.

4. If you select a service that is a JCA adapter or web service, the Dashboard page

displays the following details: ■ A graphic representation of the total incoming messages and faults since server startup. 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. 34-2 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite ■ Recently rejected messages, including the message name, time of the fault, and the type of fault business or system.

5. If you select a service that invokes a SOA composite application through a remote

RMI call known as direct binding, the Dashboard page displays similar details as described in Step 4. Direct binding enables SOA composite applications to be invoked through an API that supports transaction and security propagation across JVMs. The word Direct is displayed in the header to indicate that this is a direct binding component. However, no Polices and Properties tabs are available for direct binding components. Monitoring Service and Reference Binding Components 34-3 6. If you select a reference, the Dashboard page displays the following details: ■ A graphic representation of the total outgoing messages and faults since server startup. ■ Recent faults, including the time of the fault and the type of fault business or system. Reference binding components are only available for JCA adapters and web services.

34.2 Monitoring Binding Component Rejected Messages

You can monitor rejected messages for all binding components included in a SOA composite application. To monitor binding component rejected messages:

1. Access this page through one of the following options:

2. Select a service or reference in the Services and References section.

3. Click Faults and Rejected Messages.

The Faults and Rejected Messages page shows the list of faults and rejected messages, including details such as the error message, time of the fault, and the 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.