Professional Documents
Culture Documents
September 2009
PeopleTools 8.50 Release Notes
September, 2009
Purpose Statement
This document provides an overview of features and enhancements included in the PeopleTools 8.50 release. It is
intended solely to help you assess the business benefits of upgrading to PeopleTools 8.50 and to plan your I.T.
projects.
Disclaimer
This document in any form, software or printed matter, contains proprietary information that is the exclusive property
of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle
software license and service agreement, which has been executed and with which you agree to comply. This
document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone
outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it
be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the
implementation and upgrade of the product features described. It is not a commitment to deliver any material, code,
or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing
of any features or functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this
document without risking significant destabilization of the code.
This documentation is in prerelease status and is intended for demonstration and preliminary use only. It may not be
specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible
for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for
any loss, costs, or damages incurred due to the use of this documentation.
Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal
Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure,
modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable
Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights
set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500
Oracle Parkway, Redwood City, CA 94065.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their
respective owners.
Prerelease Notes
Prerelease notes provide more functional and technical details than the release value
proposition. This document describes how each enhancement functions within the context of
the greater business process. This added level of detail should enable project teams to
answer the following questions:
• What delivered functionality will change?
After the project team has reviewed and analyzed the prerelease notes, business decision
makers should be able to determine whether to allocate budget and initiate implementation
plans.
Prerelease notes are published before a release.
Release Notes
Release notes are published when the product is made generally available and validate the
final scope of the release. The release notes discuss the features and enhancements that are
available with the GA release of each product, describing the finalized functional and
technical details that will enable project teams to confirm budgets and complete
implementation plans.
Additional Information
Upon the general availability of this release, you can find additional information on Oracle
Technology Network and My Oracle Support. Resources include:
• Hardware and Software Requirements guide
• Installation guides
• Upgrade guides
• Oracle Consulting
• Certification documents
See Also
The value of PeopleTools 8.50 is grounded in our normal process of including accumulated
bug fixes as well as enhancements based upon customer feedback. As a result, we added
features that will simplify the integration of your heterogeneous environments, run your
business more efficiently, improve the end user’s experience, and increase cost
effectiveness. Many of the enhancements of this release involve improving the end user’s
productivity through improved usability enhancements, page performance, and integrated
related content.
In sum, PeopleTools 8.50 continues to deliver unparalleled customer choice that ensures
support of the latest technical innovation with the industry’s lowest cost of ownership and
improved user satisfaction.
Key areas and features of PeopleTools 8.50 are:
• Related content
• Supported platforms
•
Before You Begin
Before you upgrade to Enterprise PeopleTools 8.50, always make sure that you have read
any updates to the following:
• PeopleSoft upgrade documentation.
• Operating System, RDBMS & Additional Component Patches Required for Installation on
PT 8.50.
PeopleTools 8.50 Release Notes
September, 2009
• Dropping Support for HP-UX PA-RISC For IBM DB2 Database Environments.
• JRE Support.
Importan!!! The table above does not contain a comprehensive list of our support policy, nor
does it replace what appears in the certification pages of My Oracle Support (see Doc ID
747587.1). The information provided is a snapshot of the current plans for platform support
as of general availability for this release. Always refer to Doc ID 747587.1 on My Oracle
Support for the current and most comprehensive support information.
See Also
See Also
My Oracle Support Tech Update: Deprecation Notice for PeopleTools Mobile technology and
Mobile Agent (Doc ID 832874.1)
Note. Customers running DB2 databases may still use web servers running on the HP-UX
PA-RISC operating system.
Note. This restriction applies only to environments in which IBM DB2 databases are being
used. For example, environments running Oracle or Informix databases may still run their
PeopleSoft elements on the HP-UX PA-RISC operating system.
• IBM WebSphere
JRE Support
Oracle provides and supports JRE 1.6x with your PeopleTools installation. The exact version
depends on your operating system. The JRE version provided by PeopleTools is the
minimum version required for support. You can upgrade your system to newer versions of
1.6x and still be in a supported environment.
JRE 1.4x or JRE 1.5x is not provided or supported for PeopleTools 8.50.
• Search Server
• PSADMIN
• PeopleTools Security
• SYSAUDIT Additions
• DB2 Enhancements
• Data Mover
Installation Changes
This section describes the major changes to the PeopleTools installation process, including:
• Installation Programs
• Verity Installation
Note. Decoupling PIA installations from PS_HOME was technically possible in previous
PeopleTools releases, however, it is not until PeopleTools 8.50 that Oracle formally tests and
supports this configuration option.
See Also
Installation Programs
The various installation programs (setup.exe) that you use to install PeopleTools and
PeopleSoft application files to the servers in your environment have been updated to use the
Java-based InstallAnywhere.
1. Go to PS_HOME\setup\vcredist.
2. Run vcredist_x86.exe.
Verity Installation
In previous releases, Verity, the software used for PeopleSoft Search, was installed
automatically when you installed the PeopleTools software. In PeopleTools 8.50, the
installation of Verity software has been decoupled from the PeopleTools installation.
Running the separate Verity integration installation is a mandatory step after you have
installed the PeopleTools software into PS_HOME. The installation files for Verity are part of
the PeopleSoft PeopleTools files that you download from Oracle E-Delivery.
Detailed information and step-by-step procedures are included in your PeopleTools
installation documentation.
See Also
Variable Description
$TUXDIR $TUXDIR must be set to the correct Oracle Tuxedo installation directory. For
example:
TUXDIR=/home/user/Oracle/tuxedo10gR3; export TUXDIR
• Improves understanding of your business needs and provides consistent responses and
services.
See Also
• ODBC installation.
See Also
ODBC Installation
In previous releases, on the Client Setup tab there is an option to Install PeopleSoft ODBC
Driver. This option has been removed for PeopleTools 8.50.
See Also
In previous releases, the PS_HOME directory on these servers contained both the static
binary files, such as .EXE and .DLL files, as well as the dynamic and modifiable files, such as
configuration files, log files, and scripts. Because of this varied collection of file types sharing
the same location, administrators had difficulty limiting write access to the PS_HOME
directory structure. For example, while an administrator may have wanted to restrict write
access to PS_HOME, many of the processes running within a domain required write access
to PS_HOME for generating log and trace files.
To address this challenge, in PeopleTools 8.50 the default implementation of an application
server, a Process Scheduler server, or a search server, splits the binary files from the
configuration files. When you install the PeopleSoft software to your server, just as in
previous releases, the system installs all of the necessary files for that server to the specified
PS_HOME directory. This directory can be referred to as the PeopleSoft “Binary” Home.
Then, when you create a domain, PSADMIN creates the domain and its associated
configuration files in a separate location, referred to as PS_CFG_HOME, or the PeopleSoft
‘Configuration’ Home.
By default, the system creates the PS_CFG_HOME directory in the “user” directory of the
owner of the domain. For example, depending on the operating system of the server, the
system creates PS_CFG_HOME in the following location.
• Deploy PeopleTools binaries to a single location that multiple domains can use, reducing
the time and complexity involved with installations.
• Streamline upgrades and updates because the upgrade, update, patch, or bundle needs
to be installed to fewer locations.
Note. If you do not want or need to split the location of the PeopleSoft server binary and
configuration files, you can configure your installation to operate the same as previous
releases, with the binary files and domain configuration files existing within the same
directory structure.
Note. If you are an existing customer, consider that some of the previous configuration
settings will have new default values. For example, in situations where an output directory
was previously located within PS_HOME, that output directory setting will now need to
reference a location under PS_CFG_HOME or some other writeable location. By default, the
PS_HOME directory is now designed to be read only. So, when configuring nVision, Process
Scheduler, Data Mover, and so on, be careful in considering any output locations.
Note. In environments that include the IBM z/OS operating system, in many cases the length
of the default PS_CFG_HOME directory will exceed z/OS character limits (70 in some
cases). In these cases, you have the option to override the default PS_CFG_HOME value,
replacing it with a shorter path value. Or, you can also symlink the directory and use the short
path from inside your JCL scripts. Oracle developers are currently addressing this.
See Also
Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, “Working with
Domain Configurations”
Enterprise PeopleTools 8.50 Installation for your platform
Search Server
This section discusses enhancements to the search server technology:
• Search server failover
• HP Itanium support.
Application
Server
Domain 1 Primary
Search Server
Application Domain
Server
Domain 2 Failover
Search Server
Application Domain
Server
Domain n
Multiple application server domains configured to use the same primary and failover
search domains
You configure an application server domain to connect to a failover search domain by
modifying the Remote Search Server Credentials parameter in the [Search] section in
PSADMIN, or PSAPPSRV.CFG, for the application server domain.
[Search]
Deployment Type=3
Application Server Port=7077
Remote Search Server Credentials=SRCH_PRIMARY|st-
sun04:7777,SRCH_FAILOVER|st-sun05:7777
See Also
See Also
HP Itanium Support
HP Itanium is now supported as a Type-1 search server. In previous releases, Itanium search
server support was limited to specific configuration types.
• Domain Gateway TUXEDO command line option. Provides dmadmin Tuxedo command
line options specific to the domain gateway, similar to the tmadmin command line.
See Also
• A [Search Indexes] section now appears for specifying custom index locations for search
servers, the same as application servers and Process Scheduler servers in previous
releases.
See Also
PSADMIN
In PeopleTools 8.50, you will notice the following changes to PSADMIN:
• Spawning
• Windows Service
• JavaVM Options
Spawning
By default, spawning is now disabled. Spawning refers to the configuration option to enable a
domain to start additional server processes, such as PSAPPSRV, to meet increasing
demand. In previous releases, spawning was enabled by default.
See Also
Windows Service
The name of the configuration file for the Windows service that starts an application server
domain on Windows automatically has been changed. In previous releases, the name of the
configuration file was PSNTSRV.CFG. In PeopleTools 8.50, the configuration file is
PSWINSRV.CFG.
See Also
See Also
JavaVM Options
With PeopleTools 8.50, you can now include custom Java options per server process. In
previous releases, you set Java options per domain by modifying the JavaVM Options setting
in the [PSTOOLS] section in the PSAPPSRV.CFG and PSPRCS.CFG configuration files. You
can now add that option to any configuration settings section for a server process to specify
custom Java Options for that server process. This applies to any server process, such as
PSAPPSRV, PSQRYSRV, PSAESRV, and so on.
See Also
• Usability Enhancements
• Security Enhancements
Usability Enhancements
With PeopleTools 8.50, a variety of usability enhancements are available including an
improved method for viewing targets on the PeopleSoft Target page. In previous releases,
PeopleSoft targets were displayed in a list form without showing any relationship to a
particular environment. Now, PeopleSoft targets are shown in a hierarchical form where
‘child’ targets, such as application servers, Process Scheduler servers, and search servers
appear nested within the environment they belong. That is, the page displays their
association with a particular database.
See Also
Security Enhancements
With PeopleTools 8.50, the following security enhancements have been added to the
PeopleSoft Enterprise Environment Management Plug-in:
• The constraint of multiple users being required to be in the same primary group for multi-
user installation has been removed. You can now perform a multi-user installation with
users in the same secondary group. For example, the EMAgent user and PeopleSoft
user can be in a secondary group.
• Oracle Enterprise Manager provides support for a Sudo/Power Broker with use of the
PDP (Preferred Delegation Provider) API. PeopleSoft plug-in will use PDP APIs to extend
the functionality and support Sudo/Power Broker for PeopleSoft target related
administrative actions like Start, Stop, Configure, and so on.
Serial cache loading refers to the existing process for loading shared cache. In previous
releases, when loading the shared cache for application server domains, system
administrators ran an Application Engine program named LOADCACHE. The LOADCACHE
program, adds each applicable cache object to the shared cache, sequentially. The
LOADCACHE program is in place in PeopleTools 8.50, and it runs if you choose Serial
LoadCache on the Process Request page after clicking Run on the Load Application Server
Cache page.
Parallel cache loading refers to a new option intended to reduce the time required to build a
shared cache. Parallel cache loading splits the work of the LOADCACHE program into two
separate Application Engine programs that run simultaneously within the PSJob PLCACHE,
which runs when you select Parallel LoadCache on the Process Request page after clicking
Run on the Load Application Server Cache page.
Process Description
LCACHE_INDEP Loads all the cacheable objects that are independent of other cached
objects.
LCACHE_DEP Loads all the cacheable objects that are dependent on other cached
objects. Objects that are dependent on other cached objects are those
objects that, when loaded into cache, cause instances of other objects to
be loaded as well.
See Also
PeopleTools Security
This section discusses the changes to PeopleTools Security, including:
• User Profile Synchronization.
See Also
See Enterprise PeopleTools 8.50 PeopleBooks: Security Administration, “Working with User
Profiles Across Multiple Databases”
• Encryption terminology.
Encryption Terminology
“PeopleSoft Pluggable Encryption Technology” is now referred to as “PeopleSoft Encryption
Technology.”
• PTDECRYPTPET: If you use Data Mover to export PET table data from the current
version into a version of PeopleTools that predates the introduction of the encrypt and
decrypt field object methods, run PTDECRYPTPET on the source data prior to exporting
to decrypt the table data.
See Also
See Also
Taking advantage of this new feature enables database administrators a flexible and
configurable method of aligning database resources with the real-world demands of your
business on your PeopleSoft system and realigning those resources as demand changes.
See Also
• Determine the fields to be encrypted with TDE, and in Application Designer, in the Field
Properties dialog box, select Encrypt check box.
• Enter the desired encryption algorithm in the Database Encryption Algorithm edit box on
the PeopleTools Options page.
See Also
See Also
See Also
See Also
Access ID
On PeopleTools 8.50 the SQL Server login utilized as an ACCESSID does not require being
a member of the SQL Server “sysadmin” server role.
This restricts the type of activities this login can be used for which enhances overall
application security. The PeopleSoft ACCESSID is now a member of the following fixed
database roles:
db_datareader
db_datawriter
db_ddladmin
See Also
In this example, table space PTTLRG will be created with 18000 4k pages. The number of
pages is hard-coded in the script. If the actual numbers of records loaded into table space
PTTLRG exceeds the 18000 4k page capacity, a “table space full” condition occurs. To add
more free space to the table space, the DBA can either add more free pages or add more
containers, manually.
In PeopleTools 8.50, the delivered table space create scripts appear similar to the following:
CREATE TABLESPACE PTTLRG MANAGED BY DATABASE USING
(
FILE '/data1/psdb2/ptdbname/PTTLRG.DBF' 10 M
) EXTENTSIZE 16 PREFETCHSIZE 48 DROPPED TABLE RECOVERY OFF
AUTORESIZE YES INCREASESIZE 10 M MAXSIZE NONE ;
Here, the script will create the PTTLRG table space with an initial allocation of 10 Mb of free
space, space will be increased by DB2 automatically in increments of 10 Mb when the file
container becomes full, with no maximum size limit other than that imposed by the amount of
space on the server machine. The automatic space management activity is transparent to
any application connected to the database.
Note. For new PeopleSoft databases, the delivered DDL scripts create table spaces with
auto-resize one, by default. For existing databases, you can submit a SQL ALTER command
to enable auto-resize for desired table spaces.
See Also
Enterprise PeopleTools 8.50 Installation for DB2 UDB for Linux, UNIX, and Windows
Enterprise PeopleTools 8.50 PeopleBook: Data Management, “Administering PeopleSoft
Databases on DB2 UDB for Linux, UNIX, and Windows”
If you are new to PeopleTools with the 8.50 release, or you have never used the database
level auditing feature (on DB2 for z/OS) you do not need to perform any additional steps to
implement this feature other than those described in PeopleBooks. However, if you have
used the database level auditing feature and you are upgrading from a previous release of
PeopleTools, you need to make sure to complete the steps described in your PeopleSoft
upgrade instructions.
See Also
See Also
Data Mover
This section covers Data Mover enhancements, including:
• IMPORT Command Modifications
See Also
Enterprise PeopleTools 8.50 PeopleBook: Data Management, “Using PeopleSoft Data Mover
Commands,” IMPORT
See Also
Variable Description
PS_DM_DATA This variable no longer exists in PeopleTools 8.50. It has
been replaced by PS_DM_DATA_IN.
PS_DM_DATA_IN Specifies the Data Mover input directory.
PS_DM_DATA_IN=$PS_HOME/data
PS_DM_DATA_OUT Specifies the Data Mover output directory.
PS_DM_DATA_OUT=$DM_HOME/data
PS_DM _LOG Specifies the location of PeopleSoft Data Mover log files.
The default is $DM_HOME/log, as in
$HOME/PS_DM/log.
TraceFile Specifies the trace file location.
TraceFile=%DM_HOME%/datamover.trc
Variable Description
Output Directory In previous releases, it pointed to PS_HOME\data.
Now, it should point to a writeable location, such as
PS_CFG_HOME\data.
Log Directory This location must allow Data Mover write access in the
case of a read-only PS_HOME configuration. The
default is C:\Documents and Settings\admin\Local
Settings\Temp
Note. Because the Save and Ping PPM button saves the entered URL, the Save button has
been removed from the bottom of the page.
See Also
See Also
• Timeout Settings
• Jolt
• IDDA Logging
• SYSAUDIT additions.
Timeout Settings
The default value for the Receive Timeout setting has increased from 600 seconds to 1300
seconds to compensate for longer running service timeout values, such as the ICQuery
service timeout setting.
The Receive Timeout setting appears in the Web Server Jolt Settings group box on the
Security tab for web profiles.
See Also
Jolt
This section describes changes made to Oracle Jolt, including:
• Jolt Failover String
See Also
Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration,” Working with
Jolt Configuration Options,” Configuring Jolt Session Pooling
See Also
IDDA Logging
The Instrumented Development Diagnostic Aid (IDDA) logging feature provides enhanced:
• scope of logging information across multiple functional categories, including Portal,
Integration Broker, and the report repository.
• improved content and layout of the log output, including a log file header showing such
information as PeopleTools and Java versions, as well as additional metadata associated
with each log message, such as message sequence, Java thread ID, user ID, machine IP
address, and so on.
Note. In most cases, you only enable IDDA logging when instructed to do so by an Oracle
support contact seeking specific information, but, it can also be a valuable tool for your own
troubleshooting efforts.
See Also
See Also
Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, “Working with
Oracle WebLogic,” Configuring Reverse Proxy Servers
SYSAUDIT Additions
The following new SYSAUDIT audits have been added.
• SEC-31: Verifies roles contain valid user profile definitions.
• Connected Query Audits (SYSCONQRY 1-10): Check the integrity of the Connected
Query definitions.
• Style Sheet Audits (STYLESHEET 1-04): Checks for orphaned free form style sheets and
missing parent and sub style sheets.
See Also
See Also
Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, “Working with
Oracle WebLogic,” Setting Authentication Failure Timeout
Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, “Working with
IBM WebSphere,” Setting Authentication Failure Timeout
See Also
• Application Designer.
• PeopleCode.
• Global Technology.
User Interface
This section provides an overview of Asynchronous JavaScript and XML (AJAX) and the
changes to the graphical user interface, including:
• Partial page refreshes.
• Menu navigation.
Menu Navigation
There is a new left navigation menu pagelet (Menu 2.0). Because of AJAX, when you click
the expand/collapse icons in the new menu pagelet, the system redraws only the appropriate
hierarchy for the selected link or folder, instead of refreshing the entire menu pagelet. If you
click the folder name, the entire structure is refreshed.
Note. You can choose to use the non-AJAX based menu pagelet for ease of use with screen
readers.
• You can sort the menu – Click the sort icon on the main menu to toggle between
alphabetic ascending, descending, and portal sequence number presentation of folders.
• The menu is scrollable – Click the scroll arrows that appear at the top and bottom of the
menu when the menu is too long for you to view in its entirety. When you find the folder
or page, select it.
• You can search the menu – Enter a keyword or phrase and the search index will
generate matching entries as you type. When you see a match, select the item in the list.
• The menu leaves breadcrumbs – As you navigate, breadcrumbs appear across the top of
the page to inform you of your location.
Note. You must run the Build Registry Search Index process to populate the search.
When you click the BASE EE link, this page appears showing the primary key:
Type Ahead
Prompt Fields now include a type ahead text. As you type, the system searches in the
background and matches entries in the record to the text you enter. Type ahead is
configurable through User Personalizations, and appears on search pages and in prompt
dialog boxes.
Application Designer
This section details the modifications in Application Designer definitions, including new
features and enhancements, such as:
• Radio button label changes.
• When creating free form style sheets, style class names must be identical to the
PeopleTools default style class names.
• If you replace the default style sheet or override the page style sheet with a style sheet
that includes only free form text, the free form sub style sheet must define and include all
default style classes used by the application. Unexpected results will occur in both
Application Designer and PeopleSoft Internet Architecture pages if a default style class is
missing.
Note. At runtime, style classes in free form sub style sheets take precedence over
PeopleTools-formatted style classes of the same name. Free form sub style sheets are
supported in PeopleTools 8.50 and higher.
If you attempt to import a free form sub style sheet into an earlier release, the free form sub
style sheet imports as an empty standard style sheet.
• Check Box
• Radio Button
• Drop-Down List
• Image
Note. When using these methods to navigate, the cursor will move to fields within the grid. If
grid scroll bars are present, the cursor will cause the grid to scroll as it moves through rows. If
grid tabs are present, the cursor will not cause the tab to change as it moves through rows
and columns.
In scrollable grid layout, you can designate the number of rows to appear in the scrollable
area.
In scrollable layout, the user can find the string in all tabs of the grid. The search looks
through all rows in the buffer. If the string is found, the page brings the tab where the field
and value are into view, making it the active tab.
In scrollable grid layout, you can change the sort order of a grid column directly on the
transaction page by clicking the column header; sort indicator icons appear to the left of the
column heading label.
In scrollable grid layout you can drag to resize the column directly on the transaction page.
In scrollable grid layout, you can drag and drop to columns to change column order.
This Grid Properties dialog box shows the Grid Layout and the Scrollbar properties on the
Use tab:
At design time in Application Designer, place the long edit box control on the page. Open the
properties sheet and check the Enable Rich Text Editor property on the Options tab. At
runtime, the long edit box becomes a Rich Text Editor on PIA Pages.
The editor includes a default set of toolbar buttons that appear as part of the editor page
control. However, application developers can create configuration settings files which
compliment the default toolbar set. Users can specify custom toolbar configurations for each
Rich Text Editor control. Based on the value you enter in the Configuration Settings Id field in
the Rich Text Editor options, the respective toolbar set is loaded at runtime along with the
default toolbar set.
The rich text editor enables you to store inline images along with your text.
The rich text editor tool bars are highly configurable. Any customizations are maintained
through HTML definitions in the database and become managed definitions. You can use the
rich text editor as it is delivered or switch to your own configuration without deleting the basic
configuration. You can configure elements such as style sheet and plug-in style to control the
look and feel of the editor in addition to configuring the basic tool bar to control the formatting
elements, which control the look of the text.
The existing PeopleTools Spell Check is associated with this control.
• Pagelet search.
• Pagelet help.
• Can display information from other areas within the PeopleSoft application or from
external systems.
• Several types of related content services are delivered, ready to use, based on
PeopleSoft content, such as PS Query and OBIEE report pagelets.
• You can develop custom related content services and deploy these using the framework.
• Users can interact directly with information on the Related Content frame—it is not read-
only.
• Graphical analytics from external sources (for example, a data warehouse) can be
displayed.
• Threaded discussions.
• Displaying fully functional external web sites and other related links.
• You select the Force page refresh property for the pagelet.
Pagelet Search
Pagelet Wizard enables you to embed a search field within homepage and embeddable
pagelets. The pagelet search uses PeopleCode Application Classes to define the scope,
format, and results of the search. PeopleTools provides a sample search application class,
which uses the portal registry index to perform the search. You are able to use this sample
search class to test the pagelet search functionality for any pagelet.
During pagelet design, you configure the search application class, and other attributes of the
search properties of the pagelet, such as location within the pagelet.
At runtime, a search field appears in the pagelet. When the user enters the search string and
clicks on the search button on a pagelet for which the search has been enabled, a pop up
window appears and the search results are displayed. The results also include a link to the
result and a brief description.
Pagelet Help
Pagelet Wizard enables you to associate help information for each pagelet.
At the beginning of pagelet design, the user enters a help document URL in the Help URL
field. This URL should point to the help document or the section of the help document
directly.
When the pagelet is published as a homepage pagelet, a PTPPB_PAGELET_HELP_LINK
content reference attribute is added to the homepage pagelet content reference definition
corresponding to the pagelet. The value of this content reference attribute is the help URL
entered by the user.
After configuring and deploying the Analytics servlet, you must define the analytics server in
the PeopleSoft application. Once the PeopleSoft application recognizes the analytics server,
you can retrieve, access, and view OBIEE report details as your security permits. In this
implementation, you must configure and store the OBIEE administrator credentials in the
PeopleSoft application. The PeopleSoft application uses these credentials to login to the
OBIEE server, impersonate a real user, and establish a session.
You can configure OBIEE reports as pagelets, embedded pagelets, and as transaction
pages. As part of OBIEE integration, Pagelet Wizard supports the use of OBIEE reports as
the data source for any of the supported output types.
Embeddable pagelets can be used to create Related Content services for the OBIEE reports.
Using the related content framework, these OBIEE report type of related content services can
be used with application transaction pages in a context sensitive manner. The context is
provided by the page fields on the transactional page, and is used to render OBIEE reports,
based on these page field values.
PeopleCode
This section discusses changes and enhancements made to PeopleCode, including:
• Search Events for Prompt Dialogs
• PeopleCode Debugger
• PeopleCode Editor
• PeopleCode Functions
• File processing
• Meta-SQL
• Charts
See Also
PeopleCode Debugger
The PeopleCode debugger now includes a Call Stack pane.
The Call Stack pane displays a stack of PeopleCode functions and methods that are currently
active but not completed. You can use the Call Stack pane to observe the flow of an
application as it executes a series of nested functions. When a function is called, it is pushed
onto the top of the stack. When the function returns, it is removed from the stack.
The debugger also enables you to change the value of a variable in the Local Variables pane.
Setting the value of a variable in the Debugger gives you the flexibility to try out changes and
see the results in real time, or to recover from a logic error and continue testing.
See Also
PeopleCode Editor
Just as you have always been able to navigate to a function definition by right-clicking the
function name, the PeopleCode Editor now provides similar access to application packages
and application classes.
You can right-click an application package name and select View Application Package to
open the application package definition. You can right click on an application class or method
name and select View Application Class or View Application Class Method to open the
definition in a new PeopleCode editor window.
See Also
PeopleCode Functions
This section covers general updates made to PeopleCode functions.
• CompareStrings compares the content of two text strings and returns an XML-formatted
text string detailing the differences between the two strings.
• GetPageField enables your PeopleCode to access and modify the labels on radio
buttons. The GetField function references a record field name, which creates a problem
with radio buttons since all the radio buttons in a set share the same record field name.
GetPageField solves the problem by referencing a field by its unique page field name.
See Also
File Processing
Support for the ftpunx script is discontinued in PeopleTools version 8.50. If you have made
customizations to this script, please contact your Global Support Center.
Meta-SQL
This section covers general updates made to meta-SQL.
• The new %Cast meta-SQL function converts PeopleSoft date, datetime, and time data
types to character values.
• You can use the meta-SQL functions %UuidGen and %UuidGenBase64 in a SQL Insert
or Update statement to generate a Universally Unique Identifier (UUID). %UuidGen
generates a globally unique 36-character string and %UuidGenBase64 function
generates a globally unique 24-character base64 string.
%UuidGen and %UuidGenBase64 can only be used in Insert or Update statements. You
will get an error if you use the functions in any other type of SQL.
• The %GETPROGTEXT meta-SQL function will return the full text of an Application
Engine PeopleCode program.
See Also
Charting
This section covers new charting features.
• Organization charts
Organization Charts
A PeopleSoft organization chart represents hierarchical data as boxes arrayed in horizontal
rows, or levels. Vertical connectors show parent and child relationships between boxes on
adjacent levels and horizontal connectors show relationships among siblings on the same
level.
Organization chart
You can build an organization chart based on record data or based on PeopleSoft trees.
An organization chart can invoke an auxiliary chart that displays additional related data for a
chart node.
Nodes in the both the main chart and auxiliary charts can be configured with multiple links.
When a user clicks on a link, field change processing is triggered. FieldChange PeopleCode
can be used to invoke an auxiliary chart, change chart display attributes, or perform other
related tasks.
See Also
Rating Box chart with a pop-up displaying all nodes for a rating box
See Also
• Move the separator between the table section and the chart section.
• Update task details, including task name, task start time and end time, and task
predecessor and successor information.
See Also
PeopleCode API
• New built-in functions.
• New classes.
• New methods.
• New properties.
• Modified methods.
• Modified properties.
• Deprecated products.
• Deprecated methods
• Corrected information.
See Also
New Classes
In PeopleTools 8.50, the following new classes have been added to the PeopleCode API:
• Charting classes:
OrgChart class
RatingBoxChart class
CONQRS_CONST class
CONQRSMGR class
QUERYITEMPROMPT class
SCHED_INFO class
SEC_PROFILE class
UTILITY class
• Feed classes:
Feed class
FeedFactory class
DataSource class
DataSourceParameter class
DataSourceParameterValue class
DataSourceSetting class
Utility class
The 8.50 PeopleBooks contain complete documentation on each new class including
constructors, methods, and properties as is appropriate for each class. The new methods and
properties for these classes have not been listed in these release notes.
See Also
New Methods
In PeopleTools 8.50, the following new methods have been added to the PeopleCode API:
• BPELUtil class, UpdateConnectorResponseProperties method.
Note. The preceding list does not include the methods that are new due to the addition of a
new class in the PeopleCode API. The new classes are listed in these release notes.
See Also
New Properties
In PeopleTools 8.50, the following new properties have been added to the PeopleCode API:
• Chart class, RevertToPre850 property.
Note. The preceding list does not include the properties that are new due to the addition of a
new class in the PeopleCode API. The new classes are listed in these release notes.
See Also
The 8.50 PeopleBooks contain complete documentation on each modified built-in function.
See Also
Modified Methods
In PeopleTools 8.50, the following methods have been modified in the PeopleCode API:
See Also
Modified Properties
In PeopleTools 8.50, the following properties have been modified in the PeopleCode API:
• Message class, Size property.
3. The Size property is the approximate size of the uncompressed XML data generated
when the message is published. This property applies to rowset-based messages as well
as to rowset message parts within a container message.
The 8.50 PeopleBooks contain complete documentation on each modified property.
See Also
See Also
Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, “Java Class,” System
Setup for Java Classes
Deprecated Products
The following products have been deprecated:
• PeopleSoft Business Interlinks
Consequently, the PeopleCode classes, functions, methods, properties, and system variables
associated with these products have also been deprecated. However, the documentation for
these items remains in the PeopleBooks for backward compatibility only.
The following information regarding PeopleSoft Business Interlinks has been marked as
deprecated and remains in the PeopleBooks for backward compatibility only:
• Business Interlinks class.
• BIDocs class.
The following information regarding PeopleSoft Mobile Agent has been marked as
deprecated and remains in the PeopleBooks for backward compatibility only:
• Mobile class.
• PropertyInfo collection.
• CI collection.
• Data collection.
• ListViewAttrs class.
• PropertyAttrs class.
• PeerDefaultAttributes class.
• SyncServer class.
See Also
Deprecated Methods
In PeopleTools 8.50, the following methods have been deprecated:
• Chart class, Refresh method (use the SetData method or SetOLData method instead).
• Gantt class, Refresh method (use the SetTaskAppData method or SetTaskData method
instead).
See Also
Corrected Information
Previous versions of the PeopleCode API Reference included incomplete or incorrect
information. In the PeopleTools 8.50 version of the PeopleCode API Reference, the following
significant corrections have been incorporated:
• Chart class and Gantt class
• TransformData class
• Corrected properties
1
This property was previously misidentified as a property of the Field class.
In previous versions, some of the methods and properties of the Gantt class were not clearly
differentiated from the methods and properties of the Chart class. The methods and
properties of each of these classes have been reorganized so that each class describes all
methods and properties that apply.
See Also
TransformData Class
In previous versions, a chapter on the TransformData class was missing from the book. The
PeopleCode API Reference now includes a chapter providing an overview of the
TransformData class and its properties.
See Also
Corrected Properties
In the PeopleCode API Reference, the following properties have been moved to their proper
location in the book:
• SystemIDFieldName (from the Field class to the Record class).
Global Technology
This section covers changes and updates to PeopleTools Global Technology, including:
• Changes to supported character sets.
table:
See Also
• With PeopleTools 8.50, when creating an Oracle Unicode database, use the AL32UTF8
database character set.
See Also
• In Verity 6.2.1, the supported ISO encoding for Turkish documents is ISO-8859-9,
superseding ISO-8859-3.
Note. The SYSLANG-17 audit was removed from SYSAUDIT and renamed as SWAP-8.
See Also
See Also
Changes include two new DST IDs and seven, revised time zone definitions (for AKST
Alaska Time, AST Atlantic Time, CST Central Time, EST Eastern Time, MST Mountain Time,
NST Newfoundland Time, and PST Pacific Time) to comply with the U.S. Energy Policy Act
of 2005. In addition, errors in European time zone data were fixed for five time zones (CET
Central European Time, EET Eastern European Time, GMT Greenwich Mean Time, MSK
Moscow Time, and WET Western European Time).
Depending on your status as a new or existing customer, you might be required to manually
update your time zone data:
• If you are installing PeopleTools 8.50 as a new release, you have received updated time
zone data. You do not have to manually update your time zone definitions.
• If you are an existing PeopleTools customer upgrading to PeopleTools 8.50 and you
already manually updated your time zone definitions to comply with the Energy Policy Act
of 2005 or to fix errors in European time zone definitions, your updated time zone data
will not be changed during upgrade. You do not have to manually update your time zone
definitions again.
• If you are an existing PeopleTools customer upgrading to PeopleTools 8.50 and you
have not updated your time zone definitions to comply with the Energy Policy Act of 2005
or to fix errors in European time zone definitions, your noncompliant time zone data will
not be changed during upgrade. You will have to manually update your time zone
definitions to for them to be correct. See your PeopleBooks for more information.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Global Technology, “Setting and Maintaining Time
Zones,” Updating Time Zone Definitions to Comply with Legislative and Other Changes
See Also
See Also
• XML Publisher
• Connected Query
• Cube Builder
• Cube Manager
• Tree
• Optimization Framework
• PS/nVision
• Query
Process Scheduler
This section discusses the enhancements and changes for Process Scheduler, including:
• Increase Process Instance and Report IDs
• Viewing Limitations
• Retention Days
• Runtime Parameters
• Reporting Console
• CONTENTID
• PSRF_REPORT_ID
• REPORT_ID
• REPORT_INST_VAL
• REPORT_INSTANCE
• TRANSFERINSTANCE
See Also
Viewing Limitations
For Process Monitor-List and Report Manager-List pages, the filter for Last has been
changed to include Years and a Date Range option has been added. Using the Date Range
filter, you can select a From and To date for viewing.
See Also
Retention Days
The maximum retention days setting allowed in the system has been changed from 999 to
9999. Users can define the default process (report) output retention days at the following
definition levels:
• Process Type Definition
• Process Definition
• Job Definition
Users can overwrite the process output retention days at schedule time. That is, when they
schedule a process request using PeopleCode ProcessRequest Class or a Component
Interface.
See Also
Script Description
PSCSCLR.DMS Purges all entries in the Process Request tables.
RPTCLR.DMS Purges all entries in the Report Manager tables.
PSRFCLR.DMS Purges all report entries registered for a report folder.
Note: This script only deletes the report entries on the database where it is run. If you
have multiple databases that populate the report folder, you will need to run the script
on each database to clean up all report folder entries.
See Also
See Also
See Also
Runtime Parameters
New runtime parameter pages have been added to process definitions and job definitions.
The runtime parameter page is used to determine if the process or job can be run from the
Reporting Console.
This is an example of the Runtime Parameters page for a process definition:
See Also
Reporting Console
The Reporting Console provides a single interface for a user to manage and schedule
reports. From the Reporting Console users can run a report, schedule a report, organize
reports and share reports.
This is an example of the Reporting Console:
XML Publisher
This section discusses new features and changes for XML Publisher, including:
• Descriptive Names
• Performance Enhancements
Descriptive Names
A new field File Name has been added to the Output page in the Report Definition
component. This field is used to specify a file name template that gets translated at runtime to
a physical file name. The file name field accepts a combination of output variables and plain
text. Output variables are enclosed between percent signs (%). The following variables are
supported.
• %ASD% will insert the As of Date.
• %field% where field is a the name of a field from the XMLdata that lies below the first
repeating field. For example, if you have an EMPLID field, use %EMPLID%, at runtime
the value of that field will be used. All burst key candidates on the on the bursting page
are eligible.
See Also
Enterprise PeopleTools 8.50 PeopleBook: XML Publisher for PeopleSoft Enterprise, “Defining
Report Definitions Creating Report Definitions,“ Setting Output Options
• FO Processing
• HTML Output
• PDF Security
• PDF Template
• RTF Output
• RTF Template
For each property group, the properties will be displayed, as well as the default value. Use
the prompt column to select a new value for the property.
See Also
Enterprise PeopleTools 8.50 PeopleBook: XML Publisher for PeopleSoft Enterprise, “Setting
Up XML Publisher,“ Defining Global Properties
Performance Enhancements
XML generation for query data source is now in C++ which provides better performance and
less memory usage.
A new XMLDoc to XML API has been created, this API provides better performance and less
memory usage. This can be used to replace your XMLDoc data source with XML file.
See Also
Enterprise PeopleTools 8.50 PeopleBook: XML Publisher for PeopleSoft Enterprise, “Defining
Report Definitions Creating Report Definitions,“ Associating Templates
See Also
Enterprise PeopleTools 8.50 PeopleBook: XML Publisher for PeopleSoft Enterprise, “Defining
Report Definitions Creating Report Definitions,“ Associating Templates
Connected Query
Connected Query provides the ability to create a single XML file based on a set of queries
with parent-child relationships. A Connected Query is a hierarchical object built with existing
PeopleSoft Queries. A parent query can nest n levels of child queries and any child query can
have m sibling queries within a hierarchy.
There are no artificial limits to n and m, but typical use will involve a single parent-child
relationship or a few levels of nesting. Fields in a child query are mapped to related fields in
the immediate parent query. A Connected Query will return a hierarchical data set in which
data returned by child queries is filtered by the results of its immediate parent query.
The output for connected query is always an XML file.
Connected Query can be used as a data source for XML Publisher reports that require sub
reports.
A new folder for Connected Query has been added under Reporting Tools. Connected Query
has the following components:
Component Description
Connected Query Quick Start The Connected Query Quick Start is a wizard that
walks you through creating a simple Connected Query
with a single parent query and a single child query
linked using a set of related fields.
Connected Query Manager Connected Query Manager provides a report developer
the ability to create a new Connected Query, edit an
existing Connected Query, copy existing Connected
Queries, delete a Connected Query object, as well as
run it in three modes:
• Preview XML
• Run to window
• Schedule
Connected Query Viewer Connected Query Viewer is used to run the Connected
Query in three modes:
• Preview XML
• Run to window
• Schedule
Schedule Connected Query Schedule Connected Query allows you to run the
connected query in the Process Scheduler.
See Also
• HKEY_CURRENT_USER.
Note. Crystal 2008 is the latest version of Crystal Reports. The Crystal 9 is not supported
starting with PeopleTools 8.50.
HKEY_CURRENT_USER
HKEY_CURRENT_USER replaces HKEY_LOCAL_MACHINE in the previous Tools
releases.
For example, HKEY_CURRENT_USER\Software\BusinessObjects\Suite 12.0\Crystal
Reports\Database\.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Crystal Reports for PeopleSoft, “Using Crystal
Reports 2008,” Running Crystal 2008 Reports from PeopleSoft Process Scheduler
See Also
Enterprise PeopleTools 8.50 PeopleBook: Crystal Reports for PeopleSoft, “Working with
Multiple Languages,” Understanding How to Work with Multiple Languages, Crystal Reports
Designer/Runtime Language Versions
The following diagram illustrates, at a high level, the components of Crystal Reports:
You first create queries using the PS/Query Designer, and then you design report layouts in
the Crystal Reports 2008 sp1 Designer application referencing the fields defined in the
queries that you created.
Alternative 1 Alternative 2
Crystal Report 2008 Engine BusinessObjects Enterprise XI
(Embedded in PeopleTools Windows Application (on Unix, Linux, orWindows)
Server)
PeopleTools OpenQuery PeopleSoft Query Access Services (QAS)Web
Services
PS/Query execution environment PS/Query Execution Environment
PeopleSoft database PeopleSoft Database
See Also
Enterprise PeopleTools 8.50 PeopleBook: Crystal Reports for PeopleSoft, “Getting Started
with Crystal Reports for PeopleSoft,” Crystal Reports Concepts
Applications 9.1 that use Crystal Reports 9. Applications 9.1 that use Crystal 9.
For example, a PeopleTools-only upgrade. For example, a PeopleTools-only upgrade.
Scenario C: You use PeopleTools 8.50 and versions of Scenario F: You use PeopleTools 8.50 and versions of
PeopleSoft applications prior to PeopleSoft 8. PeopleSoft applications prior to PeopleSoft 8.
For example, a PeopleTools-only upgrade. For example, a PeopleTools-only upgrade
Depending on the Crystal Report execution environment that you use with PeopleTools 8.50
and your current Crystal Report execution environment, you have different considerations.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Crystal Reports for PeopleSoft, “Getting Started
with Crystal Reports for PeopleSoft,” Crystal Reports Execution Environments
When you run an earlier format Crystal Report in the Crystal Reports 2008 application or
through the PeopleSoft Process Scheduler, the Crystal Reports application runs the
Verify Database function, which picks up any errors—such as missing fields—in the
report. If errors are detected, you must correct the report before you can run it
successfully.
• When you run reports using the PeopleSoft Process Scheduler in the PeopleSoft Pure
Internet Architecture, they are created in the Crystal Reports 2008 .rpt format and you
cannot open them using any version of Crystal Reports earlier than version 9.
You can use earlier format report templates to generate reports; however, to ensure
compatibility, you should always create the reports in the Crystal Reports 2008 format.
Note. If you are upgrading from a previous version of PeopleTools, your pre-PeopleTools
8.50 Crystal reports will need to be converted to the Crystal Reports 2008 format using the
PeopleTools RPT Conversion utility pscvtrpt.exe.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Crystal Reports for PeopleSoft, “Using Crystal
Reports 2008,” Understanding Crystal Reports 2008 Compatibility Issues
PeopleTools 8.50 Installation <for your database platform>: “Installing and Configuring
Software for Crystal Reports,” Converting Crystal Reports, Converting Existing Crystal
Reports to Crystal Reports 2008 SP1 format
Cube Builder
This section discusses enhancements that are made to PeopleSoft Cube Builder, including:
• Oracle Smart View for Office 11.1.1.1 Upgrade.
Note. PeopleSoft Cube Manager is the legacy engine used before PeopleTools 8.50 to
create cubes in diverse OLAP engines, including Essbase. Although the legacy Cube
Manager has been updated to the new Essbase 11.1.1.1 API, only the new Essbase Cube
Builder contains all the new Essbase features such as Unicode support, Aggregate Storage,
and a wider set of member and dimension properties.
A new folder for Essbase Cube Builder has been added under PeopleTools Cube Builder
with the following components:
Component Description
Connections Add and maintain Essbase connectivity parameters.
Dimensions Add and maintain Essbase dimensions.
Outlines Add and maintain Essbase outlines.
Utilities Delete and rename Essbase objects.
Create Cube Run the cube creation batch process.
Dynamic Dimension Templates Create and maintain dynamic object cube dimension
templates.
Cube Dimension Builder Setup Set up values to use in the dimension builder graphical user
interface.
Connection
The first step in creating Essbase cubes is to use the Connections page to create
connectivity information:
Dimensions
Dimensions are equivalent to fields in a relational database. In data analysis terms,
dimensions can be thought of as criteria that are used to pinpoint a particular piece of data.
Dimensions are subdivided into categories called members. Members can be added
manually to dimensions; and members are populated by the results of a PeopleSoft Query or
populated from a PeopleSoft Tree structure.
Use the following pages to create Essbase dimensions:
Page Usage
Dimension Create or update Essbase dimensions.
Member Formula Enter formula information for a dimension member.
Find Tree Search for and select an existing tree that is defined in the system.
Select Top Node Select an existing node of a highlighted tree.
Find Query Select an existing query that is defined in the system.
Select a Column Select an existing column of a highlighted query.
The columns displayed are from the select statement of the query.
Generation Names Enter the generation names for Essbase dimension.
Outlines
Creating an outline is grouping dimensions together to define the structure of the cube, and
then defining the data queries that will be used to populate the cube.
Page Usage
Cube Outline Add dimensions to the current outline.
Add Cube Dimensions Select dimensions to add to the current outline.
Current Dimension List Remove dimensions from the current outline.
Data Sources Add the cube data query or queries. You can supply one or more queries to fill
the cube.
Find Query Search for available queries.
Dimension Mapping Map columns from data extraction queries to dimensions, select a column from
data extraction as the measure, and unmap previously mapped columns.
Query Prompt Values View the current prompt values for a query and change them if necessary.
Utilities
Use the Essbase Utilities component (CUB_DIMDELETE) to maintain Essbase cubes:
Page Usage
Dimension Delete Delete any created dimension in the system as long as the dimension is not
referenced in any outline.
Outline Delete Delete any created outline in the system as long as the outline is not referenced
in any cube creation run control.
Run Control Delete Delete any cube creation run control.
View Dynamic Objects View all dynamic objects (queries and trees) that are used in the definition for
the selected dimension.
View any runtime parameters that are used when you run queries.
View what queries and trees are part of the dimensional structure if you are
having problems opening the dimension definition.
Help diagnose permission problems with dynamic objects.
View Outline Structures View all the dimensions that are a part of the outline for the selected outline.
Outline Expansion Perform the full dimension expansion for every dimension that is a part of the
selected outline.
Run all dynamic queries and trees in each dimension and display the total
number of rows processed for each dynamic object.
Building Cubes
Building Essbase cubes is sending all of the defined information—cube structure and data—
to the Essbase server using the Create Cube component, which runs the Process Scheduler.
Use the following pages to build Essbase cubes:
Page Usage
Create Cubes Run the process that sends all of the defined information to the Essbase
database to build Essbase cubes.
Outline Prompt Field Values View all data source queries that are assigned to the outline.
Modify Prompt Field Values Change any query prompt values on any query that are defined in the selected
outline.
When an Essbase cube is built successfully, a new Open Cube in Smart View link is
available on the Process Details page that enables you to view the created cube (data and
metadata) in a Microsoft Excel spreadsheet.
This example shows the Smart View window that displays the top members of the two
dimensions created:
You can drill down or use the POV Smart View tool to manipulate the data.
See Also
Cube Manager
PeopleTools 8.50 continues supporting Cognos PowerPlay 7.x. The PowerPlay Options
(under PeopleTools, Cube Builder, Cube Manager, Cube Instances) page now features:
• A Cognos Binaries section that enables you to override the registry locations (of
PowerPlay, Transformer, and Enterprise server) where the binaries folders are located.
• A Logon Password field that enables you to configure Cognos Enterprise Server in cube
instance definition with passwords besides blank passwords.
• Define the prefix that is applied to each record and field definition created by PeopleSoft
Cube Manager.
Note. Oracle Essbase and Star Schema users who continue using PeopleSoft Cube Manger
must acquire Cognos in a version no higher than 7.3. (Cognos 8.x and 9.x are not
supported.)
See Also
Tree Manager
In PeopleTools 8.50, using the Detail Value List page, you have options of using tree
effective dates from the layout or enter a new effective date for trees at the time of Report
Request:
Effective Date Criteria Select the None option to display all EFFDT data rows for ranged or dynamic
tree details, including future EFFDT data.
Select the Tree Effective Date option to display EFFDT detail data with
EFFDT less than or equal to a Tree EFFDT.
Note. Future EFFDT detail date is not displayed if the Tree Effective Date
option is selected.
See Also
Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Tree Manager, “Using PeopleSoft Tree
Manager," Working with Detail Values, Viewing Detail Values
Optimization Framework
This section covers enhancements that are made to the PeopleSoft Optimization Framework.
Note. iLog CPLEX is the mathematical engine that is used by the PeopleTools Optimization
Framework. No new functionality in CPLEX 11.0 will be included; existing functionality that
we use works as with CPLEX 10 versions.
PS/nVision
This section covers changes that are made to the PeopleTools PS/nVision technology,
including:
• Accepting tree effective-date at the time of criteria definition.
• Drilling down PS/nVision reports using web services (nVisionDrill VSTO add-in).
Criteria Definition
The PeopleSoft nVision Filter Criteria dialog in nVision client is enhanced to include an As of
Date field along with the tree name. Using this page, you are able to:
• Associate effective-date for trees at the time of criteria definition.
Accepting tree effective-date at the time of criteria definition enables you to have multiple
trees in the layout with different effective dates.
Note. PeopleSoft nVision Filter Criteria dialog can be accessed only in nVision client.
Report Request
The Report Request dialog in nVision client and Report Request page in web client were
redesigned. Using this component, you have an option of either:
• Use tree effective-dates from layout definition.
Note. This change will affect only matrix layouts, as only in matrix layouts we have an option
of selecting trees. Tabular layouts are not affected.
Note. Drilldowns are affected with this change since it inherits all the criteria of the selected
cell on the parent report and provides a sub report.
In Report Request, there are new check boxes labeled Override Layout in the Windows
client or Override Tree As Of Date If Specified In Layout in the Web client.
• If this checkbox is selected, the As of Date for Trees specified in layout definition is
overridden at the time of Report Request.
• If this checkbox is deselected, the As of Date for Trees specified in layout definition is
used.
• If the As of Date for a Tree is not specified during the time of layout definition and this
check box is deselected, the As of Date for the Tree is used from Report Request.
See Also
See Also
See Also
Note. DrillToPIA and nVisionDrill VSTO add-ins do not coexist. You can use only one add-in
at a time.
See Also
Query
This section discusses enhancements made in the area of Query, including:
• Ability to develop in-tree criteria prompts.
See Also
The design of the Scheduled Query page output type will include the Email option as one of
the options in the current Type drop-down list. Changes are also made to the System
Process Request page for scheduling Application Engine programs.
See Also
See Also
See Also
Security Join Optimizer Select this option to enable this query to join once to the first security record.
• If this is a non-self join (same security tables) or a self join, the query joins
the security table once.
• If this is a non-self join with different security tables, the query joins security
table multiple times using the Inner Join logic and the Security Join
Optimizer option is not used.
Clear this option to enable this query to join mutliple times to the security record.
• If this is a non-self join with same security tables or a self join, the query
joins security table multiple times using the Inner Join logic.
• If this is a non-self join with different security tables, the query joins security
table multiple times using the Inner Join logic and the Security Join
Optimizer option is not used.
Note: If you perform Left Outer Joins with security record, the Security Join
Optimizer setting is applied using the same concepts.
See Also
Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Query, “Creating and Running Simple
Queries,” Creating New Queries, Viewing and Editing Query Properties
• Component Interfaces.
• Multichannel Framework.
Integration Broker
This section covers the new features and changes for Integration Broker, including:
• Integration Broker PeopleBooks.
• Integration gateways.
• Messages.
• Message schemas.
• Web services.
• WSDL documents.
• Transformations.
The “Data Dependencies and Relationships When Copying Data between Databases”
appendix in the PeopleSoft Integration Broker PeopleBook has been removed. The content
from the appendix has been merged into the new “Copying Integration Metadata between
PeopleSoft Databases” chapter.
See Also
See Also
www.oracle.com
iWay SOAPSwitch
Beginning with this release, iWay SOAPswitch no longer ships with PeopleTools.
For integrations with third-party systems, use the PeopleSoft Integration Broker services-
oriented architecture.
The “Using the ERP Connectors” chapter in PeopleBooks has been removed.
See Also
Integration Gateways
This section describes enhancements related to PeopleSoft Integration Broker integration
gateways.
Property Description
secureFileKeystorePath Enter the full path and file name of the gateway keystore
file, which is located in the web server directory structure.
The path is <PIA_HOME>\webserv\<DOMAIN>\keystore.
secureFileKeystorePasswd Enter the keystore password. The default value is password.
This password must be encrypted.
See Enterprise PeopleTools 8.50 PeopleBook: Integration
Broker Administration, “Managing Integration Gateways,”
Encrypting Passwords
See Also
See Also
See Also
WS-Addressing
The following PeopleCode properties have been added to the IBInfo PeopleCode object:
• &MSG.IBInfo.WSA_To;
Use this property to specify the WS-Addressing destination for the message. The
WS-Addressing destination is defined as a string.
• &MSG.IBInfo.WSA_Action;
Use this property to specify the Web Services Addressing (WS-Addressing)
action for the message. The WS-Addressing action is defined as a string.
&MSG.IBInfo.WSA_FaultTo;
Use this property to specify the WS-Addressing fault end point for the message.
The WS-Addressing fault end point is defined as a string.
If this property is not null, a message ID (the WSA_MessageID property) must
also be defined.
These values will be part of the MIME header section sent to the integration gateway. The integration
gateway will add these values to the SOAP headers accordingly. For inbound requests, the system
extracts these parameters from the SOAP header and places them in the MIME content section before
the request is sent to the application server.
See Also
See Also
See Also
See Also
Messages
This section describes enhancements for managing messages.
• Message aliases.
• Record aliases.
• Field aliases.
See Also
Beginning with this release, when you search for a message in the Messages component, the
system displays the message type as part of the search results.
See Also
A message Type dropdown list box has been added to the Messages component to facilitate
searching for and adding new message definitions to the database.
The Type dropdown list box appears on the Find an Existing Value tab and the Add a New
Value tab in the Messages component.
When you use the Find an Existing Value tab to search for an existing message definition,
you have the option to use the Type field to narrow your search. When using the Add a New
Value tab to add a new message definition to the system, you must select a message type
from the list. Doing so determines the subsequent page that appears and that you use to
define the message.
The message types that display in the Type dropdown list box are:
• Container. Select this value to add a container message to the system.
• Part Nonrowset. Select this value to add a nonrowset-based message part to the system.
• Part Rowset. Select this value to add a rowset-based message part to the system.
See Also
There are now three options for viewing the structure of rowset-based messages:
1. View the entire message structure.
When you access a rowset-based message in the Messages-Message Definitions page,
the existing default option displays all records, subrecords, and record fields (included
and excluded) for a message definition in tree format. You can expand and collapse the
tree to view the structure of the message.
2. View only the records in the message structure.
A new View Records Only link has been added to the Messages-Message Definitions
page. When you click the link the Records Only page appears and displays only the
records and subrecords in the message structure.
See Also
Warning! Turning compression off can negatively impact system performance when
transporting synchronous messages greater than 1 MB. As a result, you should turn off
compression only during integration development and testing.
Note. This setting does not affect the compression of messages that the integration gateway
sends using its target connectors.
See Also
Future-Dated Publications
A property has been added to the IBInfo object called FuturePublicationDateTime. The
property is for use with asynchronous transactions. The datetime of this field is used by
PeopleSoft Integration Broker to determine when an actual publish of the transaction is to
occur.
The signature for this property is:
• &MSG.IBInfo.FuturePublicationDateTime;
See Also
Message Parts
Modifying Part Messages
In previous releases you could not modify a part message if it was referenced in another
message. For PeopleTools 8.50 this restriction has been removed. You can now make
changes to a message part that is referenced in another part or subpart, as long as the
message part is not in the runtime tables, has not been exported as WSDL, or is a restricted
message.
See Also
PeopleSoft Integration Broker enables you to reuse message parts by referencing another
message part or by copying another message part.
You can reuse only rowset-based message parts.
You cannot reuse message parts at Level 0.
Message Reuse by Reference
See Also
The Message Definitions page features a new Message Part Default Indicator field that
appears when you select or define a rowset-based message part.
When you check the box, XML that has a value of 0 (zero) passed in an integer field, when
serialized to a rowset, causes the IsChanged property flag on the field to set to True.
By default an integer field has a value of 0. So if a 0 or <blank> is passed in a field, the end
result is a zero when accessing the field via the rowset. Now, if you check the Message Part
Default Indicator box the IsChanged property on such a field is set to True, meaning that a 0
(zero) was passed in the field.
See Also
You can now use the Size property of the Message object to obtain the actual size of the
rowset message parts within a container message.
See Also
Container Messages
Adding and Getting Container Messages Attributes
You can add attributes to container messages that contain rowset-based message parts to
provide integration partners with data and information, without adding the information to the
message definition.
To add attributes to a container message, you first define the attribute name, length, and
required flag in the container message definition in the PeopleSoft Pure Internet Architecture.
This information appears in generated container message schema. At runtime the attributes
appear at the root level of the generated XML. Next you use PeopleCode to populate the
attribute values using the IBInfo object. At runtime, PeopleSoft Integration Broker validates
the attribute values against the lengths you defined in the container message definition.
PeopleSoft provides a number of IBInfo object methods to get attributes from container
messages.
See Also
Beginning with this release you can pass more than one row of data on the Level 0 records in
container messages. As a result, the Maximum Occurs field on the Messages- Message
Definitions page is no longer read-only when a container message is defined with multiple
rowset-based part messages.
You can now modify the Maximum occurs field to specify the maximum number of level 0
rows in any given message part to include in the container message.
See Also
Argument Description
DataChunkCount The total number of data chunks or segments that comprise the message.
DataChunk Indicates the number of the data chunk or message segment that you are
sending.
For example, if there are a total of seven data chunks in the message,
and the current segment is the third chunk, the DataChunk value for the
current message is 3.
See Also
Message Schemas
This section describes enhancements for working with and managing XML message
schemas in PeopleSoft Integration Broker.
PeopleSoft Integration Broker now automatically generates message schema for rowset-
based messages at save time. As a result, you do not need to navigate to the Schema tab
and build the message schema.
The Schema tab is still available for viewing message schema, for building schemas for
rowset-based messages that may have been imported or upgraded without schema, and for
building schemas for nonrowset-based messages.
See Also
In previous releases the Add Schema button on the Messages – Schema page was disabled
if a schema had already been added to a nonrowset-based message and the message was
referenced in a runtime table.
You are now able to add message schemas for nonrowset-based messages referenced in
runtime tables.
The Add Schema button is enabled regardless if the message is referenced in a runtime
table.
See Also
Message data that is used to define services can have actual database record and field
names in the generated message schema. PeopleSoft Integration Broker provides an option
where you can exclude descriptions in generated message schemas to that sensitive
information is not exposed in generated schema.
The Messages–Message Definitions page features an Exclude Descriptions in Schema box
that enables you to suppress descriptions in generated schema.
See Also
When schema is generated for rowset-based messages, by default the system uses the
namespace value defined on the Service Configuration page. Beginning with this release you
can override the default value and enter a different value.
When working with rowset-based messages a new Include Namespace field appears on the
Messages – Message Definitions page.
When you check the box and save the page, a Namespace field appears on the Messages –
Schema page, where you can enter a namespace value.
PeopleSoft Integration Broker enables you to suppress empty XML tags in message schema
of rowset-based messages.
The Messages-Message Definition page features a Suppress Empty XML Tags check box.
When you select this box, message schema generated for the message will not include any
XML tags that contain empty or Null values.
See Also
Choosing the Number of Level 0 Rows to Include in Generated XML Message Schema
When generating XML message schema you can choose to include a single level 0 row in
the generated schema or all level 0 rows in the generated schema.
The Messages-Message Definitions page features a Single Level 0 Row checkbox. When
you select this box, PeopleSoft Integration Broker includes a single level 0 row in the XML
message schema. If this box is not selected, then the system includes all level 0 rows in the
message in the generated schema.
By default the Single Level 0 Row checkbox is not selected.
See Also
See Also
See Also
See Also
See Also
As in previous releases, the name of the inbound service operation must be specified in the
External Alias field on the routing definition of each service operation that you are invoking on
the receiving system.
See Also
See Also
See Also
Handler Descriptions
On the Service Operations-Handlers Detail page, by default the system populates the
Description field with the service operation name.
See Also
See Also
• ClearAEAttributes
• DeleteAEAttribute
• GetAEAttributeName
• GetAEAttributeValue
• GetNumberofAEAttributes
• GetTransactionIDforAE
• InsertAEResponseAttributes
See the PeopleCode API Reference PeopleBook for more information about these methods.
See Also
Beginning with this release the bulk load handlers are able to process asynchronous
nonrowset-based messages and container messages that have asynchronous rowset-based
message parts. In earlier releases, the bulk load handlers were able to process rowset-based
messages only.
When working with nonrowset-based messages, PeopleSoft Integration Broker provides a
data tree structure, like that in the Messages component, to add a data structure to define the
message content, thereby allowing non-PeopleSoft data to map to the records and fields in
the database.
In addition, PeopleSoft Integration Broker provides an optional transaction rollback feature
that enables you to rollback the database to the pre-bulk insert state if needed.
See Also
New System Audit Query to Identify Bulk Load Handlers Referencing Invalid Message
Objects
See Also
Routing Description
On the Routings – Routings Definition page, if you do not enter a description in the
Description field, the value defaults to the name of the service operation associated with the
routing definition upon save.
See Also,
See Also
See Also
See Also
Content-Based Routings
Several methods have been added to the IBInfo PeopleCode object to enable content-based
routing of service operations when using the OnRouteSend and OnSend events.
Using these attributes can lead to significant performance improvement, since Rowset or
Xmldoc objects do not have to be serialized and subsequently loaded into memory and
traversed to retrieve applicable data.
Attributes used for content-based routing are only applicable for the system that is setting the
attributes; the attributes are not part of the payload that gets sent to the target system. Thus,
if on the source system attributes are set as part of a publish, then you can read these
attributes in OnRouteSend and OnSend IB events. However, the target system will not be
able to view these attributes on any Integration Broker event run on the target system.
The following methods are available in the IBInfo PeopleCode object to get/set data used for
content-based routing determination.
• &Integer = &MSG.IBInfo.GetNumberOfAttributes();
Gets the number of attributes.
• &MSG.IBInfo.ClearAttributes();
Deletes all attributes in the IBInfo object.
See Also
See Also
The following example shows a routing definition in graphical format for an asynchronous
service operation:
As an example, if you click the Activate Operation Version link in the previous example, the
system locates the inactive service operation associated with the routing definition, activates
it, and displays the following message:
Message indicating that the service operation has been activated for the routing
definition.
You can click the OK button to return to other items to activate.
See Also
See Also
See Also
See Also
See Also
See Also
See Also
See Also
Web Services
This section describes enhancements for working with and managing web services.
See Also
See Also
WSDL Documents
This section describes enhancements for working with and managing WSDL documents in
PeopleSoft Integration Broker.
Integration Broker provides a new Clear WSDL Export Status page, which enables you to
clear the flag.
• Regenerate the WSDL on the new database using the Provide Web Service wizard.
See Also
PeopleSoft Integration Broker enables you to enforce record and field aliases in generated
WSDL. The Service Configuration page features a WSDL Generation Alias Check dropdown
list that enable you to set a system check level for aliases on message definition records and
fields.
You can set the following check levels:
See Also
Transformations
This section describes enhancements related to transformations.
For Oracle XSL Mapper to function, the JDeveloper installation location and classpath must
be specified in the PeopleSoft system in the PeopleSoft Configuration Manager.
Beginning with this release, after you enter the JDeveloper installation location, the
PeopleSoft system autodetects the classpath information and automatically populates the
information in PeopleSoft Configuration Manager.
See Also
• %TransformData.rejectTransform
%TransformData.routingDefnName
%TransformData.rejectTransform
Situations may arise when you may want to terminate a transaction. For example, you may
not want a transaction published to a specific node.
Using the %TransformData.rejectTransform property (and the %IB_Transform_Rejected
built-in function), you can terminate asynchronous transactions based on content data.
You set this property in a PeopleSoft Application Engine transform program as follows:
%TransformData.rejectTransform = %IB_Transform_Rejected;
See Also
See Also
See Also
WS-Security
This section describes enhancements to PeopleSoft’s implementation of WS-Security as it
pertains to PeopleSoft Integration Broker.
PeopleSoft Integration Broker now supports implementing inbound and outbound WS-
Security using Security Assertion Markup Language (SAML) tokens.
See Also
The Nodes - WS Security page (IB_NODESECURITY enables you to select from three levels
of encryption when you are encrypting an outbound service operation.
The Nodes - WS Security page (IB_NODESECURITY) features an Encrypt Level dropdown
list that contains the following values:
• All. This option encrypts the entire message including the message header and body.
See Also
See Also
You can override node-level WS Security settings on individual routing definitions for
outbound request and response messages on routing definitions. The security settings that
you can override are the same as those that appear on the Nodes-WS Security page.
See Also
You can implement WS Security on service operations you consume using the Consume
Web Service Wizard.
When using the Consume Services wizard, there is an option to use the default pre-defined
WSDL_NODE node or use another existing node as the receiving node for the consumed
service operations. PeopleBooks documents the action to take to implement WS Security on
consumed services depending on which of these nodes you are using.
See Also
See Also
See Also
• User invoking a service operation has different permissions than specified on the service
operation on the source node.
See Also
Domain Failover
General Domain Failover
Beginning with this release of PeopleTools if a failover domain becomes inactive the system
attempts failover to the highest priority domain. If it is unable to do so, the next domain
prioritized becomes the active domain.
As an example, consider an integration system with the domains and failover priorities shown
in the following table:
In this integration system if Domain A fails, the system will failover to Domain B. If Domain B
later fails, the system attempts to failover back to Domain A. If it is unable to do so, the
system will failover to Domain C.
In previous releases, if a failover domain became inactive, the system would failover to the
next prioritized domain. Given the previous example, if Domain A failed, the system would
failover to Domain B. If Domain B later failed, the system would failover to Domain C.
See Also
In dynamic slave failover, if the dynamic slave fails, the system generates and email
notification and the dynamic slave becomes inactive. The system does not failover to find
another dynamic slave.
Failover on the primary system has to occur for a dynamic slave to automatically go into
effect.
See Also
Template slaves enable you to dynamically add slave domains without performing any
configuration changes in PSADMIN.
When you create a template slave domain you import a domain configuration and save it as a
template for the slave domain. This process creates a static slave domain that uses all of the
pub/sub processes and queue lists configured for the domain that you import. If dedicated
servers are configured for the domain that you import, they are imported and available on the
slave domain. After you import a domain configuration and save it as a slave domain, you
can add or remove dispatcher queues from the slave domain as needed.
You import the domain configuration to use as a template slave using a new Import IB Master
Configuration menu in PSADMIN. You can import a configuration from an application domain
or from a file.
The import process merges the domain configuration with the new template slave domain
and creates the new configuration and loads it on the application server. Upon completion,
the PeopleSoft Domain Administration menu appears, where you may boot the template
slave domain, configure the template slave domain or perform other administrative tasks.
See Also
You can implement master-slave load balancing on the integration system to compensate for
processing capabilities of various machines on which master domains and slave domains
run.
As an example, you might have a domain on machine that is also running the PeopleSoft
Pure Internet Architecture. In this case, you could configure master-slave load balancing such
that the machine that is running the PeopleSoft Pure Internet Architecture processes fewer
requests than other machines on which domains reside.
Another example is a situation where the machines on which you are running domains have
different processing capabilities due to the hardware installed in them. In this situation you
can configure the machines with the most process power to process the greater number of
requests.
To configure master-slave load balancing use the Master/Slave Load Balance page. The
page enables you to assign a weight between1 and 10 to each domain to distribute request
processing. A domain assigned a weighted value of 1 processes the fewest number of
requests; a domain assigned a weighted value of 10 processes the greatest number of
requests.
See Also
PeopleSoft Integration Broker enables you to defer request processing on master domain to
slave domains that are available for processing. Configuring deferred master processing
enables you to free processing resources on the master domain machine due to hardware or
processing power limitations, or so it can run other processes.
The Master/Slave Load Balance page features a Master Processing Status dropdown list box
where you set the processing status for the master domain.
See Also
When serial recycle for pub/sub process handlers is enabled, the system recycles process
handlers (within a group) on a serial basis–one after another–to allow processing to continue
uninterrupted. If serial recycling is disabled, all pub/sub process handlers recycle at once,
which can cause throughput to come to a standstill.
You use the Serial Recycle parameter in the psappsrv.cfg file to enable and disable this
feature.
See Also
PeopleSoft Integration Broker enables you to recycle pub/sub process handlers based on
memory growth in cache.
You use the Percentage of Memory Growth parameter in the psappsrv.cfg file to specify that
the system recycle pub/sub process handlers when memory has grown by a percent value
that you specify. The system checks to see if the percentage criterion is met after processing
a specified number of requests.
By default the Percentage of Memory Growth parameter is disabled.
See Also
The pages display information from a transactional view and enable you to successively drill
down on specific messaging system components and processes to view more detailed data.
The following graphic shows a sample of statistics that display for outbound synchronous
transactions in the messaging system.
See Also
See Also
See Also
See Also
See Also
See Also
A File Encoding field has been added to several PeopleSoft Integration Broker utilities.
This field appears in the following utilities:
• Handler Tester Utility
When uploading an XML file for use with one of these utilities, use the field to select the type
of encoding of the file, thereby allowing PeopleSoft Integration Broker to correctly parse the
XML.
The encoding options you can select are UTF-8, UTF-16, and non-Unicode.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, “Using the
Handler Tester Utility”
Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, “Using the
Service Operation Tester Utility”
Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, “Using the
Schema Tester Utility”
The Handler Tester Utility and the new Service Operation Tester Utility feature a Container
Message Builder page which enables you to build and populate rowset-based messages
within container messages.
The user-interface for building and populating rowset-based messages from within these
utilities is identical to that used in the Messages component for creating and modifying
rowset-based messages.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, “Using the
Handler Tester Utility”
Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, “Using the
Service Operation Tester Utility”
• Asynchronous request-response.
• Async-to-synch.
• Synchronous.
Similar to the Handler Tester utility, the Service Operation utility enables you to populate
rowset-based or nonrowset-based messages to include in the service operation. You can
populate message data by uploading XML content, manually inputing XML data, or manually
inputing record and fields values (for rowset-based messages). You can also specify
PSCAMA record values and audit actions.
The utility also enables you to override target connectors and specify target connector
properties.
When you invoke asynchronous service operations, the system uses the Publish method.
When you invoke synchronous service operations, the system uses the SynchRequest
method.
If the invocation is successful, the system displays a success message along with a
transaction ID. You can use the transaction ID to track the transaction in the Service
Operations Monitor. If the invocation does not run successfully, an error message displays.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, “Using the
Service Operation Tester Utility”
For service operations that contain rowset-based messages, you can now assign PSCAMA
record values and audit actions to Level 0 records. In addition, you can assign PSCAMA
audit actions to Level 1 and greater records.
This functionality has been added to the Select an Action page in the Handler Tester utility.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, “Using the
Handler Tester Utility”
The version numbers were removed and the names are now:
• Integration Broker (MIME)
• JMS Project
In previous releases the 8.48 reference indicated that you were creating a project for an
integration running on PeopleTools 8.48 or later. PeopleTools 8.48 is when PeopleSoft
Integration Broker moved to a services-oriented architecture (SOA).
You can use Send Master to create projects for integration created on the pre-PeopleTools
8.48 framework. PeopleBooks discusses how to set Send Master to test pre-PeopleTools
8.48 integrations.
Unless you start Send Master in Pre-PeopleTools 8.48 mode, all projects are created for
Integration Broker’s services-oriented architecture found in PeopleTools 8.48 and later
releases.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, “Using Send
Master,” Starting Send Master, Starting Send Master in Pre-PeopleTools 8.48 Mode
See Also
Enterprise PeopleTools 8.50 PeopleBook: Integration Broker Testing Utilities and Tools,
“Using the Generate SOAP Template Utility”
• Worklist feeds
• Query feeds.
Overview
Feeds are popularized by websites like news, wikis and blogs. The content updates on these
sites are subscribed by the user using a feed reader which polls the website with a specific
URL provided by the website. With the PeopleSoft Feed Publishing Framework, you can
develop and publish feeds from any PeopleSoft or non-PeopleSoft data. Then with the
delivered user interfaces, users can find and subscribe to your feeds.
The Feed Publishing Framework provides:
• A set of APIs and code samples to assist application developers in creating new type of
feeds and integrating them with existing features.
• Unified interfaces for content owners and administrative users to create, configure, and
maintain feed definitions of various types, such as query feeds, worklist feeds, and
Integration Broker generic message feeds.
• Interfaces for end users to discover related feeds and search feed definitions.
With the PeopleSoft Feed Publishing Framework, you can develop and publish feeds from
any PeopleSoft or non-PeopleSoft data. Then with the delivered user interfaces, users can
find and subscribe to your feeds.
My Feeds
Using My Feeds pages, a user can search and discover all the feeds that are available, and
subscribe to the desired feeds. The user can also export all the feeds of their choice to an
OPML file, which can be imported into the feed reader of their choice, to subscribe to these
feeds.
The feeds list is filtered based on security settings.
Worklist Feeds
The Worklist feed data type enables workflow administrators to expose worklists as feeds.
Query Feeds
The Query feed data type enables query administrators to expose query definitions as feeds.
Query feeds include the Mapping Builder, which enables you to map feed entry attributes to
templates. A template is a string, which can have bind variables enclosed inside %.
Component Interfaces
This section discusses changes and enhancements for Component Interfaces, including:
• Excel to Component Interfaces Utility.
• Template names.
• Translations.
See Also
See Also
Template Names
The version of Microsoft Excel that you are using in conjunction with the Excel to CI utility
determines the Excel to CI template that you must use. The follow table lists the template to
use based on your version of Microsoft Excel:
Note that users for Microsoft Excel 2000 and Microsoft Excel 2003 use the same template.
See Also
Translations
Beginning with this release, standard templates are delivered for the Excel to CI utility and
translations are provided in macros.
The macros are located in subfolders in the PS_HOME\Excel directory. To apply a translation
macro you must specify it in Microsoft Excel.
Translated elements include labels, headers and strings.
See Also
See Also
See Also
See Also
MultiChannel Framework
This section describes the new features and changes for MultiChannel Framework, including:
• CTI Screen Popup
• Sample Pages
Sample Pages
The 3rd party configuration sample page has been enhanced to provide the ability to supply
reason codes in a prompt window for “Reject” operation for email, chat and generic tasks.
The “Agent-to-Agent” chat feature in 3rd party routing has been enhanced to allow an agent to
forward a task to the same queue.
See Also
• Alter Analyzer.
When defining or modifying a template you can now choose the step type of
ProcessScheduler.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Change Assistant, “Modifying Step Properties and
Parameters”
Enterprise PeopleTools 8.50 PeopleBook: Change Assistant, Configuring Change Assistant
for Upgrades, “Configuring the Upgrade Environment”
• Target
With PeopleTools 8.50 a new database type, Production, has been added to define within
your upgrade environment. In some cases, steps may need to be run against your Production
database. The Production database orientation is valid for the following step types:
• ApplicationEngine
• DataMoverUser
• DataMoverBootstrap
• ManualStop
• SQLCommand
• SQRReport
See Also
Enterprise PeopleTools 8.50 PeopleBook: Change Assistant, “Modifying Step Properties and
Parameters”
Enterprise PeopleTools 8.50 PeopleBook: Change Assistant, “Configuring Change Assistant
for Upgrades,” Configuring the Upgrade Environment
See Also
The Generate New Template option enables you to generate a Change Assistant template
and ignore any manual changes made to an existing template.
The Merge Existing Template option enables you to navigate to an existing Change
Assistant template and merge any modifications present in the existing template that are not
present in the new template.
See Also
See Also
In some cases, change packages can become superseded by a newer change package.
When a change package becomes obsolete, the page on the updates website for the change
package remains posted, however, the change package itself is removed from that page. The
page for the obsolete change package displays a link to the page containing the posted
change package that supersedes it.
When you download change packages manually, if you arrive at the page of an obsolete
change package, you click the link taking you to the superseding change package and
download the appropriate change package.
When you automatically download change packages through Change Assistant, the system
is designed to download all the prerequisite and post-requisite change packages you need.
Previously, when downloading updates automatically using Change Assistant, the update
gateway did not properly notify you of superseding prerequisite and post-requisite change
packages, nor did it automatically download the superseding change packages. This resulted
in an incomplete set of change packages that one would assume to be complete.
Now, when downloading updates using Change Assistant, the update gateway has been
enhanced to verify the current set of pre and post-requisites, including superseded change
packages. Change Assistant then downloads automatically the current set of pre and post-
requisites and superseding change packages.
See Also
See Also
Note. This applies only when both Change Assistant and the PeopleTools version are at
least at the PeopleTools 8.50 level.
See Also
See Also
See Also
Application Designer: Report Filter tab on the Upgrade Options dialog box
The –FLTR command line parameter follows this syntax:
-FLTR XXXXX XXXXX XXXXX XXXXX XXXXX
Where each X corresponds to a specific checkbox on the Report Filter tab, moving left to
right, top to bottom, beginning with the top, left hand corner (Source, Absent/Target, Absent).
The value of X can be either a 0 (not selected) or 1 (selected).
For example, the following command line parameter represents the equivalent selections on
the Report Filter tab above.
–FLTR 00000 00011 00011 01111 01111
See Also
See Also
Alter Analyzer
PeopleTools is providing a new utility named Alter Analyzer that enables you to compare the
metadata between databases running different versions of PeopleTools. By running a
provided Application Engine program, you load selected metadata information from your
source database into your target database. Then you run another provided Application
Engine program to compare the source and target metadata.
The results of the comparison are stored in the Alter Repository, a set of predefined tables,
that you can query and run reports against to gain further insight into your upgrades and alter
operations.
See Also
See Also
PeopleBooks Enhancements
With Enterprise PeopleTools 8.50, Oracle provides a new version of PeopleBooks.
Deprecated Documentation
Oracle no longer ships documentation for certain products used primarily in previous
PeopleTools releases.
For Business Interlink documentation, refer to the PeopleTools 8.46 Business Interlinks
PeopleBook posted on My Oracle Support in the following location:
The Upgrade Assistant tool is no longer shipped or supported, so the Upgrade Assistant
PeopleBook is not included with the PeopleTools 8.50 PeopleBooks. For upgrades and
updates, use Change Assistant and refer to the Change Assistant PeopleBook for
documentation.