PeopleSoft - Oracle - SAP

WebLogic Fails to Listen on SSL Port after Installing a WildCard Certificate or a SHA2 Certificate. Logs Message: "Cannot convert identity certificate

2014-10-15T16:53:00.001-07:00

This error can occur for two reasons:

Reason#1: Using a non-compliant certificate such as wildcard
------------------------------------------------------------------------
Older WebLogic versions, such as WebLogic 8.1 and 9.2, do not support wildcard certificates as per the RFC3280 specifications. Although even though the wild card certificates are not supported on older WebLogic versions, they often function without issues. However, we do know that there are issues with wildcards on WebLogic 8.1SP6 and we occasionally see issues on other WebLogic versions as well. In addition, there can be problems with using wildcard certificates on a PeopleSoft Gateway server as noted in bug 11607478.

Reason#2: Using a SHA2 certificate
------------------------------------------------
SHA2 is a newer hash algorithm and is supported by WebLogic starting with version 10.3.3. However, if you use SHA2, you must enable JSSE SSL (details in 'Solution' section) or else you will get the above error

************************************************************************************

If you are using a Wildcard Certificate:
-----------------------------------------------
Install a certificate with no wildcard characters in the common name (CN)

If you are using a SHA 2 Certificate (ie Signature Algorithm starts with 'SHA2')
------------------------------------------------------------------------------------------
1. If you are using WebLogic 10.3.2 or lower, you must first upgrade to WebLogic 10.3.3 or higher (ideally, you should upgrade to WebLogic 10.3.6 as there are some SHA2 bug fixes that are included in WebLogic 10.3.6. Refer to document 1389918.1 for instructions on upgrading WebLogic. If you are unable to upgrade, then you will need to switch to a SHA1 certificate

2. If you are using WebLogic 10.3.3 or higher, then use the following steps to enable JSSE SSL which trusts stronger certificates such as SHA2.
    a. Log in to your WebLogic admin console
    b. From left menu, choose Environment -> Servers -> PIA
    c. Click the 'Configuration' tab and 'SSL' subtab
    d. Go to bottom of page and click the 'Advanced' hyperlink
    e. Click the 'Lock & Edit' button on top left menu
    f. Go to bottom of page and check "Use JSSE SSL"
    g. Click "Save"
    h. Click 'Activate Changes'

WebLogic Fails to Start with Error "PersistentStoreException" or "Couldn't obtain an exclusive lock to the embedded LDAP data files directory"

2014-10-15T16:50:00.002-07:00

This problem occurs if you kill the WebLogic process via kill -9 on Unix or via CTL+C from the PIA command prompt on a Windows system.

Make sure that no other java process is using the same port that this server is trying to acquire. If there is another process using this port, you will need to either change the port WebLogic uses or the port for the process that is already running. This can be done through netstat or on Unix, by listing all of the running java processes with "ps -ef|grep java".

OPTION #1:
============
To resolve the error, remove the ldap directory from:
    For PeopleTools 8.44 to 8.48: \webserv\\\
    For PeopleTools 8.49+: \webserv\\servers\\data\

There is file called EmbeddedLDAP.lok that is created under the ldapfiles folder (within the ldap directory). If this file is present, the server cannot boot and you will see the exceptions above.

This file is normally unlocked on shutdown, but if the previous shutdown occurred in an abnormal way, such as a crash, then this file may not be unlocked properly and the server will generate those exceptions.

OPTION #2:
===========
Remove the *.DAT and EmbeddedLDAP.lok files.

1. Make sure the server is stopped.
2. Go to the following directory
     For PeopleTools 8.44 to 8.48: \webserv\\\ldap\ldapfiles
   For PeopleTools 8.49+: \webserv\\servers\\data\ldap\ldapfiles
3. Remove "EmbeddedLDAP.lok"
4. Remove "*.DAT"
5. Restart WebLogic.

Crystal Reports 2008 - Client - Error "Missing or invalid version of SQL library PSORA32 (200.0). Invalid userid or password

2014-10-15T16:48:00.003-07:00

The issue is caused by the following setup: PSORA32.dll present in "/bin/client/winx86" cannot be accessed from the PATH environment variable

With Peopletools 8.53, PeopleTools application and batch servers are now 64 bit applications. But some batch server components are still 32 bit. So you need to have both 32 bit and 64 bit Oracle client for batch server to work correctly.

So, as both 64 bit and 32 bit Oracle client on Scheduler machine, please make sure that both Clients locations populated correctly in "Add to Path" parameter in PSPRCS.cfg fle.

------------------------------------------------------------------------------------------------------------------

To implement the solution, please execute the following steps:

1. Please ensure both 32-bit and 64-bit connectivity has been nstalled on the batch server

2.. Go to Control Panel\All Control Panel Items\System > Advance > Environmental Variables

3. Add the /bin/client/winx86" as the first entry in PATH variable as the first entry in PATH variable. Make sure that the 32-bit connectivity is listed first, then the 64-bit listed second. If the PATH in the environment variables of the local windows machine is set up incorrectly with 64-bit listed first, then application designer would find the 64-bit connectivity first and attempt to use it, causing an error. The servers that require 64-bit will not always use the first connectivity encountered in the PATH

4. Reboot the Process Scheduler domain. In some instances, the machine would need a reboot for the solution to take effect.

5. Migrate the solution as appropriate to other environments.

6. In some instances, a reboot of the machine may be required but not necessary.

Crystal Will Not Run With The Runtime SP3 Version - Crystal Runtime Initialization Failed

2014-10-15T16:40:00.000-07:00

The issue was caused by extra Crystal DLLs existing in the problem environment's %pshome%\setup\crystalbin, which were not delivered with the PeopleTools installation. It is not clear how these files got into the %pshome%\setup\crystalbin, possibly as a result of a prior copy operation.

1) Remove the extra files in %pshome%\setup\crystalbin which should not be present from the PT installation.
For PT8.51+ only the following should be included under %pshome%\setup\crystalbin:

(don't remove these from their delivered location, they need to be able to be copied by the psodbccrinst.exe program)

~\System\libpng10.dll
~\u2lbar.dll
~\u2lps.dll
~\u25store.dll
~\u25total.dll

NOTE: To support the PStoWords function, psodbccrinst.exe also copies from %pshome%\bin\client\winx86:
(don't remove these from their delivered location, they need to be able to be copied by the psodbccrinst.exe program)

~\u25pstowords.dll
~\icudt34.dll
~\psicuin34.dll
~\psicuuc34.dll

2) Uninstall all Crystal and the Crystal Runtime from the process scheduler
3) Disable all antivirus for the duration of the Crystal and Crystal Runtime install
4) Install Crystal Reports 2008 runtim and client, if it will be used.
5) Rerun the psodbccrinst.exe and confirm that only the above files were copied by viewing the psodbccrinst.log.
6) Reenable anitvirus
7) Restart the process scheduler
8) Retest the issue.
9) Migrate as appropriate

PeopleSoft Virtualization

2013-10-16T12:54:00.001-07:00

http://www.youtube.com/watch?v=WNGIUfop8Eo&list=PL4okLhHVjSg5nP9So9CtQVMeA_GS_PqAG

PeopleSoft - Oracle - SAP: Application Engine programs only stuck at queued

2013-10-14T18:05:00.001-07:00

PeopleSoft - Oracle - SAP: Application Engine programs only stuck at queued

Generation copy book /remote call and .lis file

2013-07-19T11:10:00.000-07:00

For Microsoft Windows, cblmake.bat, which lives under %PS_HOME%\src\cbl\win32. Add this location to your PATH environment variable so you can call the command from anywhere you want. Because there are so many dependencies, I would copy everything under %PS_HOME%\src\cbl\base to a temp location like C:\Temp, then issue the following command to compile a single COBOL in error call mode

C:\Temp>cblmake.bat GLPJEDIT

(Note the drop of .cbl extension).

If you run cblmake.bat without any parameters it will display all available compile options.

Once compiled, copy the appropriate INT/GNT/EXE to your %PS_HOME%\CBLBIN<%Type%> directory.

Compiling Single COBOL program

2013-07-19T11:08:00.002-07:00

To compile a single COBOL program, run the command with the COBOL program name excluding the .cbl extension.

For example, for a PeopleSoft PeopleTools COBOL program PTPDBTST.CBL, or a PeopleSoft
Application COBOL program GPPDPRUN.CBL, run:

pscbl.mak PTPDBTST
pscbl.mak GPPDPRUN

For more information, you may refer 'Installing and Compiling COBOL on UNIX Chapter 12B' in PeopleTools 8.52 install guide

How to identify who is locking the Oracle account

2013-06-03T11:11:00.001-07:00

With AUDIT_TRAIL

The first and preferred solution is with Oracle standard auditing feature. Start by setting initialization parameter AUDIT_TRAIL to db and restart your Oracle database as it is static parameter.
Then activate network auditing with (as SYS):

SQL> AUDIT network BY ACCESS;
 
AUDIT succeeded.

With below query you get everything needed:

SELECT *
FROM dba_audit_session
ORDER BY sessionid DESC;

Returncode column contains Oracle error code and so different of 0 if logon/logoff issue. The invalid password is the error we are chasing:

[oracle@server1 ~]$ oerr ora 1017
01017, 00000, "invalid username/password; logon denied"
// *Cause:
// *Action:

So if you find 1017 values in this column then we have found what we were looking for. For example with my test case where I intentionally specify a wrong password for my account:

SQL> SELECT username,userhost,returncode
     FROM dba_audit_session
     WHERE username='YJAQUIER'
     ORDER BY sessionid DESC;
 
USERNAME                       USERHOST             RETURNCODE
------------------------------ -------------------- ----------
YJAQUIER                       server1                    1017
YJAQUIER                       GVADT30596                    0
YJAQUIER                       server1                       0
YJAQUIER                       server1                       0
.
.
.

And if you insist, as explained, you get:

SQL> SELECT username, account_status,lock_date, PROFILE FROM dba_users WHERE username='YJAQUIER';
 
USERNAME                       ACCOUNT_STATUS                   LOCK_DATE            PROFILE
------------------------------ -------------------------------- -------------------- ------------------------------
YJAQUIER                       LOCKED(TIMED)                    23-nov-2012 10:30:37 DEFAULT

If you set AUDIT_TRAIL to db behave the size of SYS.AUD$ table as a small list of audits are already implemented by default:

SQL> SET lines 200
SQL> SET pages 200
SQL> SELECT * FROM DBA_STMT_AUDIT_OPTS;
 
USER_NAME                      PROXY_NAME                     AUDIT_OPTION                             SUCCESS    FAILURE
------------------------------ ------------------------------ ---------------------------------------- ---------- ----------
                                                              ALTER SYSTEM                             BY ACCESS  BY ACCESS
                                                              SYSTEM AUDIT                             BY ACCESS  BY ACCESS
                                                              CREATE SESSION                           BY ACCESS  BY ACCESS
                                                              CREATE USER                              BY ACCESS  BY ACCESS
                                                              ALTER USER                               BY ACCESS  BY ACCESS
                                                              DROP USER                                BY ACCESS  BY ACCESS
                                                              PUBLIC SYNONYM                           BY ACCESS  BY ACCESS
                                                              DATABASE LINK                            BY ACCESS  BY ACCESS
                                                              ROLE                                     BY ACCESS  BY ACCESS
                                                              PROFILE                                  BY ACCESS  BY ACCESS
                                                              CREATE ANY TABLE                         BY ACCESS  BY ACCESS
                                                              ALTER ANY TABLE                          BY ACCESS  BY ACCESS
                                                              DROP ANY TABLE                           BY ACCESS  BY ACCESS
                                                              CREATE PUBLIC DATABASE LINK              BY ACCESS  BY ACCESS
                                                              GRANT ANY ROLE                           BY ACCESS  BY ACCESS
                                                              SYSTEM GRANT                             BY ACCESS  BY ACCESS
                                                              ALTER DATABASE                           BY ACCESS  BY ACCESS
                                                              CREATE ANY PROCEDURE                     BY ACCESS  BY ACCESS
                                                              ALTER ANY PROCEDURE                      BY ACCESS  BY ACCESS
                                                              DROP ANY PROCEDURE                       BY ACCESS  BY ACCESS
                                                              ALTER PROFILE                            BY ACCESS  BY ACCESS
                                                              DROP PROFILE                             BY ACCESS  BY ACCESS
                                                              GRANT ANY PRIVILEGE                      BY ACCESS  BY ACCESS
                                                              CREATE ANY LIBRARY                       BY ACCESS  BY ACCESS
                                                              EXEMPT ACCESS POLICY                     BY ACCESS  BY ACCESS
                                                              GRANT ANY OBJECT PRIVILEGE               BY ACCESS  BY ACCESS
                                                              CREATE ANY JOB                           BY ACCESS  BY ACCESS
                                                              CREATE EXTERNAL JOB                      BY ACCESS  BY ACCESS

So you must put in place a purging policy for this table.

Without AUDIT_TRAIL

The only drawback of the previous solution is that you have to restart the database. And maybe two times because after problem solved you would like to deactivate auditing. This is most probably not reliable solution on a production database so I have been looking for a better solution with no database reboot.
I initially thought of the AFTER LOGON trigger but you need to be logged-in and the BEFORE LOGON does not exits. Then at same documentation place I found the AFTER SERVERERROR trigger and decided to give it a try.
First I created a dummy table to log server error (columns inherited from dba_audit_session dictionary table):

CREATE TABLE sys.logon_trigger
(
USERNAME VARCHAR2(30),
USERHOST VARCHAR2(128),
TIMESTAMP DATE
);

Second I created below trigger:

CREATE OR REPLACE TRIGGER sys.logon_trigger
AFTER SERVERERROR ON DATABASE
BEGIN
  IF (IS_SERVERERROR(1017)) THEN
    INSERT INTO logon_trigger VALUES(SYS_CONTEXT('USERENV', 'AUTHENTICATED_IDENTITY'), SYS_CONTEXT('USERENV', 'HOST'), SYSDATE);
    COMMIT;
  END IF;
END;
/

Then third simulated a wrong password access with my account and issued:

SQL> ALTER SESSION SET nls_date_format='dd-mon-yyyy hh24:mi:ss';
 
SESSION altered.
 
SQL> SET lines 200
SQL> col USERHOST FOR a30
SQL> SELECT * FROM sys.logon_trigger ORDER BY TIMESTAMP DESC;
 
USERNAME                       USERHOST                       TIMESTAMP
------------------------------ ------------------------------ --------------------
yjaquier                       ST\GVADT30596                  23-nov-2012 11:05:56

Tablespace not displaying in Application designer to save records

2013-06-03T11:05:00.004-07:00

Below SQL will help to resolve the Tablespace not displaying in Application designer to save records

INSERT INTO PSTBLSPCCAT
SELECT DISTINCT DDLSPACENAME, DBNAME ,'R',' ', '' FROM PSRECTBLSPC A
WHERE TEMPTBLINST = 'N'
AND NOT EXISTS (SELECT 'X' FROM PSTBLSPCCAT
WHERE DDLSPACENAME = A.DDLSPACENAME
AND DBNAME = A.DBNAME);

JSL/WSL (jolt/Work Listener) failed to start with error Could not establish listening address on network

2013-05-31T12:33:00.005-07:00

These error messages indicate that the port number that the Tuxedo process is attempting to start listening on is either in use, invalid, or the hostname/IP address specified for that address is invalid.

The Application Server will spawn new processes when it boots up based on the Min and Max Handlers for the Workstation Listener and Jolt Listener. Make sure you have your ports spread out between the WSL and JSL to accommodate the Max Handlers value for the Workstation Listener. For example if you are using port 7000 for WSL and have a Max Handlers value of 5, ports 7001 - 7005 will be used as well. You will want to set the JSL to no less then 7006

For example appserver use port 9618 and spaned 5 more in use and it fails when rebooting.Find the spawned process in use using netstat -lpn and get the PID - kil the PID and start the appserver

netstat -lpn | grep 961*

tcp 0 0 10.137.4.25:9619 0.0.0.0:* LISTEN 16347/JSH
tcp 0 0 10.137.4.25:9620 0.0.0.0:* LISTEN 16348/JSH
tcp 0 0 10.137.4.25:9621 0.0.0.0:* LISTEN 16349/JSH
tcp 0 0 10.137.4.25:9622 0.0.0.0:* LISTEN 16350/JSH
tcp 0 0 10.137.4.25:9623 0.0.0.0:* LISTEN 16351/JSH

[PS_HOME/appserv]$ kill -9 16347 16348 16349 16350 16351

Query to find user security access by navigation

2013-03-12T13:07:00.001-07:00

select a.oprid as OPRID, a.oprdefndesc as NAME, b.rolename as ROLENAME, c.descr254 as NAVIGATION, c.descr150_mixed as DESCRIPTION
from psoprdefn a, psroleuser b, psroleclass d, psauthitem e, ps_authitem_cmp c
where a.oprid = b.roleuser
and b.rolename = d.rolename
and d.classid = e.classid
and e.menuname = c.menuname
and e.barname = c.barname
and e.baritemname = c.baritemname
and e.pnlitemname = c.pnlitemname
and a.oprclass like 'PP_UK%'
and a.acctlock = 0
order by a.oprid, b.rolename;

Maintaining Security in PeopleSoft Upgarde

2013-02-19T16:40:00.002-08:00

In order to preserve security through your upgrade passes, you will have 3 options.

1) Low Risk - Re-enter your security changes into one of the target databases. Once this is complete, those security tables can be exported out and imported into any other upgraded databases at the same tools release using security migration reDocument:610138.1, included below.

2) Low Risk - Re-do the Initial Upgrade again. This will get the security as it is when you take the copy of production. Many customers chose this option because they are most comfortable with it. Once the initial upgrade is completed, follow the steps outlined in reDocument:610138.1 (Included below) to migrate security to your other upgraded databases.

3) High Risk -
Attention! This workaround has not gone through our formal quality regression test cycle. We strongly recommend that you thoroughly test this workaround in a development environment before applying it to your production environment.

Be sure to document this change as this workaround may be detected during your next upgrade. Because this workaround has not yet gone through our formal quality regression test cycle, this workaround will have risk.

You should only follow this option if you only want the latest operator security in production migrated to your upgraded database. Do the Initial Upgrade again, up through the end of Chapter 2 (Updating PeopleTools). You will need to definitely run the Relnnn.sql scripts, copy the projects and do the alters - but to make sure you get everything correct, it would be best to run all steps in Chapter 2. Once completed your tools release will be at the same level as your fully upgraded database that you want operator security imported into. DO NOT FOLLOW Document:610138.1 as you will LOSE ALL security delivered by the new application release you just upgraded to. To migrate your operator security, select the appropriate Data Mover script for your PeopleTools release to export and import operator security:

For PT 8.4x -

******Export******
USEREXPORT.dms

This script looks as follows:

-- USERS
EXPORT PSOPRDEFN;
EXPORT PSOPRALIAS;
EXPORT PSROLEUSER;
EXPORT PSUSERATTR;
EXPORT PSUSEREMAIL;
EXPORT PSUSERPRSNLOPTN;
EXPORT PS_ROLEXLATOPR;
EXPORT PS_RTE_CNTL_RUSER;

******Import******
USERIMPORT.dms

This script looks as follows:

UPDATE PSLOCK SET VERSION = VERSION + 1 WHERE OBJECTTYPENAME = 'UPM';

REPLACE_DATA *;

UPDATE PSVERSION SET VERSION = VERSION + 1 WHERE OBJECTTYPENAME = 'SYS';
UPDATE PSVERSION SET VERSION = VERSION + 1 WHERE OBJECTTYPENAME = 'UPM';

UPDATE PSOPRDEFN SET VERSION = (SELECT VERSION FROM PSVERSION WHERE OBJECTTYPENAME = 'UPM');

Steps for PopleTools 8.5X PIA and Weblogic Installation with JRockit

2013-01-04T14:26:00.004-08:00

1) To download the latest WebLogic maintenance pack (10.3.6) for PeopleTools 8.52, do the following:

a. Go to the following URL for the “Oracle Software Delivery Cloud site (aka eDelivery): http://edelivery.oracle.com/

b. Follow instructions for filling in personal info and confirm acceptance of terms, etc. Then click 'Continue' button

c. On the "Media Pack Search" page, click on the first ("Product Pack") drop down list, and choose "Oracle Fusion Middleware".

d. In the second, "Platform" drop down list, chose Linux x86-64

e. After making your choices, click the "Go" button.

f. Click the 'Oracle Fusion Middleware 11g Media Pack for Linux x86-64' hyperlink

g. Then click the 'Download' button next to 'Oracle WebLogic Server 11gR1 (10.3.6) Generic and Coherence' (part# is V29856-01)

h. After the file is downloaded, unzip it.

2) To download the latest JRockit:

a. Go to My Oracle Support through http://support.oracle.com and log in

b. Once logged in, click the "Patches & Updates" tab.

d. Select "Product or Family (Advanced Search)". (on top right corner of page)

e. Enter the following info:

Product is: "Oracle JRockit"

Release is "Oracle JRockit 28.2.5"

Platform is: "Linux x86-64"

f. Click "Search" to continue. You will see a list of the JRockit patches available.

Please select "JDK160 ORACLE JROCKIT R28.2.5" (Make sure you get JDK160, and NOT JDK150!).

g. Click "Download", and save the patch to your local drive. The file name will be in *.zip format. For example: p14261101_2825_Linux-x86-64.zip

3) To install WebLogic 10.3.6 and the new JRockit:

a) Unzip the JRockit zip file (from step 3) to the directory where you want it installed. (I'd suggest you install it in the same directory where you are installing WebLogic
c) Now install WebLogic 10.3.6. Follow the instructions in the PeopleTools 8.52 Installation guide

(see section: "Installing Oracle WebLogic on Linux or UNIX)

4) Now try to re-install the WebLogic PIA

Linux kernal parameters for PeopleTools 8.52

2012-12-27T18:48:00.000-08:00

Below Linux kernal parameter has to be set to for PeopleTools 8.52 installtion on Linux else the the process with fail to start with less allocated memory

Add the following lines to /etc/sysctl.conf

# Added for PS
kernel.sem = 256 32000 128 192

# Added for PS
kernel.msgmni = 2048

# Added for PS
net.ipv4.ip_local_port_range = 1024 65000

to activate:

/sbin/sysctl -p

to retain settings after booting add the following line to /etc/rc.local

/sbin/sysctl -p

shell Script to monitor log file

2012-12-13T11:33:00.001-08:00

Below script will monitor for the error log file updated date every 5 minutes and compare it with the current date and send email if it is updated today.After the issue has been fixed you may need to backup the old log

Scheduled to run 5 mins:

0,5,10,15,20,25,30,35,40,45,50,55 * * * * /opt/hrms/webserv/hr/applications/peoplesoft/PSIGW/monitor.sh

Monitor.sh Script:

#!/bin/sh

cd /opt/hrms/webserv/hr/applications/peoplesoft/PSIGW

Current_Date=`date +"%b %e"`

Filerrordate=`ls -ltr /opt/hrms/webserv/hr/applications/peoplesoft/PSIGW/errorLog.html
awk '{print $6,$7}'`

if [ "$Current_Date" = "$Filerrordate" ] ; then

echo $Current_Date":Error logged in IB gateway log" >> /opt/hrms/webserv/hr/applications/peoplesoft/PSIGW/dailystatus.log

cat errorLog.html
mailx -s "URGENT::Error occured in IB Gateway please Check immediatly" xxxx@name.com

exit 0

else

echo $Current_Date":No new error in error log" >> /opt/hrms/webserv/hr/applications/peoplesoft/PSIGW/dailystatus.log

exit 0

fi

Integration Broker gateway setup with Load Balancer

2012-11-28T18:20:00.003-08:00

What should the Gateway URL be and what should the Physical Gateways URL's be?

The gateway URL should actually be the URL of the load balancer, and not any of the web servers hosting the Gateways.

If the load balancer checkbox is checked, then additional field is opened on the page where the URLs for the physical web servers (hosting the gateways) can be listed. These URLs are for information purposes only. There is no load balancing code/logic being triggered as a result of these values. The load balancing logic/code to redirect connections to one of the physical web servers (hosting the gateways) should be in the load balancer.

What happens if the Gateway URL is down, what kind of failover will happen?
If the Gateway URL (Load Balancer) is down, then messaging will not work as it will not be able to direct requests to one of the Physical gateways/web servers. But if one of the Physical Gateways were down, it will just failover to another one. There is no significance of the order in which you add those Physical Gateways.

When hitting the Load Gateway Connectors button, is that only loading connectors for the primary gateway URL? Do they need to do that for each Physical URL also?
You only need to hit the Load button once, provided you have not added or modified any of the connectors on any of the webservers. We are assuming all connectors on any of the web servers are the same and as delivered. When you hit the Load button, we are only going through one Gateway, and loading the connectors from one webserver, then loading them into the database.

When you ping a node, which Gateway is it using?
Load Balancing typically is a Round Robin approach driven by the load balancer, and PSFT does not control which Gateway to use. The way to test each Gateway is to bring down all but one > then ping. Then bring down all but the next Gateway > then ping. etc until all are tested successfully.

Process tables

2012-11-26T16:28:00.001-08:00

PS_PMN_SRVRLIST

PS_PMN_SRVRLIST – PeopleSoft Process Scheduler Server List Record.The corresponding information is available also in the PeopleSoft interface on the menu Home>PeopleTools>Process Scheduler>Process Monitor, Server List tab.The table stores the system name that identifies the server (SERVERNAME),the name of server on which the PeopleSoft Process Scheduler Server Agent was started (HOSTNAME), the last time that you refreshed the server list to display the most current information (LASTUPDDTTM),the name of the report node where the Distribution Agent posted all generated reports, logs, or trace files (DISTNODENAME), the status of the Process Scheduler server:Running, Down, or Suspended (SERVERSATUS,SERVERSTATUSDESCR), the CPU threshold percentage value specified in the server definition – CPU usage exceeds this value, the server will not schedule new requests until CPU usage drops below this amount (MAXCPU), memory threshold in percent (MINEM), the disk threshold specified in Process Scheduler configuration file (PRCSTHRESHOLD), the amount of disk space available (PRCSDISKSPACE), server load balancing option (SRVRLOADBALOPTN), the name/version of the operating system of the server (OPSYS) and some other Deamon services related information.

PSPRCSLOCK

PSPRCSLOCK – Peoplesoft Process Scheduler Lock table,contains the number of process scheduler locks (PRCSLOCK) and is used to single thread process requests and to avoid any deadlocks on the PSPRCSRQST table.

PS_SERVERNOTIFY

PS_SERVERNOTIFY – PeopleSoft Process Scheduler Notification table which can be, also, identified and updated from the menu Home>PeopleTools>Process Scheduler>Servers, Notification tab. It records the Process Scheduler name (SERVERNAME), the distribution OPRID -DISTID,the distribution id type -DISTIDTYPE (2-User ID, 3-Role Name), the options of notifying when the process scheduler errors – NOTIFYSERVERERROR, when it is down – NOTIFYWHENDOWN or when it has been started – NOTIFYWHENSTARTD, or when suspended/overloaded -NOTIFYWHENSUSP, or disabled – NOTIFYDISABLED.

PS_SERVERDEFN

PS_SERVERDEFN – PeopleSoft Process Scheduler Definition table, which can be, also, identified and updated from the menu Home>PeopleTools>Process Scheduler>Servers, Definition, Distribution and Daemon tab.This record stores the Process Scheduler name (SERVERNAME),its VERSION, its description (DESCR), the sleep time, in seconds, SLEEPTIME – the time the Process Scheduler stops searching for processes that have entered in its queue for running, therefore once every interval set in the SLEEPTIME, the process scheduler wakes up and looks for processes in”Queued” state.The generraly recommended sleeptime is 30-60 seconds and the maximum allowed is 9999 seconds.The table contains, also, the HEARTBEAT of the Process Scheduler- the interval at which the Process Scheduler Agent checks the status of the server (Running,Suspended,Down), each time this verfication is done the agent updates the field LASTUPDDTTM in the PS_SERVERDEFN record. This prevents the database from accepting more than one Process Server Agent with the same name on one or multiple servers. This table also stores the Maximum number of Application Program Interface (API) aware tasks running concurrently – MAXIAPIAWARE, the Maximum number of non Application Program Interface aware tasks running concurrently -MAXIAPIUNAWARE,the defined operating system -OPSYS (0-DOS,1-NT/Win95 Client,2-NT/Win2000,3-OS/2,4-UNIX,5-VMS,6-MPE/XL,7-OS390,9-OS/400), the distribution node name (DISTNODENAME),the Transfer System Files to Report Repository flag – TRANSFERLOGFILES (1, if checked in the PIA checkbox), the Interval for Transfer Attempt – TRANSFERINTERVAL, Maximum Transfer Retries -TRANSFERMAXRETRY, Server Load Balancing Option -SRVRLOADBALOPTN (0-Do Not Use for Load Balancing,1-Use for Load Balancing),Redistribute Workload Option – REDISTWRKOPTION (0-Do Not Redistribute, 1-Redistribute with same O/S,2-Redistribute to any O/S),the daemon enabled flag – DAEMONENABLED,the daemon servers group -DAEMONGROUP,the daemon sleep time -in minutes-DAEMONSLEEPTIME, the deamon recycle count, which recycles the deamon agent after the set number of iterations -DEAMONCYCLECNT,the deamon Process Instance -DEAMONPRCSINSTANCE, the CPU utilization treshold – MAXCPU and the Memory utilization threshold – MINMEM,both recorded as percentages.

PS_SERVEROPRTN

PS_SERVEROPRTN – PeopleSoft Process Scheduler server Operation times table, available in PT 8.4xx versions, contains the defined Process Scheduler names (SERVERNAME) and their set availability days ( established in the day of the week format with values from 0-6,Sunday is represented by 0, Monday by 1,Saturday by 6 and so on) and the start time/hour of day (STARTTIME) and the time of the day the availability ends (ENDTIME). Both STARTTIME and ENDTIME are stored at the database level as their minute value (eg: the hour 05:00 is represented in the DB as 300,23:59 as 1439 and so on).Also, the content of this table is avialble for editing and viewing from the menu Home>PeopleTools>Process Scheduler>Servers, Operation tab for the specific selected Process Scheduler name.

Process Scheduler monitoring useful script

SELECT S.SERVERNAME, X.XLATSHORTNAME,X.FIELDVALUE,cast(S.MAXCPU as varchar2(3))||’%’ MAXCPU,cast(S.PRCSDISKSPACE as varchar2(15))||’ MB’ PRCS_DISK_SPACE,TO_CHAR(S.LASTUPDDTTM,’DD-MM-YYYY HH:MI:SS’)LAST_UPDATE_TIME
FROM PSSERVERSTAT S, PSXLATITEM X
WHERE X.FIELDNAME = ‘SERVERSTATUS’
AND X.FIELDVALUE = S.SERVERSTATUS

PSPRCSRQST and PSPRCSQUE

PSPRCSRQST and PSPRCSQUE tables – when a user submits a process request to the Process Scheduler a corresponding record will be inserted in the PSPRCSRQST (Process Request) table and afterwards replicated into the PSPRCSQUE table and further acknowledged by the Process Scheduler to be processed. Therefore every “x” seconds (whatever the Sleep time is set your PS environment) 3 retrieve commands get exceuted on the PSPRCSQUE table. While the PSPRCSRQST table is used more with informational purposes to ensure that the correct data is displayed in the Process Monitor tool,the PSPRCSQUE table is the one managing the queue of processes and jobs; modifying this last table is what can detrmine a specific PS job or process to stop. Actually, the parameter that must be affected, at each process instance level, in order to generate the previously mentioned behaviour is RUNSTATUS and it controls whether or not the job is further processed by the Process Scheduler. DISTATUS is the distribution state and controls whether or not the distribution agent will pick up the job.
In order to avoid diverse Process Scheduler related problems the following tables must be always synchronized: PSPRCSRQST,PSPRCSQUE and PSPRCSPARMS.In conclusion, the values returned by the three count statements must be equal:
select count(*) from PSPRCSRQST;
select count(*) from PSPRCSQUE;
select count(*) from PSPRCSPARMS;
Also, to check if there are any incompatibilities between the fields of the above mentioned 3 tables the the following commands should be issued:
SELECT * FROM PSPRCSQUE Q WHERE NOT EXISTS (SELECT ‘N’ FROM PSPRCSRQST R WHERE R.PRCSINSTANCE = Q.PRCSINSTANCE);
SELECT * FROM PSPRCSQUE Q WHERE NOT EXISTS (SELECT ‘N’ FROM PSPRCSPARMS P WHERE P.PRCSINSTANCE = Q.PRCSINSTANCE);

Reports not Posting

2012-09-26T11:19:00.001-07:00

Troubleshooting why reports and files are not posting can be really painful.

Generally you'll be in one of two scenarios:

All reports are not posting and display not posted in the process monitor. This is generally an infrastructure issue.
A particular file or report does not post. This could be a development issue or an infrastructure issue.

So where do you start? The Administration tab in Report Manager is updated first. You'll need to know the process instance and report ID (content ID).

If you suspect an infrastructure issue, then the first course of action is to restart the relevant process scheduler(s).

Fold

Table of Contents

Report Related Tables

XML File is Invalid Error

HTTP Transfer Error

HTTP Status Code is 900

HTTP Status Code is 902

Reports not posting initially

Distribution status is N/A

Directory Creation Failed

Error 404—Not Found

Comments

Report Related Tables

Behind the scenes, the records to look at are those starting with CDM (content distribution manager). Here are the key records and the information they give you:

Record	What does it tell you?
`PS_CDM_DIST_NODE`	These are your report distribution nodes - check the configuration here if you have a system-wide reports not posting issue. Navigation: PeopleTools > Process Scheduler > Report Nodes.
`PS_CDM_AUTH`	This tells you who (users/roles) the reports were distributed to. DISTIDTYPE of 2 is user, 3 is role. You may just not be able to see the report due to security.
`PS_CDM_FILE_EXT`	These are the file extension distribution options found under PeopleTools > System Settings > Distribution File Options (tab). Are you using a new file extension? Is that configured and has it been set to display (DISPLAY_OPTION = 1)?
`PS_CDM_FILE_LIST`	This gives you a list of all files you should be able to see. Is your file in the table? What file type does it think it is - is that right? No file here means that your file probably wasn't transferred to the report repository at all.
`PS_CDM_FILTER`	These are the filter options selected in report manager by users. Does the user have a filter option that prevents them from seeing the report ?
`PS_CDM_FILTER_ARCH`	These are the filter options selected in the report manager archive tab by users
`PS_CDM_LIST`	This is probably the most useful table. It tells the process name, where the process stored its output, where that output was distributed to (if at all) and the distribution status.
`PS_CDM_LIST_ARCH`	Same as `PS_CDM_LIST` but for archived reports
`PS_CDM_LIST_PURGE`	Reports that have been purged from PeopleSoft altogether
`PS_CDM_TRANSFER`	Cases where reports were transferred between servers
`PS_CDM_TRNFR_RJCT`	Cases where reports were transferred between servers and the transfer was rejected - failed

With the information from these tables you are now ready to go looking on your process scheduler server(s).

If all looks good in the Administration tab of Report Manager, but you can't see things in the List or Explorer tabs, then you have an integration broker issue.

These are the translate values for the DISTSTATUS field (PeopleTools 8.48.15):

DISTSTATUS 0 = None
DISTSTATUS 1 = Scheduled (N/A)
DISTSTATUS 2 = Processing
DISTSTATUS 3 = Generated
DISTSTATUS 4 = Unable to Post
DISTSTATUS 5 = Posted
DISTSTATUS 6 = Delete
DISTSTATUS 7 = Posting (stuck).

XML File is Invalid Error

If you are getting errors in the message log along the lines of:

The XML file returned by the web server is invalid
XML document object creation failed

Here's a screenshot of what you might see in the message log:

It could be because you have not set the authentication option on your default local node. Find your default local node under: PeopleTools > Integration Broker > Integration Setup > Nodes (has default local node set to Y e.g. PSFT_HR). Change your authentication option to Password and enter the default user ID and their password as shown:

Once you fix this, go back to the process monitor, view the details for the relevant processes and resend the content.

Hopefully it now posts.

HTTP Transfer Error

Check the distribution agent logs for the process scheduler. If you are seeing lines like this:

(JNIUTIL): Java exception thrown: java.net.SocketException: socket closed

HTTP transfer error.

Then check your report node configuration under:
PeopleTools > Process Scheduler > Report Nodes

In particular:

Check that your URL and URI is fully qualified and includes both the server name and the domain.
You only need login information if there is web server authentication, otherwise leave this blank
If you change the URL or URI you will need to restart the appropriate process schedulers.

Also under PeopleTools > Integration Broker > Nodes

Open your default local node (e.g. PSFT_HR) - in the search page, find Local Node = 1
Confirm it is using the authentication option of password
Confirm that the user ID specified exists and has appropriate roles such as ProcessSchedulerAdmin and ReportDistAdmin
Retype the password for that user to confirm it is correct
Ensure the user's account isn't locked

HTTP Status Code is 900

If you see the following in your process message log/distribution agent log:

HTTP Status Code is: 900 (63,72)

HTTP transfer error

There is probably something wrong with your report node configuration. Browse to PeopleTools > Process Scheduler > Report Nodes, and in particular, check the connection information, such as the protocol (http/https), URI host, URI port, and URI Resource (this should beSchedulerTransfer/ps). Also confirm that the report repository location in the web profile configuration/configuration.properties of the web server is accessible and writable from the webserver.

Any changes will require at least a process scheduler restart, and perhaps a web server restart.

HTTP Status Code is 902

If you see the following in your process message log/distribution agent log:

Java exception thrown: java.lang.SecurityException: illegal URL redirect

HTTP Status Code is: 902 (63,7 2)

Navigate to PeopleTools > Integration Broker > Integration Setup > Nodes

Open the default local node (Y) (e.g. PSFT_HR):

Confirm the authentication option is Password
The default user ID is correct (and exists in the system)
The password is correct for that user ID

Navigate to PeopleTools > Security > Security Objects > Single Signon

Confirm that your default local node (e.g. PSFT_HR) is included in the trust authentication tokens issued by these nodes list.

Reports not posting initially

If reports are not posting initially, but do post after some length of time, Solution ID 660253.1 on My Oracle Support might be helpful. This involves adding the line 0 to the web.xml file on the web server.

Distribution status is N/A

One reason why the distribution status might stay at N/A for some processes is if the Transfer System Files to Report Repository check box is not set in the distribution tab of the process scheduler where the process is running.

Navigation for this is:

PeopleTools > Process Scheduler > Servers > [Distribution Tab]

A process scheduler restart might be required.

Note this is value is stored in the field TRANSFERLOGFILES in PS_SERVERDEFN.

Directory Creation Failed

If you get the following errors:

Java Exception: Error while write to file:java.lang.SecurityException: Directory Creation Failed  (6 3,49)

SchedulerTransfer Servlet error.

HTTP transfer error.

First check your report repository path is correct in the relevant web profile (and if blank there), in the configuration.properties file for your web server. Also check that the disk is not full for the relevant report repository path. Also check you have the fileauthtokenenabled.html exists in the same location as configuration.properties.

Finally check permissions - is the owner/security for the folder correct? Does it match the OS user that started the process scheduler?

Error 404—Not Found

When opening a report that has run to success and posted through view log/trace or through the report manager, the following error appears (this is for Weblogic):

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition

is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden)

can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally

configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

This is due to an incorrect value in the URL field under:
PeopleTools > Process Scheduler > Reports Nodes

For instance instead of the correct http://machinename:port/psreports/ps, I had http://machinename:port/reports/ps. Having the incorrect value (reports instead of psreports) caused this error.

PeopleSoft Character set and Multilingual

2012-09-26T11:11:00.000-07:00

Selecting and Configuring Character Sets

This chapter provides an overview of character sets and discusses how to:

Select character sets.
Convert between character sets.
Set data field length checking.
Use CJK ideographic characters in name character fields.
Detect and convert characters.

Understanding Character Sets

This section discusses:

Character sets.
Common character sets.
The Unicode standard.
Non-Unicode character sets.
Character sets across the tiers of the PeopleSoft architecture.

Character Sets

Before you install your PeopleSoft system, Oracle recommends that you choose an appropriate character set for PeopleSoft client workstations, web servers, application servers, and database servers, as well as for file attachment storage locations (that is, FTP sites, HTTP repositories, and database tables).

A character set, also known as a code page, is an ordered set of characters in which each character is mapped to a numeric index, called a codepoint. This codepoint stores character data in a computer system. Many hundreds of character sets exist. Some are international standards, maintained by the International Organization for Standardization (ISO), some are country-specific standards, and others are specific to a particular computer system vendor. Given the number of separate computers that are involved in a typical PeopleSoft installation, it is likely that your system uses several different character sets.

Common Character Sets

Although there is general agreement on the content and arrangement of most character sets, especially those that are maintained by the ISO, many different names are used by vendors and software packages for similar or identical character sets. US-ASCII encodes the basic characters and symbols that are needed to write the English language. However, US-ASCII is limited to 127 characters and cannot represent many characters that are needed by Western European languages, such as French and German, let alone ideographic languages, such as Japanese and Chinese, in which each character represents a word or concept. Many character sets, however, include all US-ASCII characters in addition to their other characters.

The following table illustrates just a few common character sets that you are likely to encounter and some of the names that are used by different vendors to refer to them:

Character Set	Description and Comments	Type	PeopleSoft and SQR Name	Oracle DBMS Name	Microsoft Windows Name
ISO 8859-1	Western European Latin-1. Contains characters that are required to represent Western European languages. However, does not include the euro symbol, the trademark (TM) symbol, or the oe ligature.	ISO	LATIN1 or ISO_8859-1	WE8ISO8859P1	CP28591
Microsoft Code Page 1252	Microsoft Code Page 1252 - Western European. Very similar to ISO 8859-1, except for the inclusion of additional characters. Includes the euro symbol, trademark (TM) symbol, and oe ligature, but using a different codepoint than ISO 8859-15.	Vendor (Microsoft)	CP1252	WE8MSWIN1252	CP1252
ISO 8859-2	Central/Eastern European Latin-2. Contains characters that are required for Central European languages, including Czech, Hungarian, and Polish. Does not include the euro symbol.	ISO	LATIN2 or ISO_8859-2	EE8ISO8859P2	CP28592
ISO 8859-15	Western European extended Latin-9. Similar to ISO 8859-1, but contains the euro symbol, oe ligature, and several characters that are required for Icelandic.	ISO	LATIN9 or ISO_8859-15	WE8ISO8859P15	CP28605
Shift-JIS	Most common Japanese character set. Defines thousands of characters for writing Japanese.	Country (Japan)	SJIS	JA16SJIS or JA16SJISTILDE	CP932
IBM CCSID 37	IBM Coded Character Set ID 37. Western European Multilingual EBCDIC-based character set.	Vendor (IBM)	EBCDIC	WE8EBCDIC37	CP1140
GB18030	Chinese national character set	Country (China)	GB18030	GB18030	GB18030

Some of these character sets, such as ISO 8859-1 and IBM CCSID 37, require only one byte to represent each character. For example, in ISO 8859-1, the hexadecimal number 61 represents the lowercase Latin letter a. However, larger character sets, such as Shift-JIS, may require more than one byte to represent each character.

The Unicode Standard

The most important consideration when dealing with character sets across a system is ensuring that all characters that you plan to represent within the PeopleSoft system exist in the character set that is used by each component of the system.

For example, if you plan to maintain Japanese characters in employee names, you must ensure that:

The character set that is used by the database system includes Japanese characters.
Each external system feeding into or out of the PeopleSoft system expects data in a character set that includes Japanese characters.
Workstations and printers are installed with fonts that include those characters.

For example, the Japanese Shift-JIS character set contains Japanese and many US-ASCII characters; it is sufficient for encoding both English data and the primary characters that are required in Japanese. However, it does not include the accented Latin characters that are needed for French, German, and other languages, so it is not a suitable character set for implementations that encompass Western European countries.

Given the sample list of common character sets in the previous table and the number of languages that are required by a typical global PeopleSoft implementation, selecting a character set can be daunting, especially when you are planning to support a large list of languages.

To simplify this situation, an industry consortium of vendors devised a universal character standard: the Unicode standard. This internationally recognized character standard represents every character that is required to write virtually every written language. The Unicode standard was developed and is maintained by the Unicode Consortium in conjunction with ISO. This standard shares the character repertoire with ISO/IEC standard 10646: the Universal Multiple-Octet Coded Character Set (UCS), also known as the Universal Character Set for short.

The PeopleSoft system uses Unicode throughout PeopleTools to simplify character handling. The PeopleSoft system allows the use of Unicode within PeopleSoft databases to enable you to maintain a single database with characters from virtually any language.

The Unicode standard and the ISO 10646 standard are available from their respective organizations.

See The Unicode Consortium: http://www.unicode.org

See International Organization for Standardization (ISO): http://www.iso.org

Unicode Encodings

Unicode defines a code space of more than one million code points (or characters). Unicode code points are referred to by writing “U+” followed by the hexadecimal number—for example, U+0000, U+0061, U+FFFF, U+27741, and so on. To manage such a large repertoire of characters, Unicode defines multiple planes each comprising 65,533 code points, or character positions. Plane 0, covering the range of U+0000 to U+FFFF, is known as the Basic Multilingual Plane (BMP) and is generally sufficient for almost all modern languages. The other planes are intended to encode extended ideographic characters, archaic scripts, and other rarely used characters (such as advanced mathematical symbols). All characters from planes outside the BMP are known as supplementary characters.

PeopleTools fully supports the use of characters from the BMP only; supplementary character support is limited to display in the browser, storage in the database, and reporting output in BI Publisher. A tool that can be used to view Unicode character properties is http://www.unicode.org/charts/unihan.html. If a character is at codepoint U+20000 or higher, it is a supplementary character.

Several different Unicode encoding forms have been standardized based on two encoding methodologies. Unicode defines these two encoding methods: the Unicode Transformation Format (UTF), and UCS. An encoding maps the Unicode code points (or perhaps a subset of code points) to sequences of code values of some fixed size. In UTF encodings, the number in the encoding name indicates the number of bits per code value; in UCS encodings, the number indicates the number of bytes per code value.

Four common encodings of Unicode are widely used:

UTF-32 — a 32-bit, fixed-width encoding; equivalent to UCS-4.
UTF-16 — a 16-bit, variable-width encoding.
UTF-8 — an 8-bit, variable-width encoding, which maximizes compatibility with ASCII.
UCS-2 — a 2-byte, fixed-width encoding; a subset of UTF-16 supporting characters in the BMP only.

Other Unicode encodings—such as, CESU-8, Java’s Modified UTF-8, UTF-1, and others—have specific, and sometimes internal, applications and are not widely used for the interchange of information.

While the PeopleSoft system currently supports only the UTF-8 and UCS-2 encodings, the following table presents a brief comparison of all four common encodings:

Encoding	Description	Min. Bytes per Char.	Max. Bytes per Char.	PeopleSoft System Usage
UTF-32	The full, 32-bit (four-byte) encoding of Unicode. Each Unicode character is represented by a four-byte number. For example, the Latin small letter a character is represented in UTF-32 hexadecimal as 0x00000061. UTF-32 was formerly called UCS-4.	4	4	None
UTF-16	An extension of UCS-2 in which the application references characters on planes other than the BMP by combining two UCS-2 code units to designate a single, non-BMP character. UCS-2 is upward compatible with UTF-16 in that each UCS-2 character is also a valid character in UTF-16. However, UTF-16 allows characters outside the BMP to be referenced. These additional characters, known as supplementary characters, require two UTF-16 code units: a low surrogate and a high surrogate, together called a surrogate pair. When no supplementary characters are present, UTF-16 is identical to UCS-2.	2	4	None
UTF-8	A transformation of Unicode that encodes each character as one to four bytes, depending on which character is being encoded. All US-ASCII characters are encoded in UTF-8 as one byte, and this byte is identical to the encoding in US-ASCII. UTF-8 data is therefore backward compatible with US-ASCII data. All characters in the BMP are encoded as one, two, or three bytes in UTF-8. Characters in other planes are encoded as four bytes in UTF-8. UTF-8 has three main advantages: it is fully US-ASCII compatible, US-ASCII data can be considered as UTF-8 data, and it does not require that all characters use two or more bytes of storage.	1	4	The PeopleSoft system uses UTF-8 for serving HTML pages in the PeopleSoft Pure Internet Architecture and for inbound and outbound XML.
UCS-2	A 2-byte (16-bit) representation of each Unicode character. As such, it can reference only 65,535 code points and is limited to characters in the BMP.	2	2	The PeopleSoft system uses UCS-2 in memory for the Microsoft Windows development tools and for the application server.

Unicode Encoding Examples

This section includes Unicode encoding examples for the following characters:

Character	Unicode Code Point	Description
a	U+0061	Latin small letter a.
ñ	U+00F1	Latin small letter ñ.
€	U+20AC	Euro symbol

The following table shows the hexadecimal representation of these characters in each of the four Unicode encodings:

Unicode Encoding	Latin Small Letter a (U+0061)	Latin Small Letter ñ (U+00F1)	€ Symbol (U+20AC)
UTF-32	0x0000006	0x000000F1	0x000020AC
UTF-16	0x0061	0x00F1	0x20AC
UTF-8	0x61	0xC3B1	0xE282AC
UCS-2	0x0061	0x00F1	0x20AC

See Also

Selecting Email Character Sets

Non-Unicode Character Sets

Although much of the PeopleSoft system runs by using Unicode, you can configure several components with a non-Unicode character set. When making these choices, you should understand the types of character sets other than Unicode that exist.

This section discusses:

Single-byte character sets (SBCSs).
Double-byte character sets (DBCSs).

Note. For the sake of terminology, some systems, such as Microsoft Windows, refer to two types of character sets: Unicode and ANSI. ANSI, in this context, refers to the American National Standards Institute, which maintains equivalent standards for many national and international standard character sets. Informally, ANSI character sets refer to non-Unicode character sets, which can be any international, national, or vendor standard character set, such as those that are discussed at the beginning of this chapter.

Single-Byte Character Sets

Most character sets use one byte to represent each character and are therefore known as SBCSs. These character sets are relatively simple and can represent up to 255 unique characters. Examples of SBCSs are ISO 8859-1 (Latin1), ISO 8859-2 (Latin2), Microsoft CP1252 (similar to Latin1, but vendor specific), and IBM CCSID 37.

Double-Byte Character Sets

DBCSs use one or two bytes to represent each character and are typically used for writing ideographic scripts, such as Japanese, Chinese, and Korean. Most DBCSs allow a mix of one-byte and two-byte characters, so you cannot assume an even-string byte length. Encoding with a mix of one- and two-byte characters is also known as variable-width encoding, and such a character set is sometimes referred to as a multi-byte character set (MBCS).

The PeopleSoft system supports two types of DBCSs:

Nonshifting
Shifting

The difference between these types of DBCSs is in the way in which the system determines whether a particular byte represents one character or is part of a two-byte character.

Nonshifting DBCSs

Nonshifting DBCSs use ranges of codepoints, specified by the character set definition, to determine whether a particular byte represents one character or is part of a two-byte character.

In nonshifting DBCSs, the two bytes that are used to form a character are called lead bytes and trail bytes. The lead byte is the first in a two-byte character, and the trail byte is the last. Nonshifting DBCSs differentiate single-byte characters from double-byte characters by the numerical value of the lead byte. For example, in the Japanese Shift-JIS encoding, if a byte is in the range 0x81-0x9F or 0xE0-0xFC, then it is a lead byte and must be paired with the following byte to form a complete character.

The most popular client-side Japanese code page, Shift-JIS, uses this lead byte/trail byte encoding scheme, as do most Microsoft Windows and Unix/Linux ASCII-based double-byte character sets that represent Chinese, Japanese, and Korean characters. Contrary to its name, Shift-JIS is a nonshifting double-byte character set.

Shifting DBCSs

A shifting DBCS is another double-byte encoding scheme in use that doesn’t use the lead byte and trail byte concept. The IBM DB2 UDB for OS/390 and z/OS EBCDIC-based Japanese, Chinese, and Korean character sets use this shifting encoding scheme.

Instead of reserving a range of bytes as lead bytes, shifting DBCSs always keep track of whether they are in double-byte or single-byte mode. In double-byte mode, every two bytes form a character. In single-byte mode, every byte is a character in itself. To track what mode the character set is in, the system uses shifting characters. By default, the character set is expected as single-byte data. As soon as a double-byte character needs to be represented, a shift-in byte is added to the string. From this point on, all characters are expected to be two bytes. This continues until a shift-out byte is detected, which indicates that the character set should go back to single-byte per characters.

This scheme, while more complex than the lead byte and trail byte scheme, provides greater performance, because the system always knows how many bytes should be in any particular character. Unfortunately, it also increases the length of the string. For example, a character string that comprises a mixture of single-byte and double-byte characters could require more space to store in a shifting character set because you need to include the shift-in and shift-out bytes, as well as the data itself.

Important! In the PeopleSoft system, shifting DBCSs have limited usage, such as for file I/O, and are not supported for use as a database character set.

Character Sets Across the Tiers of the PeopleSoft Architecture

PeopleSoft installations include multiple components, each of which must be able to handle differing character sets.

PeopleSoft application servers and clients (for example, the PeopleTools development environment and PeopleSoft Pure Internet Architecture pages) use Unicode exclusively and do not rely on other character sets to represent and process data. However, depending on your environment, not all system components support Unicode-encoded data. Therefore, you might not be able to run all parts of your system in Unicode. For example, some database platforms and third-party products do not support Unicode. The following table illustrates support for Unicode in the PeopleSoft system.

Tier	Component	Unicode Support
Client	PeopleTools development environment	Yes
Client	PeopleSoft Pure Internet Architecture pages	Yes
Web server	Web server	Yes
Application server	Application server	Yes
Database server	Non-Unicode DB (Western European or Japanese)	No
Database server	Unicode DB	Yes
File attachment storage location	FTP server	Yes
	HTTP repository	Yes
	Database table	See the previous entry for the database server tier

Examples of how to configure these tiers are provided in this chapter.

See Understanding Character Set Selection.

In addition to the tiers listed in the previous table, PeopleTools enables you to configure these system components to use other character sets:

COBOL.

The character set that is used for PeopleSoft COBOL processing must match the character set of the database. If you created a Unicode database for the PeopleSoft implementation, you must also run COBOL in Unicode.

Direct file I/O operations.

All direct file I/O operations in PeopleTools, including file layout objects, trace and log files, and file operations from Structured Query Report (SQR) programs can be performed in Unicode or any supported non-Unicode character set. This is useful in situations in which you must interface with an external system that does not support Unicode.

Third-party products that are non-Unicode compliant.

Some third-party products that are supported by PeopleTools do not yet support Unicode. In this case, PeopleTools converts application data to a specific, non-Unicode character set before communicating with these tools. Check the product documentation for your third-party application regarding Unicode compliance before determining how the application and the PeopleSoft system will interoperate.

When Unicode is not used for any of these types of operations or data storage, the PeopleSoft system transparently handles the conversion from Unicode to a non-Unicode character set. The non-Unicode character set that is used depends on several settings, which are discussed in detail later in this chapter.

PSCHARSETS Table

The character sets that the PeopleSoft system supports are defined in the PSCHARSETS table. The following table lists these character sets and the names by which they may be referred to in PeopleSoft applications. You may need to know the correct character set name to use in several situations including:

In PeopleCode programs for manipulating file layout objects.
In the Unix/Linux application server configuration to determine the default, non-Unicode character set for log files, trace files, and operating system interfaces.
When creating your database.

Refer to your hardware and software requirements guide for details about the character sets that are supported for your database platform.

PSCHARSETS Character Set Name	Description and Comments	Character Set Type
ANSI	Current ANSI-based code page. Not really a character set, but causes the system to use the default non-Unicode character set of the host operating system.	SBCS or DBCS, depending on the host operating system.
ASCII	7–bit US-ASCII	SBCS
Big5	Big5 (Traditional Chinese)	Nonshifting DBCS
CCSID1027	IBM EBCDIC 1027 (Japanese-Latin)	SBCS
CCSID1047	IBM EBCDIC 1047 (Latin1)	SBCS
CCSID290¹	IBM EBCDIC 290 (Katakana)	SBCS
CCSID300¹	IBM EBCDIC 300 (Kanji)	Nonshifting DBCS
CCSID930²	IBM EBCDIC 930 (Kana-Kanji)	Shifting DBCS
CCSID935²	IBM EBCDIC 935 (Simplified Chinese)	Shifting DBCS
CCSID937²	IBM EBCDIC 937 (Traditional Chinese)	Shifting DBCS
CCSID939²	IBM EBCDIC 939 (Latin-Kanji)	Shifting DBCS
CCSID942	IBM EBCDIC 942 (Japanese PC)	Nonshifting DBCS
CP1026	Windows 1026 (EBCDIC)	SBCS
CP1250	Windows 1250 (Eastern Europe)	SBCS
CP1251	Windows 1251 (Cyrillic)	SBCS
CP1252	Windows 1252 (Western Europe)	SBCS
CP1253	Windows 1253 (Greek)	SBCS
CP1254	Windows 1254 (Turkish)	SBCS
CP1255	Windows 1255 (Hebrew)	SBCS
CP1256	Windows 1256 (Arabic)	SBCS
CP1257	Windows 1257 (Baltic)	SBCS
CP1258	Windows 1258 (Vietnamese)	SBCS
CP1361	Windows 1361 (Korean Johab)	SBCS
CP437	MS-DOS 437 (U.S.)	SBCS
CP500	Windows 500 (EBCDIC 500V1)	SBCS
CP708	Windows 708 (Arabic - ASMO708)	SBCS
CP720	Windows 720 (Arabic - ASMO)	SBCS
CP737	Windows 737 (Greek - 437G)	SBCS
CP775	Windows 775 (Baltic)	SBCS
CP850	MS-DOS 850 (Western Europe)	SBCS
CP852	MS-DOS 852 (Eastern Europe)	SBCS
CP855	MS-DOS 855 (IBM Cyrillic)	SBCS
CP857	MS-DOS 857 (IBM Turkish)	SBCS
CP860	MS-DOS 860 (IBM Portuguese)	SBCS
CP861	MS-DOS 861 (Icelandic)	SBCS
CP862	MS-DOS 862 (Hebrew)	SBCS
CP863	MS-DOS 863 (Canadian French)	SBCS
CP864	MS-DOS 864 (Arabic)	SBCS
CP865	MS-DOS 865 (Nordic)	SBCS
CP866	MS-DOS 866 (Russian)	SBCS
CP869	MS-DOS 869 (Modern Greek)	SBCS
CP870	Windows 870	SBCS
CP874	Windows 874 (Thai)	SBCS
CP875	Windows 875 (EBCDIC)	SBCS
CP932	Windows 932 (Japanese)	Nonshifting DBCS
CP936	Windows 936 (Simplified Chinese)	Nonshifting DBCS
CP949	Windows 949 (Korean)	Nonshifting DBCS
CP950	Windows 950 (Traditional Chinese)	Nonshifting DBCS
EBCDIC	IBM EBCDIC CCSID37 (USA)	SBCS
EUC-JP	Extended UNIX code (Japanese)	Nonshifting DBCS
EUC-KR	Extended UNIX code (Korean)	Nonshifting DBCS
EUC-TW	Extended UNIX code (Taiwan)	Nonshifting DBCS
EUC-TW-1986	Extended UNIX code (TW-1986)	Nonshifting DBCS
GB12345	GB 2312 (Simplified Chinese)	Nonshifting DBCS
GB18030	GB18030 (Simplified Chinese)	Nonshifting DBCS
GB2312	GB 2312 (Simplified Chinese)	Nonshifting DBCS
HKSCS	Hong Kong Supplementary Character Set	Nonshifting DBCS
ISO-2022-JP^{2, 3}	ISO-2022-JP Japanese	Shifting DBCS
ISO-2022-KR²	ISO-2022-JP Korean	Shifting DBCS
ISO_8859-1	ISO 8859-1 (Latin1)	SBCS
ISO_8859-10	ISO 8859-10 (Latin6)	SBCS
ISO_8859-11	ISO 8859-11 (Thai)	SBCS
ISO_8859-14	ISO 8859-14 (Latin8)	SBCS
ISO_8859-15	ISO 8859-15 (Latin9/Latin0)	SBCS
ISO_8859-2	ISO 8859-2 (Latin2)	SBCS
ISO_8859-3	ISO 8859-3 (Latin3)	SBCS
ISO_8859-4	ISO 8859-4 (Latin4)	SBCS
ISO_8859-5	ISO 8859-5 (Cyrillic)	SBCS
ISO_8859-6	ISO 8859-6 (Arabic)	SBCS
ISO_8859-7	ISO 8859-7 (Greek)	SBCS
ISO_8859-8	ISO 8859-8 (Hebrew)	SBCS
ISO_8859-9	ISO 8859-9 (Latin5)	SBCS
JIS_X0201¹	Japanese Half-width Katakana	Nonshifting DBCS
JIS_X_0208	Japanese Kanji	Nonshifting DBCS
Java	Java (Unicode encoding)	Unicode
Johab	Johab (Korean)	Nonshifting DBCS
Shift_JIS	Shift-JIS (Japanese)	Nonshifting DBCS
UCS2	Unicode UCS-2	Unicode
UTF-8	Unicode UTF-8	Unicode
UTF7¹	Unicode UTF-7. (An outdated Unicode 7-bit clean transformation that is sometimes used for email that must pass through gateways that do not support 8-bit characters.)	Unicode
UTF8	Unicode UTF-8	Unicode
UTF8BOM	Unicode UTF-8 with BOM (byte-order mark)	Unicode

¹ Not commonly used.

² In the PeopleSoft system, shifting DBCSs have limited usage, such as for file I/O, and are not supported for use as a database character set.

³ To use certain Windows-31J (also known as Microsoft CP932) characters in incoming or outgoing email messages, you must complete additional configuration of your web server (incoming email) and application server or PeopleSoft Process Scheduler (outgoing email).

See Selecting Email Character Sets.

This PeopleBook also contains information about supported character set encodings for globalization when using SQR for PeopleSoft.

See SQR for PeopleSoft-Supported Character Set Encodings.

See Also

PeopleTools 8.52 Hardware and Software Requirements Guide

For more information and code charts for Microsoft code pages, visit http://msdn.microsoft.com/en-us/goglobal/bb964654.aspx

For more information and code charts for Unicode, visit http://www.unicode.org

Selecting Character Sets

This section provides an overview of selecting character sets and discuses how to:

Select database character sets.
Select application server character sets.
Select and manage client workstation character sets.
Select email character sets.

See Also

Understanding Character Sets

Understanding Character Set Selection

When configuring your PeopleSoft system, you need to consider the character set (or sets) that will be in use on the following tiers:

Client.
Web server.
Application server.
Database server.
File attachment storage location (FTP site, HTTP repository, or database table).
Email.

Some operations of your PeopleSoft system require the interaction of multiple tiers. For example, the uploading of a file attachment involves the browser on the client, the web server, the application server, the database server, and ultimately the file attachment storage location. To ensure the correct transfer of data and files between these tiers, Oracle recommends configuring each server tier (web server, application server, database server, and file storage location) to use the same character set as follows:

If your PeopleSoft system operates in a multi-language environment, use a UTF-8 character set on each server tier.
If your PeopleSoft system operates in a single language environment, use the native language character set for that language on each server tier. Alternatively, you could use a UTF-8 character set on each server tier, which would provide more flexibility than using the native language character set.

Clients can always be configured to use the native language of the user of that workstation or browser.

The following table depicts example character set settings across all tiers for three typical configurations—a multi-language environment, a single language environment (Western), and a single language environment (non-Western).

Note. This table shows examples for a particular combination of languages and platforms; your specific configuration could differ.

Tier (Platform)	Multi-Language	Single Language (Western: French)	Single Language (Non-Western: Japanese)	Where to Check
Client (Windows)	Any (for example, English uses CP1252).	French (uses CP1252).	Japanese (uses CP932).	Start, Settings, Control Panel, Regional Options
Web server (Linux) – Shell processes	en_US.utf8	fr_FR.iso88915	ja_JP.sjis	locale command
Application server (Linux) – PSAPPSRV processes	utf-8	latin15	sjis	psappsrv.cfg [PSTOOLS] Character Set
Application server (Linux) – Email processes	utf-8	utf-8	utf-8	psappsrv.cfg [SMTP Settings] SMTP Character Set
Application server (Linux) – Shell processes	en_US.utf8	fr_FR.iso88915	ja_JP.sjis	locale command
Database server (Oracle)	AL32UTF8	WE8ISO885915	JS16SJISTILDE	NLS_DATABASE_PARAMETERS
File attachments: FTP site⁴ (Linux) – Shell processes	en_US.utf8	fr_FR.iso88915	ja_JP.sjis	locale command

⁴ For file attachments, if the storage location is a database table or an HTTP repository, then the configuration of one of the other server tiers will also configure the character set in use for a file attachment storage location on that tier. Specifically, a database table as a storage location depends on the settings for the database server; an HTTP file repository as a storage location depends on the web server settings if the HTTP repository is deployed on the web server. In the preceding table, information is provided for an FTP site as a storage location only because an FTP site can be deployed independently from the other server tiers.

Failure to configure character sets correctly across server tiers can result in garbled file names.

See Also

Attachments with non-ASCII File Names

Selecting Database Character Sets

The primary character set decision that you must make when installing a PeopleSoft implementation is which character set to use for the database system. Ideally, all databases are encoded in Unicode; however, in some cases Unicode requires several bytes to represent each character when only one byte may be required in a non-Unicode character set. Therefore, the PeopleSoft system enables you to use certain non-Unicode character sets for the database.

By using a Unicode encoded database, you can maintain a single database with data in any combination of languages. A single PeopleSoft application server can serve multiple users connecting to the mixed-language database, regardless of the language or character set of those users’ client machines. The only restriction on a user’s ability to access mixed-language data is the capability of the user’s client workstation to interpret, display, and accept keyboard entry of the characters from the various languages.

Most language or region-specific non-Unicode character sets provide sufficient characters for only a few languages. If you create a non-Unicode database, you must ensure that all of the characters for all of the languages that you plan on using can be represented in the character set that you choose.

The following table lists whether a PeopleSoft language is supported in a Unicode or non-Unicode database character set:

Language Code	Language	Database Character Set
ARA	Arabic	Unicode
BUL	Bulgarian	Unicode
CFR	Canadian French	Unicode or non-Unicode
CRO	Croatian	Unicode
CZE	Czech	Unicode
DAN	Danish	Unicode or non-Unicode
DUT	Dutch	Unicode or non-Unicode
ENG	US English	Unicode or non-Unicode
FIN	Finnish	Unicode or non-Unicode
ESP	Spanish	Unicode or non-Unicode
FRA	French	Unicode or non-Unicode
GER	German	Unicode or non-Unicode
HUN	Hungarian	Unicode
ITA	Italian	Unicode or non-Unicode
JPN	Japanese	Unicode or non-Unicode
KOR	Korean	Unicode
NOR	Norwegian	Unicode or non-Unicode
POL	Polish	Unicode
POR	Portuguese	Unicode or non-Unicode
ROM	Romanian	Unicode
RUS	Russian	Unicode
SER	Serbian	Unicode
SLK	Slovak	Unicode
SLV	Slovenian	Unicode
SVE	Swedish	Unicode or non-Unicode
THA	Thai	Unicode
UKE	English	Unicode or non-Unicode
ZHS	Simplified Chinese	Unicode
ZHT	Traditional Chinese	Unicode

Depending on the data that you store and how the database stores Unicode characters, a Unicode database can be significantly larger than a non-Unicode database. However, only the storage of character data is affected; the space that is required for non-character data, such as numbers and dates (which are stored by the database system as numbers), is not affected.

Depending on the database platform, you can use one of the four character set types (SBCS, nonshifting DBCS, shifting DBCS, or Unicode) when creating the database. However, the number of characters that you can store in each column is affected greatly by the type of character set that you choose for the database encoding.

See Also

The Unicode Standard

Non-Unicode Character Sets

PeopleTools 8.52 Hardware and Software Requirements Guide

PeopleTools 8.52 installation guide for your database platform

Your operating system and database guides

Selecting Application Server Character Sets

All data that is stored in memory and processed by the PeopleTools application server is held in Unicode. However, the application server allows files on the server (created through PeopleCode file layout objects) and log and trace files to be Unicode or non-Unicode. Although the PeopleSoft application server uses Unicode internally for all data processing, it can create these files in Unicode or in a non-Unicode character set.

Each PeopleSoft application server is configured with a default non-Unicode character set. If a file operation must create a non-Unicode file, this character set is used, unless another character set is explicitly specified in the file operation. For example, if you create a file layout object to write a non-Unicode file, but you don’t specify in which character set the file should be created, the default non-Unicode character set of the application server is used.

Microsoft Windows enables you to change the default character set of the system, although as installed, the default character set matches the default locale of the Microsoft Windows installation. To change the system default locale (and therefore the character set), on Microsoft Windows servers, use the Control Panel’s Regional Options menu. In the Language settings for the system section, click the Set Default button.

When running on Unix/Linux, the PeopleSoft application server enables you to specify the default non-Unicode character set in the application server’s configuration file, which you select by using the PSADMIN tool. Any valid PeopleSoft character set with a character set type of SBCS or nonshifting DBCS is a valid default non-Unicode character set for PeopleSoft application servers that run on Unix/Linux.

Selecting and Managing Client Workstation Character Sets

You must consider the client components of PeopleTools when you are planning your language strategy. The requirements for language support on client workstations are different, depending on whether you are using the PeopleSoft Pure Internet Architecture or the PeopleTools development tools for Microsoft Windows.

This section discusses:

Character sets and fonts in the PeopleSoft Pure Internet Architecture.
Fonts and the PeopleTools development environment.
Input methods.

Character Sets and Fonts in the PeopleSoft Pure Internet Architecture

The PeopleSoft Pure Internet Architecture serves all HTML pages in the UTF-8 encoding of Unicode. This encoding is recognized automatically by the web browser, because the encoding of the page is announced in the HTTP header when the browser communicates with the web server. All browsers supported by PeopleTools can support UTF-8 encoded HTML pages.

However, the browser needs other components to correctly display and enter the vast array of characters that are available in Unicode. Specifically, you need appropriate fonts to display the various scripts in which you expect data to be maintained. In addition, you might need alternate keyboard layouts or, in the case of ideographic scripts such as Chinese, Japanese, and Korean, you need input method editors (IMEs) to convert sequences of keystrokes into ideographs. The requirement for alternate keyboard and IMEs is the same for both the PeopleSoft Pure Internet Architecture and the PeopleTools development environment.

Not all fonts contain a full repertoire of Unicode characters, because many fonts are tailored to address a specific list of languages and contain only the glyphs that are required by those languages. If you try to view Unicode data with a font that does not contain the appropriate characters for the displayed language, you will most likely see square boxes in place of the appropriate characters. The data has not been corrupted; there is just no glyph available in the current font for the character that the system is trying to display. For this reason, you may need to license or configure several fonts for a global PeopleSoft system.

The PeopleSoft Pure Internet Architecture includes a set of style sheets, defined with Application Designer, that determine the font that is used to display HTML pages. In some cases, the application data may contain characters that are not present in this font and that require a different font.

The Albany TrueType fonts shipped in the PS_HOME\fonts\truetype directory support all of the languages supported by the PeopleSoft system. Alternatively, you may need to obtain and configure fonts that contain the characters for the languages that you are planning to use, if your workstations are not already configured with these fonts. Obtain fonts from the following sources:

Many Microsoft Windows and other operating system applications are packaged with Unicode fonts containing glyphs covering a large range of languages.

Microsoft Office is packaged with several fonts containing a large portion of the characters in Unicode, including the Microsoft Sans Serif font. Use these fonts in the PeopleSoft Pure Internet Architecture by specifying them in the Application Designer style sheet definitions or by following the browser-specific instructions in this section.

Many public domain fonts exist that contain a large character repertoire for use in web browsers. The unifont.org web site is one location to get additional information on public domain fonts.

See http://www.unifont.org/fontguide/

Several font foundries license fonts for individual or corporate use.

Some of these foundries include Monotype, Bitstream, and Tiro Typeworks.

Depending on your browser, you can also download fonts from your browser’s manufacturer.

To enable the display of GB18030 characters, you can use either the SimSun-18030 font from Microsoft or the Albany fonts shipped in the PS_HOME\fonts directory. Both of these fonts have glyphs for the supported ranges of the GB18030 character set.

Fonts and the PeopleTools Development Environment

PeopleTools enables you to specify the font that is used for all graphical components for all PeopleTools modules that run on Windows, such as Application Designer. Use these methods to specify fonts:

Configuration Manager font setting (Display tab)

This setting affects the font that is used by all of the designer components of PeopleTools, including all of the text that is contained in the Microsoft Windows resource files

See Translating PeopleTools.

Changing this font setting may be necessary if your workstation’s default locale does not contain the characters that are used for the language that you are attempting to display or maintain. For example, if you are attempting to view Japanese characters on an English Microsoft Windows workstation, you can change the PeopleSoft Configuration Manager font setting to select a font that contains the characters for the language that you are trying to display.

The Albany TrueType fonts shipped in PS_HOME\fonts directory support all of the languages supported by the PeopleSoft system.

In addition, several fonts that are shipped with Microsoft Windows and Microsoft Office, including Arial Unicode MS and Microsoft Sans Serif, contain a large number of glyphs covering most of the languages that are supported by the Unicode character set. Microsoft Windows can also be configured with fonts for most worldwide languages by selecting the required languages under the Regional Settings Control Panel menu.

PeopleCode font

The PeopleCode editor in Application Designer also enables you to select a font for character display in the editor’s window itself. This is useful if the PeopleCode programs that you are working on contain Unicode characters. To set the font in Application Designer, open the PeopleCode program, select Edit, Display Fonts and Color.

Input Methods

If users will enter translated data by using PeopleSoft Pure Internet Architecture or the PeopleTools development environment, you must ensure that an appropriate keyboard layout or input method editor is installed on the workstation.

Most alphabetic languages can be typed by using a relatively simple keyboard layout. Several specialized keyboard layouts exist for most languages; configure these keyboard layouts through your operating system. For example, a Spanish keyboard layout contains keys for the n-tilde character (ñ) and several other accented characters.

However, certain PeopleSoft hot keys do not work as expected on alternate, non-U.S. keyboard layouts. For example, Alt+', Alt+\, and Alt+/ do not produce the expected results on the AZERTY keyboard. This occurs because some keys on non-U.S. keyboards produce different key codes than the same key on a U.S. keyboard (also known as a QWERTY keyboard).

A solution to this problem can be found in the appendix.

See PeopleSoft Hot Keys Do Not Function As Expected on a non-U.S. Keyboard.

There are several ways of entering these characters by using a nonlocalized keyboard. Your operating system manual can help you use specialized keyboard layouts, such as the English international layout, which enables you to enter accented characters by using two keystrokes. The Microsoft web site contains information about keyboards that are supported by Microsoft Windows and instructions for installing and configuring Windows keyboard layouts.

Ideographic languages, such as Chinese, Japanese, and Korean, require the use of a front-end processor to intercept multiple keyboard strokes and transform them into an ideographic character. These are known as IMEs, and they must be installed on each workstation where you plan to enter the ideographic languages.

Most localized versions of operating systems for these languages come preconfigured with IMEs that are appropriate for the language that is supported by the operating system. But on systems where the default locale is not Chinese, Japanese, or Korean, you may need to configure or license an IME from a third-party vendor. The PeopleSoft Pure Internet Architecture supports any IME that is supported by your browser. The designer tools in Microsoft Windows support all standard Microsoft IMEs.

Selecting Email Character Sets

The PeopleSoft system supports UTF-8 for outgoing Simple Mail Transfer Protocol (SMTP) email messages from PeopleTools application servers. In addition, the PeopleSoft system supports several additional encodings for outgoing email.

PeopleSoft application servers support the following for outgoing email:

UTF-8 (default).
ISO-2022-JP, Shift_JIS, EUC-JP (for Japanese).
ISO-2022-KR, EUC-KR (for Korean).
GBK, Big5, GB18030 (for Chinese).

Specifying Email Character Sets

You specify an email character set in the SMTPCharacterSet parameter in the application server configuration file, psappsrv.cfg. By default, the SMTPCharacterSet parameter is set to UTF-8.

Note. You should specify a value for the SMTPCharacterSet. If you do not specify a value for the parameter, email is sent as-is, with no encoding. Leave the parameter set to the default value of UTF-8 if you are not certain about which value to use.

For example, to use ISO-2022-JP encoding for outgoing SMTP mail, in the psappsrv.cfg file, set the SMTPCharacterSet parameter to ISO-2022-JP, as shown in the following example:

[SMTP Setting]

...

SMTPCharacterSet=ISO-2022-JP

SMTPEncodingDLL=blank

You can also write your own SMTPEncodingDLL modules, if necessary.

Using Extended Japanese Characters

To use certain Windows-31J (also known as Microsoft CP932) characters—specifically, NEC special characters, NEC-selected IBM extended characters, IBM extension characters, and user-defined characters—in incoming or outgoing email messages with the ISO-2022-JP Japanese character set, you must complete additional configuration of your web server (for incoming email) and application server or PeopleSoft Process Scheduler (for outgoing email).

For incoming email on the web server, the following JVM setting must be added to the JAVA_OPTIONS_WIN32 parameter in the setenv.cmd file:

SET JAVA_OPTIONS_WIN32=

"-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP"

For outgoing email on the application server or PeopleSoft Process Scheduler, the following JVM option must be added to either the psappsrv.cfg file or the psprcs.cfg file depending on whether the application server or an AE program, respectively, will be handling outgoing email messages. JVM options are set in the PSTOOLS section of the file:

[PSTOOLS]

...

JavaVM Options=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP

In addition, your web server, application server, and PeopleSoft Process Scheduler must be using a Java Runtime Environment (JRE) or Java Development Kit (JDK) that is supported for extended Japanese characters. See the release notes on My Oracle Support website.

See My Oracle Support, Knowledge, Tools and Technology, Documentation, Release Notes.

Converting Between Character Sets

You can use PeopleCode file functions to convert files or text strings from one supported PeopleSoft character set to another supported PeopleSoft character set.

PeopleCode operations such as GetFile, GetTempFile, Open, ReadLine, and WriteLine automatically account for the file encoding. Therefore, you can:

Convert from a Unicode character set to a non-Unicode character set.
Convert from a non-Unicode character set to a Unicode character set.
Automatically handle the Unicode BOM if it is present or needs to be written.

When using a character set such as UCS2 or UTF8BOM, the BOM is added at the beginning of the file contents when using WriteLine. The BOM is skipped when read by the ReadLine PeopleCode function, and not interpreted as a text character. Since the BOM is recognised as meta data and not part of the file's text the BOM is not added to file contents when writing in a non-Unicode character set with the WriteLine PeopleCode function.

In the following example PeopleCode program, the FileEncodingConversion function handles converting files from one supported character set to another. In the body of the program, the function is called to convert from the UTF8BOM character set to the UCS2 character set.:

REM this function, FileEncodingConversion() converts character encoding of

input file to another of output file.

REM an example of how to call the function is at the end of this file.

Local File &InputFile, &OutputFile;

Local string &InputDirFile, &OutputDirFile, &InputFilename, &OutputFilename;

Local string &sDirSep, &LogLine;

Local array of string &FIleEncoding;

Local boolean &ret;

Function FileEncodingConversion(&InputEncoding, &InputDirectoryFile,

&OutputEncoding, &OutputDirectoryFile) Returns boolean

&InputFile = GetFile(&InputDirectoryFile, "R", &InputEncoding,

%FilePath_Absolute);

&OutputFile = GetFile(&OutputDirectoryFile, "W", &OutputEncoding,

%FilePath_Absolute);

If &InputFile.IsOpen And

&OutputFile.IsOpen Then

While (&InputFile.readline(&LogLine))

&OutputFile.Writeline(&LogLine);

End-While;

&InputFile.Close();

&OutputFile.Close();

Return True;

Else

If &InputFile = Null Then

WinMessage("Error: PeopleCode: File Encoding I/O: " | "Failed to

open: " | &InputFile.Name);

Else

If &OutputFile = Null Then

WinMessage("Error: PeopleCode: File Encoding I/O: " | "Failed

to open:" | &OutputFile.Name);

End-If;

Return False;

End-If;

End-Function;

/*-----------------------------------------------------------------------*/

/* Function IsUnix */

/* check if OS = Unix */

/*-----------------------------------------------------------------------*/

Function IsUnix Returns boolean

&DummyFile = GetFile("/bin/sh", "E", %FilePath_Absolute);

If &DummyFile.IsOpen Then;

&DummyFile.Close();

Return True;

Else;

Return False;

End-If;

End-Function;

REM test the function above;

&FIleEncoding = CreateArray("UTF8BOM", "UCS2", "SJIS", "GB18030", "UTF8", ⇒

"a", "u");

REM WinMessage("ret: " | &ret);

If IsUnix() Then

/* for UNIX */

&ret = FileEncodingConversion(&FIleEncoding [1], "/home/FS_" |

&FIleEncoding [1] | ".txt", &FIleEncoding [2], "/home/BEFORE/FS_PCode_" | ⇒

&FIleEncoding [1] | "_to_" | &FIleEncoding [2] | ".txt");

Else

/* for WINDWOS */

&ret = FileEncodingConversion(&FIleEncoding [1], "D:\TMP\FS_" |

&FIleEncoding [1] | ".TXT", &FIleEncoding [2], "D:\TMP\AFTER\FS_PCode_" |

&FIleEncoding [1] | "_to_" | &FIleEncoding [2] | ".TXT");

End-If

Setting Data Field Length Checking

This section provides overviews of Application Designer field length semantics and field length checking for non-Unicode databases and discusses how to enable or disable data field length checking.

Understanding Application Designer Field Length Semantics

The database character set determines the way that PeopleTools interprets the column length that is defined in Application Designer.

If you create a Unicode database, the field length, as shown in Application Designer, indicates the maximum number of Unicode BMP characters that are permitted in the field, regardless of the Unicode encoding that is used by the database. Some database platforms, such as Oracle with byte semantics, use byte lengths to measure column sizes when operating in a Unicode database, while others use character lengths.

When the database uses byte-sized column lengths, the PeopleSoft system sizes the database columns based on the worst-case ratio between bytes and characters in the Unicode encoding that is used by your database. For example, if the AL32UTF8 character set is used by Oracle with byte semantics, the worst-case character-to-byte ratio when running against an Oracle Unicode database is 1:3. So, column size is tripled when creating a Unicode database on Oracle. A field that is defined in Application Designer as a CHAR(10) is created on an Oracle Unicode database with a type of VARCHAR2(30). This tripling of the maximum column size does not affect the actual size of the database, because variable length character fields do not reserve space in the database.

Other database platforms use character-based column lengths whose sizes represent the maximum number of Unicode characters instead of bytes that may be stored. Examples of this implementation are the NCHAR data type in Microsoft SQL Server and the GRAPHIC data type in DB2 UDB for Linux, Unix, and Microsoft Windows.

If you create a non-Unicode database, the field length in Application Designer represents the number of bytes that are permitted in the field, based on the character set that you used to create the database. Therefore, a PeopleSoft Unicode database enables you significantly more space for character data within the database when dealing with ideographic languages, such as Japanese, that require more than one byte storage per character.

The following tables show some of the possible database encodings for database platforms that the PeopleSoft system supports in Unicode and DBCS and their effects on database column sizes. Each table shows the database representation and the worst case number of characters allowed in the character field for a character field defined in Application Designer with a length of 10.

This table shows the information for an Oracle database with byte semantics (used by PeopleSoft 8.9 applications and earlier):

Database Character Set	Database Representation	Number of Characters
Unicode (AL32UTF8)	VARCHAR2(30)	10
Any SBCS	VARCHAR2(10)	10
Shift-JIS (JA16SJIS or JA16SJISTILDE)	VARCHAR2(10)	5

This table shows the information for an Oracle with character semantics (used by PeopleSoft 9.0 applications and later):

Database Character Set	Database Representation	Number of Characters
Unicode (AL32UTF8)	VARCHAR2(10)	10
Any SBCS	VARCHAR2(10)	10
Shift-JIS (JA16SJIS or JA16SJISTILDE)	VARCHAR2(10)	10

This table shows the information for an Microsoft SQL Server database with VARCHAR semantics:

Database Character Set	Database Representation	Number of Characters
Unicode (UCS-2)	NVARCHAR(10)	10
Any SBCS	VARCHAR(10)	10
Shift-JIS (CP932)	VARCHAR(10)	5

This table shows the information for a Microsoft SQL Server database with CHAR semantics:

Database Character Set	Database Representation	Number of Characters
Unicode (UCS-2)	NCHAR(10)	10
Any SBCS	CHAR(10)	10
Shift-JIS (CP932)	CHAR(10)	5

This table shows the information for a DB2 UDB for OS/390 and z/OS database:

Database Character Set	Database Representation	Number of Characters
Any SBCS	CHAR(10)	10
Shifting DBCS (CCSID 930/939)	CHAR(10)	4 (4 x 2 byte characters, plus shift-in & shift-out bytes)

This table shows the information for all other databases:

Database Character Set	Database Representation	Number of Characters
Any SBCS	CHAR(10)	10

Understanding Field Length Checking for Non-Unicode Databases

The maximum number of characters that are permitted in a PeopleSoft field varies, depending on the character set of the database. Because all components of PeopleTools use Unicode for internal storage, by default, field length checking occurs in terms of Unicode character counts. This calculation is appropriate for Unicode databases and for any SBCS databases.

However, if you are using a non-Unicode DBCS, special length checking must occur each time you move off a field to ensure that the string that you entered fits in the database column when the string is converted to the database’s character set.

For graphically sizing page fields, PeopleTools uses the Unicode length of the field as defined in Application Designer. For example, if a field is defined in Application Designer as a 10-character field, page fields in both the PeopleSoft Pure Internet Architecture and the PeopleTools clients for Microsoft Windows allow 10 characters to be displayed unless manually resized by the developer.

However, if the database is encoded in a non-Unicode DBCS character set, such as Japanese Shift-JIS, special length validation must occur because the database column size is created relative to a byte count, not to a character count as is used by the simple field length validation.

For example, if a user enters 10 Japanese characters into a field that is defined as CHAR(10) in Application Designer, this string needs 20 bytes of storage in a nonshifting DBCS character set and 22 bytes of storage in a shifting character set. This 10-character input would fail insertion in both of these databases.

To address this issue, the page processor checks the Data Field Length Checking option on the PeopleTools Options page and performs character-set specific length validation against the contents of each field when the field is validated. Typically length validation occurs when the field’s FieldChange PeopleCode event fires, so the actual time of validation may differ, depending on whether your page uses deferred mode processing.

Enabling or Disabling Data Field Length Checking

To enable or disable data field length checking:

Select PeopleTools, Utilities, Administration, PeopleTools Options.

The PeopleTools Options page appears.

From the Data Field Length Checking drop-down list box, select a value based on the character set that you are using for the database:

Others	Select if you are using a Unicode encoded database or a non-Unicode SBCS database. This option prevents special field length checking, which is not required by these types of databases.
DB2 MBCS	Select DB2 MBCS if you are running a Japanese database on the DB2 UDB for Linux, Unix, and Microsoft Windows platform. This options enables field length checking based on a shifting DBCS.
MBCS	Select if you are running a non-Unicode Japanese database on any other platform. This option enables field length checking based on a nonshifting DBCS.

Note. The non-Unicode DBCS settings are specifically oriented to Japanese language installations, because Japanese is the only language that the PeopleSoft system supports in a non-Unicode DBCS encoding. All languages other than Western European languages and Japanese are supported by the PeopleSoft system only when using Unicode encoded databases.

Click the Save button.

Using CJK Ideographic Characters in Name Character Fields

This section discusses PeopleSoft standard name conventions, including name conventions for Chinese, Japanese, and Korean (CJK) ideographic characters. PeopleSoft standard name conventions apply when data is entered or displayed in character fields that use Name as the format type. These conventions should be used when a complete name is constructed from multiple name character fields or when all name data is entered into a single name character field.

The PeopleSoft standard name convention is:

[lastname] [suffix],[prefix] [firstname] [middle name/initial]

Examples of typical suffixes include degrees, affiliations, and titles such as MD, PhD, Jr., and III. Examples of typical prefixes include titles and honorifics such as Ms., Mr., Dr., Rev., and Hon.

Valid examples of these conventions include:

Name as Displayed by PeopleSoft Convention	Name Elements Used	Actual Name
O’Brien,Michael	[lastname],[firstname]	Michael O’Brien
Jones IV,James	[lastname] [suffix],[firstname]	James Jones IV
Phillips MD,Deanna Lynn	[lastname] [suffix],[firstname] [middle name]	Deanna Lynn Phillips, MD
Reynolds Jr.,Dr. John Q.	[lastname] [suffix],[prefix] [firstname] [middle initial]	Dr. John Q. Reynolds Jr.
Phipps-Scott,Ms. Adrienne	[lastname],[prefix] [firstname]	Ms. Adrienne Phipps-Scott
Knauft,Günter	[lastname],[firstname]	Günter Knauft

However, if the name contains any CJK ideographic characters, different standard name conventions apply.

If the name contains any Japanese or Korean ideographic characters, the first and last names are separated by a space instead of a comma. In Japanese, a prefix or suffix is optional; in Korean, only an optional prefix can be used. These modified PeopleSoft standard name conventions can be used when a name includes any of the following types of characters:

Japanese or Korean unified ideographs (Japanese Kanji or Korean Hanja).
Japanese half-width or full-width Katakana.
Japanese Hiragana.
Korean Hangul.

The PeopleSoft standard name convention for Japanese names including these ideographic characters is:

[lastname] [firstname][{suffix|prefix}]

The PeopleSoft standard name convention for Korean names including these ideographic characters is:

[lastname] [firstname][prefix]

Valid examples of these conventions include:

Name as Displayed by PeopleSoft Convention	Name Elements Used	English Equivalent
塩次伸二	[lastname] [firstname]	Shinji Shiotsugu
塩次伸二様	[lastname] [firstname][prefix]	Mr. Shinji Shiotsugu
홍 길동	[lastname] [firstname]	Hong Gildong
홍 길동씨	[lastname] [firstname][prefix]	Mr. (or Ms.) Hong Gildong

If the name contains Chinese Hanzi, there is no space or comma between the first name, last name, suffix, and prefix. The PeopleSoft standard name convention for names including Chinese Hanzi characters is:

[lastname][firstname][{suffix|prefix}]

Valid examples of this convention include:

Name as Displayed by PeopleSoft Convention	Name Elements Used	English Equivalent
陳嘉明	[lastname][firstname]	Chan Ka Ming
陳嘉明先生	[lastname][firstname][prefix]	Mr. Chan Ka Ming

See Also

Specifying Character Field Attributes

Character Processing

Detecting and Converting Between Character Types

PeopleTools also provides PeopleCode string functions that recognize and convert between different characters within the Japanese character set. This enables you to detect, convert, and enforce the types of characters that you can enter in any PeopleSoft field. For example, the PeopleSoft system uses these functions in the development of the Alternate Character Architecture in some PeopleSoft applications. The Alternate Character Architecture is used in several PeopleSoft applications to provide a feature that enables the entry of, and enforces the characters contained in, Japanese phonetic spellings (Furigana) by using the Hiragana or Katakana scripts.

The following PeopleCode string functions can be used to recognize and convert between different characters within the Japanese character set:

CharType
ContainsCharType
ContainsOnlyCharType
ConvertChar

Shell script to automate PSUNX reboot daily

2012-06-13T11:37:00.000-07:00

1)You have to create a file called serverlist with all the app/PSUNX server name with carriage return one each line
2)Schedule the below script on Unix Crontab to run daily to make the environment available daily with out manual interaction

#!/bin/bash
cd /home/psoft8.xx
. .bash_profile
TUXDIR=/apps02/tuxedo/tuxedo9xx
export TUXDIR
ORACLE_HOME=/apps01/oracle/10.2.0
export ORACLE_HOME
PATH=$PATH:$ORACLE_HOME/bin:$HOME/bin:$TUXDIR/bin:.
export PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$TUXDIR/lib
export LD_LIBRARY_PATH
PS_HOME=/apps02/pt8.xxx
export PS_HOME
PS_CFG_HOME=/apps02/pt8.xxx
export PS_CFG_HOME
. $PS_HOME/psconfig.sh
echo $ORACLE_SID
echo "***********************************************************************" > /apps02/pt8.xxx/output.log
echo `date` "Stopping & Starting all PSUNX Peoplesoft Process schedular ..." >> /apps02/pt8.xxx/output.log
echo "************************************************************************" >> /apps02/pt8.xxx/output.log
for PIA in `cat /apps02/pt8.xxx/serverlist`
do
cd /apps02/pt8.xxx/appserv
psadmin -p stop -d $PIA
psadmin -p kill -d $PIA
echo `date` "$PIA - PSUNX Peoplesoft Process schedular Sucessfully shutdown ..." >> /apps02/pt8.xxx/output.log
psadmin -p cleanipc -d $PIA
psadmin -p start -d $PIA >> /apps02/pt8.xxx/output.log 2>&1
echo `date` " $PIA - Process schedular rebooted Sucessfully ..." >> /apps02/pt8.xxx/output.log
done

echo *********************************************************************************" >> /apps02/pt8.xxx/output.log
echo `date` " Stopping & Starting output Application server with cache clear..." >> /apps02/pt8.xxx/output.log
echo "*******************************************************************************" >> /apps02/pt8.xxx/output.log
cd /apps02/pt8.xxx/appserv
psadmin -c shutdown -d >> /apps02/pt8.xxx/output.log 2>&1
psadmin -c shutdown! -d

rm -rf /apps02/pt8.xxx/appserv//CACHE/*
psadmin -c boot -d >> /apps02/pt8.xxx/output.log 2>&1
echo `date` " Application server cache cleared and rebooted Sucessfully ..." >> /apps02/pt8.xxx/output.log

cat /apps02/pt8.xxx/output.log | mailx -s "output instance PSUNX & application server daily status" notify@xxx.com

Application server single process reboot

2012-06-02T22:09:00.000-07:00

This is really helpful if are in need to reboot only single process particularly on production environment where there is no PeopleSoft application down time..

Here is one way in 8.49 Tools, go into psadmin:

PeopleSoft Domain Administration

PeopleSoft Domain Status Menu

Domain Name: PSXX89

1) Server status
2) Client status
3) Queue status
q) Quit

Command to execute (1-3, q) [q]: 1
Loading command line administration utility ...
tmadmin - Copyright (c) 1996-1999 BEA Systems, Inc.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by BEA Systems, Inc.
Tuxedo is a registered trademark.

Prog Name Queue Name Grp Name ID RqDone Load Done Current Service

---------

PSSUBDSP SUBDQ_dflt PUBSUB 300 0 0 ( IDLE )
BBL 63085 chqpvuu+ 0 7649 382450 ( IDLE )
PSAPPSRV APPQ APPSRV 1 84 4200 ( IDLE )
PSANALYTICSRV 00080.00001 ANALYTI+ 1 0 0 ( IDLE )
PSSUBHND SUBHQ_dflt PUBSUB 301 0 0 ( IDLE )
PSMONITORSRV MONITOR MONITOR 1 0 0 ( IDLE )
PSWATCHSRV WATCH WATCH 1 0 0 ( IDLE )
PSAPPSRV APPQ APPSRV 2 81 4050 ( IDLE )
PSANALYTICSRV 00080.00002 ANALYTI+ 2 0 0 ( IDLE )
PSANALYTICSRV 00080.00003 ANALYTI+ 3 0 0 ( IDLE )
JREPSVR 00094.00250 JREPGRP 250 11 550 ( IDLE )
PSQRYSRV QRYQ APPSRV 70 0 0 ( IDLE )
PSQRYSRV QRYQ APPSRV 71 0 0 ( IDLE )
JSL 00095.00200 JSLGRP 200 0 0 ( IDLE )
PSPUBDSP PUBDQ_dflt PUBSUB 200 0 0 ( IDLE )
PSPUBHND PUBHQ_dflt PUBSUB 201 0 0 ( IDLE )
PSBRKDSP BRKDQ_dflt PUBSUB 100 0 0 ( IDLE )
PSSAMSRV SAMQ APPSRV 100 0 0 ( IDLE )
PSRENSRV RENQ1 RENGRP 101 0 0 ( IDLE )
PSBRKHND BRKHQ_dflt PUBSUB 101 0 0 ( IDLE )

Go into server status and you will see the PSRENSRV line. Do you see the third column and the value "RENGRP"? Take that value and do the following:

PeopleSoft Domain Administration

Domain Name: PSXX89

1) Boot this domain
2) Domain shutdown menu
3) Domain status menu
4) Configure this domain
5) TUXEDO command line (tmadmin)
6) Edit configuration/log files menu
7) Messaging Server Administration menu
8) Purge Cache
9) Preload File Cache
10) Clean IPC resources of this domain
q) Quit

Command to execute (1-10, q) : 5
Loading command line administration utility ...
tmadmin - Copyright (c) 1996-1999 BEA Systems, Inc.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by BEA Systems, Inc.
Tuxedo is a registered trademark.

shutdown -g RENGRP

Shutting down server processes ...

Server Id = 101 Group Id = RENGRP Machine = xxxxxx: shutdown succeeded
1 process stopped.

boot -g RENGRP

INFO: BEA Tuxedo, Version 9.1, 64-bit, Patch Level 036
INFO: Serial #: 650522264137-2065448083901, Expiration NONE, Maxusers 1000000
INFO: Licensed to: Oracle-Peoplesoft-ISV

Booting server processes ...

exec PSRENSRV -A -- -C psappsrv.cfg -D PSXX89 -S PSRENSRV :
process id=778302 ... Started.
1 process started.

Iphone data transfer from old to new phone

2012-06-02T21:56:00.001-07:00

So you're a proud owner of a new iPhone 4 - maybe you were even in the same line I just stood in to get mine this morning.

But now you realize you have a considerable investment in apps and music sitting on your old iPhone 3G or 3GS, and don't know how to transfer them over to your new iPhone.

The trick is to first backup your old phone to iTunes, and then you can restore this backup to your new iPhone, which will transfer everything over.

Here's how to transfer purchased apps and songs from your iPhone 3G/3GS to your new iPhone 4 in 5 easy steps:

1. Connect your old iPhone to your computer and open iTunes.

2. Transfer your purchases by right-clicking your iPhone in iTunes and selecting "Transfer Purchases" from the shortcut menu.

You'll see iTunes transferring your apps and songs from your old iPhone to your computer:

3. Backup your old iPhone.

Right-click on your iPhone again in iTunes and select "Back Up" from the shortcut menu.

4. Connect your new iPhone 4 (after disconnecting the old one of course).

5. Restore your iPhone 4 using the old iPhone's backup.

Right-click again on your iPhone 4 in iTunes and select "Restore from Backup".

Choose the backup you created in the 3rd step above:

Click "Restore" and wait for iTunes to restore from the backup (which also transfers over your purchased apps and music):

iTunes will automatically restart your new iPhone 4 once the backup/restore has completed and you'll see all of your purchased apps waiting for you to play with.

Open the iPod app and you'll also see your music waiting for you to enjoy.

PeopleSoft Database SSL and REN server SSL setup

2012-05-30T13:45:00.003-07:00

Step 1:

Request for Root and chain certificate from CA. He provided the Root/Chain CA

Step 2:

Paste and merge the chain certificate and then root certificate without space as below:

-----BEGIN CERTIFICATE----- ß---------Chain Certificate

DHzvjJP9QoyDfz8uhZ2VrLWSJLyi6Y+t6xcaeoLP2ZFuQ==

-----END CERTIFICATE-----

-----BEGIN CERTIFICATE----- ß--------- Root Certificate

CI3zJpDC5fcgJCNs2ebb0gIFVbPv/ErfF6adulZkMV8gzURZVE=

-----END CERTIFICATE-----

========================================================================

STEP 3: Import the Entrust chain and root certificate to database

Import the certificate as below to peoplesoft.Navigate to PeopleTools->Security->Security Objects->Digital Certificates

Fill in the below information and click the +add root .Paste the above created in step 2 chain and root certificate by clicking Add root and click ok

Root CA

Entrust Root and Intermed Cer

10/12/19 1:13:54PM

========================================================================

STEP #4. Generate the database Server certificate

Create a certificate request (CSR) from the PeopleSoft database as follows:
    a. Navigate to PeopleTools->Security->Security Objects->Digital Certificates
    b. Click '+' to add a new entry
        i. Choose type = 'Cert'
        ii. Enter any Alias name (eg 'REN SSL')
        iii. Click 'Magnifying Glass' next to Issuer Alias and choose the 'Entrust Root and Intermediate Cer' entry you created in step 2 above.
       iv. Click the 'Request' hyperlink
            - For common name, enter the name of the box that the REN server is on
              eg:xxx.domain.com (Application server)
            - Enter other 'Subject' information (eg Org Unit, State, etc) as appropriate for your company
            - Keep the default values in the 'Key Pair Information' section
            - Leave the 'Additional Certificate Attributes' blank
            - Click 'OK'

. You are now presented with the certificate request.
         i. Copy everything from 'BEGIN NEW CERTIFICATE REQUEST' to 'END NEW CERTIFICATE REQUEST' to clipboard. Then click 'ok'
            Example:
            -----BEGIN NEW CERTIFICATE REQUEST-----
           MIIBlzCCAQACAQAwVzEJMAcGA1UEBhMAMQkwBwYDVQQIEwAxCTA
           etc etc
           -----END NEW CERTIFICATE REQUEST-----
         ii. Send the above information to your certificate authority (CA) and request a certificate.

STEP 5: Import the SSL certificate (Make sure you got certificate as VIP address name)

STEP #4. After you get the signed certificate from the CA, import it into the PeopleSoft database:
    a. Navigate to PeopleTools->Security->Security Objects->Digital Certificates
        i. Click the 'import' link next to your certificate.
        ii. Paste in the certificate that you received (Server certificate only).
           Example:
           -----BEGIN CERTIFICATE-----
           MIIEJjCCA4+gAwIBAgIQMFbEDgfLmZ <-- Contents of Certificate
           etc etc
          -----END CERTIFICATE-----
        iii. Click OK

Validate the certificate is correct date and time by clicking Details>Configure REN – clear appserver/Webserver cache and reboot

Cert

RENSSLCertificate

Entrust Root and Intermed Cer

31/12/14 3:59:06PM

Detail

How to identify session stickiness problem on load balancer in PeopleSoft environment?

2012-05-30T13:26:00.003-07:00

Simple example of load balancer with session stickiness problem

Suppose you have load balancer in front of two WebLogic webservers. In this simple example, we'll call them webserver A and webserver B. When end users logs into PeopleSoft though the load balancer, the end user connects to one webserver. Suppose the load balancer routes an end user to webserver A. This end user should remain with webserver A during the entire session. While the end user is working in PeopleSoft, if this end user inadvertently connects to webserver B, this means the load balancer is not maintaining session stickiness. End users may experience intermittent problems such as getting kicked back to search page, gettting kicked out of PeopleSoft, premature timeout, seeing "Page is no longer available", images disappearing, 403 errors, appserver showing that certain UserID are logging in PeopleSoft multiple times (looping) and other strange intermittent problems in PeopleSoft.

To determine if session stickiness may be a problem

1. Test without load balancer

If the problem does not appear without the load balancer, the reported problem is likely caused by the load balancer.

2. Test with one webserver running behind load balancer.

This is a good test, but results may be unreliable since intermittent problem may still appear with just one webserver because various load balancer configuration options may still point at the load balancer

3. Collect browser headers while replicating problem

Please ask some end users to collect browser headers when they log into PeopleSoft until the intermittent problem appears. Please download free tools such as: iehttpheaders, LIVE HTTP HEADERS, Fiddler, and etc. You can find these tools with a simple web search. Once you have header logs, please look at all the POST/GET requests and cookie values before problem appears, exact time problem appears, and after problem appears. Pay close attention to the weblogic webserver cookie called *PORTAL-PSJESSIONID. This webserver cookie value should remain constant (a long encrypted string value) during the end user's entire PeopleSoft session. If you see that the PORTAL-PSJESSIONID webserver cookie value is randomly changing, your load balancer is not maintaining session stickiness.

4. Turn on WebLogic extended access logging in both webservers behind the load balancer

For instructions on turning on extended access logging, please see Document 644602.1. This is the most time consuming option and may impact performance in production, but it may provide the most valuable information.

The extended logging collects all cookies in the same domain that are forwarded from browser to webserver for all end users logging into PeopleSoft. These include PeopleSoft cookies, WebLogic cookies, 3rd party cookies, and any custom cookies.
Example 1: Session stickiness problems can cause the following behavior:

End user is randomly kicked out of PeopleSoft in load balanced environment.

End user kicked back to search page in load balanced environment.

Premature timeout in load balanced environment.

Random "Page is no longer available" in load balanced environment

403 errors

Here are some troubleshooting tips for the above behavior:
a) Turn on extended access logs in both webservers
b) Ask end users to attempt to replicate problem. When problem appears, ask for PeopleSoft UserID and exact time.
c) In webserver A, in extended access logs, search for that UserID. You'll see a PeopleSoft cookie called SignOnDefault that will match that UserID. For that UserID, please look at all the POST/GET requests and cookie values before problem appears, exact time problem appears, and after problem appears. Pay close attention to the weblogic webserver cookie called *PORTAL-PSJESSIONID. This webserver cookie value should remain constant (a long encrypted string value) during the end user's entire PeopleSoft session. If you see that the PORTAL-PSJESSIONID webserver cookie value is randomly changing, your load balancer is not maintaining session stickiness.
d) In webserver B, in extended access logs, do the same as step c.

Remember, if end user logs into PeopleSoft and connects to webserver A (you should see this UserID in access log for WebServer A) and you start to see entries in webserver B access logs for this UserID, that's a clear sign that load balancer is not maintaining session stickiness. There is also also a possibility that end user stays on webserver A, but PORTAL-PSJESSIONID is randomly changing. This also indicates a session stickiness problem.

The extended access logs from the webserver are evidence that the load balancer is not maintaining session stickiness. Customers should follow up with their load balancer vendor to properly setup session stickiness on the load balancer.
Example 2: Session stickiness problems can cause the following behavior:

In PeopleSoft load balanced environment, UserID is unknowingly logging in PeopleSoft multiple times (looping) and using up all webserver and appserver resources.

a) Turn on extended access logs in both webservers
b) Make sure appserver psappsrv.cfg has LogFence=3 or higher. Save and bounce appserver
c) In appserver psadmin, select 3 "Domain status menu". Select 2 "Client status". If you see the same UserID appears multiple times, it could be indication of random looping behavior where UserID is unknowningly logging into PeopleSoft hundreds of times. Check appserver log file and search for that UserID to see if this UserID is authenticating multiple times in a short time period. Find the timestamp when this UserID first logged into PeopleSoft in appserver log file

d) In webserver A, in extended access logs, search for that UserID. You'll see a PeopleSoft cookie called SignOnDefault that will match that UserID. For that UserID, please look at all the POST/GET requests and cookie values before problem appears, exact time problem appears, and after problem appears. Pay close attention to the weblogic webserver cookie called *PORTAL-PSJESSIONID. This webserver cookie value should remain constant (a long encrypted string value) during the end user's entire PeopleSoft session. If you see that the PORTAL-PSJESSIONID webserver cookie value is randomly changing, your load balancer is not maintaining session stickiness.

e) In webserver B, in extended access logs, do the same as step d.

Remember, if end user logs into PeopleSoft and connects to webserver A (you should see this UserID in access log for WebServer A) and you start to see entries in webserver B access logs for this UserID, that's a clear sign that load balancer is not maintaining session stickiness. There is also also a possibility that end user stays on webserver A, but PORTAL-PSJESSIONID is randomly changing. This also indicates a session stickiness problem.

The extended access logs from the webserver are evidence that the load balancer is not maintaining session stickiness. Customers should follow up with their load balancer vendor to properly setup session stickiness on the load balancer.

Example 3: Other random problems that only appear in load balanced environment

This last section just provides some general tips to troubleshoot issues in a load balanced environment.

a) Turn on extended access logs in both webservers
b) Make sure appserver psappsrv.cfg has LogFence=3 or higher. Save and bounce appserver
c) Ask end user to report when problem appears. Get UserID and time if possible.
d) Review extended access log, appserver log, and all webserver log file for that time period when problem appears. You may need to cross reference the different log files so see if a certain error or action may have caused the reported problem:

Since extended access logs contain all POST/GET requests and all cookies, it may give a clue what the end user was doing when the problem first appeared.

Are there certain POST/GET requests that seems to trigger the problem?
Do you see multiple PeopleSoft webserver cookies *PORTAL-PSJESSIONID? Perhaps end users was visiting other PeopleSoft sites or certain navigation may have caused problem What values do PS_LOGINLIST and ExpirePage contain?
Do you see other custom or 3rd party cookies such as load balancer cookies, siteminder cookies, and etc that could be causing problems in load balanced environments? Are these custom cookies suppose to maintain constant or change values?