Tag Archives: installation

Installing and Configuring LiveCycle ES3 Connector for Microsoft SharePoint 2010 for JBoss, MySQL, Windows

- Pankaj Gakhar, Software Engineer @ Adobe

The LiveCycle ES3 connector for Microsoft SharePoint 2010 contains two parts:-

  1. Document Services Component (DSC) which is installed on LiveCycle Server.
  2. Web Part that is installed on the SharePoint Server.

Installing Adobe LiveCycle ES3 Connector for Microsoft SharePoint DSC (Fresh Installation)

Install the LiveCycle ES3 server on your machine and follow the below steps to configure the SharePoint Connector:-

1. Move to the LiveCycle server installation directory and start the LiveCycle Configuration Manager (LCM). LCM is available at <LIVECYCLE_INSTALL_DIR>/configurationManager/bin/ConfigurationManager.exe or .bat.

2. If you are adding SharePoint to an existing LiveCycle ES3 Installation, please go to section Adding SharePoint Connector to an existing LiveCycle ES3 installation. If this is a fresh installation then, choose express mode of installation and on the Modulesscreen select the components that you want to install along with LiveCycle ES3 Connector for Microsoft SharePoint.


Read the complete post at Adobe LiveCycle Blog.

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.

Original article at http://blogs.adobe.com/ADEPhelp/2011/09/installing-windows-service-for-adep-experience-server.html.

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.

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.

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.

Content Services: WebSphere stops responding when many concurrent threads are running

– Samartha Vashishtha 

When the storeContent operation for Content Services 9 is invoked with more than 30 threads, the WebSphere application server may stop responding.

Follow these steps to resolve the issue:

  1. In WebSphere Administrative Console, click Servers > Server Types > WebSphere application servers and then click a server name.
  2. In the right pane, click Thread pools under Additional Properties.
  3. Click WebContainer and, on the Configuration page, increase the value of the Maximum Size field by double the number of threads that you need to run. For example, increase the value of the Maximum Size field by 80 if you want to run 40 threads.
  4. Click Apply or OK.
  5. Click Save directly to the master configuration.
  6. Restart the WebSphere application server.

Original article at http://blogs.adobe.com/livecycledocs/2011/02/content-services-websphere-stops-responding-when-many-concurrent-threads-are-running.html.

Setting up JBoss to auto reconnect after database outage

– Darren Melanson

If you had a database outage or failure while JBoss was up, you’re likely in a situation where you would have to restart JBoss because the database connections didn’t get reconnected for you. You’re likely also faced with a massive set of log files due to the data source complaining about it not being able to connect to the database.

If you want JBoss to automatically reconnect the data source pool(s) for you, here’s some settings to use (only valid if using a “local-tx-datasource”):

1) <autoReconnect>true</autoReconnect>
2) <check-valid-connection-sql>an efficient select statement</check-valid-connection-sql>
3) <failOverReadOnly>false</failOverReadOnly>
4) <maxReconnects>50</maxReconnects>
5) <initialTimeout>15</initialTimeout>

In the above settings, if the data source connectivity is lost (database down or network failure) – then JBoss will automatically attempt to reconnect 50 times every 15 seconds. You can obviously set those numbers to values suitable to your environment. It’s also important to set the failOverReadOnly flag to false as it ensures that recovered connections are writable.

Additionally, some people prefer to include a valid and efficient SQL statement in the “check-valid-connection”, it’s completely optional but a good practice in environments where stale connections are common. Optionally, there’s also “new-connection-sql” which will check on newly created connections.

Original article at http://blogs.adobe.com/livecycle/2011/03/setting-up-jboss-to-auto-reconnect-after-database-outage.html.