= Cannot Find Service Operation in Service Operation Monitor =
* Service operation instance stays in WORKING status. * Service operation instance stays in STARTED status. * Service operation instance stays in NEW status. * Service operations are being processed in an incorrect order. * Cannot find service operation in Service Operation Monitor. Possible cause is that the XML was edited and is not yet resubmitted for processing. * Service operation handler PeopleCode errors exist. * Queue property if Ordered enables subscription contracts to go in random order, which causes FULLSYNC service operations to error out when the transaction is subscribed before the header. * Subscription Handler crashed while processing message. * No row was inserted into PSAPMSGSUBPRCID, To insert a row enter the following SQL statement in your Query tool use the following statement: * Previous service operation had errors or timed out. * The Subscription Dispatcher has crashed or has been brought down. * Pub/Sub processes not configured on Application Server domain. * Queue routing rules not set up properly. * Service operation handler is missing method.
* No handler exists for the service operation. * Subscription contract is in EDIT status. * Subscription contract is in ERROR status. * Subscription contract is in WORKING status. * Subscription contract is in STARTED status. * Subscription contract is in NEW status. Possible subscription process problems include:\\ * Service operation version on target is not active. * Receiving PeopleSoft node has not been added to single signon. * Receiving Node is not defined in the integrationGateway.properties file. * The source node is not defined in the target database. * Service operation has not been granted security access on the receiving system. * Service operation is not active on the receiving system. * Inbound routing is not set up on the receiving system. * Receiving node user profile not authorized to service operation. * The reply is incorrectly routed check Gateway for correct machine address of target node. * An exception occurred on the target application server (look in APPSRV.LOG file for details) verify that: * Single threading on the application server is slowing processing. Processing should continue when the pub/sub system on the other machine comes back up. * The publication handler processing the contract is on another machine and either the machine or the domain is down. * Receiving Node URL is incorrect in integrationGateway.properties file. * No publication handler is available, either because it crashed or it was brought down. * The remote node cannot be pinged successfully the publication contract will be processed when the remote node comes back up. * After an unsuccessful ping, a row may be added to the table PSNODESDOWN which will hold up the message queue query the table PSNODESDOWN. * Previous service operation had a status of Retry, Error, or Timeout. * Publication Dispatcher crashed or was brought down. * No outbound routings exists for the service operation. * Publication contract is in ERROR status. * Publication contract is in TIMEOUT status. * Publication contract is in WORKING status. * Publication contract stays in RETRY status. Possible publication process problems include:\\ Troubleshooting guidance for publication process, subscription process, and other possible problems. Then reopen the properties dialog and proceed to set the module.= Troubleshooting PT 8.48 PT 8.49 Integration Broker =.Enter all other properties, select enabled, and OK to save the properties.Select the module version with which tasks will be executed. Typically this is the profile configured with ASG_ROLE (see Attach a Role to a PeopleSoft End User for more information). Provide an existing PeopleSoft user name with appropriate access to Zena PeopleSoft Adapter. Contact PeopleSoft administrator to find out the JOLT Port Number. Select any desired log level DETAIL, DEBUG or DEFAULT.Įnter the name or IP address of the PeopleSoft Application server.Įnter the JOLT Port number on which PeopleSoft Application server listens.
#Peoplesoft report node type update
0 kommentar(er)
