Multilingual Documentum Content in WebLogic Portal

Tuesday, February 14, 2006

Handling multilingual content from Documentum in WebLogic Portal using a little known Documentum configuration setting.

Let me preface this entry by stating I am not a Documentum guru and I may not be able to answer detailed follow-up questions. Having said that, a colleague of mine, Scott Hammer, recently pointed me to a lesser known feature in the Documentum JDBC driver that can be quite useful when dealing with multilingual content.

Documentum provides a variety of ways to integrate with WebLogic Portal, if you are using Documentum Site Caching Services (SCS) and choose to integrate to Portal in a loosely coupled way using the Documentum JDBC driver, you may have run into an issue handling multilingual content. As I understand it, Documentum handles multilingual content by publishing the content to separate SCS sites under the same structure and file names. Unfortunately, with the Documentum JDBC driver the contentURL that points to the site where the content is fetched from is in a global properties file. This means that on the surface it appears that you cannot setup multiple repositories to handle each language.

Fortunately Scott knew about an override that enables you to specify the contentURL on a per connection pool basis enabling the configuration of multiple repositories in the VCR. This override is covered in the Documentum JDBC driver guide but is easy to miss. Essentially, when configuring the Documentum JDBC driver in a connection pool in config.xml, you can specify contentURL in the properties attribute of the connection pool. When specified, this local setting will override the global setting enabling you to specify the content location on a pool by pool basis. You can then configure multiple repositories in the Portal Admin tool with each repository pointing to a different Documentum connection pool.

Posted by Gerald Nunn at 4:02 PM | Categories: WebLogic | | | Permalink