This task consists of the following procedures:
This procedure assumes that you are installing Access Manager on Solaris 10 8/07 OS or later version. Hence, no operating system patches need to be installed. The Java ES installer evaluates the state of the operating system and indicates if you need to install a patch. If you are using versions of the operating system older than Solaris 10 8/07 OS, it is better to install any required patches before you begin the actual Access Manager installation procedure.
The following procedure runs the Java ES installer without saving a state file. You can choose to run the installer and capture your input in a state file (-saveState state-filename). You could then use the state file to re-create the installation if, for example, you needed to reinstall Access Manager.
Download the Java ES software distribution to am1.
The procedure is documented in To Download the Software Distribution.
Log in as root or become superuser.
# su -
Start the Java ES installer.
# cd /portdist_71u2/Solaris_sparc
# ./installer
This procedure uses the GUI installer. The installer can also be run in text mode by using the - nodisplay option.
The Welcome panel opens.
In the Welcome panel, click Next.
The Software License Agreement panel opens.
In the Software License Agreement Panel, review the license terms and click Yes, Accept License.
The Choose Software Components panel opens.
In the Choose Software Components panel, select the following components:
Application Server Enterprise Edition 8.2
Domain Administration Server
Application Server Node Agent (Not needed for this module, but can be installed for possible future use)
Command-Line Administration Tool
Sample Application (Not needed for this module, but can be installed for possible future use)
High Availability Session Store 4.4 (Not needed for this module, but is a dependency of Application Server that is automatically selected and cannot be unselected)
Java DB 10.1 (Not needed for this module, but is a dependency of Application Server that is automatically selected and cannot be unselected)
Java DB Client
Java DB Server
Access Manager 7.1
Access Manager Core Services
Access Manager Administration Console
Common Domain Services for Federation (Not needed for this module, but can be installed for possible future use)
Access Manager SDK
Access Manager Session Failover Client
Message Queue 3.7 UR1
Install Multilingual Package(s) for all selected components (selected automatically, but optional if using English)
Also, unselect Directory Server Enterprise Edition 6.2 if it is automatically selected.
Click Next.
The Dependency Warning panel opens.
In the Dependency Warning panel, choose Use Directory Server Installed on a Remote Machine and click OK.
The installer evaluates the Java SE Software Development Kit on the computer and determines if an upgrade is required. On a fresh copy of Solaris 10 8/07 OS, an upgrade is needed, and the Java SE Software Development Kit Upgrade Required panel opens.
In the Java SE Software Development Kit Upgrade Required panel, select Automatic Upgrade to the Version Included with the Installer and click Next.
The installer evaluates the Java ES shared components on the computer and determines if any upgrades are required. On a fresh copy of the Solaris 10 8/07 OS, shared component upgrades are needed, and the Shared Components Upgrades Required panel opens.
In the Shared Components Upgrades Required panel, click Next.
The installer upgrades the shared components. The Specify Installation Directories panel opens.
In the Specify Installation Directories panel, type the following values and click Next.
Input Field |
Value |
---|---|
Access Manager |
/opt |
Application Server |
/opt/SUNWappserver |
Application Server Data and Configuration |
/var/opt/SUNWappserver |
The installer checks the system, and the System Check panel opens.
In the System Check panel, evaluate the results of the system check.
If the system check is favorable, click Next.
The Choose a Configuration Type panel opens.
In the Choose a Configuration Type panel, select Configure Now and click Next.
The Custom Configuration Panel opens.
In the Custom Configuration Panel, note the following message and click Next.
The following component products cannot be configured during installation: Java DB Click Next to configure the other components. |
The Specify Administrator Account Preferences panel opens.
In the Specify Administrator Account Preferences panel, type the following values and click Next.
If you are using different administrator accounts for different services (Java ES products), select the corresponding checkbox in the panel (see Administrator Account Specification).
Input Field |
Value |
---|---|
Administrator User ID |
admin |
Administrator Password |
app-server-admin-password |
The Common Server Settings panel opens.
In the Common Server Settings panel, type the following values and click Next.
Input Field |
Value |
---|---|
HostName |
am1 |
DNS Domain Name |
pstest.com |
Host IP Address |
10.0.2.1 |
System User |
root |
System Group |
root |
The Application Server: High Availability Session Store (HADB) panel opens.
In the Application Server: High Availability Session Store (HADB) panel, type the following values, uncheck the Automatically Start HADB checkbox, and click Next.
Input Field |
Value |
---|---|
HADB Management Port |
1862 |
HADB Resource Directory |
/var/opt |
HADB Administrator Group |
root |
The Application Server: Domain Administration Server panel opens.
In the Application Server: Domain Administration Server panel type the following values and click Next.
Input Field |
Value |
---|---|
Admin Port |
4849 |
JMX Port |
8686 |
HTTP Port |
80 |
HTTPS Port |
8181 |
Master Password |
app-server-master-password |
The Access Manager: Specify Configuration Information panel opens.
In the Access Manager: Specify Configuration Information panel, type the following values and click Next.
Also, record the values that you specify in this panel. They will be needed when installing other components in the reference configuration.
Input Field |
Value |
---|---|
Install Type |
Legacy Mode |
Administrator User ID |
amadmin (This administrator account is different from the admin account in step 15, Administrator Account Preferences panel.) |
Administrator Password |
access-manager-admin-password |
LDAP User ID |
amldapuser |
LDAP Password |
access-manager-LDAP-password |
Password Encryption Key |
password-enc-key (This password must be at least 12 characters. A value is proposed by the installer.) |
The Access Manager: Choose Deployment Container panel opens.
In the Access Manager: Choose Deployment Container panel, type the following values and click Next.
Input Field |
Value |
---|---|
Sun Java System Application Server |
Yes |
The Access Manager: Specify Sun Java System Application Server panel opens.
In the Access Manager: Specify Sun Java System Application Server panel type the following values and click Next.
Input Field |
Value |
---|---|
Secure Server Instance Port |
No |
Secure Administration Server Port |
Yes |
The Access Manager: Specify Web Container for Running Access Manager Services panel opens.
In the Access Manager: Specify Web Container for Running Access Manager Services panel, type the following values and click Next.
Input Field |
Value |
---|---|
Host Name |
am1.pstest.com |
Services Deployment URI |
amserver |
Common Domain Deployment URI |
amcommon |
Cookie Domain |
pstest.com |
Password Deployment URI |
ampassword |
Console Protocol |
HTTP |
The Access Manager: Choose Access Manager Console panel opens.
In the Access Manager: Choose Access Manager Console panel, type the following values and click Next.
Input Field |
Value |
---|---|
Administration Console |
Deploy New Console |
Console Deployment URI |
amconsole |
Console Host Name |
am1.pstest.com |
Console Port |
80 |
The Access Manager: Specify Directory Server Information panel opens.
In the Access Manager: Specify Directory Server Information panel, type the following values and click Next.
Input Field |
Value |
---|---|
Directory Server Host |
ds.pstest.com (The logical service name was created when the directory service module's load balancer was configured.) |
Directory Server Port |
389 |
Access Manager Directory Root Suffix |
dc=pstest,dc=com (The suffix was defined when Directory Server was installed.) |
Directory ManagerDN |
cn=Directory Manager |
Directory Manager Password |
directory-manager-password (This password was defined when Directory Server was installed.) |
The Access Manager: Specify Directory Server Data panel opens.
In the Access Manager: Specify Directory Server Data panel, type the following values and click Next.
Input Field |
Value |
---|---|
Is Directory Server Provisioned With User Data? |
No |
The Ready to Install panel opens.
In the Ready to Install panel, indicate whether you want to open the software registration window during installation.
This panel enables you to register the components that you have selected for installation with Sun Connection. Sun Connection is a Sun-hosted service that helps you track, organize, and maintain Sun hardware and software. For example, Sun Connection can inform you of the latest available security fixes, recommended updates, and feature enhancements.
If you choose to register, information about the installation is sent to the Sun Connection database. You can also register at a later date, after installation has been completed.
Click Install.
The installer copies files to the computer, modifies configuration files based on the values provided, and deploys Access Manager to the Application Server's Domain Administration Server (DAS) instance.
When the installation is complete, review the installation in the Summary field.
Click Exit to exit the installer.
Check the installation log files for any installation errors.
# cd /var/sadm/install/logs
# egrep -i 'fail|error' Java*
The following procedure confirms that Access Manager has been installed by starting the Access Manager Console login page.
Check that Application Server is running.
# netstat -an | grep 80
If Application Server is not running, start it.
# /opt/SUNWappserver/appserver/bin/asadmin start-domain --user admin domain1
When prompted, type the app-server-admin-password.
Verify the operation of Access Manager on am1.
Start a browser.
Open the Access Manager Console login page:
http://am1.pstest.com/amconsole
The login page opens.
Log in to the Access Manager Console by typing the following values and clicking Login.
Input Field |
Value |
---|---|
User ID |
amadmin |
Password |
access-manager-admin-password |
The Access Manager Console opens, which confirms that Access Manager is deployed and running in the web container.