Hand-picked user assistance content from the LiveCycle community
LiveCycle Enterprise Suite
LiveCycle Cluster Verification
0308 days
On top of J2EE clustering, LiveCycle is clustered using Gemfire Distributed Cache. In cluster deployments, it is important that all the members of a LiveCycle cluster are able to find each other so that they can keep their individual caches in synchronization with one another. LiveCycle Cluster is configured properly or not can be identified based on two key indicators. The following are the key indicators.
- Clustered Scheduler Service
- Gemfire Logs
---
Read the complete post at Adobe LiveCycle Blog.
Re-build lucene indexes for Content Services
0308 days
- Abhijit Ghosh, TRT Engineer @ Adobe
Content services uses the filesystem to store Apache Lucene indexes (/lucene-indexes). At times we are faced with the need of re-building indexes hence just wanted to summarize the ways in which the same can be achieved:
1. Include the JVM argument –Dindex.recovery.mode=FULL and restart the server.
2. Stop the server, delete the lucene indexes under the index root directory and restart the server.
3. Change the index directory to a different location during restart so that indexes are re-built again.
Adobe LiveCycle Content Services Delete
0309 days
Adobe Content Services sometimes takes a lot of amount to delete a directory if there are a lots of nodes under the tree.
Suppose we need to delete Myapp node in the figure above. The conventional way to delete is through the Content Space UI. However, if the subtree rooted at Myapp is relatively large, it may take long time to delete the sub-tree.
A script has been written specifically for Oracle DB which helps in deleting the node in a definite amount of time. Here are the steps to be followed:
---
Read the complete post at Adobe LiveCycle Blog.
LiveCycle ES3 – FileNet Connector for FileNet 5.0 – Documentation Clarification
0309 days
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?
---
Read the complete post at Adobe LiveCycle Blog.
Calling custom code implementation during LiveCycle Server Startup
0311 days
- Abhijit Ghosh, TRT Engineer @ Adobe
We were recently working on a customer scenario who wanted to make a custom code call during server startup.In order to achieve the same you would need to implement theLoad interface in your custom component as described below:
In the component.xml you would need to use the load-class tag in for the classes which implement the same and are to be loaded.
---
Read the complete post at Adobe LiveCycle Blog.
LiveCycle Cluster – TCP based JBoss Clustering
0326 days
- Pankaj Parashar, Lead Softweare Engineer @ Adobe
Adobe LiveCycle comes with pre-configured JBoss (Community Edition only) . The preconfigured JBoss has both standalone and cluster-enabled configurations. All cluster-enabled configurations are based on UDP by default. Various enterprise organizations have very restrictive network policy and don’t allow multicasting in their networks. For such organizations, TCP based clustering is recommended option. JBoss instances belonging to different subnets require TCP based clustering only. In this article, we will go through detailed instructions to configure TCP based JBoss cluster. These instructions are applicable for both preconfigured JBoss and downloaded JBoss (Version 5.1 only).
The Following are the detailed instructions for TCP Clustering:
---
Read the complete post at Adobe LiveCycle Blog.
Store Content to FileNet server using LiveCycle Java APIs
0327 days
- 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.
Installing and Configuring LiveCycle ES3 Connector for Microsoft SharePoint 2010 for JBoss, MySQL, Windows
0332 days
- Pankaj Gakhar, Software Engineer @ Adobe
The LiveCycle ES3 connector for Microsoft SharePoint 2010 contains two parts:-
- Document Services Component (DSC) which is installed on LiveCycle Server.
- Web Part that is installed on the SharePoint Server.
Installing Adobe LiveCycle ES3 Connector for Microsoft SharePoint DSC (Fresh Installation)
Install the LiveCycle ES3 server on your machine and follow the below steps to configure the SharePoint Connector:-
1. Move to the LiveCycle server installation directory and start the LiveCycle Configuration Manager (LCM). LCM is available at <LIVECYCLE_INSTALL_DIR>/configurationManager/bin/ConfigurationManager.exe or .bat.
2. If you are adding SharePoint to an existing LiveCycle ES3 Installation, please go to section Adding SharePoint Connector to an existing LiveCycle ES3 installation. If this is a fresh installation then, choose express mode of installation and on the Modulesscreen select the components that you want to install along with LiveCycle ES3 Connector for Microsoft SharePoint.
---
Read the complete post at Adobe LiveCycle Blog.
