Author Archive: Vishal Gupta

Removing Sample Data and Users from Correspondence Management Solution

- Mayank Gupta, Computer Scientist at Adobe

 

Adobe LiveCycle Correspondence Management Solution provides some sample collateral and creates some sample users so that developers can start using the application and make use of these samples to know about and learn the product capabilities. It is highly recommended to remove these sample assets and sample users when the solution is deployed on to a production server.

Steps to remove sample assets and sample users:

  1. Removing sample assets by uninstalling them from package manager:
    • Go to http://[hostname:port]/lc/crx (on author instance)
    • Login as admin
    • Click Package Manager
    • Click on Package with name “cm-sampleassets.zip”
    • Click More dropdown in action bar (This action bar has other actions like Edit Build etc.,. , More option is in the right most area of this bar)
    • Click Uninstall
    • Click Uninstall again on confirmation dialog
    • Wait for sometime till you see a message like “Package uninstalled in <some>ms” in the Activity Log
    • Now if you log on to CM Manage Assets UI , you will not see any sample assets. If you are still seeing them then restart the server.
  2. Removing sample users from CRX user administration:
    • Go to http://[hostname:port]/lc/crx (on author instance)
    • Login as admin
    • Click User Administration.
    • Note: Correspondence Management creates Todd Goldman (tgoldman), Caleb Lopez (clopez), Gloria Rios (grios), Frank Kricfalusi (fkricfalusi), Jocelyn Robinson (jrobinson), and Heather Douglas (hdouglas) as the sample users.
    • In the user administration dialog , Navigate to each of these users and click Remove user. Now you cannot log in to the Manage Assets UI with any of the above usernames.

Follow the steps mentioned above in 2 and remove sample users from publish instance as well. There is no need to uninstall sample assets from publish instance as they are installed on author instance only.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 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)

Installing and working with the Windows service for the ADEP Experience Server

Although you can start your ADEP Experience Server by double-clicking the Quickstart JAR file or the Windows batch file, most people will find it convenient to install the Experience Server as a Windows service. It will configure the Experience Server to start automatically when your Windows restarts and, helps you control the start and stop operations of the Experience server by using the Services control panel.

Install Experience Server as a Windows service

To install a Windows service for your Experience Server:

  1. Open the command line interface and navigate to the [ExperienceServer root]/opt/helpers/ directory.
  2. Execute the instsrv.bat <serviceName> command to install the Experience Server as a Windows service.

Verify the installed Windows service

You can verify the installed Windows service in the Services control panel. To open the Services control panel,  execute the start services.msc command from the command line interface or select Start > Administrative Tools > Services.

Windows service operations

To start the Windows service, do one of the following:

  • In the Services control panel, select the Windows service and click Start.
  • In the command line interface, execute the net start <serviceName> command.

To stop or restart the Windows service for the Experience Server, click Stop or Restart, on the Services control panel.

Uninstall the Windows service

To uninstall the Windows service, execute the instsrv.bat -uninstall <serviceName> command on the command line interface. The Windows service gets removed from the Services control panel.

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