Account Management 3.0

Account Management 3.0.2 Update Instructions

These instructions are for installing Account Management 3.0.2 (also known as Support Pack 2) to existing Account Management 3.0 systems.

Novell^® Account Management 3.0.2 includes all of the changes introduced with Support Pack 1. You do not need to install Support Pack 1 before you upgrade to Account Management 3.0.2.

First-Time Installation: If you are installing Account Management 3.0 for the first time, you can disregard this document. Instead, follow the installation procedures outlined in the Quick Start guides for installation and configuration of Account Management.

Upgrading Core Services for Linux and Solaris

Password Replication Migration

If you use or plan to use password replication and have not installed Support Pack 1, you must perform password replication migration when you upgrade to Account Management 3.0.2. For details, see Password Replication Migration.

Installing Account Management 3.0.2 to the Manager, Event Listener, and Agents

The procedure for upgrading each component (Manager, Event Listener, and Agent) to Account Management 3.0.2 is essentially the same. Upgrade the Manager first, then any Event Listeners not running on the Manager Server, and finally each Agent.

Upgrading the Manager upgrades the Event Listener running on the Manager Server.

Do not use the same temporary location for expanding archives without first removing all of the previous files from it.

1. Ensure that the component is not running.
   • To stop the Manager and Agents, use the kill command.
   • To stop the Event Listener, use ConsoleOne^® to stop the ASAMDriver object. (Do this when upgrading the Manager, and when upgrading each additional Event Listener, if any.)
2. With your Web browser, open readme.html from the root of the Account Management 3.0.2 distribution.
3. Using the link in readme.html, retrieve the Account Management 3.0.2 archive for the component. After you have upgraded the Manager, you can also use the File Distribution in the Web interface to obtain the archives.
4. Extract the archive to a temporary location. This creates and populates an ASAM directory in the temporary location.
5. Run ASAM/setup/install and respond to the prompts.
6. Remove all of the files from the temporary location.
7. Start the upgraded component. (If you have not installed Account Management to the default location, adjust the pathnames shown accordingly.)
   • To start the Manager, enter /usr/local/ASAM/bin/Manager/asammgr.
   • To start the Event Listener, use ConsoleOne to start the ASAMDriver object.
   • To start an Agent, enter /usr/local/ASAM/bin/Agent/asamagnt.

Updating the DirXML Subscriber Attributes

Use ConsoleOne to perform the following steps to modify the DirXML™ subscriber attributes for each Event Listener:

1. Add the class ASAM-enterpriseUser to the subscriber filter.
2. Add the attributes to the ASAM-enterpriseUser class.
   • ASAM-addTime
   • GUID
3. Add the class ASAM-agent to the subscriber filter.
4. Add the following attributes to the ASAM-agent class:
   • ASAM-pChangeList
   • GUID
5. Restart the Driver.