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. 188.8.131.52.1) into the quickstart kit (which has 184.108.40.206.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:
There are many resources for SUN customers who are interested in upgrading or migrating to Oracle IDM. And since this is a common request from customers, I wanted to list a few of them here for easy access.
Here are two customer stories that represent both types of upgrade: an incremental upgrade, and a full re-platform
By default, Essbase will automatically backup the Essbase
security file, Essbase.sec, every 300 seconds (5 minutes). Most customers find the frequency of the
default backup interval overhead to be unnecessary given their security update
needs. It is recommended to change the
default setting before the “build” and “go-live” phases to have better
Essbase.sec file backups proportionally spaced between backups and improve
Oracle announces the winners of the most prestigious awards in Middleware, the Oracle Excellence Awards for Fusion Middleware Innovation at Oracle Open World every year. This year's winners in SOA & BPM were selected for their innovation and it gives us great pleasure in acknowledging our heroes.
While very basic introductory examples are invaluable in explaining a new API, they can fail to do a rich API justice - especially from the perspective of more experienced developers. For some of us, looking at a slightly more involved, realistic example can shed far better light on the practical value proposition for a technology.
Ksplice is designed to work in many different computing environments. Because upgrading the kernel on any running system is a hassle, we want you to be able to deploy Ksplice as widely as possible. As a consequence of this, there are a number of ways to set up a Ksplice installation for your Oracle Linux infrastructure.