Professional Documents
Culture Documents
50
September 2009
Release Notes
Contents
PeopleTools Enterprise PeopleTools 8.50 Release Notes Preface ..................................... 1 PeopleSoft Release Information Publications .................................................................... 1 Release Value Proposition ............................................................................................. 1 Prerelease Notes ............................................................................................................ 1 Release Notes ................................................................................................................ 2 Additional Information.........................................................................................................2 PeopleSoft Enterprise PeopleTools 8.50 Value Proposition ................................................. 1 Before You Begin................................................................................................................... 1 Platform Support Enhancements ........................................................................................... 2 Whats Added and Dropped From Support ........................................................................ 2 Deprecation Notice For PeopleTools Mobile Technology and Mobile Agent..................... 4 Dropping Support for HP-UX PA-RISC For IBM DB2 Database Environments ................ 4 Dropping Support for Oracle Application Server ................................................................ 4 JRE Support ....................................................................................................................... 4 BusinessObjects Enterprise Support ................................................................................. 5 System Administration Enhancements .................................................................................. 6 Installation Changes...........................................................................................................6 PeopleSoft Internet Architecture Installation Location.................................................... 6 Installation Programs ...................................................................................................... 7 PeopleTools Running on Windows................................................................................. 8 Verity Installation ............................................................................................................8 Oracle Tuxedo Environment Variables in psconfig.sh.................................................... 8 Oracle Configuration Manager Installation ..................................................................... 9 PeopleSoft Configuration Manager ................................................................................ 9 Decoupled PS_HOME Binary and Configuration Files .................................................... 10 Search Server................................................................................................................... 12 Search Server Failover ................................................................................................. 12 Increased Support for Search Server (Type-3) Configurations .................................... 13 HP Itanium Support ...................................................................................................... 13 PSADMIN Search Domain Administration Menu.......................................................... 13 Windows Service Now Includes Search Server Domains ............................................ 13
Release Notes
Search Server Configuration File Changes .................................................................. 14 PSADMIN ......................................................................................................................... 14 Spawning ...................................................................................................................... 14 Number of PSAPPSRV Processes in Delivered Templates......................................... 15 Windows Service .......................................................................................................... 15 Maximum Open Cursors............................................................................................... 15 JavaVM Options ........................................................................................................... 15 PeopleSoft Environment Management Plug-in for Oracle Enterprise Manager .............. 16 PeopleSoft Environment Management Plug-in Documentation ................................... 16 Oracle Enterprise Manager 10.2.0.5 Certification ........................................................ 16 Process Monitor Integration.......................................................................................... 16 Usability Enhancements ............................................................................................... 17 Security Enhancements................................................................................................ 18 Loading Shared Cache Performance Improvements ....................................................... 18 PeopleTools Security ....................................................................................................... 20 User Profile Synchronization ........................................................................................ 20 SAML support for Web Services Security .................................................................... 20 Oracle Access Manager Integration ............................................................................. 20 PeopleSoft Encryption Technology Changes ............................................................... 20 LDAP Library Changes ................................................................................................. 21 Oracle Database Enhancements ..................................................................................... 21 Optimize Database CPU Usage with Oracle Control Groups ...................................... 22 Support for Oracle Transparent Data Encryption ......................................................... 23 Enhanced MODULE and ACTION Monitoring Information .......................................... 23 Oracle Database Vault Support.................................................................................... 24 Enhanced User ID Monitoring Information ................................................................... 24 Increase in Oracle Long Object (LOB) File Size Limit.................................................. 25 Increase in Oracle Minimum Number of OPEN_CURSORS........................................ 25 FIRST_ROWS Hint Feature No Longer Used .............................................................. 25 Oracle 11g Case-Sensitive User IDs............................................................................ 25 Microsoft SQL Server Enhancements.............................................................................. 25 Access ID......................................................................................................................25 SQL Server 2008 .......................................................................................................... 26 IBM DB2 Enhancements .................................................................................................. 26
Release Notes
DB2 LUW AUTORESIZE.............................................................................................. 26 DB2 z/OS Database Level Auditing Changes .............................................................. 27 Increased Monitoring Information ................................................................................. 28 Data Mover ....................................................................................................................... 28 IMPORT Command Modifications ................................................................................ 29 Data Mover Environment Variable Modifications.......................................................... 29 PeopleSoft Performance Monitor ..................................................................................... 30 Save and Ping PPM Button .......................................................................................... 30 PPM Console Display and Security.............................................................................. 31 General System Administration Enhancements............................................................... 32 Tuxedo Log Directory Character Limit.......................................................................... 32 Timeout Settings........................................................................................................... 32 Jolt ................................................................................................................................ 33 Signon Trace Link......................................................................................................... 33 IDDA Logging ............................................................................................................... 34 WebLogic Session Cookie Name Changes.................................................................. 34 SYSAUDIT Additions .................................................................................................... 34 Authentication Timeout Setting..................................................................................... 35 URL PROPERTIES PAGE ........................................................................................... 35 Development Tools Enhancements..................................................................................... 36 User Interface ................................................................................................................... 37 Asynchronous JavaScript and XML.............................................................................. 37 Partial Page Refreshes................................................................................................. 37 Modal Prompt Pages and Modal Alert Dialog Boxes ................................................... 37 Modal Grids and Long Edit Boxes ................................................................................ 38 Menu Navigation........................................................................................................... 38 Floating Drop-Down Navigation.................................................................................... 38 Favorites Menu Enhancements.................................................................................... 40 Type Ahead ..................................................................................................................41 Processing Icon Changes............................................................................................. 42 Search Page Enhancements ........................................................................................ 42 Style Sheet Modification ............................................................................................... 43 Cascading Style Sheet (CSS) Based Tabs .................................................................. 43 Application Designer ........................................................................................................ 44
Release Notes
Radio Button Label Changes........................................................................................ 44 Free Form Stylesheets ................................................................................................. 44 Command Line Password Prompt................................................................................ 45 Summary Attribute for Tables in Pages........................................................................ 45 Active Hyperlinks on Display Only Pages..................................................................... 45 Scrollable Grid Layout (Grid Enhancements) ............................................................... 46 Image Definition Changes ............................................................................................ 48 Integrated Rich Text Editor ........................................................................................... 48 Long Character Field Limit............................................................................................ 49 PeopleTools Portal Technologies .................................................................................... 50 Related Content Framework......................................................................................... 50 Pagelet Wizard Enhancements .................................................................................... 51 Pagelet Drag and Drop ................................................................................................. 51 Pagelet Search ............................................................................................................. 52 Pagelet Help ................................................................................................................. 52 OBIEE to PeopleSoft URL Integration.......................................................................... 52 OBIEE Report Integration ............................................................................................. 52 PeopleCode...................................................................................................................... 53 Search Events for Prompt Dialogs ............................................................................... 53 PeopleCode Debugger ................................................................................................. 54 PeopleCode Editor........................................................................................................ 54 PeopleCode Functions ................................................................................................. 54 File Processing ............................................................................................................. 55 Meta-SQL...................................................................................................................... 55 Charting ........................................................................................................................ 55 PeopleCode API ........................................................................................................... 58 Global Technology ........................................................................................................... 67 Changes to Supported Character Sets......................................................................... 67 Changes to the Swap Audit Report .............................................................................. 68 New PeopleSoft Language Codes ............................................................................... 68 Non-ASCII Characters in File Names Uploaded to FTP Servers Prior to 8.50 ............ 69 PeopleSoft Hot Keys Do Not Function As Expected on a non-U.S. Keyboard ............ 69 Time Zone Data ............................................................................................................ 69 Translating Application Definitions ............................................................................... 70
Release Notes
Updated Font Support .................................................................................................. 70 Using Extended Japanese Characters ......................................................................... 70 Reporting and Analytic Tools ............................................................................................... 71 Process Scheduler ........................................................................................................... 71 Increase Process Instance and Report IDs .................................................................. 72 Viewing Limitations ....................................................................................................... 72 Report Distribution By Role .......................................................................................... 72 Retention Days ............................................................................................................. 72 Data Mover Scripts to Delete Reports .......................................................................... 73 Renaming Database in Process Request Data Tables ................................................ 73 New Process Category LOADCACHE ......................................................................... 74 Runtime Parameters..................................................................................................... 74 Reporting Console ........................................................................................................ 74 Process Scheduler Web Service .................................................................................. 76 XML Publisher ..................................................................................................................76 Descriptive Names........................................................................................................ 77 Deprecated Data Sources ............................................................................................ 77 Deprecated Schema Files ............................................................................................ 77 Connected Query Data Source .................................................................................... 78 Global Properties Settings ............................................................................................ 78 Performance Enhancements ........................................................................................ 79 PDF Full Path Mapping................................................................................................. 79 Alternate XML Preview ................................................................................................. 79 Iterative Template Design............................................................................................. 79 Support for Email .......................................................................................................... 79 Query Access Service ...................................................................................................... 79 Connected Query ............................................................................................................. 80 Crystal Reports for PeopleSoft......................................................................................... 80 BusinessObjects Enterprise XI Release 3.1 Upgrade.................................................. 81 Crystal Reports and Crystal Report Print Engine 2008 Upgrade ................................. 81 HKEY_CURRENT_USER ............................................................................................ 81 Local Directory of crw32.exe ........................................................................................ 81 Crystal Reports 2008 Runtime Environment ................................................................ 82 Crystal Reports Concepts............................................................................................. 82
Release Notes
Crystal Reports Execution Environments ..................................................................... 83 Crystal Reports 2008 Compatibility Issues................................................................... 84 Cube Builder..................................................................................................................... 85 Oracle Smart View for Office 11.1.1.1 Upgrade ........................................................... 85 Essbase Cube Builder .................................................................................................. 85 Cube Manager.................................................................................................................. 91 Tree Manager ...................................................................................................................92 Optimization Framework .................................................................................................. 93 iLog CPLEX 11.0 Upgrade ........................................................................................... 93 PS/nVision ........................................................................................................................ 93 Accepting Tree Effective-Date When User Define Criteria........................................... 93 Supporting Not-in Criteria ............................................................................................. 95 Ability to Define the Types of Report Requests............................................................ 96 Restoring Query Prompts to Web Version of nVision .................................................. 96 Default Configuration under %PSHOME%................................................................... 96 Drilling Down PS/nVision Reports Using Web Services (nVisionDrill VSTO add-in) ... 96 Query................................................................................................................................ 97 Ability to Add an In-Tree Criteria Prompt...................................................................... 97 Ability to Email Application Engine Results .................................................................. 97 Drilling URL in PSQUERY ............................................................................................ 98 Schedule Query with In Tree Prompt ........................................................................... 98 Temp Files of the Query-to-Excel................................................................................. 98 Download Query Results to XML File........................................................................... 99 Security Join Optimizer................................................................................................. 99 Integration Tools Enhancements .......................................................................................100 Integration Broker...........................................................................................................100 Integration Broker PeopleBooks.................................................................................101 Deprecated Integration Technologies and Utilities.....................................................102 Integration Gateways..................................................................................................102 Target Connectors and Listening Connectors ............................................................104 New Managed Objects: WSDL and Message Schema..............................................104 Messages....................................................................................................................105 Message Schemas .....................................................................................................110 Services and Service Operations ...............................................................................112
Release Notes
Service Operation Handlers........................................................................................114 Service Operation Routings........................................................................................116 Service Operation Queues .........................................................................................122 Web Services..............................................................................................................122 WSDL Documents ......................................................................................................122 Transformations..........................................................................................................123 Integration Broker Security .........................................................................................125 Integrations with Oracle ESB-Based Services ...........................................................127 Integration Broker Logging, Tracing and Debugging..................................................127 Tuning Messaging System Performance....................................................................128 Integration Broker Service Operations Monitor ..........................................................130 Integration Broker Testing Tools and Utilities.............................................................134 PeopleSoft Feed Publishing Framework........................................................................138 Overview .....................................................................................................................138 My Feeds ....................................................................................................................138 Integration Broker Generic Message Feeds...............................................................138 Worklist Feeds ............................................................................................................138 Query Feeds ...............................................................................................................139 Developing New Feed Data Types.............................................................................139 Component Interfaces ....................................................................................................139 Excel to Component Interfaces Utility.........................................................................139 Viewing Log Files........................................................................................................141 MultiChannel Framework ...............................................................................................142 CTI Screen Popup ......................................................................................................142 SSL Support for Email ................................................................................................142 Sample Pages ............................................................................................................142 Web Chat Enhancement.............................................................................................142 Debug Tracer Enhancement.......................................................................................142 Virus Scanning for Email Attachments .......................................................................143 Lifecycle Management Enhancements..............................................................................144 Running Upgrade Steps With Process Scheduler .........................................................144 Additional Database Definition Available .......................................................................146 Exporting Change Assistant Templates .........................................................................147 Retaining Manual Modifications to Change Assistant Templates ..................................147
Release Notes
Automatic Merge Process for Integration Broker Projects .............................................148 Update Gateway Detects and Downloads Superseded Change Packages ..................149 Update Gateway Now Points to Oracle Metalink ...........................................................149 Creating Projects With Multiple Definition Types ...........................................................149 Deploying Files Performance Improvements .................................................................150 New Step Property: From Tools Release ....................................................................152 Review and Apply Option Added to Apply Change Packages Wizard ..........................153 #NT Step Parameter Modifications ................................................................................154 Compare Report Improvements .....................................................................................154 Command Line Option to Filter Report Output ...........................................................155 Database Name Appears on Compare Report Output...............................................156 Alter Analyzer .................................................................................................................156 Dropped Support for Upgrade Assistant ........................................................................156 PeopleBooks Enhancements.............................................................................................157 PeopleSoft Application Designer Lifecycle Management Guide....................................157 Deprecated Documentation............................................................................................157 Document Change History.................................................................................................158
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? What customizations may be affected?
Release Notes
How will an upgrade or new implementation affect other systems? How will these changes affect the organization?
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 PeopleSoft Enterprise PeopleTools Documentation Homepage on My Oracle Support (Doc ID 847882.1)
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 users experience, and increase cost effectiveness. Many of the enhancements of this release involve improving the end users 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 industrys lowest cost of ownership and improved user satisfaction. Key areas and features of PeopleTools 8.50 are: Related content Improved integration technology Greater end-user productivity Supported platforms
Release Notes
Tuxedo
Tuxedo 10gR3
Release Notes
Discontinued
Enterprise Manager
Crystal
Crystal 9 BusinessObjects Enterprise XI 2 Firefox 1.5, 2.0 Internet Explorer 6 Mozilla Netscape Safari 2.0.4, 3.0.4
Browser
JRE
Java 6
Java 4 Java 5
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 Enterprise PeopleTools 8.50 Hardware and Software Requirements My Oracle Support: Planned PeopleSoft Enterprise PeopleTools PT 8.50 Certifications (Doc ID 804670.1) My Oracle Support: PeopleSoft Enterprise PeopleTools Certifications (Doc ID 747587.1) My Oracle Support: Tech Update - Main Page (Doc ID 764222.1)
Release Notes
Dropping Support for HP-UX PA-RISC For IBM DB2 Database Environments
For PeopleTools 8.50, the HP-UX PA-RISC operating system is not supported for running the IBM DB2 database or server elements requiring connection to IBM DB2 database. This includes applications servers, Process Scheduler servers, Data Mover, and so on. If you run DB2 databases, and want to continue running your PeopleSoft elements on an HP operating system, it is recommended that you use the HP-UX Itanium operating system. Otherwise, you will need to select an operating system from the other supported options. 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.
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.
Release Notes
JRE 1.4x or JRE 1.5x is not provided or supported for PeopleTools 8.50.
Release Notes
Installation Changes
This section describes the major changes to the PeopleTools installation process, including: Installation Programs PeopleTools Running on Windows Verity Installation Oracle Tuxedo Environment Variables in psconfig.sh Oracle Configuration Manager Installation PeopleSoft Configuration Manager
Release Notes
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.
Release Notes
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 Enterprise PeopleTools 8.50 Installation for <your platform>
Release Notes
Variable $TUXDIR
Description $TUXDIR must be set to the correct Oracle Tuxedo installation directory. For example:
TUXDIR=/home/user/Oracle/tuxedo10gR3; export TUXDIR
$TUXDIR/lib
$TUXDIR/lib must be prepended to LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH, whichever is appropriate for your platform. For example:
LD_LIBRARY_PATH=$TUXDIR/lib:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH
$TUXDIR/bin
Including OCM a part of PeopleTools installer enables Oracle support representatives to analyze environment and configuration data and provide better service to customers. See Also Enterprise PeopleTools Installation for <your platform> Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, Working with Oracle Configuration Manager
Release Notes
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 Enterprise PeopleTools 8.50 Installation for your platform
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.
Release Notes
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. Operating System UNIX/Linux Windows PS_CFG_HOME Location $HOME/psft/pt/<version> %USERPROFILE%\psft\pt\<version>
After you create a domain, the domain exists under PS_CFG_HOME\appserv\<domain>. Domains can exist on the same physical machine or a different physical machine as PS_HOME. That is, multiple domains on different machines can leverage a single installation of PS_HOME installed on a location accessible through your network. Splitting the location of the server binary and configuration files provides a variety of benefits, enabling you to: Restrict write access to server binary files and domain configuration files to one user, limiting the possibility of accidental or malicious tampering with installed binaries and domain configuration. Deploy PeopleTools binaries to a single location that multiple domains can use, reducing the time and complexity involved with installations. Save significant disk space. 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
11
Release Notes
Search Server
This section discusses enhancements to the search server technology: Search server failover HP Itanium support. Edit configuration/log files menu Windows service now includes search domains.
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|stsun04:7777,SRCH_FAILOVER|st-sun05:7777 Where SRCH_PRIMARY and SRCH_FAILOVER represent the Domain ID value in the [Domain Settings] section of PSADMIN.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, Configuring Search and Building Search Indexes, Configuring a Separate Search Server (Type 3), Setting up Failover Search Domains
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.
See Also Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, Configuring Search and Building Search Indexes, Configuring a Separate Search Server (Type 3)
13
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, Configuring Search and Building Search Indexes
PSADMIN
In PeopleTools 8.50, you will notice the following changes to PSADMIN: Spawning Number of PSAPPSRV Processes in Delivered Templates Windows Service Maximum Open Cursors 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 Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, Using PSADMIN Menus, Setting up the PeopleSoft Windows Service
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.
15
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, Setting Application Server Domain Parameters, PSTOOLS Options, JavaVM Options
Release Notes
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.
17
Release Notes
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 multiuser 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.
Release Notes
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.
See Also Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration
19
Release Notes
PeopleTools Security
This section discusses the changes to PeopleTools Security, including: User Profile Synchronization. SAML support for Web Services Security. Oracle Access Manager integration. PeopleSoft Encryption Technology changes. LDAP library changes.
Release Notes
Encryption Terminology
PeopleSoft Pluggable Encryption Technology is now referred to as PeopleSoft Encryption Technology.
See Also Enterprise PeopleTools 8.50 PeopleBooks: Security Administration, Using Application Engine Programs to Encrypt and Decrypt Tables
21
Release Notes
FIRST_ROWS Hint Feature No Longer Used. Oracle 11g case-sensitive user IDs.
Release Notes
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 Enterprise PeopleTools 8:50 PeopleBook: Data Management, Administering PeopleSoft Databases on Oracle, Working With Oracle Resource Groups Oracle Database Administrators Guide, Using the Database Resource Manager
23
Release Notes
See Also Enterprise PeopleTools 8:50 PeopleBook: Data Management, Administering PeopleSoft Databases on Oracle, Monitoring PeopleSoft Database Connections
MODULE ------
CLIENT_IDENTIFIER -----------------
CLIENT_INFO ----------------QEDMO,bng2,BENG-
Enterprise PeopleTools 8:50 PeopleBook: Data Management, Administering PeopleSoft Databases on Oracle, Monitoring PeopleSoft Database Connection
Release Notes
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.
25
Release Notes
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 Additionally it is necessary to grant ALTER TRACE permissions to the ACCCESSID in order to be able to utilize different tracing capabilities available in PeopleTools. On PeopleTools 8.50 you will find the installation scripts were updated to reflect the changes above. It is important to take into consideration that utilizing these roles for the PeopleSoft ACCESSID login will restrict the ability to run administrative tasks not required for PeopleSoft applications like creating backups and restoring them, defining new server logins, modifying server settings, creating databases, dropping them, and so on. See Also Enterprise PeopleTools 8.50 Installation <for your platform> Enterprise PeopleTools 8:50 PeopleBook: Data Management, Administering PeopleSoft Databases on Microsoft SQL Server
Release Notes
CREATE TABLESPACE PTTLRG MANAGED BY DATABASE USING ( FILE '/data1/psdb2/ptdbname/PTTLRG.DBF' 18000 ) EXTENTSIZE 16 PREFETCHSIZE 48 DROPPED TABLE RECOVERY OFF; 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
27
Release Notes
When Used Used for distributed connections, which are process using DB2 Connect, such as PIA transactions and Process Scheduler servers (running on Windows or UNIX). Used for local connections, which are processes running under UNIX System Services, such as Application Engine, Process Scheduler servers (running on OS/390), Report Distribution Server, and so on.
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 Enterprise PeopleTools 8.50 PeopleBook: Data Management, Employing Database Level Auditing, Using DB2 for z/OS Trigger Information
See Also Enterprise PeopleTools 8.50 PeopleBook: Data Management, Administering PeopleSoft Databases on DB2 z/OS Enterprise PeopleTools 8.50 PeopleBook: Data Management, Administering PeopleSoft Databases on DB2 LUW
Data Mover
This section covers Data Mover enhancements, including:
Release Notes
29
Release Notes
Variable TraceFile
Release Notes
31
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Performance Monitor, Administering the Performance Monitor, Setting Global System Options
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.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, Appendix: PeopleSoft Timeout Settings, Web Server Timeouts
Jolt
This section describes changes made to Oracle Jolt, including: Jolt Failover String Jolt Session Pooling
33
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: Portal Technology, Configuring the Portal Environment, Configuring Web Profiles
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. configurable logging levels, including INFO, WARNING, SEVERE, and so on. 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 Enterprise PeopleTools 8.50 PeopleBook: System and Server Administration, Tracing, Logging, and Debugging, Enabling IDDA Logging
SYSAUDIT Additions
The following new SYSAUDIT audits have been added. SEC-31: Verifies roles contain valid user profile definitions. SEC-32: Flags any inactive roles existing in the system. SEC-34: Checks for orphaned service operations assigned in permission lists. IBRK-23: Checks operation definitions with no service relationship.
Release Notes
IBRK-24: Checks DMS Handlers referencing invalid messages. SYSLANG 16: Checks for invalid language codes assigned to users. PRCSHED-18: Checks for queued processes in tables used by Process Scheduler containing a DBNAME different than the current database name. 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. Feeds Framework Audits (FEEDS 01-10, GENERICFEED-01, WORKLISTFEED 01-05, QUERYFEED 01-03): Checks for references to nonexistent feeds framework definitions.
See Also Enterprise PeopleTools 8.50 PeopleBook: Data Management, Ensuring Data Integrity
35
Release Notes
Release Notes
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. Modal prompt pages and modal alert dialog boxes. Modal grids and long edit boxes. Menu navigation. Floating drop-down navigation. Favorites menu enhancements. Processing icon changes Search page enhancements. Style sheet modifications. Cascading Style Sheet (CSS) based tabs.
37
Release Notes
Minimize or collapse the page to the title bar. Close the page from the title bar close icon.
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.
Release Notes
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.
39
Release Notes
Note. You must run the Build Registry Search Index process to populate the search.
Release Notes
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.
41
Release Notes
Release Notes
43
Release Notes
Application Designer
This section details the modifications in Application Designer definitions, including new features and enhancements, such as: Radio button label changes. Free form stylesheets. Command line password prompt. Grid and scroll area summary attribute for tables in pages. Active hyperlinks on read-only pages. Scrollable grid layout (grid enhancements). Image definition changes. Integrated rich text editor.
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.
Release Notes
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. This is an example of a free form style sheet:
45
Release Notes
Release Notes
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.
47
Release Notes
This Grid Properties dialog box shows the Grid Layout and the Scrollbar properties on the Use tab:
Release Notes
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.
49
Release Notes
Release Notes
application upgrades or customizations. The PeopleSoft Enterprise Portal 9.1 related content services include: Related Discussion service Providing threaded discussions that groups can use to discuss topics of interest. Related Links service Providing links to external URLs or to content residing in PeopleSoft Enterprise Portalspecifically, blogs, discussions, or collaborative workspaces. Related Tags service Allowing you to characterize or bookmark transactional or business objects with terminology of your choosing, providing ease of access as well as collaborative classification of the information.
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleTools Portal Technology, "Working with Related Content Services" PeopleSoft Enterprise Portal 9.1 PeopleBook: Using Portal Features, "Understanding PeopleSoft Enterprise Portal-Delivered Related Content Services"
51
Release Notes
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.
Release Notes
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
53
Release Notes
Enterprise PeopleTools 8.50 PeopleBook: PeopleCode Developers Guide, PeopleCode and the Component Processor
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleCode Developers Guide, Debugging Your Application
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleCode Developers Guide, Using the PeopleCode Editor
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. StripOffHTMLTags strips all HTML tags in an HTML-formatted string. GetOrgChart returns a reference to an organization chart. GetRatingBoxChart returns a reference to a rating box chart.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleCode Language Reference Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Charting Classes
File Processing
The ftpunx script is deprecated as of PeopleTools 8.50. If you have made customizations to this script and need to continue to use these customizations in PeopleTools 8.50, run PS_HOME\scripts\PT_FILEATTACH850.dms.
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. The meta-SQL function %DatabaseRelease evaluates to the current database release version. 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 %ResolveMetaSQL meta-SQL function can be used in PeopleCode to return the resolved SQL from meta-SQL construct as a text string. The %GETPROGTEXT meta-SQL function will return the full text of an Application Engine PeopleCode program.
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleCode Language Reference, Meta-SQL
Charting
This section covers new charting features. Organization charts Rating box charts Interactive Gantt charts
55
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Charting Classes
Release Notes
Rating Box chart with a pop-up displaying all nodes for a rating box
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Charting Classes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Charting Classes
57
Release Notes
PeopleCode API
New built-in functions. New classes. New methods. New properties. Modified built-in functions. Modified methods. Modified properties. System setup for Java classes. Deprecated products. Deprecated methods. Deprecated XML Publisher items. XML Publisher items no longer supported. Corrected information. Classes not supported on IBM z/OS and Linux for IBM System z.
The 8.50 PeopleBooks contain complete documentation on each new built-in. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleCode Language Reference Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference
New Classes
In PeopleTools 8.50, the following new classes have been added to the PeopleCode API: Charting classes: OrgChart class RatingBoxChart class Connected query classes:
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference
New Methods
In PeopleTools 8.50, the following new methods have been added to the PeopleCode API: BPELUtil class, UpdateConnectorResponseProperties method. Chart class, SetLegendImg method. Field class, DecryptPETKey method. Field class, EncryptPETKey method. Grid class, EnableColumns method. Grid class, LabelColumns method. Grid class, SetProperties method. Grid class, ShowColumns method. IBInfo class, AddAEAttribute method. IBInfo class, AddAttribute method. IBInfo class, ClearAEAttributes method.
59
Release Notes
IBInfo class, ClearAttributes method. IBInfo class, DeleteAEAttribute method. IBInfo class, DeleteAttribute method. IBInfo class, GetAEAttributeName method. IBInfo class, GetAEAttributeValue method. IBInfo class, GetAttributeName method. IBInfo class, GetAttributeValue method. IBInfo class, GetNumberofAEAttributes method. IBInfo class, GetNumberOfAttributes method. IBInfo class, GetTransactionIDforAE method. IBInfo class, InsertAEResponseAttributes method. IntBroker class, GetIBTransactionIDforAE method. IntBroker class, SwitchAsyncEventUserContext method. MCFMailUtil class, IsDomainNameValid method. MCFMailUtil class, ParseRichTextHtml method. Query class, AddTrackingURL method. Query class, CopyPrivateQuery method. Query class, FormatBinaryResultString method. Query class, GetTreePromptCount method. Query class, RunToString method. Query class, RunToTemplate method. Query class, SetTrackingURL method. QueryDBRecordField class, GetImageFormat method. QueryField class, GetImageFormat method. ReportDefn class, Close method. Rowset class, GetFirstUserSortedRow method. Rowset class, GetLastUserSortedRow method. Rowset class, IsUserSorted method. Rowset class, MapBufRowToUserSortRow method. Rowset class, MapUserSortRowToBufRow method.
Release Notes
The 8.50 PeopleBooks contain complete documentation on each new 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 Release Notes for PeopleSoft Enterprise PeopleTools 8.50, "Development Tools Enhancements," PeopleCode, PeopleCode API, New Classes Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference
New Properties
In PeopleTools 8.50, the following new properties have been added to the PeopleCode API: AnalyticGrid class, SummaryText property. Chart class, RevertToPre850 property. Field class, HoverText property. Field class, IsRichTextEnabled property. Field class, MouseOverMsgNum property. Field class, MouseOverMsgSet property. File class, TerminateLines property. File class, ZeroExtend property. Gantt class, InteractiveEnd property. Gantt class, InteractiveMove property. Gantt class, InteractiveProgress property. Gantt class, InteractiveStart property. Gantt class, RevertToPre850 property. Grid class, SummaryText property. IBInfo class, CompressionOverride property. IBInfo class, FuturePublicationDateTime property. IBInfo class, WSA_Action property. IBInfo class, WSA_FaultTo property. IBInfo class, WSA_To property. MCFMailUtil class, badaddresses property.
61
Release Notes
MCFMailUtil class, imagesLocation property. MCFOutboundEmail class, BackupSMTPSSLClientCertAlias property. MCFOutboundEmail class, BackupSMTPSSLPort property. MCFOutboundEmail class, BackupSMTPUseSSL property. MCFOutboundEmail class, SMTPSSLClientCertAlias property. MCFOutboundEmail class, SMTPSSLPort property. MCFOutboundEmail class, SMTPUseSSL property. Query class, MoreRowsAvailable property. Query class, OutputUnicode property. ReportDefn class, ProcessInstance property. SMTPSession class, BackupSSLClientCertAlias property. SMTPSession class, BackupSSLPort property. SMTPSession class, BackupUseSSL property. SMTPSession class, SSLClientCertAlias property. SMTPSession class, SSLPort property. SMTPSession class, UseSSL property. TransformData class, RejectTransform property. TransformData class, RoutingDefnNameproperty.
The 8.50 PeopleBooks contain complete documentation on each new 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 Release Notes for PeopleSoft Enterprise PeopleTools 8.50, "Development Tools Enhancements," PeopleCode, PeopleCode API, New Classes Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference
The 8.50 PeopleBooks contain complete documentation on each modified built-in function.
Release Notes
Modified Methods
In PeopleTools 8.50, the following methods have been modified in the PeopleCode API: MCFMailUtil class, ValidateAddress method. 1. This method now validates a comma- or semicolon-separated list of email addresses, rather than a single email address. Invalid email addresses are now returned as an array in the badaddresses property of the MCFMailUtil class. ProcessRequest class: AddDistributionOption method, SetEmailOption method, SetItemFolder method, and SetOutputOption method. 2. These methods now take an optional ItemJobSeq parameter. ReportDefn class, Publish method. 3. The ReportPath parameter is not used and must be specified as the null string, "". RowsetCache class, Save method. 4. This method now takes an optional language parameter. The 8.50 PeopleBooks contain complete documentation on each modified method. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference
Modified Properties
In PeopleTools 8.50, the following properties have been modified in the PeopleCode API: Message class, Size property. 5. 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference
63
Release Notes
Deprecated Products
The following products have been deprecated: PeopleSoft Business Interlinks PeopleSoft Mobile Agent
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. PeopleSoft Business Interlinks 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. GetContentBody method of the Request class.
PeopleSoft Mobile Agent 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. SystemIDFieldName1 property of the Record class. TimeStampFieldName1 property of the Record class. IsMobile property of the Folder class. IsMobile property of the ContentReference class. IsMobile property of the ContentReference link.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Appendix: Quick Reference for PeopleCode Classes, Deprecated Items and PeopleCode No Longer Supported, Deprecated Products and Classes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Appendix: Quick Reference for PeopleCode Classes, Deprecated Items and PeopleCode No Longer Supported, Deprecated Methods and Properties
The PeopleBook contains details on equivalents to use instead. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Appendix: Quick Reference for PeopleCode Classes, Deprecated Items and PeopleCode No Longer Supported, Deprecated XML Publisher Items
65
Release Notes
All methods of the QueryDS class. All methods and properties of the EFTPRocessor class. All methods and properties of the FOProcessor class. All methods and properties of the FormProcessor class. All methods and properties of the FOUtility class. All methods and properties of the PDFMapTool class. All methods and properties of the RTFProcessor class.
The PeopleBook contains a detailed list of the affected classes, methods, and properties, and provides equivalents if available. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Appendix: Quick Reference for PeopleCode Classes, Deprecated Items and PeopleCode No Longer Supported, XML Publisher Items No Longer Supported
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
Chart Class and Gantt 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Charting Classes 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, TransformData Class
Release Notes
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). TimeStampFieldName (from the Field class to the Record class).
Classes not Supported on IBM z/OS and Linux for IBM System z
The following classes are not supported on IBM z/OS and Linux for IBM System z: Analytic Calculation Engine classes. Analytic Calculation Engine Metadata classes. Analytic grid classes. Analytic type classes. Optimization PeopleCode classes.
Global Technology
This section covers changes and updates to PeopleTools Global Technology, including: Changes to supported character sets. Changes to the swap audit report. New PeopleSoft language codes. Non-ASCII characters in file names uploaded to FTP servers prior to 8.50. PeopleSoft hot keys do not function as expected on a non-U.S. keyboard Time zone data. Translating application definitions. Updated font support. Using extended Japanese characters.
67
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: Global Technology, Selecting and Configuring Character Sets and Language Input and Output, Understanding Character Sets, Character Sets in the PeopleSoft Pure Internet Architecture The PSCHARSETS table is now a translated table. With PeopleTools 8.50, when creating an Oracle Unicode database, use the AL32UTF8 database character set. See Also Enterprise PeopleTools 8.50 Installation for Oracle Enterprise PeopleTools 8.50 PeopleBook: Global Technology, Selecting and Configuring Character Sets and Language Input and Output, Selecting Character Sets, Selecting Database Character Sets Although Oracles JA16SJISTILDE database character set has been supported since PeopleTools 8.46, that fact was not specifically noted in the PeopleBooks until PeopleTools 8.50. In Verity 6.2.1, the supported ISO encoding for Turkish documents is ISO-8859-9, superseding ISO-8859-3.
Release Notes
Description UK English
Enterprise PeopleTools 8.50 PeopleBook: Global Technology, Controlling International Preferences, Applying Browser Language Preferences, Using Browser Language Settings to Determine the Sign-in Language
69
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: Global Technology, Translating Application Definitions, Translating Definitions
Release Notes
Process Scheduler
This section discusses the enhancements and changes for Process Scheduler, including: Increase Process Instance and Report IDs Viewing Limitations Report Distribution By Role Retention Days Data Mover Scripts to Delete Reports Renaming Database in Process Request Data Tables New Process Category LOADCACHE Runtime Parameters Reporting Console Process Scheduler Web Service
71
Release Notes
Process Instance ID Max sequence is increased to 2147483647. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Process Scheduler, Defining PeopleSoft Process Scheduler Support Information, Defining System Settings
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Process Scheduler, Using Process Monitor, Viewing the Status of Processes Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Process Scheduler, Using Report Manager, Viewing Reports
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
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Process Scheduler, Process Scheduler Table Maintenance, Understanding the Purge Process
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Process Scheduler, Process Scheduler Table Maintenance, Renaming a Database in Process Request Data Tables
73
Release Notes
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:
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:
Release Notes
75
Release Notes
XML Publisher
This section discusses new features and changes for XML Publisher, including: Descriptive Names
Release Notes
Deprecated Data Sources Deprecated Schema Files Connected Query Data Source Global Properties Settings Performance Enhancements PDF Full Path Mapping Alternate XML Preview Iterative Template Design Support for Email
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. %RID% will insert the Report ID. %BTV% will insert the burst field value. %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
77
Release Notes
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
Release Notes
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.
79
Release Notes
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 Connected Query Quick Start Description 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 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Query, Using Connected Query
Release Notes
BusinessObjects Enterprise XI Release 3.1 upgrade. Crystal Reports 2008 upgrade. HKEY_CURRENT_USER. Local directory of crw32.exe. Crystal Reports 2008 runtime environment. Crystal Reports concepts. Crystal Reports execution environments. Crystal Reports 2008 compatibility issues.
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
81
Release Notes
The following diagram illustrates, at a high level, the components of Crystal Reports:
Release Notes
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.
83
Release Notes
Applications 9.1 that use Crystal Reports 9. For example, a PeopleTools-only upgrade. Scenario C: You use PeopleTools 8.50 and versions of PeopleSoft applications prior to PeopleSoft 8. For example, a PeopleTools-only upgrade.
Applications 9.1 that use Crystal 9. For example, a PeopleTools-only upgrade. Scenario F: You use PeopleTools 8.50 and versions of PeopleSoft applications prior to PeopleSoft 8. 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
Release Notes
Cube Builder
This section discusses enhancements that are made to PeopleSoft Cube Builder, including: Oracle Smart View for Office 11.1.1.1 Upgrade. Essbase Cube Buider.
85
Release Notes
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:
Release Notes
Page Dimension Member Formula Find Tree Select Top Node Find Query Select a Column Generation Names
Usage Create or update Essbase dimensions. Enter formula information for a dimension member. Search for and select an existing tree that is defined in the system. Select an existing node of a highlighted tree. Select an existing query that is defined in the system. Select an existing column of a highlighted query. The columns displayed are from the select statement of the query. 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.
Copyright 2009, Oracle and/or its affiliates. All rights reserved. 87
Release Notes
Use the following pages to create an outline: Page Cube Outline Add Cube Dimensions Current Dimension List Data Sources Find Query Dimension Mapping Query Prompt Values Usage Add dimensions to the current outline. Select dimensions to add to the current outline. Remove dimensions from the current outline. Add the cube data query or queries. You can supply one or more queries to fill the cube. Search for available queries. Map columns from data extraction queries to dimensions, select a column from data extraction as the measure, and unmap previously mapped columns. 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:
Release Notes
Page Dimension Delete Outline Delete Run Control Delete View Dynamic Objects
Usage Delete any created dimension in the system as long as the dimension is not referenced in any outline. Delete any created outline in the system as long as the outline is not referenced in any cube creation run control. Delete any cube creation run control. 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 all the dimensions that are a part of the outline for the selected outline. 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 informationcube 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 Create Cubes Outline Prompt Field Values Modify Prompt Field Values Usage Run the process that sends all of the defined information to the Essbase database to build Essbase cubes. View all data source queries that are assigned to the outline. Change any query prompt values on any query that are defined in the selected outline.
89
Release Notes
Integrating with Oracle Smart View 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.
Release Notes
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.
91
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Cube Manager, Building Cubes, Building Cube Instances, Defining Cube Settings for Cognos PowerPlay
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.
Release Notes
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.
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. Supporting not-in criteria. Ability to define the types of report requests. Restoring query prompts to web version of nVision. Default configuration under %PSHOME%. 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. Perform comparative reporting based on different effective dates.
93
Release Notes
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. Specify a new effective-date for all trees used in the layout.
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. By default, this check box is selected. 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.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PS/nVision, Running PS/nVision Reports in the Microsoft Windows Client, Creating Report Requests, Creating Requests Enterprise PeopleTools 8.50 PeopleBook: PS/nVision, Running PS/nVision Reports on the Web, Setting Up Report Requests, Creating Report Requests
95
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PS/nVision, Creating Matrix Layouts, Applying Filter Criteria, Selecting Filter Criteria Options
Drilling Down PS/nVision Reports Using Web Services (nVisionDrill VSTO add-in)
In addition to the current DrillToPIA add-in, you can also perform nVision drilldown using the nVisionDrill VSTO add-in (Visual Studio tools for Microsoft Office SE Runtime). This new nVisionDrill VSTO add-in enables you to use the web service capability when drilling from summarized to detailed nVision reports. Note. DrillToPIA and nVisionDrill VSTO add-ins do not coexist. You can use only one add-in at a time.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PS/nVision, "Running PS/nVision Reports on the Web," Using the PS/nVision DrillDown on the Web
Query
This section discusses enhancements made in the area of Query, including: Ability to develop in-tree criteria prompts. Enhancement request to be able to email AE results. Drilling URL in PSQUERY. Scheduling query with In Tree prompt. Temp Files tiles of the Query-to-Excel. Downloading query results to XML file. Security Join Optimizer option.
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Query, "Defining Selection Criteria," Defining Criteria, Entering Comparison Values
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Query, Modifying, Scheduling, and Organizing Queries, Scheduling Queries, Selecting Process Requests
Release Notes
Clear this option to enable this query to join mutliple times to the security record.
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
99
Release Notes
Integration Broker
This section covers the new features and changes for Integration Broker, including: Integration Broker PeopleBooks. Deprecated integration technologies and utilities. Integration gateways. Target connectors and listening connectors. New managed objects: WSDL and message schema. Messages. Message schemas. Services and service operations. Service operation handlers. Service operation routings. Service operation queues. Web services. WSDL documents. Transformations. Integration Broker security. Integrations with Oracle ESB-based services. Integration Broker logging, tracing, and debugging. Tuning messaging system performance. Integration Broker Service Monitor. Integration Broker testing tools and utilities.
100 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
101
Release Notes
iWay SOAPSwitch
Beginning with this release, iWay SOAPswitch no longer ships with PeopleTools. For integrations with third-party systems, use the PeopleSoft Integration Broker servicesoriented architecture. The Using the ERP Connectors chapter in PeopleBooks has been removed.
Integration Gateways
This section describes enhancements related to PeopleSoft Integration Broker integration gateways.
secureFileKeystorePasswd
102 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference
103
Release Notes
AS2 Connectors
PeopleSoft recommends using the Oracle SOA Suite B2B component for all EDI integrations, including those based on the AS2 specification. See Also Enterprise PeopleTools 8.50 PeopleBook: Integration Broker Administration, Using Listening Connectors and Target Connectors, Working with the AS Connectors, Understanding Electronic Data Interchange Specifications Supported
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Sending and Receiving Messages, Working with Message Segments
Release Notes
Messages
This section describes enhancements for managing messages.
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Understanding Managing Messages, Naming Conventions for Message Metadata
105
Release Notes
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. Nonrowset. Select this value to add a nonrowset-based 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. Rowset. Select this value to add a rowset-based message to the system.
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Adding Message Definitions Viewing Rowset-Based Message Structures 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. 3. View only the included fields in the message structure. A new View Included Fields Only link has been added to the Messages-Message Definitions page. When you click the link the Included Fields Only page appears and displays only the records and subrecord fields that have been included in the message structure. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Managing Rowset-Based Messages, Viewing Rowset-Based Message Structures
106 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
Asynchronous messages are always compressed and base64 encoded when sent to the integration gateway. For synchronous messages, in PSADMIN you can set a threshold message size above which messages are compressed. Beginning with this release, for synchronous messages you can override the message compression setting specified in PSAdmin at the transaction level. The following new method on the IBInfo object is provided for this purpose: &MSG.IBInfo.CompressionOverride = %IntBroker_Compress; The valid parameters for this method are: %IntBroker_Compress, %IntBroker_UnCompress, and %IntBroker_Compress_Reset. 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Understanding Supported Message Structures, Local Compression Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference
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;
An invalid datetime or blank will result in the publish occurring immediately. The status of the transaction in the Service Operation Monitor is Hold until the future date time entered becomes the current date time. At that time the status of the transaction in the Service Operation Monitor is updated to New and processed accordingly. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference
107
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Understanding Managing Messages, Restrictions for Modifying Messages Reusing Part Messages 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 A reference to a message part is read-only in the message part where it is referenced. To make changes to a referenced message part, you must make the changes to the referenced message part directly. All changes are then propagated to every message in which the message part is referenced. Message Reuse by Copying If you copy a message part, the system copies all records and fields and displays them at the record level. The messages and fields become permanent to the specific message and you can edit all records and fields directly in the message where the copied part exists. Changes you make to a copied message part are not propagated to other copies of the message part that may exist. If you must make changes to copied message parts, you do so manually to each message part that you want to change. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Reusing Message Parts Distinguishing Blank from Zero in Rowset-Based Message Parts 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.
108 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Managing Message Parts, Distinguishing Blank from Zero in Rowset-Based Message Parts Obtaining the Size of Rowset Parts within a Container Message 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Message Classes, Message Class Properties
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Managing Container Messages, Adding and Getting Container Messages Attributes Passing More Than One Row of Data on the Level 0 Records 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Managing Container Messages, Understanding Including Level 0 Rows for Message Parts in Container Messages
109
Release Notes
Message Schemas
This section describes enhancements for working with and managing XML message schemas in PeopleSoft Integration Broker. Generating Message Schema for Rowset-Based Messages PeopleSoft Integration Broker now automatically generates message schema for rowsetbased 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Generating XML Message Schema for Rowset-Based Messages Adding Message Schemas for Nonrowset-Based Messages 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Managing Nonrowset-Based Messages
110 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
Excluding Descriptions in Message Schemas 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 MessagesMessage Definitions page features an Exclude Descriptions in Schema box that enables you to suppress descriptions in generated schema. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Managing Rowset-Based Messages, Generating XML Message Schemas for Rowset-Based Messages, Excluding Descriptions in Message Schemas Namespace and Schema Generation for Rowset Based Messages 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. Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Generating XML Message Schemas for Rowset-Based Messages, Including Namespaces in Generated Message Schemas Suppressing Empty XML Tags in Message Schema 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Generating XML Message Schemas for Rowset-Based Messages, Suppressing Empty XML Tags in Message Schema 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.
111
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Managing Rowset-Based Messages, Generated XML Message Schema for Rowset-Based Messages
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Service Operations, Understanding Managing Service Operations
112 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Services, Adding Service Operations to Service Definitions
Monitoring Service Operations in Performance Monitoring Tools Using Module and Action Information
In addition to monitoring service operations in the Integration Broker Service Operations Monitor, other third-party system and performance monitoring tools may be available. Some of these system monitoring tools report metrics by capturing Module and Action information.
113
Release Notes
On an Oracle database, PeopleSoft provides service operation name and PeopleCode event name as Module name and Action name respectively. On an IBM DB2 database, PeopleSoft provides service operationname as Module name (no Action information is provided for DB2 systems). This information enables you to associate service operations with database transactions for monitoring and troubleshooting. To enable capturing service operation and PeopleCode event metrics you must set the EnableDBMonitoring option in PSADMIN. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Service Operations, Understanding Managing Service Operations, Monitoring Service Operations Enterprise PeopleTools 8.50 PeopleBook: Data Management, Administering PeopleSoft Databases on DB2 UDB for z/OS, Associating PeopleSoft Users with DB2 UDB Threads Enterprise PeopleTools 8.50 PeopleBook: Data Management, Administering PeopleSoft Databases on DB2 UDB for Linux, UNIX, and Windows, Checklists and Troubleshooting, Monitoring Module Information
Handler Descriptions
On the Service Operations-Handlers Detail page, by default the system populates the Description field with the service operation name. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Service Operation Handler, Adding Handlers to Service Operations
114 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
You can use the new Application Engine handler implementation method for Notification events. This handler schedules an application engine program to run within PeopleSoft Process Scheduler. You can track the process in the Service Operation Monitor by viewing the subscription contract. Using this handler is a good alternative for long-running programs or for service operations that have large amounts of data to process, since processing occurs in PeopleSoft Process Scheduler and not in the Integration Broker runtime environment. PeopleSoft provides several IBInfo object methods that enable you to pass information via the Message object back into the response application class defined on the handler. These methods are: AddAEAttribute ClearAEAttributes DeleteAEAttribute GetAEAttributeName GetAEAttributeValue GetNumberofAEAttributes GetTransactionIDforAE InsertAEResponseAttributes
See the PeopleCode API Reference PeopleBook for more information about these methods. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker: Managing Service Operation Handlers, Implementing Handlers Using Application Engine Programs Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference, Message Class, IBInfo Class Methods
Using Bulk Load Handlers to Process Container Messages 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.
115
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker: Managing Service Operation Handlers, Implementing Handlers Using Bulk Load Processing New System Audit Query to Identify Bulk Load Handlers Referencing Invalid Message Objects A new system audit query, IBRK-24 IB DMS Handler Referencing Invalid Message, has been added to identify situations where you have moved a Bulk Load Handler object via project copy, but did not include the associated message objects. See Also Enterprise PeopleTools 8.50 PeopleBook: Data Management, Ensuring Data Integrity, Integration Broker Integrity
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, Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Routing Definitions, Adding Routing Definitions, Adding a Routing Definition
116 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Routing Definitions, Managing System-Generating Routing Definitions, Viewing System-Generated Routing Definitions.
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();
117
Release Notes
118 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
The following example shows a routing definition in graphical format for a synchronous service operation:
119
Release Notes
Click a link in the Actions column to resolve an issue. The system activates the associated metadata and displays a message when the issue is resolved. 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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Routing Definitions, Viewing Routing Definitions in Graphical Format
120 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Routing Definitions, Creating Routing Definitions, Defining General Routing Information
Release Notes
Web Services
This section describes enhancements for working with and managing web services.
WSDL Documents
This section describes enhancements for working with and managing WSDL documents in PeopleSoft Integration Broker. Resolving Inconsistencies in Exported WSDL PeopleSoft Integration Broker provides a status message in the Messages-Message Definitions page that alerts you when a message is flagged as having WSDL exported, but no WSDL exists in the database.
122 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
This situation can arise when you use Project Copy to copy a service operation to a new database, but do not include the WSDL in the project. You can use one or more of the following options to clear this inconsistency: Clear the internal WSDL exported flag on the service operation. Integration Broker provides a new Clear WSDL Export Status page, which enables you to clear the flag. Use Project Copy to copy the WSDL to the new database. Regenerate the WSDL on the new database using the Provide Web Service wizard.
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Resolving Inconsistencies in Exported WSDL Enforcing Message Record and Field Aliases in Generated WSDL 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: Check Level Error None Warning Description If the system encounters a message definition without proper record and field aliases, it displays an error and it will not generate a WSDL document. Default. The system creates a WSDL document regardless of whether message records and fields are aliased or not. As the system creates a WSDL document it displays a warning it encounters messages definitions that do not have complete aliasing for records and/or fields. If the system encounters records or fields that do not have aliases defined, you can continue to generate the WSDL document or terminate the generation of the WSDL document.
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Messages, Enforcing Message Record and Field Aliases in Generated WSDL
Transformations
This section describes enhancements related to transformations.
123
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Applying Filtering, Transformation and Translation, Developing Transforms Using Oracle XSL Mapper, Specifying the Installation Path and Classpath for Oracle XSL Mapper
%TransformData.routingDefnName The %TransformData.routingDefnName property retrieves the routing definition name for a transaction, and allows you to retrieve the routing properties respectfully. %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; If you set the %TransformData.rejectTransform property within a transform of an inbound asynchronous transaction, the system will not create a subscription contract and the data is not sent. If you view such a transaction in the Service Operations Monitor, the Operation Instances page displays a status of Done. If you open the Asynchronous Details page in the monitor to view additional transaction details, an Error link displays. If you click the link an informational message appears that indicates that the transaction was terminated. If you set this property for an outbound asynchronous transaction, the Publication Contracts page in the Service Operations Monitor will show a contract status of Done for the transaction. However, the system does not send the message and, as with the inbound scenario, the Asynchronous Details page for the transaction will display an Error link. If you click the link an informational message appears that indicates that the transaction was terminated. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Routing Definitions, Retrieving Routing Properties Programmatically Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Applying Filtering, Transformation, and Translation, Rejecting Transformation Programs Enterprise PeopleTools 8.50 PeopleBook: PeopleCode API Reference
124 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
WS-Security
This section describes enhancements to PeopleSofts implementation of WS-Security as it pertains to PeopleSoft Integration Broker. SAML Token Support PeopleSoft Integration Broker now supports implementing inbound and outbound WSSecurity using Security Assertion Markup Language (SAML) tokens. See Also Enterprise PeopleTools 8.50 PeopleBook: Integration Broker Administration, Setting Up Secure Integration Environments, Implementing WS-Security Encryption Levels for Outbound Integrations The Nodes - WS Security page (IB_NODESECURITY enables you to select from three levels of encryption when you are encrypting an outbound service operation.
125
Release Notes
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. Body. Encrypts the message body only. Header. (Default) Encrypts the message header only
See Also Enterprise PeopleTools 8.50 PeopleBook: Integration Broker Administration, Setting Up Secure Integration Environments, Implementing WS-Security, Implementing WS-Security for Outbound Integrations (Username and SAML Tokens), Encrypting Outbound Messages Securing Responses in Asynchronous Request/Response Service Operations PeopleSoft Integration Broker sends responses for asynchronous request/response service operations to the URL set in the Target Location field in on the Service Configuration page. The URL specified on this page is typically not secure, as it is the URL used for all WSDL, schemas, and web transactions. When providing asynchronous request/responses, you can dynamically override the URL using the IBInfo object property WSA_ReplyTo. For example: &MSG.IBINFO.WSA_ReplyTo See Also Enterprise PeopleTools 8.50 PeopleBook: Integration Broker Administration, Setting Up Secure Integration Environments, Implementing Web Services Security, Securing Responses in Asynchronous Request/Response Service Operations Overriding Node-Level WS-Security Settings on Routing Definitions 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 Enterprise PeopleTools 8.50 PeopleBook: Integration Broker Administration, Setting Up Secure Integration Environments, Implementing Web Services Security, Overriding NodeLevel WS-Security Settings on Routing Definitions Implementing WS-Security on Services Consumed Using the Consume Web Service Wizard 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.
126 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: Integration Broker Administration, Setting Up Secure Integration Environments, Implementing Web Services Security, Implementing WSSecurity on Services Consumed Using the Consume Web Service Wizard
127
Release Notes
No node password found on target node. Mismatched node password on source and target nodes. No permissions set for the service operation on the source node.
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Integration Broker, Managing Error Handling, Logging, Tracing and Debugging, Debugging Integrations, Handling Common Issues
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: Domain Domain A Domain B Domain C 1 2 3 Failover Priority
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 Enterprise PeopleTools 8.50 PeopleBook: Integration Broker Administration, Setting Up Domain Failover, Understanding Domain Failover, Failover Priority General Failover Dynamic Slave Failover 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.
128 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: Integration Broker Administration, Setting Up Domain Failover, Understanding Domain Failover, Failover Priority Dynamic Slave Failover
129
Release Notes
Implementing Deferred Master Domain Processing 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 Enterprise PeopleTools 8.50 PeopleBook: Integration Broker Administration, Tuning Messaging System Performance, Implementing Master Domain Processing
130 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
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.
131
Release Notes
132 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
133
Release Notes
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 Populating Rowset-Based Message Parts in Container Messages 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
134 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, Using the Service Operation Tester Utility
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
135
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, Using the Handler Tester Utility, Understanding the Handler Tester Utility, Testing Bulk Load Handlers Testing Application Engine Handlers You can test application engine handlers only when the data used for the test is transaction data from the application database. (This is the DB Operation Transaction option when populating data.) Otherwise the application handler will fail due to no transaction ID being available to the application engine program. See Also Enterprise PeopleTools 8.50 PeopleBook: Integration Testing Utilities and Tools, Using the Handler Tester Utility, Understanding the Handler Tester Utility, Testing Application Engine Handlers
The version numbers were removed and the names are now: Integration Broker (MIME) Integration Broker (XML) EIP Testing (Batch EIP) 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 Brokers 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
136 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
137
Release Notes
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.
138 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
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. Viewing log files.
139
Release Notes
Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Component Interfaces, Using the Excel-to-Component Interface Utility Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Component Interfaces, Running the Excel-to-Component Interface Utility
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: Microsoft Excel Version Microsoft Excel 2000 Microsoft Excel 2003 Microsoft Excel 2007 Template ExcelToCI.xls ExcelToCI.xls ExcelToCI2007.xlsm PS_HOME\Excel PS_HOME\Excel PS_HOME\Excel Location
Note that users for Microsoft Excel 2000 and Microsoft Excel 2003 use the same template. See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Component Interfaces, Running the Excel-to-Component Interface Utility
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.
140 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Component Interfaces, Adding New Languages
141
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Component Interfaces, Diagnosing and Resolving Errors, Viewing Log Files
MultiChannel Framework
This section describes the new features and changes for MultiChannel Framework, including: CTI Screen Popup SSL Support for IMAP Sample Pages Web Chat Enhancement Debug Tracer Enhancement Virus Scanning for Email Attachments AOL support dropped in Instant Messaging
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.
142 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
143
Release Notes
When defining or modifying a template you can now choose the step type of ProcessScheduler.
144 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
145
Release Notes
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
146 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
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
The Generate New Template option enables you to generate a Change Assistant template and ignore any manual changes made to an existing template.
147
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Change Assistant, Working with Change Packages, Creating Change Packages
148 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
149
Release Notes
150 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
151
Release Notes
152 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
153
Release Notes
154 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Application Designer Lifecycle Management Guide, Comparing Source and Target Definitions
155
Release Notes
See Also Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Application Designer Lifecycle Management Guide, Comparing Source and Target Definitions
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 Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Application Designer Lifecycle Management Guide, Working With Alter Analyzer
156 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Release Notes
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.
157
Release Notes
158 Copyright 2009, Oracle and/or its affiliates. All rights reserved.