Wikipedia lists an Associate Array as: In computer science, an associative array, map, or dictionary is an abstract data type composed of a collection of (key,value) pairs, such that each possible key appears at most once in the collection.

PeopleSoft does not come with this type of data type so I have created an Application Package to allow for the creation of key/value pair storage. By downloading and importing the following project you will be able to reference the associative array class and create collections of key/value pairs.

 Examples: import MYLIB_ASSOC_ARRAY:* &pairs = create MYLIB_ASSOC_ARRAY:ASSOC_ARRAY(); &pairs.set( "key", "value" ); &keyValue = &pairs.get( "key" ) &keyExists = &pairs.exists( "key" ); &pairs.unset( "key" ); &keys = &pairs.getKeys(); &pairLen = &pairs.len(); &keysFor = &pairs.keysForValue( "value" ); &mergePairs = create MYLIB_ASSOC_ARRAY:ASSOC_ARRAY(); &mergePairs.set( "key2", "value2" ); &mergePairs.merge( &pairs, true ); 

by melban

PSChrome is a Chrome extension to help improve the user experience associated with everyday tasks in PeopleSoft. End users, developers and administrators will find this tool enhances their user experience.

Current Features:

• Remember login information
• Process Monitor: quick links, automated actions and auto-refresh
• Integration Brokers: auto-refresh, 1-click domain restart, passive IB error monitoring
• Generate passwords for User Profiles
• Page mini toolbar: quick field information, page/component information, log management
• PIA visualization and Favorites enhancements
• PeopleCode/SQL Trace log analytics

by melban

 All Processing Suspended: Restart OPRID=PS, RUNID=PS, PI=12345 (108,503) 

Navigate to PeopleTools > Application Engine > Manage Abends to clear out the abended app engine process - matching the relevant process instance.

by Praj

For example:

 <?xml version='1.0'?> <DATA> <DATA> </DATA> </DATA> 

The key is that the tag <DATA> is both the root level element and the tag used by the data elements.

The XML format actually required is this:

 <?xml version='1.0'?> <ROOT_ELEMENT> <DATA> </DATA> </ROOT_ELEMENT> 

What was causing the issue in this case was the XML file layout field tag. This is set in the file layout properties in the use tab. There is a field there called File Definition Tag. This is where you set the root element tag:

by Praj

Here are the four scenarios that you might have:

Regular PeopleSoft Tables

This is for anything that uses PS_ in your database as a prefix:

Find something like PS_INSTALLATION and replace with %Table(INSTALLATION)

 Find Regex: PS_([^\s]*) Replace Regex: %Table($1) 

Find something like %Table(INSTALLATION) and replace with PS_INSTALLATION

 Find Regex: %Table\(((?!PS)[^\s]*)\) Replace Regex: PS_$1 

PeopleTools Tables

This is specifically for PeopleTools tables that always start with PS and do not use the PS_ prefix for the database table name.

Find something like PSOPRDEFN and change to %Table(PSOPRDEFN)

 Find Regex: PS((?!_)[^\s]*) Replace Regex: %Table(PS$1) 

Find something like %Table(PSOPRDEFN) and change to PSOPRDEFN

 Find Regex: %Table\(((PS)[^\s]*)\) Replace Regex: $1 

How to use

Try it out in your text editor with regular expressions enabled. You may need to put qualifiers around the find regex, e.g. /%Table\(((PS)[^\s]*)\)/g depending on the regex engine you are using.

Also you can try these out using RegExr online to see them in action.

by Praj

 <IBResponse type="error"> <DefaultTitle>Integration Broker Response</DefaultTitle> <StatusCode>20</StatusCode> <MessageID>536</MessageID> <DefaultMessage>User USER not authorized to invoke Service Operation EXAMPLE. (158,536)</DefaultMessage> <MessageParameters> <Parameter>USER</Parameter> <Parameter>EXAMPLE</Parameter> </MessageParameters> </IBResponse> 

This relates to service operation security. Specifically, the user in question does not have security to the relevant service operation.

Here's how to check/update the service operation security:

• PeopleTools > Integration Broker > Integration Setup > Service Operations
• Open the service operation mentioned in the message.
• On the service operation page, there will be a hyperlink labelled Service Operation Security. Click on that to bring up the service operation security settings (opens in a new tab/window).
• Add a permission list that you know the user mentioned in your message has in their security settings.

Save and re-test.

by Praj

Previously, this was a requirement, otherwise the integration would fail with a message like this:

 User <username> not authorized to invoke service operation <service operation> 

See Oracle Note 1295566.1 for more details about the above.

The exclude PeopleSoft authentication token setting is available from the following navigation:

PeopleTools > Integration Broker > Configuration > Service Configuration > Exclude PSFT AUth Token Tab

From the screen, search for a relevant service or service operation (e.g. VENDOR_SYNC) and check the Exclude token to exclude authentication and save.

Note this is just a search page, so the item won't appear in the service operations table next time you open the page. However, you can confirm the settings have been saved by searching for all services/service operatiosn with the Exclude PSFT Auth Token flag set (check box).

by Praj

 Local object &Response = %Response; Local object &YourCookie; &YourCookie = &Response.CreateCookie("YourCookieName"); &YourCookie.Domain = %Request.AuthTokenDomain; &YourCookie.MaxAge = -1; /* Makes this a session cookie (default) */ &YourCookie.Path = "/"; &YourCookie.Secure = True; /* Set to true if using https (will still work with http) */ &YourCookie.Value = "Set the cookie value here. Encrypt sensitive information."; 

And here's how the cookie looks using FireCookie (Firefox Extension)

If you don't see your cookie make sure you have set your domain correctly (with leading full stop) to match your environment. If this is incorrect, the cookie will not be created.

If you make the MaxAge greater than 0, that defines the lifetime of the cookie in seconds. A cookie with a MaxAge of 0 is deleted immediately (not sure what you would use that for?).

by Praj

A good example is the PEOPLE_SRCH view in PeopleSoft HRMS/Campus Solutions. This view is used for row level security and validation of EMPLIDs and used on a number of delivered search pages. If it is not excluded from auto look up, whenever a user gets to one of these search pages and presses the prompt button on the EMPLID field, the system performs a full search of all EMPLIDs! Slow to say the least.

To add a record/table to the look up exclusion list:

PeopleTools > Utilities > Administration > Lookup Exclusion Table

Behind the scenes this is stored in the single table, PSRECXL.

by Praj

Standard Customization

Say we wanted to add another field called DEBUG_INFO to all message catalog entries. The purpose of this field would be to provide additional information related to the message for debugging purposes. Obviously not every message would need or want debugging information, so this would be an optional field. Also, given the delivered data in the message catalog, this field may relate more specifically to our own message catalog entries than the PeopleSoft delivered ones. However, in some cases (e.g. a known workaround) the debug info could be stored with the delivered message.

One way to do this would be to simply customize the delivered message catalog functionality using something like the steps below:

• Create a new field called PW_DEBUG_INFO
• Add the field PW_DEBUG_INFO to the delivered message catalog record, PSMSGCATDEFN
• Alter the table structure in the database
• Modify the page MESSAGE_CATALOG by adding the new field to it and rearranging the layout.

While this is very straightforward, at this point, we've made two customizations, one to a record and one to a page. Of particular concern are customizations to records because a record can be used in a number of places. Customizations to pages can also be troublesome if they are used in more than one component or are subpages used on more than one page. Oracle regularly deliver new message catalog entries, so the above will have patching implications and make impact analysis more difficult.

These are some reasons to look at using a sibling record.

A note for discretion at this point. Sibling records aren't a silver bullet for avoiding customizations. I've seen cases where developers have gone to extraordinary lengths and complexity to get a sibling record working when the patching implications really didn't warrant it. You can go too far with this approach. If support and maintenance of your sibling records/bolt-on customization causes more work on a regular basis than the impact it has on patching, then in reality you've actually made things worse not better. Good judgement is always required here, and you need to do some impact analysis. Tools like iMPACTUS! can be really helpful for this.

Sibling Record

Moving on, this is a pretty clear cut example where a sibling record is a far better approach. Here's an approach you could take to achieve essentially the same outcome:

• Create a new field called PW_DEBUG_INFO (of course reuse an existing field if that works too). Make it a Long Character field.
• Create a new record, PW_MSGCATDBGINF (name this appropriately based on your site's conventions)
• Add the same keys to PW_MSGCATDBGINF as those on PSMSGCATDEFN. These are MESSAGE_SET_NBR and MESSAGE_NBR. This is what makes your new record a sibling record. Make sure your search keys are also the same.
• Add the field PW_DEBUG_INFO to PW_MSGCATDBGINF.

So here's how our sibling record looks at this stage:

Keys are very important here, so double check you have that correct before proceeding.

Sibling Page

To continue with the bolt-on methodology, we'll also create a separate sibling page rather than modifying the delivered page. Again discretion is required here, and you may find it more complicated to add your own page and make it work in the context of the component than simply customizing the delivered page. Also keep in mind the impact on end users. Do you really want them to have to navigate to another page simply to set a check-box for one extra field? Will they forget? Will the errors confuse them when they do? Don't lose sight of the fact that creating unnecessary complexity is always worse than a minor, contained customization.

Having decided that a sibling page makes sense, we'll create another page with the same key structure as the delivered MESSAGE_CATALOG page. This page needs to transfer key data from the delivered record PSMSGCATDEFN to our bolt-on record PW_MSGCATDBGINF. What this means is that we just want to add our additional fields from the bolt-on record to the page, and let the scroll levels do the rest of the work automatically for us.

The steps to accomplish this are:

• Create a sibling page called PW_MSGCAT_DBGINF (name this appropriately based on your site's conventions)
• Modify the page title to Message Catalog Debug Information
• At scroll 0, add the fields MESSAGE_SET_NBR and DESCR from PSMSGSETDEFN. Note the description field is for informational purposes, not for passing key data. The best way to do this is to have the delivered page open and drag the fields across to your new page.
• At scroll 1, add the fields MESSAGE_NBR and MESSAGE_TEXT from PSMSGCATDEFN. You don't need the key field MESSAGE_SET_NBR here as that has already been set at scroll 0. Again the MESSAGE_TEXT is for informational purposes, not passing key data. Have the delivered page open and drag these fields across.
• Create a scroll at level 2 (occurs level 2) and add the field PW_DEBUG_INFO from PW_MSGCATDBGINF as a long edit box.

This is how the page looks in layout mode:

And this is the page structure in order mode:

What's probably confusing at this point is why your sibling record and field are at scroll 2 instead of scroll 1? The answer is that in order to automatically pass the keys from PSMSGCATDEFN (the delivered record), you need to be one level down from it. Putting the sibling record at scroll 1 assumes that all keys come directly from scroll 0 which contains only the PSMSGSETDEFN record and this is not the case (the key field MESSAGE_NBR comes from scroll 1 - PSMSGCATDEFN).

The records may be siblings in terms of key structure, but the way they behave on the page/scroll is actually more like a parent-child relationship. This means that you can't use this convention if you have a sibling record on a page where the delivered record is at scroll level 3, as you can't put your sibling record at scroll 4 (there is no scroll 4, PeopleSoft restricts this to a maximum of scroll 3). In such cases you would have to set the keys of the sibling record using PeopleCode.

Bolt-on to Component

In order to bolt-on our sibling record and page, we need something to bolt it to. That's the delivered component, MESSAGE_CATALOG1. This is where the customization has to occur. However it has minimal impact as we only need to add one page to one component. Drag your sibling page PW_MSGCAT_DBGINF into the delivered component and give it an appropriate item label.

Make sure you tag the customization in the comments of the component properties:

Also, in order to see the sibling page, you'll need to enable the Display Folder Tabs (top) setting in the Internet tab of the component (as this will be disabled as delivered).

Security

In order to see your new page, you'll need to add security to it in a relevant permission list. To find which permission lists are already associated with the MESSAGE_CATALOG page, use the following SQL:

 select * from PSAUTHITEM where PNLITEMNAME = 'MESSAGE_CATALOG'; 

One of the permission lists (CLASSID) returned is PTPT1200 and I'm going to use this one.

• Navigate to PeopleTools > Security > Permissions & Roles > Permission Lists and open PTPT1200.
• Switch to the Pages tab and find the UTILITIES menu and choose Edit Components.
• Find the MESSAGE_CATALOG1 component and choose edit pages
• Authorize the Debug Information page on this component

Press OK, and OK again, and make sure you save the permission list!

Testing

Right, time to test it and see if it works. Navigate to the message catalog:

PeopleTools > Utilities > Administration > Message Catalog

Open a message set. You should see the debug information page as well.

If you don't, a few things could be causing the problem:

• Did you save your permission list changes?
• Does the user you are logged in have access to that permission list?
• Did you enable the Display Folder Tabs (top) setting on the component?
• If the item appears in the table PSAUTHITEM then it's a caching issue. First start with clearing your browser cache/restarting your browser. If that doesn't work, try application server, and web server cache.

To complete the test, enter some debugging information and save. Verify that the page saves correctly and that you see this data in the sibling table:

 select * from PS_PW_MSGCATDBGINF; 

You should also return to search and reopen the entry and confirm the debugging information is loaded and displayed.

Source Code

The source code for this article can be downloaded from the PeopleSoft Wiki Google Code site. If you use this project, you'll still need to apply security as per the security steps above.

Comments

by Praj

by Praj

 HttpTargetConnector:PSHttpFactory init or setCertificate fails (158,99999) 

A quick search on My Oracle Support or the Internet will tell you that's to do with two entries in the integrationGateway.properties configuration file which you can access through the Advanced Properties Page link under PeopleTools > Integration Broker > Configuration > Gateways [Open Gateway] > Gateway Setup Properties link.

The two entries are:

 secureFileKeystorePath= secureFileKeystorePasswd= 

The secureFileKeystorePath needs to point to the correct location of the PeopleSoft Keystore (pskey) which for example might live under $PS_HOME/webserv/<domain./piaconfig/keystore/pskey but this will vary depending on your web server and PeopleTools version. Just make sure the path is correct.

The secureFileKeyStorePasswd has a catch to it:

• For PeopleTools 8.5x and above, this value needs to be encrypted.
• For PeopleTools 8.4x this value needs to be in plaintext.

To encrypt the password (only in PeopleTools 8.5x), use the password encryption utility at the bottom of the gateway properties page, and paste the encrypted value in the field.

If you are setting up integration between two systems, and one is on PeopleTools 8.5x or above and one is on PeopleTools 8.4x, then you need to make sure you have set up the integrationGateway.properties file correctly:

• The secureFileKeyStorePasswd needs to be encrypted on the gateway to the system running PeopleTools 8.5x
• The secureFileKeyStorePasswd needs to be in plaintext the gateway to the system running PeopleTools 8.4x.

So, with such a set up, you will have a combination of encrypted and unencrypted passwords that need to match up. If you have any of this wrong, you'll get the same message above when you try to ping nodes between the two systems. That will tell you which side you have wrong.

by Praj

Usually the directions point to navigating to the following area in the DCOMCNFG configuration page:
Component Services > Computers > My Computer > DCOM Config

Then finding the appropriate Microsoft Office application and changing its properties. Problem is, sometimes you can't find the applications even though they are installed! What's going on?

Well it turns out that if you are on a 64bit OS, you need to run the 32bit version of DCOMCNFG as Microsoft Office is largely a 32 bit application.

To do so, here's the command:

 Start > Run > DCOMCNFG -32 

Simple when you know how. You should now be able to see the relevant entries e.g. Microsoft Excel Application and Microsoft Office Word 97-2003 Document. Interestingly, there's also one in there for PeopleSoft.ApplicationDesigner.

by Praj

 Error! SQR Failed To Process *** *** System Error Code 2 ****** PS_StartProc: CreateProcess failed: cmd = C:\PT8.51\bin\sqr\ORA\binw\sqrw cwd = C:\oracle\instantclient11r2 *** ******************* Error *********************** 

Somewhat cryptic! What's happened was that the %PS_HOME% directory had been changed, so the path it was using to run sqrw had changed. Going back to the process scheduler configuration and changing the SQRBIN parameter to the correct location, and restarting process scheduler resolved the issue.

A simple solution in the end (mis-configuraton) but I noticed when I did a quick google search for the problem, I got nowhere, especially with the main results being exactly-my-problem-but-no-useful solution posts in other forums.

by Praj

In these situations, there is a way to keep this data. I call it a FOP step (short for Fail On Purpose). Basically, it involves a step with a SQL action added at the very end of an application engine program that deliberately fails. This stops the app engine program from performing the final truncate of temp tables, allowing you to view the data in them.

Here's a screenshot of the step and action:

What goes in the SQL? Well, you can have anything that will cause an error, but here's my suggestion:

 SELECT %Table(ATEMP_TBL), %Table(BTEMP_TBL), %Table(CTEMP_TBL) FROM FOP! 

Hopefully the table FOP! doesn't exist in your database so this will throw an error. The selects are the useful part. In this format, they will display the instances of the temp tables being used in your .stdout file.

Basically, something that looks like this:

 SELECT PS_ATEMP_TBL4, PS_BTEMP_TBL2, PS_CTEMP_TBL1 FROM FOP! 

Which tells you exactly which tables to go searching for your data.

For this to work, make you add the FOP as the very last step in your application engine program.

Also, I'd suggest adding a step like this and making it inactive if you are developing a new app engine program that uses temp tables. That way, when debugging is required, it can be made active. Of course, doing all of the above will cause your app engine to go to No Success in the process monitor (which is what we expect), and if restart is enabled, you will need to restart the abended instance (and not start a new one). Also keep in mind that the temporary tables may be cleared when you re-run or restart the application engine. So be careful if you want to keep data between runs.

by Praj

A common use for coalesce/nvl is to substitute a default value when a null is encountered. Probably the most common example is to substitute a null with a 0 on fields you are using for calculations.

So for example:

 select QTY * PRICE from YOUR_TABLE; 

Works fine unless you have a scenario where either the quantity or price is NULL. Yes that may be weird but this is meant to be an example. Here's how to write the same statement with coalese using Meta-SQL:

 select %Coalesce(QTY, 0) * %Coalesce(PRICE, 0) from YOUR_TABLE; 

Simple, on resolving the Meta-SQL it will be turned into the appropriate syntax for your database platform. If you use Oracle you might wonder why you would bother when you can just use nvl? Well like a lot of other Meta-SQL functions, the benefit is database platform independence. Your code will work on any database supported by PeopleSoft. Up to you.

by Praj

Here's a screenshot example of what I'm referring to with Weblogic:

For various reasons (e.g. security, user-friendliness) you might want to instead do a redirect directly to the PeopleSoft login page. You can achieve this with a meta tag redirect on the HTML page.

First, navigate to your web server directory, and under PORTAL or PORTAL.WAR find the file {{index.html}. This is the page you see by default.

At the top of this file, just below the first <meta> tag, add the following:

 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <html><head><meta http-equiv="Content-Type" content="text/html;CHARSET=iso-8859-1"> ... <meta http-equiv="refresh" content="0; URL=../ps/signon.html"> ... <!-- Start of Oracle comments ... 

The line to you want to add is <meta http-equiv="refresh" content="0; URL=../ps/signon.html">. Note the 0 indicates no timeout - i.e. automatic redirect. If you set this to a value greater than 0 it will wait that many seconds before performing the redirect.

For a brief second you do see the web server page (and also if the signon page takes a while to load), so if you like, change the heading, e.g.:

 <h1>Welcome to Weblogic Application Server 10.3&#153;</h1> 

To something that tells the user it is redirecting:

 <h1>Redirecting...</h1> 

I like this because you no longer need to remember the exact path to the signon page or have to do that one extra click to get there. Instead you can just type server:port into your browser address bar and you'll be at the signon page.

by Praj

Software

• AppLoader

• Badboy

• Grinder

• HP LoadRunner

• JMeter

• loadUI

• Neoload

• OpenSTA

• Pylot

• Selenium

• Siege

• Tsung

• Valgrind

• WebLoad

Articles

Testing PeopleSoft Performance (ERPAssociates).

Automated your testing with Badboy (ERPAssociates)

by Praj

 File: /vob/peopletools/src/pssys/stmget.cppSQL error. Stmt #: 2736 Error Position: 23 Return: 942 - ORA-00942: table or view does not exist Failed SQL stmt:SELECT OWNERID FROM PS.PSDBOWNER WHERE DBNAME=:1 PSAPPSRV.9554 (0) [05/26/11 09:48:10](1) GenMessageBox(200, 0, M): /vob/peopletools/src/pssys/stmget.cpp: A SQL error occurred. Please consult your system log for details. PSAPPSRV.9554 (0) [05/26/11 09:48:10](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database <DBNAME> with user <USERID> PSAPPSRV.9554 (0) [05/26/11 09:48:10](0) Server failed to start 

One of the things that can cause this is if the public synonym for PS.PSDBOWNER has not been created or granted public access. To fix, run the following in the database:

 CREATE PUBLIC SYNONYM PSDBOWNER FOR PS.PSDBOWNER; GRANT SELECT ON PS.PSDBOWNER TO PUBLIC; 

Also confirm that the database owner and name correctly matches the databases you are in - particularly if working with a refreshed environment.

by Praj

PeopleTools > Utilities > Administration > Query Administration

To modify a query, first perform a manual search for it:

You can then select it to modify or rename it. To make it public, click on Assign New Owner and clear out the owner to make it public.

by Praj