Developing the Installation and Configuration Plan

Installing and configuring a Java ES solution is an extended process that uses the Java ES installer along with separate configuration wizards for a number of components. For trouble-free installation and configuration of your solution, a plan is essential.

This section describes how the installation and configuration plan for the evaluation solution is developed. The two main issues you address to develop an installation and configuration plan are the following:

• Components have configuration dependencies, so you must install and configure your components in the correct sequence. For example, most components store configuration data in Directory Server's LDAP directory and make directory entries for their administrator accounts. Therefore, Directory Server must be installed and running before you configure the other components. Your installation and configuration plan must identify the correct sequence for the components in your solution.

• Components in a solution must interoperate as a system, and you must supply configuration values that “glue” the components together. These configuration values are specific to your solution. For example, when you configure Directory Server you establish a URL for accessing the directory and a directory manager account and password for logging in to the directory. Later, when you configure Access Manager, you supply the Directory Server URL, the directory manager account, and the directory manager password. This configuration makes it possible for Access Manager to interoperate with Directory Server. Developing an installation and configuration plan ensures that your configuration input values are consistent and that you will configure a system of interoperating components.

The basic steps for installing and configuring any Java Enterprise System solution are the following:

1. Run the installer to copy all of the component files to the computer systems used in your solution. The installer configures instances of some components. based on values you input. You supply values that implement the directory tree described in your User Management specification and configure the component instances for interoperation.

2. Start and verify correct functioning of the component instances that are configured by the installer.

3. Run the configuration wizards to configure instances of the components not configured by the installer. The order in which you run the configuration wizards is determined by the components' configuration dependencies.

When the installation and configuration plan is complete, it lists the values to input in the installer, the correct sequence for running the configuration wizards, and the values to input in the configuration wizard pages.

Applying this approach to the set of components identified in the architecture for the evaluation solution gives the following specific installation and configuration steps for the evaluation solution:

1. You run the installer only once, on one computer system. The installer copies all component files to the computer system and registers the components with the operating system. The installer also configures instances of the following components:

   • Directory Server.

   • Web Server

   • Access Manager

   • Portal Server

   When you run the installer, you establish the base DN for the LDAP directory. You also supply configuration values, such as the Directory Server URL, that configure the components to interoperate. You also use the installer to install a sample portal desktop.

2. You start and verify Directory Server. You start the Directory Server instance first because all the other components use directory services.

3. You start Web Server. Starting Web Server starts the components that run in Web Server's web container, which are Access Manager and Portal Server.

4. You verify that Access Manager is running. Access Manager must be running because the other components use Access Manager’s authentication services.

5. You verify that Portal Server is running.

6. You configure Directory Server for use with the communications components.

7. You create, configure, and start an instance of Messaging Server. You configure your Messaging Server instance to interoperate with Directory Server and Access Manager. You must configure Messaging Server before the remaining components, because configuring Messaging Server creates a branch of the LDAP tree that corresponds to the mail domain. You then configure the remaining components to use the new branch for their user and group data.

8. You verify your Messaging Server instance.

9. You create, configure, and start an instance of Calendar Server. You configure your Calendar Server instance to interoperate with Messaging Server, Directory Server, and Access Manager.

10. You verify your Calendar Server instance.

11. You create, configure, and start an instance of Communications Express. You configure your Communications Express instance to interoperate with Calendar Server,Messaging Server, Directory Server, and Access Manager.

12. You create, configure, and start an instance of Instant Messaging.

13. You verify your Instant Messaging instance.

14. You create, configure, and start an instance of Delegated Administrator.

15. You use Delegated Administrator to extend you LDAP schema for mail and calendar services.

16. You use Delegated Administrator to create a test end user account.

17. You configure Messaging Server, Calendar Server, and Portal Server for single sign-on.

18. You verify that your test user account can use single sign-on log in to Communications Express and access mail and calendar services.

19. You verify that your test user account can use single sign-on log in to access mail and calendar services through the portal desktop.

The configuration dependencies for the evaluation solution are the same for as they would be for a multiple-system production solution, therefore the sequence of configuration tasks is similar to the sequence you use for a larger solution.

In a larger, multi-system solution, the sequence often becomes more complex. For example, you might need to run the installer on several systems to install several instances of Directory Server, and then start all the Directory Server instances. You next run the installer on another set of systems to install several instances Messaging Server, and follow that by configuring the Messaging Server instances, and so on.