– 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.
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:
- Open the command line interface and navigate to the [ExperienceServer root]/opt/helpers/ directory.
- 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.
Beginning with LiveCycle ES2 Service Pack 2 (188.8.131.52), LiveCycle ES2 supports just-in-time provisioning of users that don’t yet exist in User Management. Just-in-time (JIT) provisioning creates new users dynamically in User Management once an authentication provider has successfully authenticated their credentials. Additionally, relevant roles and groups are assigned on-the-fly to the new user.
We have published a new TechNote that you can read to understand and implement this feature. This TechNote discusses the following:
- The need for JIT user provisioning
- How to implement JIT user provisioning
- JIT user provisioning: Behind the scenes
Here are a few new LiveCycle TechNotes that were published recently:
- This TechNote describes how you can synchronize Tivoli dynamic LDAP groups with User Management in LiveCycle ES or LiveCycle ES2.
- This TechNote may help if you’re encountering Process Management ES2 throughput issues for Oracle.
- When an XDP form with relative references to images is rendered as an interactive PDF form through LiveCycle, and passed to the Output service for flattening or to the Assembler service for conversion to a PDF/A document, you may not have all of the images in the generated output. This TechNote lists a couple of workarounds for the issue.
To search for more LiveCycle TechNotes or TechNotes for other Adobe products, use the Only Adobe content
option on the Search Community Help
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:
A LiveCycle ES Evaluation Virtual Appliance is now available for download. It is essentially a VMware ESX-based virtual machine containing the operating system (SUSE Linux Enterprise Server 10 64-bit SP2), a JDK (Sun HotSpot 1.5 64-bit), a J2EE application server (JBoss AS Community Edition 4.2), a database management system (MySQL Community Edition 5.0.26), and LiveCycle ES 8.2.1 SP1 evaluation version. You can learn more about the download here:
This is a great tool for developers and programmers to access a LiveCycle ES server without having to complete all the steps involved in a typical installation.
Let’s say you have configured LiveCycle ES with an enterprise domain that retrieves user information from an LDAP directory server. If you decide to move those users to another LDAP directory server, there are steps you should follow to retain the same user IDs and prevent users from losing tasks that are currently in their To Do lists in LiveCycle Workspace ES.