|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
SAP to WebSphere MQ: one-way (for IDoc) pattern |
« View previous topic :: View next topic » |
Author |
Message
|
smeunier |
Posted: Wed Sep 05, 2012 12:16 pm Post subject: SAP to WebSphere MQ: one-way (for IDoc) pattern |
|
|
 Partisan
Joined: 19 Aug 2002 Posts: 305 Location: Green Mountains of Vermont
|
We are currently using the external WebSphere Adapter mySap.com with Message Broker V6.0 and I'm looking at prototyping migrating to Message Broker V7 using internal adapter nodes. The Data distribution SAP to WebSphere MQ: one-way (for IDoc) pattern seems to be a good first step as we have multiple partners which receive the data from the current external adapter in BO xml format.
As a first step, I wanted to see if I could get data from SAP to the Message Broker. I configured the Inbound adapter made available via the pattern and was able to validate that we had successfully made a good RFC connection.
Apparently on bar deployment, it insures that a RFC connection can be made before a deployment can be successful. In making the connection, the connectivity parameters were the same as used in the external adapter.....simple enough.
The problem came, when trying to do a RFC connection test from SAP and it showed that the RFC program id was not registered and the connectivity test failed.
I turned RFC trace on, and it looks like the initial adapter connection was made at deployment, but it looks like the connection is dropped after that has been done. Simply put, it looks like the connection started and stopped after deployment. Is there some other step that needs to be done to keep this long lived? As a further test, I released a IDOC from SAP, with RFC trace on, and there was not tracing that occurred, which confirms that the RFC communications link was no longer active.
I have looked and verified that I have performed the necessary steps, which it appears I have, but I have dead ended in trying to figure this out. Thought?
Also, with external adapter logging can occur. I have enabled logging and error collection, but have seen not evidence of messages. Documentation implies logging only on success. Is everything else and error? What about informational? This goes back to the first issues. Other than doing and RFC trace, how can I confirm that the adapter is up/running/connected?
Thanks in adavnce |
|
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
|
|
|
|