Must Have Bookmark for WebCenter / ADF Faces Developers

The best way to teach something is to use what you are teaching to teach it. This is held up at http://jdevadf.oracle.com/adf-richclient-demo/, where the ADF UI components are listed and clicking each components renders and example of the component and a JDeveloper-context of how to work with the component.

If you found this interesting, please share.

© Scott S. Nelson

Frankenserver: Sharing WLS Install between WLP 10.3.5 and WebCenter 11.1.1.1.7

Caveat: I have only tried this on Windows. *nix varieties may vary. For a limited time only, the latest releases of WLP and WC can run on the same version of WLS (10.3.5). I found that if you first install WLP and then install WebCenter the same Oracle Home (in my choice, C:OracleMiddleware11.1.1.7) they seem to co-exist nicely.

That said, the first time I did this I left OEPE running and tried to start JDev after applying some of the tweaks described at http://bexhuff.com/2012/09/jdeveloper-memory-and-performance. This was not a good thing, and resulted in the need for the fix described at http://ariklalo.com/2012/05/27/unable-to-create-an-instance-of-the-java-virtual-machine-jvm-dll/. I probably would not have had the problem if I had closed OEPE first, but the fix seems to be a good thing either way, so no harm done and a fairly easy lesson learned.

If you found this interesting, please share.

© Scott S. Nelson

JDeveloper, WebCenter, TaskFlows and 11.1.1.6.0

Posting some of my random notes as their current container will be wiped in less than 48 hours…

If you find JDev freaking out while trying to edit a TaskFlow in Customization Mode, the word is that you need Patch 13948973.

If you found this interesting, please share.

© Scott S. Nelson

WebCenter as a Service and JPS-06514 Error

Ran into this where someone had created a WebCenter environment on a Windows server and I couldn’t get it to run after the first server restart. The error in the logs was:

JPS-06514: Opening of file based keystore failed.

Turns out that the credentials don’t get created correctly for the domain path in Windows all of the time. The fix was to go to the domain folder, right click  and:

  1. Go to Properties
  2. choose the Security tab
  3. click Advanced
  4. click on the entry for Administrators Group
  5. click change permissions
  6. click on the entry Administrators Group
  7. check box “Replace all child object permissions with inheritable permissions from this object”
  8. click “OK”
If you found this interesting, please share.

© Scott S. Nelson