Creating an Outbound Adapter Service

8-50 Oracle Fusion Middleware Users Guide for Technology Adapters

13. Click the Automatically Create Input Variable icon that is displayed at the end of

the Input Variable field.

14. Click the Browse Partner Links icon at the end of the Partner Link field.

The Partner Link Chooser dialog is displayed.

15. Select Outbound, and then click OK.

The Invoke dialog is displayed with the Partner Link field populated with the value Outbound.

16. Accept the defaults, and click OK.

17. Click OK.

18. Double-click the Assign activity.

The Assign dialog is displayed.

19. Click the plus icon, and select Copy Operation.

The Create Copy Operation dialog is displayed.

20. Select the variables, and click OK.

21. Click OK in the Assign dialog.

22. Click File, Save All.

8.4.8.7 Deploying with JDeveloper

You must deploy the application profile for the SOA project and the application you created in the preceding steps. To deploy the application profile by using JDeveloper, perform the following steps:

1. Create an application server connection by using the procedure described in

Chapter 2.7, Creating an Application Server Connection for Oracle JCA Adapters.

2. Deploy the application by using the procedure described in

Section 2.8, Deploying Oracle JCA Adapter Applications from JDeveloper.

8.4.8.8 Monitoring Using the Fusion Middleware Control Console

You can monitor the deployed composite by using the Fusion Middleware Control Console. Perform the following steps: 1. Navigate to http:servername:portnumberem. The composite you deployed is displayed in the Application Navigator. Note: When using Oracle JMS Adapter to dequeue from AQ JMS Topics with durable subscriptions, if you notice that the dequeue operation exhibits slow performance, then you can speed up the entire performance by using multiple inbound threads for each adapter service. Oracle JMS Adapter allows multiple inbound threads if you specify an endpoint property adapter.jms.receive.threads. However, note that this workaround is not applicable when using non-durable subscriptions because doing so will result in duplicate messages.