Posts tagged "Data Dictionary"

Data Dictionary Best Practices

Correspondence Management DataDitionary provides a representation of the underlying data structure of a complex backend enterprise system in a simple and user-friendly manner which business users can easily understand.

In any enterprise implementation of Correspondence Management usually middle ware developers work on creation of data dictionary.

We get requests from our customers to understand the best practices for creation of DataDictionary.

The answer is try to Keep It Simple.

  1. Do not try to create a single Data Dictionary with tens of thousands of elements to cater to the needs of all the correspondences
  2. If there is a possibility to create multiple data dictionaries by logically separating the correspondences based on business units / business needs , prefer to create multiple data dictionaries.
  3. If a single complex data dictionary is created (even if there isn’t a real need) , there would be some trade-off in the form of performance for some operations like Publishing the datadictionary and preview of letters that use this data dictionary.
  4. Do not try to over complicate the data dictionary by creating too many levels down the hierachy and do not even use a DD which is completely flat.
In case of any confusion or more queries , feel free to post your queries on Adobe LiveCycle forums.

 

ADEP CM : Documentation

 

Adobe® Digital Enterprise Platform (ADEP) offers an integrated set of capabilities and technologies that enable organizations to create Customer Experience Management solutions.

ADEP comprises of two servers :

  1. Document Server :  All the services related to documents and process (of earlier LiveCycle) are now part of ADEP Document Server
  2. Experience Server : All Solutions (applications) and content are part of Experience Server [ Solutions like CM & ICR used Alfresco based Content Services to store all the content in earlier versions , now they use Day's [now part of Adobe] CRX content repository to store all the content]

 

Architecture diagram :

For more information on understanding ADEP architecture refer documentation

 

 

Installation :

Installation of Experience server is as simple as a double click.

Refer to installation document for Experience Server for system requirements and installation steps and steps to configure Experience Server to work with Document server

You can watch following video for the same

 

Release Notes :

Before getting started with the ADEP CM , please spend sometime to go through Release Notes for known issues

 

API Reference Documentation :

What CM includes?
The following picture explains what CM includes :
Solution Guide :
The Correspondence Management Solution Guide provides guidelines to implement correspondence management solutions.
Developer Guide :
For developers who wants to extend the OOTB CM solution to add some new capabilities , they can go through Developer guide
Correspondence Management solution comprises of following three building blocks :
Click on above links for Technical guides of the CM building blocks