Communications Suite 6 Update 2 Installation Scenario - Access Manager

Communications Suite 6 Update 2 Installation Scenario - Install Access Manager

Topics:

Assumptions

This scenario shows how to install Access Manager on a separate host. It is based on the Install/configure Access Manager leaf in the Communications Suite 6 Update 2 Installation Flowchart. The scenario makes these assumptions:

  • You are deploying Communications Suite on multiple hosts or Solaris zones.
  • This Access Manager installation is one functional component of your multi-host deployment.
  • You are installing Access Manager on a separate host or Solaris zone; you are not bundling Access Manager with Communication Suite products on the same host.
  • If you are deploying multiple instances of Access Manager across several hosts or zones, you can follow these instructions for each host on which you install Access Manager.

Which Software Components and Downloads Do You Need?

  • Java ES 5 Update 1 distro - for Access Manager 7.1 and Web Server 7.0 Update 1

Download this software from the Communications Suite download site. For details, see Get the Software.

Note
If you are installing Access Manager 7.1 on a Red Hat Linux system, verify that a compatible version of Java Development Kit (JDK) is installed. For details, see Verifying the Correct JDK Version to Support Access Manager.

Which Task Sequence Do You Follow?

  1. Be sure that Directory Server Enterprise Edition 6.3 is installed and configured on another machine or zone in your deployment.
  2. Start Directory Server.
  3. Launch the Java ES 5 Update 1 installer.
  4. With the Java ES installer, install Access Manager 7.1 and Web Server 7.0 Update 1.
    To install these products, follow the instructions in the Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.
    For details, see this Access Manager Configuration Guide. You can also find installation instructions in this Access Manager Deployment Example.
  5. Start Web Server.
  6. Start Access Manager.

Labels

installing installing Delete
accessmanager accessmanager Delete
installationscenario installationscenario Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (1)

 

  1. Apr 14, 2008

    DNReddy says:

    Kendo Needs either of Access Manager Server OR AM sdk to be installed on same ...
    • Kendo Needs either of Access Manager Server OR AM sdk to be installed on same host if AM auth/sso is used as Identity strategy.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact