Chapter 9. WebSphere Connection Manager integration 303
9.1.1 Common configurations
Configuring Everyplace Connection Manager and WebSphere Everyplace
Access in a large enterprise can involve a large number of separate servers. A
typical configuration might include:
Everyplace Connection Manager servers
WebSphere Everyplace Access portal servers
WebSphere Everyplace Access synchronization
Corporate LDAP servers
Database servers
Domino servers
Application servers
Sametime servers
Intelligent notification servers
9.2 LDAP considerations
Both Everyplace Connection Manager and WebSphere Everyplace Access use
Lightweight Directory Access Protocol (LDAP) to store and retrieve user and
configuration information. In addition, the following options should be taken into
consideration when integrating these two products:
Everyplace Connection Manager and WebSphere Everyplace Access both
offer the choice of creating a local LDAP or using a remote LDAP.
Everyplace Connection Manager can also be configured in a split LDAP
configuration with configuration data and user data in separate LDAPs.
In general, the LDAP strategy is a complex approach. This book does not
discuss it in detail. However, some highlights are important to understand in a
WebSphere Everyplace Access and Everyplace Connection Manager
integration, and this chapter attempts to cover the most important issues in a few
common scenarios.
You can consider the configurations described in the following sections.
Note: Scalability and redundancy requirements can further add complexity to
the scenario.
304 IBM WebSphere Everyplace Access V5, Volume IV: Advanced Topics
Case 1: Using separate user directories
This is the non-integrated approach where Everyplace Connection Manager and
WebSphere Everyplace Access implement their own independent LDAP
directory. The scenario is illustrated in Figure 9-1.
Figure 9-1 Separate LDAP directories
This configuration where Everyplace Connection Manager and WebSphere
Everyplace Access use separate LDAP directory servers, gives you the benefit
that LDAP directories run on different machines, which gives to each product
independency, and better performance. However, it creates a user management
overhead since users must reside on both directories.
Note: This is the sample scenario described in Chapter 8, “Using Everyplace
Connection Manager HTTP Access Services” on page 273
WebSphere
Everyplace
Connection
Manager
LDAP
Directory
Configuration
Users
WebSphere
Everyplace
Access
LDAP
Directory
Configuration
Users
Chapter 9. WebSphere Connection Manager integration 305
Case 2: Sharing user directory
In this scenario, you configure Everyplace Connection Manager to access the
user entries residing in the WebSphere Everyplace Access LDAP directory
server. Only the user directory is shared and the Everyplace Connection
Manager configuration values still reside in its own LDAP directory. The scenario
is illustrated in Figure 9-2.
Figure 9-2 Sharing user LDAP directory
This scenario provides the following benefits:
Centralizes user management in a single directory
Deploys the WebSphere Everyplace Access LDAP directory behind the
firewalls providing better security for the user information.
Note: This is the approach that is included as a sample scenario in this
chapter in 9.3, “Sample scenario” on page 308.
WebSphere
Everyplace
Connection
Manager
LDAP
Directory
Configuration
only
WebSphere
Everyplace
Access
LDAP
Directory
Configuration
Users
U
s
e
r
s
306 IBM WebSphere Everyplace Access V5, Volume IV: Advanced Topics
Case 3: Sharing user directory and configuration
In this scenario, you configure Everyplace Connection Manager to access both
its configuration values and the user entries residing in the WebSphere
Everyplace Access LDAP directory. The scenario is illustrated in Figure 9-3.
Figure 9-3 Sharing LDAP for users and configuration
This scenario provides the following benefits:
Centralizes user management in a single directory.
Deploys the WebSphere Everyplace Access LDAP directory behind the
firewalls providing better security for both the Everyplace Connection
Manager configuration values and its user information.
The drawback in this scenario is that Everyplace Connection Manager has a
dependency on WebSphere Everyplace Access for configuration changes.
WebSphere
Everyplace
Connection
Manager
WebSphere
Everyplace
Access
LDAP
Directory
Configuration
Users
U
s
e
r
s
a
n
d
C
o
n
fi
g
u
r
a
t
i
o
n
Chapter 9. WebSphere Connection Manager integration 307
Case 4: LDAP Enterprise Directory
In this scenario, you configure both Everyplace Connection Manager and
WebSphere Everyplace Access to access a centralized LDAP Directory. The
scenario is illustrated in Figure 9-4.
Figure 9-4 LDAP Enterprise directory
This scenario provides the following benefits:
Centralizes user management in a single directory.
The enterprise LDAP directory resides behind the firewalls and therefore
provides better security for both the Everyplace Connection Manager and
WebSphere Everyplace Access configuration values and the user
information.
The drawback in this scenario is that both products have a dependency on the
enterprise LDAP directory for configuration changes.
WebSphere
Everyplace
Connection
Manager
WebSphere
Everyplace
Access
Enterprise
LDAP
Directory
WECM configuration
WEA configuration
Users
Get IBM WebSphere Everyplace Access V5 Handbook for Developers and Administrators Volume IV: Advanced Topics now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
