| Author |
Message
|
| LuckySkunk |
 Posted: Wed Nov 03, 2004 6:24 pm Post subject: MQ R3 Link Settings (Inbound) |
 |
|
Novice
Joined: 27 Sep 2004
Posts: 10
|
Hi all,
Anyone out there dealed with the linkage between MQ and R3 using MQ R3 Link adapter before. Need a few pointers on the inbound side. I need only to configure the smqDestConf and in.ini files or are there more to this such as writing an interface program in C or Java? Do I create separate .ini and start smqsi process for each inbound queues?
Appreciate any contribution. Thanks.
_________________
Don't bomb us, man ... we're just IT guys |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Nov 03, 2004 8:44 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Yes you need a different .ini and process for each inbound queue. Question is why do you have multiple inboud queues? It makes no difference to SAP which Idoc type is getting transmitted.
The only reason we have 2 inbound queues is about priority and the possibility to process fast messages and batch messages in different queues....
Enjoy  |
|
| Back to top |
|
|
| LuckySkunk |
| Posted: Wed Nov 03, 2004 9:13 pm Post subject: |
|
|
Novice
Joined: 27 Sep 2004
Posts: 10
|
Thanks for tips. How about the smqDestConf and in.ini files. Is that only thing I need to configure to enable the IDoc to come in thru the Link?
Thanks again.
_________________
Don't bomb us, man ... we're just IT guys |
|
| Back to top |
|
|
| Hema30 |
| Posted: Thu Nov 04, 2004 11:22 am Post subject: hi |
|
|
Acolyte
Joined: 02 Aug 2003
Posts: 59
|
Multiple inbound sever instances are needed if there are multiple SAP clients.Each client may get messages on one queue .
Thanks
Hema |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 04, 2004 2:32 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| LuckySkunk wrote: |
| How about the smqDestConf and in.ini files. Is that only thing I need to configure to enable the IDoc to come in thru the Link? |
You would wish. Of course you need to configure SAP ALE layer to accept/send the messages that will flow through the link.
Make sure the SAP login information is in your files to be able to register to SAP. Then the Idoc header information (EDI_DC40) needs to match the SAP ALE setup....
Enjoy  |
|
| Back to top |
|
|
| LuckySkunk |
| Posted: Thu Nov 04, 2004 5:55 pm Post subject: |
|
|
Novice
Joined: 27 Sep 2004
Posts: 10
|
Thanks again for ur prompt response. I have configured the ALE part as well as the RFC.
The RFCs in SAP is liken to channels in MQ. and I know for a fact that things would work just fine if I use only 1 port number with a single RFC for both inbound and outbound. But if the RFCs is equivalent to Channels, shouldn't I be creating a Port for inbound and another for outbound? The outbound one, I'm clear on how it gets integrated with the smqso process but the inbound one I'm not sure. Is it the smqDestConf and in.ini files the only place where I need to configure besides what is needed to be configured at the SAP side?
Thanks for your help thus far.
_________________
Don't bomb us, man ... we're just IT guys |
|
| Back to top |
|
|
| LuckySkunk |
| Posted: Thu Nov 04, 2004 6:01 pm Post subject: |
|
|
Novice
Joined: 27 Sep 2004
Posts: 10
|
Thanks Hema30 for the tip. We only deal with one client but the team lead has decided to segregate the different type of messages, so that is why we are using more than 1 queue and a few server processes.
_________________
Don't bomb us, man ... we're just IT guys |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Nov 05, 2004 2:32 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You need to realize that in fact you have 2 different processes going to SAP.
One is the inbound SAP communication. This uses a logon type SAPLOGON. It does not need the more sofisticated approach of the registered communication.
The outbound from SAP is really more complex. You need to register your server with SAP (registered communication). This will allow SAP to send messages to your MQ-Link Server. In SAP you need as well to specify the gateway host and gateway service to which you have registered (SM59). This allows SAP to route the message to the application server you have registered to in case your instance has multiple apps servers (most have).
So yes if you want to make an approximation you could liken those 2 communication ways to mq channels, however they are quite different in essence as well as in the way they authenticate.
On the inbound side once you have authenticated to SAP (client user passwd sapgw## langu) you can communicate with SAP and send whatever is on the queue.
Now for what you send to be accepted and processed you need to have SAP configured (WE20) to accept messages from the source you are sending and how to process them. Part of this configuration is done in SAP, part of it is done in the IDOC header (EDI_DC40) by the sending system, and both parts need to match.
Enjoy |
|
| Back to top |
|
|
|
|
