246 DCE Replacement Strategies
Security: Used to set up the global security configuration of the IBM
WebSphere Application Server. The security configuration comprises the
authentication mechanism configuration, settings for SSL, configuration of
access to the LDAP directory, and the CSIv2 protocol configuration. The
necessary steps are described in detail in “Configuring WebSphere
Application Server security” on page 212.
System Administration: Assigns user and groups to administrative roles, as
described in the
Administration interface
section of “Installing and configuring
IBM WebSphere Application Server” on page 211. If the user registry resides
in an LDAP directory, provide the Distinguished Name for the administrative
account, instead of its common name, while assigning a user to an
administrative role.
10.6 Discussion and conclusions
This scenario showed an application that uses DCE's secure remote procedure
calls and how it could be moved to a Java-based application server with a
significant re-use of the legacy C code. Although in this scenario the proportion
of new code was relatively high in relation to existing DCE code, most real-life
applications can be revised with considerably less new code.
The scenario also demonstrated both an easy path to enable legacy DCE
applications for the Web, and an easy path for legacy DCE applications to
migrate an entire application to Java. In the first situation we used a CORBA
client to replace an existing DCE client, but we could have used a Web client
such as a browser or applet. In the second situation, we wrote the enterprise
bean wrapper layer to route calls either into newly written code or to our existing
C code with little extra effort.

Get DCE Replacement Strategies now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.