Account Management 3.0
 
Core Services Quick Start Guide for Linux and Solaris
    Prerequisites Installation and verification steps
  1. Verify the server you wish to install Account Management Components to is running eDirectory 8.6.2 or higher.
  2. Make sure the server(s) you are installing Secret Store to have the latest NICI installed on them, version 2.4 at a minimum.
  3. Retrieve Secret Store 3.03 for Linux or Solaris from the web at download.novell.com
  4. Install Secret Store 3.03 or higher to all servers holding replicas of users to be managed by Account Management
    5. Make sure "Update timestamp on read secret" is unchecked on the secret store object inside of the security object at the root of your tree.
  5. Make sure the SecretStore installation has completed correctly by
    6. issuing nss -l (it will either load or say it is loaded).

    Account Management Manager Installation
  6. Retrieve the Manager Services archive for Linux or Solaris here by selecting am300_manager_linux.tar.gz or am300_manager_solaris.tar
  7. From the Linux or Solaris server, extract the archive to a temporary directory.
  8. Execute setup/am-install and follow the steps provided.
  9. Locate and execute /usr/local/ASAM/bin/Manager/manager-config which extends the schema for Account Management and launches the Manager with the -i option (verify by 'ps -ef | grep asammgr').
  10. Access the manager https://managerServerIPorDNS:3451/ and continue the configuration process. When you have completed, kill and restart the manager without the -i.
    For initial configuration you should use IP addresses since DNS can cause timeouts at certain sites, you can later add dns entries once the intitial configuration is complete.
  11. Verify that the manager installation was successful by going to the Account Management Web Interface at https://managerServerIPorDNS:3451/ (the port number after the colon will match what you chose during installation).


    Account Management Event Listener (Account Management's DirXML Driver) Installation
    If you are installing the Event Listener on the same server you installed the Manager you can skip the following three steps because the Core Services Setup completed these.
  12. Create the Event Listener object in the Web Interface by selecting Event Listeners on the left panel. Select add and choose a unique Event Listener object name.
    Make sure the IP address(es) for the Event Listener Object are configured correctly.
    For initial configuration you should use IP addresses since DNS can cause timeouts at certain sites, you can later add dns entries once the intitial configuration is complete.
  13. Retrieve the Event Listener archive for Linux and Solaris either from this link am300_eventlistener linux.tar (the event listener for Solaris is not available at release time, please check at support.novell.com for updates regarding the Event Listener for Solaris) or download it from the Manager Web Interface.
  14. Launch the install script lst-config and follow the settings as prompted.
  15. If DirXML is not installed on the server planned for running the Event Listener Run the DirXML 1.1 (or higher) installation program as directed by the DirXML documentation
  16. When prompted to select the driver to install during the DirXML installation (if DIrXML was all ready installed Choose Install a new Application Driver from the Wizards menu in ConsoleOne) browse to directory you installed the Manager or Event Listener to and select ASAMDriverInstall_unix.xml (/usr/local/ASAM/ASAMDriverInstall_unix.xml by default). Respond to the configuraion options.
  17. Start the Driver by selecting the driver set associated with the driver and choose properties in ConsoleOne then select start.
  18. To verify the Event Listener configuration complete the steps outlined in Core Initial Configuration and Testing following the Agent Installation.


    Account Management Agent Installation
  19. Create the Agent object by going to the Account Management Web Interface and select agents on the left panel then choose Add. Enter a unique agent name and enter the other options as requested.
    If you are installing the Agent on the same server as the Manager make sure the ports are different.
    For initial configuration you should use IP addresses since DNS can cause timeouts at certain sites, you can later add dns entries once the intitial configuration is complete.
  20. Retrieve the Agent archive for Linux or Solaris either from this link am300_agent_linux.tar or am300_agent_solaris.tar from the Manager Web Interface.
  21. From the Linux or Solaris server, extract the archive and run the ASAM/setup/install script. Follow the steps indicated.
  22. Run '/usr/local/ASAM/bin/Agent/asamagnt -s' to obtain an SSL Certificate for the agent.
  23. Run the agent by issuing (/usr/local/ASAM/bin/Agent/asamagnt)
  24. Verify that the agent installation was successful by first checking to see if the ASAM Agent is running (ps -ef | grep asamagnt). Next go to the Account Management Web Interface at https://managerServerIPorDNS:3451/ (the port number after the colon will match what you chose during installation). Coose log viewer and select the agent operational log. If you can view the log the installation was successful.


    Account Management Core Initial Configration and Testing
  25. Go to the Web Interface and select Census on the left panel.
  26. Configure the options as you desire including search object configuration. Select a container for starters that has a few users in it as your first search object.
  27. Initiate a trawl by selecting trawl on the left panel in the Web Interface and select start.
    Every time you modify a search object you should initiate a trawl to make the changes take effect.
  28. Select Object Search and press search with out selecting anything and see if the users you set up in the Census Search objects are listed.
  29. To verify the Event Listener create a uniquely named user, using ConsoleOne, or similar utility, under a contianer referenced by a Census Search Object.
  30. Do NOT run a trawl.
  31. Wait a bit
  32. Do an object search again for the user(s) you just created. If they show up, all is operating properly and you are ready to install your first platform. See the quick start guide for the platform OS you are installing listed in the readme.html