LiveCycle ES3 – FileNet Connector for FileNet 5.0 – Documentation Clarification

Issue:
For LC ES3 – the “Preparing to Install Adobe LiveCycle ES3″ Guide – section 2.2.9 (Additional requirements for Connector for IBM FileNet) – for FileNet Connector configuration is unclear.

The section reads as below –
=======
IBM FileNet 5.0
If LiveCycle is connecting to IBM FileNet 5.0 Content Engine, you must install the Content Engine Java Client. Use the IBM FileNet 5.0 content engine client installer located by default in C:\Program Files\FileNet\CEClient. During installation, select at least one of the components from Application Engine or Process Engine on the component selection screen.

For IBM FileNet 5.0 Process Engine, you must install the IBM FileNet 5.0 Process Engine Client located by default in C:\Program Files\FileNet\BPMClient. During installation, select the Other option on the component selection screen.
=======

Questions:
The above text in red does not clearly answer the below questions:
– Does this mean that during the Java Client installation, the user needs to point to an existing Application Engine installation (which maybe be on a different server than LiveCycle)? 
– Or does this mean that the Java Client has to be installed where the Application Engine resides (which it already is) and so this step can effectively be skipped? 
– Or does this mean that another instance of Application Engine needs to be installed on the same server as LiveCycle?

Answer:
LiveCycle ES3 Connector for IBM FileNet needs the FileNet’s client jars to be available on the LiveCycle machine. The user can either properly install the Content Engine client and Process Engine client software on the LiveCycle machine OR as a shortcut he/she can just copy the Content Engine client and Process Engine client jar files (list os jars will be provided in the FileNet Documentation) to any folder on the LiveCycle machine and provide the folder path while configuring the LiveCycle server.

select at least one of the components from Application Engine or Process Engine on the component selection screen” – This is a documentation bug. The user just needs to select “Other Applications” while installing the client software (for both Content Engine client and Process Engine client) in case of FileNet 5.0.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (2 votes cast)
LiveCycle ES3 - FileNet Connector for FileNet 5.0 - Documentation Clarification, 10.0 out of 10 based on 2 ratings

About Ameeth Palla

Ameeth Palla is a Technical Account Manager for the Adobe Digital Enterprise Platform team. Previously he was in the role of a Technical Expert for LiveCycle for the the Technical Response Team (what is now the Sr.Support Architect role). In both roles, Ameeth handled several technical issues for various customers and worked closely to aid with Sales POC's, Development/Implementation and Manitenance of LiveCycle/ADEP Projects. In the current role he handles several high profile customer accounts and provides guidance in all aspects of LiveCycle/ADEP. Also he is a Certified LiveCycle ES2.5 Process Management Expert. He was nominated for the 'Adobe Founders Award' and the 'Excellence Matters' award for LiveCycle/ADEP BU.
This entry was posted in Adobe LiveCycle ES3 and tagged , , , . Bookmark the permalink.

One Response to LiveCycle ES3 – FileNet Connector for FileNet 5.0 – Documentation Clarification

  1. Ketty says:

    Nice blog! All articles is very intereting and useful !