Posts tagged filenet

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 FilesFileNetCEClient. 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 FilesFileNetBPMClient. 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?

---

Read the complete post at Adobe LiveCycle Blog.

Store Content to FileNet server using LiveCycle Java APIs

- Pankaj Gakhar, Software Engineer @ Adobe

You should have LiveCycle server installed and LiveCycle connector for IBM FileNet should be configured with it.

Follow the steps below to store content to FileNet server using LiveCycle’s Java APIs:

1. Create ServiceClientFactory Object.

2. Create an object of IBMFileNetContentRepositoryConnectorServiceClient class using the object of ServiceClientFactory class.

---

Read the complete post at Adobe LiveCycle Blog.

Go to Top