Occasionally questions will come up about the STAR schema and how it maps to fields in P6. The STAR schema is comprised of data pulled from the P6 EPPM Extended view schema, the rest of the data is calculated as part of the Transformation process. Calculated data includes - historical captures, hierarchies, burndown and work planning calculations, and many others.
More than two (:-)) folks asked this question recently so it might worth a short note. The question is how does one deploy a new mapviewer version (e.g. 220.127.116.11.1) into the quickstart kit (which has 18.104.22.168.0)? A manual process is the simplest.
Shutdown the glassfish server if it's running.
Make a copy of the existing mapviewer.war directory and rename it (e.g. mapviewer.war.111170).
Delete the contents of the mapviewer.war directory (or create one named mapviewer.war if you just renamed, without copying, the old one).
With the occasion of an Oracle WebCenter event around The Connected Customer last week in Madrid, I have had the chance to listen and to discuss with different companies including big retailers from supermarkets to luxury brands. During the day, several questions and concerns came to my attention, so here you have some thoughts inspired by the meeting and by my own recent readings on the subject and in particular by Brian Solis´s book The End of Business as Usual.
We have been exploring design time customizations on various Fusion Applications and compiled a list of dependencies that cause deployment failures in the integrated WLS. Below list contains servlets, filters and EJB reference entries that can be commented in web.xml for testing the customizations locally.
For HCM comment out below in your Customization workspace's web.xml: