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 will stop the web container instance so only the instance needed to be started. For instructions on restarting Access Manager, see Starting and Stopping Access Manager.
After a Configure Now installation, you can start Access Manager and log into 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 or not 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 Later installation, the packages are installed and you are ready to configure Access Manager using the Access Manager configuration script, AccessManager-base/bin/amconfig. Instructions for using this program are contained in the Sun Java System Access Manager 7.1 Postinstallation Guide.
For instructions on configuring Access Manager for a third-party web container on Solaris OS (BEA WebLogic or IBM WebSphere Application Server), refer to Sun Java System Access Manager 7.1 Postinstallation Guide.