- 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.
- Ankush Kumar, Lead Software Engineer @ Adobe
- Go to Websphere console -> Servers -> Application servers -> server1 -> Process Definition -> Java Virtual Machine.
- Enable the checkbox against Debug Mode.
- Fill in the following as debug arguments in the text box:
Djava.compiler=NONE -Xdebug -Xnoagent
- Go to Home >Summary of Servers >DocServer Server Start tab.
- Edit arguments and add:
- For JRockit R28 and above -XX:
- For others:
Add following in run.conf (for Non-Windows) and run.conf.bat/run.bat (for Windows):
- Non-Windows: JAVA_OPTS=-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n $JAVA_OPTS
- Windows: set JAVA_OPTS=”-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n %JAVA_OPTS%”
Taking Thread Dump
If the server is started through a console/command line and not as a service, press a ctrl+z. The thread dump would be logged in the console window/console logs.
If the server is running as a service, do the following:
You can use a utility SendSignal. Follow the docs at this URL.
Identify the process id and then fire command
kill -3 <pid>
Got to <jboss_home>\bin and execute following command:
twiddle.bat invoke “jboss.system:type=ServerInfo” listThreadDump > threaddump.html
For Weblogic 10 R3 you can use following way. Go to Weblogic Console -> Environment -> Servers On left side. Then select <your server> -> Monitoring tab -> Threads -> Dump Thread Stacks.
It will display the thread info.
- Login to the machine where the WebSphere server is running.
- Open a command prompt and change directory to /WebSphere/AppServer/bin.
- Type wsadmin (will take a minute to connect – if authentication is enabled, it will prompt).
- Enter set jvm [$AdminControl completeObjectName,process=server1,*].
- Replace server1 with the actual server you want to take a thread dump from (has to be local to this machine).
- Enter $AdminControl invoke $jvm dumpThreads.
The thread dump is created in the profile folder for the server you created a dump for. There should be a “javacore.someText.txt” file created. If it’s a cluster, you’ll have to repeat the above steps for each server.
Using JConsole. Connect the JConsole present in IBM JDK and trigger threaddump using that. You would have to follow the steps mentioned here for it to get to work.
Capturing SQL Logs
The SQL queries by UM can be logged using the default logging system for that system. Following two categories should be used:
- com.adobe.idp.storeprovider.jdbc – Logs all the queries fired with the value populated.
- storeprovider.stacktrace – This would also log the stacktrace of the thread which fired the query.
The logging level should be set to TRACE or the lowest for the queries to be logged. For the POF layer use the category com.adobe.pof.adapter for seeing the queries getting fired.
- Mayank Gupta, Computer Scientist @ Adobe
Steps to add a custom service in Correspondence Management solution are as follows:
- The implementation for this user story involves code changes and rebuilt. So, one is required to setup the development environment via steps mentioned @ Setting up development environment.
- Add your sample custom service interface and implementation class in the CorrespondenceManagementSolutionTemplate/Services project for example @ com.adobe.icc package in the source code. See the sample @ http://blogs.adobe.com/LiveCycleHelp/files/2012/06/SampleCustomService1.zip.
- Now define your service as a spring bean. For this, add the following entry in your CorrespondenceManagementSolutionTemplate\Services\resources\META-INF\spring\cm\adobe-cm-spring-config.xml file:
<bean id=”sampleCustomService” class=”com.adobe.icc.SampleCustomServiceImpl” />
- Now expose your spring bean as a osgi-service. For this, add the following entry in your CorrespondenceManagementSolutionTemplate\Services\resources\META-INF\spring\osgi-context.xml file:
<bp:service interface=”com.adobe.icc.SampleCustomService” ref=”sampleCustomService” >
<bp:service-properties><entry key=”connectors.httpinvoker” value=”true” />
<entry key=”connectors.httpinvoker.alias” value=”/sampleCustomService” />
<entry key=”connectors.remoting” value=”true” />
<entry key=”connectors.remoting.id” value=”sampleCustomService” />
- Rebuild and redeploy the Solution template to view the changes. For information on rebuilding and redeploying, see Building and deploying the Solution Template.
- Saurabh Kumar Singh, Computer Scientist at Adobe
Following are a few tips and workarounds for LiveCycle PDFG. Please note that the workaround marked as unsupported are not officially supported by Adobe.
- [Unsupported] On UNIX servers customers can use 64-bit OpenOffice to do OpenOffice based conversions. The obvious benefit from this is the performance improvement we get. To achieve this just point JAVA_HOME_32 to 64 bit version of Java. Same can achieved on widows too but you may observe immediate conversion failures for other native file formats.
- [Unsupported] Any file which can be opened by Acrobat (like a text file) can be converted to PDF using LiveCycle PDF Generator. You just need to add the comma separated file extension (for example txt for text files) in XPS to PDF file-type setting.
- A user/administrator can directly jump to PDF Generator UI by hitting http(s)://<server-name>:<port>/pdfgui. This way a user can skip couple of clicks on UI to land on PDF Generator user interface.
Watch this space, for a lot more upcoming tips and tricks.
- 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:
- 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.
- 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.
- 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.
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.
|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!
This blog post is part of the series on customizing the Adobe Integrated Content Review solution.
Any entity of the Integrated Content Review solution like, a campaign, a project, or an asset, includes many participants or team members. The participants at any level in the campaign hierarchy include participants from lower levels. In other words, a campaign includes all the participants of a project. A project, in turn, includes all the participants of the assets within it. Additionally, at any level in the campaign, a participant can be added directly to the team list.
To view/add team members at any level in a campaign, click an entity in the Gantt chart and then click the Resources tab. A newly added team member may not have an avatar image. An instance is shown below:
Newly added user does not have an avatar
Understanding the naming convention of the image files
The images display only if the image files are named using the canonicalname_domainname convention. To know the value of domain name and canonical name, follow these steps:
- Navigate to http://localhost:4502/crx/index.jsp.
- Log in using the credentials of the user whose domain name and canonical name is to be determinded.
- The UserID is displayed of the format lcu::domainname::canonicalname. Note the domain and canonical names from the string.
For example, for an administrator the name is displayed as lcu::DefaultDom::SuperAdmin. Hence, the domain name is DefaultDom and canonical name is SuperAdmin.
Adding an image
Let us add an image for a newly-added user named Shashank Kapoor.
- Navigate to ICR_SOURCE/integratedcontentreview/package_data/content/icr/assets/user-images.
Note: ICR_SOURCE folder is the folder where you extract the provided source code of the solution interface. Refer to this help page to read more.
- Add an image with the file name shakapoo_DefaultDom.jpg.
Note: To update an existing image, replace the image file with a new image file. The image file is scaled to 45 x 58 pixels in size. The image filenames are case sensitive.
- Create a directory named shakapoo_DefaultDom.jpg.dir.
- In this directory create a file named .content.xml. Add the following code to it:
<?xml version=”1.0″ encoding=”UTF-8″ ?>
<jcr:root xmlns:jcr=”http://www.jcp.org/jcr/1.0″ xmlns:nt=”http://www.jcp.org/jcr/nt/1.0″ jcr:primaryType=”nt:file”>
<jcr:content jcr:primaryType=”nt:unstructured” />
- Save and deploy the customized solution interface. To know more, refer to this article.
After updating the image for the above instance it shows in the solution interface as shown below:
User with an avatar image added
Read more about adding team members here, in the ICR solution guide.
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