cancel
Showing results for 
Search instead for 
Did you mean: 

Problem while using WMB SAP Adapter on AIX

Former Member
0 Kudos

Hi,

I have the MB Toolkit 6104 installed on my Windows machine. Also the Broker runtime is 6104.

I have configured the SAP Adapter to connect to one of the SAP systems and I am able to send the IDOCs to it correctly.

But now, when I am trying to deploy the BAR (created on Windows System) to an AIX system, I am getting the following error in the trace logs:

2009-10-26 10:04:57.968528 6169 >> } ImbMessage::ReadCursor::~ReadCursor MyApplicationFlow#FCMComposite_1_3 ComIbmSAPRequestNode , MyApplicationFlow.SAP Request

2009-10-26 10:04:57.968560 6169 >> ImbRequestTemplateNode::processMessageAssemblyToFailure file:/build/S610_P/src/DataFlowEngine/TemplateNodes/ImbRequestTemplateNode.cpp line:411 message:2231.BIPv610 MyApplicationFlow#FCMComposite_1_3 ComIbmSAPRequestNode 'Caught exception and propagating to failure terminal' , MyApplicationFlow.SAP Request

2009-10-26 10:04:57.968560 6169 >> UserTrace BIP2231E: Error detected whilst processing a message in node 'MyApplicationFlow.SAP Request'.

The message broker detected an error whilst processing a message in node 'MyApplicationFlow.SAP Request'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.

See the following messages for details of the error.

2009-10-26 10:04:57.968572 6169 >> requestData file:MbErrorHandler.java line:122 message:3442.BIPv610 'Caught Throwable' , 'SAP Request', 'MyAdapter.outadapter'

2009-10-26 10:04:57.968572 6169 >> RecoverableException BIP3442E: An exception occurred in adapter node ''SAP Request'', which is using adapter component ''MyAdapter.outadapter''..

This message broker node ''SAP Request'' attempted to process a message and communicate with an EIS using an adapter component ''MyAdapter.outadapter''. An error occurred during this processing.

See the following messages for details of the error.

2009-10-26 10:04:57.968584 6169 >> throwableToMbException file:MbErrorHandler.java line:247 message:3450.BIPv610 'Caught Throwable' , 'JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'

JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [sapjcorfc (A file or directory in the path name does not exist.)]. java.library.path [/opt/IBM/mqsi/6.1/jre15/ppc64/bin:/opt/IBM/mqsi/6.1/jre15/ppc64/bin:/opt/IBM/mqsi/6.1/jre15/ppc64/bin/classic:/usr/mqm/java/lib64:/opt/IBM/mqsi/6.1/xml4c/lib64:/usr/mqm/lib64:/opt/IBM/mqsi/6.1/ODBC64/V5.3/lib:/opt/IBM/mqsi/6.1/xlxpc/lib64:/opt/IBM/mqsi/6.1/lib:/opt/IBM/mqsi/6.1/bin:/usr/lib:/lib:/home/d64wps1/sqllib/lib:/opt/mqm/java/lib:/home/snukavar/lib:/opt/IBM/mqsi/6.1/jre15/ppc64/bin/j9vm:/home/d64wps1/sqllib/lib:/usr/lib]

'

2009-10-26 10:04:57.968584 6169 >> RecoverableException BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is ''JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'

JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [sapjcorfc (A file or directory in the path name does not exist.)]. java.library.path [/opt/IBM/mqsi/6.1/jre15/ppc64/bin:/opt/IBM/mqsi/6.1/jre15/ppc64/bin:/opt/IBM/mqsi/6.1/jre15/ppc64/bin/classic:/usr/mqm/java/lib64:/opt/IBM/mqsi/6.1/xml4c/lib64:/usr/mqm/lib64:/opt/IBM/mqsi/6.1/ODBC64/V5.3/lib:/opt/IBM/mqsi/6.1/xlxpc/lib64:/opt/IBM/mqsi/6.1/lib:/opt/IBM/mqsi/6.1/bin:/usr/lib:/lib:/home/d64wps1/sqllib/lib:/opt/mqm/java/lib:/home/snukavar/lib:/opt/IBM/mqsi/6.1/jre15/ppc64/bin/j9vm:/home/d64wps1/sqllib/lib:/usr/lib]

''.

This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter ''JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'

JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [sapjcorfc (A file or directory in the path name does not exist.)]. java.library.path [/opt/IBM/mqsi/6.1/jre15/ppc64/bin:/opt/IBM/mqsi/6.1/jre15/ppc64/bin:/opt/IBM/mqsi/6.1/jre15/ppc64/bin/classic:/usr/mqm/java/lib64:/opt/IBM/mqsi/6.1/xml4c/lib64:/usr/mqm/lib64:/opt/IBM/mqsi/6.1/ODBC64/V5.3/lib:/opt/IBM/mqsi/6.1/xlxpc/lib64:/opt/IBM/mqsi/6.1/lib:/opt/IBM/mqsi/6.1/bin:/usr/lib:/lib:/home/d64wps1/sqllib/lib:/opt/mqm/java/lib:/home/snukavar/lib:/opt/IBM/mqsi/6.1/jre15/ppc64/bin/j9vm:/home/d64wps1/sqllib/lib:/usr/lib]

''.

Inspect the diagnostic information that is provided by the adapter. Further diagnostic information might be written to user trace. Inspect user trace for further information.

The Broker Run-time is also 6104.

The mqsireportproperties is showing correct path of the directory where librfccm.so, libsapjcorfc.so and sapjco.jar files are placed.

The File permissions are correct (755).

The PATH and CLASSPATH variables have been set correctly.

The File Transfer mode was binary.

I wonder Is it because I have used Windows machine to configure the SAP Adapter (i.e., I have used sapjcorfc.dll and librfc32.dll while configuring the Adapter).

Please help me resolving my problem.

Thanks,

Sandeep

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Sandeep were able to resolve the issue? We have having a similar issue.