| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem connecting SAP system using WMB connectivity samples |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bravo |
 Posted: Tue Jul 19, 2011 6:28 am Post subject: Problem connecting SAP system using WMB connectivity samples |
 |
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
Hi All,
I am using SAP connectivity sample to connect to SAP system from my local system.
WIN XP
WMB 7.0.1
SAP ECC 6
I was able to pull BO (MATMAS) from SAP system in Toolkit. Then I tried to deploy bar file and it gave below error
| Code: |
Begin running task [Deploying [SAP_MATMAS05_To_MQFlow.msgflow.generated.bar] to execution group [EXEC2]]
BIP2087E: Broker UUFWMB1I was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Execution group 'EXEC2' received an invalid configuration message. See the following messages for details of the error.
The broker was asked to deploy a message flow which contained properties that were not recognized by the broker. This typically results from a message flow requiring a version or type of node that is not supported by the broker installation.
Check that the message flow is only using properties or nodes that are supported on the broker. Check that all necessary user-defined extensions are installed and that they are of a version that is compatible with the message flow.
BIP3400E: The creation of adapter component 'Inbound_SAP_MATMAS05.inadapter' has failed.
Review previous messages to find out why the error occurred.
BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'org/apache/xpath/XPathAPI.selectNodeList(Lorg/w3c/dom/NodeLjava/lang/String)Lorg/w3c/dom/NodeList... (data of len 102 truncated)'.
This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter 'org/apache/xpath/XPathAPI.selectNodeList(Lorg/w3c/dom/NodeLjava/lang/String)Lorg/w3c/dom/NodeList... (data of len 102 truncated)'.
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 task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation.
|
RFC program id has been created on SAP system and I am using the same RFC program id.
When we tried to test RFC connection in SAP system even before deploying code, it gave error.
Basis team requested me to deployed as the RFC program id will get registered dynamically once the connection get establish. I have limited knowledge on basis side, so I am not sure.
I am under the imperssion, when Basis team creates a new RFC progarm id using SM59, we can test the connection in SAP itself, please correct me if am wrong or do we have to do any special processing to register server program?
I even turned on RFC trace in Adapter connection wizard but no trace file is generating.
please help!!!
_________________
Bravo |
|
| Back to top |
|
 |
| rglack10 |
| Posted: Tue Jul 19, 2011 8:32 am Post subject: |
|
|
Apprentice
Joined: 06 Jul 2011
Posts: 34
|
Hi,
I would suggest patching both the broker toolkit AND runtime to latest 7.0.0.2.
Also, when you create the adapter make sure you are selecting the version of the Webpshere Adapter appropriate for your level of patch. For Toolkit, Runtime 7.0.1 you should be selecting adapter version 7.0.0.1 displayed in the wizard.
When you have done this rebuild the adapter from scratch. It could also be you are not building the adapter correctly using the wizard.. Have you checked all of the properties like default method and message set etc? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 19, 2011 1:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| rglack10 wrote: |
Hi,
I would suggest patching both the broker toolkit AND runtime to latest 7.0.0.2.
Also, when you create the adapter make sure you are selecting the version of the Webpshere Adapter appropriate for your level of patch. For Toolkit, Runtime 7.0.1 you should be selecting adapter version 7.0.0.1 displayed in the wizard.
When you have done this rebuild the adapter from scratch. It could also be you are not building the adapter correctly using the wizard.. Have you checked all of the properties like default method and message set etc? |
Also check the effective level of the broker runtime. If it is still 7.0.0.0 you need to enable 7.0.0.1 (see mqsichangebroker)
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Bravo |
| Posted: Tue Jul 19, 2011 4:27 pm Post subject: |
|
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
Thanks rglack10 and fjb_saper.
I have applied fixpack 2 both runtime and Toolkit. I have ran mqsichangebroker UUFWMB1I -f 7.0.0.2
but no luck
_________________
Bravo |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 19, 2011 7:41 pm Post subject: Re: Problem connecting SAP system using WMB connectivity sam |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Bravo wrote: |
| Code: |
BIP3400E: The creation of adapter component 'Inbound_SAP_MATMAS05.inadapter' has failed.
Review previous messages to find out why the error occurred.
BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'org/apache/xpath/XPathAPI.selectNodeList(Lorg/w3c/dom/NodeLjava/lang/String)Lorg/w3c/dom/NodeList... (data of len 102 truncated)'.
This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter 'org/apache/xpath/XPathAPI.selectNodeList(Lorg/w3c/dom/NodeLjava/lang/String)Lorg/w3c/dom/NodeList... (data of len 102 truncated)'.
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.
|
RFC program id has been created on SAP system and I am using the same RFC program id.
When we tried to test RFC connection in SAP system even before deploying code, it gave error.
Basis team requested me to deployed as the RFC program id will get registered dynamically once the connection get establish. I have limited knowledge on basis side, so I am not sure.
I am under the impression, when Basis team creates a new RFC progarm id using SM59, we can test the connection in SAP itself, please correct me if am wrong or do we have to do any special processing to register server program?
I even turned on RFC trace in Adapter connection wizard but no trace file is generating.
please help!!! |
OK, so first of all stop looking at the connection information. There is nothing in your error or adapter trace that you have published that would point to an error in communications.
Now you need to look at the adapter trace and find out why data length of 102 gets truncated... Something has been defined incorrectly. This needs to be fixed before you can move on. You may want to open a PMR
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
