ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Interchange Server + AdaptersmySAP Adapter Error

Post new topicReply to topic Goto page Previous  1, 2
mySAP Adapter Error View previous topic :: View next topic
Author Message
pribuan
PostPosted: Sun Dec 21, 2008 10:32 pm Post subject: Reply with quote

Newbie

Joined: 07 Dec 2008
Posts: 9

oh.., thanks for this infor. We have designed it in the same way. Only drawback s we are not having access to SAP to view the status of the IDocs. The SAP team says for all the 9000 IDocs., they see the same status : 41.
My guess is., the 300 records that have errored out would have got processed in the second attempt. Cause., when the Idocs have errored out, they would have status as 03. 03 denotes that the records are waiting at the port. Since it is at the port, the adapter would have attempted to pick it up again, and reprocessed it successfully. And hence these guys see all the Idocs successful.

There is another I see now. How have you handled the ARCHIVE Queue in your implementation ?

The Archive queue has reached the max depth and is now not allowing the rest of the IDocs to get processed. There are 4000 Idocs at the Port waiting to get processed. I will have to purge the ARCHIVE queue now.

Is there any other way to handle the Archive queue or would we have to write an automated task to purge the queue when it reaches it max depth ?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Dec 22, 2008 1:47 pm Post subject: Reply with quote

Grand Poobah

Joined: 18 Nov 2003
Posts: 19758
Location: LI,NY

pribuan wrote:
oh.., thanks for this infor. We have designed it in the same way. Only drawback s we are not having access to SAP to view the status of the IDocs. The SAP team says for all the 9000 IDocs., they see the same status : 41.
My guess is., the 300 records that have errored out would have got processed in the second attempt. Cause., when the Idocs have errored out, they would have status as 03. 03 denotes that the records are waiting at the port. Since it is at the port, the adapter would have attempted to pick it up again, and reprocessed it successfully. And hence these guys see all the Idocs successful.

There is another I see now. How have you handled the ARCHIVE Queue in your implementation ?

The Archive queue has reached the max depth and is now not allowing the rest of the IDocs to get processed. There are 4000 Idocs at the Port waiting to get processed. I will have to purge the ARCHIVE queue now.

Is there any other way to handle the Archive queue or would we have to write an automated task to purge the queue when it reaches it max depth ?

Note. Idocs that error out at the port get a different status and need manual intervention for reprocessing. You may have the program for reprocessing scheduled... W?(L|B?)05 will show you the status of the different Idocs grouped by status (and /or time)

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
pribuan
PostPosted: Tue Jan 06, 2009 7:30 pm Post subject: Reply with quote

Newbie

Joined: 07 Dec 2008
Posts: 9

Thanks fjb_saper.

We are now planning to manually resend those idocs. And hope its goin to work successfully.

Any idea of how to set the Expiry parameter found in the RHUTIL header while the message is written to the ARCHIVE Queue itself. If we set this, we need not purge the Queue often. The message will get expired after the time period we mention in that parameter.

Any idea how we ll have to set it ?

OR, how have you handle the ARCHIVE Queue in your implementation?
Back to top
View user's profile Send private message
jamesyu
PostPosted: Wed Aug 24, 2011 7:07 am Post subject: Where to find the max. number of connections for SAP Reply with quote

Acolyte

Joined: 31 Jan 2007
Posts: 70

pribuan wrote:
I find a parameter in the connector Config file - "MaxNumberOfConnections" which describes "The maximum number of concurrent interactions possible between the connector and the SAP application"

This has a value 1. You adviced me to change this to 5 or was it something else ?


Where is the exact location for this "connector config file"? I need to increase the max number of SAP connections in the pool
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum IndexWebSphere Interchange Server + AdaptersmySAP Adapter Error
Jump to:



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
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.