IBM Support

Publishing features in IBM FileNet Content Management 5.2

Technical Blog Post


Abstract

Publishing features in IBM FileNet Content Management 5.2

Body

Let's take a look at the Publishing features in IBM FileNet Content Management 5.2. There are two different types of Rendition Engines available which allow publishing content to either HTML or PDF formats. The first Rendition Engine is based on the Liquent InSight Rendering product that allows publishing of common document formats such as MS Office, AutoCAD and image formats to both PDF and HTML. The second Rendition Engine is based on the Darwin Information Typing Architecture (DITA) Open Toolkit and allows publishing of DITA projects to PDF documents.

Once a Rendition Engine has been installed and configured, there are three ways to publish a document. The process is the same for either Rendition Engine. You can publish a document by calling the source document object's publish and republish methods in one of the FileNet P8 APIs, a process workflow or the IBM FileNet Workplace application. Below are examples of each.

 

1. Process workflow with a publishing step.



image

2. Publishing a document through Workplace.





image

3. Java API example of pubishing a document.



// Define the publication name in XML format.

String publishOpts = new String("<publishoptions><publicationname>My New Title</publicationname><publishoptions>");



// Get a reference to the source document to publish.

String path = "/someFolder/My Source Document";

Document sourceDoc = Factory.Document.fetchInstance(objectStore, path, null);



// Retrieve a collection of publish templates.

// (In a typical scenario, you might qualify the publish templates query to get the ones that can be applied.)

String sqlStr = "Select * from PublishTemplate";



SearchSQL sql = new SearchSQL(sqlStr);

SearchScope ss = new com.filenet.api.query.SearchScope(objectStore);

EngineCollection ec = ss.fetchObjects(sql, null, null, Boolean.TRUE);



Iterator iter = ec.iterator();

if (iter.hasNext())

{

PublishTemplate pt = (PublishTemplate) iter.next();



// In this example, we'll use the first publish template.

// Submit the publish request and return the PublishRequest object for this publish operation.

PublishRequest pubReq = sourceDoc.publish(pt, publishOpts);

pubReq.save(RefreshMode.REFRESH);

}






Publishing a document with a Rendition engine is useful when you want to make a document available, but you do not want others to be able to modify the document. On the published document, you can define different security, properties, location and specific file and presentation formats. At the same time, you maintain control over the source document and can continue to make changes that are not visible to users of the published document. When you are ready to make the new version of the document available to your users, just republish the source document which creates a new version of the published document.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

UID

ibm11280308