FileNet Integration Process

gowebing

FileNet is an enterprise content management (ECM) platform developed by IBM. It provides various tools and services for managing content, processes, and workflows within an organization.

Documentum product is an enterprise content management (ECM) platform. It provides a wide range of tools and services for managing content and information in organizations. Documentum was originally developed by Documentum, Inc. and was later acquired by EMC Corporation, which was, in turn, acquired by Dell Technologies. Below are some of the benefits of migrating FileNet into Documentum.

  1. Improved user experience: Documentum's user interface is often seen as more modern and user-friendly than FileNet's, which can lead to improved adoption and productivity among users.
  2. Simplified architecture: Documentum's architecture is based on a client-server model, which can simplify deployment and management compared to FileNet's more complex service-oriented architecture.
  3. More flexible integration: Documentum's API is known for being more flexible and easier to work with than FileNet's, which can make it easier to integrate with other systems and applications.
  4. Strong compliance features: Documentum has a strong reputation for compliance, including support for industry-specific regulations such as FDA 21 CFR Part 11 and SEC Rule 17a-4, which can help organizations ensure regulatory compliance.
  5. Lower cost: Depending on the specifics of the migration project, moving from FileNet to Documentum may result in lower licensing and maintenance costs, which can help organizations save money over the long term.

Integrating FileNet with Documentum is a complex process that requires meticulous planning and execution. Here are the general steps involved in integrating FileNet with Documentum:

  1. The first step in integrating FileNet with Documentum is to identify the integration requirements, such as the types of content to be incorporated, the frequency of updates, and the security requirements.
  2. There are different integration approaches available for integrating FileNet with Documentum, such as using APIs, middleware, or third-party integration tools. The choice of integration approach will depend on the requirements and the existing infrastructure.
  3. The next step is to map the metadata and content from FileNet to Documentum, such as file types, naming conventions, and metadata fields. This requires careful planning to ensure that the content and metadata are properly mapped and synchronized between the systems.
  4. Once the metadata and content mapping is complete, integration code needs to be developed to transfer content and metadata between FileNet and Documentum. This may involve using APIs or other integration tools to share content and metadata between the systems.
  5. After the integration code is developed, it needs to be tested and deployed in a controlled environment to ensure that it works as expected. This may involve testing for content and metadata transfer, security, and performance.
  6. Once the integration is deployed, it needs to be monitored and maintained to ensure that it continues to work correctly. This may involve monitoring performance, troubleshooting issues, and updating the integration code as needed.

The integration specifics will depend on the requirements and the existing infrastructure.

An example code snippet for integrating FileNet with Documentum using APIs. This code assumes that the FileNet Content Engine API and the Documentum Foundation Services (DFS) API are already installed and configured:

Set up the FileNet Connection

Java
  
String fileNetUrl = "http://<hostname>:<port>/wsi/FNCEWS40MTOM/";

String fileNetUsername = "<username>";

String fileNetPassword = "<password>";

Connection fileNetConnection = Factory.Connection.getConnection(fileNetUrl);

Subject fileNetSubject = UserContext.createSubject(fileNetConnection, fileNetUsername, fileNetPassword, null);

UserContext.get().pushSubject(fileNetSubject);


Set up the Documentum Connection

Java
  
String documentumUrl = "http://<hostname>:<port>/documentum/services/";

String documentumUsername = "<username>";

String documentumPassword = "<password>";

Service documentumService = new Service(documentumUrl, "Documentum", documentumUsername, documentumPassword);


Get the Content From FileNet

Java
  
String fileNetDocId = "<FileNet document ID>";

Document fileNetDoc = Factory.Document.fetchInstance(fileNetConnection, fileNetDocId, null);


Create a New Documentum Document

Java
  
String documentumFolderId = "<Documentum folder ID>";

String documentumDocName = fileNetDoc.getProperties().getStringValue("DocumentTitle");

String documentumDocContent = fileNetDoc.getContent();


Java
  
IDfSession documentumSession = documentumService.getSession();

IDfFolder documentumFolder = (IDfFolder)documentumSession.getObject(new DfId(documentumFolderId));

IDfSysObject documentumDoc = (IDfSysObject)documentumSession.newObject("dm_document");

documentumDoc.setObjectName(documentumDocName);

documentumDoc.setContentType("pdf");

documentumDoc.setFile(documentumDocContent);

documentumDoc.link(documentumFolder.getObjectId());

documentumDoc.save();


Clean up the Connections and Sessions

Java
  
UserContext.get().popSubject();

documentumSession.disconnect();


This code snippet shows how to transfer a PDF document from FileNet to Documentum. It sets up the connections to both systems, fetches the document content from FileNet using the Content Engine API, creates a new document in Documentum using the DFS API, and transfers the content from FileNet to Documentum. Finally, it cleans up the connections and sessions.

 

 

 

 

Top