Whenever you use the Java ES installer to configure Access Manager on Web Server, you will need to perform the following steps.
For all Access Manager installations, the web container needs to be restarted. If a full installation is being performed on Web Server or Application Server, the installer stops the web container instance, which requires you to start web container manually. For instructions on restarting Access Manager, see Starting and Stopping Access Manager.
After a Configure Automatically During Installation, you can start Access Manager and log in to the Access Manager console. However, you cannot perform basic user management operations until you complete some final configuration steps. These steps differ depending on whether Access Manager is using a Directory Server instance that is already provisioned with user data. There are additional configuration tasks that you might want to perform for your deployment.
Directory Server Provisioning Situations
Enabling the Directory Server Referential Integrity Plug-in
Adding Access Manager Indexes to Directory Server
For instructions on performing these tasks, refer to the Sun Java System Access Manager 7.1 Postinstallation Guide.
After a Configure manually after installation operation, the packages are installed and you are ready to configure Access Manager by using the Access Manager configuration batch file, AccessManager-base\setup\amconfig.bat. For more information about using this program, see Sun Java System Access Manager 7.1 Postinstallation Guide.
For instructions on configuring Access Manager for a third-party web container (BEA WebLogic or IBM WebSphere Application Server), see Sun Java System Access Manager 7.1 Postinstallation Guide.