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 Index » General IBM MQ Support » IDOC tracing

Post new topic  Reply to topic
 IDOC tracing « View previous topic :: View next topic » 
Author Message
hos82
PostPosted: Mon Jun 10, 2019 4:45 am    Post subject: IDOC tracing Reply with quote

Newbie

Joined: 10 Jun 2019
Posts: 4

Hi guys, is there any tool or way to trace an IDOC that goes thru an MQ infrastructure? That being, follow it thru the logs?
I've been reading that it should be done on the SAP side, which makes sense, but is there any way to do it, aside from being configured on SAP?
SOrry if it is a dumb question, never worked with SAP before, and my manager says there are a couple of tools from MQ side to do it, but never found them
Thanks in advance.

HEctor
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Jun 10, 2019 5:18 am    Post subject: Re: IDOC tracing Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

hos82 wrote:
Hi guys, is there any tool or way to trace an IDOC that goes thru an MQ infrastructure? That being, follow it thru the logs?


Same way you'd trace anything else going through an MQ infrastructure. MQ doesn't parse payload so it doesn't act differently for an IDOC, an XML document or a serialized COBOL copybook.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Mon Jun 10, 2019 5:38 am    Post subject: Re: IDOC tracing Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9394
Location: US: west coast, almost. Otherwise, enroute.

hos82 wrote:
SOrry if it is a dumb question, never worked with SAP before, and my manager says there are a couple of tools from MQ side to do it, but never found them
Thanks in advance.

Not a dump question at all. A thorough business process audit would ponder MQ's involvement.

Think of MQ as a pipe through which messages flow. MQ is not aware of, or concerned with, message content (application data payload).

MQ offers a set of API's that allow an application to connect to a queue manager server, open a queue, get or put a messages, and more.

Several trace options are available to capture MQ involvement, including an application-level trace, a stand-alone trace-route utility to capture message routing (message arrival, departure on MQ channels).

Search google for 'mq trace' for details.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
hos82
PostPosted: Mon Jun 10, 2019 6:36 am    Post subject: Reply with quote

Newbie

Joined: 10 Jun 2019
Posts: 4

Ok, thanks for your answers, and if you want to log the IDOC header? That would be a SAP side config right?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Jun 10, 2019 11:48 am    Post subject: Reply with quote

Grand High Poobah

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

hos82 wrote:
Ok, thanks for your answers, and if you want to log the IDOC header? That would be a SAP side config right?

That is not a SAP Config. It is standard in SAP.
Now if the app consuming/receiving the IDOC or producing the IDOC is not SAP, you may want to have it log this too.

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
hos82
PostPosted: Mon Jun 10, 2019 12:19 pm    Post subject: Reply with quote

Newbie

Joined: 10 Jun 2019
Posts: 4

Ok, yeah, I meant seeing the IDOC header in the MQ logs
Back to top
View user's profile Send private message
bruce2359
PostPosted: Mon Jun 10, 2019 12:24 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9394
Location: US: west coast, almost. Otherwise, enroute.

hos82 wrote:
Ok, yeah, I meant seeing the IDOC header in the MQ logs

MQ rules apply: if the message persistence attribute value is set to PERSISTENT at mqput time, then the entire message content (MQ headers, plus application data payload) will be written to MQ logs.
Google 'mq+idoc+header' for details
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Jun 11, 2019 4:27 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

bruce2359 wrote:
hos82 wrote:
Ok, yeah, I meant seeing the IDOC header in the MQ logs

MQ rules apply: if the message persistence attribute value is set to PERSISTENT at mqput time, then the entire message content (MQ headers, plus application data payload) will be written to MQ logs.
Google 'mq+idoc+header' for details


I would not be so cavalier about advising people to read the queue manager transactional logs, especially while the queue manager is using them.

I also question the value of these logs as an audit trail or diagnostic tool if circular logging is in use.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » IDOC tracing
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.