Tuesday, May 27, 2014

Caveats on Using WebLogic Server with JDK7

Now JDK 7 has been out for a while (JDK 8 is out too as of writing). There are some caveats using WebLogic Server with JDK 7 you might want to know, not matter it's on 10.3.6 or 12c.

1. Out of memory error on starting Admin Server. This error is caused by the fact that the new JVM requires more PermGen space. Depending on your RAM, you can set it >350m. In my case, I would set the perm size to 512M.

-XX:MaxPermSize=512m

2. In some cases, the new compiler generates larger byte code. It is possible that a large method may exceed the 64KB limit per method. In this situation, you may need to refactor the method. This seems to only affect WebLogic 10.3.6

3. Classes may have been removed that are from the internal package sun.*, or that have been marked as deprecated in a previous version of the JVM. If an application uses these removed methods, a ClassNotFound exception will occur.

4. JDBC 4.1 is introduced in JDK7. JDBC 4.1 methods are not currently supported in WebLogic Server with JDK 7. Calls to these methods will result in an SQLException indicating that the method is not supported.

If you are using WebLogic 10.3.6, after installing WebLogic Server, copy the following files from WL_HOME/modules to JAVA_HOME/jre/lib/endorsed, where WL_HOME is the WebLogic Server installation home directory:
  • javax.annotation_1.0.0.0_1-0.jar
  • javax.xml.bind_2.1.1.jar
  • javax.xml.ws_2.1.1.jar

Reference:

Monday, May 26, 2014

FrameworkFolders Support has come to Oracle WebCenter Portal

As of late April 2014, FrameworkFolders support on Oracle WebCenter Portal has been enabled by Oracle WebCenter 11.1.1.8.3. Previously, Oracle WebCenter Portal only supported Folders_g.

Now it's time to review the essentials on what, why and how.

What's Framework Folders?

Introduced in WebCenter PS5, the framework folders (also called folders component) provide a hierarchical folder interface, similar to conventional file system, for organizing and locating some or all of the content in the repository. It's a scalable, enterprise solution and is meant to be a replacement for contribution folders (folders_g component).

Why it's better than Folders_g (FrameworkFolders vs. Folders_g)?

With the FrameworkFolders component as the underlying folder architecture, many functionalities and features have been made available.
  • Mass metadata updates with folders (metadata propagation):  "Query Folders" is added in the FrameworkFolders component. Query folders are folders that are populated simply by a query. Query folders contain the actual repository content items returned by the query. The contents of query folders can change dynamically as the contents of the repository change. By using the query folder and the propagate function, one can make mass metadata updates of folders in a very easy way.
  • Unlimited content items: There is a limitation of 1000 content items in a folder or subfolders within a folder with Folders_g. There is no such limit with FrameworkFolders.
  • Enhanced search functionality: With frameworkFolders, several enhanced features are available to make search easier and more performant. User can save a query result in a query folder, as well as records management by using RetentionQuery folder. By default, you cannot search folders with folders_g. Now users can search for folders, content items within a folder with FrameworkFolders.
  • Personal folder support: Added personal folder for each user and the content within a personal folder is only available for the user himself/herself.
  • New user interface support: with the FrameworkFolders component, a new look and feel presentation layer of the content server is available. The new UI is built by ADF technology.
How to get it?

For an Oracle WebCenter Portal instance patched from an earlier release, you must continue to use Folders_g. For new installations of Oracle WebCenter Portal, it is recommended that you enable the FrameworkFolders component on Content Server for better performance and so as to be able to use any new Content Server features.

The FrameworkFolders component can be enabled only for the installations that meet the following criteria:

  • You must have a new Oracle WebCenter Portal 11.1.1.8.0 installation. Oracle WebCenter Portal must not have been patched from a previous release, that is, it should be a completely fresh instance.
  • You must have a new installation of Oracle WebCenter Content 11.1.1.8.0, with the FrameworkFolders component enabled. Oracle WebCenter Content must not have been patched from a previous release, that is, it should be a completely fresh instance.
  • Content Server should never have been configured to run with the Folders_g component. You must not enable FrameworkFolders if Folders_g was previously enabled.

To configure FrameworkFolders support for Oracle WebCenter Portal, you need to apply various patches to your new installations of Oracle WebCenter Content 11.1.1.8.0 and Oracle WebCenter Portal 11.1.1.8.0.

To prepare Oracle WebCenter Portal for FrameworkFolders support:

  • Ensure there is no content within Oracle WebCenter Content and Oracle WebCenter Portal
  • Download and apply the WebCenter Content MLR04 patch (latest as of today)
  • Download and apply the WebCenter Portal BP3 patch 18085041
  • Download and apply the WebCenterConfigure component patch 18387955

Reference:

11g Folders – organized, optimized, modernized
Mass Metadata Update with Folders
WebCenter Content 11.1.1.6 FrameworkFolders
Using Folders and WebDAV
Folder Services