Author Archive: Suhas

Adobe Digital Enterprise Platform | Documentation Updates | October, 2011

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

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

Writing pre- and post-stage hooks for Integrated Content Review solution

The Review, Commenting, and Approval building block, part of the Integrated Content Review solution, allows you to inject said functionality or custom Document Services processes at any point in your solutions workflow. You can add functionality or custom processes prior to or after staging, called Pre-stage and Post-stage hooks respectively. See Writing Pre- and Post-Stage Hooks for more information and a quickstart to help you get started.

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: 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)