Before you deploy the OpenSSO Enterprise WAR file, here are a few changes to consider from previous releases of Access Manager and Federation Manager:
You deploy OpenSSO Enterprise from the opensso.war file, using the web container administration console or deployment command. You no longer run the Java Enterprise System installer.
You initially configure OpenSSO Enterprise using either the GUI or command-line Configurator. Then, to perform additional configuration, you use either the Administration Console or the new ssoadm command-line utility. You no longer run the amconfig script using variables in the the amsamplesilent file as input.
Configuration data, including policy agent configuration data, is stored in a centralized repository. This repository can be either Sun Java System Directory Server or the OpenSSO data store (which is usually transparent to the user). OpenSSO Enterprise server does not use the AMConfig.properties or serverconfig.xml files, except for co-existence with previous versions of Access Manager.
The following procedure summarizes the OpensSSO Enterprise WAR file deployment. Links are provided to the detailed steps in the Sun OpenSSO Enterprise 8.0 Installation and Configuration Guide.
If necessary, install, configure, and start one of the supported web containers listed in Chapter 2, Deploying the OpenSSO Enterprise Web Container, in Sun OpenSSO Enterprise 8.0 Installation and Configuration Guide.
Download and unzip the opensso_enterprise_80.zip file from one of the following sites:
OpenSSO site: http://opensso.dev.java.net/public/use/index.html
Be sure to check the Sun OpenSSO Enterprise 8.0 Release Notesfor any current issues.
Deploy the opensso.war file to the web container, using the web container administration console or deployment command.
Run either the GUI or command-line Configurator.
To run the GUI Configurator, enter the following URL in your browser:
For example: https://opensso.example.com:58080/opensso
If you are running the GUI Configurator, enter values in the Configurator fields or accept the default value for some fields. The GUI Configurator has two configuration options:
The Default Configuration option requires you to enter only the OpenSSO Enterprise administrator (amAdmin) and default policy agent (UrlAccessAgent) passwords. The Configurator then uses default values for the other configuration options.
Use the Default Configuration for development environments or simple demonstration purposes when you just want to evaluate OpenSSO Enterprise features.
The Custom Configuration option allows you to enter specific configuration values for your deployment (or accept the default values).
Use the Custom Configuration for production and more complex environments. For example, a multi-server installation with several OpenSSO Enterprise instances behind a load balancer.
Detailed steps for configuring OpenSSO Enterprise are in:
Launch OpenSSO Enterprise using the specific web container console or deployment command, or by specifying the URL from Step 4 in your browser.
Login to the Console as the OpenSSO Enterprise administrator (amadmin) using the password you specified when you ran the Configurator.
To make additional configuration changes to your deployment, use the OpenSSO Administration Console or the ssoadm command-line utility.
For information, refer to the OpenSSO Administration Console Online Help or the Sun OpenSSO Enterprise 8.0 Administration Reference.