Sun Java Communications Suite 5 Installation Guide

Requirements and Sequence Issues

If your installation plan calls for deploying Access Manager in an instance of Web Server or Application Server that is not owned by the superuser (root), you must install Access Manager in a separate installation session from Directory Server and Web Server or Application Server.

The general steps for creating this installation sequence include the following:


Note –

If you have already deployed Access Manager in a root-owned instance of Web Server or Application Server, uninstall any copy of Access Manager before following the procedure in this section.


ProcedureTo Develop a Sequence for Host A

The following high-level tasks are required:

  1. Checking the installation sequence guidelines

    Check to see what guidelines apply to this example and make adjustments as needed.

  2. Checking the installation prerequisites

    Check to see what tasks you might need to perform for this installation before starting.

  3. Installing Directory Server using the Configure Now type

    • In the Common Server Settings page, enter the non-root user for System User and non-root group for System Group.

    • Select port numbers for Directory Server that are higher than 1024 (389 for instance LDAP port and 636 for instance SSL LDAP port).

  4. As the non-root user, starting Directory Server (all processes must be owned by the non-root user)

ProcedureTo Develop a Sequence for Host B (First Session)

The following high-level tasks are required:

  1. Checking the installation sequence guidelines

    Check to see what guidelines apply to this example and make adjustments as needed.

  2. Checking the installation prerequisites

    Check to see what tasks you might need to perform for this installation before starting.

  3. Installing Web Server using the Configure Now type

    • In the Common Server Settings page, enter the non-root user for System User and non-root group for System Group.

    • In the Directory Server Instance Creation page, set System User and System Group to non-root user and group.

    • In the Web Server: Administration page, change the Administration Runtime User ID to the non-root user.

    • In the Web Server: Default Web Server Instance page:

      1. Change the Runtime UNIX User ID to the non-root user.

      2. Select a value for HTTP Port that is higher than 1024.

  4. As the non-root user, starting the Web Server administration instance and Web Server instance

    All processes should be owned by the non-root users.

ProcedureTo Develop a Sequence for Host B (Second Session)

The following high-level tasks are required:

  1. Installing Access Manager using the Configure Later type

  2. Changing ownership of the following directories from root/other to the non-root user/non-root group:

    These shared component directories must be changed because they are configured into the web container classpath by the Access Manager configuration program. All processes should be owned by the non-root users.

    • Solaris OS: /opt/SUNWma and /etc/opt/SUNWma

    • Linux: /opt/sun/mobileaccess and /etc/opt/sun/mobileaccess


      chown -R nonroot-user:nonroot-group
      
       /opt/SUNWma /etc/opt/SUNWma
  3. Deploying Access Manager


    ./amconfig -s ./am.non_root_install
  4. As the non-root user, stopping the Web Server admin instance and Web Server instance

  5. As root, changing the ownership of the Web Server installation directory


    chown -R <non-root-user\>:<non-root-group\> WebServer-base
    
  6. As the non root-user, starting the Web Server admin instance and Web Server instance