Posts

Showing posts from October, 2010

How to Bulk Delete Messages from Message/Service Operation Monitor in Error Status

The following is how to delete messages in Error status by a delivered way. 1. Run messaging achieve process at PeopleTools>Integration Broker>Service Operation Monitor>Monitoring>Archive Monitor Data. This will archive all the service operations in Done or Cancel status. 2. Run appmsgpurgelive.dms to delete all the service operations in status other than "Done" or "Cancel" including Error. WORKAROUND: You can customize PSAPMSPURGELIVE.DMS. Set where clause in every delete statement at PSAPMSPURGELIVE.DMS. "where IBTRANSACTIONID in (Select IBTRANSACTIONID from PSAPMSGPUBHDR where PUBSTATUS=0 AND PUBLISHTIMESTAMP " " Now you can run the appmsgarch process. =============================================================================== In PT8.48 or above, You can actual use the filter in the service operation monitor to identify service operations in ERROR status. You need to go to the operation instance, publication contract and subcontrac

Interation Broker:The 'IsChanged=Y' flag is always present in the XML's , what are they ? and what do they signify ?

When sending and receiving messages, all blank data values get stripped. As a result, you cannot determine if a field value is blank by definition, or if its value was stripped in the messaging process. The PeopleCode functions - CopyRowset, CopyRowsetDelta and CopyRowsetDeltaOriginal, feature an IsChanged attribute that automatically gets set to identify fields that have been changed. Any field that has been changed displays the attribute IsChanged="Y". Note. The IsChanged attribute applies only to rowset-based messages. It does not apply to nonrowset-based messages, including container messages, or part messages. If you are writing subscription PeopleCode you reference the IsChanged value of the field in the message rowset, as always. However, the blanks appear with the attribute IsChanged="Y".