Skip navigation.

Duncan Davies

Syndicate content The PeopleSoft Tipster Blog
A PeopleSoft Tips and Tricks Blog
Updated: 7 hours 8 min ago

Help Please! The UKOUG Partner of the Year awards

Thu, 2014-07-31 07:48

We’d really appreciate your help. But first, a bit of background:

The Partner of the Year awards is an annual awards ceremony held by the UK Oracle User Group. It allows customers to show appreciation for partners that have provided a service to them over the previous 12 months. As you would imagine, being voted a winner (for the categories that you operate in) is a wonderful accolade as it’s the end-users that have spoken.

Cedar Consulting has a long history of success in the competition, reflecting our long standing relationships with our clients. I wasn’t going to ask for votes this year, however I notice that many of our competitors are filling Twitter and LinkedIn with pleas so I feel that I should also ask for your vote.

If you’re an existing Cedar client site we’d love your vote. Also, if you are a recipient of any other Cedar service – and I guess here I’m talking about the free PeopleSoft and Fusion Weekly newsletters that we send out – we’d be very grateful if you gave 3 minutes of your time to vote for us.

What we’d like you to do:

1) Go to: http://pya.ukoug.org/index.php

2) Fill in your company name, first name and surname. Then click Next.

3) Enter your email address in both fields, then click Next.

4) Select any checkboxes if you want ‘follow-up communications’ from the UKOUG, or leave all blank, and click Next.

5) Select Cedar Consulting from the drop-down, and click Next.

6) On the PeopleSoft page, select the Gold radio button on the Cedar Consulting row (note, it’s the 3rd column!), then click Next.

7) Repeat by selecting the Gold radio button on the Cedar Consulting row of the Fusion page, then click Next.

8) Click Submit.

And you’re done. Thank you very much. If you want some gratitude for your 3 minutes of effort drop me an email and I’ll thank you personally!


An Introduction to PeopleTools 8.54 (part 2)

Thu, 2014-07-31 07:08
1. Introduction

The recently launched version of PeopleTools 8.54 contains a broad range of enhancements. Although we’ve had the GA (General Availability) release we can’t upgrade existing environments until the 8.54.02 patch, so now is a good time to perform a fresh sandbox install to investigate the details and highlight the areas that are of most interest.

As in the first part of this series, there is a lot of content to cover so I’ve spread it over several entries. This first part looked at the back-end, infrastructure and System Admin changes, whereas this post moves up the software stack with integration and reporting, and the final entry will finish with the Fluid UI.

2. Developer UI Enhancements

There have been a number of improvements to the User Interface – we’re not talking about Fluid, this is in the Classic UI too although these changes may also benefit Fluid pages).

a. Charting Enhancements

The development team have introduced some new charting types to the toolset. We were already able to select from quite a few options, however we’ve now got Gauges, the LED lights, Status Meters and Funnel charts.

1-charts

b. Long Edit Box Character Counter

Previously people (myself included) have accomplished similar functionality – with varying levels of success – by inserting JavaScript onto the page. Now it’s natively built in to PeopleTools. A character counter can be activated on the properties on the Long Edit box control:

2-long edit setup

The result on-screen is like this:

3-long edit result

Note: this functionality doesn’t actually limit the text entry and if the user exceeds the limit it will show a negative number.

c. Pivot Grids

Pivot Grids have been enhanced in a lot of ways – there are almost 30 improvements listed in the Release Notes. Just picking a few, they now include the ability to restrict the number of rows shown in a Pivot Grid, PS Query drilling URLs and Bubble and Scatter charts are now available as Pivot Chart types.

4-pivots

3. Reporting a. BI Publisher

As of PeopleTools 8.54, BI Publisher now includes support for PCL (Printer Control Language) code in RTF templates. This allows for printing PDF with Secure Fonts, essential for the secure printing of cheques.

Also newly supported are digital signatures – which can be used to verify the sender and to ensure that it the output hasn’t been amended in transit, and updatable PDFs.

b. PS Query

PS Query now supports defaults for prompts:

5-query

There have been workarounds to achieve a similar result before, but it’s now built into the configuration pages so we don’t need to search online for the workaround each time we want to use it.

Also new with PS Query is the option to include image fields in your output. There are a number of display alternatives with image fields, either Image Data (in which case PS Query will display the image inline with the rest of the HTML result set), or a Base64 encoded data string representing the image with any output other than HTML, or – when the property is set to Image Hyperlink – a URL to the image will be returned instead of the image itself. When the URL is clicked, the image will be displayed in a new browser window.

6-query images

Additionally, all PS Queries can be exposed as REST services, and Microsoft Excel 2007 and above is supported thereby increasing the amount of rows you can download from a Query result set into Excel above the previous limit of 64 thousand.

Finally, PeopleTools 8.54 introduces a new Query type, the Composite Query. Composite Queries are a superset of Connected Queries (which have been in PeopleTools for a couple of releases). Composite Queries allow users to connect queries together and have the output presented as a flat result set (instead of the hierarchical data sets which were output from Connected Queries).

4. Batch Processing

One very visible improvement to the Process Scheduler is a new status window that slides in from the lower right corner to give updates on processing progress. This is a nice touch that I’m sure end-users will appreciate:

7-batch window

Secondly, Activity Guides can improve batch processes as steps – which is important if there’s something a bit more process intensive that’s needed as part of a sequence of steps.

Finally, App Engine program trace allows you to specify which sections to appear in the trace, rather than having to wade through the trace for an entire program. This needs to be enabled in the Process Scheduler config, in Configuration Manager, and then in the App Engine itself:

8-trace

5. Other Enhancements

Other enhancements included in this version of PeopleTools are:

- There’s a WorkCenter to make the setting up of new Activity Guides easier, plus a cloning function which will be useful when similar – but slightly different – guides are needed.

- SES facets now include numerical and date ranges. Results can include images and report repository content.

- Change Assistant has now been decoupled from the PeopleSoft Image, enabling packages to be moved to subsequent environments without also needing to connect to the PeopleSoft Image (this was quite restricting in Tools 8.53). It also has a fresh new UI and can be scripting/configured via the command line

- Data Migration Workbench has received improvements to Application Data Sets (and define relationships between groups), plus merging, support for managed objects and an improved UI.

- PeopleSoft Test Framework now allows you to perform mass updates (updating a set of tests in one change), interaction with App Designer projects and some usability enhancements.

6. Conclusion

The next version of PeopleTools is bringing many improvements. Much is being made of the new User Interface – and rightly so – however there are other improvements that we will improve our workflow by making it both simpler and more efficient.


PeopleTools 8.54 Sandbox

Mon, 2014-07-14 08:00

Following the announcement on Friday that Tools 8.54 was available, we dived straight in (whilst cursing under our breath that it was released at 6pm on Friday night on the weekend of the World Cup final!).

We download all of the media (which doesn’t take long on AWS – this is the 2.7GB tools 8.54.01 patch coming down in about a minute and a half):pt85401 download

 

At the time of GA you can’t perform an upgrade yet (that’s in the 8.54.02 patch) so our only option was a clean install.

Over the course of the weekend we managed to get a complete install running. The install was fairly painless, although there were a couple of times that we had to stop and think.

One example is during the install of WebLogic (now rebranded as Fusion Middleware):

weblogic

 

You can see it reports both the OS and Java version as incorrect. The OS we used was Windows 2012R2, which is a certified platform. The Java version we used is Java 8 and it was expecting Java 7. It let us continue but during the installation of the PIA the Java version caused an issue and we had to remove v8 and put v7 on.

Fluid aside, this feels like a big release. There are lots of intriguing new items that we noticed during the install that we didn’t have time to investigate and we don’t recall from the RVP or Pre-Release notes.

We like the jazzy new sign-on page:

pt854 signon

We’ll post more when we’ve dug a little deeper …


Generating a custom Org Chart in PeopleSoft

Tue, 2014-07-08 15:52

This week we have a second guest-post from Richard Yip. Richard is a PeopleSoft HCM & Payroll Technical Consultant at Santander Bank here in the UK. He is a long-term PeopleSoft techie and a regular at the UKOUG conferences.  I’m delighted to be able to give him a conduit through which to share some of his good work.

Richard’s previous post can be found here.

Custom Organisation Charts in PeopleSoft

In the PS_EMPLOYEES table, there is a custom field called SUPERVISOR_ID. This is used to connect the employee to the supervisor or line manager. This is similar to the REPORTS_TO field in PS_JOB.

I developed this after toying with the GOOGLE API Organisation Chart. Generating the boxes was straight forward enough, so the trick was to understand how to generate the connecting lines.

I also included some Javascript to make the images appear when the box is clicked and disappear when it is double-clicked. The images are from the PS_EMPL_PHOTO, so a data URI with Base64 encoding is used.

org_chartDefault Appearance

org chart picturesExpanded to show photos

Richard has kindly shared all the code required to get this working. See Generate a custom Organisation chart from ps_employees for the listings.


New Pastures

Tue, 2014-06-24 16:58

I try to keep the content on here focused on the products and implementation tips however I hope you’ll indulge me with one personal post.

After six and a half enjoyable years I have left Succeed Consultancy. I’m leaving behind a lot of talented colleagues and great friends, however for reasons that I don’t want to bore you with it’s time to move on.

As of yesterday I’ve started work for Cedar Consulting. One of the largest the ‘tier 2′ PeopleSoft consultancies in EMEA.

Cedar have been running – in one form or other – for nearly 20 years and have an impressive list of PeopleSoft implementations, upgrades and support/hosting clients. There are few UK PeopleSoft clients who haven’t engaged Cedar at one point or other. As well as their large team of UK consultants they have a number of offices spread globally and a solution centre in India.

Importantly for me, Cedar also have a strong focus on Fusion and already have both a live Fusion client under their belt and the UKOUG Fusion Partner of the Year gold award.

This career move also means that the branding of the PeopleSoft and Fusion Weeklies will change. I’d to thank Succeed for sponsoring the newsletters up to this point and I’m grateful to Cedar for agreeing to sponsor it going forwards. You should notice a rebrand in this week’s editions.


PeopleSoft 9.3 – A clarification

Fri, 2014-06-20 02:49

After the release and subsequent removal of the ‘there is no PeopleSoft 9.3′ post on the My Oracle Support site and twitter I’ve been in contact with Oracle to find out the truth behind these rumours. Let me share with you what I have learned directly from Oracle…

Oracle believes PeopleSoft customers want new capabilities delivered at a high frequency that they can adopt in a non-disruptive, low cost way. They understand that the model of big, disruptive, high cost upgrades every several years doesn’t work any more.

The new PeopleSoft delivery model enables Oracle to give PeopleSoft customers what they want – new capabilities delivered at a high frequency that they can adopt in a non-disruptive, low cost way. PeopleSoft Update Manager (PUM), delivered with PeopleSoft 9.2 is the technology that enables this revolutionary new delivery model.

What does this mean for a PeopleSoft 9.3 release? PeopleSoft customers would like to avoid major upgrades. Oracle’s focus now and for the foreseeable future is to deliver new innovative capabilities onto PeopleSoft 9.2 and (if possible) avoid delivering a PeopleSoft 9.3 release and thus pushing customers towards a major upgrade. The level of Oracle’s commitment to PeopleSoft and the investment in new features, functions, and capabilities remains the same regardless of the delivery mechanism (i.e. delivery onto PeopleSoft 9.2 or in a new PeopleSoft 9.3 release).

Learn more for yourself; check out the PeopleSoft Talk featuring Paco Aubrejuan discussing the new PeopleSoft delivery model and its impact on a PeopleSoft 9.3 release: http://youtu.be/Hm4UWtooG0I


It’s official, there is no PeopleSoft 9.3

Wed, 2014-06-18 02:43

EDIT: It seems that this was an erroneous announcement by Oracle (it appeared on both their Twitter feed and the MOS site).

I’ve now received further clarification from Oracle, read about it here.

 


Loading Photos into PeopleSoft in v9.2

Tue, 2014-06-17 08:00

This is a guest post by Anton de Weger, a highly experienced PeopleSoft Consultant who works for StratusHR in Australia. Anton has been previously featured in the post “I’m Anton de Weger and This is How I Work“.

Introduction

As part of a v8.9 to v9.2 upgrade of PeopleSoft HCM my current client wanted to take the opportunity to load all of their employee photos from their security system into PeopleSoft so that they could take advantage of the photos showing on the Talent Summary and Manager Dashboard, as well as on the name mouse-over in the core pages. I thought this would have been a pretty straight forward process given that this is delivered functionality, but was surprised at the lack of examples on the internet and the difficulty in doing image manipulation through PeopleCode.

Requirements:

  • Load employee photos from site specific network directories which had different naming conventions (i.e. Employee ID in file name or random filename with link to employee in Active Directory).
  • Store photos in PeopleSoft delivered record (EMPL_PHOTO).
  • Fix the problem with the photos stretching depending on the size of the original photo when viewed in the mouse over. Numerous cameras were used over time and there were periods when manual clipping was performed on the photos.
  • Automatically pick up new employees when their photos become available.

The solution to this problem was to create an Application Engine to do a load of the photos and a custom Java class to pad out the photos to the 100 height x 80 width aspect ratio that is used by PeopleSoft in the mouse over pages.

Maxchunksize

The first thing that is required before the photos can be loaded is that the database MAXCHUNKSIZE has to be set. This done through the following:

UPDATE PSOPTIONS 
   SET MAXCHUNKSIZE = 500000

Remember to store the original MAXCHUNKSIZE value and reset it at the end of the process.

Run Control

A Run Control page was created with some basic options including the path to the image locations on the network.

image1

Dynamic SQL

Working out which employees to load was done via some dynamic SQL based on the run control parameters. This was then used with a

Local SQL &employees = CreateSQL(&employeesSQL);

and

While &employees.Fetch()…

to loop through all of the employees that need to be checked. This could have just as easily been done through a Do Select in step to give more control over the commit frequency, but I just used a CommitWork(); statement in the loop.

Getting the Filename

This was site specific, either using the Employee ID in the name of the photo file or via a field in Active Directory. The accessing Active Directory was interesting in that I used the delivered LDAP_SEARCH business interlink.

First step was to load up the active directory configuration and test it via the delivered page.

image2

image3

Then this was loaded in PeopleCode via

&LDAP_SRCH_SCHENTRY = GetInterlink(Interlink.LDAP_SEARCH);
&PSDSDIR = CreateRecord(Record.PSDSDIR);
&PSDSSRVR = CreateRecord(Record.PSDSSRVR);
&PSDSDIR.DSDIRID.Value = "MYADDOMAIN";
&PSDSDIR.SelectByKey();
&PSDSSRVR.DSDIRID.Value = "MYADDOMAIN";
&PSDSSRVR.DSSRVR.Value = "INTERNAL.MYADDOMAIN.COM.AU";
&PSDSSRVR.SelectByKey();

&LDAP_SRCH_SCHENTRY.Clear();
&LDAP_SRCH_SCHENTRY.UserID_Attribute_Name = "uid";
&LDAP_SRCH_SCHENTRY.URL = "file://psio_dir.dll";
&LDAP_SRCH_SCHENTRY.BIDocValidating = "Off";
&LDAP_SRCH_SCHENTRY.SSL = "NO";
&rootInDoc = &LDAP_SRCH_SCHENTRY.GetInputDocs("");

&ret = &rootInDoc.AddValue("Connect_DN", &PSDSDIR.DSCNCTDN.Value);
&ret = &rootInDoc.AddValue("Connect_Password", Decrypt("dirmgrpwd", &PSDSDIR.DSCNCTPWD.Value));
&DirSrchParmsDoc = &rootInDoc.AddDoc("Directory_Search_Parms");
&ret = &DirSrchParmsDoc.AddValue("Host", &PSDSSRVR.DSSRVR.Value);
&ret = &DirSrchParmsDoc.AddValue("Port", &PSDSSRVR.LDAPPORT.Value);
&ret = &DirSrchParmsDoc.AddValue("Base", "DC=internal,DC=MYADDOMAIN,DC=com,DC=au");
&ret = &DirSrchParmsDoc.AddValue("Scope", "Sub");
&ret = &DirSrchParmsDoc.AddValue("Filter", "(employeeNumber=" | &emplid | ")");
&ret = &DirSrchParmsDoc.AddValue("Attributes", "comment");
&EXECRSLT = &LDAP_SRCH_SCHENTRY.Execute();

This then brought back the code for the comments field from Active Directory from which the file name was extracted. A simplified version of the code that accessed the comments is as follows:

If (&EXECRSLT = 1) Then
 &rootOutDoc = &LDAP_SRCH_SCHENTRY.GetOutputDocs("");
 &DirEntriesDoc = &rootOutDoc.GetDoc("Directory_Entries");
 &AttributeDoc = &DirEntriesDoc.GetDoc("Attribute");
 &ret = &AttributeDoc.GetValue("Value", &userActiveDirComment);
 &userActiveDirComment = RTrim(&userActiveDirComment);
 /* Process Comments */
End-If;
Pre-Processing the Photos

The ClipImage() PeopleCode function doesn’t work from Application Engine, and I couldn’t find an easy way to pad out the photos in PeopleCode, via a Component Interface or directly in the database, so I decided to use Java to do it. After a bit of research I decided on the imgscalr library to perform the required image manipulation.

Initially I tried calling the imgscalr class directly from PeopleCode, but I couldn’t easily manipulate the image in memory using the “any” PeopleCode variable type or the IMAGE field (via AET) into the bufferedimage type required by the imgScalr class and I was getting overloading issues. I probably could have persisted down this path, either using reflective type conversion or by writing a wrapper java class to remove the function overloading of imgscalr, but in the end I took the quicker (to code) approach of manipulating the image file and saving in a temporary file before loading into PeopleSoft. This was done via a custom java class (PhotoSync.java). This pads out either the height or width of the photo with white to achieve a 100 height x 80 width aspect ratio, while maintaining the full resolution of the original image.

import java.awt.image.*;
import java.awt.Color;
import java.io.*;
import javax.imageio.*;
import static org.imgscalr.Scalr.*;
public class PhotoSync {
public static void main(String[] args) throws IOException {
 }
 
 public static void padToPeopleSoft(String sourceFileName, String targetFileName) throws IOException {
 File sourceImageFile = new File(sourceFileName);
 BufferedImage img = ImageIO.read(sourceImageFile);
int height = img.getHeight();
 int width = img.getWidth();
 int expectedWidth = (int) Math.floor((double)height * 80 / 100);
 
 if (width > expectedWidth) {
 /* Add padding to the top of the image */
 
 int newHeight = (int) Math.floor((double)width / 80 * 100);
 int padding = (int) Math.floor((double)(newHeight - height) / 2);
 newHeight = height + (padding * 2);
 img = pad(img, padding, Color.WHITE);
 img = crop(img, padding, 0, width, newHeight);
 } else {
 if (width < expectedWidth) {
 /* Add padding to the side of the image */
 
 int newWidth = (int) Math.floor((double)height / 100 * 80);
 int padding = (int) Math.floor((double)(newWidth - width) / 2); 
 newWidth = width + (padding * 2);
 img = pad(img, padding, Color.WHITE);
 img = crop(img, 0, padding, newWidth, height); 
 }
 }
 img.createGraphics().drawImage(img, 0, 0, null);
 ImageIO.write(img, "jpg", new File(targetFileName));
 }
}

This was then compiled to create the Class file. Just a note that I ended up having to compile using jdk1.7.0 as the process scheduler was not able to run the Java 8 compiled class.

And the resulting PhotoSync.class file plus the imgScalr classes (in their org\imgScalr directory) were all copied to the PeopleTools\class directory on the process scheduler. In this case it was only distributed to the windows process scheduler, but theoretically it should have worked with other operating systems. This was called from the Application Engine PeopleCode as follows:

Local JavaObject &Photo = GetJavaClass("PhotoSync");
&Photo.padToPeopleSoft(&filename, &targetFilename);

As the Java code has not got error capture built in you have to check the availability of the image first.

Loading the Photo into PeopleSoft

The final step was to load the photo, now resized to the right aspect ratio into PeopleSoft. This was done as follows.

&fPhoto = GetFile(&targetFilename, "E", "", %FilePath_Absolute); 
&sTempFileName = &emplID | ".jpg";
SQLExec("DELETE FROM PSFILE_ATTDET WHERE ATTACHSYSFILENAME = :1", &sTempFileName);
&sResult = PutAttachment("record://PSFILE_ATTDET", &sTempFileName, &fPhoto.Name);
If PHOTO_LOAD_AET.REPLACE_IND = "Y" Then
SQLExec("DELETE FROM PS_EMPL_PHOTO WHERE EMPLID = :1", &emplID);
End-If;
SQLExec("SELECT FILE_DATA FROM PSFILE_ATTDET WHERE ATTACHSYSFILENAME = :1 AND VERSION = 1", &sTempFileName, &Data);
&rec = CreateRecord(Record.EMPL_PHOTO);
&rec.EMPLID.Value = &emplID;
&rec.PSIMAGEVER.Value = (Days365(Date3(1999, 12, 31), %Date) * 86400) + (%Time - Time3(0, 0, 0));
&rec.EMPLOYEE_PHOTO.Value = &Data;
&rec.Insert();
SQLExec("DELETE FROM PSFILE_ATTDET WHERE ATTACHSYSFILENAME = :1", &sTempFileName);
The Result

image4

This shows the padding in the image in yellow (rather than white). The photos retained the original resolution so were either large or small depending on when they were taken. It would be possible using this method to standardise the size of the photos as well.

image5

This is the mouse-over on the name for the employee.

Accreditation

Anton de Weger has been working with PeopleSoft since 1994 and currently works for Stratus HR (www.stratushr.com) a small specialist consultancy with a couple of other experienced colleagues.

 


An Introduction to PeopleTools 8.54 (part 1)

Tue, 2014-06-10 15:32
1. Introduction

The next version of PeopleTools is expected to be released in a couple months’ time. Oracle have now made available both the Release Value Proposition and the Pre-Release Notes for PeopleTools 8.54. As no more official documents are expected before the release hits GA (General Availability) now is a good time to pick through the details and highlight the areas that are of most interest.

There is a lot of content to cover so – to prevent this entry becoming too big to read in one sitting – I’ll spread it over several parts. This first part will look at the back-end, infrastructure and System Admin changes, whereas subsequent posts will move up the software stack with integration and reporting, and finishing with the new UI.

2. Supported Platforms

Each new release of PeopleTools adds new supported platforms and retires older versions. PeopleTools 8.54 introduces support for new versions of Oracle Weblogic (12.1.2) and Oracle Tuxedo (12.1.1), and deprecates WebLogic 10.x and Tuxedo 11.x. The version 12 releases are the only supported versions of these technologies.

Also added are some new server OS versions: Windows 2012 and 2012 R2, plus Oracle Linux v6. Deprecated OSes are Windows 2008 R1 (although 2008 R2 should still be supported) and zOS 1.11.

On the database side Oracle 12c is added and 10.2.0.5 and 11.2.0.3 removed (so 11.2.0.4 should still be supported). SQL Server sees MSSQL 2014 added and MSSQL 2008 removed, leaving 2012 and 2014 as the supported versions.

Without doubt the most difficult items to adhere to will be the client browser and OS certifications. Firefox and Chrome are straightforward as they typically auto-update to the latest versions, however for enterprises where the mandated corporate standard is Internet Explorer it gets a little trickier. Support for IE11 has been added and IE8 deprecated with PeopleTools 8.54, leaving IE9, 10 and 11 as the supported versions. If you wish to use the new Fluid UI however, you need to get your users to IE11. Users on IE9 and 10 will get the ‘classic’ UI, which means the look and feel from PeopleTools 8.53.

Finally, you’ll also need to ensure that your clients are on Windows 7 (64-bit) or Windows 8.x. The 32-bit version of Windows 7 is not supported. As with all PeopleTools versions, it is possible to run using an un-certified browser and client OS combination, however there may be some workarounds required for edge-case functionality.

3. Oracle Database Specific Enhancements

This release brings some enhancements specifically for the Oracle RDBMS.

a. Global Temporary Tables

PeopleTools already has temporary tables built-in to the toolset (i.e. if you wish to enable multiple copies of an App Engine to run concurrently you need to build that many instances of the Temporary Tables). With Tools 8.54 you can take advantage of Oracle Global Temporary Tables within the database itself (but only for batch processes, not online page operations). GTTs are working tables that are process specific, so each concurrent process doesn’t have access to the working data from the tables from another version of the same process, and they’re lighter-weight on the database (specifically, they don’t generate redo) so they are more efficient to use.

Some clients have already made use of this, including one major retailer here in the UK – with the assistance of a DB tuning guru – however now it’ll be built into the PeopleTools toolset rather than requiring customisation.

b. Materialised Views

For the uninitiated, a materialised view is a special database object where the results of the view SQL is stored as a data table. They’re especially useful for migrations, integration, reporting and data warehouses as they save repeated queries against the same data. Complex SQL can be used in a Materialised View so that it is performed once, and then any subsequent queries for the same data can use the data stored as the view output rather than running the query again.

c. Multi-tenant Database Support

Oracle’s 12c database comes with the ability to store ‘pluggable databases’ within a ‘container database’. This reduces overheads by saving on disk space, CPU and memory, but also by enabling database patching to be performed once. PeopleTools 8.54 includes support for the pluggable databases within the Oracle 12c database platform.

d. Partitioning Support

Many clients use partitioning on their tables, particularly with PeopleSoft Global Payroll and large numbers of employees. It was possible to partially configure this from Tools 8.51, however partitioning can now be completed entirely within App Designer with Tools 8.54.

4. Developer Tools

What functionality has changed for developers in Tools 8.54? For a start, the developer tools are now 64-bit, which – aside from the performance benefit – will make developer client machine administration easier. This includes not only App Designer, but Data Mover, Change Assistant, App Engine etc.

The other major improvement – and it’ll be a much welcomed one – is code completion in App Designer. Many other IDEs have had this functionality for a while so I’m grateful that we’re going to be seeing this in PeopleTools. App Designer will auto-complete after the developer uses a ‘.’ for constants, system variables, functions and app classes – not just showing the method but the parameter details also.

5. Automated Configuration Manager

An intriguing item in both of the Oracle documents is the ‘Automated Configuration Manager’. Neither document gives a great amount of detail, but it sounds like an improvement or twist to the Automated Environment Configuration tool that Hakan Biroglu blogged about. As a sys-admin this is particularly exciting as it’s moving PeopleSoft towards the ‘dev-ops’ holy grail of automated configuration management popularised by tools such as Chef and Puppet. Any tool that makes the creation of new environments quicker, or reduces the changes of configuration getting out of sync will be very welcome.

6. Conclusion

The next version of PeopleTools is bringing many improvements. Much is being made of the new User Interface – and rightly so – however there are other improvements that we will improve our workflow by making it both simpler and more efficient.

 


PeopleSoft and Heartbleed

Tue, 2014-04-22 09:00

Oracle have released a post detailing exactly whichheartbleed products are vulnerable to Heartbleed, which have fixes available and which aren’t vulnerable at all.

If you aren’t aware of what Heartbleed is, here’s a primer:

http://www.engadget.com/2014/04/12/heartbleed-explained/

There’s also an excellent web-comic here that explains quickly how the exploit works:

http://xkcd.com/1354/

Here is Oracle’s list:

http://www.oracle.com/technetwork/topics/security/opensslheartbleedcve-2014-0160-2188454.html

Happily, PeopleSoft is on the ‘not vulnerable’ list.

This doesn’t mean that you’re completely safe of course. You may well be using other components in your system that were impacted. At Succeed, for example, we use Amazon’s Elastic Load Balancer that was vulnerable but has now been patched.