| Author |
Message
|
| ajayvizag |
 Posted: Wed Mar 07, 2012 12:19 am Post subject: Problems with SAP Adapter |
 |
|
Apprentice
Joined: 20 Feb 2009
Posts: 31
|
Hi All,
We are observing a scenario where in the SAP Inbound Adapter stops listening to events on SAP after a n/w issue i.e if there was a n/w issue with SAP server, the WMB SAP Inbound Adapter stops listening to events after the n/w issue is resolved. We are currently mitigating this by retarting the SAP Adapter flow.
Please share your thoughts on this.
Thanks,
Ajay. |
|
| Back to top |
|
 |
| mqsiuser |
| Posted: Wed Mar 07, 2012 12:51 am Post subject: Re: Problems with SAP Adapter |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
Write a (korn-)shell script that gets triggered by cron (e.g. every 5 minutes).
The script should check if the adapter (process) is running, and if not (try to) start it (the SAP adapter).
You check processes on unix with e.g. "ps -eaf | grep sapadapter" (or similiar).
Evaluate based on this result(-string) (it is either empty or it is there) whether the adapter is running or not (and trigger the restart if necessary).
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| ajayvizag |
| Posted: Wed Mar 07, 2012 1:01 am Post subject: |
|
|
Apprentice
Joined: 20 Feb 2009
Posts: 31
|
Thanks, for your reply. The point i am trying to highlight here is, that the adapter is up and running while there a n/w issue or even when the n/w issue is sorted. But after a n/w glitch it stops listening on events(Adapter is running but is not picking any events from SAP). After we restart the Adapter it works fine. I am curently working on how to identify a n/w problem and stop & start the adapter.
What i want to know from the experts is whether this is a known problem with the Adapter where though it is up and running after a n/w issue with SAP it stops listening to events when the n/w is up.
Thanks,
Ajay. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Wed Mar 07, 2012 1:21 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
Listeners have a timeout and that is usually configured like 5 Minutes (or 300 seconds  ) ... probably you might want to search for that property and increase it to e.g. 60 Minutes...
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 07, 2012 2:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
mqsiuser - I think you are still mixing up the old SAP adapter with the Broker built-in adapter.
ajavizag, you should be able to find configuration information on how to resolve this in the info center. I've not done a lot with the SAP adapter so I don't know what there is off the top of my head. |
|
| Back to top |
|
|
| ajayvizag |
| Posted: Fri Mar 09, 2012 12:59 am Post subject: |
|
|
Apprentice
Joined: 20 Feb 2009
Posts: 31
|
| Thanks for your reply, i havent come across a property that sets the time out on listeners. Has anyone faced such a scenario? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Mar 09, 2012 6:14 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| ajayvizag wrote: |
| Thanks for your reply, i havent come across a property that sets the time out on listeners. Has anyone faced such a scenario? |
| Quote: |
Inbound calls are supported by the ALE interface using asynchronous event notification. For the inbound call, the adapter acts as an RFC server and listens for ALE events from the SAP application. The adapter uses an event recovery table to manage the inbound events. The AEP interface of the WebSphere SAP adapter is used for both inbound and outbound processing. For inbound processing, it polls for events in SAP, converts them into business objects, and sends the event data as business objects to Message Broker.
In WebSphere Adapter for SAP Software V7, inbound synchronous processing of RFC-enabled functions is known as the BAPI callout or synchronous RFC callout. By using the Wait parameter before calling the BAPI Commit parameter, you can control whether the SAP Adapter waits for SAP to commit updates synchronously, or issues a commit and then returns while the SAP commit occurs asynchronously.
Message flows can implement both one-way and synchronous BAPIs that can be called from an SAP system. One-way operations are implemented with an SAPInput node, which can represent one or more BAPIs; synchronous operations are implemented with the combination of an SAPInput node and an SAPReply node, which can reside on different message flows.
SAP nodes can get SAP connection details from either the adapter component or a configurable service. By using configurable services, you can change the connection details for adapters without the need to redeploy the adapters.
SAPConnection configurable service
connectionIdleTimeout
The number of seconds for which a connection can be idle before it is closed by WebSphere Message Broker to effectively maintain the connection pool. The default value for this property is 0 (zero) seconds, indicating that no timeout occurs.
New connections to SAP are opened with different user IDs, therefore do not set this property to zero if you are using identity propagation.
retryInterval
Specifies the time interval (in milliseconds) between attempts to restart the event listeners. This property applies only to .inadapter files.
You can set this property to a positive integer. The default value is an empty string, which indicates that behavior is controlled by the .inadapter component.
|
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
