Posts in Category "General"

How to hide the ‘DO-NOT-DELETE’ tag with CSS

Problem

The ‘DO-NOT-DELETE’ tracking tag that is added to the end of a reply-to-complete email should be hidden from end users if possible.

Solution

When an HTML email is sent, the ‘DO-NOT-DELETE’ tag can be easily hidden by using a CSS style sheet to hide that section of the email.

Detailed explanation

You can reply to an email to complete a task that you are assigned in LiveCycle Workspace 9. The feature (informally called  “Reply-to-complete”) is available in LiveCycle Process Management 9 and allows you to complete an assigned task without opening the form or even logging in to Workspace. A good example of this might be a purchase request below 200 dollars.

The email that is received from the Assign Task or Assign Multiple User operation in the process includes a tracking tag that is prefixed with ‘DO-NOT-DELETE’. This tag can be confusing to some users when they receive the email so it would be nice if it could be removed from the presentation so that it is not a concern.

The DO-NOT-DELETE tag is easily hidden in HTML emails by adding a small style declaration to your HTML email template. The following html style block should be added to the beginning of your HTML email template:

<style>
p#task-tracking-id
{
display: none;
}
</style>

That’s it! Now the DO-NOT-DELETE tracking id will be hidden in the emails of your end users.

 

- Khushwant Singh

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

SQL Server in Windows Authentication Mode

Administrators can login to SQL Server either in Windows Authentication Mode or SQL server authentication mode. In the Windows Authentication mode, whenever you login to SQL server, you need not to provide the credentials; SQL Server uses your Windows credentials.

1)       Open SQL Server Management Studio, connect to the database server using SQL Server Authentication.

2)       Click Server > Security, and then right-click Logins and select New Login.

3)       Enter the login name in Login Name box [domainName/Username].

4)       Select the Windows Authentication.

5)       Leave the Default Database to Master

6)       In the Select a page pane, click Server Roles, select the sysadmin check box, and then click OK.

7)        Disconnect the Object Explorer and again Connect in Windows Authentication mode.

In the following procedure, [database_name] represents the name of the windows Authenticated DB.

8)       Click Server > Databases > Right Click on Databases and click New Database.

9)       Enter the database name of your choice for example: [database_name].

10)   (SQL Server 2005 Only) Ensure that Use Full-Text Indexing is deselected.

11)   In the Database Data Initial Size MB box, enter the appropriate value:

•      For small development or small production systems, specify 200 MB.

12)   In the Database DataAutogrowth box, enter 50%.

13)   In the Database Log Initial Size box, enter the appropriate value:

•      For small development or small production systems, specify 20 MB.

14)   In the Database LogAutogrowth box, enter 50%.

15)   Click OK to create the database.

16)   Click Server > Databases > [database_name] > Security, and then right-click Schemas and select New Schema.

17)   In the Schema Name box, type an appropriate schema name, example: [schema_Name], and click OK.

18)    Change the default owner to ‘sa’. The detailed steps are listed below:

        18.1 In SQL Management Studio menu, click New Query.

        18.2 In the query Panel, type the following command:

         Use [database_name] EXEC sp_changedbowner 'sa'

        18.3 Click Execute. A success response is displayed in the messages panel.

19)   Click Server > Databases > [database_name] > Security, and then right-click Users and select New User.

20)   Select user Type “Windows User” from the drop down menu.

21)   In the New User dialog box, type the login name and user name as [domainName/UserName] as created through steps 1-7.

22)   Set the default schema to schema created as in step 16-17.

23)    (SQL Server 2008 R2) In the Schemas Owned by this User area, select the schema as created in step 16-17.

24)   Click Server > Databases > [database_name] > Security, and then right-click schema  [created in step 16-17] and select properties and  select permissions

a)       Click search button in Users or Roles and type [database_username] and click OK.

b)       In the Explicit tab grant  the following permissions:

   1. Alter

  2. Insert

 3.  Reference

 4.  Select

 5.  Update

6.  Delete

c)       Click OK.

 25)   Right Click Server > Databases > [database_name] and select properties then select permissions tab

a)       Select Explicit tab

b)       Grant the following  permissions:

1. Connect

2. Create Table

3. Create View

c)       Click Ok.

Associate the LiveCycle user with the database

After you create the LiveCycle user, associate it with the LiveCycle database.

26)   Click Security > Logins, and then right-click [domainName/UserName] and select Properties.

27)   In Login Properties, on the General page, set the user’s default database to [database_name].

28)   Select the User Mapping page and, in the Users Mapped to This Login section, verify that [database_name] is selected, User is set to [domainName/UserName], and Default Schema is set to [schemaName created in step 16-17].

29)   Ensure that [database_name] is selected in the Users Mapped to This Login table, and ensure that public is selected in the Database Role Membership for [database_name] table and then click OK.

Set the isolation level for the LiveCycle database

 LiveCycle requires a specific isolation level to manage deadlocking when long-running transactions occur at the same time as numerous shorter reads.

Important: You must set the isolation level for MS SQL Server to avoid deadlocking issues.

1)        Click Databases and then right-click [database_name] and select New Query.

 Note: [database_name] represents the name you specified when you created your database.

 2)        In the Query panel, type the following text:

ALTER DATABASE [database_name] SET READ_COMMITTED_SNAPSHOT ON GO

3)       Click Execute. A response is displayed in the messages panel.

 Note: In order to deploy the LC when DB is in Windows Authentication Mode, Application Server and DataBase user must be created under same user (DomainName/Username). If Application Server and DataBase do not fall under same user, then create the common user on both the Systems which are having DB and App Servers.

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

Using LiveCycle to programmatically split the PDF documents – Part 1

- Khushwant Singh, Content and Community Lead @ Adobe

A discussion on Adobe forums indicates that a lot of LiveCycle users are trying to figure out how to programmatically split a PDF file. Adobe LiveCycle provides a simple method to programmatically split PDF documents using LiveCycle Assembler service. You can split PDF files using the bookmark tags or by page number.

To split the PDF documents, you require:

  • A DDX (For more information about DDX, see Adobe LiveCycle DDX reference guide)
  • Source documents
  • Access to the running instance of Adobe LiveCycle

You can write a custom DDX document suited to your requirements.  Some of the most commonly requested DDX are:

DDX for splitting PDF document using bookmarks

In the following sample DDXLiveCycle Assembler service generates a single document for each level 1 bookmark in the source document (AssemblerResultPDF.pdf in this example). The Assembler service generates a name for each document that is the concatenation of the following items:

  • A string specified by the prefix attribute
  • A 6-digit sequence number (This number could be used to re-create the original order of the pages after the document is disassembled.)
  • The bookmark title
  • The filename extension .pdf

<PDFsFromBookmarks prefix="stmt">
<PDF source="doc1.pdf"/>
</PDFsFromBookmarks>

DDX for splitting PDF document using page numbers

In this sample DDXLiveCycle Assembler service generates documents for the mentioned page number from the source document. The Assembler service generates a name for each document based on the result parameter specified in the DDX.

<?xml version="1.0" encoding="UTF-8"?>
<DDX xmlns="http://ns.adobe.com/DDX/1.0/">
<PDF result="Final.pdf">
<PDF source="PDF1.pdf" pages="1"/>
</PDF>
<PDF result="Final2.pdf">
<PDF source="PDF1.pdf" pages="2"/>
</PDF>
</DDX>

DDX for splitting PDF document using the page range

In this sample DDXLiveCycle Assembler service generates documents for the mentioned range of the pages. The Assembler service generates a name for each document based on the result parameter specified in the DDX.

<?xml version="1.0" encoding="UTF-8"?>
<DDX xmlns="http://ns.adobe.com/DDX/1.0/">
<PDF result="Final.pdf">
<PDF source="PDF1.pdf" pages="1-5"/>
</PDF>
</DDX>

DDX for splitting PDF documents using page range from different PDF documents and creating a single resultant PDF document

In the following sample DDXLiveCycle Assembler service extracts pages from multiple documents as per the range of pages mentioned in the DDX and generates a single output document

<?xml version="1.0" encoding="UTF-8"?>
<DDX xmlns="http://ns.adobe.com/DDX/1.0/">
<PDF result="Final.pdf">
<PDF source="PDF1.pdf" pages="1-3"/>
<PDF source="PDF2.pdf" pages="4-5"/>
</PDF>
</DDX>

Sample program to split a PDF document
Let us write a simple Java program to split a PDF document into multiple documents.   To download the resources used in this sample program, click here.

Complete the following steps:

  1. Create a new file and add the following code  to the file
    <DDX xmlns="http://ns.adobe.com/DDX/1.0/">
    <PDFsFromBookmarks prefix="Readme">
    <PDF source="AssemblerResultPDF.pdf"/>
    </PDFsFromBookmarks>
    </DDX>

    For this example, save the XML file as shell_disassemble.xml.
  2. Create a new Java project and add shell_disassemble.xml to the project.
  3. Add the following libraries to your project. These libraries are required to invoke assembler service in SOAP mode:
    • adobe-assembler-client.jar
    • adobe-livecycle-client.jar
    • adobe-usermanager-client.jar
    • adobe-utilities.jar
    • jbossall-client.jar (use a different JAR file if LiveCycle ES is not deployed on JBoss)
    • activation.jar
    • axis.jar
    • commons-codec-..jar
    • commons-collections-..jar
    • commons-discovery.jar
    • commons-logging.jar
    • dom-xml-apis-.jar
    • jaxen-.-beta-jar
    • jaxrpc.jar
    • log4j.jar
    • mail.jar
    • saaj.jar
    • wsdl4j.jar
    • xalan.jar
    • xbean.jar
    • xercesImpl.jar
  4. Create a new class named DisassemblePDFSOAP .
  5. Add the source PDF file to the project. I have used AssemblerResultPDF.pdf
  6. Add following code to the class:
    import com.adobe.livecycle.assembler.client.*;
    import java.util.*;
    import java.io.InputStream;
    import java.io.*;
    import com.adobe.idp.Document;
    import com.adobe.idp.dsc.clientsdk.ServiceClientFactory;
    import com.adobe.idp.dsc.clientsdk.ServiceClientFactoryProperties;
    public class DisassemblePDFSOAP
    {
    public static void main (String args[]) {
    Document outDoc = null;
    try{
    //Set connection properties required to invoke LiveCycle ES2
    Properties connectionProps = new Properties();
    connectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_SOAP_ENDPOINT, “http://10.40.18.95:8080″);
    connectionProps.setProperty(ServiceClientFactoryProperties.DSC_TRANSPORT_PROTOCOL,ServiceClientFactoryProperties.DSC_SOAP_PROTOCOL);
    connectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE, “JBoss”);
    connectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_USERNAME, “administrator”);
    connectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_PASSWORD, “password”);//Create a ServiceClientFactory instance
    ServiceClientFactory myFactory = ServiceClientFactory.createInstance(connectionProps);//Create an AssemblerServiceClient object
    AssemblerServiceClient assemblerClient = new AssemblerServiceClient(myFactory);FileInputStream myDDXFile = new FileInputStream(“E:\\workspace\\disassemble\\src\\shell_disassemble.xml”);
    //Create a Document object based on the DDX file
    Document myDDX = new Document(myDDXFile);//Create a Map object to store PDF source documents
    Map inputs = new HashMap();FileInputStream mySourceMap = new FileInputStream(“E:\\workspace\\backup\\disassemble\\src\\AssemblerResultPDF.pdf”);//Create a Document object based on the map.pdf source file
    Document myPDFSource = new Document(mySourceMap);//Place two entries into the Map object
    inputs.put(“AssemblerResultPDF.pdf”,myPDFSource);//Create an AssemblerOptionsSpec object
    AssemblerOptionSpec assemblerSpec = new AssemblerOptionSpec();
    assemblerSpec.setFailOnError(false);//Submit the job to the Assembler service
    AssemblerResult jobResult = assemblerClient.invokeDDX(myDDX,inputs,assemblerSpec);
    java.util.Map allDocs = jobResult.getDocuments();

    //Retrieve the result PDF documents from the Map object

    int index = 0;

    //Iterate through the map object to retrieve the result PDF document
    for (Iterator i = allDocs.entrySet().iterator(); i.hasNext();) {
    // Retrieve the Map object’s value

    Map.Entry e = (Map.Entry)i.next();
    if (index == 0)
    {
    Object o = e.getValue();

    //Cast the Object to a Document
    //and save to a file
    outDoc = (Document)o;
    File myOutFile = new File(“E:\\disassemble\\SplitPDF”+index +”.pdf”);
    outDoc.copyToFile(myOutFile);
    }
    index++;
    }
    if (index > 0)
    System.out.println(“The PDF document was disassembled into “+index+” PDF documents.”);
    else
    System.out.println(“The PDF document was not disassembled.”);

    }catch (Exception e) {
    System.out.println(“Error OCCURRED: “+e.getMessage());
    e.printStackTrace();
    }
    }
    }

  7. Modify the locations mentioned in the sample code according to the file paths in your machine
  8. Run the code.
  9. The code splits the file into multiple PDF documents based on the bookmarks or the page numbers specified in the DDX.

This is first blog in the series of the blogs about programmatically splitting the PDF document. In this blog I have shared sample code to split PDF document using bookmarks. In the follow-up blogs, I will include sample code to split PDF documents using:

  • Page numbers
  • Page range
  • Pages from different PDF documents and generate a single output document
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.2/10 (5 votes cast)

Platform Combinations Supported by LiveCycle

Siddharth Jain, Quality Engineering Manager @ Adobe

Adobe  LiveCycle deployment involves many third-party software like Application Servers, Databases and Operating Systems. LiveCycle team certifies certain platform combinations for each release of LiveCycle. For example, the supported platform combinations for our latest LiveCycle ES3 SP1 offering can be looked at http://help.adobe.com/en_US/livecycle/10.0/supported_platforms.html. It provides details of third-party software along with the version details on which LiveCycle is certified and supported. Given that these third party software keep coming up with their latest offerings too, LiveCycle has a third party software patch support statement available at http://helpx.adobe.com/livecycle/kb/livecycle-third-party-software-patch.html.

Together, these two documents should help you figure out whether platform of your choice is supported by LiveCycle or not. In case, you need any clarification, contact Adobe Enterprise Support for guidance.

If you find that platform of your choice is not supported by LiveCycle, for example, you wish support for version X of a database vendor due to your project considerations while LiveCycle supports version Y, you should contact Adobe Enterprise Support who can guide you on next steps.

In addition, Adobe LiveCycle team has a process known as Customer Commit Request in which such a request can be routed to engineering for evaluation if the customer has committed to using LiveCycle by means of purchase or M&S. If engineering finds that there is feasibility to support such a platform for your identified use, it carries out testing on that platform for your use case on LiveCycle version you intend to use. If all goes well, LiveCycle team reverts back in positive and provides support to you for your specific requirement on your desired platform for that LiveCycle release.

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

Debugging LiveCycle – Working with logs (Part-1)

Ankush Kumar, Lead Software Engineer @ Adobe

Logs are the first thing that come to the mind when we run into an issue. Following are some tips on improving the logging on the application side as well as the application server side.

Enabling/Modifying Logging of Application Servers


JBoss

Jboss, which is bundled with LiveCycle has a pre-configured log4j configuration file. It is present as <Appserver Home>/server/<profile>/conf/jboss-log4j.xml. you can track new packages or existing packages at debug level by simply using the following command:

<category name=”com.adobe.mypackage”>

<priority value=”DEBUG”/>

</category>

From here, you can do the following configurations:

  • Change log file path
  • Change log entry structure
  • Specifying log rotation policy
  • Enable cluster logging

The following JBoss wiki can help you play around the logging file.

https://community.jboss.org/wiki/Logging


Weblogic

Weblogic logging can be configured from Weblogic administration console. There are separate administration consoles for each managed server. On Weblogic administration console, logging can be accessed at Environment > Servers > [Name of Managed Server or Admin Server] > Logging.

Here, you can define following configurations

  • Log file path
  • Rotation Policy

However, in the advanced section, you can define:

  • Log entry layout
  • Logging Level
  • Specify package level logging in “Logger Severity Properties” box:
    com.adobe.mypackage=Debug

Note that on Weblogic, if you are running into issues while deploying EARs, you may want to look into Domain logs and Adminserver logs. Both of these are created under <Weblogic Domain>/servers/<Admin Server>/logs.


Websphere

Websphere logs can be found at <Websphere Home>/AppServer/profiles/<Profile Name>/logs/<server name>. You can configure it from Websphere administration console at Websphere Application Servers > [name of server] > Logging and Tracing.

In JVM Logs, you can configure SystemOut and SystemErr logs for your server.

Here, you can configure:

  • Location of Log file
  • Rotation Policy

From Logging and Tracing, with few simple steps, you can enable the trace level logging for a specific package:

  1. Select “Change Log Detail Levels” from General Properties section.
  2. Under “Change Log Detail Levels” page, you can find a text box and tree beneath it with root node as “* [All Components] “.
  3. Expand Root node “* [All Components] > com.adobe.livecycle.*” and click “com.adobe.mypackage.*”.
  4. This will open a context menu. Go to Message and Trace Levels and choose finest from sub menu.
  5. Click Apply button and Save the settings to master configuration. Now you should be back to “Logging and tracing”.
  6. Select Diagnostic Trace link. This will open Diagnostic Trace Service page.
  7. Make sure File radio button is selected. Increase the Maximum File Size to 50 MB, and Maximum Number of Historical Files to 5.
  8. File Name text box shows “${SERVER_LOG_ROOT}/trace.log” by default. This means trace logs are getting created at default logs folder. You can change it by giving any absolute path where you want diagnostic logs to be written.
  9. Click Apply and Save the settings to master configuration.
  10. Restart the server. File specified at step 8 should get created.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 6.6/10 (7 votes cast)

LiveCycle PDF Generator – HTML to PDF

- Saurabh Kumar Singh, Computer Scientist at Adobe

 

LiveCycle PDF Generator supports HTML to PDF conversions. HTML document can be provided in any of following forms:

  • Submit an html file to be converted to PDF.
  • Provide http(s) URL of the html to be converted to PDF.
  • Submit a ZIP file containing an entire website (zip should contain index.html at the top level) for creating PDF.

While submitting an input HTML file, the user can provide a variety of options like:

  • The level to which spidering will be performed
  • Whether to get the entire site or not
  • Stay on same path (in terms of URL), while fetching the HTML document(s)
  • Stay on same server. It is useful when you have specified spidering level of more than 1 and at the same time does not want to create PDF from html documents linked on input html if it’s on a different server.
  • PDF page size and margin options
  • Add bookmarks
  • Enable tagging
  • Set initial views settings: It contains option like which page to open on PDF open

LiveCycle ES2 PDF Generator and later provides the facility to specify Adobe Acrobat Professional as the fallback to create PDF files. A downside to this fallback is that Acrobat based conversion is single-threaded, whereas LiveCycle PDFG based conversions are multi-threaded. Also, Acrobat Professional does not honor the options mentioned above.  This facility is only available on Windows. LiveCycle Administrator can also configure the Generate PDF Service to always prefer the Acrobat route. To do this navigate to Home > Services > Applications and Services > Service Management > Configure GeneratePDFService and set the “Use Acrobat WebCapture (Windows Only)” option to True.

What’s New in ES3

The HTML to PDF engine creates high fidelity PDF documents. Time taken to create the best quality PDF document may seem longer to some users. For some user a low quality PDF is acceptable, if the conversion time is faster.

In LiveCycle ES3 a new conversion engine is introduced to achieve this and get a quick turnaround time for conversions. This engine is supported on all the supported platforms of LiveCycle. Moreover this engine honors all the conversion options mentioned above. There is a bonus option of specifying header and footer text to be put in the generated PDF document. This engine acts as fallback for high quality HTML to PDF engine on UNIX machines. In order to set this new engine as the preferred route, navigate to Home > Services > Applications and Services > Service Management > Configure GeneratePDFService and set “Use ICEBrowser based Html to PDF” option to True.

 

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

LiveCycle forums have gone thinner!

Adobe LiveCycle forum is a platform where LiveCycle community meets, learns, and discusses experiences about using LiveCycle. We are committed to provide the best user experience to the community when they are on the forum, and we have taken a step in that direction.

The LiveCycle forum, until sometime ago, comprised of 70 forums and sub-forums. We monitored the forums and found that the unnecessary bulk is making it difficult for the community to manage discussions and participate on the forum. As a result, most of the are inactive as it was unintuitive to drill-down to the correct forum for discussions.

As we understand the importance of a close-knit community, we have optimized the forum structure, so that it is easier for the community to search, post, and participate on the forum. The new forum structure is thin, focused, searchable, and easy to manage.

In its new look, the LiveCycle forum has relatively flat hierarchy, but with a logical grouping of discussions. The streamlined new structure includes seven top-level forums, including one forum with 14 sub-forums. The flat hierarchy relies on the tags for filtering discussions related to a specific area of LiveCycle.

The following table lists the top-level forums with their description.

Forum

Description

LiveCycle modules and development tools A top-level forum with 14 sub-forums for each LiveCycle module and development tool.
LiveCycle installation, configuration, deployment, and administration A forum for discussing issues related to LiveCycle installation, configuration, and administration. Also, you can discuss issues related to application servers and databases while installing or deploying LiveCycle.
LiveCycle Collaboration Services A dedicated forum for discussing LCCS.
Related products – Managed Services, Central Output Server, Production Print etc. In this forum, you can discuss product that do not form the core of LiveCycle, but are related to the LiveCycle technology.
General discussions – features, feedback, training, documentation etc. This forum is suitable for general discussions about LiveCycle features, learning, and documentation. Also, you can share any tips and tricks, learning experiences, and submit feature requests in this forums.
LiveCycle pre-ES (6.x and 7.x) discussions For everything related to pre-ES versions of LiveCycle.
Deprecated modules – Content Services, Mosaic, PDFG 3D, Guides etc. This is just the right place to talk about deprecated LiveCycle modules.

 

As we see it as a striking shift in how you currently interact on the LiveCycle forum, please take a note of the following things:

  • If you have bookmarked or following any LiveCycle forum, we recommend that you visit the corresponding forum in the new structure and configure it again as the URL for the forum might have changed.
  • The discussion threads are sorted by the last modified date; however, in some cases, the threads prior to streamlining might not appear in the desired sequence. It’s a known technical issue and we are trying to restore the sorting.
  • There is no impact on the URLs of individual discussions and you will continue to receive notifications for any updates to the discussions posted by you.

We hope that the streamlined forum will enhance and add value to your interactions with the community. Please visit the forum at http://forums.adobe.com/community/livecycle and let us know your valuable feedback as comments on this blog. We will continue to make improvements to the forum to give the community the engaging and best-in-class user experience.

Thanks for being such a wonderful community of experts!

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

Adobe Digital Enterprise Platform | Documentation Updates | October, 2011

This October carries festivities galore, the onset of winter, and, not to forget, a fresh set of important documentation updates for Adobe Digital Enterprise Platform. Here’s a summary of all the updates that are now live and accessible on the ADEP Documentation Home Page.

  • Upgrading to Document Services: The upgrade documents had significant updates, particularly concerning topics related to Business Activity Monitoring. As the cookie crumbles, ADEP Document Services is the last release to support Business Activity Monitoring and, hence, the BAM server cannot be upgraded, but it can certainly be reused to work with the new Document Server. See the Upgrade to Document Services documentation.
  • Connector for SharePoint: All sites on the SharePoint server are available for configuration for all Document Services features by default. A new feature for the Connector for SharePoint allows you to restrict configuration and usage of Document Services features on a specified SharePoint site. The Configure ADEP Document Services – Connector for SharePoint tells you how you could do this.
  • Plug-in for Hyperic HQ: Hyperic HQ allows you to monitor and manage your web infrastructure, server, services, and devices of ADEP Document Server. See Using the plug-in for Hyperic HQ, a new document, to know more about Hyperic HQ, its installation and usage procedures.
  • Action Script Reference was refreshed with addition of new Packages and APIs for Customer Experience Solutions (Correspondence Management and Integrated Content Review in particular).
  • Correspondence Management Developer’s guide had significant updates. The guide now has download locations of all jar files’ required to set up your development environment for the Correspondence Management solution.
  • Disaster recovery for Correspondence Management explains how to back up and restore your Correspondence Management data.

Until the next time we have more updates, Adios!

-

ADEP Community Help and Learning Team

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

Use logging with your Composite Application Framework app

Adobe forums served up some nice information about logging runtime messages for your Composite Application Framework (aka Mosaic) apps. The Client Component Framework (codename: Gravity) provides the logging libraries….Composite Application Framework runs on Client Component Framework….here’s how to get those logger juices flowing:

<quote>

Yes, Gravity logging APIs can be used in Mosaic as-is. To view the log output:

1.       Open CRXDE lite in a browser and log in
2.       Navigate to /libs/mosaic/components/index/index.jsp
3.       Locate the line in the file that initializes the flashvars variable. In 10.0 this should be on line 65
4.       After that line, add a new line:

flashvars.mdebug = true;

5.       Click the “Save All” button to save the changes

Then, when a new application is launched, a debug window will appear with a “Log Viewer” tab. Note that the debug window will appear in the upper left corner of the browser in a layer that will be behind html or pdf content, so if your application’s layout has html or pdf content in the upper left region you may not be able to see the debug window.

</quote>

What was the OP’s result you may ask?

“That debug window certainly is useful. It has much more useful information than I was expecting. The DOM Viewer is especially nice. It is good to be able to confirm which libraries get loaded.”

 

This is the forum post:  http://forums.adobe.com/message/3973532#3973532

Here are the Composite Application Framework docs: http://help.adobe.com/en_US/enterpriseplatform/10.0/AEPDeveloperGuide/WS6e4bbd81fea965ef18585f3012fda7a1d5e-8000.html

Here are the Client Component Framework docs: http://help.adobe.com/en_US/enterpriseplatform/10.0/AEPDeveloperGuide/WS3ad6fd7a5b41dea4-28996cf812f6f54ab88-8000.html

Client Component Framework ActionScript reference: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/index.html?filter_livecyclees=10.0&filter_flashplayer=10.2&filter_air=2.6#top — see the com.adobe.gravity.* packages.

Scott

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

ADEP Data Services quick starts and bundling articles

Here are some great new blog posts from our good friends in the Adobe Support group:

How to Create a Data Services application for the Experience Server that returns data – Sound familiar? This is a remix of this walkthrough in the ADEP help. Lin’s version is friendlier to CRX and Maven novices.

How to create class/jar files for data service project without using maven – Not ravin’ about Maven? This is for  you!

ADEP Data Services Complete Quick Start – Boils down much of the product help content to include only procedures. If you just want to do, and knowing why is not the immediate priority, this is perfect for you.

Scott (Brodersen)

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