Archive for October, 2012


Other Possible Problems
– Cannot find service operation in Service Operation Monitor.
– Service operations are being processed in an incorrect order.
– Service operation is not created.
– Unable to ping a node.
– Queue is PAUSED.

Cannot Find Service Operation in Service Operation Monitor – possible cause:
– filtering is set in the Service Operation Monitor.

Service Operations are Being Processed in an Incorrect Order – possible cause:
– Queue was partitioned and the resulting subqueues do not match what was assumed for the ordering of the service operations.

Service Operation Instance not Created – possible cause:
– service operation is inactive.

Unable to Ping a Node – possible causes are:
– The web server for the Gateway is down.
– The Gateway is not configured properly.
– The application server for the node is down.
– The Gateway URL is incorrect; verify that the URL is correct.
Copy URL in browser address; you should see:
PeopleSoft Integration Gateway
PeopleSoft Listening Connector
Status: ACTIVE

Queue Is PAUSED – possible cause:
– some Queues are delivered as paused. Change the status to Run for the service operations to process from New to Working.

Advertisements

Subscription Process Problems:
– Subscription contract is not created.
– Subscription contract is in NEW status.
– Subscription contract is in STARTED status.
– Subscription contract is in WORKING status.
– Subscription contract is in ERROR status.
– Subscription contract is in EDIT status.

Subscription Contract Is not Created – possible causes are:
– No handler exists for the service operation.
– Service operation handler is missing method.
– Queue routing rules not set up properly.

Subscription Contract Is in NEW Status – possible causes are:
– Application Server is down.
– Pub/Sub processes not configured on Application Server domain.
– The Subscription Dispatcher has crashed or has been brought down.
– Receiving queue is paused.
– Receiving node is paused.
– Previous service operation had errors or timed out.
– No row was inserted into PSAPMSGSUBPRCID, To insert a row enter the following SQL statement in your Query tool use the following statement: insert into PSAPMSGSUBPRCID values(0)

Subscription Contract Is in STARTED Status – possible causes are:
– Subscription Handler is down.
– Target component is not valid.

Subscription Contract Is in WORKING Status – possible causes are:
– Subscription Handler crashed while processing message.

Subscription Contract Is in ERROR Status – possible causes are:
– 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.
– Service operation handler PeopleCode errors exist.
– Application data errors exist.

Subscription Contract Is in EDIT Status – possible cause is
– XML was edited and is not yet resubmitted for processing.

Publication Process Problems:
– Publication contract is not created.
– Publication contract is in NEW status.
– Publication contract stays in RETRY status.
– Publication contract is in WORKING status.
– Publication contract is in TIMEOUT status.
– Publication contract is in ERROR status.

Publication Contract Is Not Created – possible causes are:
– No publication PeopleCode exists.
– Publication PeopleCode is incorrect.
– No outbound routings exists for the service operation.
– User initiating a publication does not have access to the Service Operation.

Publication Contract Is in NEW Status – possible causes are:
– Sending node is not set as Active.
– Sending queue is paused (not in Run status).
– Sending domain is not active.
– Previous service operation had a status of Retry, Error, or Timeout.
– Publication Dispatcher crashed or was brought down.
– Publication Handler process type has only one instance (Min Instances = 1, Max Instances = 1), while a minimum of 3 is needed for normal operation.
– After an unsuccessful ping, a row may be added to the table PSNODESDOWN; which will hold up the message queue; query the table PSNODESDOWN.
The application server log file may show the statement: PSPUBDSP_dflt.1844 (1) [08/28/12 00:20:16](4) (PublishSubscribe): PublicationContractManager::IsNodeAvailable(): publication contract synchronization activated for queue XXXXX

Publication Contract Stays in RETRY Status – possible causes are:
– The remote node cannot be pinged successfully; the publication contract will be processed when the remote node comes back up.
– No publication handler is available, either because it crashed or it was brought down.
– Receiving Node URL is incorrect in integrationGateway.properties file.

Publication Contract Is in WORKING Status – possible causes are:
– The publication handler processing the contract is on another machine and either the machine or the domain is down. Processing should continue when the pub/sub system on the other machine comes back up.
– Single threading on the application server is slowing processing.

Publication Contract Is in TIMEOUT Status – possible causes are:
– An exception occurred on the target application server (look in APPSRV.LOG file for details); verify that:
– The reply is incorrectly routed; check Gateway for correct machine address of target node.
– Bad XML syntax.

Publication Contract Is in ERROR Status – possible causes are:
– Receiving node user profile not authorized to service operation.
– Inbound routing is not set up on the receiving system.
– Service operation is not active on the receiving system.
– Service operation has not been granted security access on the receiving system.
– The source node is not defined in the target database.
– Handler PeopleCode is bad.
– Remote application server is down.
– Receiving Node is not defined in the integrationGateway.properties file.
– Receiving PeopleSoft node has not been added to single signon.
– Service operation version on target is not active.

Operation Instances Problems:
– Service operation instance stays in NEW status.
– Service operation instance stays in STARTED status.
– Service operation instance stays in WORKING status.

Service Operation Instance Stays in NEW Status – possible causes are:
– The domain on which a pub/sub server resides is Inactive.
– The Application server is down.
– Pub/sub services are not configured on the Application Server domain. Check the server status via Psadmin to make sure PUBSUB services are running.
– The Message Dispatcher crashed or was brought down.
– The item is not at the top of the queue; all service operations with the same queue or subqueue are in the same queue.
– The node status is in Paused state.
– Missing data from PSIBPROFILE (Document:1108466.1E-IB:Messages Stuck In New After Tools 8.50 Upgrade)
– PUBSUB processes in-memory queues got out of sync with the database because of running a purging script without shutting down the app server domain ()
– Only one domain is configured for PUBSUB services but in the psappsrv.cfg file it is set as a slave domain. The Slave Mode should be set to 0 if not implementing static master/slave.
– In PT 8.51+ the domain status page shows one active domain and the Slave indicator is Sync Template. There needs to be a master domain. Recreate the domain in PSAdmin.

Service Operation Instance Stays in STARTED Status – possible causes are:
– All Message Handlers crashed or were brought down; processing will resume when Message Handlers come back up.
– The Message dispatcher processing the message is on another machine, and either the machine or the application server domain is down.
– Application server domain was created using the developer template. Recreate using small, medium or large.

Service Operation Instance Stays in WORKING Status – possible causes are:
– Message Broker Handler crashed.
– The Message Handler processing the message is on another machine, and either the machine or the application server domain is down.
– The Message Handler working on the message is blocked. The service will time out, and the Message Dispatcher will retry the message.
– Application server domain was created using the Developer template. Recreate using small, medium or large.

Unlock PeopleSoft Objects All at Once

Change control is used in Application Designer to lock definitions and track history changes for each object. Change control can be activated through Application Designer using Tools > Change Control > Administrator.

After few good size projects, you can easily have hundreds if not thousands of locked objects. Attempting to unlock the objects one by one is very time consuming, so here is a way to speed up the process.

Locked objects are stored on PSCHGCTLLOCK table. Here is how PeopleSoft describes the table:

This table contains a a row for every object that is currently locked by any user. When the user requests to lock an object in the Application Designer, first this table is searched to see if the object is locked by another user. If it is not found, a row is inserted into the table. When the user requests to unlock an object, the row in this table is deleted.

From the description above, I would feel safe enough to assume that if you want to unlock objects, just delete them from this table! Here is an example to delete by operator ID, you can also delete by object name or object type.

— deletes locked objects by user id.
DELETE FROM pschgctllock
      WHERE oprid = :userid;

Instead of clicking  Help > About People Tools from App designer,

We can modify Configuration Manager settings (Screenshot 1) for related People Tools as below to display Database Name in App designer (Screenshot 2).

This will be helpful while we open multiple instances of App Designer.

Here is the code which will add a Welcome Message in PIA Header.

Open Application Package PT_BRANDING, Application Class BrandingBase, Method getIframeHeaderHTML.
– look at the beginning of the function.

Replace:

Local string &greeting = ” “;

With

/* – Adding user and environment to branding */
Local string &greeting = %UserId | ” on ” | %DbName;

/* – End */

– look also in this function for the line “&greeting = &Portal.Homepage.Greeting;”

and comment it like this:

/* – commenting this line, so the message remains the customized one, not the one set-up from the Homepage personalize Content
&greeting = &Portal.Homepage.Greeting;
– End */

Note:
This customization is present in HR Development environment. You may also want to refer below Oracle SR.
Reference: E-PIA: How to Add a Welcome Message in the Application Portal Header [ID 1098274.1]