Posts in Category "Contentspace"

Content Services: Disable content indexing

You can disable content indexing to improve Content Services 9 performance. Disabling indexing also disables text-based search within new content. However, you can still search within already-indexed content.

Follow these steps to disable indexing:

  1. In the adobe-contentservices.ear file, navigate to LiveCycle Content Services.ear/contentservices.war/WEB-INF/classes/alfresco/model and open the contentModel.xml file for editing.
  2. Locate the following line:
    <type name=”cm:content”>
  3. Set the index enabled and tokenized properties to false.
  • Change <index enabled=”true”> to <index enabled=”false”>.
  • Change <tokenized>true </tokenised> to <tokenized>false </tokenised>.

Disable the conversions required for indexing

To realize additional performance improvements, disable the conversions required for indexing. Follow these steps:

  1. In adobe-contentservices.ear, browse to contentservices.war\WEB-INF\classes\alfresco\extension.
  2. Preserve a backup of the custom-metadata-extractors-context file.
  3. Delete this file from the EAR.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Content Services: Dependencies for indexing different types of content

Indexing of content in LiveCycle Content Services 9 depends on different LiveCycle ES2 components and services. Here are a few important prerequisites:

  • Indexing of PDF files (except for dynamic PDF forms) requires the Assembler service, which is part of all LiveCycle ES2 installations.
  • Indexing of dynamic PDF files requires LiveCycle Output 9. If Output is not installed, the FormDataIntegration service, available on all LiveCycle ES2 installations, is used instead. However, in such cases, for dynamic PDFs created in Acrobat, only the form data is indexed. The form design is left unindexed.
  • Indexing of Microsoft Word 2007/2010 files (.docx) requires PDF Generator 9 (the GeneratePDF service).

Additionally, files protected by LiveCycle Rights Management 9 are not indexed.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)

Content Services ES2: Improving performance

You can disable content indexing to improve Content Services ES2 performance. However, keep in mind that disabling indexing will also disable text-based search within new content. To disable indexing:
  1. In the adobe-contentservices.ear file, navigate to
    LiveCycle Content Services.ear/contentservices.war/WEB-INF/classes/alfresco/model and open the contentModel.xml file for editing.
  2. Locate the following line:
    <type name=”cm:content”>
  3. Set the index enabled and tokenized properties to false
  • Change <index enabled=”true”>  to <index enabled=”false”>.
  • Change <tokenized>true </tokenised> to <tokenized>false </tokenised>.
For additional performance improvements, you can disable the conversions required for indexing. To disable these conversions:
  1. In adobe-contentservices.ear, browse to 
    contentservices.war\WEB-INF\classes\alfresco\extension.
  2. Preserve a backup of the custom-metadata-extractors-context file.
  3. Delete this file from the EAR.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

New admin guide for Content Services ES2 is live

The Administering LiveCycle Content Services ES2 guide is now available. The guide discusses the following administration activities, besides others:

  • Configuring the inbound and outbound email service
  • Monitoring Content Services ES2 using the Java Management Extension (JMX)
  • Estimating how many servers to use for running Content Services ES2

View this new guide here.

Also check out the following related Help:

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES web application cheat sheet

After installing LiveCycle ES, there are a number of URLs that you use to access various LiveCycle ES web applications. Here’s a cheat sheet for those URLs.

Continue reading…

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (2 votes cast)

Comparing Alfresco Enterprise Edition and Adobe LiveCycle Contentspace ES

People sometimes ask what the difference is between Alfresco and Adobe LiveCycle Contentspace ES, so we thought posting a quick overview on the subject would be helpful.

LiveCycle ContentSpace ES is based on Alfresco 2.1 and offers full Alfresco functionality*, plus LiveCycle Content Services ES. Adobe added more service capabilities by extensively customizing the Alfresco user interface and by integrating various LiveCycle Content Services ES solution components.

Technically speaking, these are the key differences between Alfresco Enterprise Edition and LiveCycle Content Services ES:
– Web Content Management is not embedded or distributed.
– Replaced jBPM with LiveCycle Process Management ES.
– Replaced PDF libraries.
– Enhanced security to enable single sign-on (SSO) with other LiveCycle components such as Workspace and integration with Adobe User Management.
– Added support for the full LiveCycle ES 54 platform matrix including clustering/failover.
– Integrated LiveCycle ES solution components such as LiveCycle Workspace ES, LiveCycle Rights Management ES, and LiveCycle PDF Generator ES.

The key architecture of Alfresco in terms of Java APIs, ACPs, customized content models, actions, and so forth, are the same.

Using LiveCycle Contentspace ES, end users can manage the content through library services such as versioning, check-in/checkout, rights protecting, and archiving according to policies. Developers can also implement processes to enable end users to interact with content and automate procedures like document transformation and PDF generation, rights management, as well as workflows like data capture, and document review and approval.

Along with the Alfresco content management system capabilities, LiveCycle Content Services ES provides the following functionality.

Process automation

Content Services ES can leverage LiveCycle ES for business events by running processes based on content events, such as adding new documents to the repository. A process can also wait for content events to occur, such as a completed document review.

Users can perform the following tasks:
– Attach files, such as reports to a form, and submit the form. After the form is submitted, both the data and the attachments are saved, and can be opened and viewed in the same form layout.
– Access different form applications or content types in the same portal.
– Search and browse by association between processes and documents, and by process and document attributes.

Process initiation

Developers can run processes from LiveCycle Contentspace ES and leverage LiveCycle Workspace ES to review and approve content.

Form rendering

Developers can set up the following form rendering tasks:
– Pre-populate forms by using content or metadata.
– Render forms with attachments from Content Services ES.
– Update forms with a new version of assets referenced during run-time.
– Keep form template versions consistent during the life cycle of the process.

Information protection

Content Services ES can leverage LiveCycle Rights Management ES to automatically apply policies to content that is stored in the repository. Using Rights Management ES, organizations can protect PDF documents. The policies are applied transparently to content when users retrieve content from the repository and save it on the local file system, send content by email to someone who is external to the organization, or place content on devices such as USB keys.

Document output

Content Services ES has pre-built actions that developers can use to automatically convert documents to other formats (for example, from MS Word to PDF). Also, developers can configure actions to start short-lived processes for assembling a set of documents within a shared space into a package, generating PDF files from three-dimensional content, or converting content to PDF/A format for archiving.

* LiveCycle Contentspace ES does not utilize the Web-based Distributed Authoring and Versioning (WebDAV) file server configuration capabilities of Alfresco.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)