Purge Runtime Service Operations Monitor Tables
The PeopleSoft system provides a collection of Data Mover scripts that you can run to purge the runtime Service Operations Monitor tables within a database. These scripts reside in the PS_HOME\scripts directory on your file server. There are many reasons or occasions to purge the appmessage tables, especially during an upgrade or other activities life renaming a […]
Continue readingDuplicate Routing Error – Routing xxx already exists. Please select a unique name. (158, 2075)
Routings in PeopleSoft Integration Broker are used to carry a predefined function. A routing definition defines the sending and receiving nodes for a transaction, specifies any inbound and outbound transformations to invoke and defines external aliases. It also defines overrides that the default integration gateway and the default target connector that the local node use to […]
Continue reading
1
Configuring Integration Broker Messaging Between PeopleSoft Instances at Different PeopleTools Levels
There are scenarios especially when doing a PeopleTools upgrade that you might have to establish PeopleSoft Integration Broker messaging between instances running at different PeopleTools levels. Let me give you an example – Say you have the following solutions implemented on PeopleTools 8.50.08: PeopleSoft HCM 9.1, PeopleSoft CRM 9.1, PeopleSoft FMS 9.1, PeopleSoft Portal 9.1 […]
Continue readingRenaming a Default Local Node
There are several situations in which you might need to rename a node definition. PeopleSoft allows you to rename of delete a node because of such reasons. One of the situations where you might need to rename a default local node could be that you created a new instances by copying the database from production. […]
Continue readingIntegration Broker Authentication: Invalid Authentication type (AUTHOPTN) for node PSFT_LM. (158,452)
This issue “Integration Broker Authentication: Invalid Authentication type (AUTHOPTN) for node PSFT_LM. (158,452)” has been documented in Oracle Support as well with ID 1127403.1. The reason for this error is that the two nodes are not able to talk to each other because of different authentication type (hint is in the error – Invalid Authentication […]
Continue reading