Description:
Description:
============
If you install TIBCO ActiveMatrix BPM with an external LDAP directory server, you may experience issues connected with the demonstration LDAP resource "easyAs". The TCT installation still installs the LDAP Connection and Authentication Shared Resources for the easyAs resources, using the URL of the external LDAP that you have specified.

Environment:
==========
TIBCO ActiveMatrix BPM versions 1.3.x or 2.x on any supported platform.

Symptoms:
=========
As your LDAP directories will not contain any entries for the "easyAs" LDAP, these connections will fail. This can prevent access to the LDAP Container configuration - the LDAP Container option within Openspace or Workspace does not respond, or responds with an error message.

Cause:
=====
LDAP Directories do not contain any entries for the "easyAs" LDAP.

Resolution:
=========
There are two solutions available:
• Modify the configuration of the LDAP Connection Shared Resource
   Template ldap/de/easyAs to make it refer to a valid LDAP URL and Base
   DN. You can do this by copying the connection properties used for
   ldap/de/system. This will then be replicated to each BPM Node, and avoid
   the need to modify those node configurations. The Shared Resource
   Instance will have to be re-deployed after saving the modifications; and
   this often requires a Node restart in order to refresh the pooled LDAP
   Connections.
• Delete the LDAP Connection Shared Resource Instance ldap/de/easyAs.
   Only the Shared Resource Instance should be deleted. Deleting the Shared
   Resource Template or the associated Authentication Application
   amx.bpm.auth.easyAs in a multi-node environment will prevent the creation
   of replicated BPM nodes. This option requires that the Shared Resource
   Instance is deleted from every replicated BPM Node, as and when nodes
   are created.
Symptoms:

Cause:

This advises users how to resolve issues with easyAs LDAP resources after installing TIBCO ActiveMatrix BPM with an external LDAP.