Peopletools 8.43 Release Notes: June 13, 2003
Peopletools 8.43 Release Notes: June 13, 2003
Peopletools 8.43 Release Notes: June 13, 2003
43 Release Notes
2
3 PeopleSoft Proprietary and Confidential
Table of Contents
TABLE OF CONTENTS.......................................................................................................................................................3
PREFACE........................................................................................................................................................................7
PeopleBooks Considerations.................................................................................................................................7
Upgrade Reminder.................................................................................................................................................8
Platform News.......................................................................................................................................................9
Microsoft SQL Server 2000................................................................................................................................9
New Service Pack for BEA WebLogic 6.1.........................................................................................................9
New Version of Micro Focus Server Express.....................................................................................................9
JDBC Database Drivers....................................................................................................................................10
IBM AIX 5.2.....................................................................................................................................................10
Solaris 9............................................................................................................................................................10
Web Browser Support: Netscape 7...................................................................................................................10
Future Support Plans.........................................................................................................................................10
PeopleSoft Internet Architecture (PIA)...............................................................................................................13
New Personalization Settings...........................................................................................................................13
Browser Settings...............................................................................................................................................13
Adding Pages to My Favorites..........................................................................................................................14
SQR for PeopleSoft Language Reference............................................................................................................14
PeopleSoft Component Interfaces........................................................................................................................14
Object Adapter..................................................................................................................................................15
CopyRowset Language Considerations............................................................................................................16
WSDL Binding for Component Interfaces.......................................................................................................16
Microsoft Excel to Component Interfaces Utility.............................................................................................16
PeopleSoft Business Interlinks.............................................................................................................................17
Allowing Redirects...........................................................................................................................................17
Writing an XML Design-Time Plug-In............................................................................................................17
PeopleSoft Optimization Framework..................................................................................................................18
Designing a Problem Type Definition .............................................................................................................18
Creating Optimization PeopleCode..................................................................................................................18
PeopleSoft Application Designer.........................................................................................................................23
Definition Changes...........................................................................................................................................23
Fixing Audit Errors...........................................................................................................................................24
Alter Table Changes.........................................................................................................................................25
PeopleSoft Administration Tools (Formerly Data Management).......................................................................25
Data Mover.......................................................................................................................................................25
PeopleSoft Upgrade Assistant.............................................................................................................................26
Setting System Variables for Upgrade Assistant..............................................................................................26
Running Data Conversion Concurrently on the client via the Upgrade Assistant............................................26
PeopleSoft Integration Broker.............................................................................................................................27
Understanding Changes to the Message Channel Properties Dialog Box........................................................27
Viewing Messaging System Performance Statistics.........................................................................................27
Increasing Asynchronous Message Processing Performance...........................................................................27
Throttling Dispatched Messages Through the Pub/Sub System.......................................................................27
Understanding Synchronous Message Logging Enhancements.......................................................................29
Applying Transformations on the Integration Gateway...................................................................................30
Understanding Routing Information in Messages Published to Non-PeopleSoft Systems..............................30
3
4 PeopleSoft Proprietary and Confidential
Understanding Routing Types for Nodes and Outbound Transactions............................................................31
Understanding Simple Post Utility Enhancements...........................................................................................31
Understanding Send Master Enhancements......................................................................................................36
Viewing Non-English Characters in Integration Gateway Log Files...............................................................40
Understanding HTTP Listening Connector Enhancements..............................................................................40
Using the HTTP Target Connector...................................................................................................................40
Specifying the Message Destination in HTTP Headers....................................................................................41
Pinging the SimpleFile Target Connector.........................................................................................................42
Testing JMS Listening Connectors...................................................................................................................42
Encrypting the JMS Target Connector Password.............................................................................................42
Partitioning Unstructured or Inbound Messages...............................................................................................43
Known Issues and Workarounds......................................................................................................................43
PeopleSoft Integration Tools and Utilities .........................................................................................................47
Understanding Added Parsing Support for all Comma Separated Value (CSV) Types...................................47
Understanding Added Parsing Support for Excel CSV Specifications............................................................47
Understanding the Imply Decimal Place Option..............................................................................................50
Decimal Padding With File Layout Definitions...............................................................................................51
Using Dates With the ReadRowset Method.....................................................................................................51
PeopleSoft MultiChannel Framework.................................................................................................................52
Updates to REN Server.....................................................................................................................................53
REN Servers and Upgrading from PeopleTools 8.42...................................................................................53
Instant Messaging.............................................................................................................................................53
Configuring MCF Clusters...............................................................................................................................53
Configuring MCF Agents: Miscellaneous........................................................................................................56
Accessing the MultiChannel Console...............................................................................................................56
New Parameters for MCF Cluster Tuning .......................................................................................................57
Peoplesoft CTI..................................................................................................................................................57
Email Channel...................................................................................................................................................58
PeopleTools Mobile Agent...................................................................................................................................59
Increase Synch Server TimeOut.......................................................................................................................60
Effective Dated Records...................................................................................................................................60
Multi-language Support for the Mobile Page Designer....................................................................................60
Controlling the Invisible Property for the List View and Display View..........................................................60
Conflict Detection and Resolution in the Synch Server...................................................................................60
Conflict Resolution Algorithms....................................................................................................................60
OnConflict PeopleCode................................................................................................................................61
Second Pass Resolution................................................................................................................................61
Conflict Resolution at the Component Interface Level....................................................................................62
Changes to the List View and Detail View Labels...........................................................................................62
Make Object Browser Human Readable and Tree Bases.................................................................................62
Displaying and Hiding Content References on the Laptop and PDA...............................................................63
PeopleCode Reference.........................................................................................................................................63
Searching PeopleCode for SQL Injection.........................................................................................................63
How to prevent SQL Injection..........................................................................................................................64
Updates to PeopleCode Functions, Classes, and Variables..............................................................................65
Changes to XmlDoc Class................................................................................................................................68
Updates to SendMail.........................................................................................................................................70
SendMail.......................................................................................................................................................70
Updates to SetAuthenticationResult.................................................................................................................74
SetAuthenticationResult................................................................................................................................74
New Function - NumberToDisplayString.........................................................................................................77
New Function TransformExCache ..................................................................................................................80
TransformExCache.......................................................................................................................................80
5
6 PeopleSoft Proprietary and Confidential
Disabling Recycle Count on Error..................................................................................................................123
PeopleSoft Workflow.........................................................................................................................................124
Worklists.........................................................................................................................................................124
Notification Templates....................................................................................................................................125
Required Tables for Workflow and Currency Conversion.............................................................................126
Approval Rule Set Step Limitation.................................................................................................................126
Worklist Monitor: Page Access Issues...........................................................................................................126
Worklist Entry Updates Page..........................................................................................................................126
Deleting a Route Control................................................................................................................................126
Reassigned Worklist Item Behavior Modifications........................................................................................127
RESOLVED INCIDENTS...................................................................................................................................................129
Preface
Version 03: 07/14/03
Edit History
This PeopleTools maintenance release includes a variety of enhancements and resolves several minor
issues found in our previous release. We refer to this kind of maintenance release as a “PeopleTools
Only” upgrade, which means your PeopleSoft applications will not be affected.
Important! If you skipped any maintenance releases, we recommend that you download the Release
Notes corresponding to the release(s) you skipped. For instance, if you’re installing the PeopleTools 8.43
update but skipped PeopleTools 8.42, you should download and review the Release Notes for
PeopleTools 8.42. Do this to make sure that you are aware of the previous changes and new features.
Most importantly, when upgrading to a new maintenance release, be sure to check the PeopleSoft
Platforms database on Customer Connection for any new support details.
This is a "living" document to which we add updates and corrections as needed to support our
maintenance releases in a dynamic manner by giving you the most current information. We suggest that
you refer to Customer Connection regularly to see if there have been any updates to this document.
When the Release Notes are updated, you will see a new version number and date at the top of this
page. Click the Edit History link to keep track of the changes we've made to the document.
The Release Notes contain:
• Information on New and Changed Features and instructions for implementing particular fixes.
• A summary of Resolved Incidents for this release.
Note. If you are installing this version of PeopleTools without having first installed PeopleTools 8.4, use
the PeopleTools product CD-ROM as part of the standard installation process described in your
PeopleTools Installation Guide for your platform.
PeopleBooks Considerations
The following considerations relate to installing PeopleBooks.
• Warning! Never install new PeopleBooks over an existing PeopleBooks web site! Instead,
PeopleSoft recommends moving the existing web site into a new directory and then installing into the
old (empty) directory. This will minimize the amount of reconfiguration required to enable the new
installation.
• If you have existing PeopleBooks content that you want to move into the new installation (for
example, translated PeopleBooks), refer to the document "Managing the PeopleSoft Online Library
and PeopleBooks" on Customer Connection (Patches and Fixes, Documentation Updates, All
7
8 PeopleSoft Proprietary and Confidential
Product Lines, All in selected Product Line).
• If you are installing PeopleTools/PeopleBooks for the first time, see the PeopleTools Installation
guide for your database platform.
Upgrade Reminder
Note. The PeopleTools-only upgrade instructions are no longer provided in the release notes.
PeopleTools upgrades are performed with the PeopleSoft Upgrade Assistant. Data conversion scripts
have been written in Application Engine and templates are needed to perform the upgrade. To find
documentation and related information for your PeopleTools upgrade, visit Customer Connection and be
sure to login.
The navigation path to upgrade documentation on Customer Connection has changed. From Customer
Connection select Implement, Optimize, + Upgrade, Upgrade Guide, Upgrade Documentation and
Software, Upgrade Documentation and Scripts, Release. Select the Product you are upgrading, or
PeopleTools if this is a PeopleTools only upgrade, then choose the release you are
upgrading to.
Note. New PeopleBooks documentation was last produced for PeopleTools 8.42 (a separate
PeopleBooks CD should be included with your PeopleTools shipment). The release notes include
additional documentation and alert you to the new features that have been added.
PeopleSoft recommends that you also review the Release Notes for any prior 8.4x releases to make sure
that you are aware of any other features or items of interest that do not appear in the PeopleBooks.
Platform News
The following sections provide information regarding products supported by PeopleSoft.
In general, PeopleSoft has attempted to update the support of all third party products to their latest, stable
versions. This ensures that customers have the most recent updates throughout the PeopleSoft system.
Note. Always check the Supported Platforms information on Customer Connection for the most current
support information.
• Solaris 8 and 9
Server Express 2.2 provides bug fixes and increased performance. Server Express 2.0.11 is still
supported.
9
10 PeopleSoft Proprietary and Confidential
PeopleSoft recommends that users of MicroFocus NetExpress upgrade to MicroFocus NetExpress 3.1
SP1.
Solaris 9
With PeopleTools 8.43, PeopleSoft announces support for Solaris 9.0.
• Windows XP
• Windows 2000
• Mac OS 9
• Mac OS X
• Linux
Operating Systems
• AIX 4.3
• HP UX 11.0
The minimum operating system requirements for PeopleTools 8.44 will be:
• HP UX 11.11
• Solaris 8
• AIX 5.1
• z/OS 1.2
• Windows 2000
• Windows 2003 Server 64-bit (database server only, with Microsoft SQL Server 2000 SP3 64-bit)
Database Versions
• Informix 9.21
• Oracle 9.0.1.x.x
• Oracle 9.2.0.2 for Real Application Cluster on Unix and Windows 2000
11
12 PeopleSoft Proprietary and Confidential
• Oracle 9.2.0.2 (32-bit) for Red Hat Linux Advanced Server 2.1 (32-bit). (all PeopleSoft Internet
Architecture tiers)
• Oracle 9.2.0.2 (64-bit) for Red Hat Linux Advanced Server 2.1 (64-bit). (database server only
certification)
• DB2 UDB 8.1 FP2 (32-bit) for Red Hat Linux Advanced Server 2.1 (32-bit). (all PeopleSoft Internet
Architecture tiers)
• DB2 UDB 8.1 FP2 (64-bit) for Red Hat Linux Advanced Server 2.1 (64-bit). (database server only
certification)
• DB2 UDB 7.2 (for Unix and Windows); no change from PeopleTools 8.42, 8.43
• DB2 UDB 6.1 for z/OS; no change from PeopleTools 8.42, 8.43.
• Sybase 12.5.0.1 ESD #1. Non-Unicode uses 4K page size. Unicode uses 8K page size. 2K page
size no longer supported.
• Informix 9.30.
Microsoft SQL Server 2000 SP3 (64-bit) (SP3 is the minimum service pack for 64-bit SQL Server
2000)
• 64-bit database server only certification on Red Hat Linux AS 2.1 64-bit:
Web Browsers
For PeopleTools 8.44, PeopleSoft plans to add support for the Apple Safari web browser on Mac OS X.
For PeopleTools 8.44, PeopleSoft plans to discontinue support for Netscape Navigator 6.2x. PeopleSoft
recommends that users upgrade to Netscape Navigator 7.
The minimum requirement will be Netscape Navigator 4.7 (but not 6.2), or Microsoft Internet Explorer 5.
For PeopleTools 8.44, the following application server upgrades will be required:
• The JRE/J2SE 1.4.1 upgrade will be included with PeopleTools 8.44.
Web Servers
For PeopleTools 8.44, the following web server upgrades will be required:
• BEA WebLogic Server 8.1 SP1
Browser Settings
After an upgrade, end users might encounter anomalies with the display of fonts and certain images, such
as the menu icon. If this occurs, users should clear the browser cache on their individual machines. In
Microsoft Internet Explorer version 5.50 this is done in Internet Options.
13
14 PeopleSoft Proprietary and Confidential
.2 On the General tab, select Delete Files… in the Temporary Internet Files group
area.
.3 Select Delete all offline content if desired.
.4 Click OK in the Delete Files dialog box.
Internet Explorer begins deleting http files from the Temporary Internet Files folder. This process can
take a minute or two depending on how many files you have. This process does not delete cookies.
.5 Click OK in the Internet Options dialog box.
Note. This procedure might be slightly different if using a different version of Microsoft Internet Explorer.
Consult Internet Explorer help for more information.
See also
Note. PeopleSoft does not support running PSSQR.EXE directly from a DOS or Unix command line.
PSSQR.EXE is a wrapper program used by PeopleSoft Process Scheduler to run SQR reports.
PSSQR.EXE is not designed to run manually outside of Process Scheduler.
PTSET02.SQC
Previously, the PTSET02.SQC only supported letter and A4 paper size. The PTSET02.SQC has been
modified to also support the legal format. Whenever the customer needs the legal size, the following line
of code should be uncommented in SETENV.SQC.
#define PAPER_SIZE LEGAL
Object Adapter
For PeopleTools 8.43, there is a new property exposed to Java programs. In addition, there are two
methods related to this property. The name of the property is OAType, and it holds the value of the object
adapter type. Exposing this property and supplying the associated methods enables you to detect
possible data type mismatches between the database and the component interface object.
The new Java methods are:
Method Description
getOAType() Returns the object adapter type.
getType() Returns the type of the property of a particular database field.
For example,
try {
switch ((int)iPropertyInfo.getOAType()) {
/* Object Adapter Type == 0 */
case CIPropertyTypes.PSPROPERTY_OA_TYPE_BOOL:
strOAType = "BOOL";
break;
/* Object Adapter Type == 1 */
case CIPropertyTypes.PSPROPERTY_OA_TYPE_NUMBER:
strOAType = "INTEGER";
break;
/* Object Adapter Type == 2 */
case CIPropertyTypes.PSPROPERTY_OA_TYPE_FLOAT:
strOAType = "FLOAT";
break;
/* Object Adapter Type == 3 */
case CIPropertyTypes.PSPROPERTY_OA_TYPE_STRING:
strOAType = "STRING";
break;
}
switch ((int)iPropertyInfo.getType()) {
/* Database Type == 0 */
case CIPropertyTypes.PSPROPERTY_DB_TYPE_CHARACTER:
strDBType = "CHARACTER";
break;
/* Database Type == 1 */
case CIPropertyTypes.PSPROPERTY_DB_TYPE_LONG_CHARACTER:
strDBType = "LONG_CHARACTER";
break;
15
16 PeopleSoft Proprietary and Confidential
/* Database Type == 2 */
case CIPropertyTypes.PSPROPERTY_DB_TYPE_NUMBER:
strDBType = "NUMBER";
break;
/* Database Type == 3 */
case CIPropertyTypes.PSPROPERTY_DB_TYPE_SIGNED_NUMBER:
strDBType = "SIGNED NUMBER";
break;
/* Database Type == 4 */
case CIPropertyTypes.PSPROPERTY_DB_TYPE_DATE:
strDBType = "DATE";
break;
/* Database Type == 5 */
case CIPropertyTypes.PSPROPERTY_DB_TYPE_TIME:
strDBType = "TIME";
break;
/* Database Type == 6 */
case CIPropertyTypes.PSPROPERTY_DB_TYPE_DATETIME:
strDBType = "DATETIME";
break;
}
}
catch (Exception e) {
e.printStackTrace();
}
System.out.println("\n" + propName +
" Object Adapter Type is: " + strOAType +
", Database Type is: " + strDBType);
}
Allowing Redirects
The optional Redirect parameter specifies if redirection is allowed at the merchant URL. If set to YES, or
not specified, then redirects are allowed at the merchant URL. When a redirect occurs,
return_status_message is set to 200. If Redirect is set to NO, redirects are not allowed; however, if a
redirect is attempted , return_status_message is set to 302.
Use the following syntax:
<parameter name="Redirect"
type="enum(YES,NO)"
required="false"
default="value"/>where value is either YES or NO.
To write a Business Interlink runtime plug-in using C++, you need to set up the development environment
on the UNIX system.
cd $PS_HOME/sdk/psinterlinks/src/c++/samples
cp -rf simple yourplugindirname
.4 .Edit the makefile in your plug-in directory.
Replace “simple” with yourplugindir.
name = yourplugindir
For AIX, replace “libext=so” with “libext=aix”.
17
18 PeopleSoft Proprietary and Confidential
.6 Store the .cpp and .h files within the directory you created.
You can copy, rename, and use the .cpp and .h files contained in the simple directory as a template.
.7 To compile and link your runtime plug-in, run the following make commands:
yourplugindirname\unix>make rulesfile
yourplugindirname\unix>make
Integer arrays are not allowed as transaction parameters, use a number array instead.
Add the following note to step 4 in Entering Problem Type Transaction Properties section. Also, add it the
Creating the Optimization PeopleCode chapter, GetNumberArray method description.
Note. Do not pass an array of type Integer as a transaction parameter. Use an array of type Number
instead.
You must plan for uncommitted database changes in your optimization PeopleCode. The PeopleTools
8.43 Optimization Framework detects pending database updates. If data is not committed before certain
optimization methods are called, a failure status is generated.
Database update detection occurs at runtime for the CreateOptEngine function and these methods:
RunSync, RunAsync, Shutdown, GetTraceLevel, and SetTraceLevel. Therefore, ensure that your
PeopleCode performs database updates and commits before you execute these methods.
If you use the optional detailed status parameter, or the DetailedStatus property available for the
methods, check the status of %OptEng_DB_Updates_Pending to see if there is a pending database
update.
The InsertOptProbInst and DeleteOptProbInst functions can be called only inside FieldChange, PreSave
and PostSave PeopleCode events, and in Application Message Subscription PeopleCode and Workflow.
OptEng_DB_Updates_Pending Status
The OptEng_DB_Updates status, indicating database updates are pending, has been added to the
CreateOptEngine function and these methods: RunSync, RunAsync, Shutdown, GetTraceLevel, and
SetTraceLevel.
Now you can load multiple copies of the same problem instance into multiple instances of an optimization
engine, if each instance of the optimization engine resides in a different application server domain. Each
problem instance loaded into a given domain must be unique. The optimization engine maintains data
integrity by checking to see if the data has been altered by another user.
The optimization engine writes changed data in memory to the optimization application records. If the
changed data was modified by another user before the optimization engine processes it, the optimization
engine returns a failure status and rolls back the changes.
Note. The absolute number of optimization engine instances that may be loaded in a given domain is
controlled by a configuration file loaded by Tuxedo during its domain startup.
When a record is deleted from a problem type, the associated delete record is not needed if this record is
not used elsewhere.
Currently, no optimization application requires updating the solver license. You should update solver
licenses only when instructed to by PeopleSoft.
In the Creating the Optimization PeopleCode chapter, Using Optimization PeopleCode on the Application
Server section and Using Optimization PeopleCode in an Application Engine Program section, remove
the following:
You do not need to commit for:
• CheckOptEngineStatus
• InsertOptProbInst
• DeleteOptProbInst
19
20 PeopleSoft Proprietary and Confidential
Replace with:
Ensure that changed data is committed to the database before calling the CreateOptEngine optimization
function and the following OptEngine class methods:
• RunSynch
• RunAsynch
• ShutDown
• SetTraceLevel
• GetTraceLevel
Note. Use caution when forcing commits on pending database updates; because it prevents roll-back on
error. If needed, PeopleCode functions CommitWork() and DoSaveNow() can be called within a step to
save uncommitted data to the database before calling the above. CreateOptEngine, ShutDown,
InsertOptProbInst and DeleteOptProbInst modify the database, use caution when aborting the Application
Engine program without committing the changes made by those calls.
Add the following note in Designing a Problem Type Definition chapter, Deleting an Existing Problem
Instance section.
Note. If you attempt to delete an existing problem instance that is loaded in a running optimization engine,
DeleteOptProbInst returns %OptEng_Fail, and the optional status reference parameter is set to
%OptEng_Exists.
When you run an asynchronous transaction (using the RunAsynch method), a new browser window
opens showing a progress meter for that transaction. This page does not display for synchronous
transaction (RunSynch).
The progress meter shows the percentage progress of the asynchronous transaction until the transaction
completes. When it completes, detailed messages for this transaction appear. The messages in the
progress meter are created by the optimization plug-in.
To start the progress meter, you must set up REN server and its security settings for optimization.
Remember to enable REN Permissions for optimization.
See the “PeopleTools 8.43: Configuring REN Servers” PeopleBook Enhancement on Customer
Connection.
&FunctionStatus Parameter
Any optimization functions and OptEngine methods that use either the &functionstatus parameter or
&status used as a parameter, replace these parameters with &detailedstatus. This is more clear, and
consistent with what is used in the Lights-out OPT_CALL message.
Note. If the optimization engine cannot be contacted for shutdown, the return status is %OptEng_Fail and
&functionstatus is OptEng_Not_Available. Before this method is called, CreateOptEngine or
GetOptEngine must be called to reference an optimization engine. Also, ShutDown should be called to
shut down an optimization engine even when running in PeopleSoft Application Engine.
Change the return value from boolean to integer. Change all calls to it to reflect that they return
%OptEng_Success or %OptEng_Fail. “Not &status” changed to “&status=%OptEng_Fail” in If statements.
GetTraceLevel Method
• %Severity_Status
• %Severity_Error
• %Severity_Warn
• %Severity_Info
• %Severity_Trace1
• %Severity_Trace2
21
22 PeopleSoft Proprietary and Confidential
Local OptEngine &myopt;
Local integer &tracelevel;
Local integer &detailedstatus;
Local integer &status;
&myopt = GetOptEngine("PATSMITH");
&status = &myopt.GetTraceLevel(%Opt_Engine, &detailedstatus);
if &status = %OptEng_Success then
if (&tracelevel = %Severity_Info_ then
winmessage("Severity level for the OptEngine is ’Info’");
End-if;
End-if;
SetTraceLevel Method
CreateOptEngine Function
DetailedStatus Parameter
In all OptEngine methods, remove the &detailedstatus parameter and replace it with using DetailedStatus.
The DetailedStatus property contains the detailed execution status of an OptEngine method after the
method is executed.
Local integer &status;
&status = myopt.ShutDown();
Use the ProcessInstance property within Lights Out PeopleCode. Set the ProcessInstance property to the
name of the process instance for the Lights Out process scheduler job. The default is zero.
The following is an example of PeopleCode in Lights Out, PT_OPTCALL Application Engine program. It’s
in the Process Scheduler, sending request messages to and obtaining the process instance.
&rs.InsertRow(2);
&rec = &rs.GetRow(3).PT_OPTPARMS;
&rec.PARMKEY.Value = "PROCINSTANCE";
&nInst = Record.PT_OPT_AET.PROCESS_INSTANCE.Value;
&rec.VALUE.Value = String(&nInst);
&procinst = String(&nInst);
The following is an example of is OPT_CALL application message PeopleCode.
If &myopt <> Null And &isSync = "N" Then
&myopt.ProcessInstance = &procInst;
&optstatus = &myopt.RunASynch(&trans, &delayParm, &delay, &sleepParm,
&isSleep);
&detStatus = &myopt.DetailedStatus;
End-If; /* if myopt=null */
Definition Changes
Field Definitions
We have removed the International Format Settings tab and its attributes from the Field Properties dialog
box. These settings were only applicable to the windows client.
The PeopleTools 8.42 release included a new “Top” label position for edit boxes, long edit boxes, and
drop-down list boxes as the default setting for new fields added to a page. In this release, we have
changed the default label position to be immediately adjacent to the left of the field as it was in previous
releases.
Subpages in a Grid
As of the PeopleTools 8.4 release, you can now insert subpages into a grid. Subpages in a grid function
the same as those on pages except that the fields display at runtime as grid columns. In PeopleSoft
Application Designer, the subpage displays as a single column in the grid.
23
24 PeopleSoft Proprietary and Confidential
Subpages can be dragged from the project workspace directly into the grid or inserted on the page from
the Insert menu and then copied into the grid using cut and paste. Be aware that subpages containing
invalid field types for grids, such as radio buttons or static text, cannot be inserted. PeopleSoft Application
Designer generates an error indicating the invalid field type and will not insert the subpage. Likewise, if at
a later point an invalid field type is added to a subpage already in a grid, the system will generate a
runtime error when the user accesses the page containing the subpage in PIA.
Subpages added to a grid can contain page fields that are associated with subrecord record fields. The
same record name substitution mechanism that applies to subpages inserted onto a page applies to
those inserted as grid columns. The system replaces the name of the subrecord as part of the
expansion process and it is never seen at runtime.
See PeopleTools 8.42 PeopleBook: PeopleSoft Application Designer, “Using Page Controls—
Using Subpages.”
Bulk Operations
We have altered security access for the Bulk Operations utilities. For the 8.43 release going forward, only
users logged in under the “PeopleSoft Administrator” role will have access to the Bulk Operations menu
items. For all other users, these menu options are disabled.
In addition, we have made some behind the scenes changes to the Bulk Operations properties and
PeopleCode API to facilitate upgrade deletes for customers. When passing the project name as a
parameter, if the project contains definitions with an upgrade action of delete, the system ignores those
definitions. The following built-ins have been modified for this purpose: BulkModifyPageFieldOrder,
BulkInsertField, and BulkDeleteField.
With the 8.43 release, disabling a PeopleTools toolbar button, such as Return to Search or Next In List,
also disables the associated hot keys in PeopleSoft Internet Architecture. You disable toolbar buttons on
the Internet tab of the Component Properties dialog box.
Copying Definitions
PeopleSoft delivered definition types (such as pages, application engine programs, iScript PeopleCode,
and so on) cannot be copied across product lines. License codes for these definitions are specific to the
product line in which the definition is delivered. If a PeopleSoft delivered definition is copied to a different
product line, it may be inaccessible on the target database.
Creating Indexes
When creating indexes using the Alter method, drop the statistics created explicitly on columns prior to
altering the table using "DROP STATISTICS".
Altering Tables
When altering tables, the alter process does not create indexes if either of the Alter Table Options are
selected on the Alter tab of the Build Settings dialog box. In the case of “Alter by Table Rename,” the
indexes are dropped automatically when the temp table is dropped. For the “Alter in Place” option, the
index creation process goes through the “Recreate index only if modified” option on the Create tab.
Data Mover
The following changes apply to Data Mover for PeopleTools 8.43.
There are two environment variables required to setup trace for Data Mover: PS_SERVER_CFG and
PS_SERVDIR. The environment variable that PS_SERVER_CFG points to is in the
$PS_HOME/setup/psdmtx.cfg file that PeopleSoft delivers. The environment variable that PS_SERVDIR
points to is in the output log directory. In order to set a specific trace, you must edit the psdmtx.cfg file to
set the trace bit flag specified in the file. After running Data Mover, the trace file is located in
$PS_HOME/log/LOGS/AE__0 directory.
.5 EXPORT PS_SERVER_CFG=$PS_HOME/setup/psdmtx.cfg
.6 EXPORT PS_SERVDIR=$PS_HOME/log
25
26 PeopleSoft Proprietary and Confidential
Trace file is located in $PS_HOME/log/LOGS/ AE__0/AE__0.trc
The tlscopy.sqr is no longer needed to perform the alter on a recfield rename. To write the change to the
system tables, use PeopleSoft Application Designer to alter the tables.
4. In this same location, append the <PS_HOME>\class\psjoa\psjoa.jar directory to the system variable
CLASSPATH to include the psjoa.jar file.
Administrators can now obtain detailed performance information around integration points, enabling them
to see exactly where their system is spending its time. This enhancement is available to all PeopleSoft
applications, and enables an administrator to determine the source of bottlenecks, reducing
administration time and enabling increased system performance to be obtained.
Integration Broker Monitor features a Statistics tab that enables you to view performance statistics for
your messaging system.
To access the Statistics page, select PeopleTools, Integration Broker, Monitor, Monitor Message,
Statistics.
For documentation on this new feature, see the PeopleBook Enhancement posted on Customer
Connection titled “Viewing Messaging System Performance Statistics.”
27
28 PeopleSoft Proprietary and Confidential
• Provides an internal threshold limitation based on Tuxedo queue size to avoid queue saturation and
degraded performance.
You set throttling parameters in the psappsrv.cfg. The following throttling parameters are available in the
file:
Messages page
Use the following field to select the level of synchronous logging:
Field Description
Synchronous Logging The valid options are:
29
30 PeopleSoft Proprietary and Confidential
• Header Only. Log header information only.
With this option, you can view synchronous
message header information on the
Integration Broker Monitor Synchronous
Details page.
The steps to apply transformations at the integration gateway level include setting transformation
properties in the integrationGateway.properties file.
Rather than manually enter the properties in the integrationGateway.properties file and then set the
values as required in the previous release, by default the properties are now provided in the file. To set
the properties all you need do is uncomment the properties, enter the appropriate values, and save the
file.
Note: While you may apply transformations at the integration gateway level, PeopleSoft strongly
recommends that you apply them at the application server level due to a more robust infrastructure to
support them.
You may encounter differences in implementing transformations at the integration gateway level as
opposed to implementing them at the application server level. See www.apache.com for additional
information.
• MessageType
• OrigTimeStamp
• NonRepudiation
• To
• From
When using the JMS target connector to send messages to non-PeopleSoft systems, the following IBInfo
data is contained in the JMS headers:
• RequestingNode
• FinalDestinationNode
• DestinationNodes
• MessageName
• MessageType
• OrigTimeStamp
• NonRepudiation
• UTF-8 compliancy.
31
32 PeopleSoft Proprietary and Confidential
Accessing the Simple Post Utility Via a Java API
You can now access the Simple Post utility via a Java API, in addition to accessing it via a command line.
This section provides code examples that show how to:
• Construct a Java file that contains the parameter names and value pairs that the Simple Post utility
requires.
In addition, this section also features a sample of the XML file that is sent to the utility.
/** Constructor */
public TestSimplePost() {}
// Turn on printouts
mainSPObj.setVerbose(true);
// Requesting Node
mainSPObj.setRequestingNode("QE_UNDERDOG");
// Message Name
mainSPObj.setMessageName("QE_SYNC_MSG");
// Input file name, root node name must be the name of the
message
/* // Optional data
mainSPObj.setMessageVersion("VERSION_1");
mainSPObj.setMessageType(MESSAGE_TYPE_SYNC);
mainSPObj.setDestinationNode("QE_LOCAL");
mainSPObj.setTimeOut(2.5);
mainSPObj.setPassword("");
mainSPObj.setOriginatingUser("");
mainSPObj.setOriginatingNode("");
mainSPObj.setOriginatingProcess("");
mainSPObj.setSubChannel("");
mainSPObj.setFinalDestinationNode("");
*/
} else {
// Success!
The following example shows a command line of compiling the Java file. In this example, the
Java file name is TestSimplePost.java:
javac -classpath
"C:\beawls61sp4\wlserver6.1\config\peoplesoft\applications\PSIGW\WEB-
INF\classes;." TestSimplePost.java
33
34 PeopleSoft Proprietary and Confidential
UTF-8 Compliancy
The Simple Post utility reads any file format for incoming messages and converts them to
UTF-8 to send to the integration gateway.
Simple Post has a new encoding option that allows for the data to be compressed/encoded.
To get access to the compression/base64 encoding functionality, add an "-en" option to the command line
invocation as shown in the following example.
java com.peoplesoft.pt.simplepost.SimplePost -msgname QE_SYNC_MSG -reqnode
QE_UNDERDOG -url http://machine050102/PSIGW/HttpListeningConnector -infile
"C:\Documents and Settings\user1\Desktop\QE_SYNC_MSG.xml" -outfile
"C:\Documents and Settings\user1\Desktop\response.xml" -v –en
When then command line option is located on the Simple Post call, the logic compresses and
base64 encodes the data, places it into the Data node, and then adds the required headers
into the request.
The following example shows what the utility generates before the POST with the encoding option not
enabled.
<?xml version="1.0" ?>
<IBRequest>
<From>
<RequestingNode>QE_UNDERDOG</RequestingNode>
<OrigTimeStamp>2002-10-13T03:43:46.642-0800</OrigTimeStamp>
</From>
<MessageName>QE_SYNC_MSG</MessageName>
<MessageType>sync</MessageType>
<ContentSections>
<ContentSection>
<Data>
<![CDATA[
<?xml version="1.0"?>
<QE_SYNC_MSG>
<FieldTypes>
<QE_SALES_ORDER class="R">
<QE_ACCT_ID type="NUMBER"/>
<QE_ACCOUNT_NAME type="CHAR"/>
<QE_ADDRESS type="CHAR"/>
. . .
</QE_SALES_ORDER>
<PSCAMA class="R">
<LANGUAGE_CD type="CHAR"/>
<AUDIT_ACTN type="CHAR"/>
. .
</PSCAMA>
</FieldTypes>
<MsgData>
The following example shows the same file when encoding is used.
<?xml version="1.0" ?>
<IBRequest>
<From>
<RequestingNode>QE_UNDERDOG</RequestingNode>
<OrigTimeStamp>2002-10-13T03:43:46.642-0800</OrigTimeStamp>
</From>
<MessageName>QE_SYNC_MSG</MessageName>
<MessageType>sync</MessageType>
<ContentSections>
<ContentSection>
<Headers>
<encoding>base64(deflate)</encoding>
<encodedlength>648(485)</encodedlength>
<length>2263</length>
</Headers>
- <Data>
- <![CDATA[
eJyVlsFu4yAQQO8r7T9Y/oB1eyeOCBAnlQ0JYHX3hKw0qi
qlSRVHVffvl7XjGMdgaG6eeR7GwDwFzL/eD9Hn/ly/nY6z
+PHXQzxPf/4AW6LEH4pUITL9GOkfWL7tDy/y78e+vkaa6H
8Q5kQoxjHh0e5Q1fUs5rHBdBxESKo1ji66xiymZbEgPE7s
ICupVBQW5EqjFXSwGHMihA/brBj11lpyVnD2LIj0kZKFcY
JQrASDaiFpICtCWMkh/V7d7TfKhrcAN4hhEl46GN+Ui99F
hkKgVFOIPeCmAjEc0YzFwWS4WU2UxuBYAHd1zuHNCthpnv
Bk03AEq+lvuCeXhdQEBVaU8+oPuStWubOT2u/gTOkR0Wtq
ZCQIuIZRH0E+VqsFC9z0o+tswWqT3ZqYEHS7mGnk2TkE1D
Ur7i6VOZL8lwd62p30XayXe0A83Ts1T73rRvpm3PSp6o+H
aOlXnt3am7FIOso0IrIVb8RkCvZi8dFdMJx5U3ReBgxxZh
ima6zDSjjX6oXyHQpLzYQhgu6icIK3AQxut5uMTRpjxwax
35
36 PeopleSoft Proprietary and Confidential
hjmlNAMJGbAwveiSCFIjCcLe2+LdoFR1PKmoQ7rltwrI33
QY3wfs703dIe1tuGM8YYPXNGGxioASW+M9oy6vyz/AP6S+
]]>
</Data>
</ContentSection>
</ContentSections>
</IBRequest>
Beginning with the PeopleTools 8.43 release, when you create a Send Master project, you also select the
project type. In previous releases you first created a Send Master project and then later selected the
project type.
In addition, a new project type, MQSeries, has been added that enables you to post synchronous and
asynchronous messages to MQSeries queues to test your implementation of the JMS listening connector.
WebLogic:
WebLogic_home\config\peoplesoft\applications\PSIGW
WebSphere:
WebSphere_home\installedApps\peoplesoft\PSIGW
.2 Next to the Project field, click the New Project button. A new project dialog box
displays.
.3 In the Project Name field, enter a name for the project.
.4 From the Project Type dropdown list, select a project type. The valid options are:
Input File. Use to test servers that are expecting XML data over HTTP(S).
8.4 Integration Broker (MIME). Use to test listening connectors that expect MIME data.
8.4 Integration Broker (XML). Use to test listening connectors that expect IBRequest XML
formatted data.
.5 Click OK.
See Also
PeopleTools 8.42 PeopleBook: PeopleSoft Integration Broker, “Using the Integration Broker SDK,”
Testing Message Processing Using Send Master.
PeopleTools 8.43 enables you to use Send Master to create an MQSeries project type and
test posting synchronous and asynchronous messages to MQSeries queues.
Note. To successfully post messages to an MQSeries queue using Send Master, the MQSeries queue
must already be set up and running and the JMS API must already be installed. Refer to the MQSeries
documentation for information about performing these tasks.
37
38 PeopleSoft Proprietary and Confidential
Before you attempt to post messages to an MQSeries queue, verify that the following Java Archive (JAR)
files are installed. These files are installed as part of the MQSeries installation. For more information, refer
to the IBM MQSeries documentation.
• com.ibm.mq.iiop.jar
• com.ibm.mq.jar
• com.ibm.mqbind.jar
• com.ibm.mqjms.jar
• fscontext.jar
• jms.jar
• jndi.jar
• providerutil.jar
When you use Send Master to post a message to an MQSeries queue, you perform the following tasks:
1. Create an MQSeries project.
2. Enter header-specific information. Use the Header tab to enter JMS, message and node-specific
information. When you post the message, Send Master uses the information to generate and insert
the header required to use the JMS connector.
3. Enter input file information. Use the Input File tab to compose, open or edit the message body.
4. Post the message. Click the Post button to generate the message header, insert the header in the
message body and post the message to the MQSeries queue.
5. View output information. If you are working with a synchronous message, Send Master displays
response information from the target system in the Output Information section.
Note. The following information describes only the new fields and controls that are specific to posting
messages to an MQSeries queue. For information about other fields, see the PeopleTools 8.42
PeopleBook: PeopleSoft Integration Broker, “Using the Integration Broker SDK,” Testing Message
Processing Using Send Master.
.1 In the Input Information section, click the Header tab if not already selected.
iPlanet
MQSeries
WebLogic
.3 In the JMS Queue field, enter the queue to which the messages will post.
.4 In the JMS Factory field, enter the factory to which the queue belongs.
.5 In the JMS URL field, enter the LDAP directory or local file system address, as
appropriate.
.6 In the Message Name field, enter the name of the message that you are posting.
.7 From the Message Type dropdown list, select the message type. The valid
options are:
.8 In the Requesting Node field, enter the name of the requesting node.
.9 (Optional.) In the Destination Nodes field, enter the name(s) of the destination
node(s). Separate a series of nodes with a comma ( , ).
.10 (Optional.) In the Final Destination Nodes field, enter the name of the node
that is the final destination for the message.
.11 (Optional.) In the Node Password field, enter the password for the requesting
node.
.12 (Optional.) In the JMS User field, enter the name of the JMS user.
.13 (Optional.) In the JMS Password field, enter the JMS user password. You must
confirm that the password setting required for destination system is configured
or the message will fail with incorrect user ID and password.
.14 Click the Post button to post the message to the MQSeries queue.
39
40 PeopleSoft Proprietary and Confidential
• Encoding strings.
• HTTP status codes for non-Simple Object Access Protocol (SOAP) messages.
Encoding Strings
• The special characters ".", "-", "*", and "_" remain the same.
• The space character " " is converted into a plus sign "+".
• All other characters are unsafe and are first converted into one or more bytes. Then each byte is
represented by the three-character string "%xy", where xy is the two-digit hexadecimal
The following list summarizes HTTP status codes for non-SOAP messages:
• For an asynchronous message, HTTP status codes 200 to 299 indicate a message status of
Success.
• For a synchronous message, the HTTP status code 200 indicates a message status of Success.
When sending synchronous messages, only the HTTP status code 200 indicates Success.
• HTTP status code 404 indicates that the server has not found anything matching the Request-
URI. PeopleSoft Integration Broker throws an ExternalSystemContactException on the integration
gateway and the message status goes to Retry.
• HTTP status code 503 indicates that the server is currently unable to handle the request due to
temporary server overload or maintenance. PeopleSoft Integration Broker throws an
ExternalSystemContactException on the integration gateway and the message status goes to Retry.
• All other HTTP status codes throw an ExternalApplicationException and changes the status of a
message to Error.
The following list summarized HTTP status codes for SOAP messages:
• If you are following SOAP 1.1 standards, the HTTP status code 500 indicates an Error.
• If you are following SOAP 1.2 standards, the following HTTP status codes apply:
o InvalidMessageException
o MessageMarshallingException
o MessageUnmarshallingException
o ExternalSystemContactException
o ExternalApplicationException
o GeneralFrameworkException
When message credentials are supplied in HTTP headers, the "To:" (destination node)
specification is ignored. PeopleSoft Integration Broker uses the Default Application Server
node entry in the integrationGateway.properties file as the destination node, not the "To:"
41
42 PeopleSoft Proprietary and Confidential
entry from the headers. If no default application server entry is specified in the
integrationGateway.properties file, the follow error is generated:
<?xml version="1.0"?>
<IBResponse type="error">
<DefaultTitle>Integration Broker Response</DefaultTitle>
<StatusCode>20</StatusCode>
<MessageID>10201</MessageID>
<DefaultMessage>null</DefaultMessage>
</IBResponse>
You can specify destination node information in the SOAPAction field or HTTP query string.
If using SOAP, Integration Broker takes all IBInfo from the SOAPAction field, not from the HTTP header
or HTTP query string.
Note. A password set in the Gateways component takes precedence over one set in the
integrationGateway.properties file.
.3 Use the PSCipher.bat file delivered with Integration Broker and located in your
web server directory to encrypt the JMS target connector password.
Deleting Codesets
If a codeset has value mappings, you must first remove dependencies before you can delete the codeset.
Use the Codeset Value page to remove codeset value dependencies. To access the page, select
PeopleTools, Integration Broker, Codeset Values.
To remove a codeset value dependency, clear the Select checkbox next to a match name/match value
pair and save the change.
After you have removed any dependencies, you can return to the Codeset page and delete the codeset
match name/value row.
You cannot delete relationships and transaction modifiers. As a workaround, inactivate the relationship or
transaction modifier that you wish to remove, and create a new one.
After you rename a local node, you must reboot the web server.
43
44 PeopleSoft Proprietary and Confidential
Out of Memory Error While Posting Messages to the Integration Gateway Using Send Master or
the Simple Post Utility
When posting files 5 MB or larger to the integration gateway using Send Master or the Simple Post utility,
an “Out of Memory” error may occur.
This error can occur when using Send Master if you have not modified the StartSendMaster.bat
(Windows) or StartSendMaster.sh (UNIX) file to accommodate the larger file size.
This error can occur when using the Simple Post utility if the Java Virtual Machine (JVM) heap size is set
to the default of 64 MB.
This section discusses how to:
• Allocate additional memory in Send Master.
The steps to increase the JVM heap size depend on the web server.
When using a WebLogic web server, you increase the JVM heap size in the setenv.cmd file. When using
a WebSphere web server, you increase the JVM heap size in the server-cfg.xml file.
You can increase the heap size to any value you wish, as long as your machine has the RAM to support
the value you choose. However, PeopleSoft recommends that if you use WebSphere that you increase
the JVM heap size to 256 MB.
To increase the JVM heap size if you are using a WebLogic web server:
.1 Use a text editor to open the setenv.cmd file. The file is located via the following
path:
bea\wlserver6.1\config\peoplesoft
.2 Locate the SET JAVA_OPTIONS parameter. The following example shows the
parameter set to a maximum of 128 MB.
SET JAVA_OPTIONS=-hotspot -ms1m -mx128m
More information concerning WebLogic tuning is located on the WebLogic web site. See
http://edocs.bea.com/wls/docs60/perform/JVMTuning.html#1104303
To increase the JVM heap size if you are using a WebSphere web server:
.1 Use an HTML or XML editor to open the server-cfg.xml file. The location of the
file is:
%WAS_HOME%/config/server-cfg.xml
45
46 PeopleSoft Proprietary and Confidential
installedApps/peoplesoft/PORTAL/WEB- INF/lib/
entappletp5.jar;${WAS_ROOT}/installedApps/peoplesoft/PORTAL/WEB-
INF/lib/entappletp7.jar;${WAS_ROOT}/installedApps/peoplesoft/PORTAL/WEB-
INF/lib/entappletssl.jar" bootClasspath="" verboseModeClass="false"
verboseModeGarbageCollection="false" verboseModeJNI="false"
initialHeapSize="256" maximumHeapSize="256" runHProf="false"
hprofArguments="" debugMode="false" debugArgs=""
genericCommandLineArgs="com.ibm.ws.runtime.StandardServer"
disableJIT="false"></jvmSettings>
Before you archive messages using the Archive process in Integration Broker Monitor, inactivate the
pub/sub domain. Use the Domain Status page to inactivate the pub/sub domain.
.1 Access the Domain Status page. Select PeopleTools, Integration Broker, Monitor,
Monitor Messages, Domain Status.
.2 Inactivate the pub/sub servers on a domain:
.a To inactivate domains on all machines in the messaging system, check the All Domains Inactive
check box. To activate the servers at a later time, select the All Domains Active box.
.b To inactivate domains on individual machines, locate the domain(s) to inactivate. From the
dropdown list, select Inactivate. To activate the servers at a later time, select Activate from the
list.
.3 Click Update.
Browser Closes Unexpectedly When Viewing Subscription Contract Status in Integration Broker
Monitor
When viewing the status of bulk subscription contracts (such as 100,000 or more) in Integration Broker
Monitor using a Solaris operating system and an Oracle database, your browser session may close
unexpectedly.
As a workaround, PeopleSoft recommends that you filter the number of subscription contracts for which to
view status information.
To filter the number of subscription contracts for which to view status information, in Integration Broker
Monitor on the Sub Contract page, use the Last dropdown list to select whether to filter information by the
day, hour or minute. In the box to the left of the dropdown list, enter the number of days, hours or
minutes. The volume of messages going through your system will determine the best values to enter.
You cannot sequence transaction modifiers to handle multiple relationships to the same node.
• All empty fields are returned as empty strings or numbers equal to zero.
• When a field is in quotes, any embedded quotes must be escaped by two quotes.
• When non-Excel format backslashes are embedded within a string, they must be double-backslashes
to be interpreted as a backslash, otherwise they are interpreted as an escape character.
Understanding the Differences Between Excel CSV Parsing and Non-Excel CSV Parsing
The following table summarizes the differences between Excel CSV parsing and non-Excel CSV parsing.
47
48 PeopleSoft Proprietary and Confidential
Specifying Excel CSV Properties
To support Excel CSV parsing, additional fields have been added to the Use tab of the File Layout
Definition Properties dialog box.
To access the File Layout Definition Properties dialog box, in PeopleSoft Application Designer, open a
File Layout object. Select File, Definition Properties.
Field Description
Excel Format Check the box to parse the field using
Excel CSV specifications.
Qualifier Optional Check the box to parse the field based on
• \n. Newline.
is interpreted as:
abc"def
49
50 PeopleSoft Proprietary and Confidential
is interpreted as:
abc"def
The PeopleBooks indicate the following rule for applying dates when using the ReadRowset method:
51
52 PeopleSoft Proprietary and Confidential
Single digits in dates in the form MMDDYY or MMDDYYYY must be padded with zeros. That is, if the
date in your data is February 3, 2003, the form must be:
• 02/03/03
• 02/03/2003
In addition, when using the date format DDMMYY, single digits should also be padded with zeros and the
month value should be in all caps. For example, if the date in your data is February 2, 2003, the form
must be:
• 02-FEB-03
Security Enhancements
Improvements to the Real-time Event Notification (REN) server have been introduced to improve security.
While security best practices prescribe the use of firewalls and proxy servers in a corporate network, the
REN server adds several additional features to prevent unauthorized user access, tighten up
administration rights of the REN server, improved proxy configuration and version checking.
Administration Enhancements
PeopleTools 8.43 consolidates all REN server administration pages. This enables an administrator to
administer all REN server parameters for Reporting, Optimization, and MCF for ERMS and Chat in one
place, reducing administration time.
Instant Messaging
The HTML chat functionality delivered in PeopleTools 8.42 has been extended to popular instant
messaging networks. An outbound chat can be initiated with a customer using a public instant messaging
network such as AOL, IBM/Lotus Sametime, or Yahoo. This enables an external user to participate in a
business transaction through instant messaging.
PeopleTools 8.43 makes use of presence information supplied by the third-party instant messaging
network to alert the PeopleSoft application user of the availability of a chat partner. This functionality is
integrated into the PeopleSoft MultiChannel Framework and can easily be added to any PeopleSoft
application by using the page designer within PeopleSoft Application Designer.
Instant Messaging
The new instant messaging functionality is covered separately, in the “PeopleTools 8.43: Configuring
Instant Messaging” PeopleBook Enhancement, available on Customer Connection.
53
54 PeopleSoft Proprietary and Confidential
Other PeopleSoft MultiChannel Framework configuration and administration pages have been updated to
reflect page and field names consistent with the updated MCF and REN server cluster terminology.
See Also
55
56 PeopleSoft Proprietary and Confidential
• 0 – None (default)
• 1 – Information
• 2 – Debug
Peoplesoft CTI
The following updates were made to PeopleSoft CTI for PeopleTools 8.43.
• A context ID (such as a customer case number or an invoice number) is attached to the call data.
This allows PeopleSoft application context to be passed on to Cisco or Genesys middleware where it
may be stored. This context can be used to establish a relationship between the outbound call and
the application context when the call was made.
The outbound call demonstration page has been updated to include two optional functions:
• You can attach a string to the call as OutboundContext.
Two new parameters have been added for configuring the Cisco expanded call context variable.
Configure these expanded call context variables in the Cisco middleware:
• user.PS.referenceID: CTI internal use only. The applet uses this parameter to identify a call.
• user.PS.OutboundContext: This variable, a string type, is attached to an outbound call. This variable
can be used to associate an outbound call with the desired context.
CTI users will only see the MultiChannel Console if their user ID belongs to a role that has:
57
58 PeopleSoft Proprietary and Confidential
• MCF_AGENT or MCF_SUPR real-time event notification permissions, and
See the “PeopleTools 8.43: Configuring REN Servers” PeopleBook Enhancement on Customer
Connection for information on REN server security.
If an agent erroneously clicks Cancel instead of Go when accepting an incoming call, the agent can
recover the call by:
• Selecting a call option, or
Automatic Logout
Previously, when a CTI agent closed the CTI console without logging out the agent would always remain
logged on. Now a CTI agent on a Genesys switch system can choose on the agent customization page
whether to automatically log out when the console is closed.
This enhancement applies only to Genesys. Cisco always logs out the CTI agent when the CTI console is
closed.
CTI events are now logged in by the MCF logger in addition to MCF events. The logged CTI events can
be viewed by navigating to PeopleTools, MultiChannel Framework, Universal Queue, Administration, CTI
Event Log.
Email Channel
The following updates have been made to the PeopleSoft MultiChannel Framework email channel
functionality.
Set the values of email sent time timezone offset (in minutes) and receive time timezone offset (in
minutes) whenever possible. The default value is 800 which indicates timezone information not available.
When available the values range from +720 to -720.
Set the Reference IDs and Reply-To IDs whenever possible. If the email headers contain message IDs in
the References and In-Reply-To sections they will be extracted.
Added a new error code "10" for email content errors such as “Unable to obtain the body of a part.” Error
descriptions will be written to the gateway error log. The connector continues to fetch other emails in the
batch.
The connector sometimes cannot determine the size of the message. In such cases the size is set to 0
and an error message is written to the gateway error log.
Threshold Behavior
Integration Broker threshold behavior has been changed slightly to make the email channel behavior
more predictable. The differences between the old and new behavior is explained below with an example:
Test case: two emails in the mailbox
Email1: Email with a simple body of size 10KB
Email2: Contains 2 text parts of 2KB and 5KB respectively
Connector size limit is 1 MB, Integration Broker size limit is 15KB and Part Size limit is 11KB
Old Behavior: Reaches IB limit while processing second email and downloads the second part of the
Email2 to the repository. Return status set to the Integration Broker size limit violated.
New Behavior: Return Email1 only with the return status set to success. If the first email is deleted from
the mail server and emails are fetched again, the second email is also returned successfully. No emails
are downloaded in this case.
If the size of the first email itself exceeds the Integration Broker size limit then it is downloaded to the
repository . Connector continues fetching from the second email.
The reason for doing this is that once the email is downloaded to the repository the content can only be
displayed through a URL. It cannot be accessed by applications for content analysis. Therefore, we are
trying to minimize the downloads.
The mail server properties previously set on the PT_EMAIL_POP3 gateway node are now set on the
MCF_GETMAIL node.
59
60 PeopleSoft Proprietary and Confidential
Controlling the Invisible Property for the List View and Display View
When you define a field on a mobile page, you can establish the default properties for the field based on
the related views. You can indicate whether the field is visible in the List View. In addition, you can
specify whether the field in the Display View is invisible and/or for display only. This feature provides the
flexibility to hide certain fields in one view while displaying them in another.
If you set the default properties of a field to invisible (Invisible=true) on a Detail View, PeopleCode can
only affect the List View when the properties are changed. The Detail View becomes invisible irrespective
of the PeopleCode. Conversely, if you don’t set the field to Invisible, then PeopleCode can affect both the
Detail View and List View.
The server wins algorithm is probably the least understood of any of the system-provided resolution
algorithms. This is because it does not actually resolve the conflict, but rather it defers it. If server wins is
the selected algorithm for a CI, and a conflict is detected, no action is taken, and every conflict is
considered valid. If no action is taken by the application developer to modify this behavior, the upload
attempt will be rejected, and an unresolvable conflict error will be reported to the mobile user.
Device Wins
The device wins algorithm represents the exact opposite behavior from server wins. When this algorithm
is selected, all conflicts are considered to be resolved, and every upload attempt will be processed. Note
that when device wins is selected, it is not possible for the application developer to alter the behavior or
outcome of the detection/resolution for the object.
When field level merge is the selected resolution algorithm, Sync Server examines each property that is in
conflict, and, where possible merges the values into one composite image of the object. For example, if a
value has been changed on the server, but not on the device, then the server value will be applied to the
composite image. If a value has been changed on the device, but not on the server, then the device
value will be applied to the composite image. If a value has been changed in both locations, it is
considered to be an unsolvable conflict, and the object will be rejected.
Custom
In the current implementation of Sync Server, the custom resolution algorithm does not attempt to resolve
any conflicts, but relies solely on the application developer to resolve them using the OnConflict
PeopleCode.
OnConflict PeopleCode
In the case of the server wins, field level merge, and custom algorithms, once the system-provided
algorithm has completed, any unresolved conflicts will be processed through appropriate OnConflict
PeopleCode programs, if they have been defined.
Within the PeopleCode, the application developer can examine both the device and server values for any
property in conflict, and decide to:
• Mark the property as no longer in conflict.
• Change the conflict detection algorithm for this instance of the object.
or
• Do nothing, leaving the conflict in place.
61
62 PeopleSoft Proprietary and Confidential
Once the second pass is complete, if any conflicts still remain, they will be reported to the device.
Otherwise, the object is considered to be ready for processing. If all objects that represent the hierarchy
of a CI are resolved, they will all be saved to the server database as one operation. If any are found to be
in conflict, the entire hierarchy will be rejected.
Note. The Object Browser will be documented along with the Debug features in the 8.44 PeopleBook.
PeopleCode Reference
The following updates to PeopleCode apply for PeopleTools 8.43.
63
64 PeopleSoft Proprietary and Confidential
Remember, the only vulnerable PeopleCode programs are those that allow unvalidated user input
concatenated to SQL.
The following functions and methods provide a way for SQL to be submitted to the database, and are
therefore subject to SQL injection vulnerabilities:
• SQLExec function
• CreateSQL function
Note. This cannot always be avoided. "String-building" does not actually pose a threat unless
unvalidated user input is being concatenated to SQL.
See Also
Attachment Functions
You can now use the DeleteAttachment built-in function in a PeopleSoft Application Engine program.
You cannot use attachments from the portal to a remote node.
Bulk Functions
EncodeURL
Int
Note. PeopleSoft only supports 32 bit integers. The largest integer value we support is 4294967295.
65
66 PeopleSoft Proprietary and Confidential
IsDigits
Numeric characters do not include sign indicators and comma and period decimal points. If you want to
check for numbers as well as sign indicators, use the IsNumber function instead.
Transform
The Transform function can now take either an XML string or an XmlDoc object as input.
In addition, the Returns section has been modified to state the following:
This function returns an XmlDoc object containing the resulting XML from the transformation. Null is never
returned. If you do not want to display an error to the user, place this function inside a try-catch statement.
See also
TransformExCache
ViewContentURL
Chart Class
The RotateAngle property was only rotating the chart half of the degrees specified with this property. The
RotateAngle property now rotates the chart the full number of degrees specified.
The numeric values for the XAxisLabelOrient and YAxisLabelOrient properties, for the vertical value,
should be 90. The value table should be as follows:
A new class, MCFIMInfo has been added. Use this class to initiate instant messaging sessions. See the
“PeopleTools 8.43: Configuring Instant Messaging” PeopleBook Enhancement, MCFIMInfo Class chapter,
available on Customer Connection, for more information.
ProcessRequest Class
When you run a report, then use the ProcessRequest class to send email when the job is finished, the
email of the person who submitted the job is no longer appended to the OutDest property.
A new output option, WINDOW, was added for the following generic process types:
• AppEngine
• Crystal
• nVision
• SQR
• Other
In addition, the WINDOW output type is not available if the user does not have REN Server Report
Window permission, or there is no active REN Server cluster available for Reporting. The process would
run using the web output type and the following message will display: You do not have the permission
required to run WINDOW option.
Rowset Class
The InsertRow method can be executed against the same rowset where the insertion will take place.
%Language
The %Language system variable remains for backward compatibility only. New applications should use
the %Language_User system variable instead.
67
68 PeopleSoft Proprietary and Confidential
If multi-language entry is enabled, %Language_Data returns a string value representing the current data
language selected by the user.
If multi-language entry is not enabled, %Language_Data returns the current session language.
Use %Language_Data if your application must know the language any entered application data is stored
as in the component's related language records. Do not use this variable to control the user interface,
such as messages or page text. For determining the language of the user interface, use the
%Language_User variable.
Note. The value of this system variable may not reflect the current data language if the user has multi-
language entry enabled.
%Menu
In the root tag, the attribute xmlns stands for the XML namespace. This allows you to define namespaces
for tag names so that collisions can be avoided and validation logic can be run.
If you do not give a prefix for an XML namespace, but instead define it with the tag (xmlns) followed by a
colon (:) and then a unique namespace, for example,
xmlns:psft
• Give every xmlns a prefix. The system will use XPath correctly and find the node.
Unstructured Xml should be transformed to structured if you want to use the full rowset abilities.
PeopleSoft recommends transforming the data into a structured message.
If you do not want to transform the data, you need to break it up using the Transaction tag around the
equivalent of each level 0 rowset, as shown in the example.
<?xml version="1.0" ?>
- <SAMPLE_MSG>
- <Transaction>
- <QE_SALES_ORDER class="R">
<QE_ACCT_ID>26</QE_ACCT_ID>
<QE_ACCOUNT_NAME>APG-65</QE_ACCOUNT_NAME>
<QE_ADDRESS>F18 HORNET WAY</QE_ADDRESS>
<QE_PHONE>(206)544-1264</QE_PHONE>
<QE_FROMROWSET />
<QE_TOROWSET />
<QE_SEND_SOA_BTN />
<QE_SEND_SOS_BTN />
<QE_TRAN_SOA_BTN />
<QE_SEND_SQ_BTN />
<QE_TRAN_SOS_BTN />
<QE_TRAN_APCODE_BTN />
<QE_TRAN_SPCODE_BTN />
<QE_PUBXMLDOC_BTN />
<QE_CLEAR_BTN />
<DESCRLONG />
</QE_SALES_ORDER>
</Transaction>
- <Transaction>
- <QE_SALES_ORDER class="R">
69
70 PeopleSoft Proprietary and Confidential
<QE_ACCT_ID>27</QE_ACCT_ID>
<QE_ACCOUNT_NAME>JASON
ACCOUNT</QE_ACCOUNT_NAME>
<QE_ADDRESS>THE ADDRESS</QE_ADDRESS>
<QE_PHONE>(PHONE NUMBER</QE_PHONE>
<QE_FROMROWSET />
<QE_TOROWSET />
<QE_SEND_SOA_BTN />
<QE_SEND_SOS_BTN />
<QE_TRAN_SOA_BTN />
<QE_SEND_SQ_BTN />
<QE_TRAN_SOS_BTN />
<QE_TRAN_APCODE_BTN />
<QE_TRAN_SPCODE_BTN />
<QE_PUBXMLDOC_BTN />
<QE_CLEAR_BTN />
<DESCRLONG />
</QE_SALES_ORDER>
</Transaction>
</SAMPLE_MSG>
Updates to SendMail
There are four new optional parameters that can be used with SendMail.
SendMail
Syntax
SendMail(flags, recipients, CCs, BCCs, subject, text,
[, attachment_filenames][, attachment_titles] [, Mail_From]
[, Mail_Sep] [, ContentType] [, Reply_To] [, Sender])
Description
Use the SendMail function to send an email message from a PeopleSoft page. The APIs that support
these subsystems must be present on the system for the function to work.
Note. The code that actually calls SendMail determines the run location, not the originating code.
The function sends a message using standard mail options, including recipient, CC, BCC, subject, and
the text of the note. The message can include attached files, for which you supply fully qualified file
names (that is, file names with paths) and titles (which appear in place of the fully qualified filename in the
message). In addition, you can specify Mail_From, which identifies the source email address. You can
also use the Reply_To parameter to specify the email address to be used by the recipient for replying,
which should be different from the Mail_From address.
See Also
Parameters
Value Description
1 Allows a logon interface if required.
2 Prevents Simple MAPI from using an existing shared session if
one is present.
8 Displays a dialog box which enables the user to create or
modify the message.
71
72 PeopleSoft Proprietary and Confidential
text The text of the message.
attachment_filenames A string consisting of a semicolon-separated list of fully
qualified filenames, containing the complete path to the
file and the filename itself.
attachment_titles Another semicolon-separated list containing titles for each
of the files provided in the attachment_filenames
parameter. The titles appear near the attachment icons in
place of the fully qualified filename.
Mail_From A string used to populate the 'reply-to' field. If this
parameter isn't used, the sender address from application
server configuration file is used.
Mail_Sep Specify the delimiter to be used to separate one email
address from another. The default value is a semicolon (;).
Content_Type Specify the content type of the email as a string. The
default value is plain text.
Returns
Returns a Number value, which, if not one of the following general return codes, is platform-dependent.
73
74 PeopleSoft Proprietary and Confidential
Note. Additional VIM and MAPI error codes may be generated, depending on your email provider.
Example
The following example sets up several variables that are then used to construct an email message that
includes two attachments:
&MAIL_FLAGS = 0;
&MAIL_TO = "dduffield@peoplesoft.com;sweet_pea@peoplesoft.com";
&MAIL_CC = "";
&MAIL_BCC = "mom@aol.com";
&MAIL_SUBJECT = "Live long and prosper!";
&MAIL_TEXT = "Please read my attached CV. You will be amazed and hire me
forthwith.";
&MAIL_FILES = "c:\mydocs\resume.doc;c:\mydocs\coverlet.doc";
&MAIL_TITLES = "My CV;READ ME";
&MAIL_FROM = "MyEmail@Yahoo.com";
&RET = SendMail(&MAIL_FLAGS, &MAIL_TO, &MAIL_CC, &MAIL_BCC, &MAIL_SUBJECT,
&MAIL_TEXT, &MAIL_FILES, &MAIL_TITLES, &MAIL_FROM);
if not (&RET = 0) then
WinMessage("Return status from mail = " | &RET);
end-if;
Updates to SetAuthenticationResult
The SetAuthenticationResult function has an additional optional parameter, DaysLeftBeforeExpire, as well
as additional functionality added to the ResultDocument parameter.
SetAuthenticationResult
Syntax
SetAuthenticationResult(AuthResult [, UserId] [, ResultDocument] [,
PasswordExpired] [, DaysLeftBeforeExpire])
Description
Note. If you set AuthResult to False, ResultDocument must be the text of an error message. This text is
displayed on the signon screen.
Parameters
75
76 PeopleSoft Proprietary and Confidential
Returns
Example
If updateUserProfile(%SignonUserId, %SignonUserPswd, &array_attribs) Then
SetAuthenticationResult(True, &SignonUserID, "", False);
End-If;
The following example is within a function used for logging onto a system:
If (AddToDateTime(&fmc_wsl_exp_date, 0, 0, 0, 0, 10, 0) >= %Datetime) Then
/* WSL logon was within last x minutes, so accept WSL for PS
logon */
SetAuthenticationResult( True, Upper(&userID), "", False);
Else
/* WSL logon was too long ago, so request a more recent WSL logon
*/
SetAuthenticationResult( False, "getmorerecentcookie", "",
False,7); /*displays the customized passwordwarning.html. */
End-If;
In the following example, AuthResult is True and ResultDocument is set as text to be displayed in an
HTML tag.
SetAuthenticationResult( True, &USERID, "Result Doc Text", False, 0);
As part of this example, specify the following in the configuration properties:
singonresultdoc_page=signonresultdoctext.html
In signonresultdoctext.html, add a meta field as follows:
<%=resultDoc%>:
<html>
....
<tr><td class="PSSRCHACTION" no wrap=true><%=resultDoc%></td></tr>
.....
</html>
This produces a screen shot similar to the following:
See Also
Syntax
NumberToString(Format, Number [, Width] [, Precision])
Description
Use the NumberToDisplayString function to format Number according to the pattern specified in Format.
The decimal and thousand's separator are formatted with what is specified with the end user's
preferences.
Specify the Width and Precision parameters when you want to dynamically specify the width or precision.
Both width and precision can be set based on Format. For example, the following statically specifies the
width to be 6, and the precision to be 2:
&MyValue = NumberToDisplayString("%6.2", &Num);
77
78 PeopleSoft Proprietary and Confidential
The following example show the width taken dynamically from the &Width variable:
&MyValue = NumberToDisplayString("%*.2", &Num, &Width);
The following example shows how both the width and the precision values are taken dynamically from the
&Width and &Precision variables, respectively.
&MyValue = NumberToDisplayString("%*.*", &Num, &Width, &Precision);
Parameters
Flag Description
- Left align the number.
$ Fill out field on left hand side with international currency
symbol.
# Force the number to have a decimal point.
blan Pad left hand side with blanks only indicating a negative
k number with a '-' sign.
+ Prefix output with plus sign.
M Append " (cr)" on right for negative numbers and " (dr)" for
positive numbers.
m Opposite of M: " (dr)" for negative and " (cr)" for positive.
A Bracket negative numbers with "[" and "]".
a Bracket negative numbers with "(" and ")".
q Display zeros as blanks.
Q Display zeros as "None".
0 Pad left hand side with zeroes. This must be the last flag
before any other pattern indicators.
• Width must be specified as a non-negative integer. Specifying an asterisks ("*") allows for dynamic
field width specification. The maximum width is 50.
• R specifies rounding in conversion from the internal PeopleCode representation, that is, specifying
12.345 with precision of 2 (%n.2Rt) prints 12.35. In the absence of the R control rounding is the
default.
• T specifies truncation in conversion from the internal PeopleCode representation, that is, specifying
2.345 with precision of 2 (%n.2Tt) prints 12.34.
Type Description
t Type has format like printf %f. For example, the form dddd.dddd.
This is the default value.
v 1000ths separator delimited output. For example, if the separator is
a comma, the format is 1,000,000.02.
w Scientific format like printf %e. For example, the form d.ddddeddd
where "e" indicates exponent. d specifies 1 decimal digit and dddd
specifies an arbitrary number.
W Scientific format (like above, for "w") except "e" is "E".
z Scientific Engineering format like printf %e where the exponent is
always a multiple of 3 and the mantissa is between 1 and a 1000.
Z Scientific Engineering format (like above, for "z") except "e" is "E".
Returns
A string value.
Example
79
80 PeopleSoft Proprietary and Confidential
See Also
NumberToString
TransformExCache
Syntax
TransformExCache(&XmlDoc, FilePath, XsltKey)
Description
The Transform function uses an existing Application Engine program to do transformations. This enables
you to break up the flow of Integration Broker and do transformations when you need to. If you wish to
reuse your Application Engine programs, you can invoke them by using this function.
The TransformEx function does not use an Application Engine program to do a transformation. Instead, it
does an Extensible Stylesheet Language Transformation (XSLT.) This enables you to dynamically do
transformations outside of Integration Broker, such as, performing transformations on pagelets in a portal
every time a page is accessed.
The TransformExCache function also does XSLT transformations without using an Application Engine
program, outside of Integration Broker. Use TransformExCache when you have a large volume of similar
transformations to be done. Caching technology is used with this function. You may see an increase in
performance, as well as an increase in memory consumption, using this function.
Parameters
An XmlDoc object containing the resulting XML from the transformation. Null is never returned. If you do
not want to display an error to the user, place this function inside a try-catch statement.
Example
See Also
• OnChange
81
82 PeopleSoft Proprietary and Confidential
Changes to SwitchUser
The following note in the SwitchUser function description is no longer accurate.
Note. SwitchUser changes only the user for the session of the local application server. It does not
cascade back to the portal or to any other application servers in the environment.
Note. SwitchUser changes the Portal user rather than the content specific user; therefore, it changes
the user ID in all the databases to which you are connected.
Changes to ViewAttachment
A new optional parameter, NewWindow, was added to the ViewAttachment function. The syntax is as
follows:
ViewAttachment(URLSource, DirAndFileName, UserFile [, NewWindow])
6. Change the Field Map for the TO field in Activity email routing to "Roleuser by Oprid Qry" or "Rouser
by Roleuser Qry". Map the bind variable to a field on the page, the value of which will be formatted at
runtime in PeopleCode. For this example, assume it to be RECEIVER_ID. It can be a field of a
derived/work record.
7. In the workflow event where the TriggerBusinessEvent is called, use the following code. Change the
code in italics/red according to the application.
Local Rowset &ROLE_USER;
/* loop through user list to send email to each one of them in their language
code */
For &i = 1 To &ROLE_USER.ActiveRowCount
RECEIVER_ID = &ROLE_USER(&i).ROLEUSER_VW.OPRID.Value;
&temp = TriggerBusinessEvent(BusProcess."bus_proc_name",
BusActivity."activity_name", BusEvent."event_name");
End-For;
83
84 PeopleSoft Proprietary and Confidential
.a Select the Installed check box corresponding to the Hebrew language code.
.b Select Hebrew1 in the Verity Locale Mapping column.
.c Save the changes.
• In general, spidering doesn’t always detect UTF-8 character set correctly and interprets the character
set as internal one. As a result, some characters are corrupted in collections.
• If you are using an Asian language on HPUX, you must install vdk-asian-locale-patch.tar.Z. If you will
be spidering PDF documents in an Asian locale, modify any style.uni files and change /format-filter =
“flt_pdf” to /format-filter = “flt_kv”. Verity vspider does not support indexing UTF-8 documents.
See PeopleTools 8.43 Installation Guide for your database platform, “Setting up the File Server.”
3. Create PeopleSoft Data Mover import scripts (DMSs) using the PeopleSoft Database Setup program.
See PeopleTools 8.43 Installation Guide for Your Database Platform, appendix “Creating a Database
Manually”, section “Create Data Mover Import Script”.
You should see both the English database objects and your new translated objects in the Database
Setup program. Be sure to enter the same database parameters you entered the first time you ran
the Database Setup program to install your English database.
Before clicking Next on the Select PeopleSoft Application dialog box, ensure that you select Add New
Language for the Database Type.
Note. For DB2/OS390 and z/OS customers, please see PeopleTools 8.43 Installation Guide for
DB2 UDB for OS/390 and z/OS, chapter “Creating a Database”, section “Create Data Mover Import
Script”.
Because you already created your database and set up the appropriate database-specific objects,
you can move directly to the tasks in the step, Run Data Mover Import Scripts. Ensure that you run
PeopleSoft Data Mover in bootstrap mode by logging in using your database’s access ID.
5. Run the VERSION Application Engine program against your database to update your PeopleTools
version numbers.
This re-synchronizes the PeopleTools version numbers, taking the new translations into account.
6. Swap your base language if you are planning on running with a non-English base language.
7. Re-run your database audits to ensure that your database is complete.
See PeopleTools 8.43 Installation Guide for Your Database Platform, chapter “Creating a Database”,
section ”Check Database”.
85
86 PeopleSoft Proprietary and Confidential
If None(PORTAL_HPWRK.PORTAL_TAB_NAME) Then
Error MsgGetText(95, 117, "The homepage tab name was not found.");
End-If;
PORTAL_HPWRK.PORTAL_TAB_NAME = %Request.GetParameter("tab");
If None(PORTAL_HPWRK.PORTAL_TAB_NAME) Then
rem Error MsgGetText(95, 117, "The homepage tab name was not found.");
PORTAL_HPWRK.PORTAL_TAB_NAME = &Portal.GetDefaultHPTabOID();
End-If;
When you click the New Window link with the corrected PeopleCode in place, the new browser window
displays a valid PeopleSoft page, and the popup message window no longer appears.
Note. You can click the New Window link on the Personalize Content or Personalize Layout page of any
homepage tab. Regardless of which page you’re initially on, the new browser window always displays the
Personalize Content page of the default homepage tab. You can navigate from there to any other portal
page.
87
88 PeopleSoft Proprietary and Confidential
<td>
.........
</td>
</FORM>
</tr>
</table>
To make the form work, when constructing your HTML, you end the table at the point just before the form
starts, then insert the next part of the original table content inside the form, as follows:
<table id="mytable">
......
</table>
<table.........>
This produces valid HTML in your rendered pagelet, without significantly affecting the resulting user
interface.
• To access the Long Description field of any other portal, navigate to PEOPLETOOLS, PORTAL, PORTAL
DEFINITIONS, then click the Edit button of the portal definition you want to modify.
Note. The portal registry definition is cached on your web server. To enable changes you make to the
portal you’re currently signed on to, you must sign out, then stop and restart your portal’s web server.
Implementing Caching
You implement caching by entering predefined values in a content reference attribute on the pagelet
definition. The caching scope can be:
• User-based.
• Role-based.
• Application-based.
.1 In PIA, open the Content Ref Administration page of the pagelet you want to
cache.
Navigate to PEOPLETOOLS, PORTAL, STRUCTURE AND CONTENT, PORTAL OBJECTS, PAGELETS, select the folder containing
your pagelet, and edit its content reference.
.2 Add a new content reference attribute.
.3 Specify the attribute name and label.
89
90 PeopleSoft Proprietary and Confidential
• public — Implement application-based caching.
Interval is the number of minutes before the cache expires and is subject to an automatic refresh. For
example, to implement user-based pagelet caching with a seven minute expiration, enter:
private,max-age=7
.5 Save the content reference.
The next time a user signs on and displays the pagelet, the caching you specified takes effect.
When you implement pagelet caching, by default the following refresh button appears in the pagelet
header:
To prevent users from manually refreshing the pagelet, you can hide the refresh button.
.1 In PIA, open the Content Ref Administration page of the pagelet you want to
cache.
Navigate to PEOPLETOOLS, PORTAL, STRUCTURE AND CONTENT, PORTAL OBJECTS, PAGELETS, select the folder containing
your pagelet, and edit its content reference.
.2 In the Pagelet Attributes section, select the Hide refresh image check box.
.3 Save the content reference.
The next time a user signs on and displays the pagelet, the refresh button doesn’t appear in the
pagelet header.
.1 Determine the section of documentation to which you want your help button to
link.
Note. If you want to add new PeopleBooks content to the installed PeopleBooks Library (for example,
translated PeopleBooks), refer to the documentation for Managing Your PeopleSoft Online Library on
your PeopleBooks CD or on the PeopleSoft Customer Connection web site (click Support,
Documentation, Documentation Updates by Category, PeopleSoft 8 PeopleBooks, All Product
Lines, Managing the PeopleSoft Online Library and PeopleBooks).
.3 Enter the content name from the HTML PeopleBooks anchor tag as the pagelet
definition Help ID for that content.
.a Select PeopleTools, Portal, Structure and Content, Portal Objects, Pagelets.
.b Navigate to the folder containing the pagelet for which you want online help.
.c Edit the content reference for the pagelet.
.d In the Help ID field of the Pagelet Attributes section, enter the content name.
The name should be the same as the NAME attribute of the HTML anchor tag in the pagelet
documentation, not including the F1ID_ portion. Using the previous examples, you would enter
SDK_BUS_EXPENSES or MY_PAGELET_CONTENT.
.e Save the pagelet and sign out.
.4 Insert the appropriate URL for context sensitive help into your portal’s
configuration.properties file.
Use the helpUrl property to specify this URL. The value you provide must have the following format:
http://webserver:port/path/f1search.htm?ContextID=%CONTEXT_ID%&LangCD=
%LANG_CD%
91
92 PeopleSoft Proprietary and Confidential
Webserver is the domain name of the web server machine where your PeopleBooks are installed.
Port is the HTTP port your web server listens to. Path is the directory path into which you installed the
PeopleBooks. Following is an example of this property:
helpUrl=http://mywebserver:5080/PSOL/htmldoc/f1search.htm?ContextID=
%CONTEXT_ID%&LangCD=%LANG_CD%
.5 Stop and restart your web server to apply the new setting.
When you sign on to your portal, you should now see the following help button in the pagelet header:
When a user signs on to the portal, then invokes an application, the normal signon dialog is bypassed,
and the defaultUSERID and defaultPWD properties are used to automatically authenticate the user.
See Also
Note. Setting the log fence value to 4 also produces a stack trace of PeopleCode, and can affect portal
performance. You should use this setting only for debugging purposes, and reset it to 3 or lower when
you deploy your portal application.
See Also
PeopleSoft 8.42 PeopleBook: PeopleSoft Server Tools Administration, “Understanding Application Server
Domain Parameters,” Domain Settings
93
94 PeopleSoft Proprietary and Confidential
Constructing Pagelets
In this section, under Working with Fixed-Name HTML and Image Objects, add two rows to the table,
as follows:
Under Adding Images to Homepage Tabs, the following introductory sentence is incorrect:
You can specify up to an extra 15 images for a homepage using %BIND variables on tab or pagelet
HTML objects.
Also under Adding Images to Homepage Tabs, add one row to the table, as follows:
Reporting Tools
In PeopleTools 8.43 several enhancements and improvements have been added to the Reporting Tools
Suite. This section highlights those changes.
Crystal Reports
To create a paginated text output file, add this optional -LN command line parameter to the
Process Definition:
Parameter Value and Notes
-LN Use to produce a paginated text file: For
example:
Runtime Prompts
When you are running a Crystal report in PeopleSoft Internet Architecture (PIA) that has
runtime prompts, the prompt values need to be passed in via the Command Line. This can
be done either by hard coding static values in the Process Definition page, or by creating a
PIA page to gather values from the users and dynamically passing them into the Command
Line.
Note. The number and order of the prompt values must be exact.
For example, if you have a report whose query prompts on Business Unit, and you only ever
want the report to run for Business Unit "BU001", you could hard code that prompt value
into the Process Definition in quotes:
95
96 PeopleSoft Proprietary and Confidential
.4 Use the dropdown lists to select the record and field you are prompting on.
.5 Save your changes.
.6 Go to Process Scheduler and modify the process definition parameter list to
include your prompt field using the format :RECORD.FIELD
Note. The resulting command line would look the same as above except; instead of "BU001" it would
contain the selected value.
PS/nVision
In certain situations, a PSNVD.DLL – Failed to Install error previously occurred for non-administrative
users when they tried to launch PS/nVision. This problem has now been fixed. However, the following
message may appear if some components have not been registered:
PS/nVision is not configured properly for this workstation.
To configure PS/nVision:
Note. The System Administrator can also select Start, Run, and type: <psnvs.exe path> /register. For
example, c:\pt842\bin\client\winx86\psnvs.exe /register
Previously, when reports with output type of email or web were run through a report book with the process
scheduler override output type set to default, they were not distributed to the recipient email list or web
report node respectively. This has now been fixed.
Also, when reports with a scope were run directly from a report request or a report book, with the output
type set to email, only the first instance generated by the scope definition was emailed. Subsequent
instances failed with an error message. This has now been fixed.
Previously, when a workbook contained multiple worksheets, where each worksheet represented a report
instance, drilldown from most of the report instances generated incorrect results. This problem has now
been fixed.
You can now drill down on the web for a report that has been run as file output. To use this feature you
must enter a value of 1 for a new option, EnableDrillDownForFile, which has been added to the nVision
section of the Process Scheduler configuration file.
See PeopleTools PeopleBook: PS/nVision, “PS/nVision Reporting on the Web,” Using DrillDown and
“PeopleTools PeopleBook: PeopleSoft Process Scheduler, “Using the PSADMIN Utility”.
97
98 PeopleSoft Proprietary and Confidential
Security for Report Request Secondary Pages
If you select the Report Request - Enter Delivery Template Options hyperlink, the system automatically
displays the Nvs Rqst File Sbp, Nvs Rqst Email Sbp, or the Nvs Rqst Web Sbp page based on the Output
type. Since these secondary pages are implemented using the DoModal people code function, the
security permissions will be inherited from the parent Report Request page, and the Display Only options
set in the nVision Report Request component for these pages will be ignored.
Process Scheduler Run Status for Report Books May Display as Error Temporarily
When running a Report Book with "ignore runtime errors" option, the Process Scheduler run status may
display the status of Error for the report book instance during processing, and then change to Success
when complete. This problem has now been fixed. The Process Scheduler run status is not updated until
all requests in the Report Book have been processed.
In the Using the PS/nVision Visual Basic Interface chapter of the PS/nVision PeopleBook, the procedure
for attaching a macro using NVSInstance Hook was not clear regarding how to enter the name of the
macro. An example has now been added to Step #3. See below.
Previously, successive drilldowns from a single report produced the same output filename for all
drilldowns. To correct this problem, the process instance ID has been added to the drilldown output
filename. This makes every drilldown output filename unique.
For Financial databases, if there is no security defined in Define Business Rules, Administer Security,
Use, Security Options page, the prompt view used for Business Unit was wrong. This has been fixed.
Previously, errors would occur when using the PSADMIN utility to define long path names in the Process
Scheduler configuration file. This problem has now been fixed. PSADMIN will now allow up to 960
characters and will truncate excess characters.
Multiple Process Schedulers and Report Repositories - Purge Process Not Deleting Files From
Report Repository
Previously, if multiple Process Schedulers are running against the same database and each have their
own report repository, the purge process was only deleting files from the report repository associated with
the Scheduler performing the purge. This problem has now been fixed. All files from all repositories will
now be deleted.
The EnableServerCaching and ServerCacheMode options have been removed from the Cache Settings
section of the PeopleSoft delivered psprcs.cfg file. However, if you need to override the default settings
you can enter these options into the psprcs.cfg file manually. System Settings – Event Notification
changes
Previously, the System Settings – Event Notification page was used to add REN server information for
Event Notification. This page has now changed to be view only. The page lists information only for those
REN servers configured for reporting purposes. In addition, the following field names have been updated
to be consistent with PeopleSoft MultiChannel Framework information:
Name: Cluster ID.
Internal URL: Cluster URL.
When the Test button is selected for the desired REN Server, a new Test REN Server page is displayed.
Buffer tests can only performed on the Cluster URL, and Ping tests can only performed on Browser
URLS.
See: PeopleTools PeopleBook: PeopleSoft Process Scheduler, Defining Process Scheduler Support
Information, Defining System Settings, “Testing Event Notification.”
99
100 PeopleSoft Proprietary and Confidential
Configuring a REN Server
The procedures for configuring a REN Server have been updated. The basic steps for configuring a REN
Server are included in the PeopleSoft Process Scheduler PeopleBook. The PeopleSoft MultiChannel
Framework PeopleBook contains more detailed information regarding REN Servers.
See PeopleTools 8.42 PeopleBook: PeopleSoft Process Scheduler, Defining Process Scheduler Support
Information, Defining System Settings, “Event Notification – Configuring a REN Server.”
See PeopleTools 8.42 PeopleBook: PeopleSoft MultiChannel Framework, “Configuring REN Servers.”
The Window output type is not available if the user does not have REN Server Report Window
permission, or there is no active REN Server cluster available for Reporting.
For processes that are triggered without using the Process Request dialog, the following message will
appear: You do not have the permission required to run window option. However, the processes will still
run defaulting to the output type of Web.
Note. To grant access to the new browser window, the permission lists of the users must include full
access for the Real-time Event Notification for Reporting Window and the WEBLIB_RPT web library with
full access.
See PeopleTools PeopleBook: PeopleTools Security, Working With Permission Lists, “Defining
Permission Lists.”
To grant access to the new browser window, the permission lists of the users must include full access for
the Real-time Event Notification for Reporting Window and the WEBLIB_RPT web library with full access.
The PeopleSoft delivered ProcessRequest PeopleCode can only be used for processes that do not pass
in extra parameters. This means that reports that require extra parameters can only be run from the Run
Control page.
PSSQR.EXE Information
The executable program PSSQR.EXE is a wrapper program used by PeopleSoft Process Scheduler to
run SQR reports. It is not designed to run manually outside of Process Scheduler.
A document titled Securing Report Repository - WebSphere has been posted to Customer
Connection. This document is a replacement for the procedure to set up Basic Authentication in
WebSphere, which can be found in PeopleTools PeopleBook: PeopleSoft Process Scheduler, Appendix E
– Securing Report Repository for HTTP, “Setting Up Basic Authentication in WebSphere”. Please use
these instructions in place of the instructions found in the 8.42 PeopleSoft Process Scheduler
PeopleBook.
The following rules apply when using the Override Notification List from Processes in Job List option:
Job Definition: Select to notify only users that are specified in the job definition. If cleared, users
specified in both the job and process definitions are notified.
Job Within Job: Select to notify only users that are specified in the main job definition. If cleared, users
specified in the main job, jobs within, and process definitions are notified.
Important. The Override option is ignored for any job listed within the main job.
Scheduled JobSets: The Override option is not available for scheduled JobSets. Only notification
information entered in the JobSet will be in effect. Once Process Scheduler detects there are
notifications in any of the items of the JobSet, it will ignore any notification information found
in the Job Definition and Process Definition. If notification information is not entered in the JobSet,
the previous rule applies.
The following rules apply when using the Override Distribution List from Processes in Job option:
Job Definition: Select to use the distribution IDs from the job definition. If the check box is cleared
distribution IDs from both the job and process definitions are used.
Job Within Job: The Override option for the main job is ignored. Process Scheduler uses the distribution
IDs from the PSJob definition. If the check box is cleared distribution IDs from both the PSJob and
process definitions are used.
101
102 PeopleSoft Proprietary and Confidential
Note. When the Override option is selected for the main job, Process Scheduler uses the distribution IDs
from the main job definition and ignores only the distribution IDs from the individual process definitions
within the main job.
Scheduled JobSets: The distribution list is based solely on the information in the JobSet. If the JobSet has
no distribution list, the requester will be the only recipient of the reports.
Only message information entered in the JobSet will be in effect. Once Process Scheduler
detects there are messages in any of the items of the JobSet, it will ignore any message
information found in the Job Definition and Process Definition.
Previously, Process Scheduler would always use the default settings for output types and output formats.
It would ignore any output type or output format defined in the JobSet. This problem has now been fixed.
Process Scheduler would also ignore any distribution information entered in a JobSet. Information would
only be distributed to the requester. This problem has now been fixed.
The Schedule JobSet Definition requires you to enter time information. The Begin Date and Time fields
default to the current date and time. To run the JobSet immediately, leave these fields with the default
values, activate the JobSet, and select Save. Do not click the Run Now button, as this will also trigger a
process request. The Run Now button should only be used if the Begin Date and Time values are
changed to a future date/time and you also want the process to run immediately.
Previously, when email notification information was entered in a JobSet, it caused a core dump or an
abort of the Application Server or Process Scheduler. This problem has now been fixed.
Previously, when using HTTP transfer protocol, directories and files were not getting purged from the
report repository. This problem has now been fixed.
Due to the fact that the Process Output Format Settings page uses information regarding output types, it’s
important to save any changes made to output type settings before attempting to change an output format
setting.
Filtering criteria should be used to reduce the number of reports in your view because the more reports
you have in your view the longer it takes the system to fetch them. A warning message will display the
first time you open the page if there are more than 1000 reports in your view, or when changing the filter
criteria causes more than 1000 reports to display.
PeopleSoft now automatically archives the Process Scheduler configuration file whenever it is changed.
The older version is archived as PSPRCS_<Time Stamp>.CFG and the current version becomes
psprcs.cfg. The location of the archive directory is <PS_Home>\Appserv\prcs\<database>\Archive. For
example, C:\PT843\Appserv\prcs\FIN843\Archive.
If your report output contains characters outside the EBCDIC invariant character set, such as accented
characters required for Western European languages, and your Process Scheduler is running on OS390,
you must use HTTP to transfer reports to the repository. The FTP transfer option will not correctly
transfer report output containing these characters.
If spaces exist in the WINWORD path in the Process Scheduler configuration file (psprcs.cfg), WinWord
reports will fail. You will need to modify the Process Type Definition and add quotes around the entry in
the Command Line field, for example " %%WINWORD%%\WINWORD.EXE".
PeopleSoft Query
Previously, when trying to run a query to Excel using an HTTPS server, access errors occurred. These
errors were due to a known Microsoft IE bug (see Microsoft Knowledge Base Article Q323308). Microsoft
documented a workaround to this problem, which has now been implemented.
In PeopleTools 8.17, the method for which query designer generated Eff Date Logic SQL for a query was
changed. Due to numerous requests, PeopeSoft has reverted back to the original functionality, which is
to only generate criteria for Eff Date Logic for key fields, which physically occur before the EFFDT field in
the record. Any keys located after the EFFDT field in the record will not be included in the Eff Date Logic.
Previously, a browser timeout would occur when trying to select values from a table that contained a large
amount of data. A new Search option is now available, which uses a wildcard to limit the amount of data
returned. For example, if the user enters a value of 10, the system will return all values, (up to a total of
300), that begin with 10, such 10, 100 and 10069. The user can also enter a single value without having
to use the Search option.
Note. The new Search option is also available to select a constant value.
See PeopleTools PeopleBook: PeopleSoft Query, Defining Selection Criteria, Entering Comparison
Values, “Selecting a Constant Value,” and “Building a List of Values.”
103
104 PeopleSoft Proprietary and Confidential
Translate Values and Unions Clarification
If translate values are used, PS Query appends fields to the select list in the SQL that are not specified in
the select tab of query. This causes problems when making a union because the select fields must be the
same for both sides of the union. Therefore, translate values, long or short description, cannot be
displayed in a union query. Only the code for the field can be selected for output display.
Previously, when using PIA Query, a user could run or schedule workflow queries even if they did not
have create permission. This has now been fixed to match Windows Query functionality. If a user does
not have permission to create a workflow query, they do not have permission to run or schedule a
workflow query.
PeopleSoft 8.43 includes the new Enable Auto Preview feature. Enable Auto Preview alleviates the need
to click the Rerun Query link on the Preview page each time you want to preview the query’s most recent
changes. When this feature is enabled, your query automatically runs each time you click the Preview tab.
If you have large trees, (over 40,000 nodes), we recommend increasing the heap size on the web server,
and also increasing the Tuxedo receive timeout to 72000 in the web server pstools.properties file.
To increase the heap size using WebLogic on UNIX, open startWebLogic.sh and edit the following line:
$JAVA $JAVA_OPTIONS -ms64m -mx64m -classpath $JAVACLASSPATH
-Dweblogic.class.path=$WEBLOGICCLASSPATH -Dweblogic.home=.
-Djava.security.manager -Djava.security.policy==`pwd`/weblogic.policy
PSweblogic
To increase the JVM heap from 64MB to 128MB, update -ms64m -mx64m to –ms128m –mx128m.
See PeopleSoft Server Tools Administration, “Administering Web Servers.”
Branch trees were designed to give multiple users the ability to maintain separate sections of the tree
while working simultaneously. Due to the risk of conflicts the following actions are no longer allowed when
working with tree branches. A message will display if a user attempts to perform any of these actions:
Action Comment
Moving nodes with subbranches. Not allowed in order to keep tree
branches independent.
Switching levels on nodes with Not allowed in order to keep tree
subbranches. branches independent.
Unbranching nodes with subbranches. Subbranches should be unbranched first.
• Switching levels.
Previously, in Tree Viewer if a tree is branched, search results listed the tree numerous times, once for
each branch including the root branch. For example, a tree with three sub-branches would be listed four
times in the search results. Branches are ignored in Tree Viewer. Therefore, the search results should
only return the main tree. This problem has now been fixed.
Previously, edit checks were not being performed when the user modified the to or from range of a detail
value. This problem has now been fixed. The edit checks performed include overlapping detail ranges,
duplicate detail values, duplicate detail values under the same parent ( if duplicate details are allowed in
the tree).
See PeopleTools 8.42 PeopleBook: PeopleSoft Tree Manager, “Creating Trees,” Performing Audits
The drag and drop functionality does not work on all the supported browsers listed in the platforms
database. System requirements for the drag and drop functionality for PC are: Microsoft Internet Explorer
version 5 (IE5) and higher or Netscape Navigator version 6 (NN6) and higher. System requirements for
Macintosh are: Netscape Navigator version 6 (NN6) and higher.
105
106 PeopleSoft Proprietary and Confidential
Application server configuration files for previous versions of PeopleTools can be applied to a
PeopleTools 8.43 application server. This enables an administrator to rapidly reproduce an existing
environment on the new version of PeopleTools. Any new configuration parameters that do not exist in
the imported configuration file are set to default values. The import option is located in psadmin under
menu options 4 and 7 for the Process Scheduler and Application Server respectively.
A new automated “clean-up after shutdown” procedure has been added to PeopleTools 8.43. When the
application server is shut down, the clean-up procedure runs to ensure that any related processes are
removed. In addition, a new “watchdog process” has been added to each domain configuration. This new
background process is managed by the system automatically and periodically monitors the health of the
domain, and recovers the system from any processes that are in a hung state.
Miscellaneous Notes
PeopleSoft Ping
The PeopleSoft Ping feature is now available with Netscape 6.2 browser.
Index Location
Application Server
To track changes made to PSAPPSRV.CFG and the history of the changes, a new sub-directory has
been added for archiving versions. This sub-directory, named archive, resides in the domain name
directory as in $PS_HOME\appserv\domain name\archive, where you can find the current version of
PSAPPSRV.CFG.
When you boot the application server domain for the first time, PSADMIN places a copy of
PSAPPSRV.CFG in the archive directory. In subsequent bootups, if PSADMIN detects a change in
PSAPPSRV.CFG based on the time stamp values, it will replace the current PSAPPSRV.CFG with the
latest version. The file name of the new version is changed to psappsrv_mmddyy_hhmm_ss.cfg.
Application server configuration files for previous versions of PeopleTools can be applied to a
PeopleTools 8.43 application server. This enables an administrator to quickly reproduce an existing
environment on the new version of PeopleTools. Any new configuration parameters that do not exist in
the imported configuration file are set to default values. The import option is located in PSADMIN, menu
options 4 and 7 for the Process Scheduler and Application Server respectively.
This release includes two enhancements to detect and kill orphaned application server
processes.
Note. These enhancements only affect application server domains, not process scheduler domains.
To identify orphaned application server processes, all server processes within a server’s domain must be
uniquely identified. Therefore, the system appends a unique number to the DOMAIN ID defined in the
PSAPPSRV.CFG file. If you refer to DOMAIN IDs in scripts or processes, you may need to
change those to reflect the new naming convention.
The command line varies slightly depending on the application server process--but will look similar to the
following:
PSAPPSRV -C dom=pt84_52692 ...
(Before 8.43 no numbers are appended to the DOMAIN ID: dom=pt84 ...)
One enhancement affects the application server domain shutdown operation in PSADMIN
(both normal and forced shutdown). Following a successful domain shutdown, PSADMIN
checks and kills orphaned processes in the domain. If PSADMIN identifies and kills any
orphaned server processes, it displays a screen message at the end of the shutdown
operation.
PSWATCHSRV Process
A new server process, called PSWATCHSRV, has been added to the application server domain. Every 2
minutes, PSWATCHSRV wakes up to identify and kill any hung or orphaned server processes. If any
hung or orphaned processes are found, it prints a message to the application server log file.
This option now has a default value of 1, that is, enabled. To disable database monitoring, set the value to
0.
This option is required for Database Level Auditing. How it works varies slightly depending on the
database platform. This option enables you to view more information regarding the clients connected to a
107
108 PeopleSoft Proprietary and Confidential
database server through the application server. For instance, you can view the client machine name or
user ID associated with a particular connection. Without this option enabled, all connections appear
somewhat anonymously, as in PSFT or APPSERV. Not supported on Informix and DB2 UDB (UNIX/NT).
For use with IBM DB2 UDB only. PeopleSoft added a bit flag value was added to the DBFlag option to
indicate how the table should be purged, using an SQL delete or truncate operation. The new value is bit
value 2, meaning to "Ignore Truncate command for DB2Unix (NT, Solaris, HPUX, AIX), Use SQL Delete
instead". This instructs the Meta SQL %TruncateTable to issue an SQL delete command instead of the
DB2 truncate operation. This new flag was required due to a bug within IBM DB2 V7 and should be fixed
when V9 is released.
This bug is specific to the UDB Enterprise Edition (EE), not to be confused with Extended Enterprise
Edition (EEE); and when used with a huge bufferpool space intended to hold the Truncate table data.
Do not set this bit flag (2) for normal application usageuse Truncate to purge the table.
Browser URL
A new option has been added to define the browser URL that is shown on the browser. This is only used
to create a PS_LOGINLIST entry when a Reverse Proxy Server (RPS) and pswebservername is not
already defined. For example, browserURL=http://hr.peoplesoft.com:8000.
A new option has been added to support Dirty Reads / Uncommitted Reads from PSQuery for DB2/UDB.
Enable the dirty read option by specifying UseDirtyRead=0.
Timeout Warning
A new timeout option warns users when their browser session is about to expire; then, they have the
option of continuing with their current session by clicking the OK button in the warning message. If the
user does not respond within two minutes, the session ends and the expired connection page opens. As
in the past, the user can then return to the PeopleSoft signon page. You can change the default settings
for this feature in the configuration.properties file.
Defaults are SessionTimeoutWarning=1080 (18 minutes) and SessionTimeout = 1200 (20 minutes).
Two new values, 4 and 5, have been added to the LogFence property in the PSAPPSRV.CFG file. They
allow for more detailed error messages in the application server log file. The default value is 3, which is a
tracing level 1. Set the value to 4 or 5 (tracing level 2 or 3, respectively) for more detailed error messages,
for example, LogFence=4.
Specifically, setting LogFence=4 prints the stack trace of PeopleCode and could negatively impact
performance. This value should be used for debugging only and not while in production.
However, setting LogFence=4 or =5 prior to sending GSC the application server log file facilitates the
early diagnosis of a problem.
To simplify configuration management, the MaxInMemoryObjects parameter has been removed from the
PeopleSoft delivered psappsrv.cfg file.
Cache Settings
To simplify configuration management, the Cache Settings section of the PeopleSoft delivered
psappsrv.cfg file has been removed. The behavior will be to cache all metadata types and to have
separate cache directories for each process.
Web Server
This section describes how to turn off compression in the web server configuration properties file, which is
T-RKUMAR-QN9J2 Downloading query results to Excel does not include all rows
It applies to all database and operating system platforms.
Note. This workaround has not been processed in a formal quality regression test cycle. PeopleSoft
strongly recommends that you thoroughly test this workaround in a development environment before
applying it to your production environment. Document this workaround completely because it may be
detected during your next upgrade and may be different than the final solution delivered in a PeopleTools
patch or Minor/Major release.
This section decribes how to disable browsing of a directory in IBM HTTP Server.
109
110 PeopleSoft Proprietary and Confidential
.1 If you are using IBM HTTP Server 1.3.19.x as RPS with WebSphere AEs 4.x, open
the {IBM_HTTP_SERVER_HOME}/conf/httpd.conf file.
.2 Search for the following:
<Directory “C:/IBM HTTP Server/cgi-bin”>
AllowOverride None
Options Indexes
</Directory>
.3 Change “Options Indexes” to “Options None”. After the change, you should
have the following:
<Directory “C:/IBM HTTP Server/cgi-bin”>
AllowOverride None
Options None
</Directory>
This setting prevents display of the directory structure on the browser when IBM HTTP Server fails to find
the respective file within the document root.
PeopleSoft supports IBM HTTP Server 1.3.19.x in PeopleTools 8.4, 8.41, 8.42, and 8.43. By default,
multiviews is disabled.
IBM WebSphere
Please note that the section entitled, “Understanding WebSphere AEs,” has been removed from the
Working with IBM WebSphere chapter of PeopleSoft Server Tools Administration PeopleBook.
Refer to the following Port Table if you receive port conflict errors when starting IBM WebSphere. The
values refer to ports in WAS_ROOT}/config/server-cfg.xml file. Ensure that you don’t use port numbers
used by other processes. After changing port numbers, re-start WebSphere.
Port Use Current Port # New Port # XML tag in server-cfg.xml file
OLT 2102 2103 <objectLevelTraceSettings
xmi:id="ObjectLevelTrace_1"
enable="false"
hostname="localhost" port="2102"
debug="false" sourcePath=""/>
LSD 9000 9001 <locationServiceDaemon
xmi:id="LocationServiceDaemon_1"
hostname="localhost" port="9000"
mode="NONE"/>
111
112 PeopleSoft Proprietary and Confidential
.3 Restart WebSphere.
.4 Execute the following command from {WAS_ROOT}//bin folder:
$ra {Machine_Name} 900 AES
Application resources(servlets).
Runtime resources.
JVM Memory.
WebSphere threads.
Web applications.
The Log Analyzer analyzes and reports errors in the activity.log (WAS_ROOT)/logs/activity.log file). The
analysis contains an explanation of an error and how to recover from it.
To start Log Analyzer in
• Windows, execute the file {WAS_ROOT}/bin/waslogbr.bat
There have been reports of IBM WebSphere Java language Out of Memory errors on PeopleSoft
applications using PeopleTools 8.42 and 8.43 and IBM WebSphere Server 4.0.3 on Windows, ,AIX and
Linux platforms.
This problem is caused by a JRE bug in IBM WebSphere's embedded JRE 1.3.1 [ Build:April 2002 ] on
Windows, AIX and Linux platforms. The problem is resolved in IBM WebSphere's JRE 1.3.1
[ Build:November 2002 on Windows , AIX and Linux platforms]. Errors may be logged in
{WAS_HOME}/logs/default_server_stdout.txt or in {WAS_HOME}/logs/default_server_stderr.txt files.
If you find this kind of error logged follow the instructions to upgrade JRE.
Note. These instructions assume WebSphere is owned by root and you are upgrading JRE as root user.
.1 Extract the following file from Customer Connection to any folder. If you are
unable to locate it, call Global Support Center.
ftp://ftp.peoplesoft.com/outgoing/ptools/websphere/4.0.3/JRE/win32/JDK_Refresh3_Fix_WINDOWS.z
ip.
.1 Extract the following from Customer Connection to any folder. If you are unable
to locate it, call Global Support Center.
ftp://ftp.peoplesoft.com/outgoing/ptools/websphere/4.0.3/JRE/aix/JDK_Refresh3_Fix_AIX.ta
r.gz.
.1 Extract the following file from Customer Connection to any folder. If you are
unable to locate it, call Global Support Center.
ftp://ftp.peoplesoft.com/outgoing/ptools/websphere/4.0.3/JRE/linux/JDK_Refresh3_Fix_LINU
X.tar.gz.
113
114 PeopleSoft Proprietary and Confidential
{WAS_HOME}/java/bin$./java –fullversion
.3 To check the java version for Windows, type in the following command:
{WAS_HOME}/java/bin>java –fullversion.
You should be able to see the java full version as “J2RE 1.3.1 IBM AIX build ca131w-20021107
ORB130”, that is, the java version from November 2002 build. This will ensure that the upgrade is
successful.
Open {WAS_HOME}/config/server-cfg.xml file and check if other applications are already using the
ApplicationRef_8,WebModuleRef_9 ,WebModuleRef_10 and WebModuleRef_11 , then replace them with
other unique numbers.
To check if other applications are using these references, open {WAS_HOME}/config/server-cfg.xml and
search for these tokens.
This will ensure all the applications are loaded during WebSphere boot.
CompressCacheFiles Option
When using a BEA WebLogic 6.1 sp4 web server with a WebLogic 6.1 sp4 reverse proxy server, set the
option compressCacheFiles=false.
There is a document posted on Customer Connection that explains how to configure your system so that
you can monitor PeopleSoft sessions using the WebLogic console.
You can add multiple URLs to spider. To add more to the list, use the plus button. To remove a URL from
the list, use the minus button. If you forget to include the http:// (scheme) portion of the URL, the system
automatically includes it.
URLs should contain only the alphanumeric characters as specified in RFC 1738. Any special character
needs to be encoded. For example, a space character should be encoded as "%20", a '<' should be
encoded as "%3c". For more information, see http://www.w3.org/Addressing/rfc1738.txt.
Timeout Settings
The following tables list timeout settings for PeopleTools 8.43 web server, application server, Process
Scheduler, and PIA.
All configuration changes made on the web server require a restart before taking effect.
115
116 PeopleSoft Proprietary and Confidential
in configuration.properties. This
will prevent state loss and dangling
HttpSessions on the web server.
All configurable settings for the application server require modification in PSADMIN.
117
118 PeopleSoft Proprietary and Confidential
nt Cleanup Session.
Timeout
Increasing this value can keep
unnecessary server-side resources
from being allocated. Setting this
value can cause resinstantiation of
resources for a client that has
surpassed the inactivity interval.
This value is only required for three-
tier connections.
Workstation psappsrv.cfg The amount of time allowed for the 5 minutes
Listener/init WSL process to start. The customer
Timeout should not adjust this setting.
This value is only required for three-
tier connections.
For each psappsrv.cfg The time period permitted for the PSAPPSRV:
server services to run in the process in 300 seconds
process/Ser question. If the service has not (5 minutes)
vice completed within the allotted time
PSOPTENG:
Timeout period, Tuxedo will terminate the
270 seconds
server processing and then restart
(must be
the server process.
less than
Set to the longest time that any PSAPPSRV
service is expected to take for that timeout)
particular server.
PSSAMSRV:
300 seconds
PSQCKSRV:
300 seconds
PSQRYSRV:
1200
seconds (20
minutes)
PSBRKHND_
dflt: 1200
seconds
PSSUBHND_
dflt: 1200
seconds
PSPUBHND_
dflt: 1200
seconds
A value of 0
infers an
infinite
timeout on
any service.
This is the
setting that
most of the
internal
developer
templates
assume.
All configurable settings for the Process Scheduler require modification through domain configuration
within PSAdmin.
119
120 PeopleSoft Proprietary and Confidential
PIA Timeouts
A number of additional timeouts may be set through PIA. These settings reflect changes at the database
level that may pertain to different groups of users.
Note. The timeout settings in PIA are optional and are not required to run PIA. However, an
understanding of how these settings can contribute to a user’s session duration is important in the context
of other timeout values described in this document.
server to be effective.
PeopleTools Security
The following updates have been made to PeopleTools Security for PeopleTools 8.43.
121
122 PeopleSoft Proprietary and Confidential
Password History
Note. Technically, the role membership can involve more than directory group. You can determine role
membership using any arbitrary LDAP search criteria, such as condition other than just group
membership. For example, you could assign everyone whose last name starts with S to a role.
Note. Although you can’t search directly for members within a group based on certain directory criteria,
you can use the search filter to search for a specific group. Once you've located the group, you can then
select the directory attribute that identifies the group membership. Alternatively, you can write some
PeopleCode to determine group membership using any arbitrary LDAP search criteria.
Note. The behavior of the SwitchUser built-in function has changed — please refer to the discussion
about SwitchUser in the PeopleCode section of the release notes, under Changes to SwitchUser.
123
124 PeopleSoft Proprietary and Confidential
SCHDLR_<mmdd>.LOG:
Process Scheduler encountered an error sending the request to the AE
Tuxedo Server
then set Recycle Count = 0 in the PSAESRV section (Application Engine Tuxedo Server) of the Process
Scheduler configuration file (PSPRCS.CFG). The PSADMIN utility provides an interface for editing the
PSPRCS.CFG file.
PeopleSoft Workflow
The following updates have been made to Workflow for PeopleTools 8.43.
Worklists
The following information applies to worklists.
Creating Worklists
Before you create a worklist routing for an activity, create a worklist record definition. The worklist record
determines what fields of information the system stores for each work item and in what order the work
items appear.
Worklist Replication
When replicating worklists between databases, keep the following behavior in mind.
PeopleSoft formats the Worked By Activity field by examining the worklist definition in the target
database. If the activity definition is not in the target database, the system can’t format the Worked By
Activity field. So, in some cases, this field may appear blank after replication, and as long as the
WORKEDBYACTIVITY is not defined in the target database this field will be blank.
There are two solutions to this issue:
Databases at the same From the source database, export the replicated worklist
release level (8.4x to 8.4x) definition (activity) and the worked by activity (if they are
not the same). Import the definitions into the target
database.
Databases at different Manually recreate the activity in target database.
release levels (8.1x to 8.4x)
In previous releases, in some cases the Worklist Detail and Worklist Summary pages returned all of the
worklists in the system as opposed to those associated with a particular user, which often exceeded 300
rows. Now the user can filter the worklists by user. To refresh the list, click the Worklist link at the top of
the page.
There is a new checkbox named Delete Pooled WL When Select, which allows the user to specify when
the pooled worklist is to be dropped from another's queue.
Note. You must reboot the application server after enabling this option.
The Previous User field only reflects the last UserID assigned to a worklist item. It will be updated when a
user accesses the Worklist and Worklist Detail pages, the Worklist tab for a user profile, and the tools
update worklist entries page. If you have developed any custom worklist maintenance pages, you must
update this field manually.
The Filter on the Worklist and Worklist Detail pages now shows the worklist assigned to the current user
only. If there are new worklist items assigned to the user, the user needs to click the Worklist link again to
refresh the list.
Notification Templates
Notification template variables do not indicate the true order of the variables. The order of template
variables is determined by the sequence of the variables specified in the message text on the Define
Template page.
125
126 PeopleSoft Proprietary and Confidential
• PS_RT_TYPE_TBL
• RT_TYPE_LANG
These database objects currently reside in the Common Components project, which is named
EO_COMMON. If you require these features to function within the PTSYS database, then you must
transfer these tables into the PTSYS database using the upgrade copy feature in Application Designer.
• Ctrl + Delete
Scenario A
In this scenario, a worklist item is reassigned to a user within the supervisor level.
The previous behavior of the system in this scenario is as follows. Upon approval, a message appears
stating that the Worklist needs Manager Approval (if a Message Catalog is used in the Approval Rule
Set). At this point if the worklist is sent to Virtual Approver, and the worklist is completely dropped from
the user’s list.
Scenario B
In this scenario, the worklist item is reassigned to a user with no approval authority.
The previous behavior of the system in this scenario is as follows. Upon approval, the system completely
drops the worklist from the user’s list with no message shown.
Scenario C
In this scenario, the worklist is reassigned to a user within the president level, who can then approve the
item. This behavior is correct and has not been modified in PeopleTools 8.43.
In PeopleTools 8.43 the following options have been added to the Worklist System Defaults page.
127
128 PeopleSoft Proprietary and Confidential
Application
Designer- Issue using Translate Tools
Page Defn 1977931 560883000 with Change Control activated Fixed logic in code.
129
130 PeopleSoft Proprietary and Confidential
1881002,
1947015,
Application 1959487, Message 108,544 is not in
Engine 3034038 132797000 8.4x databases. Message added.
1902722,
1915980,
1998333, PT 8.18.07 - PSAPPSRV -
Application 3001191, exception: Illegal instruction -
Server 3015262 103125000 AIX - DownToChild Fixed logic in code.
PT 8.41.03 - Solaris
PSAPPSRV server exception
- fb4da268 Added preventive fixes, so that
__1cJCPSScrollOGetSortVie when the request contains an
Application 1883157, wPos - SIGSEGV: invalid action, it should not
Server 1898356 119974000 Segmentation violation cause crash.
1761453, EnableDBMonitoring=1
1804983, causes Application Server
1845683, crash with SQL Server 2000,
Application 1854023, when a really long user name
Server 3032158 574892000 is used. Fixed logic in code.
131
132 PeopleSoft Proprietary and Confidential
2004202,
2007233,
2008703, psdbgprc.exe error when
2025289, getting an existing record in
Component 2026841, RD_CONSUMER_2_CI Fixed logic in code to improve
Interface 3024035 565491000 component interface tester. duplicate name checking.
1992477,
1998239,
Component 2005403, PT: Component scope
Interface 2047340 566734000 variables appear to be reset. Fixed logic in code.
2022961,
2041976,
Component 2051772, Can't access PSMessages
Interface 3003836 572284000 from VB in PT 8.42. Fixed logic in code.
133
134 PeopleSoft Proprietary and Confidential
CTI & PT 8.16.01 with The CTI default URL now uses
extremely large web server ps_newwin to avoid "Page
CTI 1944880 110286000 /cache directories. Expired" errors.
135
136 PeopleSoft Proprietary and Confidential
1943669,
1990407,
1992528,
2004098,
2036529, Help call always passes Not required--works as
General 3004806 131495000 25000 as the context ID. designed.
French multilingual
installation of CRM 8.4 on
Oracle: incorrect data on
Message table
PSMSGCATLANG - The
Global apostrophe character is Fixed erroneous characters in
Technology 1782472 101292000 displayed as ¿ the French message dat file.
Integration Broker:
communication issue
between
Integration HTTPTargetConnector and
Broker 1949861 102238000 webMethods XML Adaptater. Fixed logic in code.
PT 8.42.x: PeopleSoft
Integration HTTPListeningConnector
Broker 2015382 570021000 replying with wrong charset. Fixed logic in code.
137
138 PeopleSoft Proprietary and Confidential
RemoteCall() function in
subscription PeopleCode fails
with Think-time PeopleCode
event(RemoteCall) invoked
Integration while a cursor is busy is Changed logic in RemoteCall ()
Broker 2037335 580389000 illegal. (2, 149). function.
Integration Gateway
Transformation Errors seem
Integration to send back error *and* Changed logic in
Broker 3000673 583577000 process. HttpListeningConnector.
FP: T-WHOELT-AV2CC
Issue with PeopleCode
Internet setauthenticationresult 3rd A new flag added to
Client 1885587 131728000 parameter - not working. configuration file.
psft.pt8.definitions.GenParms
Internet needs to be serializable for Made class GenParrms
Client 1929157 142476000 stateful failover to work. serializable.
Browser personalization
Internet 1839277, Remove toolbars and location settings added, documented in
Client 1844450 145309000 bar from the browser window. release notes.
139
140 PeopleSoft Proprietary and Confidential
2000960,
2047959,
3024670, PSNVS.EXE AND EXCEL
3032514, doesn't close after running a Added a third CoUninitialize in
nVision 3035438 132643000 report. ExitInstance.
2000193,
2012954,
2035494, Modified code to update the
3036194, PSPRCSRQSTTEXT table if it
3037562, nVision DrillDown causing detects the Parameter List
nVision 3043071 569293000 issues with PSPRCSPARMS. exceeds the 254 character limit.
nVision 1919684, 569471000 8.18 and 8.42 Now use COALESCE and
1945153, PSTREESELECT tables %TRIMSUBSTR only for DB2 to
2015624, causing null detail node not avoid the extra padding of white
2021202, return any value. space and to force insertion of
2036539, white space when the result of
2047256, %TRIMSUBSTR is NULL. For
2048651, all other DBs we revert to the
2052191, original usage of
3013207,
3027773,
3032415,
3032845 %SUBSTRING.
Appserver crash -
CRTFieldOccurs::TestHiddenI
nAllRows+2a (E:\PT842rc7-
Panel retail\SRC\pspnlrt\rtfieldoccur
Processor 1995909 134595000 s.cpp line 2947). Fixed logic in code.
1878307,
1975586,
1984059,
2009962,
2013984,
2016530,
2036785,
2057335, Added new Scroll logic that will
Panel 3029920, Issue with "CUSTOMIZE" re-apply the user grid
Processor 3037840 135915000 option on GRID in PIA PAGE. customizations.
141
142 PeopleSoft Proprietary and Confidential
Applying personalizations to
PIA Core the grid on the page
Technology 1972863 561252000 RECV_WPO fails. Changed logic in code.
143
144 PeopleSoft Proprietary and Confidential
java.lang.NullPointerExceptio
n error messages in the
PIA Core 2021706, pia_weblogic log file with
Technology 3034043 572778000 WebLogic 6.1 and sp2. Fixed logic in code.
1892093,
1931488,
1940203,
1940801,
1945393,
1969123,
1983525,
1996015, Publishing a word document,
2007604, but click on "Click here for
2025723, details" to view the document, Portal will pass a flag to
2032487, a script error pop-up piaDirect to indicate if it is a
2035370, 'document.win1.elements' is target content request. If so,
Portal 3022615 112850000 not an object. post data will be used.
WebLogic 6 on PT 8.40.04 is
crashing daily (thousands of
connections not being
cleaned up and heap size
Portal 1853565 117928000 never reclaimed). Fixed logic in code.
145
146 PeopleSoft Proprietary and Confidential
FP: T-THASSL-UK4HF
Incorrect characters are
shown when a page is
displayed without a refresh
Portal 1807148 126792000 from server. Correct characters now display.
On first log-on to portal and
minimize a Pagelet will add
pagelets which are not given
access. When clicking on the
content, could see that those
pagelets are checked. After
saving the Personalize
Portal 1969191 135946000 Content works fine. Correct pagelets now copied.
1974432,
2013453,
2022784, Changes made on a
2048415, permission list removes
3021950, access to other pages within
Portal 3041904 571622000 that folder in Portal. Fixed logic in code.
Customer1: Intermittent
login.jsp page occurs when
using the Customer Portal Using more explicit delimiter for
Portal 2047312 577564000 (SMSESSION corruption) cookie attributes.
1919825, Can't run Crystal Reports You can now run Crystal
Process 2022295, when logging in through an Reports when logging in
Scheduler 3030653 102223000 LDAP Server through an LDAP Server.
PeopleCode - Schedule
Method Of Modified the code to prevent
CreateProcessRequest() API two users from getting the same
Process 1950340, is not handling the Duplicate instance (if they call the function
Scheduler 2018719 117029000 Row insert properly. almost at the same time).
147
148 PeopleSoft Proprietary and Confidential
1924455,
1971888,
1980406,
1990579, Process Scheduler and
1993929, Distribution Server dumping
2000638, when job notifications are Modified notification routine to
2002400, added to the job definition. correct the command to write
Process 2021164, PSDSTSRV hangs on out the content of the email to a
Scheduler 2025913 130897000 PostReport. file.
1947905,
1949215, 8.40.09 nVision: Distributing
1949571, to multiple users doesn't work
Process 1964590, from the Report Request
Scheduler 2016668 134756000 page. Fixed logic in code.
149
150 PeopleSoft Proprietary and Confidential
1761595,
1766979,
1787366,
1823957,
1850952,
1873589,
1873645,
1884213,
1888707, Web Query IN LIST lookup
1977550, does not respond if Lookup
2013865, table contains huge amount
Query 2014263 143815000 of data. Fixed logic in code.
2001496,
2016369, Unable to do nVision
2017153, drilldown in more than one
Report 2028537, site, when using one web
Distribution 3020081 576950000 server. Fixed logic in code.
151
152 PeopleSoft Proprietary and Confidential
1759646,
1782168,
1795850,
1801084,
1802038,
1817792,
1862017,
1872553, Error when changing the edit
1880238, components settings, then
1889210, saving a permission list. field
1909127, is required;
1913216, ACL_PAGES_VW2.-
Security 3001735 127407000 BARNAME (124,64). Fixed logic in code.
Application messaging:
1761663, USER_PROFILE not
1948609, updating target database
Security 2020487 136152000 when unlocking an account. Fixed logic in code.
153
154 PeopleSoft Proprietary and Confidential
The PS_MAINTENANCE_LOG
Application Bundles: can't table is now updated correctly
track incident ID when copy during a database to database
Upgrade 1905445 102414000 database to database. project copy.
155
156 PeopleSoft Proprietary and Confidential
1983259,
2005395, Data missing in
2017588, PS_XMLSERVICEINFO Added PS_XMLSERVICEINFO
Upgrade 3027763 569507000 tables. to the script.
Upgrade
Process- Going through the PT 8.42
Customer upgrade manual, one of the
Upg 2055475 587246000 steps is install 8.42 . . . Added manual step to process.
Upgrade-
Data
Administrator 3034801 562318000 Index Build Error in DB2/Unix Fixed logic in code.
1940390,
1953435,
1982420,
2019771, PeopleBooks Tools 8.42 Made changes to 3 WebLogic
2044836, Search result's "NEXT" button scripts so that the
Web Server 3042501 117850000 broken again. SCRIPT_NAME var is unset.
="PeopleCode "SendMail"
needs to return error status Software change to return error
Workflow 1898674 111108000 code when failing." status when send mail failed.
1950056,
1964840, Worklist: Link does not work Software change to make
1988595, when InstanceID of Worklist worklist link work when worklist
Workflow 2018066 114420000 has reached 100000. are over 100000.
157
158 PeopleSoft Proprietary and Confidential
1956062,
1960526, Workflow - Unable to delete
1970232, or modify a Route Control
Workflow 1991977 125201000 from Approval Rule Set in 8.4. Fixed logic in code.
1923372,
2017268,
2052675, ExecuteRoleWorkflowQuery
2056005, and TriggerBusinessEvent Code change for
3003408, have significant performance ExecuteRoleWorkflowQuery
Workflow 3014488 141025000 issues. function.
1233537,
1828924, Workflow: WL_VOL_MON
1988479, Application Engine Not
Workflow 2016966 574550000 Sending notifications. Fixed logic in code.
WL_REPICATE Not
transferring Priority when
changed or Worked By
Workflow 2053596 578922000 Activity. Fixed logic in code.
159
160 PeopleSoft Proprietary and Confidential
Edit History
1. 6/13/03 PeopleTools 8.43 Release Notes posted at general availability.
2. 7/10/03 Added updates for Integration Broker, PSADMIN, Integration Tools and Utilities,
and Server Tools Administration.
3. 7/14/03 Added update to the PeopleTools Global Technology section describing an error
in the current PeopleBooks.