Documentum D7, Java 7, Documentum Clients, and the Compatibilities

We are asked many times if Documentum will be capable of supporting Java Version 7, specifically the content server, webtop and the xPlore index server.

Documentum Version 7 (D7) was releases at 2012 Q4. The benefits include the performance improvement and Java 7 version support. D7 is using Intelligent Session Management (ISM) which allows several users to share the same connections at the same time.  Therefore, it reduces the number of open connections and active sessions, which in turn dramatically reduces the amount of resources required.

After D7 release, here is the updated for Java 7 support as of today

Content Server Version 7: Java Version 7 64 Bit supported

Documentum Admin Version 7: Java Version 7 supported

xPlore 1.3:  xPlore release notes only mention Java 7 for client browser to access the xPlore administration UI. However, the server (xDB included) uses Java 6 (1.6.0_31), Java 7 but it hasn’t been certified for this version.

Webtop: Version 6.7 SP2 (future within first half of 2013) will support D7 with DFC 6.7SP2 release, which I believe will support Java 7 as well.

Documentum DFS File Upload Limit

Documentum DFS has a default size limitation for uploading the large file. I believe it is 50 Mb. When you upload the large fie size like 60M, it gives java.lang.OutOfMemoryError.

But there is a way to bump up the maximum file size, using UCF mode to transfer the file. For the detail implementation, please refer DFS development guide

After refactored the code, the test for uploading 60MB file is very smooth.

Cloud Computing

Recent government forecasts IT cloud services expenditures to reach $21.5 billion in 2010 and over $72.9 billion worldwide in 2015. This would be over a 300% increase in IT cloud spending.

Gartner defines Cloud computing environments as having eight key service attributes which distinguish them from virtualization and clustering architectures.
● Shared, standard service. Built for a market (public cloud); internal shared (private cloud).
● Solution packaged. A “turkey” offering, integrates required resources.
● Self-service. Administration and provisioning; may require some “on boarding” support
● Elastic scaling. Dynamic and fine grained.
● Use-based pricing. Supported by service metering (private may not chargeback)
● Accessible via the Internet. Ubiquitous (authorized) network access
● Standard UI technologies. Browsers, Rich Internet Application (RIA) clients, and underly-ing technologies.
● Public service interface/Application Programming Interface (API). Web services and other common Internet APIs

Beyond these service attributes, there are three major delivery models:
● Public. Service shared among unrelated enterprise and consumers; open to a largely unrestricted universe of potential users; designed for a market, not a single enterprise
● Private. Service shared within a single enterprise (or extended enterprise), with restrictions on access, and level of resource dedication, defined/controlled by the enterprise, and beyond control available in public cloud offerings; can be onsite or offsite; can be managed by a third-party or in-house staff
● Hybrid. Service that is delivered through a combination of public and private cloud models

There are three cloud computing categories.
1) Software as a service (SaaS) ensuring each capability is provided to our client to use their applications on a cloud infrastructure. This also includes development tools, databases and system software
2) Platform as a service (PaaS) providing the capability to deploy onto the cloud infrastructure using programming languages or tools. The primary difference between SaaS is that PaaS providers operate an integrated environment versus delivery of a single application.
3) Infrastructure as a service (IaaS) providing the capability of provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications.

SharePoint Server and Documentum Integration

There are three EMC products that can be used to integrate Documentum with SharePoint:

1. MyDocumentum for SharePoint
2. Repository Services for SharePoint
3. SharePoint Documentum Framework (SDF)

Each product can meet the different need depending on the requirement. Here are some pros and cons of each product. 

MyDocumentum for SharePoint: Configure SharePoint  interface using Microsoft Portal Webpart to access the Documentum content server directly.

Pros:

• Provide Content Library Service, and the options for configuring functions and displaying folders and documents
• Provide Simple Search and Advanced Search
• Allows users to work from a single SharePoint UI

Cons:

• No business logic implemented within the UI
• No software development kit
• Search Documentum content only

Repository Services for SharePoint:  Centrally manage Sharepoint Content at the Documentum Repository.

Pros:

• No impact for SharePoint end-user experience
• Drive mixed enterprise-wide business process
• Reduction in SharePoint operating costs

Cons:

• Maintaining two copies meta both at Sharepoint SQL server and Documentum SQL server

SharePoint Documentum Framework: A customization framework that allow you to leverage most Documentum functionality within a SharePoint product

Pros:

• Providing Software Development Kits
• Using Documentum Foundation Service (DFS) Extensions
• Enable the user to add custom menu items at Sharepoint that can call DFS
• Integrating with SharePoint workflows

Cons:

• Only sold as part of an implementation under EMC Professional Services agreement.

Security Alert CVE-2010-4476

Oracle issued Security Alert CVE-2010-4476. Documentum provides the script to automatically update the most Documentum products, but  xPlore search Engine has to be manually updated and there is a couple of steps we must follow.

Upgrade JDK for xPlore

1. Stop all services;
2. Copy <xPlore> to <xplore>.orig
3. Rename <xPlore>/jdk to <xPlore>/jdk.orig
4. Install jdk
For windows, get jdk-6u24-windows-i586.zip and extract to <xPlore>\jdk

5. Install jdk for jboss
rename <xPlore>/jboss4.3.0/jdk to <xPlore>/jboss4.3.0/jdk.orig
For 32 bit xPlore, copy <xplore>/jdk to <xPlore>/jboss4.3.0/jdk

6.Start your xPlore instance or index agent instance. Check that the new version of java is used by looking into the boot.log in <xPlore>/jboss4.3.0/server/<InstanceName>/log

 

Documentum Mobile

Mobile is a really hot topic. EMC has a Documentum Mobile product. Therefore we did some research on it.

The release of the Documentum Mobile Client solution consists of two components: Documentum Mobile Server and the EMC Documentum Mobile client. The client is available as a free download from Apple’s App Store and the Documentum Mobile Server is available for download on Powerlink.

A Mobile user is entitled to use Documentum Mobile with a Documentum Client named user and must be accompanied by a Documentum Platform named user license. The client named user can be any one or more licenses of: Webtop,  My Documentum, xCP User Bundle,  etc.

Customers will also need two additional components: the Thumbnail Server (provided with the platform) and the Documentum Mobile Server. These are the infrastructure components that support the instance of the mobile client.

The Documentum Mobile Client and Server are not free, they are additional entitlements included with Documentum Platform and Documentum Clients. The Mobile Client is a free download from Apple’s App Store but the user must still be licensed to use the product.

Enterprise Content Management solution provider

Posted on May 23, 2012 by America On Top Corp (AOT) Blogs

America On Top Corp (AOT)  is Enterprise Content Management solution provider:

– Documentum COTS product support and customization
– Enterprise E-mail Record Management Solution
– Lotus Notes Email Archiving Services
– Web Content Management
– Records Management
– SharePoint Solution
– Search and Retrieval Technology

Create Window Installer For Java Application using Freeware

There are two steps:

1)     In order to use open source, I have to use Lauch4J to wrap Java applications distributed as jars in lightweight Windows native executable. For example, Lauch4J will create BulkExport.exe based on BulkExport.jar. JSmooth is also a good tool, but is little out of date and we also need to write the ANT script. Lauch4J is strictly a GUI tool.

2)     Use Advanced Installer. This is a unified package containing the complete Advanced Installer application, which includes Freeware, Professional, For Java, Enterprise, and Architect. Freeware features can be accessed at any time by creating a project of type “Simple”

We create a Simple project packing it into MSI window installer file, such as BulkExport.msi