In CQ you have the form functionality available that allows you to create a form on a page, for each form you can specify a “thank you” page that will be displayed when the form is submitted.
In this blogpost I will explain how you conditionally can route to different thank you pages depending on the values entered by the user.
On November 9th Adobe announced our focus on Digital Marketing and Digital Media. In a recent blog post, our CEO Shantanu Narayen described Adobe’s transformation and plan to focus in these two areas. I would like to provide some additional color to that message and what it means for LiveCycle, Adobe’s enterprise business and our customers.
The Adobe LiveCycle business will continue to pursue enhancements and new customers in select verticals such as government and financial services. We will continue to support customers in all verticals.
We will maintain our investment in the product line in upcoming releases and we will continue to provide bug fixes, security updates, and support for new versions of operating systems, application servers, databases and browsers.
Over the years, we have built a large portfolio of LiveCycle customers and a large partner network. The LiveCycle team looks forward to continuing to support our customers.
Dave Welch
Senior Director LiveCycle
In the ADEP release, the Experience Server “Quickstarts” come with a Java Content Repository (JCR) called CRX. This is horizontally scalable by clustering multiple nodes and putting a load balancer in the front.
TERMINOLOGY
———–
You can have a farm of multiple CRX nodes that are unaware of one another (not clustered, but only load-balanced). Adobe documentation calls this “Read-Only Clustering” but this is not really clustering in the traditional sense.
You can also have “true” clustering. It can be of three different types:
1) Shared Journal + Shared Data Store
2) Shared Data Store only (see Steve Forrest’s blog posts 1 and 2 on how to configure this)
3) Shared Nothing
#1 and #2 requires that you set up a network share using NFS, SAMBA or CIFS.
Problem: Your tar journal is growing and consuming a lot of space.
Solution: If you are using shared clustering, Please see this.
For ‘Shared Nothing’ Clustering, you need the following configuration (If you want rotation to happen after every 24 hours) in repository.xml
<Journal>
<param name=”maxFileSize” value=”104857600″ />
<param name=”maximumAge” value=”PT24H” />
</Journal>
Sometimes on a project you know that you just have to write a blogpost, because you struggled too long with an issue to get it resolved.
The goal :
We wanted to use the twitter4j api inside on our Java-classes in the CQ5.4 installation.
The development was ok, and via maven we used the following dependency to make the code work :
<dependency>
<groupId>org.twitter4j</groupId>
<artifactId>twitter4j-core</artifactId>
<version>[2.2,)</version>
</dependency>
So far so good, deployment is then the next step. We use the “maven-bundle-plugin” to generate the manifest file for the OSGi-bundle.
After the deployment, the following errors showed up in the system-console (http://localhost:4502/system/console/bundles/)
twitter4j — Cannot be resolved
twitter4j.conf — Cannot be resolved
And the status of the bundle was set to “Installed” and not “Resolved”
These errors were caused because I didn’t put the twitter4j packages in the <Export-Package> element of the “maven-bundle-plugin”.
> /repository/repository/index
Lucene Search Index for jcr:system (includes jcr:versionStorage)
> /repository/workspace/crx.default/index
Lucene Search Index for crx.default workspace
> /repository/workspace/crx.default/index*.tar
Tar PM Index for crx.default workspace
> /version/index
Tar PM Index for version workspace
> /tarJournal/index*.tar
Tar PM Index for the cluster journal for Journal PM in 5.4
Snapshot of exporting user report
The new Reporting Framework in CQ5.4 allows to generate customized reports on all available information. Example to help you monitor and analyze the state of your instance, CQ provides a selection of default reports, which can be configured for your individual requirements. More details click here.
This article describes three steps to export to csv.
When you install the CQ quickstart, or the ADEP Solutions Quickstart, the repository file structure (and initial repository contents) is created by default under drive:\quickstart installation directory\crx-quickstart\repository\
You can override this behaviour and have the repository created in a custom location as long as you perform the customization of the install process prior to installing the quickstart the first time.
Scenario Described:
I recently worked on an escalation where customer was not able to remove “samples” category using LiveCycle Admin UI -> Services > Applications and Services > Category Management. Error message was:
ALC-DSC-115-000: com.adobe.idp.dsc.registry.EndpointCategoryInUseException: Cannot delete Samples endpoint category because it is being used.
The reason they were not able to delete the “samples” category was because it was associated with specific Task Manager Endpoints.
Scenario:
Often times we run into situations where form rendering or flattening (via Forms Service or Output Service) fails and server log shows a high level error message like -
——
<Error> <com.adobe.formServer.PA.XMLFormAgentWrapper> <BEA-000000> <ALC-OUT-002-004: Unable to find service: XMLFormService, error: Connection to failed service.>
——
Stacktraces are not typically useful in that case because problem is typically related to something on the native side viz. Things related to XMLForms native process.
We recently encountered this error on LiveCycle ES3 (a.k.a. ADEP) deployed on Weblogic 10.3.4 and RHEL 5.5 64-bit server.
