HP Servicecontrol Manager 3.0 User’s Guide Edition 2.2 Manufacturing Part Number: 5990-8540 June 2004 United States © Copyright 2002-2004 Hewlett-Packard Development Company L.P.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Publication History The manual publication date and part number indicate its current edition. The publication date will change when a new edition is released. The manual part number will change when extensive changes are made. To ensure that you receive the new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details. • • • • HP Servicecontrol Manager 3.0 User’s Guide, 5990-8540 June 2004, Edition 2.2 HP Servicecontrol Manager 3.
Book Title Title of a book. On the Web and on the Instant Information CD, it may be a hot link to the book itself. Command Command name or qualified command phrase. ComputerOut Text displayed by the computer. Emphasis Text that is emphasized. Emphasis Text that is strongly emphasized. KeyCap Name of a keyboard key. Note that Return and Enter both refer to the same key. Term Defined use of an important word or phrase. UserInput Commands and other text that you type.
Contents 1. HP Servicecontrol Manager Introduction HP Servicecontrol Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 The Management Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Disable the Tomcat Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manage SCM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inspect the Audit Log Regularly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restrict root access on the CMS. . . . . . . . . . . . . . . . . . . . . .
1 HP Servicecontrol Manager Introduction This chapter introduces the basic concepts and functionality of the HP Servicecontrol Manager.
HP Servicecontrol Manager Introduction HP Servicecontrol Manager Overview HP Servicecontrol Manager Overview SCM is an easy-to-use, multi-system management solution with a Web-enabled interface and a command line interface. SCM delivers multi-system access to all key system administration tools for fault monitoring, configuration, and workload management. Administrators with multiple HP systems running primarily HP-UX or Linux benefit the most from using SCM.
HP Servicecontrol Manager Introduction HP Servicecontrol Manager Overview Chapter 1 Features Benefits Security– secure authentication between the managed node and the central management server (CMS), as well as between the CMS and the network client Increases confidence knowing that the transactions between the network client, the CMS, and the managed nodes are all authenticated and encrypted.
HP Servicecontrol Manager Introduction The Management Domain The Management Domain The management domain is a collection of resources that are placed under the control of the SCM. The dark-shaded area in Figure 1-1 represents a management domain. The individual resources are called managed nodes. One node in each management domain is the central management server (CMS). For more information about the CMS, see “Central Management Server” on page 11.
HP Servicecontrol Manager Introduction The Management Domain Nodes can belong to one or more node groups, but they do not have to belong to a node group. A node group cannot be a member of another node group, but all the nodes of a node group can be completely contained within another node group. In Figure 1-2, Node11 is in node groups B and C. Nodes 9 and 10 represent nodes that do not belong to a node group.
HP Servicecontrol Manager Introduction The Management Domain Network client SCM can be accessed from any network client. The network client can be part of the management domain, but it doesn’t have to be. Figure 1-3 represents the relationship between a network client, the CMS, and several managed nodes.
HP Servicecontrol Manager Introduction Users and Roles Users and Roles An SCM user can be anyone with a valid operating system login on the CMS. Once a user is added to SCM, then he can be authorized for roles on one or more nodes in the management domain. Figure 1-4 represents the relationship between users, roles, and nodes or node groups.
HP Servicecontrol Manager Introduction Users and Roles deleted from SCM. All other roles can be enabled, disabled, or deleted. If you don’t want a user to have access to all available tools for a specific node or node group, they should not be authorized for the master role on that node or node group. CAUTION A user assigned the master role on the CMS can execute commands as any user. Therefore, this user could grant trusted user privilege to himself.
HP Servicecontrol Manager Introduction Users and Roles Figure 1-5 Users and Trusted Users User Fred User Sue authorized for Operator Role: Operator Tool A authorized for Operator Tool C on Node Group A Node Node 1 2 on Node 3 Node Node 3 4 also authorized for Master Role Role: Master Role on Node 5 Node 5 All Tools Trusted User Chris Node Group A authorized for Web Admin Role: Web Admin Tool B on Node 6 Node 6 Tool D In Figure 1-5, the only difference between Chris, Sue, and Fred is tha
HP Servicecontrol Manager Introduction Tools Tools Tools are applications, commands, or scripts that are launched from within SCM. You can add custom tools into SCM and execute them across multiple systems simultaneously. Tool Types There are three types of tools supported in the SCM environment: Web tools, X Window tools, and command line tools. Web tools Web tools must reside on a Web server. The Web server can be running on the CMS or on a managed node.
HP Servicecontrol Manager Introduction Tools • Copying files to managed nodes The DTF connects the CMS to agent software running on each node in the cluster. This is shown in Figure 1-6. Figure 1-6 Distributed Task Facility Central Management Server Managed Node Commands Servicecontrol Manager Files Distributed Task Facility Files Results DTF Agent Daemon The DTF communicates to the agent daemon what tasks need to be performed on the node.
HP Servicecontrol Manager Introduction Information Storage Information Storage SCM uses an audit log and a database repository to track activity and store your management domain information. SCM Audit Log SCM logs all tasks performed by all SCM users on all nodes. The information is stored in the audit log on the CMS. Each managed node that has the DTF agent running also keeps a separate audit log that contains just the tasks performed on that node.
HP Servicecontrol Manager Introduction Security and Access Security and Access SCM utilizes several technologies to provide secure access and secure transactions. The security model is graphically represented in Figure 1-7. To simplify the image, each managed node in Figure 1-7 is only running one management application or protocol. Normally, managed nodes are running multiple management applications and protocols.
HP Servicecontrol Manager Introduction Security and Access Secure Transactions The security of the transaction depends on your networking environment and on the management application or protocol that each tool is using. Java Remote Method Invocation (RMI) Transactions The distributed task facility uses Java RMI to communicate with the DTF agents. Transactions are digitally signed using the public keys, which provides authentication protection but not encryption.
HP Servicecontrol Manager Introduction Security and Access SNMP Transactions SNMP Versions 1 and 2 are not secure protocols. Therefore, anyone with access to your network will be able to intercept and view SNMP transactions. SCM does not use SNMP SetRequests. By default, the supported operating system platforms have SNMP SetRequests disabled. For improved security, do not enable SNMP SetRequests on the CMS or on the managed nodes.
HP Servicecontrol Manager Introduction Security and Access SCM uses the following fixed ports on managed nodes, including the CMS: Service Port Protocol Used By Configurable? WBEM/ HTTP 5988 Inbound/Outbound TCP WBEM No WBEM/ HTTPS 5989 Inbound/Outbound TCP WBEM No RMI 2367 Inbound/Outbound TCP SCM Daemons No SNMP 161 Inbound/Outbound UDP SNMP No DCE RPC 135 Inbound (possibly others) TCP DMI No HTTP 2301 Inbound TCP ProLiant Web agent (Elm) No HTTPS 2381 Inbound TCP Pro
HP Servicecontrol Manager Introduction Security and Access If required, the maximum and minimum anonymous socket numbers can be set for HP-UX and Linux. • For HP-UX: ndd -set /dev/tcp tcp_smallest_anon_port min_port ndd -set /dev/tcp tcp_largest_anon_port max_port • For Linux: /sbin/sysctl -w net.ipv4.ip_local_port_range="min_port max_port" where min_port and max_port delimit the desired anonymous port number ranges. Note that changes by these commands do not persist across a reboot.
HP Servicecontrol Manager Introduction Security and Access 24 Chapter 1
2 Installing HP Servicecontrol Manager This chapter covers the following topics: Chapter 2 • “Installation Overview” on page 26 • “System Requirements” on page 28 • “Installing Servicecontrol Manager on HP-UX” on page 30 • “Installing Servicecontrol Manager on Linux” on page 33 • “Adding Managed Nodes” on page 37 • “Upgrading from Servicecontrol Manager 2.5 to 3.0” on page 41 • “Updating to Servicecontrol Manager 3.0 Version 3.00.
Installing HP Servicecontrol Manager Installation Overview Installation Overview Installing a management domain involves installing the central management server (CMS), installing the DTF and WBEM agent software on the managed nodes, and adding the managed nodes to the CMS. Figure 2-1 presents a flow diagram of the install process. Figure 2-1 SCM Install Process Accessing the software Servicecontrol Manager is available on the Web and with the HP-UX application releases.
Installing HP Servicecontrol Manager Installation Overview Estimated installation time Chapter 2 The time it takes to install an SCM management domain will depend on the performance and load of the target systems during the install process and on your familiarity with the execution process. It will also depend on the size of the management domain that you are installing.
Installing HP Servicecontrol Manager System Requirements System Requirements For the latest system requirements, go to: http://software.hp.com/products/SCMGR/ CMS requirements The table below identifies the hardware and software requirements for an SCM central management server (CMS). Operating System Software Computer Free Disk Space • HP-UX 11.0 • HP-UX 11i v1 (B.11.11) • HP-UX 11i v2 (B.11.23) • Red Hat Linux 7.2 Professional • Red Hat Linux 7.3 Professional • SuSE Linux 8.
Installing HP Servicecontrol Manager System Requirements Managed node requirements The table below identifies the hardware and software requirements for an SCM managed node. Operating System Network Client • HP-UX 11.0 • HP-UX 11i v1 (B.11.11) • HP-UX 11i v2 (B.11.23) • Red Hat Linux 7.2 Professional • Red Hat Linux 7.3 Professional • SuSE Linux 8.
Installing HP Servicecontrol Manager Installing Servicecontrol Manager on HP-UX Installing Servicecontrol Manager on HP-UX This section provides steps to successfully install the Servicecontrol Manager (SCM) central management server (CMS) on a server running a supported version of HP-UX. See “System Requirements” on page 28 to verify which versions of HP-UX are supported. If you are installing SCM on Linux, see “Installing Servicecontrol Manager on Linux” on page 33.
Installing HP Servicecontrol Manager Installing Servicecontrol Manager on HP-UX NOTE MySQL may have been installed from a tar file instead of an SD package. Look in /var and /opt to see if it is installed from a tar file. If the correct version of MySQL is already installed, you can skip installing it during the CMS software installation. If a different version is installed, you need to remove it before installing SCM. To remove MySQL: a. Uninstall the MySQL: swremove MySQL where MySQL is the bundle ID.
Installing HP Servicecontrol Manager Installing Servicecontrol Manager on HP-UX Step 3. Install Java SDK if version 1.4 or later isn’t installed on the system: swinstall -s server:directory T1456AA where server is the hostname of the depot server and directory is the location of the depot files on the depot server. Step 4. Install Tomcat if version 4.1.
Installing HP Servicecontrol Manager Installing Servicecontrol Manager on Linux Installing Servicecontrol Manager on Linux This section provides steps to successfully install the Servicecontrol Manager (SCM) central management server (CMS) on a server running a supported version of Linux. See “System Requirements” on page 28 to verify which versions of Linux are supported. If you are installing SCM on HP-UX, see “Installing Servicecontrol Manager on HP-UX” on page 30.
Installing HP Servicecontrol Manager Installing Servicecontrol Manager on Linux If the correct version of MySQL is already installed, you can skip installing it during the CMS software installation. If a different version is installed, you need to remove it before installing SCM. To remove MySQL: a. Identify the MySQL product names including MySQL, MySQL server, MySQL shared, and MySQL client: rpm -qa | grep mysql b.
Installing HP Servicecontrol Manager Installing Servicecontrol Manager on Linux SCM.3.0_RH.7.2_7.3_mxserver.bin • For SuSE Linux 8.0: SCM.3.0_SuSE.8.0_mxserver.bin Step 4. Initialize and configure the CMS: /opt/mx/bin/mxinitconfig -a server To manually install the CMS software on a Linux server: Step 1. Download the required bin files identified below to the local file system or copy them from a network location if they are already available. To download, go to: http://software.hp.
Installing HP Servicecontrol Manager Installing Servicecontrol Manager on Linux — mysql-server-3.23.49-3.i386.rpm — mysqlclient9-3.23.22-4.i386.rpm • For SuSE 8.0 only: — mysql-3.23.48-35.i386.rpm — mysql-shared-3.23.48-35.i386.rpm — mysql-client-3.23.48-35.i386.rpm • mxagent-B.03.00.04.i386-1.rpm • mxrepository-B.03.00.04.i386-1.rpm • mxcms-B.03.00.04.i386-1.rpm Step 6. Initialize and configure the CMS: /opt/mx/bin/mxinitconfig -a server Next Steps Servicecontrol Manager is now installed.
Installing HP Servicecontrol Manager Adding Managed Nodes Adding Managed Nodes This procedure walks you through adding managed nodes to a new management domain. Managed node systems must be running a supported version of HP-UX or Linux.
Installing HP Servicecontrol Manager Adding Managed Nodes To manually add managed nodes: Step 1. Log on to the CMS as root. Step 2. Verify the location of the SCM agent software. You located and/or downloaded this software at the same time that you located the CMS software during the CMS install process. Step 3.
Installing HP Servicecontrol Manager Adding Managed Nodes Step 8. Log on to one of the managed nodes as root. NOTE Step 8 to step 11 will need to be completed on each managed node separately. Step 9. Install the SCM DTF agent and WBEM software on the managed node: • For HP-UX (all versions): swinstall -s server:directory B8339BA.SysMgmtAgent B8465BA where server is the hostname of the depot server and directory is the location of the depot files on the depot server.
Installing HP Servicecontrol Manager Adding Managed Nodes where node1 node2 node3... is the list of hostnames or IP addresses for the nodes you added.
Installing HP Servicecontrol Manager Upgrading from Servicecontrol Manager 2.5 to 3.0 Upgrading from Servicecontrol Manager 2.5 to 3.0 The SCM upgrade will install the 3.0 version of SCM and migrate your SCM data to be compatible with SCM 3.0. The upgrade installation migrates all custom data including: • • • • • • users nodes node groups tools roles authorizations Multiple versions of SCM cannot coexist on the same system. NOTE You must be running SCM 2.5 to upgrade to 3.0.
Installing HP Servicecontrol Manager Upgrading from Servicecontrol Manager 2.5 to 3.0 mxtool -lf > /directory/mxtool.scm25 mxrole -lt > /directory/mxrole.scm25 where directory is a directory that won’t be deleted during the installation upgrade. Step 3. Install the software on the CMS by following the instructions in the section “Installing Servicecontrol Manager on HP-UX” on page 30. CAUTION When upgrading the CMS, do not install the SCM software with other products at the same time. Step 4.
Installing HP Servicecontrol Manager Upgrading from Servicecontrol Manager 2.5 to 3.0 Additional Suggested Removal and Clean-up Tasks There are several additional tasks you may want to perform to fully remove SCM 2.5 from your CMS system. Remove Netscape Directory Server (NDS) NDS provided the repository for SCM 2.5, and it is not removed during the upgrade in case you need to extract data from it after you upgrade. SCM 3.0 uses MySQL instead of NDS for the repository.
Installing HP Servicecontrol Manager Upgrading from Servicecontrol Manager 2.5 to 3.0 where Tool Name is the name of the new tool.
Installing HP Servicecontrol Manager Updating to Servicecontrol Manager 3.0 Version 3.00.04 Updating to Servicecontrol Manager 3.0 Version 3.00.04 Complete this procedure to update earlier versions of SCM 3.0 to version 3.00.04. To update to SCM 3.0 version 3.00.04: Step 1. Back-up your SCM data by copying the output of the mx commands into a file. mxnode -ln > /directory/mxnode.scm30 mxngroup -ln > /directory/mxngroup.scm30 mxauth -lf > /directory/mxauth.scm30 mxuser -lf > /directory/mxuser.
Installing HP Servicecontrol Manager Removing Servicecontrol Manager Removing Servicecontrol Manager You can either remove the SCM software or just remove the SCM configuration. CAUTION Removing the SCM software or removing the SCM configuration will delete all custom information in the SCM repository. You can also remove a managed node from a CMS’s management domain without removing the SCM agent on the node. To remove SCM including the repository data: Step 1.
3 Getting Started with SCM If this is your first time using HP Servicecontrol Manager (SCM), this chapter provides procedures to familiarize you with the SCM features using the graphical user interface and the command line interface.
Getting Started with SCM Types of SCM Users Types of SCM Users As an SCM user, you will be using it in at least one of the following capacities: • • using SCM to manage network resources administering SCM to enable other users to manage network resources Users who administer SCM must be assigned the trusted user privilege. The features and benefits of SCM will vary based on how you use it.
Getting Started with SCM Getting Started Using SCM Getting Started Using SCM Get started using SCM by familiarizing yourself with how to log on, select a node, and execute a tool. This procedure walks you through launching several different types of tools from the graphical user interface and the command line interface. This procedure is optional but recommended for new users. To get started using SCM: Step 1. Log on to the SCM graphical user interface. a.
Getting Started with SCM Getting Started Using SCM a. From the Tools tab menu, expand System Administration and select Accounts for Users and Groups. If this tool isn't available, your authorizations may not be associated with this tool, or the node selected isn't compatible with this tool. The tool launch page displays in the workspace. b. Open an X server or server emulator on the network client where you want to display the tool. c.
Getting Started with SCM Getting Started Using SCM Step 13. Execute the Accounts for Users and Groups tool on the same HP-UX target node that you selected in step 4. a. Type the command: mxexec -t "Accounts for Users and Groups" -n node where node is the hostname or IP address of the target node. b. View the results displayed on the screen. Step 14. Execute the View Properties tool on the same target node with WBEM installed that you selected in step 6. a.
Getting Started with SCM Getting Started Administering SCM Getting Started Administering SCM Get started administering SCM by familiarizing yourself with how to add a tool. To administer SCM, you must be a trusted user. This procedure walks you through adding a custom tool and executing the tool from the command line interface and the graphical user interface. To get started administering SCM: Step 1. Log on to the central management server (CMS) as a trusted user. Step 2.
Getting Started with SCM Getting Started Administering SCM b. Access the log on screen by navigating to: https://hostname:50000/ where hostname is the hostname of the CMS. c. Enter your User name and Password. d. Click Log On. Step 8. Select an HP-UX or Linux node with the DTF protocol. a. From the Nodes tab menu, select All Nodes to load the nodes list in the workspace. b. Select or clear the check boxes beside the nodes as necessary. The Tools tab menu replaces the Nodes tab menu after you select a node.
Getting Started with SCM Getting Started Administering SCM 54 Chapter 3
4 Increasing Servicecontrol Manager Security If you are in an environment where you need a higher level of security than what is provided by default with SCM, there are several things you can do to increase security.
Increasing Servicecontrol Manager Security Replace Self-Signed Tomcat Certificates Replace Self-Signed Tomcat Certificates Replacing the Tomcat self-signed certificate with a certificate authority signed (CA-signed) certificate on your CMS and your managed nodes will increase your security. You can purchase a CA-signed certificate from a third-party certificate authority, or you can act as your own certificate authority. This will increase SCM security if you are accessing SCM from a Web browser.
Increasing Servicecontrol Manager Security Replace Self-Signed Tomcat Certificates Step 6. Use the new certificates file created in step 5 to generate a request for the certificate authority: # keytool -certreq -alias tomcat –keystore \ /etc/opt/mx/config/security/certificates -keypass password \ -file mycert.csr where password is the MxKeystorePassword. The file mycert.csr will be created and will contain the command output. Step 7.
Increasing Servicecontrol Manager Security Enable WBEM Certificate Validation Enable WBEM Certificate Validation By default, all WBEM transactions are encrypted, but the identity of the managed node is not validated. Certificates passed from target nodes are automatically trusted. Enabling certificate validation will increase the level of security for WBEM transactions. You can use self-signed certificates for medium security or CA-signed certificates for high security.
Increasing Servicecontrol Manager Security Enable WBEM Certificate Validation • /etc/opt/mx/config/collectors/cimclient.properties Comment out the following line that sets the trust manager in each file. TrustManager=orig.snia.wbemcmd.xml.DontValidateCertificate Step 8. Restart SCM and Tomcat on the CMS: /opt/mx/bin/mxstop /opt/mx/bin/mxstart To enable WBEM certificate validation with CA-signed certificates: NOTE You must have a certificate server available on the network to use CA-signed certificates.
Increasing Servicecontrol Manager Security Enable WBEM Certificate Validation • /etc/opt/mx/config/collectors/cimclient.properties Comment out the following line that sets the trust manager in each file. TrustManager=orig.snia.wbemcmd.xml.DontValidateCertificate Step 13.
Increasing Servicecontrol Manager Security Encrypt Java RMI Transactions Encrypt Java RMI Transactions Java RMI transactions can be encrypted using the IP Security Protocol (IPSec) to increase security on RMI transactions. IPSec provides an infrastructure to allow secure communications including authentication, integrity, and confidentiality over IP-based networks between systems and devices that implement the IPSec family of protocol standards.
Increasing Servicecontrol Manager Security Disable the Tomcat Web Server Disable the Tomcat Web Server For increased security, the Web server on the CMS can be shut down when it is not needed. This will prevent it from responding to any Web-based requests. The SCM graphical user interface is dependent on the Web server. SCM operations can still be performed from the command line on the CMS when the Web server is shut down. To shut down the Web server: • For HP-UX: /sbin/init.
Increasing Servicecontrol Manager Security Manage SCM Software Manage SCM Software Inspect the Audit Log Regularly The SCM audit log contains a record of all tasks performed by SCM users on all managed nodes. This log should be inspected regularly for unexpected use of sensitive tools or for access to sensitive managed nodes. See administering SCM - audit log in the SCM online help for more information about the audit log.
Increasing Servicecontrol Manager Security Verify Security Dependencies Verify Security Dependencies Software Security Dependency SCM security is dependent on the security of the products and technologies described in this chapter. A threat to the security of these dependencies is a threat to the security of SCM. To minimize these threats, always apply the latest patches and updates available to combat known exploits.
Glossary agent See management agent authorization triplet A mapping of the authorization relationship between a user, a role, and a node or node group. A program interface that takes advantage of the computer's graphics capabilities to make the program easier to use. SCM's GUI is Web-enabled and displays in a Web browser. group See node group banner The section of the graphical user interface at the top of the screen that provides access to SCM help and other resources.
Glossary MySQL MySQL An open source relational SQL database software that is used by SCM for the repository. node Any device on the network that can communicate with SCM including servers, printers, workstations, hubs, and routers. Nodes must be added to an SCM management domain, and they can be assigned to one or more node groups by a trusted user. node group A group of nodes defined by a trusted user to divide a network into manageable units.
Glossary XML document X server A local application that accepts X client requests and acts upon them. X Window System A cross-platform windowing system that uses the client/server model to distribute services across a network. It enables applications or tools to run on a remote computer. XML See extensible markup language XML document A collection of data represented in XML.
Glossary X server 68 Glossary
Index A access, 49 administering SCM get started, 52 anonymous ports, 22 calculate CMS requirements, 22 set socket number range, 23 audit log, 8, 18, 48 configuration, 18 configure, 53 maintain, 53 view, 51 authorizations, 13, 14 add, 53 B browser supported versions, 29 C CA-signed certificates, 56, 58 central management server, 10, 11 HP-UX install, 30 Linux install, 33 ports, 21 requirements, 28 certificate authority, 19, 56 certificate server, 59 client see network client cluster see management domain CM
Index Mozilla supported version, 29 multi-system management, 8 MxConfigPassword, 63 MxDBUserPassword, 63 MxKeystorePassword, 56, 58, 59, 63 MySQL, 11, 18 N navigating SCM, 51 Netscape supported version, 29 Netscape Directory Server, 43 network client, 12, 48 requirements, 29 node groups, 10 add, 53 delete, 53 nodes, 10 add, 53 delete, 53 select, 49 view properties, 51 nodes list customize, 51 O operating systems supported versions, 28, 29 P password DBAdminPassword, 63 generated at install, 63 MxConfigPassw
Index TDEF file see XML tool definition file telnet, 19 Tomcat, 56 restart, 59, 60 security, 20 tools, 16, 43 add, 52, 53 command line tools, 16 default authorizations, 13 delete, 53 execute, 49, 52 types, 16 Web tools, 16 X Window tools, 16 trusted user, 14, 48, 52, 63 U update, 45 upgrade, 41 additional clean-up tasks, 43 agent compatibility, 41 manually convert tools, 43 remove Netscape Directory Server, 43 requirements, 41 user interfaces, 8, 48 users, 13 add, 53 delete, 53 types of, 48 uses for SCM, 48
