Have you ever seen this one?  In a non-production HR environment (Tools 8.47 in this case), you change an employee's Phone # (or any other personal data) and it publishes the PERSON_BASIC_SYNC message to your non-Production Financials environment.  Everything looks great on the HR side in Message Monitor, but on the Financials side there's no evidence the message ever existed.  Nothing in message monitor at all.  Check the gateway config to make sure the node points to the correct environment and it all checks out.  Nothing in the log files either.

I hate to admit it, but I honestly couldn't figure this one out and had to get help via Customer Connection.  Here's what finally solved it: 

Each integration broker transaction has a Publication ID (PUBID).  When the PUBID already exists in the target environment, Integration Broker decides the message is already there so there's nothing to do, it's all good, and no need to worry anybody with an error message.

So why would the PUBID already exist in the target environment?  Because we cloned the target environment (Financials) from production more recently than we cloned the source environment (HRMS).  The Financials PUBID's were ahead of HRMS, so Integration Broker assumed everything HRMS published already existed in Financials.

Fortunately there are a couple of easy fixes.  The one I recommend is to always run APPMSGPURGEALL.DMS in the cloned environment before you bring up the app server.  This will give you a clean start on your integration broker transactions.

But if you have integration broker transactions you don't want to loose, here's another option:

First, go to the message monitor in the target environment and hit the Message Instances tab.  Search for the Channel Name associated with your message, and figure out what the most recent PUBID is.

Then pull up your favorite SQL tool, log on to your source environment, and run this SQL:

update PSAPMSGPUBINST set PUBID = <PUBID from the previous step + 1> where CHNLNAME = <Channel name of your message> 

That'll bump up the message counter and you should be good to go from that point forward.

Sorry but I haven't tried this in PTools 8.48 or later so you're on your own there, although I'm sure running APPMSGPURGEALL.DMS in your non-production environment will fix this specific issue.

Comments (0)

Write comment

Name

Email

Website

Title

Comment

Write the displayed characters

Add Comment