PeopleTools Automated Environment Configuration - PTEM

A while ago Oracle started to deliver PeopleSoft appliances on VirtualBox...
To do this they developed tool-kits to be able to deliver a self configurable system like PTEM.

With "PeopleTools Automated Environment Configuration" you can configure the components that most admins are configuring using SQL refresh scripts.
Unfortunately some parameters cannot be refreshed using SQL: ie the Integration Gateway properties file ... but you can do it with PTEM !

With this new feature you can:

1. Rename Integration Broker Node
2.  Configure Integration Broker Node
3. Configure Gateway node
4. Configure gateway properties file (integrationGateway.properties)
5. Configure Process Scheduler Report Node
6. Configure Process Scheduler Server
7. Configure Secure Enterprise Search (SES)
8.  Deploy and schedule Search Index
9. Configure PeopleSoft Test Framework (PTF)

Even if it's not yet supported by Oracle you can use it to build new environment or to refresh environments.
If you have VirtualBox PeopleSoft images you can also have a look how it's done.

The main steps are:

1) set variables
export PTEM_PROP=ptem_YourEnv.properties
echo $PTEM_PROP

2) Check the server configuration file
echo $PS_SERVER_CFG

3) Run PTEM configuration
psae -CT ORACLE -CD ORACLE_SID -CO PS -CP PS -R PTEM_CONFIG -AI PTEM_CONFIG

Make PeopleSoft and Active Directory case insensitive

CASE #1
PeopleSoft deliveres a function LDAP_AUTHENTICATION() to authenticate PeopleSoft users with Active Directory credentials.
It is designed to be case isensitive, but all users must be created upper case:
  - DANIEL.CRAIG in PeopleSoft
  - any case in Active Directory. Daniel.Craig or daniel.craig or DANIEL.CRAIG will work

CASE #2
You may want to create users lower case in PeopleSoft? then you just need basic code change to make it possible:
  - daniel.craig in PeopleSoft
  - any case in Active Directory. Daniel.Craig or daniel.craig or DANIEL.CRAIG will work

CASE #3
You may want users to be case sensitive between PeopleSoft and Active Directory ? This is also possible with basic code change:
  - daniel.craig in PeopleSoft
  - only authenticated with daniel.craig in Active Directory

  CASE #4
You don't have much control in users provisioning in PeopleSoft or Active Directory ... or both ?

1.1 search for this line: &USER_PROFILE.UserID = Upper(&prflProps.GetByPropertyName("UserID").value);
1.2 and replace it With: &USER_PROFILE.UserID = &prflProps.GetByPropertyName("UserID").value;
2.1 search for this line: SetAuthenticationResult( True, Upper(&psUserId), "", False);
2.2 and replace it with: SetAuthenticationResult( True, &psUserId, "", False);
With this setup you are configured like CASE #3 but you need an extra step.

3.1 Add the following line before this line: SetAuthenticationResult( True, &psUserId, "", False);
    SQLExec("select OPRID from PSOPRDEFN where lower(OPRID) = :1", Lower(&psUserId), &psUserId);


You can now have mixed authentication cases like:
  - daniel.craig in PeopleSoft
  - and Daniel.Craig in Active Directory
and
  - Tony.Stark in PeopleSoft 
  - and tony.stark in Active Directory

JRE 7 runs PeopleTools 8.53

The Java part of PeopleTools 8.53 will no longer use JRE 6 but JRE 7.
All Java layers like WebLogic or BI Publisher will now require to install JRE 7.

PeopleTools 8.53 generally available

Initially planned in September 2012, PeopleTools 8.53 are generally available since the 1st of February 2013.
They will be the foundation for PeopleSoft 9.2, so it's time to get prepared !