To Develop a Sequence for Host B (Second Session)

The following high-level tasks are required:

Steps

1. Installing Access Manager using the Configure Later option

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.

   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. Editing the amsamplesilent file

   1. Go to the Access Manager bin directory:

      Solaris OS: cd AccessManager-base/SUNWam/bin

      Linux: cd AccessManager-base/identity/bin

   2. Make a copy of the amsamplesilent file. For example:

      cp -p amsamplesilent am.non_root_install

   3. Edit the copy of the amsamplesilent file.

      • Set BASEDIR to the same value that you selected for the installation directory of Access Manager during installation

      • Update SERVER_HOST, SERVER_PORT, DS_HOST, DS_PORT, ROOT_SUFFIX, WS61_ADMINPORT and all related password fields (DS_DIRMGRPASSWD, ADMINPASSWD, AMLDAPUSERPASSWD).

4. Using the edited amsamplesilent file to deploy Access Manager

   ./amconfig -s ./am.non_root_install

   1. Set NEW_OWNER to the non-root user.

   2. Set NEW_GROUP to the non-root group.

5. As the non-root user, stopping the Web Server admin instance and Web Server instance

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

   chown -R <non-root-user\>:<non-root-group\> WebServer-base

7. As the non root-user, starting the Web Server admin instance and Web Server instance

8. Accessing the Web Server admin console in a browser and logging in as the admin user

9. Selecting the instance on which you deployed Access Manager

   1. Click Manage.

   2. Click Apply and click Apply Changes.