Enabling the Oracle BAM Integration in Oracle B2B

Programmatically Accessing Instance Message Data 24-3 ■ Section 24.3.3, Executing Queries Remotely Using Weblogic.jar

24.3.1 Handling a Large Number of Messages

If the query returns a large number of messages then the weblogic.socket.MaxMessageSizeExceededException may occur. To recover from this issue, increase weblogic.MaxMessageSize, and pass -Dweblogic.MaxMessageSize=100000000 in the client command line. This parameter setting will allow you to receive 100 MB messages. For example: java -cp .:ORACLE_HOMEwlserver_10.3serverlibwlthint3client.jar:SOA_HOME soamodulesoracle.soa.b2b_11.1.1b2b.jar -Dweblogic.MaxMessageSize=100000000 TestInstanceMsg

24.3.2 Handing Large Payloads

Rather than return the payload itself, a large inbound or outbound payload will return as a reference to the location of the payload. For example: tmpGlobalChips_1_custnonxml_largepayload.dat9844C4341297D3EB7B60000011A0CC9D .dat See Appendix A, Handling Large Payloads for more information about how Oracle B2B handles large payloads.

24.3.3 Executing Queries Remotely Using Weblogic.jar

If while using weblogic.jar and executing queries remotely you may see classpath issues for Oracle WebLogic Server, and the java.lang.ClassNotFoundException:weblogic.security.subject.Abstr actSubject exception. To recover, execute queries using wlthint3client.jar. For example: java -cp .:ORACLE_HOMEwlserver_10.3serverlibwlthint3client.jar:SOA_HOME soamodulesoracle.soa.b2b_11.1.1b2b.jar TestInstanceMsg 24-4 Oracle Fusion Middleware Users Guide for Oracle B2B Part VI Part VI Appendixes This part contains the following appendixes: ■ Appendix A, Handling Large Payloads ■ Appendix B, Setting B2B Configuration Properties in Fusion Middleware Control ■ Appendix C, Back-End Applications Interface ■ Appendix D, Exception Handling ■ Appendix E, Self Service Utility Protocols, Identifications, Security Specifications, and Parameters 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.