Tag Archives: configuration

Configuring LiveCycle JDBC Data Sources in WebLogic for DB Failover

– Jayan Kandathil

For IBM WebSphere, see here.

LiveCycle ES2′s Configuration Manager (LCM) provides you two options for configuring JDBC data sources in WebLogic:

1) Package it inside the EAR files (more secure)
2) Create it in the WebLogic Admin Console

Choice #2 provides a lot more flexibility when it comes to configuring the data sources for database failover. Runtime configuration changes such as increasing the pool size can be done without having to un-deploy and re-deploy EAR files.

To ensure that the connections in the connection pool are valid, the following additional configuration changes are necessary. This is based on an actual customer deployment against an active-passive SQL Server database cluster. You can make changes as necessary to fit your IT environment.

1) In the ‘Connection Pool‘ tab for the JDBC data source, in the ‘Advanced‘ section, ensure that the checkbox for ‘Test Connections on Reserve‘ is checked

2) Set ‘Test Frequency‘ to 10 seconds

3) Set ‘Test Table Name‘ to “DUAL” or “EDCJOBENTITY”

4) Set ‘Seconds to Trust an Idle Pool Connection‘ to 5 seconds


6) Set ‘Connection Creation Retry Frequency‘ to 12 seconds

7) Set ‘Login Delay‘ to 0 seconds

8) Set ‘Inactive Connection Timeout‘ to 0 seconds

9) Set ‘Connection Reserve Timeout‘ to 10 seconds

Original article at http://blogs.adobe.com/livecycle/2011/04/configuring-livecycle-jdbc-data-sources-in-weblogic-for-db-failover.html.

Understanding the LiveCycle GDS – and freeing up disk space

LiveCycle, as an piece of Enterprise software, tends to assume that you may want to keep a quantity of data around for posterity. Long-lived processes can cause a lot of disk space bloat, and whilst this is fine for those who wish to archive lots, this may not be ideal when running a lower-spec server.
In this article, I will point out the main areas where data and disk space use can happen, and how to clean up.

Read the complete post here.

Things to Know Before Installing ADEP Experience and Document Services

I’ve recorded two webinars (Adobe Connect sessions) for people who are about to install ADEP Experience and Document Services. The first one discusses some high-level topics like supported platforms, development tools etc. while the second provides screen-by-screen details of a complete install effort on Windows, including the installation of Flash Builder 4.5, its integration with an ADEP Experience Server, and the integration of the Experience Server with the Document Server.

Since these are Adobe Connect sessions, your browser should have Adobe Flash Player installed.

1) Install – Introduction (15 minutes)
2) Install – Detailed Steps (31 minutes)

Additional Resources are available:

– Introductory video on ADEP by Steve Forrest (9 minutes)

– YouTube video by Gary Gilchrist, explaining how to integrate ADEP Experience Server with ADEP Document Server (12 minutes)

Original article at http://blogs.adobe.com/ADEP/2011/08/things-to-know-before-installing-adep-experience-and-document-services.html.

Upgrade to LiveCycle ES2!! My fav bits

I was recently reading about upgrade to ES2 and new features of ES2 and these are my favorite bits. I’ll play with ES2 after the GM release and post the experiance later.. But so far this is what I’m really looking forward in ES2.

  • Simplify testing and deployment by previewing your business process, including testing form and Flex® user interfaces, and recording the process results.

The testing is on the top of my wish list. I even thought of writting a whole new AIR application to make our life easier around workflow testing and deployment. I’m talking about deployment on several staging environment!! But for now let’s forget about my AIR app development… Thanks ES2 for looking into this.

  • Reference real-time graphical server health statistics within the LiveCycle administration UI.

Love this…eliminates the need for a monitoring software for small projects.. Will it also have customisable alerts too?

  • Upgrade available from ES update 1, LC 7 and LC 6.

This is a big sale point to encourage clients on LC7 deployments. I wish the ‘compatibility layer’ usage can be kept to minimal usage as part of the upgrade.

  • Enhancements to Form Guide development cycle.

This is BIG improvement… It’s something you just need to play with.

Original article at http://blog.pandyaparth.com/2009/11/upgrade-to-livecycle-es2-my-fav-bits/.

Determining if the LiveCycle Scheduler has Started in Cluster Mode

LiveCycle product blog has recently published a nice article that allows you to check if the LiveCycle scheduler has started properly in cluster mode or not.

Thanks LiveCycle team for publishing the details.
The blog entry can be found at – http://blogs.adobe.com/livecycle/2011/02/schedulerclustermode.html

Original article at http://blog.pandyaparth.com/2011/02/determining-if-the-livecycle-scheduler-has-started-in-cluster-mode/.

Configuring IIS 7.5 to Load-Balance a LiveCycle Cluster

– Jayan Kandathil

To configure Apache Web Server, see here.

Microsoft Windows Server 2008 R2 comes with IIS 7.5

IIS 7.0 comes with Windows Server 2008. Microsoft re-architected IIS in version 7.0 to be more modular like Apache Web Server. Metabase was removed.

As a result, configuring IIS 7.5 to load-balance a LiveCycle cluster (whether it is WebSphere, WebLogic or JBoss) is now simple and straightforward. You don’t need to make any changes on the J2EE app servers.

The following instructions assume that the IIS 7.5 instance is dedicated. For a shared IIS instance/farm, you will have to modify some of these instructions. Also, Microsoft’s AppCmd can be used to script all of these. AppCmd is a command line utility to manage IIS via commands and scripts. It is different from PowerShell.

For handling complex environments, the URL Rewrite module will be very useful.

1) Add the role “Web Server (IIS)” on Windows Server 2008 R2

– Use the menu Administrative Tools->Server Manager

– Choose Roles (there are about 17 roles defined in Windows Server 2008 R2 standard edition)

– Add Roles, then Web Server(IIS)

– Make sure “Directory Browsing” is unchecked (it is checked by default)

– Check “HTTP Redirection”

– Click Install

– Re-start the server

2) Install Application Request Routing (ARR)

You can download it here. Once downloaded, run ARRv2_setup_amd64_en-us.exe Once finished, check the install log in %USER_TEMP% and make sure that all of the components installed fine. You don’t want to see the following:

rewrite_amd64_en-us.msi Failed Status Code 1603
webfarm_amd64_en-us.msi Failed Status Code 1603
requestrouter_amd64_en-us.msi Failed Status Code 1603
ExternalDiskCache_amd64_en-us.msi Failed Status Code 1603

3) Using IIS Manager, create a new “Server Farm”

Start Internet Information Services (IIS) Manager. If the installation of Application Request Routing is successful, you should see a new node in the left pane under “Sites” called “Server Farms”.

– Create a new “Server Farm”

– Name it with something meaningful like LC_TEST_CLUSTER

– One by one, add all of the members of your LiveCycle cluster. For each, make sure that you click the ‘Advanced Settings” and provide the completely qualified DNS name (eg: server1.company.com), HTTP port (eg: 8001 for WebLogic) and HTTPS port (eg: 8002) of each of the cluster members.

– Save the “Server Farm” definition. Say “Yes” to the creation of an InBound URLRewrite Rule.

4) Configure the new “Server Farm”

– Click on the new Server Farm. On the right pane, dbl-click ‘Caching’. Make sure that for ‘Query String Support’, “Include Query String” is chosen.

– On the right pane, dbl-click ‘Load Balance’. For ‘Load Balance Algorithm’, you can choose “Weighter Round Robin” or another that makes sense to your environment (test). For ‘Load Distribution’, you can choose “Even Distribution”. If the cluster members are not all alike in their capabilities, you can choose “Custom Distribution” and assign a higher weight to a more capable cluster member so that more requests get routed to it.

– On the right pane, dbl-click ‘Routing Rules’. Make sure that the checkbox for “Use URL Rewrite to inspect incoming requests” is checked. If it is not, check it and click ‘Apply’ on the top right to save.

– On the right pane, dbl-click ‘Server Affinity’. Make sure that the checkbox for “Client Affinity” is checked.

5) Test

– Exercise your application from multiple client machines (with different IP addresses)

– Verify in IIS Manager. Click on the Server Farm. On the right pane, dbl-click ‘Monitoring and Management’. Check under the column ‘Total Requests’ and make sure that all members of the cluster received requests.

Original article at http://blogs.adobe.com/livecycle/2011/03/configuring-iis-7-5-to-load-balance-a-livecycle-cluster.html.

Migrating an Application from Adobe® LiveCycle® ES to ES2

Are you migrating existing LiveCycle applications to LiveCycle ES2?
Check out the recent  captivate recording I put together:
  • Importing an 8.x LCA and verifying functionality
  • Making minor edits to resources and pushing them back to the legacy repository
  • Full upgrade/migration of the application to ES2 application model, taking advantage of the new tooling

Full documentation for migration of applications can be found here:


Original article at http://livecycleapps.wordpress.com/2010/05/12/migrating-an-application-from-adobe%C2%AE-livecycle%C2%AE-es-to-es2/.

Determining the SOAP Port for your IBM WebSphere application server

Suhas Yogin

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 "..scriptsjaclconfig.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration service is not available.

For more information on IBM WebSphere, click here.

Original article at http://blogs.adobe.com/livecycledocs/2010/11/determining-soap-port-websphere.html.