Programmatically Accessing Instance Message Data

A Handling Large Payloads A-1 A Handling Large Payloads This appendix contains the following topics: ■ Section A.1, Handling Large Payloads – Section A.1.1, Introduction to Large Payload Support – Section A.1.2, Large Payloads and 32-Bit Windows PCs – Section A.1.3, Settings for a Large Dataset Scenario A.1 Handling Large Payloads Oracle B2B can handle large payloads through the SOA Infrastructure and JMS internal queues. A.1.1 Introduction to Large Payload Support Inbound Setup Figure A–1 shows the properties to set for inbound cases. Go to Administration Configuration . Figure A–1 Large Payload Size The image shows the following Performance fields: Large Payload Size the default value is 2000000 and Large Payload Directory the default value is tmp. If a composite is deployed to handle the large payload, this is the only configuration needed. If B2B is not delivering the payload to a composite, set Use JMS Queue as default to true, as shown in Figure A–2 . Go to Administration Configuration. A-2 Oracle Fusion Middleware Users Guide for Oracle B2B Figure A–2 Use JMS Queue The image shows the following Generic fields: Use JMS Queue the value shown is true, Use B2B Queue the value shown is false, and Callout Directory the value shown is MyCalloutDir. With Use JMS Queue as default set to true, the payload is delivered to B2B_IN_QUEUE, a JMS-based queue. Outbound Setup Figure A–3 shows the properties to set for the outbound case. Figure A–3 Large Payload Directory The image shows the Large Payload Directory field the default value is tmp. You must also notify B2B that a service engine is sending a large payload. The change involves two steps: The b2b.largePayload property must be set in the BPEL process when sending a large payload to Oracle B2B. For composite samples, which do not handle large payload, there is no change. Code change in Oracle B2B to handle this flag

1. Declare the Variable_largePayload variable in an outbound BPEL process in the

variables section. variable name=Variable_largePayload type=xsd:string

2. In the Assign activity, copy true into the variable.

copy from expression=true to variable=Variable_largePayload copy

3. Assign the variable to b2b.largePayload in the Invoke activity.

bpelx:inputProperty name=b2b.largePayload variable=Variable_largePayload