View source for PeopleSoft Roadshow 2016

The UK OUG [[PeopleSoft]] Roadshow 2016 is the best one I have been to for a while. It included many user stories as well as updates from Oracle themselves. PeopleSoft Roadshow is a very useful place to keep up to date with the bigger PeopleSoft picture, I would thoroughly recommend it, particularly if you have not gone along in a while.

The following are some of my jotted notes that I made during the day...

==Marc Weintraub, Oracle==

[[PeopleTools]] 8.56 will have the ability to continuously upgrade. 

Oracle have created a site for enhancement requests and for customers to vote on which requests they like.

The Oracle cloud can support:

* Infrastructure as a Service - the virtual machines
* Platform as a Service - the database and the machines 

PeopleSoft will not be supplied as Software as a Service on a subscription basis.

Customers can make use of IaaS to provide from just a latest Demo environment on demand or development, test and staging through to full Production provision. This could let a prospective cloud client "dip their toes" with Demo before making a serious commitment.

==Arvind Rajan, BeAstute==

Selective Adoption in 9.2 should be driven by a conversation between all the stakeholders - whether you are going to use full annual (or biannual) adoption, or a more regular but perhaps more piecemeal approach.

==Colin Kirkpatrick and Graham Smith==

The PeopleSoft Cloud Architecture (as delivered in [[PeopleTools 8.55]]) can be used for both cloud and non-cloud deployment.

The PeopleSoft ... Architecture has the following components:

* Deployment Framework and DPK's
* Automated Configuration Management (ACM) that was first introduced in 8.54.
* Puppet

The new DPK downloads from Oracle can contain the build and set up of VirtualBox to run it in.

There are three types of DPK:

* Upgrade
* VirtualBox DPK
* Native DPK

The Native DPK can be used to load to Oracle Compute Cloud, Azure etc.

Automated Configuration Management can (amongst other things):

* Rename Nodes
* Setup Integration Broker
* Define Integration Gateway
* Set up Report Nodes
* Set up Process Scheduler

This is all controlled by the Puppet YAML file.

Graham also gave some hints on how to prevent issues when installing.

==Fluid at Oxfam, Jo Lock and Angela McKenna==

Another great presentation, giving a customer's view of implementing Fluid.

Oxfam decided they only wanted to maintain homepage(s) in one technology.

Using Fluid would future proof them for mobile phone and tablet use

They built Fluid home page tiles that connected tonFluid pages and menus, as well as work centres and classic pages.

They showed how, on Fluid pages, they used group boxes to regulate the display using the Fluid tan and style.

They also found that although there is a process to convert Classic to Fluid (essentially you make the classic page a subpage and put it into a Fluid container), the result will need to be adjusted to take advantage of the Fluid features. 

They also showed how they adjusted their absence page.

The delivered approvals page uses MAP rather than Fluid. For this there was some extra setup required:

* Integration Gateway
* REST Target
* HMAP_APPROVAL Service Operation

This whole new interface required little training - a 2 page document was provided to users but most found it intuitive and did not read it.

Feedback about the new interface was very positive.




==Related Links==
[http://www.ukoug.org/peoplesoft PeopleSoft at UK OUG] ( #ukoug_psoft )