| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue with build in SAP nodes configuration |
« View previous topic :: View next topic » |
| Author |
Message
|
| Maximreality |
 Posted: Fri Jan 23, 2009 4:20 am Post subject: Issue with build in SAP nodes configuration |
 |
|
Acolyte
Joined: 04 Jun 2004
Posts: 65
Location: Copenhagen
|
I have come across an issue with the broker interaction when sending idocs out of SAP
We are using R3link today (but i also have experience using the websphere adapters for SAP)
Our setup in SAP today are as follows:
One partner profile called MQLINK01 that are configured with alle our inbound and outbound idoc message types (about 20 different)
They are all using the same receiver port called MQL01CL700
The receiver port has an RFC destination called MQLINK
The RFC destination has a program ID called MQL.RS6.700.O.1
This means that all idocs end up on one R3LINK component, then distributes messages to the different queues based on the configuration (pretty much similar to what the websphere adapter for SAP does)
-------------------------------------------------
My experience with the build in SAP adapter nodes is that this scenario is not possible (or maybe i am doing something wrong)
For example we have one interface called ZORGPUBZ, which uses 2 idoc message types (but the same basic type)
For this i created 2 adapter configurations, one for each message type. I also have 2 messagesets.
IDoc values to identify selected operation:
Adapter2 has: ReceivingPartner=WEBSPHRSAP; MessageType=ZORGPUBZ02; MessageCode= ;MessageFunction=;
Adapter3 has: ReceivingPartner=WEBSPHRSAP; MessageType=ZORGPUBZ03; MessageCode= ;MessageFunction=;
The RFC program ID is that same on both configurations: WEBSPHRSAPADPT
My message flow has 2 SAPInput nodes.
When i send out two test messages, one ZORGPUBZ02 and one ZORGPUBZ03 i get an error like this for ZORGOUBZ03 (ZORGOUBZ02 is processed sucessfully):
| Quote: |
( BDHLUW03461.MULTI ) An adapter error occurred during the processing of a message. The adapter error message is ''commonj.connector.runtime.SelectorException: For the IDoc type SapZorgpub01, operation key=ZORGPUBZ03 not found using the application-specific information {Create={MsgType=ZORGPUBZ02, MsgCode=, MsgFunction=}} verify apropriate combination of MsgType,MsgCode, MsgFunction is set in SapZorgpub01, application-specific information.
For the IDoc type SapZorgpub01, operation key=ZORGPUBZ03 not found using the application-specific information {Create={MsgType=ZORGPUBZ02, MsgCode=, MsgFunction=}} verify apropriate combination of MsgType,MsgCode, MsgFunction is set in SapZorgpub01, application-specific information.
''.
This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter ''commonj.connector.runtime.SelectorException: For the IDoc type SapZorgpub01, operation key=ZORGPUBZ03 not found using the application-specific information {Create={MsgType=ZORGPUBZ02, MsgCode=, MsgFunction=}} verify apropriate combination of MsgType,MsgCode, MsgFunction is set in SapZorgpub01, application-specific information.
For the IDoc type SapZorgpub01, operation key=ZORGPUBZ03 not found using the application-specific information {Create={MsgType=ZORGPUBZ02, MsgCode=, MsgFunction=}} verify apropriate combination of MsgType,MsgCode, MsgFunction is set in SapZorgpub01, application-specific information.
''.
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. |
Based on this it seems that no matter what i send out using my current partner profile the idocs will alway reach the same adapter instance.
My assumption is then that only the "ReceivingPartner" values is used to determine which adapter instance receives the message, hence i would need a unique ReceivingPartner value for each MessageType that i want to send out of SAP?
Am i completely off the track or ? |
|
| Back to top |
|
 |
| SOLOHERO |
| Posted: Mon Jun 15, 2009 12:21 am Post subject: |
|
|
Centurion
Joined: 01 Feb 2007
Posts: 107
|
Hi mate....i may not help you..
I think you might be of help....
1. What version of MessageBroker Toolkit are you using.
2. I assue you are using 6.1, which comes with inbuilt SAPrequest and SAP input node.
3. Do you have SAP adapters seperatley.....
4. what is the transportation is it via MQ.
Thanks....
_________________
Thanks |
|
| Back to top |
|
|
| Maximreality |
| Posted: Sun Jun 21, 2009 11:56 pm Post subject: |
|
|
Acolyte
Joined: 04 Jun 2004
Posts: 65
Location: Copenhagen
|
| SOLOHERO wrote: |
Hi mate....i may not help you..
I think you might be of help....
1. What version of MessageBroker Toolkit are you using.
2. I assue you are using 6.1, which comes with inbuilt SAPrequest and SAP input node.
3. Do you have SAP adapters seperatley.....
4. what is the transportation is it via MQ.
Thanks.... |
you need to be using latest version of the toolkit and runtime environment(6.1.0.4)
We are using the build in SAP nodes
The SAP adapter component is now part of the broker environment, so you do not need to have a seperate SAP adapter installed (you only need to pay the license afaik).
The communication between SAP and SAP adapter is either tRFC og qRFC (a SAP protocol over tcp/ip) |
|
| Back to top |
|
|
| SOLOHERO |
| Posted: Mon Jun 22, 2009 5:07 am Post subject: |
|
|
Centurion
Joined: 01 Feb 2007
Posts: 107
|
thank you.....
_________________
Thanks |
|
| 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
|
|
|
|
