| Author |
Message
|
| gugs |
 Posted: Thu Apr 09, 2009 5:24 am Post subject: SAP Adaptor |
 |
|
Apprentice
Joined: 10 Jul 2007
Posts: 30
|
I am getting the following error when I try to deploy a message flow containing SAP Outboud Adaptor: BIP3412E: An attempt to set the property 'setRFCTraceLevel' to value '1 (SAP JCo Java API logging)' failed.
I have not set any RFC Trace Level in the adaptor. The broker states the following: The current version of the adapter installed on the runtime component had a problem setting a property given in the adapter component configuration file. The most likely reason for this is a mismatch between the Message Broker Toolkit and the runtime component levels.
I am on:
Toolkit Version: 6.1.0.3, Build id: 6.1.0.3-IFix003-20090305_1223
Broker: BIP8996I: Version: 6103; CMVC Level: S610-FP03 DH610-L81015
Any Ideas anyone?
_________________
Thanks in advance |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Thu Apr 09, 2009 5:52 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
|
| Back to top |
|
|
| Pythor |
| Posted: Thu Nov 19, 2009 6:53 am Post subject: Was this problem ever resolved? |
|
|
Newbie
Joined: 10 Aug 2006
Posts: 1
|
Was this issue ever resolved? I have got exactly the same problem.
Regards
Peter |
|
| Back to top |
|
|
| JonathanHill |
| Posted: Mon Feb 22, 2010 7:30 am Post subject: |
|
|
Novice
Joined: 30 Jan 2009
Posts: 13
|
Try checking the registered entities against EISProviders: -
mqsireportproperties <BROKER_NAME> -c EISProviders -o AllReportableEntityNames -r
The last time I had "An attempt to set the property 'setRFCTraceLevel' to value 1" error, when toolkit and broker runtime versions were inline, it was down to the SAP JCO library paths not being specified: -
mqsichangeproperties <BROKER_NAME> -c EISProviders -o SAP -n jarsURL -v <PATH_TO_LIBRARIES>
mqsichangeproperties <BROKER_NAME> -c EISProviders -o SAP -n nativeLibs -v <PATH_TO_LIBRARIES>
Hope this helps... |
|
| Back to top |
|
|
| crossland |
| Posted: Mon Mar 22, 2010 8:39 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
| JonathanHill wrote: |
Try checking the registered entities against EISProviders: -
mqsireportproperties <BROKER_NAME> -c EISProviders -o AllReportableEntityNames -r
Hope this helps... |
The following command would be better:
mqsireportproperties <broker> -c EISProviders -o SAP -r |
|
| Back to top |
|
|
| hari.g |
| Posted: Mon Mar 22, 2010 11:43 pm Post subject: |
|
|
Newbie
Joined: 22 Mar 2010
Posts: 5
|
Please chk the library and jar paths and try to redeploy after restarting the broker as this error would be as a result of discrepency between the actual path and path to which broker is pointing
Regards
HARI |
|
| Back to top |
|
|
| ein |
| Posted: Wed Mar 24, 2010 2:03 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2009
Posts: 108
|
Hi Gugs,
when you configuring the SAP adapter, You might not have checked the RFC trace level . By default it is one. You can increase the up to 8 for Debug.
Please make sure that , The password you have given in the adapter should be in CAPS for SAP Systems.Double check with SAP BASIS guys on this. |
|
| Back to top |
|
|
|
|
