User manual NOVELL IMANAGER INSTALLATION V2.7

[. . . ] novdocx (en) 16 April 2010 AUTHORIZED DOCUMENTATION Installation Guide Novell® 2. 7 October 15, 2010 iManager www. novell. com Novell iManager 2. 7 Installation Guide novdocx (en) 16 April 2010 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. [. . . ] All plug-ins are downloaded or updated or the iManager download server is unavailable appears in the plug-in download area, one or more of the following conditions exist: There are no updated plug-ins available on the Novell download site There is a problem with your Internet connection; verify your connection Installing iManager 17 novdocx (en) 16 April 2010 Connection to the Novell Descriptor File (http://www. novell. com/products/consoles/ imanager/iman_mod_desc. xml) was not successful. The iManager install is behind a proxy that does not allow a connection to the above URL 11 Specify if you want to install plug-ins from a local drive, then click Next. 12 (Conditional) To install plug-ins from a local directory, specify the directory path that contains the appropriate plug-in (. npm) files. The default path is /extracted location/iManager/installs/plug-ins, but you can specify any valid mount point here. The defaults are 8080 for HTTP, 8443 for HTTPS, and 9009 as the MOD_JK connector port. 14 (Optional) Specify an authorized user and the appropriate eDirectory tree name that this user will manage, then click Next. This information is not used to authenticate to eDirectory during installation and the information is not validated in any way. If you leave these fields blank, iManager allows any user to install plug-ins and make changes to iManager server settings (not recommended long-term. ) Specify an authorized user postinstall from the Configure > iManager Server > Configure iManager > Security page in iManager. For more information, see "Authorized Users and Groups" in the iManager 2. 7. 4 Administration Guide. During installation, iManager files are installed, plug-ins are downloaded, and configuration changes occur. After the installation completes, the Install Complete page, which displays the successful/ unsuccessful installation message, is displayed. To access iManager, click the first link on the Getting Started page, then log in. For more information, see "Accessing iManager" in the iManager 2. 7. 4 Administration Guide. IMPORTANT: When you install iManager on Linux, the following files from InstallAnywhere is left with writeable permission. /var/opt/novell/tomcat5/webapps/nps/UninstallerData/ . com. zerog. registry. xml /var/opt/novell/tomcat5/webapps/nps/UninstallerData/ Uninstall_<PluginName>/. com. zerog. registry. xml <PluginName> - The name of the plug-in installed on iManager. You must change the permissions from 600 to 644 using the chmod command. If you modify, it might impact the other installations that use InstallAnywhere. 18 Novell iManager 2. 7 Installation Guide novdocx (en) 16 April 2010 1. 5. 2 iManager Server on Windows If the iManager 2. 7 installation routine detects a previously installed version of iManager 2. 5 or 2. 6, it prompts you that it will remove the existing iManager and Tomcat. However, when removing the previously installed version of iManager, its directory structure is backed up to the old TOMCAT_HOME directory to preserve any previously created custom content. To prepare for the installation, review the following checklist of prerequisites. Prerequisites In addition to the general prerequisites listed in Section 1. 2, "Prerequisites, " on page 12, the following prerequisites also apply to iManager on Windows: Previous versions of iManager: If you have installed iManager 2. 5 or 2. 6, you do not need to uninstall it. See Chapter 2, "Upgrading iManager, " on page 27 for more information. However, following the iManager 2. 7 installation, you can manually integrate iManager with your existing Web server infrastructure, if desired. Processor: Pentium III 600 MHz or higher processor Disk Space: 500 MB minimum for a local installation Memory: 512 MB of RAM (1024 MB recommended) iManager can install the following products during installation: Tomcat 5. 5. 29 Sun JRE 1. 6. 0_20 Novell International Cryptographic Infrastructure (NICI) 2. 7. 3 Procedure For information about running iManager Server on the same machine as Novell eDirectory, see "Running eDirectory and iManager on the Same Machine (Windows only)" in the iManager 2. 7. 4 Administration Guide. 2 At the Novell download site (http://download. novell. com), search for iManager products, select iManager 2. 7, then download it to a directory on your server. [. . . ] 2 To update them, select the number in the Out-Of-Date column for the Collection you want to update. 3 Select the module you want to update, then click Update at the top of the table. NOTE: When updating to iManager 2. 7, or re-installing iManager 2. 7, existing plug-ins are not updated automatically. To update plug-ins manually, launch iManager and browse to Configure > Plug-in Installation > Available Novell Plug-in Modules. [. . . ]