Peopletools 8.43 Release Notes: June 13, 2003

PeopleTools 8.
43 Release Notes
June 13, 2003

PeopleBooks Contributors: PeopleTools Product Documentation and Development.
Copyright © 2003 PeopleSoft, Inc. All Rights Reserved.
All material contained in this documentation is proprietary and confidential to PeopleSoft, Inc.
("PeopleSoft") and is protected by copyright laws. No part of this documentation may be reproduced,
stored in a retrieval system or transmitted in any form or by any means, including, but not limited to,
electronic, graphic, mechanical, photocopying, recording, or otherwise without the prior written permission
of PeopleSoft, Inc.
This documentation is subject to change without notice, and PeopleSoft does not warrant that the material
contained in this documentation is free of errors. Any errors found in this documentation should be
reported to PeopleSoft in writing.
This documentation that accompanies the software is licensed for use only in strict accordance with the
applicable license agreement, which should be read carefully, as it governs the terms of use of this
documentation and the related software, including the disclosure thereof.
PeopleSoft, PeopleTools, PS/nVision, PeopleCode, PeopleBooks, PeopleTalk, and Vantive are registered
trademarks, and Pure Internet Architecture, Intelligent Context Manager, and The Real-Time Enterprise
are trademarks of PeopleSoft, Inc. All other company and product names may be trademarks of their
respective owners. The information contained herein is subject to change without notice. Copyright ©
2003 PeopleSoft, Inc. All rights reserved.
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
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
June 13, 2003 PeopleTools 8.43 Release Notes

Updates to Mobile Classes................................................................................................................................81
Changes to SwitchUser ....................................................................................................................................82
Changes to ViewAttachment............................................................................................................................82
PeopleTools Global Technology..........................................................................................................................82
PeopleTools Global Technology PeopleBook Update.....................................................................................82
Enable Searching of Hebrew in Verity.............................................................................................................83
Adding Hebrew Locale and Verity Locale Mapping....................................................................................83
Verity Considerations for Non-English Environments.....................................................................................84
Object Naming Conventions.............................................................................................................................84
Adding Translations to an Existing PeopleSoft 8.4x English-Only Database..................................................84
Changes to Display of Fields and Labels in Translation Designer...................................................................85
Printing for Legal and A4 Paper.......................................................................................................................86
PeopleTools Internet Technology........................................................................................................................86
Using the New Window Link on the Personalize Pages...................................................................................86
Use Authentication Token Domain Name In URLs.........................................................................................87
HTML Forms in Tables....................................................................................................................................87
Inserting HTML Using document.write...........................................................................................................88
Specifying a Portal Browser Window Title......................................................................................................88
Caching and Manual Refresh for Pagelets........................................................................................................89
Context Sensitive Pagelet Help.........................................................................................................................90
Signout From a New Page................................................................................................................................92
Improved Session Timeout Behavior................................................................................................................92
Detailed Error Messages in the Network Log...................................................................................................93
PeopleBook Corrections and Additions............................................................................................................93
Reporting Tools...................................................................................................................................................94
Crystal Reports..................................................................................................................................................94
PeopleSoft Cube Manager................................................................................................................................96
PS/nVision........................................................................................................................................................96
PeopleSoft Process Scheduler...........................................................................................................................99
PeopleSoft Query............................................................................................................................................103
PeopleSoft Tree Manager...............................................................................................................................104
PeopleSoft Server Tools Administration............................................................................................................106
Miscellaneous Notes.......................................................................................................................................106
Application Server .........................................................................................................................................106
Configuration Properties File Options............................................................................................................107
Web Server......................................................................................................................................................109
IBM WebSphere.............................................................................................................................................110
PeopleSoft Internet Architecture Installation..................................................................................................114
BEA WebLogic 6.1.........................................................................................................................................114
Setting Up Additional Web Applications in a Single PIA Domain................................................................115
Building HTTP Spider Indexes.......................................................................................................................115
Timeout Settings.............................................................................................................................................115
PeopleTools Security.........................................................................................................................................121
Increasing the METAXP Default Value.........................................................................................................121
Tracking Recently Used Passwords................................................................................................................121
Defining the Role Membership Rules.............................................................................................................122
Query Trees Sorting Order..............................................................................................................................122
Script to Grant Permission to All Pages and Menus.......................................................................................122
Reboot the Server to Save the Password Settings...........................................................................................123
Improved Session Timeout Behavior..............................................................................................................123
SwitchUser Function Support.........................................................................................................................123
PeopleSoft Application Engine..........................................................................................................................123
Rolling Back on Component Interface Error..................................................................................................123
5
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
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.

New and Changed Features
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.
Microsoft SQL Server 2000

PeopleSoft strongly recommends applying service pack SP3 to avoid applying all the necessary hotfixes
and bundled fixes currently required for service pack SP2. However, note that service pack SP2 is still
the minimum supported service pack.
New Service Pack for BEA WebLogic 6.1

BEA WebLogic Server 6.1 SP4 is embedded into PeopleTools 8.43. You are required to upgrade to this
new Service Pack if you use BEA WebLogic. SP4 includes several bug fixes and JRE 1.3.1, and it
provides improved security and performance. You can apply SP4 over WebLogic 6.1 SP2 that was
installed with previous versions of PeopleTools.
New Version of Micro Focus Server Express

In PeopleTools 8.43, Server Express 2.2 is certified on the following operating systems:
• AIX 4.3, 5.1, and 5.2
• HP UX 11.0 and 11.11
• Solaris 8 and 9
• Compaq Tru64 5.1
Server Express 2.2 provides bug fixes and increased performance. Server Express 2.0.11 is still
supported.
9
PeopleSoft recommends that users of MicroFocus NetExpress upgrade to MicroFocus NetExpress 3.1
SP1.
JDBC Database Drivers

PeopleSoft no longer includes any JDBC drivers with the PeopleTools shipment. These drivers are
supplied either by the database product you use, or they may be obtained from your database vendor
respective database vendor.
Using the JDBC driver supplied by the database vendor ensures a predictable and well-supported
environment, with less potential for interoperability issues.
IBM AIX 5.2

With PeopleTools 8.43, PeopleSoft announces support for IBM AIX 5.2.
Solaris 9
With PeopleTools 8.43, PeopleSoft announces support for Solaris 9.0.
Web Browser Support: Netscape 7

With PeopleTools 8.43, PeopleSoft announces support for Netscape 7 on the following operating
systems:
• Windows NT
• Windows XP
• Windows 2000
• Mac OS 9
• Mac OS X
• Linux
Future Support Plans

In PeopleTools 8.44, PeopleSoft intends to change support for the following third party products.
However, keep in mind that the PeopleSoft support policy is subject to change. PeopleSoft is publishing
the following lists so that you can make the appropriate arrangements to prepare for any support changes
that will affect your site.
Operating Systems
PeopleSoft plans to discontinue support for the following operating systems:

• Windows NT 4

• Solaris 7
• AIX 4.3
• HP UX 11.0
• Tru64 Unix 5.0A
• OS390 v2r8 and v2r10
• Red Hat Linux 7.x (web server)
The minimum operating system requirements for PeopleTools 8.44 will be:
• HP UX 11.11
• Tru64 Unix 5.1
• Solaris 8
• AIX 5.1
• z/OS 1.2
• Windows 2000
• Red Hat Advanced Server 2.1 32-bit
PeopleSoft plans to add support for the following operating systems:

• Red Hat Linux AS 2.1 32-bit
• Red Hat Linux AS 2.1 64-bit (database server only)
• HP UX 11.23 for Itanium 2 processor family (IPF2)
• Windows 2003 Server 32-bit
• Windows 2003 Server 64-bit (database server only, with Microsoft SQL Server 2000 SP3 64-bit)
Database Versions
PeopleSoft plans to discontinue support for the following database versions:

• Sybase 12.0 and the 2K page size; a 4K page size will be required.
• Informix 9.21
• Oracle 9.0.1.x.x
Minimum database requirements will be:

• Oracle 8.1.7.4 and 9.2.0.2 for Unix and Windows 2000
• Oracle 9.2.0.2 for Real Application Cluster on Unix and Windows 2000
• Microsoft SQL Server 2000 SP3 (32-bit) for Windows 2000
11
• 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.
PeopleSoft plans to add support for the following databases:

• 32-bit database servers on Red Hat Linux Advanced Server 2.1 32-bit running all PeopleSoft Internet
Architecture tiers. Supported database are:
 Oracle 9.2.0.2 (32-bit).
 DB2 UDB 8.1 (32-bit).
• 64-bit database server only certification on Windows 2003 Server 64-bit:
 Microsoft SQL Server 2000 SP3 (64-bit) (SP3 is the minimum service pack for 64-bit SQL Server
2000)
 Oracle 9.2.0.2 (64-bit).
 DB2 UDB 8.1 FixPak 2 (64-bit).
• 64-bit database server only certification on Red Hat Linux AS 2.1 64-bit:
 Oracle 9.2.0.2 (64-bit)
 DB2 UDB 8.1 FixPak 2 (64-bit)
• Sybase 12.5 Unicode support
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.

Application Servers
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.
• The BEA Tuxedo 8.1 upgrade will be required.
Web Servers
For PeopleTools 8.44, the following web server upgrades will be required:
• BEA WebLogic Server 8.1 SP1
• IBM WebSphere Server 5.1 Network Deployment
PeopleSoft Internet Architecture (PIA)

For the 8.43 PeopleTools release, we’ve made small changes that are specific to the display of certain
browser elements. These settings are in the form of new personalizations. We also recommend that end
users clear their browser cache if image or font problems occur.
A PeopleBook Enhancement, "Browser Limitations," is available on Customer Connection. This
document is a trouble shooting guide for known issues relating to PeopleSoft supported web browsers.
New Personalization Settings

System administrators can now control the display of certain browser elements to their users while using
PeopleSoft applications. On the Define Personalizations page there are three new browser-related
settings. These settings function on all supported browsers.
BADDRESSBAR Controls the display of the browser’s address bar.
BBUTTONS Controls the display of the browser’s navigation bar, which
usually contains the Back, Forward, Home, and Refresh
buttons among others depending on the browser in use.
BMENU Controls the display of the browser’s menu bar.
Note that keyboard commands still activate menu options and other functions.
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.
To clear browser cache when using Microsoft Internet Explorer:
.1 Select Internet Options from the Tools menu.
13
.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.
Adding Pages to My Favorites

In the 8.4x PeopleTools releases, the system only allows users to add pages that are already registered
in the portal registry to the My Favorites folder. Since external web pages are not PeopleSoft managed
objects, they cannot be added to the My Favorites folder. An error message displays and directs users to
contact their portal administrator for assistance.
See also
PeopleTools 8.42 PeopleBooks: PeopleSoft Application Designer, “Using Registration Wizard”
SQR for PeopleSoft Language Reference

Add to the SQR for PeopleSoft Language Reference Guide chapter "Using the PSSQR.INI File and the
PSSQR Command Line," section "Using PSSQR.EXE Command Line Options," after the first paragraph:
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
PeopleSoft Component Interfaces

The following updates were made to PeopleSoft Component Interfaces in PeopleTools 8.43.

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,
public static void printPropertyType(String propName,

ICompIntfcPropertyInfo iPropertyInfo) {
String strOAType = null;

String strDBType = null;
try {
switch ((int)iPropertyInfo.getOAType()) {
/* Object Adapter Type == 0 */
case CIPropertyTypes.PSPROPERTY_OA_TYPE_BOOL:
strOAType = "BOOL";
break;
case CIPropertyTypes.PSPROPERTY_OA_TYPE_NUMBER:
strOAType = "INTEGER";
break;
case CIPropertyTypes.PSPROPERTY_OA_TYPE_FLOAT:
strOAType = "FLOAT";
break;
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;
case CIPropertyTypes.PSPROPERTY_DB_TYPE_LONG_CHARACTER:
strDBType = "LONG_CHARACTER";
break;
15
case CIPropertyTypes.PSPROPERTY_DB_TYPE_NUMBER:
strDBType = "NUMBER";
break;
case CIPropertyTypes.PSPROPERTY_DB_TYPE_SIGNED_NUMBER:
strDBType = "SIGNED NUMBER";
break;
case CIPropertyTypes.PSPROPERTY_DB_TYPE_DATE:
strDBType = "DATE";
break;
case CIPropertyTypes.PSPROPERTY_DB_TYPE_TIME:
strDBType = "TIME";
break;
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);
}
CopyRowset Language Considerations

In previous PeopleSoft releases, CopyRowset* functions for component interfaces were not sensitive to
the language code on PSCAMA. Because of this, related language processing did not take place when
language code on PSCAMA was different than the base language code. This has been modified in
PeopleTools 8.43. PeopleSoft is now detects the language code in PSCAMA.
WSDL Binding for Component Interfaces

A PeopleBook Enhancement, “PeopleSoft Component Interfaces, WSDL Binding for Component
Interfaces,” is available on Customer Connection. This document describes the PeopleSoft
implementation of the WSDL specification for the set of SOAP transactions exposed for Component
Interfaces.
Microsoft Excel to Component Interfaces Utility

A PeopleBook Enhancement, “PeopleSoft Component Interfaces PeopleTools 8.42 Excel to Component
Interface Utility,” is available on Customer Connection. This document is an update to the PeopleTools
8.41 Excel to Component Interface Utility.

PeopleSoft Business Interlinks

Note the following updates to PeopleSoft Business Interlinks for PeopleTools 8.43.
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.
Writing an XML Design-Time Plug-In
Setting Up a Business Interlink Runtime Plug-In
To write a Business Interlink runtime plug-in using C++, you need to set up the development environment
on the UNIX system.
To set up for your Business Interlink Plug-in in UNIX:
.1 Navigate to the <PS_HOME> directory and run the following command:

. ./psconfig.sh
.2 Test the setup by running the Business Interlink tester on the executable files in
the simple directory.
.3 Create the directory for your plug-in.
You can copy files from the sample directory to your plug-in directory.
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”.
 For HP, replace “libext=so” with “libext=sl”.
.5 Create your Business Interlink Runtime plug-in.
17
.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
PeopleSoft Optimization Framework

This section discusses the changes in PeopleTools 8.43 for PeopleSoft Optimization Framework.
PeopleSoft Optimization Framework provides an optimization engine that is integrated into the PeopleSoft
Pure Internet Architecture. This enables PeopleSoft applications that may need optimal decision making
to readily access optimization functionality without leaving the PeopleSoft application environment.
PeopleSoft Optimization Framework is currently used by PeopleSoft Supply Planning applications
(previously known as Enterprise Planning and Production Planning applications). This supersedes the
Red Pepper products and enables optimization functionality to be used without the need for any code to
be deployed on client machines, delivering benefits for both users and administrators.
Designing a Problem Type Definition
Integer Array Not Allowed
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.
Creating Optimization PeopleCode
Programming for Database Updates
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.

Note. The pending database update may have happened considerably earlier in the code. Forcing a
commit within your PeopleCode to avoid this problem prevents roll-back on database error. Forcing a
commit should be used with care.
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.
Loading the Same Problem Instance
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.
Optimization Delete Records
When a record is deleted from a problem type, the associated delete record is not needed if this record is
not used elsewhere.
Updating Solver Licenses
Currently, no optimization application requires updating the solver license. You should update solver
licenses only when instructed to by PeopleSoft.
Changes to Commit Statuses in Application Engine Programs
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
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.
Deleting an Existing Problem Instance
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.
Checking Asynchronous Transactions
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.

Change to CheckOptEngineStatus
PeopleCode CheckOptEngineStatus generates PeopleCode constants for the CheckOptEngineStatus

return status.
For example, CheckOptEngineStatus can return %OptEng_Idle and DetailedStatus is
%OptEng_Success.
For CheckOptEngineStatus, DetailedStatus can have the value, %OptEng_Success or %OptEng_Fail.
Remove the 0 Message ID from return status.
Changed Return Values for FillRowSet
FillRowSet has changed return values:

Returns an integer value: %OptEng_Success if the rowset was successfully retrieved; %OptEng_Fail
otherwise.
Optimization Shutdown Method
Add the following note.
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.
RunSynch, RunAsynch, Shutdown, SetTraceLevel Methods
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
Added a Returns section:

Returns one of the following.
• %Severity_Fatal
• %Severity_Status
• %Severity_Error
• %Severity_Warn
• %Severity_Info
• %Severity_Trace1
• %Severity_Trace2
Added an Example section.
21
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
Clarified the explanation for the severity parameter:

Set to one of the following PeopleCode constants. This sets the degree to which errors are logged. You
can set the tracing levels differently for various parts of the optimization engine, as needed. This enables
you to control the amount of trace information generated by the optimization engine. The following list
shows the order of the severity, listed from lower to higher. For example, in the example of
Severity_Error, it logs Severity_Fatal, Severity_Status and Severity_Error messages and filters out the
others. Keep in mind that the higher the severity, the greater the performance overhead.
%Severity_Fatal
%Severity_Status
%Severity_Error
%Severity_Warn
%Severity_Info
%Severity_Trace1
%Severity_Trace2
CreateOptEngine Function
Replaced the machine_name parameter with processinstance:

Enter the process instance id. You use this parameter only with Lights Out processing, most likely with
the subscription PeopleCode for application message.
The state record that you use with Application Engine contains the process instance id.
This optional parameter is positional. If you use it, you must also use the &detailedstatus parameter.
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();

if &status=%OptEng_Fail and &myopt.DetailedStatus=%OptEng_Method_Disabled
then
<perform some action>
End-if;
New Process Instance Property
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 */
PeopleSoft Application Designer

The following updates have been made to PeopleSoft Application Designer in PeopleTools 8.43.
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.
Page Field Labels
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
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.
Disabling Toolbar Hot Keys in PeopleSoft Internet Architecture
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.
Fixing Audit Errors

In the 8.42 release we suggested a workaround to solve the issue of non-standard SQL table names
associated with temporary tables showing up in the DDDAUDIT as Table-1 errors. This issue has been
resolved in the 8.43 release of PeopleTools. However, non-standard SQL table names may still be an
issue if Datamover is run manually to import external tables into the database. In this release we added
the new audit RECORD-13 to Sysrecrd.sqc to report non-standard SQL table names during the audit.
Run the following SQL to fix any instances reported by the audit:
UPDATE PSRECDEFN SET SQLTABLENAME=''WHERE RECTYPE=7;

Alter Table Changes
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.
PeopleSoft Administration Tools (Formerly Data

Management)
The following updates to PeopleSoft Administration Tools apply in PeopleTools 8.43.
Data Mover
The following changes apply to Data Mover for PeopleTools 8.43.
New Ability to Create Trace Files on UNIX
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.
To set a Data Mover trace:
.1 Start a new telnet session.

.2 cd $PS_HOME
.3 . ./psconfig.sh
.4 vi $PS_HOME/setup/psdmtx.cfg
Specify the trace flag.
.5 EXPORT PS_SERVER_CFG=$PS_HOME/setup/psdmtx.cfg
.6 EXPORT PS_SERVDIR=$PS_HOME/log
25
Trace file is located in $PS_HOME/log/LOGS/ AE__0/AE__0.trc
TLSCOPY.SQR No Longer Used in Renames
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.
PeopleSoft Upgrade Assistant

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, and then
choose the PeopleSoft release you are upgrading to.
PeopleSoft Upgrade Assistant can now be used on Microsoft Windows XP.
Setting System Variables for Upgrade Assistant

The workstation running Upgrade Assistant must also be setup to access the component interface API
using COM.
To set system variables for Windows 2000 workstations:
1. Click Start, Settings, Control Panel, System, Advanced, Environment Variables.
2. Append the <PS_HOME>\jre\bin\hotspot directory to your system variable Path.
3. Add the directory that contains the jvm.dll file in the Path variable.
4. In addition, append the <PS_HOME>\class\psjoa\psjoa.jar directory to the system variable
CLASSPATH to include the psjoa.jar file.
To set system variables for Windows NT workstations:
1. Start, Settings, Control Panel, System, Environment, System Variables.
2. Set the system variable Path to include the directory containing the jvm.dll file.
3. Include a path to the bin directory.
For example: c:\pt842rc7\bin\client\winx86.
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.
Running Data Conversion Concurrently on the client via the Upgrade

Assistant
Upgrade Assistant cannot run data conversion processes (Application Engine programs) concurrently on
the client. If you must run data conversion processes concurrently, run them concurrently on the server.
This limitation does not effect running data conversion processes or other Application Engine programs in
serial mode.

PeopleSoft Integration Broker

This section discusses new and changed features for Integration Broker in PeopleTools 8.43.
Understanding Changes to the Message Channel Properties Dialog

Box
The Quality of Service options, Best Effort and Guaranteed, have been removed from the Use tab of the
Message Channels Properties dialog box.
The Best Effort option is not implemented, so quality of service is always Guaranteed. If PeopleSoft
Integration Broker fails to deliver a message, it retries until the time-out period expires. Then it marks the
message as Timeout in Integration Broker Monitor. Once the target system is ready to receive the
message, the system administrator can resubmit any message that timed out.
Viewing Messaging System Performance Statistics
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.”
Increasing Asynchronous Message Processing Performance

The psappsrv.cfg file features a new External Configuration option to increase asynchronous message
processing performance.
When you set External Configuration equal to Y the Message Dispatcher processes the next message(s)
in the queue and does not wait on the dispatcher scan interval to send another message.
This option is useful if the active pub/sub servers are on a different domain from where the application
server processes are performing a publish (through PeopleCode) or accepting the IBRequest via a Jolt
request from the integration gateway.
Throttling Dispatched Messages Through the Pub/Sub System

A new throttling enhancement:
• Provides mechanisms to throttle the number of dispatched messages from a given dispatcher to its
associated handler(s).
27
• 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:
Section in psappsrv.cfg Parameter Description

Settings for PSAPPSRV Tuxedo Queue The value of your Tuxedo queue
Size size. This is a kernel parameter in
UNIX. For Window, look in BEA
Tuxedo, IPC Resources.
This parameter is used for Tuxedo
queue threshold determination
and is used for Pub/Sub
processing only. Integration
Broker sends messages to the
queue until the queue size
reaches the value specified. When
messages sent exceed the queue
size, Tuxedo writes the message
to the Tuxedo log.
A value of 0 (zero) disables
Tuxedo queue threshold
determination and usage.
A value of -1 uses the following
defaults:
• Windows: 65535
• AIX: 4000000
• Solaris: 65535
• HP: 65535
All dispatcher sections. Tuxedo Queue Indicates the frequency that
(PSBRKDSP_dflt, Status Check Integration Broker reads the
PSSUBDSP_dflt and Count Tuxedo queue for every cycle of
PSPUBDSP_dflt.) the dispatcher.
The higher the number, the less
frequently the queue is checked.
PeopleSoft recommends that you
keep the default setting of 1. A
value of 0 (zero) means the queue
is never checked.
All dispatcher sections. Dispatcher List Limits the number of dispatches
(PSBRKDSP_dflt, Multiplier by the number you specify,
PSSUBDSP_dflt and multiplied by the number of

PSPUBDSP_dflt.) associated handler(s). This

parameter is useful for unordered
channels when all messages could
go out at once.
The default value is 5.
All dispatcher sections. Dispatcher Determines the maximum number
(PSBRKDSP_dflt, Channel Max of items per channel that the
PSSUBDSP_dflt and Queue Size dispatcher keeps in memory.
PSPUBDSP_dflt.)
The default value is 1000.
Understanding Synchronous Message Logging Enhancements

A logging option has been added to the Messages page for a transaction that enables you to
select the level of information logging for synchronous messages.
To access the Messages page, select PeopleTools, Integration Broker, Node Definitions. The
Node Definitions page displays. Click the Transactions tab, and click the Edit link for a
transaction. Select the Messages tab.
Messages page
Use the following field to select the level of synchronous logging:
Field Description
Synchronous Logging The valid options are:
29
• Header Only. Log header information only.
With this option, you can view synchronous
message header information on the
Integration Broker Monitor Synchronous
Details page.
• Header and Detail. Log header and

message detail information. With this
option, you can view synchronous
message header information and XML
message content on the Integration Broker
Monitor Synchronous Details page.
• No Logging (Default). Turn off all logging.
Applying Transformations on the Integration Gateway
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.
Understanding Routing Information in Messages Published to Non-

PeopleSoft Systems
A message has two parts—the transaction data and the IBInfo header that is the routing envelope used
by PeopleSoft Integration Broker.
Before PeopleTools 8.43, the IBInfo header was stripped off when a message was published to a non-
PeopleSoft system. In the event that the receiving system wants to make use of the IBInfo data, IBInfo
header information is now included when publishing messages to non-PeopleSoft systems when using
the HTTP target connector or the JMS target connector.
The IBInfo header information is contained in the HTTP header or the JMS header. The content of the
message (message body) is not impacted.

When using the HTTP target connector to send messages to non-PeopleSoft systems, the following
IBInfo data is contained in the HTTP headers:
• MessageName
• 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
Understanding Routing Types for Nodes and Outbound Transactions

After you create a node, the routing type for the node and the routing type for outbound transactions
function independently.
For example, if you create a node and choose a routing type of Explicit, and then create several outbound
synchronous and outbound asynchronous transactions and save your work, the routing type for the
transactions you created default to Explicit. However, if you later change the node routing type, the
routing type does not automatically get changed for any of the existing outbound transactions. You must
manually change the transaction routing type, if desired, on the Transactions Detail tab for the
transaction.
Understanding Simple Post Utility Enhancements

This section discusses enhancements to the Simple Post utility and discusses:
• Accessing the Simple Post utility via a Java API.
• UTF-8 compliancy.
• Support for compression and base64 encoding.
31
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.
• Compile the Java file.
• Run the test program.
In addition, this section also features a sample of the XML file that is sent to the utility.
The following example shows a submission via a Java API.

// Import the SimplePost API
import com.peoplesoft.pt.simplepost.SimplePost;
/** Test class to use SimplePost functionality */

public class TestSimplePost {
/** Constructor */
public TestSimplePost() {}
public static void main (String argv []) {
// Create the SimplePost object

SimplePost mainSPObj = new SimplePost();
// Turn on printouts
mainSPObj.setVerbose(true);
// Use this function to see the output stream,

// defaulted to System.out
// mainSPObj.setOutputPrintStream(<PrintStream>);
// Turn on Encoding for 8.4.3

mainSPObj.setEncoding(true);
// SET THE REQUIRED DATA
// Requesting Node
mainSPObj.setRequestingNode("QE_UNDERDOG");
// Message Name
mainSPObj.setMessageName("QE_SYNC_MSG");
// Server URL, must be the HttpListeningConnector or a

//connector that can accept an IBRequest XML message
mainSPObj.setServerURL("http://localhost/PSIGW/HttpListeningCo
nnector");
// Input file name, root node name must be the name of the
message

mainSPObj.setInputFileName("c:\\temp\\QE_SYNC_MSG.xml");
/* // 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("");
*/
// Post the data

boolean returnValue = mainSPObj.post();
// Check the return value

if (!returnValue) {
// False, printout the error message

System.out.println(mainSPObj.getMessage());
} else {
// Success!
// Printout the return code and server message

System.out.println("\n" + mainSPObj.getResponseCode() + " - "
+ mainSPObj.getResponseMessage());
// Printout the headers

System.out.print("\n" + mainSPObj.getResponseHeaders() + "\n");
// Printout the data

System.out.print("\n" + mainSPObj.getResponseData());
}
}
}
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
To following example shows how to invoke the test program.

java -classpath
"C:\beawls61sp4\wlserver6.1\config\peoplesoft\applications\PSIGW\WEB-
INF\classes;." TestSimplePost
33
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.
Support for Compression and Base64 Encoding
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>

<Transaction>
<QE_SALES_ORDER class="R">
<QE_ACCT_ID/>
<QE_ACCOUNT_NAME>
NationalAccount
</QE_ACCOUNT_NAME>
. . .
</QE_SALES_ORDER>
<PSCAMA class="R">
<LANGUAGE_CD>ENG</LANGUAGE_CD>
<AUDIT_ACTN>A</AUDIT_ACTN>
. . .
</PSCAMA>
</Transaction>
</MsgData>
</QE_SYNC_MSG>
]]>
</Data>
</ContentSection>
</ContentSections>
</IBRequest>
The following example shows the same file when encoding is used.
<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
hjmlNAMJGbAwveiSCFIjCcLe2+LdoFR1PKmoQ7rltwrI33
QY3wfs703dIe1tuGM8YYPXNGGxioASW+M9oy6vyz/AP6S+
]]>
</Data>
</ContentSection>
</ContentSections>
</IBRequest>
Understanding Send Master Enhancements

This section describes:
• Creating Send Master projects and selecting project types.
• Posting messages to MQSeries queues to test the JMS listening connector.
Creating Send Master Projects and Selecting Project Types
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.
To create a Send Master project and select the project type:
.1 Launch StartSendMaster.bat (Windows) or StartSendMaster.sh (UNIX). The

location of the files depends on the Web server you are using.
 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.

 MQSeries. Use to add a message to a JMS queue.
.5 Click OK.
See Also
PeopleTools 8.42 PeopleBook: PeopleSoft Integration Broker, “Using the Integration Broker SDK,”
Testing Message Processing Using Send Master.
Posting Messages to MQSeries Queues
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.
The Send Master workspace for an MQSeries project type
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
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.
To create the MQSeries project:
.1 Launch StartSendMaster.bat (Windows) or StartSendMaster.sh (UNIX).

.2 Create a new project and choose MQSeries as the project type.
See “Working with Send Master Project Types” in these release notes.
To enter message header-specific information:
.1 In the Input Information section, click the Header tab if not already selected.

.2 From the JMS Provider dropdown list, select a provider. The valid options are:
 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:
 Async. Asynchronous message.
 Sync. Synchronous message.
.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.
To enter input file information and post the message:
.1 In the Input Information section, click the Input File tab.

.2 Enter information for the input file (message).
.3 Click the Post button to post the input file to the MQSeries queue.
39
To view output information:

If you are working with a synchronous message, the Output Information area displays response
information from the target system.
If you are working with an asynchronous message, no response information is received. However, the
term <Raw Message> displays in the View field when the Post is successful.
Viewing Non-English Characters in Integration Gateway Log Files

To view non-English characters in the integration gateway log files you must enable UTF-8 encoding in
your Web browser.
For example, if you are using Microsoft Internet Explorer 5.5, you can enable UTF-8 encoding by
selecting View, Encoding, Unicode (UTF-8). If you are using Netscape Navigator 6.0, you can enable
UTF-8 encoding by selecting View, Character Encoding, Unicode (UTF-8).
Understanding HTTP Listening Connector Enhancements

The HTTP Listening Connector now accepts compressed and based64-encoded data.
Using the HTTP Target Connector

This section provides information about using the HTTP target connector and discusses:
• Using the Content-Type property.
• Encoding strings.
• HTTP status codes for non-Simple Object Access Protocol (SOAP) messages.
• HTTP status code for SOAP messages.
Using the Content-Type Property
When the HTTP target connector property Content-Type is application/x-www-form-urlencoded, the

connector converts the content string to MIME format.
Encoding Strings
When encoding a String, the following rules apply:

• The alphanumeric characters "a" through "z", "A" through "Z" and "0" through "9" remain the same.
• 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

representation of the byte.
Understanding HTTP Status Codes for Non-SOAP Messages
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.
Understanding HTTP Status Codes for SOAP Messages
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:
 HTTP status code 400 can mean any of the following:
o InvalidMessageException
o MessageMarshallingException
o MessageUnmarshallingException
 HTTP status code 500 can mean any of the following:
o ExternalSystemContactException
o ExternalApplicationException
o GeneralFrameworkException
Specifying the Message Destination in HTTP Headers
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
entry from the headers. If no default application server entry is specified in the
integrationGateway.properties file, the follow error is generated:
<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.
Pinging the SimpleFile Target Connector

You can use the Integration Broker Monitor to ping the Simple File Target Connector.
Testing JMS Listening Connectors

See Understanding Send Master Enhancements.
Encrypting the JMS Target Connector Password

With this release you can use the integrationGateway.properties file to store an encrypted
JMS target connector password.
You can continue to specify the JMS target connector password in the connector properties
section in the Gateways component, however a password set in this location is not
encrypted.
Note. A password set in the Gateways component takes precedence over one set in the
integrationGateway.properties file.
To generate and store an encrypted JMS target connector password:
.1 Open the integrationGateway.properties file.

.2 Locate the following section in the file and uncomment the line in bold.
#JMS Providers Password for JMSTargetconnector
#Password is Ciphered using PSCipher command.
#ig.jms.JMSTargetConnector.JMSProvider.Password=
.3 Use the PSCipher.bat file delivered with Integration Broker and located in your
web server directory to encrypt the JMS target connector password.

.4 Cut and paste the encrypted value after the equal sign in the line you
uncommented in Step 2.
.5 Save your changes.
For information about using PSCipher to encrypt passwords, see the PeopleTools 8.42 PeopleBook:
PeopleSoft Integration Broker, “Managing the Integration Gateway,” The integrationGateway.properties
File.
Partitioning Unstructured or Inbound Messages

To partition unstructured messages, all XML tags must be uppercase.
XMLDoc partitioning uses XPath, which is case sensitive. The fields that you select for partitioning an
unstructured message on the message channel or fields that are added to the message channel are all
uppercase. Therefore any fields to be partitioned must also be uppercase. As a result, when you create
an XMLDoc, the field names used for partitiioning must be uppercase.
The same holds true for inbound messages.
Known Issues and Workarounds

This section discusses known issues and workarounds for PeopleSoft Integration Broker.
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.
Warning! Clearing name/value pairs may break existing transformations.
After you have removed any dependencies, you can return to the Codeset page and delete the codeset
match name/value row.
Deleting Relationships and Transaction Modifiers
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.
Web Server Reboot Required After Renaming the Local Node
After you rename a local node, you must reboot the web server.
43
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.
• Increase the JVM heap size.
Allocating Additional Memory in Send Master
To allocate additional memory in Send Master, open StartSendMaster.bat (Windows) or

StartSendMaster.sh (UNIX) and add the –XmxZZm parameter, where ZZ equals the amount of memory,
in megabytes, to allocate.
For example, the value – Xmx128m indicates to allocate 128 MB.
The following example shows how to add the parameter in the StartSendMaster.bat file:
"C:\Bea\jdk131\Bin\java.exe" -Xmx128m -classpath
"C:\Bea\wlserver6.1\config\peoplesoft\lib\xalan.jar;C:\Bea\wlserver6.1\con
fig\peoplesoft\lib\xerces.jar;C:\Bea\wlserver6.1\config\peoplesoft\lib\mai
l.jar;C:\Bea\wlserver6.1\config\peoplesoft\applications\PSIGW\WEB-
INF\classes;C:\Bea\wlserver6.1\config\peoplesoft\
lib\entappletbase.jar;C:\Bea\wlserver6.1\config\peoplesoft\lib\entappletss
l.jar;C:\Bea\wlserver6.1\config\peoplesoft\applications\PSIGW\WEB-
INF\lib\sfc.jar;C:\Bea\wlserver6.1\config\peoplesoft\
applications\PSIGW\WEB-INF\lib\symbeans.jar;C:\Bea\wlserver6.1\
config\peoplesoft\applications\PSIGW\WEB-INF\lib\activation.jar"
com.peoplesoft.pt.sendmaster.SendMaster
Increasing the JVM Heap Size
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.

If your web server is WebSphere, the JVM heap size is most likely set to a minimum heap
size of 64 MB and a maximum size of 256 MB. Setting the JVM heap size to a larger minimum
value (preferably one that equals the maximum value) avoids a compromise in performance
incurred by dynamically growing the JVM and improves predictability; it also lessens the
frequency for JVM garbage collection. With the improved, thread-based garbage collection
mechanism in JDK 1.3, the impact on workload capacity is greatly reduced when garbage
collection occurs. It also eliminates the inefficiencies of earlier JDKs when heap size
exceeded 512 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
.3 Save the changes.

When you invoke the Simple Post utility, you must specify the maximum Java heap size that you
specified. For example, if you set the JAVA_OPTIONS parameter in the setenv.cmd file to 128 MB, when
invoking the Simple Post utility you must add the following argument to the command line:
-Xmx128m
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
.2 Locate the initialHeapSize and maximumHeapSize parameters and increase the

values.
<jvmSettings xmi:id="JavaVirtualMachine_1" classpath="$
{WAS_ROOT}/lib/bootstrap.jar;${WAS_ROOT}/properties;${WAS_ROOT}/ins
talledApps/peoplesoft/PORTAL/WEB- INF
/lib/entappletbase.jar;${WAS_ROOT}/installedApps/peoplesoft/PORTAL/
WEB-INF/lib/entapplethttp.jar;${WAS_ROOT}/installedApps/peoplesoft/
PORTAL/WEB-INF/lib/entappletp10.jar;${WAS_ROOT}/installedApps/
peoplesoft/PORTAL/WEB-INF/lib/entappletp12.jar;${WAS_ROOT}/
45
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>
.3 Save the changes.

When you invoke the Simple Post utility, you must specify the maximum Java heap size that you
specified. For example, if you set the maximumHeapSize parameter to 256 MB, when invoking the Simple
Post utility you must add the following argument to the command line:
-Xmx256m
Archiving Messages in Integration Broker Monitor
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.
To inactive a pub/sub server on a 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.

For more information see the PeopleTools PeopleBook: PeopleSoft Integration Broker, "Using Integration
Broker Monitor," Working with the Monitor Messages Component.
Sequencing Transaction Modifiers
You cannot sequence transaction modifiers to handle multiple relationships to the same node.
PeopleSoft Integration Tools and Utilities

This section describes enhancements to PeopleSoft Integration Tools and Utilities for the PeopleTools
8.43 release.
Understanding Added Parsing Support for all Comma Separated

Value (CSV) Types
The following list summarizes the added parsing support in Preview and Runtime for all CSV types:
• All blank lines are ignored. (In the past, blank lines came in as empty records.)
• All empty fields are returned as empty strings or numbers equal to zero.
• Fields, including commas or new line, are surrounded in quotes.
• 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 Added Parsing Support for Excel CSV Specifications

This section discusses added parsing support for Excel CSV specifications.
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.
Item Excel CSV Parsing Non-Excel CSV Parsing

White space. Leading and trailing white Leading and trailing whites
space is significant for strings. paces are ignored, including
converted tabs.
Backslashes. Not interpreted as special Interpreted.
characters, except for new lines.
Quotes inside quoted Double-quoted. Escaped.
strings.
Tabs. Converted to a single space. Interpreted as tabs and ignored.
47
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.
File Layout Definition Properties dialog box

When you select CSV as the File Layout Format, parameters specific to the CSV format display. The new
fields to support Excel CSV are described in the following table.
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

delimiters, When a qualifier exists, the
field is parsed using a closing matched
qualifier. All characters are ignored
before and after the qualifier.
If you do not check the box, the field
must have qualifier pairs. All characters
are ignored before and after the qualifier.
Convert Tabs to Spaces Check the box to convert all tabs within
the field to spaces.
If you do not check the box, all tabs are
ignored.
Note. If the Strip White Space option is also

selected, the system also removes trailing and
leading tabs.
Interpret Backslashes Check the box to interpret backslashes

within field data as escape characters.
The following characters have special
meaning and are interpreted as follows:
• \t. Tab.
• \n. Newline.
If the check box is not selected, backslashes

are considered regular text data.
Strip White Space Check the box to remove all leading and
trailing white space within field data from
the output data.
Note. If this option is selected, trailing and

leading tabs will also be removed, regardless of
whether you have selected the Convert Tabs to
Spaces option.
Double Quote Check the box to interpret two double

quotes (" "), as one double quote (") in
output data.
For example, if you enable this option:
"abc""def"
is interpreted as:
abc"def
49
Backslash Quote Check the box to interpret backslash

quotes (\") as one double quote (") in
output data.
For example, if you enable this option:
"abc\"def"
is interpreted as:
abc"def
Understanding the Imply Decimal Place Option

An Imply Decimal Place option has been added to the Fixed File Layout properties page This option
displays only when the File Layout Format is Fixed.

File Layout Definition properties dialog

When importing a file into a PeopleSoft database and no decimal place is specified for
numeric values in the file, if the Imply Decimal Place box is checked, the system will add a
decimal place to numeric values based on the decimal value specified in the field definition.
Decimal Padding With File Layout Definitions

When creating a CSV or XML file using the File Layout definition in the PeopleTools 8.43 release, the
system automatically pads the decimal places with zeros when amounts do not have values beyond the
decimal point. For example, 100 will automatically be written as 100.00.
Using Dates With the ReadRowset Method
The PeopleBooks indicate the following rule for applying dates when using the ReadRowset method:
51
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
The following is not valid: 2/3/03.
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
The following is not valid: 2-Feb-03.
PeopleSoft MultiChannel Framework

The following sections describe new and updated features to PeopleSoft MultiChannel Framework for
PeopleTools 8.43
The PeopleSoft MultiChannel Framework (MCF) is an integral part of the PeopleSoft Pure Internet
Architecture, and provides support for real-time event notification, consolidated message channels, and
email response. It is used for report notification and PeopleSoft CRM, and first appeared in PeopleTools
8.42.
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.

Updates to REN Server

Updates to REN server configuration, administration, and security are included in a separate PeopleBook
Enhancement, “PeopleTools 8.43: Configuring REN Servers,” available on Customer Connection.
REN Servers and Upgrading from PeopleTools 8.42

The Application Engine program UPGMCF843 converts REN server configuration information in your
PeopleTools 8.42 database to the new PeopleTools 8.43 format.
REN servers run in the application server domain. They are used for the PeopleTools MultiChannel
Framework (MCF) and Reporting Window output option. PeopleTools 8.43 consolidates all REN server
configuration information into the database. Old REN server configurations must be upgraded before
attempting to boot under PeopleTools 8.43.
If you did not configure any REN servers in PeopleTools 8.42, then the UPGMCF843 program makes no
changes. The program converts standard REN server configurations to the PeopleTools 8.43 format,
including MCF cluster information. If it cannot convert one of your configurations, error messages are
written in the Application Engine message log.
After running UPGMCF843 check the psrenconfig.txt file located in each application server domain that
include a PeopleTools 8.42 REN server (the file does not exist in application server domains that did not
start a REN server). Each old file should have been replaced with the new PeopleTools 8.43 template file
located at PS_HOME\appserv\ren\psrenconfig.txt. Old template files cannot be used with the
PeopleTools 8.43 REN server. If you customized your old files by manual edits (compare them with the
PeopleTools 8.42 template to see; it is located in the same place as the new template), manually edit the
new files and update them.
Instant Messaging
The new instant messaging functionality is covered separately, in the “PeopleTools 8.43: Configuring
Instant Messaging” PeopleBook Enhancement, available on Customer Connection.
Configuring MCF Clusters

The UQ Cluster page has been updated to reflect naming changes consistent with configuration of REN
servers and REN server clusters. The UQ Cluster page is now the MCF Cluster page.
An MCF cluster exists only in relation to its associated REN server cluster. PeopleSoft MultiChannel
Framework automatically creates an MCF cluster for each REN server cluster for which MCF is identified
as an owner in the REN server configuration. REN server clusters not owned by MCF cannot be
associated with MCF clusters.
Use the following navigation path to access this page:
Page Name Navigation

MCF Cluster PeopleTools, MultiChannel Framework, Universal
Queue, Configuration, Cluster
53
MCF Cluster page

MCF Cluster ID The MCF cluster ID is created based on the associated
REN server cluster ID. The REN server cluster must be
owned by MCF or ALL. The cluster ID takes the name of
the associated REN server cluster with MCF appended
(for example, MCF-RENCLSTR_0001).
REN Server Cluster ID The ID of the REN server cluster associated with this MCF
cluster.
REN Server Cluster URL The URL for the REN server cluster that serves this MCF
cluster. This is the URL used by internal processes.
PeopleSoft MultiChannel Framework picks up the URL

from the REN server cluster when creating the MCF
cluster.
Buffer Test Click to initiate a test of the REN server's ability to break
up and send a large file using multiple internal buffers.
The buffer test is not dependent on specified domain

names, so you can use it to verify that a REN server
process is running on the network.
REN Server Browser URL The URL for the REN server cluster that serves this MCF
cluster for external clients and for agent chat. The browser
URL may be different from the cluster URL, which should
not have to go through any firewall, reverse proxy server,
or other outward-facing security barrier.
Ping Test Click to initiate a test of the REN server specified in the
URL fields. Failure may indicate that a URL or

MCF Cluster ID The MCF cluster ID is created based on the associated
REN server cluster ID. The REN server cluster must be
owned by MCF or ALL. The cluster ID takes the name of
the associated REN server cluster with MCF appended
(for example, MCF-RENCLSTR_0001).
authorization token is incorrectly specified, the REN server
is not running, or that single sign-on is not implemented.
[What about single sign-on requirement?]

Queue Server ID Each queue server can belong to only one MCF cluster.
A unique identifier for each queue server to identify its

entries in the database control tables. The log server
process paired with this queue server uses this same ID to
identify its entry in the log cluster table.
An MCF cluster can consist of a primary queue server and

any number of backup servers. Each cluster requires a
minimum of one queue server. The primary queue server
is the first queue server booted, and the remaining queue
servers are backups. If the primary queue server fails, the
system determines the subsequent primary queue server
among the backups.
You can add a queue server to a cluster by adding a new

row. Before removing a queue server, ensure that it is not
the master, then shut down its domain. Then click Delete
(the minus sign).
If an application server domain is started with a queue

server that does not belong to a cluster, PSUQSRV and
PSMCFLOG poll the MCF configuration tables indefinitely
until the queue is assigned to a cluster.
Application Server Domain Specify the application server domain of which this queue
server is a member.
Host Machine Specify the host name of the application server host
machine.
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
“PeopleTools 8.43: Configuring REN Servers” PeopleBook Enhancement, available on Customer

Connection
55
Configuring MCF Agents: Miscellaneous

A new Miscellaneous tab has been added to the PeopleSoft MultiChannel Framework Agent
Configuration page.
Use the following navigation path to access this page:
Page Name Navigation

Agents, PeopleTools, MultiChannel Framework, Universal
Miscellaneous Queue, Administration, Agents, Miscellaneous
Agents Miscellaneous page

When task is unassigned Select from:
• Close the task window
• Do not close the task window
• Prompt whether to close window (default)
Trace Level Select from:
• 0 – None (default)
• 1 – Information
• 2 – Debug
Accessing the MultiChannel Console

The MultiChannel Console link appears in the header for any user with full access permissions defined for
the MCF Agent object. However, the user must also be configured as an MCF or CTI agent to access the
MultiChannel Console.

New Parameters for MCF Cluster Tuning

A new cluster tuning option, max_refresh, sets the maximum number of consecutive times that results are
discarded when refreshing the task queue from the database if there is an intervening notification of new
persistant tasks. The default value for this parameter is 5. Refresh this option by selecting the Refresh
tuning parameters button on the Cluster Notify page.
A new cluster tuning option, max_no_reply, sets the maximum number of consecutive agent timeouts
before the queue server automatically logs out the agent and sets the agent’s console status as Assumed
Unavailable. The default value for this parameter is 5. Refresh this option by selecting the Refresh tuning
parameters button on the Cluster Notify page.
Peoplesoft CTI
The following updates were made to PeopleSoft CTI for PeopleTools 8.43.
Outbound Dial Support enhancements
When making an outbound call:

• A URL can be specified to popup a page. When popping the page, the outbound call data is also
attached to the URL so that an application can collect information such as the ANI, DNIS, and so on.
• 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.
New Outbound Call Demonstration Page
The outbound call demonstration page has been updated to include two optional functions:
• You can attach a string to the call as OutboundContext.
• You can popup a page when dialing out.
These options work with both Genesys and Cisco middleware.
Setting Up Cisco for Popup Windows
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 and the Permissions for the MCF Console
CTI users will only see the MultiChannel Console if their user ID belongs to a role that has:
57
• MCF_AGENT or MCF_SUPR real-time event notification permissions, and
• WEBLIB_MCF web libraries in their permission list.
See the “PeopleTools 8.43: Configuring REN Servers” PeopleBook Enhancement on Customer
Connection for information on REN server security.
Recovering From an Erroneous Call Cancel
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
• Selecting the line that is receiving the incoming call.
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 Event Logging
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.
New MCF_Force_Download_Attachments Connector
A new connector property, MCF_Force_Download_Attachments, enables downloading attachments that

might otherwise be interpreted as text. The property is by default set to False. If it is set to True all
attachments, including text/plain, irrespective of their size, are downloaded to the attachment repository.
The property MCF_Force_Download_Attachments enables reading of non-ASCII attachments.
Time Zone Offsets
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.

Email Headers
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.
New Error Code
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.
Connector Determination of Email Size
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.
Update to MCF_GETMAIL Node
The mail server properties previously set on the PT_EMAIL_POP3 gateway node are now set on the
MCF_GETMAIL node.
PeopleTools Mobile Agent

The following topics describe the changes made to PeopleTools Mobile Agent for PeopleTools 8.43
59
Increase Synch Server TimeOut

Increasing the jolt connection timeout value in pstools.properties has increased the default time for the
synch server timeout from 120 seconds to 600 seconds. This new timeout value should provide sufficient
time to complete a bootstrap synchronization. This setting can be set higher if timeouts persist. Higher
settings have no adverse effects on performance.
To support large attachments, you can increase the size of the memory available to the web server Java
VM. This can be accomplished by increasing the JAVA_OPTIONS –mx64m to a larger number in the
setEnv.cmd file, depending on the available memory on your web server machine.
Effective Dated Records

To support Mobile Time and Expense, the Mobile Agent now passes all rows (historical, current, and
future) that are effective dated to the mobile device during synchronization. This feature will achieve a
more accurate calculation of expenses that are based on effective dated records.
Multi-language Support for the Mobile Page Designer

The List View and Detail View labels in the Mobile Page Designer now reside in the related language
table: PSMPDEFNLANG and PSMPCONTDEVLANG. You can translate those labels through the related
language record.
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.
Conflict Detection and Resolution in the Synch Server

This section discusses the PeopleTools Mobile Agent conflict resolution functionality.
Conflict Resolution Algorithms

The four system provided conflict resolution algorithms are as follows:

Server Wins
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.
Field Level Merge
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.
Second Pass Resolution

Once the OnConflict PeopleCode programs have all executed, any remaining conflicts will be processed
a second time through the system-provided algorithm. If this is the same algorithm as previously used, no
difference in behavior will occur. However, if the server wins algorithm is replaced with device wins or
field level merge, additional conflicts may be resolved in this second pass.
61
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.
Conflict Resolution at the Component Interface Level

Conflict detection is performed on properties and collections that are part of the same synchronizable
Component Interface. If two sets of information are part of the same object, the conflict detection function
will not raise any conflicts if the information is not exposed to the same synchronization Component
Interface.
Changes to the List View and Detail View Labels

To better distinguish the group labels from field labels in the Detail View and List View, we’ll use the
PSGROUPBOXLABEL style for the laptop display. The color of the group label text is white on a gray
background (bar), and the alignment of the text is left justified. The appearance of the field label remains
unchanged
Make Object Browser Human Readable and Tree Bases

Enhance Object Browser so, where possible, all the values for instances or classes are human readable
instead of just object Ids. Also, the Object Browser uses a tree layout to show the hierarchy.
Note. The Object Browser will be documented along with the Debug features in the 8.44 PeopleBook.

Displaying and Hiding Content References on the Laptop and PDA

You can now hide a content reference on the PDA but display it on the laptop, and vice versa. Depending
on the device type setting encoded in the URL property, you can choose to display or hide certain content
references in your application.
PeopleCode Reference
The following updates to PeopleCode apply for PeopleTools 8.43.
Searching PeopleCode for SQL Injection

SQL Injection is a technique that enables users to pass SQL to an application that was not intended by
the developer. SQL injection is usually caused by developers who use "string-building" techniques to
generate SQL that is subsequently executed.
PeopleSoft recommends you search your PeopleCode for SQL injection vulnerabilities.
To search for potential SQL injection vulnerabilities:
.1 Open Application Designer.

.2 Choose Find In from the Edit menu in Application Designer.
.3 On the Find In dialog, select "SQL Injection in PeopleCode" as the Find Type.
Please note that this only finds potential vulnerabilities.
.4 Review any PeopleCode programs that are flagged.
63
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
• Rowset class Select method
• Rowset class SelectNew method
• Rowset class Fill method
• Rowset class FillAppend method
Let's take the following snippet of PeopleCode as an example:

rem Retrieve user input from the name field;
&UserInput = GetField(Field.NAME).Value;
SQLExec("SELECT NAME, PHONE FROM PS_INFO WHERE NAME='" | &UserInput | "'",
&Name, &Phone);
The intent of the developer is to allow the user to type in a name and get the person's phone number. In
the above piece of code, the developer trusts that the user is going to input data like "Smith", in which
case the resulting SQL would look like:
SELECT NAME, PHONE FROM PS_INFO WHERE NAME='Smith'
However, if the user specified "Smith' OR AGE > 55 --", then the resulting SQL would look like:
SELECT NAME, PHONE FROM PS_INFO WHERE NAME='Smith' OR AGE > 55 --'
Note the use of the comment operator (--) to ignore the trailing quote placed by the developer's code. As
you can see, this would allow a devious user to find everyone older than 55. Obviously, this would
require some knowledge of SQL and the table structures; however, it is a vulnerability.
How to prevent SQL Injection

PeopleSoft recommends the following approaches to avoid SQL injection vulnerabilities:
• Where possible, avoid using "string-building" techniques to generate SQL.
Note. This cannot always be avoided. "String-building" does not actually pose a threat unless
unvalidated user input is being concatenated to SQL.
• Use bind variables where possible rather that string concatenation.
So, rather than this:

&Name, &Phone);

Code this:
SQLExec("SELECT NAME, PHONE FROM PS_INFO WHERE NAME=:1", &UserInput,
&Name, &Phone);
• Use the Quote PeopleCode function on the user input before concatenating it to SQL. This pairs the
quotes in the user input, effectively negating any SQL injection attack.
So, rather than this:

&Name, &Phone);
Code this:
SQLExec("SELECT NAME, PHONE FROM PS_INFO WHERE NAME='" | Quote(&UserInput)
| "'", &Name, &Phone);
See Also
PeopleTools 8.42 PeopleBook: PeopleCode Reference, "PeopleCode Built-in Functions", Quote
Updates to PeopleCode Functions, Classes, and Variables

The following are the updates to the PeopleCode built-in functions and variables for PeopleTools 8.43.
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
For the BulkDeleteField, BulkInserField, and BulkModifyPageFieldOrder functions, the following

clarification has been added:
If you specify a project name as a parameter, and if that project contains objects such as fields which
have an upgrade action of delete, those objects are ignored.
EncodeURL
You can now use EncodeURL in an Application Engine program.
Int
The following note has been added to the Int function.
Note. PeopleSoft only supports 32 bit integers. The largest integer value we support is 4294967295.
65
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
The following section was added to the ViewContentURL function:

Considerations Using JavaScript
The JavaScript window open method uses the backslash (\) as a quote for the next character. You must
use double backslashes for the ViewContentURL function to work in a JavaScript. Note the four
backslashes in the beginning of the following code example:
ViewContentURL("\\\\PT-NFS01\\PSUSERWS\\TEMP\\TVN\\81X-PATCHES.TXT");
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:
Numeric Value Constant Value Description

1 %ChartValue_Horizontal The axis label is displayed
horizontally.
90 %ChartValue_Vertical The axis label is displayed
vertically.
The numeric values for the LegendPosition property are incorrect. They should start at 0 and go to 4, not
start at 1 and go to 5. The value table should be as follows:

0 %ChartLegend_Left Display legend to the left
of the chart.
1 %ChartLegend_Right Display legend to the right
of the chart.


2 %ChartLegend_Top Display legend to the top
of the chart.
3 %ChartLegend_Bottom Display legend to the
bottom of the chart.
4 %ChartLegend_Separate Generate a chart without a
legend.
New Class MCFIMInfo
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.
New Variable %Language_Data
A new system variable %Language_Data has been added.
67
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.
New Variable %Language_User
A system variable %Language_User has been added.

%Language_User returns a string value representing the current session's language as selected from the
signon page. This value can be changed for the current session with the SetLanguage function.
Note. The value of this system variable may not reflect the current data language if the user has multi-
language entry enabled.
%Menu
The following note was added to the %Menu system variable:
Note. Don't use the %Menu variable in the SearchSave event.
Changes to XmlDoc Class

The description of the RootTagName parameter of the LoadIBContent method is incorrect. If a root tag
name is not specified, and the data is non-XML, the contents are wrapped with the default root tag name
PSMessage.
The AddNode and InsertNode methods do not return a value.
If you specify a string URL for the path parameter of the ParseXmlFromURL method, the URL must be
enclosed in quotation marks.
The following section was added to the XmlDoc class:
Considerations Using a Unique Namespace
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

For example, this sort of functionality allows you to have two nodes named "Transaction", but one can be
referenced by a "psft" namespace and another not, allowing for two nodes with the same name to exist,
but each containing different data.
<root xmlns:psft="http://www.peoplesoft.com">
<psft:Transaction>Value</psft:Transaction>
<Transaction>Another</Transaction>
</root>
Incorrect results can be returned when you have a namespace as in the above example, which belongs to
the namespace defined in http://www.people.com. When the system tries to find the path of
"root/Transaction", it may return multiple nodes when in fact the end user might only want to return one.
To avoid this, do one of the following:
• Do not use FindNode. Use GetElementByTagName instead. This does not use XPath to resolve
entries in the DOM. Instead, it works at a node by node basis, for example, by getting the root node,
then getting the transactions node. This code may be a bit more complex to write, but you loose the
richness of XPath.
• Give every xmlns a prefix. The system will use XPath correctly and find the node.
Considerations Using Rowsets
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.
- <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
<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.

The flags parameter of this function and its return codes are platform dependent: the values are different
depending on whether the platform is using the VIM or MAPI mail API (the SMTP mail API ignores any
additional flags.) For this reason, SendMail should be used only in customizations that run on a known
platform, if it is used at all. The preferred, platform-independent method for sending email from
PeopleCode is to define an email routing as part of a business event, then trigger the business event
using TriggerBusinessEvent.
For workflow, in the activity email routing, you can specify the field map for Reply_To and Sender.
See Also
PeopleTools 8.42 PeopleBook: PeopleCode Reference, “PeopleCode Built-in Functions,”

TriggerBusinessEvent
PeopleTools 8.42 PeopleBooks: PeopleSoft Workflow, "Defining Event Triggers"
Parameters
flags An integer value passed directly to the mail system API to

control mail system options. The value passed in this
parameter is platform-dependent. The SMTP mail API
ignores this parameter.
The following values can be used with MAPI. You can
combine different options by adding any of the following
values and passing the sum. Pass zero to turn all of the
options off.
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.
recipients A string consisting of a semicolon-separated list of email

addresses containing the names of the message’s primary
recipients.
CCs A string consisting of a semicolon-separated list of email
addresses that are sent copies of the message.
BCCs A string consisting of a semicolon-separated list of email
addresses that are sent copies of the message. These
recipients won’t appear on the message list.
subject A string containing the text that appears in the message’s
Subject field.
71
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.
If you want to specify HTML, you should use the following:

Content-type: text/html; charset=US-
ASCII
Reply_To Optionally specify the email address that the receiver
should use when replying to this email instead of the
Mail_From value.
Sender Specifies who the email is from, as a string. This may be
different than the values specified for Mail_From or
Reply_To parameters.
Returns
Returns a Number value, which, if not one of the following general return codes, is platform-dependent.
General Return Codes
Return Code Description

0 No Error
-1 No mail interface installed.
VIM Return Codes

0 SMISTS_SUCCESS
1 SMISTS_FAILURE
4 SMISTS_ATTACHMENT_NOT_FOUND


8 SMISTS_INSUFFICIENT_MEMORY
15 SMISTS_NAME_NOT_FOUND
16 SMISTS_NOT_SUPPORTED
22 SMISTS_OPEN_FAILURE
128 SMISTS_INVALID_ADDR_BOOK
129 SMISTS_TOO_MANY_FILES
130 SMISTS_TOO_MANY_RECIPIENTS
131 SMISTS_USER_CANCEL
MAPI Return Codes

1 MAPI_USER_ABORT
2 MAPI_E_FAILURE
3 MAPI_E_LOGIN_FAILURE
4 MAPI_E_DISK_FULL
5 MAPI_E_INSUFFICIENT_MEMORY
6 MAPI_E_ACCESS_DENIED
8 MAPI_E_TOO_MANY_SESSIONS
9 MAPI_E_TOO_MANY_FILES
10 MAPI_E_TOO_MANY_RECIPIENTS
11 MAPI_E_ATTACHMENT_NOT_FOUND
12 MAPI_E_ATTACHMENT_OPEN_FAILURE
13 MAPI_E_ATTACHMENT_WRITE_FAILURE
14 MAPI_E_UNKNOWN_RECIPIENT
15 MAPI_E_BAD_RECIPTYPE
16 MAPI_E_NO_MESSAGES
17 MAPI_E_INVALID_MESSAGE
18 MAPI_E_TEXT_TOO_LARGE
19 MAPI_E_INVALID_SESSION
20 MAPI_E_TYPE_NOT_SUPPORTED
21 MAPI_E_AMBIGUOUS_RECIPIENT
22 MAPI_E_MESSAGE_IN_USE
23 MAPI_E_NETWORK_FAILURE
73

24 MAPI_E_INVALID_EDITFIELDS
25 MAPI_E_INVALID_RECIPS
26 MAPI_E_NOT_SUPPORTED
Note. Additional VIM and MAPI error codes may be generated, depending on your email provider.
There are no special return codes for SMTP.
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
The SetAuthenticationResult function is used in signon PeopleCode to customize the authentication

process. It enables the developer using Signon PeopleCode to implement additional authentication
mechanisms beyond the basic PeopleSoft ID and Password authentication.

When PasswordExpired is True, it indicates the password is expired, the passwordexpired.html page is
displayed during login when signon PeopleCode is enabled.
When DaysLeftBeforeExpire is greater than 0, and PasswordExpired is False, indicating that the
password will expire in x days, the passwordwarning.html page is displayed during login when signon
PeopleCode is enabled.
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
AuthResult Specify whether the authentication is successful. This

parameter takes a Boolean value. If True is used, the end-
user of the UserId specified on the Signon page is allowed
access to the system.
When AuthResult is True, the customer is responsible for

providing a logout to the end user. They will remain logged
in until a logout command is issued from the user, or the
session expires.
UserId Specify the UserId of the user signing on. The default
value is the UserId entered on the signon page. This
parameter takes a string value.
ResultDocument When ResultDocument is blank (""), this parameter value
is ignored. Otherwise, specify a message to be displayed
in the signonresultdoc.html file when AuthResult is True. If
AuthResult is False, the ResultDocument text value is
displayed on the signon screen. If ResultDocument has a
value, any values in PasswordExpired and
DaysLeftBeforeExpire are ignored.
PasswordExpired Specify if the user’s password has expired. The values
are:
• False (default) if the user's password hasn't expired.
• True if the user's password has expired
If this value is specified as True, the user is allowed to log

in, but is able to access only a limited portion of the
system: just enough to change their expired password.
DaysLeftBeforeExpire A numeric value indicating the number of days left before
the password expires. If the value is greater than 0, a
warning is displayed when Authorized is True and Expired
is False.
75
Returns
A Boolean value: True if function completed successfully, False otherwise.
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:

Example with Result Doc Text
See Also
PeopleTools 8.42 PeopleBook: PeopleCode Reference, "System Variables," %ResultDocument,

%AuthenticationToken
PeopleTools 8.42 PeopleBook: PeopleSoft Security, "Understanding PeopleSoft Security," PeopleSoft
Signon
New Function - NumberToDisplayString

The NumberToDisplayString function is similar to NumberToString. It formats a number according to the
specified parameters. However, NumberToDisplayString also uses the values the end user specified to
display the decimal and thousand's separator.
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
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
Format Specify the pattern for of how Number is supposed to be

formatted. See Using the Format parameter, below.
Number Specify the number to be formatted.
Width Specify the width of the string to be formatted.
Precision Specify the precision of the string to be formatted.
Using the Format Parameter
The Format parameter has the following format:

%[flags][width][.precision][R | T] [type]
• Flags have the following format:
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.

• Precision specifies how many digits follow the ".". It must be specified as a non-negative integer.
Specifying an asterisks ("*") allows for a dynamic precision specification. The maximum precision 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
In the following example, &Str1 would be "0001234,56".

&Num = 1234.56;
&Str1 = NumberToDisplayString("%#010.2t", &Num);
In the following example, &Str2 would be "$$$1234.56".
&Num = 1234.56;
&Str2 = NumberToDisplayString(("%$10.2", &Num);
In the following example, &Str3 would be " 1,234.56".
&Num = 1234.56;
&Str3 = NumberToDisplayString(("%10.2v", &Num);
In the following example, &Str4 would be "1.23456e+003".
&Num = 1234.56;
&Str4 = NumberToDisplayString(("%w", &Num);
79
See Also
NumberToString
New Function TransformExCache

A new built-in function has been added.
TransformExCache
Syntax
TransformExCache(&XmlDoc, FilePath, XsltKey)
Description
Use TransformExCache to do an Extensible Stylesheet Language Transformation (XSLT) transformation

of the specified XmlDoc object.
The file specified by FilePath must be in well-formed XML.
Considerations Using the Transform Functions
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
&XmlDoc Specify an already instantiated and populated XmlDoc

object that you want transformed.
FilePath Specify an XSLT file. You must specify an absolute path
to the file, including the file extension.
XsltKey Specify a key to uniquely name the compiled and cached
XSLT in the data buffers. This key is used both to create
the item in memory as well as retrieve it. This parameter
takes a string value, up to 30 characters.

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.
Example
Local XmlDoc &inXMLdoc = CreateXmlDoc("");
Local Boolean &ret = &inXMLdoc.ParseXmlFromURL("c:\temp\in.xml");
Local XmlDoc &outDoc = TransformExCache(&inXMLdoc, "c:\temp\in.xsl",

"INBOUND");
See Also
PeopleTools 8.42 PeopleBook: PeopleCode Reference, “PeopleCode Built-in Functions,” TransformEx,

Transform
Updates to Mobile Classes

It was possible to assign a pre-instantiated Component Interface to a peer reference property. This is not
a legal operation and would later cause a program assert. An explicit check is now made at the time of
assignment to disallow this.
PeopleSoft recommends always checking the value of what is returned by the Item method on the
PropertyInfo collection. If a valid object is not available (for example, you've reached the end of the
collection) a Null is returned.
&MyChild = %ThisMobileObject.MyChildren.Item(3);
if &MyChild = NULL then;
....
end-if;
For numeric and decimal fields that have been marked as required, and have a value of zero, result in a
required field missing value failure when the object is saved. If zero is a valid value in your application, the
field should not be required. Validation should be performed in PeopleCode.
The DoSave built-in function is supported in the following Mobile events:
• OnChangeEdit
• OnChange
Save processing (including OnSaveEdit, OnSavePreChange, and OnSavePostChange) is executed

exactly as if the end user clicked the save button. OnObjectChangeEdit and OnObjectChange are
executed prior to initiating the save processing.
If an error occurs during save processing, it is handled the same as if the user clicked the save button.
For example, if save processing encounters an OnSaveEdit error, it displays the appropriate message
box. If the error is on the current detail view, the detail view is rendered with the error highlighted. If the
error is not on the current detail view, the user is asked if they would like to transfer to the object with the
error. The user can correct the error and continue working with the component. If the PeopleCode calls
DoSave followed by TransferMobilePage and an error occurs during save processing, the
TransferMobilePage is not executed.
81
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.
Replace it with the following note.
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])
NewWindow Specify if the browser should try to use a new window to

display the attachment. This parameter takes a Boolean
value. The default is False.
PeopleTools Global Technology

The following topics describe the changes made to Global Technology PeopleBook for PeopleTools 8.43.
PeopleTools Global Technology PeopleBook Update

In the PeopleTools Global Technology PeopleBook, Chapter 3, “Controlling International Preferences” in
the section “Controlling the User Profile Language Preference,” the following paragraph contains incorrect
information (indicated in bold/red):
Since this email event is triggered not by the person to whom the message is addressed, but by
the requester, it does not make sense to send the message in the language preference of the
sender; since the recipient may not understand that language. Instead PeopleTools reads the
User Profile language preference of the email’s intended recipient and sends the email in
that user’s preferred language.
As a workaround, you can set the email language with SetLanguage(). If there are multiple recipients
with different language preferences, then individual emails could be sent to each recipient by creating a
For loop around the SetLanguage and TriggerBusinessEvent calls.
For example, if the TO field is a Role mapped to a field SEND_TO_ROLE without route control, make the
following changes:

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;
/* Create a rowset to retrieve all users for the role */

&ROLE_USER = CreateRowset(Record.ROLEUSER_VW);
&ROLE_USER.Fill("where ROLENAME= :1", SEND_TO_ROLE);
/* 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;
SQLExec("Select LANGUAGE_CD FROM PSOPRDEFN where OPRID = :1", &OPRID,

&LAN_CD);
&temp = SetLanguage(&LAN_CD);
/* May need to check return code &temp for error .....*/
/*..... Format any field that requires translation .....*/
&temp = TriggerBusinessEvent(BusProcess."bus_proc_name",
BusActivity."activity_name", BusEvent."event_name");
End-For;
/* set language code back to current user */

SQLExec("Select LANGUAGE_CD FROM PSOPRDEFN where OPRID = :1", %OperatorId,
&ORIGINAL_LANGCD);
&temp = SetLanguage(&ORIGINAL_LANGCD);
/*..... Or &temp = SetLanguage(%Language).....*/
Enable Searching of Hebrew in Verity

The following changes affect the Verity Search.
Adding Hebrew Locale and Verity Locale Mapping

Top enable searching in Hebrew, the following steps describe how to manually set up the Hebrew locale
for Verity:
1. Refer to the chapter “Adding New Languages” posted in the Customer Connection to add the Hebrew
language. This chapter is part of the Global Technology PeopleBook and has been updated in the
8.19 Release Notes.
2. On the Manage Installed Languages page (PeopleTools, Utilities, International, Languages), do the
following:
83
.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.
Verity Considerations for Non-English Environments

• For Hebrew, visual ordered documents are not indexed correctly.
• 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.
Object Naming Conventions

While system objects can be named using characters outside of the US-ASCII range, doing so
can cause problems with specific objects in some environments. In particular, we strongly
recommend using only US-ASCII characters for User ID, Password, and Run Control ID. These
are often passed as parameters in a command line; only US-ASCII characters are guaranteed
to be recognized in command line parameters in any operating system.
Adding Translations to an Existing PeopleSoft 8.4x English-Only

Database
The following changes affect the section entitled “Adding Translations to an Existing PeopleSoft 8.4x
English-Only Database” in Chapter 1 of the PeopleTools Global Technology PeopleBook:
To add translations to an existing PeopleSoft 8.4x English-only database:
1. Load your PeopleSoft Multi-Language CD-ROM.
Remember that this CD-ROM uses a different license code than the other PeopleSoft CD-ROMs.
See PeopleTools 8.43 Installation Guide for your database platform, “Setting up the File Server.”
2. Re-run the “Setting up the Batch Environment” steps.

If you are running a Windows NT PeopleSoft Process Scheduler (PSNT), you must re-run the steps
documented in PeopleTools 8.43 Installation Guide for Your Database Platform “Setting up the Batch
Environment.” Because the PeopleSoft Global Multi-Language CD-ROM contains translations for
your Crystal Reports and PS/nVision layouts, you must transfer these to your Windows NT Process
Scheduler. If you run only non-Windows NT Process Schedulers, you can skip this step.
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”.

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”.
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.
4. Run your modified DMS against your existing PeopleSoft database.

See PeopleTools 8.43 Installation Guide for Your Database Platform, appendix “Creating a Database
Manually”, section “Create Data Mover Import Script”.
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”.
Changes to Display of Fields and Labels in Translation Designer

The following changes were made to the Translation Designer for pages, and affect the section entitled
“Using Translation Designer” in Chapter 14 of the PeopleTools Global Technology PeopleBook.
 All fields on the page will be displayed, even if they are hidden fields.
 The default label ID will appear in italics but not in boldface.
 Any label ID that is used but that is not the default label will appear in boldface italics.
 Page text from hyperlinks will now display.
 If the same field has multiple label IDs on the same page, it will no longer be displayed multiple
times for that page.
85
Printing for Legal and A4 Paper

In PeopleTools Global Technology, replace the section "Printing for A4 Paper" in the chapter "Global
Reporting and Analysis" with the following text:
PeopleTools supports printing A4, Legal, and US Letter sized paper. Changing the PAPER_SIZE setting
in SETENV.SQC changes the paper size for all reports that share the same file/report/batch server
directory.
To print Legal paper, uncomment the following line in the SETENV.SQC file:
#define PAPER_SIZE LEGAL
To print A4 paper, uncomment the line above and edit it to be:
#define PAPER_SIZE A4
To ensure that you are printing your desired paper size, you must comment out or delete any other
#define PAPER_SIZE statements.
PeopleTools Internet Technology

PeopleTools 8.43 introduces performance enhancements for the PeopleSoft Enterprise Portal. Self-
service applications need to support a very large number of concurrent users. In addition, data privacy
considerations do not allow use of web browser based caching as a performance optimization.
PeopleTools is making available a server-based pagelet cache as a performance optimization. This
extends support for better performance to a larger set of self-service users while consuming less systems
resources.
The PeopleTools 8.42 Internet Technology PeopleBook provides an overview of PeopleSoft Internet
Technology, and discusses the base portal technology delivered with PeopleTools.
Using the New Window Link on the Personalize Pages

When you click the New Window link in a PIA component, a new browser window opens that displays the
search page for that component. However, when you click this link on the Personalize Content or
Personalize Layout page, the new window contains only the message “An error has occurred that has
stopped this transaction from continuing.” A popup window then appears with the message “The
homepage tab was not found.”
You can apply a workaround that resolves this error and provides a usable new browser window. To
resolve the error, you must modify the first few lines of the PeopleCode associated with the
PORTAL_HOMEPAGE component PostBuild event.
Replace the following bad PeopleCode:
PORTAL_HPWRK.PORTAL_TAB_NAME = %Request.GetParameter("tab");
If None(PORTAL_HPWRK.PORTAL_TAB_NAME) Then
Error MsgGetText(95, 117, "The homepage tab name was not found.");
End-If;
REM Used by the Personalize Content page activate peoplecode;

&FirstTime = True;
&Portal = PortalOpen();

With the following corrected PeopleCode:
REM Used by the Personalize Content page activate peoplecode;
&FirstTime = True;
&Portal = PortalOpen();
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.
Use Authentication Token Domain Name In URLs

If you supplied an authentication token domain name during PIA installation, or you entered a value for
the AuthTokenDomain property in your portal web server’s configuration.properties file, you must use that
domain name in all URLs you specify in your portal. For example, if your authentication token domain is
.mydomain.com:
Instead of using
http://mymachine:8080/pshome/signon.html
You must use
http://mymachine.mydomain.com:8080/pshome/signon.html
HTML Forms in Tables

On homepage pagelets or HTML template pagelets, you can’t insert an HTML form within a table — the
PeopleTools portal technology treats it as malformed HTML and won’t render it properly at runtime.
However, you can reformat your pagelet HTML so the form isn’t inside the table, but still appears to be.
Following is an example of the portal technology output of a pagelet containing a form within a table. It
doesn’t render properly:
<table id="mytable">
<tr>
.........
</tr>
<FORM NAME="selectReports" ACTION="index.cfm" METHOD=POST onSubmit="return

_CF_checkselectReports(this)">
<tr valign="top">
87
<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>
<FORM NAME="selectReports" ACTION="index.cfm" METHOD=POST onSubmit="return

_CF_checkselectReports(this)">

<table width="218" cellpadding="3" border="0" cellspacing="0">
<tr valign="top">
<td>
..........
</td>
</tr>

</table>
</FORM>
<table.........>
This produces valid HTML in your rendered pagelet, without significantly affecting the resulting user
interface.
Inserting HTML Using document.write

If you’re using the JavaScript document.write method to insert one HTML element inside another, such as
a form inside a table, ensure that you insert a space before the ‘/’ (slash) in the closing tag. For example:
<SCRIPT>
document.write("<FORM...>........< /FORM>");
</SCRIPT>
Notice that the key element is the space before the slash in the closing FORM tag. Without this, the
Specifying a Portal Browser Window Title

When you navigate through the portal, your browser window title changes according to the content being
displayed. For registered content, the portal takes the browser window title from the value of the Label
field in the content reference definition. You can specify a different label for each content reference.
In the current release, you can also define a browser window title for your portal home page and any
unregistered content. The title is taken from the value of the Long Description field in the portal definition.
If you leave this field blank, the browser window title is taken from the Portal Name field.

• To access the Long Description field of the portal you’re currently signed on to, navigate to
PEOPLETOOLS, PORTAL, GENERAL SETTINGS.
• 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.
Caching and Manual Refresh for Pagelets

PeopleTools portal technology now implements caching for individual pagelets. You can also control
whether the user is able to refresh the pagelet manually.
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.
To implement caching for a pagelet:
.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.
• For the Name field, enter PSCACHECONTROL.
• For the Label field, enter PSCache-Control.
.4 Specify the attribute value using the following syntax:

cache_scope,max-age=interval
Cache_scope can be one of the following:
• private — Implement user-based caching.
• role — Implement role-based caching.
89
• 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.
Disabling Manual Pagelet Refresh
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.
To 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.
Context Sensitive Pagelet Help

Your PeopleSoft application is delivered with online documentation in the form of HTML based
PeopleBooks, and a search engine that provides context sensitive help by linking you directly to the
appropriate PeopleBook section when you invoke help from a PIA page in your application.
Portal pagelets can take advantage of the same help engine. When you use a pagelet to present an
existing PIA application page that’s documented in the accompanying PeopleBooks, the page-level help
link isn’t available. You can, however, configure the pagelet to display its own help button, which will
invoke the same help link and display the same section of your PeopleBooks. You can alternatively
configure the button to invoke the help engine to link to new HTML documentation that you’ve added to
your PeopleBooks.
To configure context sensitive help for a portal pagelet:
.1 Determine the section of documentation to which you want your help button to
link.

The section of documentation you want to link to must be part of an HTML PeopleBook that you
installed on a web server. It can be part of a delivered PeopleBook, or it can be added to the
PeopleBooks Library after installation.
.2 Ensure that the section you want to link to contains a properly formatted HTML
anchor tag.
The PeopleBook section’s HTML source must contain an anchor tag with a NAME attribute whose
value starts with F1ID_.
• The PeopleBooks delivered with your PeopleSoft application already contain F1ID
anchors for the documented PIA pages that are part of the application. The text following F1ID_ is
the name of the Application Designer definition for the PIA page discussed in that section, for
example:
<a NAME="F1ID_SDK_BUS_EXPENSES"></a>
• If you’re linking to a section of documentation you added to your PeopleBooks Library
after installation, you must insert an F1ID anchor tag in the HTML source to represent the subject
discussed in that section. You can use any string containing letters, numbers, and underscores.
Remember that the name must start with F1ID_, for example:
<a NAME="F1ID_MY_PAGELET_CONTENT"></a>
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
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:
.6 Click the help button.

The system generates a URL to the PeopleBook content based on a combination of the helpURL
property in the configuration.properties file, the Help ID field in the pagelet attributes, and the
browser’s current language setting, then opens a new browser window and applies the URL to
display your PeopleBook content.
Signout From a New Page

When you click the Signout button on a new Portal page (new window) that you access through a page
link, you lose your PIA connection to all of the PeopleSoft sites. To re-establish your PIA connection, you
must sign on to PIA again.
In order to display the PIA signon screen, you need to keep the new page open, return to the page from
which you accessed the new page, and perform one of the following:
• Click the Home button.
• Trigger a PeopleCode event.
Improved Session Timeout Behavior

This issue applies only to configurations using a default user ID and password to access applications from
a portal.
With PeopleSoft portal technology, users can access applications through the portal without being
required to sign on to the applications separately. You enable this feature by making the following settings
in your portal’s configuration.properties file:
• Provide a user ID value for the defaultUSERID property.
• Provide a password value for the defaultPWD property.
• Set the byPassSignOn property to true.
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.

In previous releases, if you used the byPassSignOn feature and also set a permission list timeout for the
default user ID, your web server would acquire the same timeout setting as the permission list, overrriding
its own HTTP session timeout setting. This meant that the typically quite long timeouts set for the
permission lists would apply to the web server’s HTTP session instead of its own typically short timeout.
This can create a scenario in which inactive users unnecessarily tie up web server resources.
The solution is a new property in the configuration.properties file.
You can now specify that the permission list timeout you set for your default user ID shouldn’t apply to
your portal web server’s HTTP session. You accomplish this with the following setting in your portal’s
configuration.properties file:
usePermissionTimeoutInHttpSession=false
This enables you to continue managing application timeouts for portal users using permission lists. The
default value of usePermissionTimeoutInHttpSession is true. This setting takes effect only if you activate
the byPassSignOn feature.
See Also
PeopleSoft 8.42 PeopleBook: PeopleTools Security

PeopleSoft 8.42 PeopleBook: PeopleSoft Server Tools Administration
Detailed Error Messages in the Network Log

If you encounter a portal error condition such as a message indicating a homepage template failure, you
can diagnose this problem more easily by generating more detailed error messages in the application
server log file.
You can produce more detailed messages by increasing the logging detail level (the LogFence property)
in the PSAPPSRV.CFG file. The default value is 3 (tracing level 1). Set its value to 4 or 5 instead
(tracing level 2 or 3, respectively), for example:
LogFence=4
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
PeopleBook Corrections and Additions

In the current release of the PeopleTools Internet Technology PeopleBook, under “Changing the Portal
Interface,” Using Homepage HTML Objects, make the following corrections and additions.
93
Constructing Pagelets
In this section, add one row to the table, as follows:
HTML/Image Object Value

PORTAL_HP_ACTIONBAR_REFRESH HTML object for the refresh image on the
pagelet action bar
Customizing Homepage and Pagelet Objects
In this section, under Working with Fixed-Name HTML and Image Objects, add two rows to the table,
as follows:
HTML/Image Object Value

PT_PORTAL_IC_REFRESH Image name in database
PORTAL_HP_ACTIONBAR_REFRESH HTML object name in database
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.
Replace it with the following corrected sentence:

You can specify up to 15 extra images for a homepage using %BIND variables on
PORTAL_HP_COMPONENT and PORTAL_HP_ACTIONBAR_xxx HTML objects.
Also under Adding Images to Homepage Tabs, add one row to the table, as follows:
Bind Variable Object Replaced

%BIND(:28) Image PT_PORTAL_IC_REFRESH
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
Paginated Text Output Format for 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:

-LN60: Paginated text file with 60

lines per page
-LN20: Paginated text file with 20
lines per page
-LN0: Non-paginated text file
(Not used): Non-paginated text file
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:
PeopleSoft Process Scheduler - Process Definition – Override Options page

The resulting Command Line would look similar to the following:
C:\PT842\BIN\CLIENT\WINX86\PSCRRUN.EXE -CTMICROSFT –CDPT842 –COUSER1
-CPOPRPSWD -I45 -RP"Employees by Department for BU001" -OT5
-OPDistribution List -LGENG -OF8 -ORIENTL "BU001"
To allow users to dynamically select prompt values at runtime:
.1 Using PeopleSoft Application Designer, create a PIA Run Control page.

.2 Insert an edit box for each prompt field.
.3 Click on the newly inserted edit box to display the Page Field Properties dialog
box.
95
.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
PeopleSoft Process Scheduler – Process Definition – Override Options page
Note. The resulting command line would look the same as above except; instead of "BU001" it would
contain the selected value.
PeopleSoft Cube Manager
Registering Cube Manager Server
If you experience problems running Cube Manager perform the following:

1. Log on as an administrator.
2. Register Cube Manager server by running %ps_home%\BIN\CLIENT\WinX86\psolap.exe
/REGSERVER in the command line. For example:
C:\pt819\BIN\CLIENT\WinX86\psolap.exe /REGSERVER
PS/nVision
PS/nVision Not Configured Properly for a Workstation
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.

Note. Install workstation needs to be done prior to launching PS/nVision in 2 tier or from the Web. If this is
not done and you run reports from the web, the message will be displayed on the server and nVision
process will appear as hung.
To configure PS/nVision:
.1 Logon as a System Administrator.

.2 Go to Configuration Manager, Client Setup.
.3 Select Install Workstation. Click Apply or OK to install the workstation.
The message will no longer appear.
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
Running Reports With Output Type of Email
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.
Drilldown Using a Workbook Containing Multiple Worksheets
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.
DrillDown on the Web For Reports With File Output
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.
EnableDrillDownForFile Using PS/nVision on the web.

Indicate whether you want to enable
drilldown on a report with the output type
of file.
1 = Enable drilldown.
0 = Disable drilldown. (Default).
See PeopleTools PeopleBook: PS/nVision, “PS/nVision Reporting on the Web,” Using DrillDown and
“PeopleTools PeopleBook: PeopleSoft Process Scheduler, “Using the PSADMIN Utility”.
97
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.
Using Relative Adjustment Periods
Use the following example to specify the Relative Adjustment Period.

To retrieve x number of periods back:
"BaseAdjustmentPeriod - x" where BaseAdjustmentPeriod =
(FirstAdjustmentPeriod - 1).
For example, FirstAdjustmentPeriod = 901 (For period 1). BaseAdjustmentPeriod = 900. To specify the
last two adjustment periods, Relative StartAdjustmentPeriod should be 898.
To retrieve x number of periods ahead:
"BaseAdjustmentPeriod + x".
Using the example above, to retrieve two periods ahead, define Relative EndAdjustmentPeriod as 900 +
2 = 902.
Attaching Macros to a PS/nVision Layout Using NVSInstance Hook Procedure
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.
To attach a macro using NvsInstance Hook:
.1 Select the cell in the layout.

.2 Select Insert, Name, Define.
For the name, enter the sheet name followed by an exclamation point and the text NvsInstanceHook.
For example, Sheet 1!NvsInstanceHook.
.3 Enter the name of the macro in the Refers to field.
For the name, enter the name of Excel Visual Basic Module, where the macro is located, followed by
a period and the name of the Excel VB Macro. For example, Module1.MacroName
.4 Click Add.

.5 Click OK.
Your macro is executed after the PS/nVision Instance is created.
Unique Drilldown Output Filenames
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.
Business Rules with no Security Defined
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.
PeopleSoft Process Scheduler
Entering Long Path Names Using PSADMIN Utility
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.
Changes to the PSADMIN Utility – Cache Settings Section
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
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.”
Availability of the Window Output Type
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.”
Real-Time Event Notification Permissions
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.
To include full access for REN permission for Reporting Window:
.1 Go to PeopleTools, Security, Permissions & Roles, Permission Lists.

.2 Select the desired permission list.
.3 Go to the PeopleTools page and select the Realtime Event Notification
Permissions link.
The REN Permissions page will display.
.4 Select Full Access for the Reporting Window option.
See PeopleTools PeopleBook: PeopleTools Security, Working With Permission Lists, “Defining
Permission Lists.”

PeopleCode ProcessRequest Class Information
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.
Securing Report Repository for HTTP – WebSphere Clarification
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.
Job Definition - Email Notification Override Rules
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.
Job Definition – Distribution Lists Override Rules
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
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.
Scheduled JobSets Messages
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.
Scheduled JobSets - Output Settings
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.
Scheduled JobSets – Run Now Clarification
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.
Scheduled JobSets – Email Notifications Causing Aborts
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.
Purging Directories and Files From Report Repository Using HTTP
Previously, when using HTTP transfer protocol, directories and files were not getting purged from the
report repository. This problem has now been fixed.
Defining Process Output Types Clarification
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 Report Views in Report Manager
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.

Archiving Process Scheduler Configuration File
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.
OS390 Process Schedulers and Languages Containing Special Characters
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.
Process Scheduler Configuration File – Spaces in Directory Paths
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
Running Query to Excel Through PIA Using HTTPS Server
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.
Automatic Clauses on EFFDT and EFFSEQ
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.
Adding Criteria Values Using the Condition In List
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
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.
Workflow Queries Permissions
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.
Enable Auto Preview
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.
To activate the Enable Auto Preview feature:
.1 Click the Preferences link.

The Query Preferences dialog box appears.
.2 Select Enable Auto Preview.
.3 Click OK.
PeopleSoft Tree Manager
Performance Improvement When Modifying Tree Nodes
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.”

Restrictions When Working With Tree Branches
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.
Performance Improvement When Working With Tree Branches
Performance has improved on branch trees for following operations:

• Branching and unbranching tree nodes that have a large number of descendents.
• Switching levels.
• Moving nodes (Cutting and pasting )
• Inserting new nodes.
Tree Viewer Searches
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.
Edit Checks Performed While Updating the Range of a Leaf
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
System Requirements For Drag and Drop Functionality
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
PeopleSoft Server Tools Administration

PeopleTools 8.43 improves on existing administration features for the PeopleSoft application server,
resulting in productivity improvements for administrators.
Import of PeopleTools 8.x configuration files
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.
Improvements in application server robustness
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
Index location is $PS_HOME/data/search/<index name>/<db name>/<language cd>.
Application Server
Archiving Application Server Configuration Files
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.

Importing PeopleTools 8.x Configuration Files
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.
Detecting Orphaned Application Server Processes
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.
Identifying Servers Processes in a Domain
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 ...)
Shutting Down Server Processes in a Domain
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.
Configuration Properties File Options
New Default Value for EnableDBMonitoring
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
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).
Additional Flag Value DBFlag for IBM
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 usageuse 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.
Dirty Reads/Uncommitted Reads
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).
Detailed Error Messages in the Network Log
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.

MaxInMemoryObjects
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
Turning Compression Off in Web Server
This section describes how to turn off compression in the web server configuration properties file, which is
a workaround for the following incident:
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.
To turn compression off:
.1 Shut down the web server.

.2 Modify the compression setting in the configuration.properties file on the web
server as follows: compressResponse=OFF.
.3 Delete the browser cache.
.4 Restart the web server.
Disabling Directory Browsing in IBM HTTP Server
This section decribes how to disable browsing of a directory in IBM HTTP Server.
To disable browsing of a directory:
109
.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.
Support for IBM HTTP Server
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.
Port Conflict When Starting IBM WebSphere
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"/>

Administrati 7000 or 7501 7001 <traceService

ve xmi:id="TraceServiceConfig_1"
Debugging enable="true"
traceSpecification="*=
all=disabled"
traceOutputFilename="stdout"
diagThreadPort="7000"/>
Bootstrap 900 901 <orbSettings xmi:id="ORBConfig_1"
enable="true"
bootstrapHost="localhost"
bootstrapPort="900">
HTTP 9080 9081 <transports
Transport xmi:type="applicationserver:HTTPTrans
Port port"
xmi:id="HttpTransport_1"
hostname="*"
port="9080">
</transports>
HTTPs 9443 9444 <transports
xmi:type="applicationserver:HTTPTrans
port"
hostname="*"
port="9443" sslEnabled="true">
</transports>
Administrati 9090 9091 <transports
ve Console xmi:type="applicationserver:HTTPTrans
port"
hostname="*"
port="9090" external="false">
</transports>
virtual host 9080 9081 <virtualHosts xmi:id="VirtualHost_1"
name="default_host">
9443 9444
<aliases xmi:id="HostAlias_1"
hostname="*" port="9080"/>
<aliases xmi:id="HostAlias_2"
hostname="*" port="9443"/>
Displaying Performance Data with Resource Analyzer
Resource Analyzer is a graphical tool that displays WebSphere performance data.
111
To start Resource Analyzer:
.1 Access the (WAS_ROOT)//binn folder.

.2 Run the following command
$seappinstall –install ..installableAppsPmiSingleServerBean.ear –ejbdeploy false
.3 Restart WebSphere.
.4 Execute the following command from {WAS_ROOT}//bin folder:
$ra {Machine_Name} 900 AES
.5 You can view the following performance data in chart form.
 Application resources(servlets).
 Runtime resources.
 JVM Memory.
 WebSphere threads.
 Web applications.
Analyzing Errors with Log Analyzer
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
• UNIX, execute the file {WAS_ROOT}/bin/waslogbr.sh.
IBM WebSphere Out of Memory Errors
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.

To upgrade JRE embedded in WebSphere 4.0.3 running on Windows:
.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.
.2 Run install.bat from the extracted ZIP file to upgrade JRE.

Enter the WebSphere destination folder during upgrade. Select the remaining default values.
Refer to JDK_Refresh3_Fix_Readme.txt for complete instructions to upgrade JRE.
To upgrade JRE embedded in WebSphere 4.0.3 running on AIX:
.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.
.2 Run install.sh from the extracted TAR file to upgrade JRE.

Enter the WebSphere destination folder during upgrade. Select the remaining default values.
To upgrade JRE embedded in WebSphere 4.0.3 running on Linux:
.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.
.2 Run install.sh from the extracted TAR file to upgrade JRE.

Enter WebSphere destination folder during upgrade. Select rest of the default values.
To verify JRE Upgrade embedded in WebSphere AEs 4.0.3
.1 From the command prompt, change directory to {WAS_HOME}/java/bin.

.2 To check the java version for UNIX, type in the followiing command:
113
{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.
PeopleSoft Internet Architecture Installation

PeopleSoft Internet Architecture Installation updates {WAS_HOME}/config/server-cfg.xml file to deploy
PIA.
It updates the file and adds the following.
<installedApps xmi:id="ApplicationRef_8" name="PeopleSoft Enterprise
Application" archiveURL="${APP_INSTALL_ROOT}\peoplesoft">
<modules xmi:type="applicationserver:WebModuleRef"
xmi:id="WebModuleRef_9" uri="PORTAL"/>
xmi:id="WebModuleRef_10" uri="PSIGW"/>
xmi:id="WebModuleRef_11" uri="PSINTERLINKS"/>
</installedApps>
and
<webContainer xmi:id="WebContainer_1" installedWebModules=" WebModuleRef_9
WebModuleRef_10 WebModuleRef_11 ">
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.
BEA WebLogic 6.1
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.
Monitoring PeopleSoft Sessions Using the WebLogic Console
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.

The page is entitled “Monitoring PeopleSoft Sessions via the WebLogic Console.” You can access it
using the following navigation:
Customer Connection, Support, Documentation, Documentation Updates, PeopleTools, Internet
Architecture.
Setting Up Additional Web Applications in a Single PIA Domain

Please refer to the PeopleBook Enhancement entitled “Setting Up Additional Web Applications in a Single
PIA Domain” posted on Customer Connection.
Building HTTP Spider Indexes

On the HTTP Gateway Page, add the following description to this option.
List http://URLs to spider
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.
Web Server Timeouts
All configuration changes made on the web server require a restart before taking effect.
Name In this File Description Default

sessionTime configuration.proper The inactive interval permitted for a 1200
out ties user’s PIA/Portal usage session. seconds
This is akin to an idle browser auto (20 minutes)
logout time.
warningTim configuration.proper The inactive interval permitted for a 1080
eout ties PIA/Portal usage session before a seconds (18
session termination warning minutes)
appears.
Suppress this warning by setting
this value to be greater than the
sessionTimeout value.
Tuxedo_net pstools.properties Specifies that the client connection 0
115
work_discon must be retained throughout the

nect_timeou session. If the connection becomes
t invalid (due to one of the other
timeouts), the session will expire.
Do not adjust this setting.
If 0 is specified, the Jolt client
attempts to connect the Jolt Server
Handler in RETAINED mode. If >0 is
specified, the Jolt client attempts to
connect JSH in RECONNECT mode.
Tuxedo_sen pstools.properties The amount of time permitted to 50 seconds
d_timeout elapse between the issue of a Jolt
Request from the client (servlet)
and its complete arrival at the
application server.
This may require an increase in
value when a large amount of data
is being sent to the application
server and/or when the network is
slow.
Tuxedo_rec pstools.properties The amount of time permitted to 600 seconds
eive_timeou elapse between the issue of a Jolt (10 minutes)
t Request from the client (servlet)
and the arrival of the ensuing
response from the application
server.
This value should be considerably
larger than the
tuxedo_send_timeout and should be
set equal to or greater than the
maximum online service timeout
value on the application server.
session- web.xml (specific Determines the time period that can 20 minutes
timeout location of the file elapse before the web server
depends on the (WebLogic or WebSphere) will
server vendor) terminate HttpSession. This is akin
to an abandoned session cleanup
timeout.
If this value is set less than the
sessionTimeout in
configuration.properties, it will not
terminate the user’s online session.
The HttpSession will be removed but
the user’s session will remain valid
due to the presence of cookie in the

user’s browser. Adjusting this

setting will affect the users by
causing their state (stored in the
HttpSession) to be lost. If this
setting is too high, it will affect
resource utilization on the web
server.
Ideally, the value of this setting will
be the same as the sessionTimeout
in configuration.properties. This
will prevent state loss and dangling
HttpSessions on the web server.
Application Server Timeouts
All configurable settings for the application server require modification in PSADMIN.

JOLT psappsrv.cfg The inactive interval permitted for 60 minutes
Listener/Clie the server-side JoltSession.
nt
Raising this value can keep
CleanupTim
unnecessary server-side resources
eout
allocated beyond the time period
required. Setting this value too low
can cause the resinstantiation of
resources for a client who has
surpassed their inactivity interval.
Note. Setting this value higher
than the user’s inactive session
duration is advisable. This value will
not affect the user experience but
has a server side performance
impact.
JOLT psappsrv.cfg The amount of time allowed for the 5 minutes
Listener/Init JSL process to start.
Timeout
It is not necessary for the customers
to adjust this setting.
Workstation psappsrv.cfg The inactive interval permitted for 60 minutes
Listener/Clie the server-side Workstation Listener
117
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.
Process Scheduler Timeouts
All configurable settings for the Process Scheduler require modification through domain configuration
within PSAdmin.

Process psprcs.cfg Interval in seconds between 300 seconds
Scheduler/R attempts to reconnect to database (5 minutes)
econnection when the connection is lost.
Interval
Process psprcs.cfg This parameter indicates the 300 seconds
Scheduler/A duration in minutes allotted before (5 minutes)
uthenticatio PeopleTools Security module will
n Timeout terminate the authenticating
process released by Process
Scheduler. The timer starts from
the time the Process Scheduler
initiates the request.
PSOPTENG/ psprcs.cfg The time period permitted for the 10 seconds
Service service to run in the process in
A value of 0
Timeout question. If the service has not
infers an
completed within the allotted time
infinite
period, Tuxedo will terminate the
timeout on
service and restart the server
any service.
process.
This is the
This value should be set to the setting that
longest time that any service is most of the
expected to take for the server. internal
developer
templates
assume.
RemoteCall/ psprcs.cfg This parameter indicates the 300 seconds
RCCBL duration in seconds to run a Remote
Timeout Call within an Application Engine
119
program before it is terminated.

This is akin to a general Tuxedo
service timeout.
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.
Name Navigation Path Description Default

PS TOKEN PeopleTools, Defines the time window of a token 720 minutes
Security, Security over which a system (database) will (12 hours
Objects, Single entrust a single signon token from
Signon the same or another content
provider.
As long as a user remains signed on,
the expiration of the PS Token will
not impact the user in any way.
This is only relevant during the
GetCertificate request in a Single
Signon.
Permission PeopleTools, The administrator may select the 0 (no
List Security, appropriate permission list and timeout)
Permissions & apply a customized timeout. For a
Roles, Permission chosen permission list, the
Lists administrator may elect to never
time out, or to time out after a
specific time period.
If a user belongs to multiple
permission lists, the largest value of
those candidate permission lists is
applied to the user’s session during
signon. The permission list timeout
is only effective if its value is less
than the one configured on the web
server (see the session timeouts
table). This implies that all of the
permission list timeouts for a
particular user must be less than
the session Timeout on the web

server to be effective.
PeopleTools Security
The following updates have been made to PeopleTools Security for PeopleTools 8.43.
Increasing the METAXP Default Value

To optimize navigation, the default time page held in cache (METAXP) has been increased from 20
minutes to 900 minutes. This change affects the General Options in Personalizations.
Tracking Recently Used Passwords

Per the Joint Financial Management Improvement Program (JFMIP), an application must prevent the user
from reusing the last three recently used passwords.
To enable this feature, we are adding a new table PSPSWDHISTORY to store the number of passwords
defined on the Security Policies page (Security>User Profiles>Password Controls>Security Policies
page).
Once you have defined the number of passwords to retain, any new passwords will be added to the
history table. Consequently, you will not be allowed to reuse the three recent passwords to access the
application.
Password Control – Security Policies page
121
Password History
Number of Passwords to Enter a minimum of 3 to track the three recently used

Retain passwords.
Defining the Role Membership Rules

The following note in the section “Defining the Role Membership Rules” in Chapter 5, Incorporating LDAP
Directory Services of the PeopleTools Security PeopleBook is incorrect.
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.
The note has been amended to read as follows:
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.
Query Trees Sorting Order

Query trees are not ordered by tree name but by effective date through the Query Access Manager
(PeopleTools, Security, Query Security, Query Access Manager).
Script to Grant Permission to All Pages and Menus

To facilitate the customers in creating their own Permission Lists that can have full access or display only,
we’ll be delivering a script, DispOnly.sql, to populate the ALLPAGES Permission List with all pages. To
make a page display only, you can simply change the 0 value to 1.

Reboot the Server to Save the Password Settings

If you make any changes to the Security Polices page (PeopleTools, Security, User Profiles, Password
Controls, Security Policies), you must reboot the application server in order for those settings to take
effect. Keep in mind that changing the password setting automatically changes all login user’s password
settings because the change is global.
Improved Session Timeout Behavior

This is a portal-specific issue; it is documented in the PeopleTools Internet Technology section of the
release notes.
SwitchUser Function Support

Do not use the PeopleCode SwitchUser built-in function in PeopleSoft Application Engine or in
asynchronous subscription PeopleCode. Using SwitchUser in these cases causes an entry in the
Application Server log file indicating that SwitchUser is not supported.
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.
PeopleSoft Application Engine

The following changes have been made to PeopleSoft Application Engine for PeopleTools 8.43.
Rolling Back on Component Interface Error

Application Engine PeopleCode needs to be aware of the transaction management between itself and
component interfaces. If a component interface has a fatal error, the transaction is terminated. Application
Engine PeopleCode needs to detect this and react to it. You can detect this by checking the component
interface messages and all return codes. You can react by noting that the component interface item (such
as a row) is in error, and reopening the transaction. This rollback undoes any processing in the current
transaction, so the application PeopleCode needs to limit this undoing by calling CommitWork().
Disabling Recycle Count on Error

If the following conditions occur:
• the PeopleSoft Application Engine server (PSAESRV) recycles, showing the following message in the
PeopleSoft Application Engine Server log file, APPSRV_<mmdd>.LOG:
Recycling server after "NN" services
• and the following error message also occurs in that log file:
Failed to establish RunAeProgAsync service context for user XXXXXX
• and the following error message occurs in the PeopleSoft Process Scheduler log file,
123
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)
Worklist Replication Behavior
With worklist replication the following behavior should be noted.

A pooled worklist item could be replicated such that it is in a “not worked” state in both the source and the
target database.
In previous releases, if a user worked a pooled worklist item in the source database, the system removed
the worklist item from the database. This created orphaned worklist items in the target database.

Now, when the replication process runs, the pooled worklists are synchronized and items that had been
deleted from the source database are deleted from the target database.
Worklist Detail and Summary Page Filters
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.
Workflow System Defaults
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.
Define Template page: Message Text edit box

If the sequence of the variables in the message text is not in ascending, numerical order, then the
template variables you have declared must follow the order in the message text. If you do not
synchronize the order of the template variables and the order they appear in the message text, the
system does not resolve the unordered variables.
125
Required Tables for Workflow and Currency Conversion

The Approval Rule Set Properties dialogue, Virtual Approver, and some currency-related PeopleCode
functions depend on a set of database objects that do not exist in the PTSYS database.
The set of database objects includes:
• PS_RT_DFLT_VW
• 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.
Approval Rule Set Step Limitation

In previous releases, some customers had experienced issues when the number of steps within an
approval rule set exceeded 9. PeopleSoft has addressed this issue and approval rule sets containing
more than 9 steps now work as expected. For step numbers less than 10, the system now adds a zero
before the step number (01, 02, 03, and so on) so that all sorting processes derive the same order.
Worklist Monitor: Page Access Issues

On the Worklist Entries page in the Worklist Monitor some customers had reported having issues after
clicking the “T” button (transfer) and not being able to access the referenced page(s) even though proper
access rights were in place. This issue has been fixed in PeopleTools 8.43.
Worklist Entry Updates Page

In previous releases, the search dialog box for the Worklist Entry Updates page only displayed the
Business Process Name, Worklist Name, and Instance ID columns in the search results list. This, at
times, made it difficult to narrow the search for a desired item. With PeopleTools 8.43, additional items
now appear in the search results to help narrow the search for unique items.
Deleting a Route Control

To delete a route control on the Rules tab in an Approval Rule set, you need to select the route control
line in the grid and press one of the following key combinations:
• Shift + Delete
• Ctrl + Delete
This deletes the entire line from the grid.

Reassigned Worklist Item Behavior Modifications

The following diagram depicts three scenarios involved in worklist reassignment working in conjunction
with the virtual approver. For PeopleTools 8.43, slight modifications have been made to scenarios A and
B.
Worklist Reassignment Scenarios
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.
PeopleTools 8.43 Modifications Addressing Scenario A and B
In PeopleTools 8.43 the following options have been added to the Worklist System Defaults page.
127
Resubmit VA worklist options
Note. “VA” refers to Virtual Approver.
Not allowed In scenario A, the system presents an error notifying the

user that this approval had been submitted before. The
system will not allow the user to resubmit for approval.
In scenario B, the system presents an error expressing the

fact that the user to which the worklist is being assigned
does not have the appropriate approval authority.
In both scenario A and B, the transaction can’t be

completed and saved.
Admin/Role User only Only an administrator or the user that has the appropriate
role on one of the approval steps can save and resubmit
worklists for approval.
Yes for everyone The system does not present error messages. All users
can save and resubmit worklists for approval.

Resolved Incidents
The following table describes the customer-reported incidents that were fixed in this release. The table is
sorted by product area, so incidents affecting more than one product area may appear more than once.
Subproduct GSC Case # Incident # Incident Title Resolution
Memory leak in Application

Designer when the log file
Application options are selected for the
Designer 1896496 100781000 PeopleCode debugger. Memory leak closed.
Application Designer ML:

Definitions type "Application
Package" do not show up
Application 1931959, when logged in Non-English
Designer 3019848 111421000 App Designer session. Fixed logic in code.
Application Improving debugger error

Designer 1931705 119561000 messages Message changed.
ABEND when Test Page

button is selected in App
Application 1783356, Designer for Page
Designer 1787423 131793000 RSF_OPP_DETAIL Fixed logic in code.
Application
Designer- Issue using Translate Tools
Page Defn 1977931 560883000 with Change Control activated Fixed logic in code.
129
Error Class not found on

Process Scheduler when
Application 1836549, customer created object
Engine 1836556 123621000 PeopleCode command Fixed logic in code.
1881002,
1947015,
Application 1959487, Message 108,544 is not in
Engine 3034038 132797000 8.4x databases. Message added.
Modified code to always use the

Application Hub model does not work for local node for the requesting
Messaging 2048294 143305000 async node when publishing xnode.
Add configuration option to Added configuration option to

Application send a TPA call back to the send back a TPA call to the
Messaging 2043353 152521000 Message Broker. message broker.
1902722,
1915980,
1998333, PT 8.18.07 - PSAPPSRV -
Application 3001191, exception: Illegal instruction -
Server 3015262 103125000 AIX - DownToChild Fixed logic in code.
HTTP Spider Indexes -

Application PeopleCode error when using
Server 1964112 110888000 Proxy Host, Proxy Port 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.

Daily Core dumps on

Application 1852294, PSAPPSRV -- App server on
Server 2003108 128882000 AIX Fixed logic in code.
Need to improve Application

Server log file by removing
"noise" and improving
Application 1965130, information when a crash Improved selection of
Server 1985011 129150000 occurs. messages written to log.
Portal -Schedule for a search

Application index doesn't pick start time
Server 2000992 569006000 from the recurrence defn. Fixed logic in code.
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.
8.1xFP:BI on HP-UX 11: C++

source of Simple delivered in
1905069, SDK\HPUX_11_00\sdk.tar is Updated instructions included in
Business 2023804, Windows specific and fails to PeopleTools 8.43 release
Interlink 3023077 115138000 compile with Unix compiler notes.
Business Interlinks: cannot Updated instructions included in

Business determine if a HTTP redirect PeopleTools 8.43 release
Interlink 1970162 117663000 was followed. notes.
PT 8.1x, 8.4x -- PTPLOGMS

Changes compared to 7.5x
code causes cursors not to be Changed dedicated cursors to
COBOL 1922636 108738000 disconnected. common cursors.
131
HRMS 8.8 GPPDPRUN :

Peoplesoft Global Payroll and
COBOL 2005762 575858000 Absence. Fixed logic in code.
1287773,
1291205,
1291214,
1371595,
1432246, Component Interface fails
1489599, with inserting row with EFFDT
Component 2005670, converted to Character in
Interface 2058065 117351000 Oracle. Fixed logic in code.
Posting results to the Data

Input Page from the
Submission page does not
Component copy the Status for the first
Interface 2044726 120313000 entry only. Fixed logic in code.
Forward Port: If there's a

broken CI in the DB,
getNamespace() throws an
Component exception and doesn't return
Interface 1897825 135091000 a list of CIs. Fixed logic in code.
Error occurs because array

sArrTemplates used in Function
addToTmplArray is not
allocated enough space. Setting
Component EXCELTOCI - Subscript out the value to a high number
Interface 2044764 564718000 of Range Runtime Error. resolves this issue.
Component 2002134, Unable to see Error message

Interface 2044727 564945000 when upload fails. Fixed logic in code.
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.
Component ExceltoCI - Overflow

Interface 2044771 567672000 Problem. Fixed logic in code.
Component Interface not

firing System Edits (i.e. Name
Component Format) from
Interface 1994023 570870000 PeopleCode/App engine. 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.
Component PT 8.42 CI Possible Memory

Interface 2030781 573071000 leak from VB. Works as designed.
Component Changing connect information Fixed logic in code to prevent

Interface 2032286 576254000 in ExceltoCI does not work. errors.
Java API - PT 8.18.02 and

later, getPropertyByName()
Component API returns object of type
Interface 3011572 584179000 String instead of Float. Fixed logic in code.
133
REL scripts for Informix PT

Conversion 8.42 have incorrect default Changed all references of
Scripts 2032157 579176000 definitions. DECIMAL(n) to DECIMAL(n,0).
Upgrade: Release 8.42: Removed the

Conversion MVPRDEXP and Exporting PS_SET_CNTRL_TBL from the
Scripts 2057023 580407000 the PS_SET_CNTRL_TBL. MVPRDEXP.DMS.
Forward Port to 8.4x: T-

YIMAOK-D444Q PT:
CrystalReport8.x connecting Crystal Reports connecting to
to UNICODE database UNICODE database now
Crystal 1923441, outputs half length of double outputs correct double byte
Reports 1979126 127690000 byte characters. characters.
CTI Console now receives the

CTI: Customer reporting that list of available T-servers from
CTI Applet uses 120 KB the CTI main console instead of
bandwidth for every incoming retrieving them from the
CTI 1906857 102928000 call. configuration server.
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.
CTI Genesys - CTI console Fixed logic in code so that the

1504855, errors if no ANI is present for console works if ANI is not
CTI 1926728 113548000 the call. present in some environments.
Attach ANI to user data so that

the correct ANI can be in the
CTI: Customer reporting URL of popup screen when the
1488994, losing ANI on transfer when agent receives a transferred
CTI 1496950 122538000 using default URL. call.

CTI - Customer reports that

closing the browser is not Now the agent can choose in
1504920, logging out the agent and the agent customization page
1837992, agent continues to get calls whether to automatically log out
CTI 3043812 124558000 through the ACD. when the console is closed.
CTI: Customer reports that Software change to enable

launching CTI console fails if launching CTI console if
previous console crashed or previous console crashed or
CTI 1851052 128072000 browser was killed. browser was killed.
CTI: Customer reports that By building Genesys new 6.5

console does not recover API into pCti.cab and pCti.jar
connection with backup if files, the CTI applet now
CTI 1801874 142505000 primary T-server fails. supports T-server failover.
CTI: Customer want console Give user the option to store

to pass CTI (Genesys) call ID call ID into PeopleSoft database
to application page for or store PeopleSoft transaction
outbound calls( case ID in CTI system when the user
CTI 1911470 142838000 1911470). makes an outbound call.
CTI: Customer (Case #

1471954) would like warning
message popped up when
1471954, Genesys loses connection to Added message 162, 55 to
CTI 1472007 152716000 ACD or T-Server is shutdown. Message Catalog.
PSSYSTEMID needs to be Moved the PSSYSTEMID

2061074, defined in a row level locking record to the PTLOCK
DB2 2061074 585561000 tablespace. tablespace.
This version includes the fix for

the error 500 when the search
1545102, query is blank or query syntax is
1877784, Error 500--Internal Server illegal if the web server is
Documentati 1890391, Error occurs when the search WebLogic 5.10 SP9 or later
on 2026862 109994000 query is blank. version of WebLogic .
135
Unlike documentation claims, Remove this sentence from the

IsDigits() PeopleCode IsDigits function documentation:
function fails with strings "Numeric characters include
Documentati containing "." or "," or "-", or sign indicators and comma and
on 1923962 142893000 "+". period decimal points."
PT 8.42 File Layout is

File 3000894, unstable. No fields showing
Processing 3043841 581187000 up in Preview for segment Fixed logic in code.
Fixed performance problem in
CFileXML::ProcessBuffer by
resetting (CFileBaseStr *
m_pCurrRecData) to be equal
to the physical file size.
Very slow performance with Introduced new
readRowSet when reading CFileObject::GetSize() to help
General 1987664 104119000 larger XML files. getting the file size.
Workflow: PIA does not sort

1831375, Worklists According to
1883814, PeopleBooks, documentation
General 1944909 117478000 enhancement or fix needed. Documentation corrected.
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.
Global AD - Entering XLAT via PIA

Technology 1960698 104336000 creates problems. Fixed logic in code.


1834953,
1930526,
1937779,
1979245,
1986438,
2000304, Grid Download to Excel : When users clicks the grid
2029631, French accentuated Download to Excel button,
Global 3021898, characters are replaced by French accented characters will
Technology 3029245 113961000 unreadable characters. now be displayed correctly.
When running BI's with

UNICODE character sets
Global PT :Japanese characters (Japanese, etc) string is now
Technology 1886121 140494000 broken via BI Runtime plugin. displayed correctly.
Integration Broker:
communication issue
between
Integration HTTPTargetConnector and
Broker 1949861 102238000 webMethods XML Adaptater. Fixed logic in code.
Integration Broker: All Jolt

Integration 1924554, responses are failing with Biz
Broker 3032331 124560000 Talk integration. Fixed logic in code.
PT 8.42.x: PeopleSoft
Integration HTTPListeningConnector
Broker 2015382 570021000 replying with wrong charset. Fixed logic in code.
Integration PT 8.4x --security leak Fixed logic in code to tighten

Broker 2019515 570059000 regarding JMS Connector. security.
Can't see Chinese character

Integration in Notes R5 when using
Broker 2019375 576257000 PeopleSoft Notifications. Changed SendMail() function.
137
Integration 3000701, Appserver crashes on the 'A'

Broker 3013902 580256000 domains at Lufthansa. Fixed logic in code.
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.
Added missed SamDestroy

statements to
Internet Service ICPanel FAILED due prsmCheckChildrenPerm()
Client 1966434 138495000 to missing SQL commit. function.
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.

Enhance grids to allow up Enhanced grids so that the user

Internet 3002796, down navigation of rows can move from row to row using
Client 3024877 586659000 using cursor keys. the cursor keys.
Multi- PT :[IB] Japanese character New

Channel was corrupted via MCF_Force_Download_Attach-
Framework MCFGetMailClass and ments Connector implemented.
(MCF) 1986537 566898000 PT_EMAIL_POP3. See release notes.
Made the timeout available in

Multi- REN browser client falls into the configuration file as a tuning
Channel long retry loop over a slow parameter, with a shipped
Framework network -- reported by default of 10 sec. See release
(MCF) 1979864 578267000 customer on 8.42-05A. notes.
This fix sets the

CompressOutput flag to false
for PNG and WMZ format
Nvision: Logo not showing up image files, allowing their
nVision 1390892 101478000 when running thru the web. display.
Increased the size of

szPrcsName in
PSMPRCSEMAIL structure to
nVision 8.18 : Subject line on use
1886482, the email changes according PSM_PRCSLONGNAMELEN
nVision 1900590 106734000 to the length of the file name. (value 127).
After nVision run succeeds, a
new function called
TerminateExcel checks whether
8.19 FWP : Excel.EXE is the Excel created by nVision
remained in task manager, exists or not, and if it exists then
even if nVision process ended terminates Excel using the
nVision 2027658 108413000 successfully. PS_StopProc().
The process instance ID has

NV:Unable to open multiple been added to the drilldown
1967396, drilldown instances on the output filename. See release
nVision 2017857 110239000 web. PeopleTools 8.42. notes
139

Made changes to the records
NV: Creating scope on the TREE_FIELD_VW,
web, an inactive future eff- TREE_FIELDNS_VW and
dated tree would cause a TREE_FIELDBU_VW. Made
1964545, current tree not shown on the the EFFDT Key field a search
nVision 2036904 117603000 tree list. key.
8.19 FWP: RT - nVision

Report Request - Security Removed automatic uppercase
Template forces format for Email Template and
nVision 1947888 119628000 UPPERCASE. Security Template field.
NV: All of the nVision report
instances that have the fiscal
year variable
(%FY2,LACTUALS%)return
only a single digit of 2 instead
of two digits of 02.
%.YEAR,RGLCOMMON%
nVision 1962109 122767000 (YY). Fixed logic in code.
Added a global flag

g_bReportBook, which is
Report Book: Process checked in NamError(). If
scheduler shows failed status g_bReportBook is TRUE, then
while NVision reports running, we do not update the scheduler
nVision 1934042 127620000 but success once completed. runstatus.
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.
nVision email distribution:

users cannot override the
email template values in
"distribute to" page unless
they remove the email Added new fields and modified
nVision 3035755 571092000 template value from nVision. code. See release notes.
NV: Report Request runs to

"No Success" if security
template has over 200
nVision 2006371 576181000 character and space. Fixed logic in code.
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.
Trailing double byte spaces will

no longer be truncated by
PeopleTools when retrieving
data from the database. This
will result in them being
displayed in edit box fields and
Double byte space at the end will avoid problems with the (18,
Panel of strings cause an error 1) error message when trying to
Processor 1954017 136187000 when updating. delete them.
141
The "Last" navigation button on

grids will now work correctly,
Panel Grid Navigation does not even when used in conjunction
Processor 1990924 561948000 work properly. with column sorting.
Dates entered on Date fields
with only a two digit
specification for the year part
will now default to the 21st
Problem With Date century (2000) if the year is less
Panel Formatting Within Item -> than OR EQUAL to the target
Processor 2007041 566378000 Purchasing Attributes Page. year (usually 50).
Grid Download not working in

Open Period Update and
Appserver crash when Clicking the Download to Excel
Panel downloading Grid data to icon on a grid will no longer fail
Processor 2005571 569171000 Excel. when the grid has hidden rows.
DB2/Unix - View Attachment

1978340, gets HTTP 404 Page Not
2045121, Found error when called from
2047459, a window with session Changed logic in code to store
3010314, number appended in the files to be viewed under the
PeopleCode 3026417 105606000 URL. primary site directory only.
Added a new Method

GetMenuName() to
CICPanelService Class
(Prototype and implementation)
and modified the call to the ppr
constructor to call
%Menu will not return a value GetMenuName() instead of
PeopleCode 1986501 144030000 in SearchSave PeopleCode. NULL. See release notes.
PeopleSoft Ping Utility -

format issue, impossible to
Performance 1997283 571672000 stop the ping test case. Fixed logic in code.
Add additional debug

message for the
Performance 3037763 575375000 %GetNextNumberWithGaps. Fixed logic in code.

Invalid attempt to change

visibility of page
GM_PROJECT_DEPT At
PIA Core PROJECT_GENERAL.GBL.P
Technology 1953372 101991000 OST. Fixed logic in code.
1871305, Internal Server Error 500 - Changed logic in code to use

PIA Core 1885556, Netscape 4.7 / Mac - Tools only the first char of version
Technology 2026532 105177000 8.18.05 string to convert.
Updating a User gives a error

PIA Core "Page Data is inconsistent
Technology 1920497 117878000 with Database." Fixed logic in code.
Move response write out of

onAction to reduce the Moved response write out of
session locking duration when onAction to reduce the session
PIA Core TCP socket hanging on locking duration when TCP
Technology 1823406 126738000 writes. socket hangs on writes.
1795110,
1829379,
1914976,
1928624,
1960688,
PIA Core 1983948, Clicking Dropdown list causes
Technology 2018507 128955000 whited out. Fixed logic in code.
Customer wants to be able to

do a drilldown through PIA,
on an nVision report that was
1881729, created and sent to a file
1883047, destination(File output type), You can now drill down on the
2019556, as opposed to an nVision web for a report that has been
PIA Core 3008454, report in the report run as file output. See release
Technology 3048639 147419000 repository(Web output type). notes.
Applying personalizations to
PIA Core the grid on the page
Technology 1972863 561252000 RECV_WPO fails. Changed logic in code.
143
PIA Core Customer1: PSProperties not

Technology 1989003 561296000 yet initialized. Fixed logic in code.
Bad French message in the

tooltip when pointing on
PIA Core column header of search
Technology 1992623 562464000 results lists. Fixed message.
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.
PIA Core Hyperlink color from

Technology 2035854 574854000 stylesheet Fixed logic in code.
After clicking on the New

PIA Core Window link, a user received
Technology 2023141 574897000 the following error message: Fixed logic in code.
Spell Check causing core

PIA Core dump on Independent Text
Technology 2050980 578964000 Solution. Fixed logic in code.
"Page not found" error when

trying to use
PIA Core 2026507, loadbalancer/proxy listening
Technology 2061100 579937000 on Port 80 and 443. Fixed logic in code.

Mandatory spell checker

PIA Core doesn't check summary on Mandatory spell checker now
Technology 2059866 580406000 existing case. always checks derived fields.
<FORM> Tags improperly

written in Portal and causing
Portal 1931884 108028000 whitespace/format issues Fixed logic in code.
When using default port
property, and web- Checking the defaultPort again
accelerator, PS_LOGINLIST defaultScheme if set or request
1969524, check in scheme if defaultScheme not
1997493, PT_SAVEWARNING's set. It port is 80 and scheme is
1999281, getLoginCookieValue() http or port is 443 and scheme
2010056, javascript can fail, causing is https, the port should be
2040125, immediate expire (logout) blank and should not be a part
Portal 2055844 108728000 upon login. URL anywhere.
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.
1880019, 'Home' link in the portal

1890807, header does not refresh the Changed the
Portal 1899786 125003000 homepage. ForceRefreshPage() function.
145
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.
1793031, Netscape 6.2 Problems In

1971099, Portal 8.4(External Cref's do Fixed issue with Netscape 6
Portal 3025977 136405000 not work). and external content.
Unable to add external web

pages to Favorites inside
Enterprise Portal 8.4. Gives
PeopleCode error when tried Added an error message when
1934552, to add the external page that a user attempts to add a page
Portal 2017008 138990000 is not registered. that is not a registered cref.
Portal Admin: "Error getting

cref ..." error message is not
detailed enough, frustrating Added detailed error message
users who don't know why the to API code when Error Getting
Portal 1779295 143042000 CREF is corrupt. CRef error occurs.
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.
Base Portal Data Pagelet

Portal 2019349 572328000 Bug. Fixed logic in code.


1984837,
2002789,
2026070,
2026989, 102004000 Error Getting
3018599, Content - When Custom EPM
3022801, pagelet loads on Portal
Portal 3036042 575370000 Homepage. 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.
Sybase - Portal search page

does not display certain
Portal 2022066 585911000 results. Fixed logic in code.
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.
PSNT hangs w/ "BB lock

1934711, appears stuck: held by
Process 1984294, pid=3768". PSAESRV job
Scheduler 2034578 106088000 stays in initialize state. Fixed logic in code.
Cancelling process running

on PSUNX from Process
Monitor does not release the
1910962, concurrent process slot if
Process 1928047, Master Scheduler Service is
Scheduler 3036321 107150000 running on PSNT. Fixed logic in code.
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

1555890,
1736725,
1924993,
1934604,
1973955,
Process 3023546, NV:Unique constraint error
Scheduler 3023567 122964000 while running Report Books. Fixed unique constraint error.
SysAdm Password exposed

1934081, and easily accessible when
1949270, submitting a process through
Process 3013268, Process Scheduler Process
Scheduler 3024193 126713000 Request Page. Fixed logic in code.
PT 8.1x, PT 8.4x -- Process

kicked off via the process
Process scheduler create file under Modified Process Scheduler to
Scheduler 1750812 128625000 "/var/tmp" not being deleted. delete files created in /var/tmp.
Email distribution: The

second user's email which got
added into the distribution
1805530, detail is not being picked up
Process 1841050, by the Process Request
Scheduler 2045004 129903000 Parameter page. Fixed logic in code.
Distribution Agent Crash -

CProcSchdlrLog::FormatMes
sageW+3b (E:\PT842rc6-
Process 2027109, retail\SRC\PSSCHDLR\sched
Scheduler 3038582 130348000 ulerlog.cpp line 398) Corrected logging.
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.


1724546, Modified the awk command to
1804190, take in consideration that the
1862461, Process Scheduler is column for the available space
1868855, suspended and log gives an will be in the next line when
Process 1970357, error saying that log_output executing the Unix's df or bdf
Scheduler 1983139 131564000 dir has 0 bytes left. command.
PT 8.41: Sleep time for

Process
Scheduler/Application Engine
Process daemon is not functioning
Scheduler 1911585 133183000 correctly. Modified the scheduler code.
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.
3023026, Process Scheduler

Process 3035403, Recurrence Definition: Unable
Scheduler 3043411 136030000 to save with Custom Date. Fixed logic in code.
1965947,
1967617,
1981051,
1982405,
1991444,
1994198,
1998258,
1998493,
1998574,
1998591,
2008024,
2008595,
2012755,
2015531,
2033840, SYSAUDIT reports PAGE-06
2039006, on page:
2051365, AP_MESSAGE_LOG; record:
Process 3018145, PMN_MSGLOG_VW; field:
Scheduler 3028704 137478000 MSG_LOG_TIME. Dropped table added back.
149
Report Manager displays

Process 2001330, invalid entries for user when
Scheduler 2023795 564576000 instance number is specified. Fixed logic in code.
1933914, Process Scheduler:

2031613, Notification doesn't work for
Process 2043772, Scheduled JobSets and Job
Scheduler 3032864 570335000 containing Other Jobs. Fixed logic in code.
Users who are not supposed

to be seeing the reports have
1986334, access to the reports in the
Process 2027791, Explorer tab of Report
Scheduler 3039138 573773000 Manager. Fixed logic in code.
1800096,
1829614,
1912674,
1986676,
2033919,
2036130, Vanilla "UPDATE
2042120, PSQRYSTATS" SQL
3044250, statement fails for French Changed SQL to use binds for
Query 3046010 128768000 users. the floating point numbers.
Forward port incident T-

RKUMAR-QN9J2, "Query:
Downloading to Excel only Compression must be disabled.
Query 2030245 137079000 returns 2/3 of results" See release notes.
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.


Unable to delete report(s)
from report manger when
have at least of 1000 or more
reports in the Report
Manager. Error, "Invalid
message while SQL
transaction in process: More
than 1000 rows will be
Report returned, this may take a long
Distribution 1440944 108051000 time. Fixed logic in code.
Unable to delete nVision

report instances from Report
Manager ... "More than 1,000
rows will be returned"
Report warning... clicking OK -
Distribution 1926485 131479000 system hangs. Fixed logic in code.
My Reports Pagelet not

Working Properly on Oracle.
Encountering SQL Error .
Stmt #: 653 - ORA-01830:
1809280, date format picture ends
Report 1903578, before converting entire input Fixed SQL error on customizing
Distribution 1903585 138595000 string. the My Reports Pagelet.
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.
Cannot access Workflow Software change to make

Address Book page with Workflow Address Book page
Security 1930330 103642000 super users (PSCR, VP1...). accessible.
SwitchUser does not work

from a content provider db in
Security 1921389 104506000 the portal. Fixed logic in code.
151
Directory Rule Enabled fails Fixed code to ensure

1834986, when you attempt to execute DynRoleMembers() in
1938611, rule with a status of No FUNCLIB_LDAP.OPRID.FieldF
Security 2040843 119764000 Success. ormula returns a value.
Password confirmation page Added code on

1917682, is not displayed when user DERIVED_PSWD.CHANGE_P
1989377, successfully changes their WSD_BTN Save Edit to display
Security 2003085 121358000 password. a confirmation page.
1863649, There will not be invalid log msg
1879131, for invalid credentials( earlier ,
1900169, previous successfully logged
1904677, Invalid PIA signon causes user id were used instead of
1920173, GetCertificate error for using the current userid while
2027019, another user connected in 3- logging in the errors for invalid
Security 2036145 123487000 tier. credentials).
PT 8.4x: Change Password

allows new Password to be Change Password will no longer
Security 1916510 124868000 blank. save without a password.
Browser Lab - Security - After

Page has expired, Clicking on
the back button and on any
links behave as the session
never expire on NS and IE on
Security 2032007 125643000 all platforms. Fixed logic in code.
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.
Review Security Information Review Security Information

1831784, Queries Error if Permission Queries can now contain
1868345, List is greater than 8 permission lists that are over 8
Security 3037828 140784000 characters long. characters long.
Need the ability to track Added a new table

recently used passwords. PSPSWDHISTORY that stores
JFMIP (Federal requirement) the number of passwords
requires prohibiting the user defined on the password control
1723774, from reusing 3 recent page. These passwords may
Security 1867957, 150671000 passwords. not be reused.
LDAP Security Allows partial Changes made in

Security 2003565 565295000 usernames with wildcard. FUNCLIB_LDAP PeopleCode.
PSACCESSLOG table isn't

2018023, logging PIA users access
Security 2050995 574309000 times properly. Fixed logic in code.
Role Status was removed as a

Role Status needs to be list box item on
Security 2043759 576364000 removed from Role Search. PSROLEDEFN_SRCH.
DB2/UDB Deadlock from

PUB/SUB and application
Security 3012278 586054000 messaging. Works as designed.
153

1498193,
1826326,
1842905,
1890816,
1895544,
1898014,
1907120,
1908788,
1915297,
1915986,
1930057,
1943160,
1957612,
1969949,
2043441,
3004455,
3004728, No email sent and SQR
3017039, Report produces core file
3018693, when submitting SQR Report
3020386, to Email and CSV format on
SQR 3048999 102378000 PSUNX. Fixed logic in code.
HTML Tree Manager - Audits The edit checks performed

are not performed during the include overlapping detail
editing of detail data, only ranges, duplicate detail values,
Tree during inserts and saving the and if duplicate details are
Manager 2005625 120224000 tree. allowed. See release notes.
After doing a 'Save As' on a

tree and changing the effdt
not able to add a node onto
the tree (with an effdt greater
Tree 1899819, than original tree) until tree is
Manager 1923342 123418000 closed and reopened. Fixed logic in code.
Tree Concurrency update in Tree Fixed logic in code. See release

Manager 1946663 141597000 Manager (branch trees). notes.
Tree Tree creation process is

Manager 2028608 572879000 taking too long Fixed logic in code.

Updated templates for PT 8.42

Task 4-11 and PT 8.43 setting the alter for
PPLTLSCURTables.sql PPLTLS84CUR to Alter by
Upgrade 1931812 100091000 failing. Table Rename.
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.
In upgrade assistant, changed

the parameters passed during
Upgrade Assistant - Adding an SQL command or SQL script
the "-I" parameter while step to include a -I for Microsoft
running OSQL for MS SQL SQL Server. The -I is 'to enable
Upgrade 1909210 104626000 Server. quoted identifier.'
When opening an existing job,

Upgrade Assistant defaults to Upgrade Assistant was
1889916, ds file when opening an prompting to open the .ds file
Upgrade 1897218 131288000 existing job. instead of the .jb file.
Turn off Upgrade permission
for PTPT1100 (Security
Administrator) and PTPT1300
(Portal Administrator) and
leave on for only PTPT1200
(PeopleTools). This way, user Removed Full Access to
needs to change only Tools Upgrade for permission lists
Permission list to set Upgrade PTPT1100 and PTPT1300 per
Upgrade 1939258 137862000 security. TPRD.
When running an upgrade

compare and report, UA was
not picking up the report filter
1903908, flags from the template step
1950777, Upgrade Assistant - Compare properties upgrade options
Upgrade 2024561 141668000 Report Filter isn't always used settings.
Inserts for PSYPCMNAME in

1982556, REL800.SQL on Informix do
Upgrade 2009853 568036000 not have correct case. New REL scripts.
155
1983259,
2005395, Data missing in
2017588, PS_XMLSERVICEINFO Added PS_XMLSERVICEINFO
Upgrade 3027763 569507000 tables. to the script.
REL840 does not have a

tablespace definition for Index
Upgrade 2032694 573842000 PSCPSPCMNAME. New REL scripts.
When copying projects from

file using Upgrade Assistant,
customer gets a Invalid
Language Code 'KRN'
Upgrade 2055651 582696000 Message Fixed language code.
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.
CRM 80/84to88 - Alter w/o

deletes script drops several
Upgrade- columns - (Script generated
Data from UA and AppDes)
Administrator 1938874 140392000 Oracle9 - T203. Fixed logic in code.
Upgrade-
Data
Administrator 3034801 562318000 Index Build Error in DB2/Unix Fixed logic in code.
Poor performance running

1865786, WebLogic 6.1 on Red Hat
Web Server 3029195 107584000 Linux 7.1 Fixed logic in code.

WebLogic errors pose

security risk -- EWatcher
Web Server 1779048 115598000 connections at Sybase. This issue is fixed in SP4.
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.
Workflow: When using the

refresh button from the
Worklist page, the instances Software change to make
are not reset and hyperlinks Refresh button function properly
Workflow 1850927 102107000 do not work properly on worklist page.
Workflow, Application
Messaging: Worklist
Description NOT Transferred
in WORKLIST_MSG when
using WORKLIST_DESCR
field and no associated Software change in
2036994, WORKLIST_URL field in the PeopleCode and database
Workflow 3020035 105840000 _WL Record. objects.
When a Worklist Entry is

Reassigned to a User, there Software change to record the
1922483, is no way of identifying the previous assigned operator for
Workflow 1983392 107435000 Source of Origination. the given worklist item.
="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
Workflow: Virtual Approver

Intermittently Not Using Software change to ensure
Correct Approval Rule Set virtual approver using correct
Workflow 1920749 116651000 (View). approval rule set.
Forward Port to 8.4x: T-
DDECES-E433H Workflow,
Virtual Approver - A single
approver in greater than 1
1985652, role within the Approval Rule
2027799, Set with the same Route Software change so that a
3015316, Controls causes looping with single approver in greater than
Workflow 3025800 120991000 Approvals. 1 role will work with Approvals.
Workflow: Worklist page

hyperlink color improperly Modified PeopleCode to make
Workflow 1923700 123676000 reflects selected colors display properly.
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.
Problem with links in the Software change to make "Mark

worlklist after marking some Worked" button function
Workflow 1860085 133567000 of the notifications as worked. correctly when it is the last item.
Worklist item can still be

opened when it has already
been cancelled by another
Workflow 2030343 138789000 user. Fixed logic in code.
1923372,
2017268,
2052675, ExecuteRoleWorkflowQuery
2056005, and TriggerBusinessEvent Code change for
3003408, have significant performance ExecuteRoleWorkflowQuery
Workflow 3014488 141025000 issues. function.

SendMail: cannot reply to an

email address which is
different than the sender's Added optional fields to
Workflow 1852297 148663000 address. SendMail built-in function.
FP from 8.18: Pooled

Worklist: Enhancement to
select at which point the
Worklist drops from others'
Workflow 1906874 149487000 Worklist Queue. Fixed logic in code.
User is logged out after any

command executed on a
1816881, screen opened from a
Workflow 1989662 565554000 notification. Fixed logic in code.
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.
Workflow: The 'From' field is

not getting replicated when
using WL_REPLICATE
Workflow 2056787 580074000 process. Fixed logic in code.
159
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.

Peopletools 8.43 Release Notes: June 13, 2003

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Peopletools 8.43 Release Notes: June 13, 2003

Caricato da

Copyright:

Formati disponibili

PeopleTools 8.

June 13, 2003

June 13, 2003 PeopleTools 8.43 Release Notes

June 13, 2003 PeopleTools 8.43 Release Notes

June 13, 2003 PeopleTools 8.43 Release Notes

Microsoft SQL Server 2000

New Service Pack for BEA WebLogic 6.1

New Version of Micro Focus Server Express

• HP UX 11.0 and 11.11

• Compaq Tru64 5.1

JDBC Database Drivers

IBM AIX 5.2

Web Browser Support: Netscape 7

Future Support Plans

PeopleSoft plans to discontinue support for the following operating systems:

June 13, 2003 PeopleTools 8.43 Release Notes

• Tru64 Unix 5.0A

• OS390 v2r8 and v2r10

• Red Hat Linux 7.x (web server)

• Tru64 Unix 5.1

• Red Hat Advanced Server 2.1 32-bit

PeopleSoft plans to add support for the following operating systems:

• Red Hat Linux AS 2.1 64-bit (database server only)

• HP UX 11.23 for Itanium 2 processor family (IPF2)

• Windows 2003 Server 32-bit

PeopleSoft plans to discontinue support for the following database versions:

Minimum database requirements will be:

• Microsoft SQL Server 2000 SP3 (32-bit) for Windows 2000

PeopleSoft plans to add support for the following databases:

 Oracle 9.2.0.2 (32-bit).

 DB2 UDB 8.1 (32-bit).

• 64-bit database server only certification on Windows 2003 Server 64-bit:

 Oracle 9.2.0.2 (64-bit).

 DB2 UDB 8.1 FixPak 2 (64-bit).

 Oracle 9.2.0.2 (64-bit)

 DB2 UDB 8.1 FixPak 2 (64-bit)

• Sybase 12.5 Unicode support

June 13, 2003 PeopleTools 8.43 Release Notes

• The BEA Tuxedo 8.1 upgrade will be required.

• IBM WebSphere Server 5.1 Network Deployment

PeopleSoft Internet Architecture (PIA)

New Personalization Settings

To clear browser cache when using Microsoft Internet Explorer:

.1 Select Internet Options from the Tools menu.

Adding Pages to My Favorites

PeopleTools 8.42 PeopleBooks: PeopleSoft Application Designer, “Using Registration Wizard”

SQR for PeopleSoft Language Reference

PeopleSoft Component Interfaces

June 13, 2003 PeopleTools 8.43 Release Notes

public static void printPropertyType(String propName,

String strOAType = null;

CopyRowset Language Considerations

WSDL Binding for Component Interfaces

Microsoft Excel to Component Interfaces Utility

June 13, 2003 PeopleTools 8.43 Release Notes

PeopleSoft Business Interlinks

Writing an XML Design-Time Plug-In

Setting Up a Business Interlink Runtime Plug-In

To set up for your Business Interlink Plug-in in UNIX:

.1 Navigate to the <PS_HOME> directory and run the following command:

 For HP, replace “libext=so” with “libext=sl”.

.5 Create your Business Interlink Runtime plug-in.