Account Management 3.0
 
Core Services Quick Start Guide for NetWare
    Prerequisites Installation and verification steps
  1. Verify the NetWare server you wish to install Account Management Components to is running
    2. eDirectory 8.6.2 or higher.
  2. Make sure the NetWare server(s) you are installing Secret Store to have the latest NICI installed on them, version 2.4 at a minimum.
  3. Install Secret Store 3.03 or higher to all netware servers holding replicas of users to be managed by Account Management 3.0
    4. 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.
  4. Make sure the SecretStore installation has completed correctly by checking to see if the Secret Store NLMs have loaded correctly. To verify the installation of SecretStore Issue the command modules ssldp*. Restart nldap.nlm if it has not loaded yet.

    Account Management Manager for NetWare Installation
  5. Retrieve the Manager Services setup program for Windows and NetWare from this archive or CD by selecting managersetup.exe.
    6.
  6. From a Windows workstation with the NetWare client installed, log into the tree containing the server you are installing Account Management Manager to, and launch the managersetup.exe program and follow the instructions.
    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.
  7. Load the Manager (ASAMMgr.nlm) from the directory you installed it to (sys:asam\bin\manager by default).
  8. Add the manager startup to your autoexec.ncf if you wish to load it on server startup and restart the server holding the manager to verify the autexec.ncf is setup properly.
  9. 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 two steps because the Core Services Setup completed these.
  10. 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 to add the IP address of the server the Event Listener is running on to the object.
    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. Retrieve the Event Listener Setup program for Windows and NetWare. Select this link eventlistenersetup.exe to download or retrieve it from the Account Management Web Interface.
  12. Run the setup program and follow the settings as prompted.
  13. If DirXML is not installed on the server planned for running the Event Listener Run the DirXML 1.1 (or higher) setup program as directed by the DirXML documentation
  14. 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_nw.xml (sys:asam\ASAMDriverInstall_nw.xml by default). Respond to the configuraion options.
  15. Start the Driver by selecting the driver set associated with the driver and choose properties in ConsoleOne then select start.
  16. To verify the Event Listener configuration complete the steps outlined in Account Management Core Initial Configuration and Testing following the Agent Installation proceedures.


    Account Management Agent for NetWare Installation
  17. Create the Agent object by going to the Account Management Web Interface and selecting Agents on the left panel then choose Add. Enter a unique agent name, click apply, then enter the other options as requested.
    Make sure
    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.
  18. Retrieve the Agent Setup program for Windows and NetWare either from this link agentsetup.exe or from the Manager Web Interface, select file distribution, and retrieve the file.
  19. From a Windows workstation with the NetWare client installed, log into the tree containing the server you are installing Account Management Agent to, and launch the agentsetup.exe program and follow the instructions.
  20. Load the Agent (ASAMagnt.nlm) from the directory you installed it to (sys:asam\bin\agent by default).
  21. Add the agent startup to your autoexec.ncf if you wish to load it on server startup and restart the server holding the manager to verify the autexec.ncf is setup properly.
  22. Verify that the agent 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 the manager installation) and choosing log viewer. Select the agent operational log. If you can view the log the installation was successful.


    Account Management Core Initial Configration and Testing
  23. Go to the Web Interface and select Census on the left panel.
  24. 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.
  25. 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.
  26. Select Object Search and press search with out selecting anything and see if the users you set up in the Census Search objects.
  27. To verify the Event Listener create a uniquely named user using ConsoleOne, or similar utility, under the contianer pointed to by the Census Search Object.
  28. Do NOT run a trawl.
  29. Wait a bit
  30. Do the search again, this time type the first few letters of the user 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