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 » WebSphere Message Broker (ACE) Support » How to Search & Replace in a entire XML Payload

Post new topic  Reply to topic
 How to Search & Replace in a entire XML Payload « View previous topic :: View next topic » 
Author Message
naio
PostPosted: Mon Nov 12, 2012 6:28 am    Post subject: How to Search & Replace in a entire XML Payload Reply with quote

Voyager

Joined: 08 Nov 2012
Posts: 82

Hi to Everyone again!
I have a requirement to complete, In fact I was ask for an opinion about a problem.
Nowadays, ALL the WMB services make a call when the start and when they finish to a Flow that populate a Logging system, in that way the client have the input message of the flows, and the eventual errors.

The problem, is that they are populating the Logging System with ALL the message, the Passwords are included, so they want yo ofuscate those passwords before they arrive to the logging system.
The thing is that only 20 services of a total of 400, have passwords and the password located in the XML are not always in the same place, so a massive search and replace should be done.
I want opinions on how to process the XML in search for password in the most performance way. The flow that take the info and send it to the Logging system, is separated from the main flow (via MQ Queues).
One option that I have considered was to make a XSL transformation that runs on all the payload message, I assume that this is no the best way, maybe something with ESQL....

I am looking for options!

THANKS YOU MASTERS!!!!!


Ignacio


PD: under WMB 7.0
_________________
"God is in his heaven all's right with the world"
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Mon Nov 12, 2012 6:31 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Use log4j to log only the information you want.

We turn off logging in Prod as HIPAA and PCI are primary confidentiality motivators.

If we have a problem transaction, our Customer Service people run the problem in Test environment which has logging turned on by default.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
naio
PostPosted: Mon Nov 12, 2012 6:58 am    Post subject: Reply with quote

Voyager

Joined: 08 Nov 2012
Posts: 82

The problem, is that the message is Compress and then send to the Logging System, so the Passwords should be ofuscated before compressed. That´s way Log4J can´t be used.

_________________
"God is in his heaven all's right with the world"
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Mon Nov 12, 2012 7:00 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

There are ways to address the situation where you could use log4j; but, nevertheless, you can use Flow Order then the SELECT statement in a Compute node to overwrite the sensitive info before you send it to the logger.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
naio
PostPosted: Mon Nov 12, 2012 7:27 am    Post subject: Reply with quote

Voyager

Joined: 08 Nov 2012
Posts: 82

I am gonna trie that.
Thanks!
_________________
"God is in his heaven all's right with the world"
Back to top
View user's profile Send private message
kash3338
PostPosted: Mon Nov 12, 2012 8:50 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

For all 400 flows other than those 20 sensitive flows you can use the existing logging framework and for the 20 flows you can custom design the existing framework wherein only the required details are captured from the input message and not the complete payload.

One more point here is, what is the use of logging the payload? The approach largely depends on the requirement. Is it used for replay/repost? Then no point of ignoring some fields, else is it it just for tracking? Then you can just track the required context data.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » How to Search & Replace in a entire XML Payload
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.