WLP and needles in a haystack

Still no (statement of) direction? No maps, of road or such? Trying to find your way? Maybe you have not noticed (and you would certainly not be alone) that the new WLP version has actual documentation also, with release notes galore? No wonder, as it is missing from the documentation index and from any search results. The way to get there is to go to the product page and click the unassuming documentation link. Of course, that’s where it’s supposed to be, right?

Anyhoo, here’s the list of new stuff and here’s the list of limitations and workarounds, they kindly also mention about the database issue when creating the domain using (the default) PointBase database (see 9224906). While there are a huge amount of things there to look at, one or two things you might want to take a look at. For example, Dynamic Visitor Tools (DVT) documentation link no longer talks about it being just a sample and not meant to be used in production, like in the previous versions where the documentation very specifically stated that point of view.

There is also an interesting Atom based REST API for accessing content, and while this seems to be tied to the Universal Content Management (UCM) / Stellent product, it is an fascinating direction to go to. One more thing is the Unified User Profile (UUP) REST API, which confusingly is not present in the REST API documentation, but you have to go digging for it in the User Management Guide. Still, it’s seems like a good API which allows for CRUD operations on the current user profile. Also, most of the updates are made using POSTs so you could use HTTPS for those (not that you would have too sensitive data in the user profiles, right?).

Unboxing the new WebLogic Portal

Doesn’t it feel like Christmas when you download a new (point) release of a software and start the installation process. No? Really? Well, even so, you might want to mosey on down to the ever pleasant Oracle Technology Network and take a gander of the new WebLogic Portal and the wonders that it beholds.

All kidding aside, it does have a plethora of new features and improvements that belie it’s humble update from 10.3.1 (or 10.3.1.0.2 for those who like to patch these things) to 10.3.2. And as everyone likes lists, here’s one list for your enjoyment:

  • Windows installation kit is slightly (~100Mb) larger than before, which is nice
  • Binary installation now allows you to choose WebLogic SCA and Oracle Enterprise Pack for Eclipse
  • Prebundled JDK’s (well <a href=http://www.oracle.com/us/sun/index.htm alt=Oracle Buys Sun>they own them both now</a>) are version 1.6.0_14 instead of 1.6.0_05
  • The Eclipse and plugins want to install to a directory called oepe_11gR1PS1, how about a mouthful
  • The installation screens promote JSF 1.2 and full integration to UCM (and a richer web experience, but please..)
  • JSR-286 \o/ and WSRP 2.0, also UUP REST services
  • WebLogic Server is the same version (10.3.2) as WebLogic Portal, except for the marketing version, which is 11gR1 for WLS and 10gR3 for WLP (a rose by any other name..)
  • Funnily (ha ha?) enough the rest of the promos are about WebLogic Server and Oracle Technology Networks

So what to think of these things? Same same but different? We’ll just have to wait and see until the grand publishing of the Roadmap/Statement of Direction, hope it comes soon.

Oh, and just a quick run-through of the Dom^H^H^H Fusion Middleware Configuration Wizard, in the form of a list, because.. well you know why:

  • You are no longer allowed to have weblogic/weblogic, so I guess the new standard is weblogic/weblogic1 or something? This special character requirement obviously comes from WLS
  • The database settings (and you will need to go through these now) are more simple, except that from a usability standpoint the database Test Connections (which now runs automatically) screen warns that PointBase is not available. Don’t Panic! It’s all OK, just move on to the next screen and ignore the warnings, the SQL scripts will load up fine
  • Now the Dynamic Visitor Tools libraries seem to be deployed automatically, which is nice
  • And bye bye Autonomy, it was great knowing you