cancel
Showing results for 
Search instead for 
Did you mean: 

How to read PCo notification message as an Input Parameter in MII

fvviviani
Participant
797

Dear experts,

I have defined an XML input Transaction variable in my MII transaction, and I have put as a value a sample of the NotificationMessage outbound from the agent. Then I simply defined a parameterized PCo Query that writes a tag. If I execute the transaction from MII, the whole loop works, as I left some value into the XML nodes corresponding to the tags, but I don't know if this is correct. If I trigger the transaction from the PCo agent, I really believe it's unable to read the input, and it's not using the default value I left inside either. I have seen similar questions here, and this should be the right approach, but still I'm not able to figure out what I am missing.

Also, is it possible to log the Transaction errors somewhere if they are called by PCo? I have flagged the PCo MII destination persistence as "Only Save Transaction in MII if Error Occurs" but I don't understand where it is stored.

I hope this explanation was clear. My setup is quite particular now so I'm not able to share the full NotificationMessage.

Thanks,

Federico

Accepted Solutions (0)

Answers (2)

Answers (2)

Kevin_Hunter
Product and Topic Expert
Product and Topic Expert

Hi Federico,

Yes this functionality does work and is quite a common scenario that is used by a lot of clients.

Its not clear from your description where the issue is happening but break your scenario down into small pieces and test each one to help diagnose the issue.

The first part is to make sure your notification in PCo is arriving in MII. In the Output tab of the notification there is a test delivery button that will send the message. You can then create a simple MII transaction with an XML input variable with one action block that stores this incoming XML to a file.

When you send a test message you should see a XML file being created and see what's inside of it.

The most common issue is not mapping to the correct part of the XML structure.

Hope this helps

Kevin

fvviviani
Participant

Hi Kevin,

I assumed the message was at least arriving, since the agent correctly executes the Transaction in MII when triggered, but I was wrong apparently, since using the Test feature that you indicated I get timed out. To do so, I of course have stopped the agent.

What could be the cause of this timeout?

Thanks,

Federico

Kevin_Hunter
Product and Topic Expert
Product and Topic Expert

Hi Federico,

Now Im confused. In this comment you say it didnt trigger the MII transaction but in the comment to Mike you say it did. The test button uses the same method as when the agent is started so should both be the same.

If your comment to Mike is correct did you receive the correct XML ?

Thanks

Kevin

fvviviani
Participant
0 Kudos

Hi Kevin,

I was not able to trigger the Transaction before, but then I restarted the agent and inserted an Event Logger to log the input XML, which was also correct.

The issue with the testing feature still persists, though.

I hope I have clarified.

Thanks,

Federico

Kevin_Hunter
Product and Topic Expert
Product and Topic Expert
0 Kudos

Which version of PCo are you using (i will see if I can replicate the test button issue)?

If you are receiving the correct XML in MII then the issue is maybe my original suggestion (the mapping of the XML) .

Can you show us the XML you receive and how you map the value from the XML node?

Thanks

Kevin

agentry_src
Active Contributor
0 Kudos

One could set the default Transaction Persistence to Always in the System Parameters in SAP MII, then the results of the Transaction will be retained in the Transaction Manager (in System Administration), but only for whatever the retention period defined in System Parameters (8 or 24 hours or whatever it was set to). This may give you enough insight to determine the actual function of the transaction. You might also add some event loggers in the transaction which writes information to the NW Log (see the Log Viewer in System Administration). But leaving the Transaction Persistence at Always is not good for long term functioning. It adds significant amounts of content to NW database. So when you are done troubleshooting, set it back to On Error.

Let us know your progress in troubleshooting and we can take a few further steps to determine what is working or not.

Cheers, Mike

fvviviani
Participant

Hi Mike,

Yes, I have done exactly what you said, and I was able to see that Notifications from PCo were arriving correctly to my MII Transaction. So now the situation is that everything seems to be working, except for the test Notification feature, that gets always timed out. Does this make any sense?

Thanks!

Federico

agentry_src
Active Contributor
0 Kudos

Hi Federico,

It really does not make much sense to me, but I suspect Kevin is a better resource for solving this issue. But without more insight into how you have configured your test, I don't know what else to tell you. Can you provide a screenshot or two? Or alternatively save the PCo Input XML in a file (use XML saver). Create the path such as "web://<project name>/CM/PCo"&datefromxmlformat(datenow, "yyyyMMddHHmmss")&".xml" and the content from your notification. Then look under the Web tab for your file. You might have to create the CM folder, but I think that happens automagically. Then view your content as saved.

Regards, Mike