| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WebSphere Message Broker Adapter for SAP v6.1.3 |
« View previous topic :: View next topic » |
| Author |
Message
|
| JonathanHill |
 Posted: Fri Jan 30, 2009 1:29 am Post subject: WebSphere Message Broker Adapter for SAP v6.1.3 |
 |
|
Novice
Joined: 30 Jan 2009
Posts: 13
|
Hi
I'm looking for advice as to the 'best practice' when using the SAP Adapter (SAPInput) Node for Message Broker v6.
My problem is that on the previous version of the SAP Adapter (v5) I could create multiple messageset projects (for each iDoc) and control the connection to SAP via the Adapter's cfg file.
In version 6, of the SAP Adapter, the concept of the 'Adapter' (and a single cfg file) has been replaced with SAPInput and SAPRequest nodes for each iDoc. However once the iDoc discovery phase has built your messageset it also builds an iDoc specific connection to SAP (.inadapter file).
The result is that, after downloading 10 iDoc definitions, I have 10 projects (each with a single messageset - which is fine) but each project also has its own (.inadapter) connection file despite all the iDocs coming from the same SAP environment.
Is this the way multiple iDoc definitions should exist in v6?
In theory this isn't too bad apart from the fact that the .inadapter files aren't text-files so I can't maintain them via scripts. So if I move from a SAP test environment to a SAP live environment I have to manually change each .inadapter file...not ideal.
Any advice appreciated. |
|
| Back to top |
|
 |
| jhosie |
| Posted: Fri Jan 30, 2009 5:30 am Post subject: |
|
|
Apprentice
Joined: 12 May 2005
Posts: 28
|
Do you use a different RFC program ID for each of the IDOCs?
If so, then you do want a separate .inadapter for each. to solve the problem of moving from test to production, 6.1.0.3 does help here. The SAPConnection configurable service is introduced.
That can be used to override the connection properties for specific adapters. So you would still need one Configurable Service defined for each adapter but they are administered from command line or config manager proxy API so can be scripted.
This is a good place to start. http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=/com.ibm.etools.mft.doc/ac66170_.htm
If you need to use the same program ID for all IDOCs, then you should run the Adapter connection wizard once, select all IDOCS and therefore create a sinlgle .inadapter and MsgSet for the entire set of IDOCs. |
|
| Back to top |
|
|
| JonathanHill |
| Posted: Fri Jan 30, 2009 6:07 am Post subject: |
|
|
Novice
Joined: 30 Jan 2009
Posts: 13
|
Yes, the requirement is to use a seperate RFC Program ID for each iDoc.
I did notice 'mqsicreateconfigurableservice' which appeared to provide a solution to the .inadapter file 'issue', as this takes priority over the file's parameters, but was unsure as to whether or not I was missing something about how the new adapter works.
Thanks for this link, I'll read and digest.  |
|
| 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
|
|
|
|
