Thursday, 17 April 2014

IE11, PeopleTools 8.53 and Compatibility Mode

According to Oracle Certifications Database Microsoft IE11 is supported on PeopleTools 8.53.


However, according to the PeopleTools 8.48 - 8.53 Browser Compatibility Guide (Doc ID 704492.1) - Page 34 - IE10 (ten) MUST be run in Compatibility Mode.  There is no statement anywhere that I can see about what mode to run IE11 in.

So, what's this all about. Some things I know.... some things I'm learning about..... some things I take an educated guess on and others I have cases open with My Oracle Support.

Please feel free to correct, comment or add to my discussion here.

What is Compatibility Mode


compatibility mode is a software mechanism in which a software emulates an older version of software in order to allow obsolete software or files to remain compatible with the computer's newer hardware or software.

What does this mean for Internet Explorer?


Internet Explorer 8 was promoted by Microsoft as having stricter adherence to W3Cdescribed web standards than Internet Explorer 7. As a result, as in every IE version before it, some percentage of web pages coded to the behavior of the older versions would break in IE8. This would have been a repetition of the situation with IE7 which, while having fixed bugs from IE6, broke pages that used the IE6-specific hacks to work around its non-compliance. This was especially a problem for offline HTML documents, which may not be updatable (e.g. stored on a read-only medium, such as a CD-ROM or DVD-ROM).
To avoid this situation, IE8 implements a form of version targeting whereby a page could be authored to a specific version of a browser using the X-UA-Compatibledeclaration either as a meta element or in the HTTP headers.[1]
In order to maintain backwards compatibility, sites can opt-into IE7-like handling of content by inserting a specially created meta element into the web page that triggers the "Compatibility mode" in the browser, using:[2]
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
A newer version of the browser than the page was coded for would emulate the behavior of the older version, so that the assumptions the page made about the browser's behavior holds true.

What does this mean for PeopleSoft?

If you use a version of PeopleTools that has support for IE8 or IE9 and you use one of these browsers then the browser must be set to run in Standards Mode.  See Pages 36 and 38 of Doc ID 704492.1.




If you use a version of PeopleTools that has support for IE10 or IE11 and you use one of these browsers then the browser must be set to run in Compatibility Mode.


What are some of the effects of using compatibility mode?

A number of things occur when running in compatibility mode.

1) some html and JavaScript hacks written by PeopleSoft to work around the non-compliance of standards by older versions of IE are supported under compatibility mode in new version of IE.
2) running in compatibility mode may also result in the older, slower and less efficient JavaScript engine being used.  This is why we see much slower rendering of complex or large pages even in the supposedly faster IE11 browser compared to to say Google Chrome or FireFox.

Taking a Closer Look at 8.53 HTTP Responses

Using Fiddler (free from Telerik) to capture and examine http responses from PeopleSoft to IE10 and IE11 we can see that some (but not all) responses from POST method requests contain the X-UA-Compatible: IE=8 or X-UA-Compatible: IE=EmulateIE8 directives in the http header.  This instructs the browser to render the page using compatibility mode.



So why then do we also need to set the browser to be in compatibility mode if the pages themselves from PeopleSoft are instructing the browser to be in compatibility mode?

My guess is that not all responses contain this directive and specifically AJAX calls that return html fragments do not generally contain this directive.  This looks like a work in progress by the PeopleSoft developers and hence because not all responses instruct the browser to run in compatibility mode we have to set the browser to process all responses from PeopleSoft in compatibility mode.

There is a difference between IE10 and IE11 here.  Far fewer http responses contain the compatibility directive in IE11 then in IE10.  It seems to be that only responses from psp servlet contain the directive in IE11.  It's possible that the portal header instructs the browser and therefore anything rendered in the content frame is also run in compatibility mode.  It's also possible that when PeopleTools identifies the browser being used on signin that it knows that IE11 has improved support for older style HTML and JavaScript and so the compatibility directive is not required.  I am not 100% certain of this but it is my best guess with what I've observed.  If anyone has greater insight into this then I'd value your input.

How to set IE10 and IE11 to run in Compatibility Mode?

In IE10 and IE11 under the Tools|Compatibility View Settings menu you can add specific web servers to a list of sites to run in compatibility mode.

In IE11 you can also enable Enterprise Mode which gives greater flexibility in specifying servers and also centralised control over deployment.   See here for more details http://technet.microsoft.com/library/dn640687.aspx

The Bottom Line

This is all very technically interesting but the bottom line is that if you're using IE10 or IE11 with 8.53 then you should enable compatibility mode.  


PeopleSoft 9.2 Upgrade Insights from Oxfam GB

At the recent UKOUG PeopleSoft Roadshow I presented some thoughts and experiences on a major FSCM 9.2 upgrade project that I'm working on at Oxfam GB.

If you're a member of UKOUG then you can download my presentation from UKOUG site here http://www.ukoug.org/2014-events/emea-peoplesoft-roadshow-2014/agenda/upgrading-to-peoplesoft-92-practical-insights/ along with a link to the SQL script to report all customised objects in your database.

If you're not a member (and you should be if you're in the UK) then links to the PowerPoint and SQL script are below.


PowerPoint http://goo.gl/axrn7o

SQL Script http://goo.gl/gFjNs4

Happy Upgrading and Happy Easter!


Wednesday, 26 March 2014

UKOUG PeopleSoft Roadshow 2014

What a great day of networking with PeopleSoft customers, partners and Oracle staff.  If you're in the UK and are involved in using PeopleSoft as an end user, developer, administrator or analyst then don't miss next years roadshow event.

The two Oracle speakers, Marc Weintraub (PeopleSoft Product Strategy) and Jeff Robbins (PeopleTools Strategy) gave some useful sessions on PeopleSoft application and PeopleTools roadmap.  I'll post more on what they told us about 8.54 when I get some more time.  Until then take a look at Jeff demonstrating the new PeopleSoft user interface "FLuiD" available in 8.54 sometime later this year.


Marc spent time covering the message that PeopleSoft is "State Of The Art" and this description can apply to software that is over two decades old.   More on this when I have time too.  


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

And finally...... here's some news that's interesting on Oracle Secure Enterprise Search.  http://www.oracle.com/technetwork/search/oses/overview/index.html 




Thursday, 6 March 2014

EMEA PeopleSoft Roadshow 2014

Featuring the well respected Marc Weintraub (Oracle PeopleSoft Product Strategy) and Jeff Robbins (Oracle PeopleTools Strategy) this is sure to be a most useful event.

Hear the latest news from Oracle and network with Oracle staff, PeopleSoft customers and partners.

I'll be speaking at this event on some practical insights into upgrading to PeopleSoft 9.2.

Hope to see you there.

Thursday, 23 January 2014

One PC - Five Virtual Machines

Having a simple and quick way to get at fully functioning virtual images of the entire PeopleSoft stack for each application is great news for customers and partners.

See PeopleSoft Demo Image Homepage at MyOracleSupport

Claims of "you can run these images on a PC" are true but ..... how "quick" this stuff works has a lot to do with the speed of your disks.

I originally started up these images on my laptop = downloading, unzipping, combining multipart files, importing, snapshotting and providing our project access team network access..... phew!!!!  Yes... it does work... but it's hard work.

My project team is working on an FSCM 9.2 upgrade project and so invested in a super fast PC. List price of all this kit is under £900.

Technical Specification:

On my production kit I get a PSPing time of 0.3 seconds and on this fast PC I get 0.12 seconds.  Overall performance is similarly impressive.   

PS Ping on our FSCM Production System
PS Ping on our project team Fast PC with SSD














This is what it is.  Just a fast PC.  No failover, no redundant parts, no sophisticated management.... just a fast PC that imports the PeopleSoft image in under 2 mins and boots one from scratch in under 1 min. 30 seconds. 
High speed import of Image in VirtualBox
The geek in me just had
to post a picture !


















So put this all together and this is what it looks like.....

3 x PeopleSoft images running in VirtualBox
2 x Windows XP machines running in VMWare Player



Wednesday, 16 October 2013

UKOUG Apps 2013 Conference

The UKOUG PeopleSoft community have two days of finance, HR and PeopleTools presentations at The Brewery in London as part of the Apps 2013 event.  As always the networking with other customers and partners proved very useful.  Thanks to everyone who came and shared and participated in this community event.

I shared some of Oxfam's experiences in upgrading to PeopleTools 8.53 and my presentation can be accessed here.  

If anyone else is doing or about to start doing a PeopleSoft 9.2 or PeopleTools 8.53 Only upgrade then please get in touch.  Always happy to exchange ideas and share experiences.


Thursday, 3 October 2013

How to put PeopleSoft credentials into SOAP request

If you have the User/Password Required checked on for a SOAP based Service Operation then you'll need to supply the PeopleSoft user credentials in the SOAP header request.  This is what the wsse section of the SOAP request looks like.  You'll likely want to enable https so that your plain text username and password is encrypted.