Posts in Category "Install and Configuration"

Debugging LiveCycle – Working with logs (Part 2)

- Ankush Kumar, Lead Software Engineer @ Adobe

In Debugging LiveCycle – Working with logs (part 1), we covered how to handle logs at application server level. In this blog, we will cover a few areas where we can fine tune the logging in applications itself.

 LCM Logs

As you might have noticed LCM logs are found at <LiveCycle Installation Location>/configurationManager/log. Default logging level of this is INFO. This is governed by properties file kept inside adobe-lcm.jar: \com\adobe\livecycle\lcm\logging\log.properties.

Using this property file, you can:

  • Change Logging Level
  • Define file location and file name.
  • Define rotation policy

If you want to overwrite the default location of this file to a more convenient location, you can do so by modifying <LiveCycle Installation Location>/configurationManager/bin/ConfigurationManager.bat and specifying following system property:

-Djava.util.logging.config.file=<path to file>

 Generating ORB Trace

While working with natives like XMLForms, you can sometimes run into issues where an application abnormally terminates. Following parameters help in generating extra trace information for debugging such issues.

These are required to be placed as argument to the native application:

-ORBtraceLevel 25 -ORBtraceThreadId 1 -ORBtraceInvocations 1 -ORBtraceInvocationReturns 1 -ORBtraceTime 1 –ORBtraceFile <Path to log file>

Also, when we are debugging an issue related to native applications, in System Out logs we can find system natives being invoked and a large IOR is passed to them as input. This IOR can be analyzed by many easily available IOR parsers. (Just Google for them). This can be first step towards debugging natives related problem.

Variable Logging

In order to better understand and debug an orchestration, LiveCycle offers excellent process debug feature. Using workbench, one can easily trace every step of a process and find what exact values any variable hold. For more information, one can refer this blog.

http://blogs.adobe.com/shwetank/2011/11/21/process-recording-feature-of-livecycle-workbench/

But sometimes this gets difficult due to environment constraints and performance overheads. One may want to introduce a step which will log current state of all variables in either System Out log or the log of your choice.

This can be accomplished using Variable Logger service. One can introduce this while designing the orchestration. Now each time the orchestration runs, the values of variables will be logged as the step is executed.

Other Application Logging Locations

Content Services and CMSA Logs

Content Services and CMSA logs are created in working directory of the application server.

LiveCycle Installer Logs

Installer logs can be found in following two locations

  • <LiveCycle Installation Home>
  • <LiveCycle Installation Home>/logs

Service Pack Logs

Service pack logs can be found at <LiveCycle Installation Home>/patch/<Patch Name>/log

CRX and Correspondence Management Logs

From ES3 onwards, you will find CRX and CM logs at <CRX Repository Directory>/logs. (More on this will be covered in next part of blogs)

PDFG Configuration Logs

  • PDFG System Readiness Testing Logs:  <LiveCycle Installation Home>/pdfg_srt/reports
  • PDFG Config Logs: <LiveCycle Installation Home>/logs
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)

Troubleshooting Common LiveCycle Configuration Errors

- Shishir Pandey, Software Engineer @ Adobe

The following lists the common configuration errors, why they occur, and steps to troubleshoot them.

  • Error: Component: com.adobe.xxx version: 10.0.3.20120511.1.316647 introduced a new service, it should not be patched
    Reason: This issue generally occurs when order of operation in Configuration Manager is incorrect after applying a patch. That is, the deployment of the component is performed before configuring and deploying of the EAR files. It usually occurs in command line execution because each step is run separately in this mode.
    Workaround: Re-run the Configuration Manager and ensure that configuration and deployment of ear is done before deploying components.
  • Error: In case of Weblogic, a “null” folder gets created after deploying EARs.
    Workaround: Stop the managed-server first, followed by the node manager, and finally stop the admin-server. Restart them in reverse order. You will see a folder Adobe gets created in the Weblogic domain.
  • Error: The following error occurred while executing this line: java.lang.OutOfMemoryError: Java heap space
    Reason:  This issue generally occurs if the XMX setting is missing from the server configuration.
    Workaround:  Increase the XMX value for the server or restart the server, and re-run Configuration Manager.
  • Error: weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on Resource AdobeService Operation: set , Target: EnableSSL at com.adobe.livecycle.bootstrap.bootstrappers.CoreBootstrapper.bootstrap(CoreBootstrapper.java:60)
    Reason:  This error generally occurs due to missing JMX policies in case of Weblogic during the Initialize LiveCycle step of the Configuration Manager.
    Workaround: Configure JMX as described in Creating JMX policies for database initialization. Restart the server and re-run the Initialize LiveCycle step.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.0/10 (4 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)

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)

Determining the SOAP Port for your IBM WebSphere application server

When configuring LiveCycle ES2 using LiveCycle Configuration Manager, you have to provide SOAP port of your WebSphere application server on some LiveCycle Configuration Manager screens. Follow the steps below to determine which port is used for SOAP connections with your WebSphere application server. The default port, however, is 8880.

To determine the SOAP port on WebSphere Base:

  1. In the navigation panel of the WebSphere Administrative Console, do the following:
    • (WebSphere 6.1) Click Servers > Applications Servers > [serverName] > Communications > Ports.
    • (WebSphere 7) Click Server Types > WebSphere application servers > [serverName] > Communications > Ports.

  2. Under Communications, click Ports. On the next screen, make a note of the port number for SOAP_CONNECTOR_ADDRESS.

To determine the SOAP port on WebSphere Deployment Manager:

  1. In the navigation panel of your WebSphere Administration Console, click System Administration > Deployment Manager.
  2. Under Additional Properties, click Ports. On the next screen, make a note of the port number for SOAP_CONNECTOR_ADDRESS. The WebSphere Administrative Console lists the SOAP Connector Address in two different sections. You must ensure you use the path provided in step 1 for WebSphere Deployment Manager. If you use the SOAP port listed at Servers > Application Servers > [serverName] > Communications > Ports, you will see the following error when running LiveCycle Configuration Manager:

com.adobe.livecycle.cdv.util.JaclResponseParser, parseString: WASX7017E: Exception received while running file "..\scripts\jacl\config.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration service is not available.

For more information on IBM WebSphere, click here.

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

LiveCycle ES2 Service Pack 1 available!

We recently released LiveCycle ES2 Service Pack 1 (SP1), a significant update to the LiveCycle server components, LiveCycle Workbench ES2, and LiveCycle Designer ES2. You can access the download page here. To download the service pack, you’ll need to log in using your Adobe ID and agree with the EULA.

The updated LiveCycle ES2 SP1 documentation is now live at the LiveCycle Developer Center. The SP1 ReadMe (PDF) describes how you can install the service pack for LiveCycle ES2 server, Workbench ES2, and Designer ES2. The ReadMe also lists the 80+ customer-reported issues that were addressed in this service pack.

To review the SP1 release notes for LiveCycle components, see this page. A related announcement on the LiveCycle Product Blog is here.

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

Updates to the install documentation

We updated the Installing and Deploying LiveCycle ES2 for JBoss (Single Server) guide recently to capture how to configure the JBoss Application Server to run as a service on Windows Server 2003 and 2008. While free tools to achieve this for 32-bit Windows/Java environments have existed for a while, you can now use the JBoss Web Native Connector for both 32-bit- and 64-bit environments.

We also updated the Prepare to Install/Upgrade LiveCycle ES2 documentation. The revised guides now explicitly mention support for JBoss Enterprise Application Platform (EAP) 4.3, besides JBoss 4.2.0 and 4.2.1.

You can download the latest PDFs from the LiveCycle Developer Center.

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