CONTROL-M Installation Guide

CONTROL-MInstallation Guide Supporting Version 6.4.01 of CONTROL-M/Enterprise Manager Version 6.4.01 of CONTROL-M/Server for UNIX® and Microsoft Windows Version 6.4.01 of CONTROL-M/Agent for UNIX® and Microsoft Windows September 2008 www.bmc.com Contacting BMC Software You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities. United States and Canada Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax (01) 713 918 8000 Fax 713 918 8000 Outside United States and Canada Telephone (01) 713 918 8800 © Copyright 2008 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. IT Infrastructure Library® is a registered trademark of the Office of Government Commerce and is used here by BMC Software, Inc., under license from and with the permission of OGC. ITIL® is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office, and is used here by BMC Software, Inc., under license from and with the permission of OGC. Linux is the registered trademark of Linus Torvalds. Oracle is a registered trademark of Oracle Corporation. UNIX is the registered trademark of The Open Group in the US and other countries. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation. Restricted rights legend U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address. Customer support You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see “Before contacting BMC.” Support website You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can ■ ■ ■ ■ ■ ■ ■ ■ read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation download products and maintenance report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers Support by telephone or e-mail In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to [email protected]. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance. Before contacting BMC Have the following information available so that Customer Support can begin working on your issue immediately: ■ product information — — — ■ product name product version (release number) license number and password (trial or permanent) operating system and environment information — — — — — machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level ■ sequence of events leading to the issue ■ commands and options that you used ■ messages received (and the time and date that you received them) — — — product error messages messages from the operating system, such as file system full messages from related software 3 License key and password information If you have questions about your license key or password, contact BMC as follows: ■ (USA or Canada) Contact the Order Services Password Team at 800 841 2031, or send an e-mail message to [email protected]. ■ (Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send an e-mail message to [email protected]. ■ (Asia-Pacific) Contact your BMC sales representative or your local BMC office. 4 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . . . . CONTROL-M/Agents and remote hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Server . . . . East Asian (CJK) language considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for CONTROL-M/Agent installation on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents About this book 15 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents 47 48 48 49 49 53 54 55 5 . . . . . . . . . CONTROL-M/Enterprise Manager . . . . . . . . . . 16 16 17 17 Chapter 1 19 Introducing the CONTROL-M solution CONTROL-M architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows requirements . Database installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation requirements for CONTROL-M/EM and CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support . . . . . . Installing CONTROL-M/EM server components . . . . . . . . . . . . . . . . . . . UNIX requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for CONTROL-M/Agent installation on Windows . . . . . . . . . . . . . . . . . Installation requirements for CONTROL-M/Agent. . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM server and client components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM on Windows . . . CONTROL-M Control Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database server options . . . . . . . . . . . 23 31 32 32 35 35 40 42 43 43 44 45 Chapter 3 47 Installing CONTROL-M/EM Overview . . . . . . . . . Migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 21 21 21 22 22 Chapter 2 23 Planning the CONTROL-M solution Using the CONTROL-M installation roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ensuring Oracle Availability on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other database options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Installing CONTROL-M/Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Setting the protocol version for the upgraded CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . 84 Chapter 6 Post installation for CONTROL-M/Server 87 Modifying the automatic startup procedure for CONTROL-M/Server (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Importing WIN panel functionality (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Installation parameters . . . . . 100 6 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Chapter 4 Post installation for CONTROL-M/EM 67 Starting up the CONTROL-M system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . 72 Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Checking Java software . . . 62 Multiple instances of CONTROL-M/EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Setting startup options for CONTROL-M/EM services on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Where to go from here. . 69 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Interactive installation or upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . 76 Installing CONTROL-M/Server on Windows . . . . . . . . . . . 82 Silent installation . . . . . 70 Chapter 5 Installing CONTROL-M/Server 71 Installation database server options . 98 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . 82 Where to go from here. . . . . . . . . . . . . 68 Component communication for UNIX . . . . . . . 89 Using NFS with CONTROL-M/Server (UNIX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Using CONTROL-M/EM Web Launch . . . 64 Installing multiple database clients considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Silent installation or upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Interactive installation or upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Persistent connection between CONTROL-M/Server and CONTROL-M/Agent. . . . . . . . 90 Chapter 7 Installing CONTROL-M/Agent 91 Installing CONTROL-M/Agent on UNIX . . . . . . . . . . 64 Naming multiple instances. . . . . . . . . . . . . . . . . . . . . . . . . . 95 Installing CONTROL-M/Agent on Windows . . . . . . . . . . . . . . . . . . . . . . . . . 89 Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows) . . . . . . . 95 Silent installation . . . . . . . . . . . . . 73 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the test data . . . . . . . . . . . . . Performing a silent installation . . . . . . . . . . . . . . . . . . . . .Chapter 8 Post installation for CONTROL-M/Agent 101 Setting CONTROL-M/Agent file permissions for NFS (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Installing a dedicated database server . Modifying the automatic startup procedure for CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Where to go from here. . . . . . . . . . . . Where to go from here . . . . . . . . 127 Cleaning up after an existing installation . . . . . . . . . . . . . . . . . . . Installing a CONTROL-M/EM tablespace using an on-site Oracle client . . . . . . . . . . . . . . . . . . . . 115 Installing a tablespace using an on-site Oracle client . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 106 107 108 Appendix A 111 Installing an Oracle database on UNIX Preparing for installation . . . . . . . 113 Installing a database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Checking the installation log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents 130 131 131 131 133 134 135 136 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Oracle installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from CONTROL-M/Agent version 6. . . . . . . . . . . . . . . . . . . . . . 127 Appendix B Installing an Oracle database on Windows 129 Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating and running a job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Cleaning up after a dedicated installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade with CONTROL-M Option for Oracle Applications installed . . . . . . . . 102 102 103 103 103 104 104 Chapter 9 105 Running your first job 101 Testing the new installation . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Performing a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Running the Oracle pre-installation script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Setting Oracle installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring the job . . . . . . . . . . 117 Where to go from here . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Installing an Oracle client using an on-site Oracle client (for CONTROL-M/EM only) 119 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Installing an Oracle client (for CONTROL-M/EM only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Installing on an existing database server . 121 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changes to system files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here. . . . . . . . . . . . 127 Performing post-installation cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Cleaning up a failed Oracle installation . . . . . .1 or earlier. . . . . . . . . . . . . . . . Upgrade with CONTROL-M Option for PeopleSoft installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0. . . . . . . . . . . . . . . . . . . . . . . . . 178 Installing BMC Batch Impact Manager on clusters. . . . . . . . . . . . . . . . . . 175 Setting up failover nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Creating cluster resources for Windows . . . . . . . . . . . . . . 148 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Setting up the CONTROL-M/EM Windows cluster environment. . . 152 Database pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . 179 Installing CONTROL-M/Forecast on clusters. . . . . . . . . . 180 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Appendix C Installing a CONTROL-M database with Sybase on UNIX 141 Interactive installation of the CONTROL-M database . . . . . . . 144 Appendix D Preparing clusters for database components 147 Preparing the database for UNIX . . . 174 Cluster administration mode . . . . . . 158 Cluster administration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Set up the host and listener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Create CONTROL-M/EM Gateway cluster resource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Setting up the CONTROL-M/Server Windows cluster environment for PostgreSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Database pre-installation . . . . . . . . . . . . . . . . . . 144 Installation parameters . . . . . 181 Appendix F Configuring CONTROL-M/Server clusters 183 Setting up the CONTROL-M/Server UNIX cluster environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Where to go from here. . . . . . . . . . 183 Configuring the policy file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Updating BMC Batch Impact Manager and CONTROL-M/Forecast cluster resources . . 176 Installing CONTROL-M/EM client components . . . . . . . . . . . . . . 142 Silent installation of the CONTROL-M database. . . . . . . . . . 159 Installing the CONTROL-M/EM client components on Windows . . . . . . . . . . . . . . . . . . . . . . 155 Appendix E Configuring CONTROL-M/EM clusters 157 Setting up the CONTROL-M/EM UNIX cluster environment . . . . . . 150 Creating cluster resources for UNIX . . . . . . . . . . . . . . . . . . 149 Database post-installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 CONTROL-M Configuration Manager administration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Monitoring CONTROL-M/Server processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Where to go from here. . . . . . . . . . . . . . . . . 185 8 CONTROL-M Installation Guide . . 152 Preparing the database for Windows . . . . . . . . . . . 154 Where to go from here. . . . . . . . . .Cleaning up a failed existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Setting the virtual host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Setting up failover nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 200 200 200 201 201 201 Appendix J 203 Uninstalling CONTROL-M and database servers Uninstalling CONTROL-M/EM from UNIX. . . . . . Solaris 8. . . . . . . . . . . . . . . . . . . . . . . Unmounting media devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All platforms . . . . . . . . . . . . AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling a CONTROL-M Oracle database server from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/EM from Windows . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Agent from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying system parameters . . . . . . . . . . . . . . . . . . . 204 205 205 206 206 207 208 208 Index 209 Contents 9 . . Where to go from here. . . . . Uninstalling CONTROL-M/Server from Windows . . . . . . . . . . 9 (for CONTROL-M/EM and CONTROL-M/Server) . . . . . . . . Uninstalling CONTROL-M/Server from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solaris 10 (for CONTROL-M/Server). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling a CONTROL-M Oracle database server from Windows. . . . . . . . . . . . . . . . . 188 Appendix H Checking and modifying UNIX parameters 189 Checking memory . . . . . . . . 190 190 190 191 193 194 195 196 198 Appendix I 199 Mounting DVDs and CDs on UNIX computers Mounting media devices. . . . . . . . . . . . . . . . . . . 187 Updating CONTROL-M/Agent system path information on cluster installations 188 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Appendix G Configuring CONTROL-M/Agent clusters 187 Considerations for a Microsoft Windows cluster environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Agent from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 CONTROL-M Installation Guide . . . . . . . . . . . CONTROL-M/Server installation on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Server installation on Windows . . . . . . . . . . . .Figures CONTROL-M scheduling solution for distributed systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/EM installation on UNIX continued . . . . . . . . . . . . . . . . . . . . CONTROL-M/EM installation on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figures 20 24 25 26 27 28 29 30 11 . . . . . . . . . . . . . . . . . . CONTROL-M/EM installation on Windows continued . . . . . . . . . . . . . CONTROL-M/EM installation on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full CONTROL-M installation roadmap . . . . . . . . . . . . . . . . . . 12 CONTROL-M Installation Guide . 195 Kernel parameters – Solaris with Oracle . . . . . . 190 Kernel parameters for CONTROL-M/Server – additional values . . . . . . . . . . . . . . . . . . . . . . . 130 Oracle Database – Windows installation parameters . . . . . . . . 176 Checking available memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 CONTROL-M/Server – UNIX database and application installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and CONTROLM/Agent . . . . . . . . . . . . . . 33 Installation resource requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 92 CONTROL-M/Agent – Installation parameters . . . . . . . . . . . . . . . . . . . . 108 Oracle installation types . . . . 84 Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . 96 Silent installation parameters . . . . . 155 Oracle processes . . . . . . . . . . . . . . . . . . . 77 CONTROL-M/Server – Windows database and application parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Kernel parameters for CONTROL-M – values for all platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Server. . . . . . . 113 Oracle Database – UNIX installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 CONTROL-M/EM services . 31 Alternative database servers . . . . . . . . . . . . . . . . . . . . . . . . 144 Windows cluster parameters . . . . . . . 175 CONTROL-M/EM Gateway resource definition . . . . 123 Oracle installation options . . . . . . . . . . . . 33 Database server configuration . . . . . . . . . . . . . . . . . . . . . . . 43 UNIX and Windows interactive and silent installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . 194 Kernel parameters – Solaris with Embedded PostgreSQL . . . . . . . . . . . . . 130 Installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Kernel parameters for CONTROL-M – HP-UX with Embedded PostgreSQL . . . . . . . . . . . . . . . . . . . .CONTROL-M/Agent on UNIX . . . . . . . . . . . . . 192 Kernel parameters for CONTROL-M/EM – HP-UX with Sybase . . . . . . . . . . . . . . . . . . . . . . . . 164 Defining a cluster resource . . . . . . . . . . . . . . . . . . . . . .for interactive installations only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Job status colors indicated by the color of a node’s title bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Installation steps . . . . . . . 164 CONTROL-M/EM processes . . . . . . . . . . 136 UNIX interactive and silent installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Windows requirements for CONTROL-M/EM and CONTROL-M/Server . . . . . 40 Minimum system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Asynchronous I/O parameters – AIX . . . . . . . . . . . . . . . . . . . . . . 193 Kernel parameters for CONTROL-M/Server – HP-UX with Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Tables 13 . . . . . . . . . . . . . . . . . . . . . . 191 Kernel parameters for CONTROL-M – HP-UX with Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Limits for CONTROL-M/EM or CONTROL-M/Server Accounts on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Kernel parameter requirement for CONTROL-M/Agent . . . . . . . . . . . . 35 UNIX requirements for CONTROL-M . . . . . . . . . . .Tables Installation checklist for CONTROL-M/EM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Displaying kernel parameter values – Linux with Oracle and Sybase . . . 196 Kernel parameters– Linux with Oracle and Sybase . . . . . . . . . . . . . . . . . . . . . . 196 Kernel parameters – Linux with Embedded PostgreSQL . . . . .Kernel parameters – Solaris with Sybase . . . . . . . . . . . . . . 197 14 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . com. To request additional printed books or to view online books and notices (such as release notes and technical bulletins).01 of the CONTROL-M (CONTROLM/EM.com/support_home. To access Help. To view.bmc. CONTROL-M/Server. Like most BMC documentation.About this book This book describes how to install version 6. About this book 15 .adobe. CONTROL-M/Agent) product.4. or copy PDF books. NOTE Online books are formatted as PDF or HTML files. Some product shipments also include the online books on a documentation CD. print. you can obtain the reader at http://www. use the free Adobe Reader from Adobe Systems. this book is available in printed and online formats. The software also offers online Help. If your product installation does not install the reader. press F1 within any product or click the Help button in graphical user interfaces (GUIs). see the Customer Support website at http://www. predict completion schedules. and literal examples are presented in this typeface. Actions => Create Test instructs you to choose the Create Test command from the Actions menu. facilities. operating system terms. system messages. or syntax is displayed in italic text: testsys/instance/fileName ■ 16 The symbol => connects items in a menu sequence. monitor services. Conventions This book uses the following special conventions: ■ All syntax. For example. ■ Variable text in path names. monitor and maintain the full CONTROL-M environment. and operating instructions ■ A guide to the CONTROL-M production control system in a mainframe environment. CONTROL-M Installation Guide .Related publications Related publications The following related publications are related to CONTROL-M: Category Document User Guides Reference Guides Administrator Guides ■ CONTROL-M User Guide ■ CONTROL-M for z/OS User Guide ■ CONTROL-M Business Service Management Solutions User Guide ■ CONTROL-M Parameter Guide ■ CONTROL-M Utility Guide CONTROL-M Administrator Guide Description ■ CONTROL-M/M concepts. and populate batch services ■ syntax and usage for all parameters and variable that are included in CONTROL-M job processing definitions ■ command-line utilities that can be used to perform various CONTROL-M tasks in batch defines tasks that the CONTROL-M administrator must perform to define. ■ how to define and manage CONTROL-M job processing definitions. features. -level] (UNIX) UNLOAD device={disk | tape. You must use a comma to separate the options if you choose more than one option. About this book 17 .. If a variable is represented by two or more words. columnName. you would choose either commit or cancel. . columnName . In the example. [tableName.. field] Braces indicate that at least one of the enclosed items is required. {commit | cancel} An ellipsis indicates that you can repeat the previous item or items as many times as necessary.Syntax statements Syntax statements The following example shows a sample syntax statement: COMMAND KEYWORD1 [KEYWORD2 | KEYWORD3] KEYWORD4={YES | NO} fileName. Do not type the brackets when you enter the option. Do not type the braces when you enter the item. {-commit | -cancel} (UNIX) Support In addition to release notes that accompany this product. {DBDName | tableName} databaseDirectory serverHostName [-full. up-to-date. The following table explains conventions for syntax statements and provides examples: Item Example Items in italic type represent variables that you must replace with a name or value. initial capitals distinguish the second and subsequent words. installation and service information that becomes available after this product is shipped will be placed on the BMC Software Customer Support Web site at: http://www. A comma means that you can choose one or more of the listed options. alias Brackets indicate a group of optional items.com/support_home BMC Software recommends that you access this location before you install this product.bmc. . -incremental. essential. fileName | deviceName} {-a | -c} (UNIX) A vertical bar means that you can choose only one of the listed items. Support 18 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . After you provide CONTROL-M with scheduling and processing instructions for each job. . . . . . . . 19 21 21 21 22 22 CONTROL-M architecture CONTROL-M is a unified. . . . . . . . . . . . . . . . . . . Figure 1 illustrates the CONTROL-M solution and how each component fits into it. . . . . . . . . . . . . . . . . . . CONTROL-M executes batch jobs such as scripts or programs. . . . . . . . . . CONTROL-M/Server . . . . . . . . such as an ABAP program in the SAP® application. . . . . . . .Chapter 1 1 Introducing the CONTROL-M solution This following topics are discussed in this chapter: CONTROL-M architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration considerations . . . . . . . . that can be executed either at the operating-system level or under a packaged external application. . Chapter 1 Introducing the CONTROL-M solution 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Enterprise Manager . . . . . CONTROL-M Control Modules . . . . . . . . . . . . . . . . . . . . CONTROL-M/Agents and remote hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . dynamic system that offers a comprehensive solution to production control requirements for batch processing. . . . the jobs are able to run. enterprise-wide. . . . . . . . . . . . . . CONTROL-M architecture Figure 1 CONTROL-M scheduling solution for distributed systems The remainder of this section describes the major components that comprise the CONTROL-M solution. For detailed information about the full CONTROL-M solution, see the CONTROL-M Concepts Guide. 20 CONTROL-M Installation Guide CONTROL-M/Enterprise Manager CONTROL-M/Enterprise Manager CONTROL-M/Enterprise Manager (CONTROL-M/EM) is a collection of client-server components that control and manage your production jobs. CONTROL-M/EM provides a single, centralized point of access and control that allows you to view, monitor, manage, and intervene in batch flow processing across the entire enterprise. The product’s graphical user interface (GUI) provides the main interface to your real-time batch environment. CONTROL-M/Server CONTROL-M/Server is the scheduling engine that handles job scheduling and processing needs that can be used in the CONTROL-M environment. Several instances of CONTROL-M/Server can installed in a CONTROL-M environment. Each CONTROL-M/Server is responsible for scheduling individual jobs, managing job processing flows, and notifying CONTROL-M/EM of job statuses. CONTROL-M/Agents and remote hosts CONTROL-M/Agent handles job execution and many can be used in the CONTROL-M environment. As the name implies, CONTROL-M/Agents are agents of CONTROL-M/Server. A CONTROL-M/Agent submits jobs on behalf of its requesting CONTROL-M/Server, tracks the job processing, and returns status information back to the CONTROL-M/Server. Though CONTROL-M/Servers are responsible for job scheduling and processing, they do not have to limit their activity to the computer on which they reside; they can schedule jobs on other computers that come under their control. CONTROL-M/Agents are commonly used to place computers under the control of a CONTROL-M/Server. CONTROL-M/Agents submit jobs on behalf of the CONTROL-M/Server, track the jobs’ processing, and provide status information back to the CONTROL-M/Server. As an alternative to having a dedicated CONTROL-M/Agent installed, CONTROL-M jobs can be submitted to remote hosts without having CONTROL-M/Agents installed on the remote host machines. If you use the remote host feature, you may decide not to install separate CONTROL-M Agents. For details about remote hosts and when to use them, see the CONTROL-M Concepts Guide and the CONTROL-M Administrator Guide. Chapter 1 Introducing the CONTROL-M solution 21 CONTROL-M Control Modules NOTE The version of CONTROL-M/EM being installed must be the same or higher than the versions of CONTROL-M/Server and CONTROL-M/Agent. CONTROL-M Control Modules CONTROL-M Control Modules (CMs) enable CONTROL-M/Agents to interface with external applications (for example SAP and Oracle Applications), bringing CONTROL-M functionality to your external, packaged application environment. For more information about installation of CONTROL-M Control Modules, see the CONTROL-M Module guide for the specific platforms. Migration considerations Migration is the process of moving data and configuration settings from earlier installations of CONTROL-M/EM and CONTROL-M/Server to newer versions of the product. The Migration Toolkit utility automates most of the migration steps. The Migration Toolkit exports the previous version database to a temporary location and imports it into the new version. During the import process, data is adjusted as necessary to conform to enhancements in the new version. CONTROL-M/EM and CONTROL-M/Server are migrated as separate processes. For more information about migration and the Migration Toolkit, see: 22 ■ CONTROL-M /Enterprise Manager Migration Guide from the BMC Software Customer Support Web site (http://www.bmc.com/support_home), solution SLN000015053002. ■ CONTROL-M/Server Migration Guide from the BMC Software Customer Support Web site (http://www.bmc.com/support_home), solution SLN000015061431. CONTROL-M Installation Guide Chapter 2 2 Planning the CONTROL-M solution This chapter describes planning for CONTROL-M version 6.4.01. This following topics are discussed in this chapter: Using the CONTROL-M installation roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other database options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation requirements for CONTROL-M/EM and CONTROL-M/Server . . . . . . UNIX requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation requirements for CONTROL-M/Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for CONTROL-M/Agent installation on UNIX . . . . . . . . . . . . . . . . . . . Preparing for CONTROL-M/Agent installation on Windows . . . . . . . . . . . . . . . East Asian (CJK) language considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 31 32 32 35 35 40 42 43 43 44 45 Using the CONTROL-M installation roadmap You can use the flowcharts in Figure 3 through Figure 8 to identify the CONTROL-M products that will be installed on your system. The flow diagrams can help you easily choose the type of installation you require and guide you to the relevant instructions. To use the roadmap, start with Figure 2, use subsequent (Figure 3 through Figure 8) flow diagrams to select the CONTROL-M installation that you require. Click on the corresponding links to go to the information for each installation type. After reading the information, can link back to the correct flow diagram. Chapter 2 Planning the CONTROL-M solution 23 Using the CONTROL-M installation roadmap Figure 2 Full CONTROL-M installation roadmap page 48 page 53 page 72 page 80 page 91 24 CONTROL-M Installation Guide page 95 . Using the CONTROL-M installation roadmap Figure 3 CONTROL-M/EM installation on UNIX page 31 page 113 page 113 page 48 page 48 Chapter 2 Planning the CONTROL-M solution 25 . Using the CONTROL-M installation roadmap Figure 4 CONTROL-M/EM installation on UNIX continued page 55 page 131 page 55 page 67 page 67 26 CONTROL-M Installation Guide . Using the CONTROL-M installation roadmap Figure 5 CONTROL-M/EM installation on Windows page 31 page 53 page 55 page 67 Chapter 2 Planning the CONTROL-M solution 27 . Using the CONTROL-M installation roadmap Figure 6 CONTROL-M/EM installation on Windows continued page 129 page 131 page 53 page 55 page 131 page 67 28 CONTROL-M Installation Guide . Using the CONTROL-M installation roadmap Figure 7 CONTROL-M/Server installation on UNIX page 31 page 72 page 113 page 113 page 72 page 87 Chapter 2 Planning the CONTROL-M solution 29 . Using the CONTROL-M installation roadmap Figure 8 CONTROL-M/Server installation on Windows page 31 page 80 page 87 30 CONTROL-M Installation Guide . See the release notes 6 Perform pre-installation checks For UNIX. CONTROL-M/Agent 2 Install database components. CONTROL-M/Server. Chapter 5. ■ For Asian language considerations. see “UNIX requirements” on page 35 Note: A pre-installation check is provided For Windows. see “Windows for UNIX installations requirements” on page 40 7 8 (Optional) Review migration and East Asian language considerations Install the product ■ For migration. Table 3 4 Ensure that you have all the resources necessary for the installation “Installation requirements for CONTROL-M/EM and CONTROL-M/Server” on page 35 5 Identify the installation DVD for the product and platform. ■ BMC Software Embedded PostgreSQL (default) ■ For a non-default installation. Table 1 Installation checklist for CONTROL-M/EM. CONTROL-M/Server. see “East Asian (CJK) language considerations” on page 45 Chapter 3. see “Migration considerations” on page 22.Using the Installation checklist Using the Installation checklist The installation checklist in Table 1 shows the major steps required to complete the installation of the full CONTROL-M solution. Table 2 3 Select a database server. identify the CONTROL-M products that will be installed on your system as part of the overall solution for example. You should review the installation checklists for CONTROL-M/EM. Chapter 7 Chapter 2 Planning the CONTROL-M solution 31 . CONTROL-M/Server. and CONTROL-M/Agent for the products you want to install. install the necessary database components. and CONTROL-M/Agent (Part 1 of 2) Check Step Task Where to go 1 Figure 2 If you have not yet done so. CONTROL-M/EM. Other database options Depending on the specific database requirements at your site. 32 CONTROL-M Installation Guide . Database installation options The recommended option is CONTROL-M installed on a dedicated Embedded PostgreSQL database server supplied by BMC Software. Download both from BMC Software Customer Support Web site (http://www. Sybase.Database installation options Table 1 Installation checklist for CONTROL-M/EM. Chapter 6. see the CONTROL-M/Server Migration Guide and Migration Toolkit. or MSSQL third-party database servers A dedicated installation refers to installation of a database server and client supplied by BMC Software (Embedded PostgreSQL and Oracle only). NOTE For the PostgreSQL existing installation option. Chapter 8 10 Migrate data from previous version (optional) see the CONTROL-M /Enterprise Manager Migration Guide and Migration Toolkit. CONTROL-M can also be installed on the following alternative database servers: ■ an Oracle database server supplied by BMC Software ■ Oracle. CONTROL-M/Server. and CONTROL-M/Agent (continued) (Part 2 of 2) Check Step Task Where to go 9 Perform post-installation procedures Chapter 4. database server already on site. or a BMC supplied. An existing installation refers to installation of a database client that connects it to a customer owned.bmc.com/support_ home) solution SLN000015053002. use only an existing installation supplied by BMC Software. The device folder must be empty in order to proceed with the installation. x Version 10.x Windows with Server Supplied Supported Supplied Version 10.1.2.x Version 11.5.1.5.x Version 15.0.x Version 11.1. ■ You must install an Oracle client on each account that hosts a full CONTROL-M/EM or CONTROL-M/Server installation. Table 2 Alternative database servers UNIX with EM or Server Database Component Supported Supplied Windows with EM Supported Oracle server & client Version 10. N/A MSSQL client N/A Version 2005 N/A Version 2005 N/A Table 3 provides supported configurations for all database servers.3 Version Version 10.x Version 12. ■ Chapter 2 Planning the CONTROL-M solution 33 .x Version 15.5.x Version 10.2.0.0. ■ For CONTROL-M/EM on Windows only You must install an Oracle client on each account that hosts a CONTROL-M/EM client that includes the Reporting Facility.4 and in Sybase 15 below version 15. Table 3 Database server configuration (Part 1 of 2) Database Type Specifications Dedicated BMC Remote (existing) Embedded PostgreSQL (UNIX and Window) ■ Oracle (UNIX and Window) ■ A BMC-supplied Oracle database server or an existing Oracle full enterprise edition database server must be present.0.Other database options Table 2 provides information about alternative database servers.0.0.x 10.2. You can not use Oracle Standard edition servers.3 N/A N/A N/A N/A N/A Note: a false “database is full” alarm can occur in Sybase 12 below version 12.x Sybase client N/A Version 12.2.0. MSSQL is not provided by BMC Software. ■ An MSSQL based installation must always be performed using an existing English language MSSQL database server version 2005. ■ In addition to the database server. . MSSQL clients must be installed on any computer that hosts CONTROL-M/EM or CONTROL-M/Server. ■ Database client version 15. ■ The Sybase database server and client is not part of the installation package and must exist at your site before you install CONTROL-M.Other database options Table 3 Database server configuration (Part 2 of 2) Database Type Sybase (UNIX and Window) Specifications ■ You must use an existing Sybase database server with 8-KB paging with the following minimum parameter values: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ MSSQL (Windows only) 34 CONTROL-M Installation Guide max memory: 375000 procedure cache: 90000 number of user connections: 200 additional network memory: 49152 max network packet size: 8192 number of devices: 40 number of index trips: 4 number of large i/o buffers: 8 number of oam trips: 4 number of open objects: 6000 number of open indexes: 7500 number of pre-allocated extent: 4 number of locks: 40000 user log cache: 8192 tcp no delay: 1 deadlock checking period: 1000 housekeeper free write percent: 10 runnable process search count: 2000 recovery interval in minutes: 10 Allocate max shared memory: 1 Dynamic allocation on demand: 1 ■ The database server and client character sets must be the same and should be set to either iso_1 or utf8.0 requires the following command to create the libraries name: $SYBASE/OCS-15_0/scripts/lnsyblibs create ■ A Sybase client must be installed separately on each computer that hosts CONTROL-M/EM or CONTROL-M/Server. you do not need to install the MSSQL Client. ■ If you install CONTROL-M/EM or CONTROL-M/Server on a computer with an existing MSSQL server. Installation requirements for CONTROL-M/EM and CONTROL-M/Server Installation requirements for CONTROL-M/EM and CONTROL-M/Server Ensure that the resources listed in Table 4 are available before installing CONTROL-M/EM or CONTROL-M/Server. Operating system and database compatibility information is listed at: http://www.cfm.bmc.sh scripts Administrator privileges N/A N/A ■ Installing CONTROL-M UNIX requirements Before beginning the installation perform the following steps: ■ Ensure that your operating system and database software is compatible with the current version of CONTROL-M.sh script (Oracle only) Running the orapreinst. Chapter 2 Planning the CONTROL-M solution 35 . and disk space meet the minimum requirements for CONTROL-M/EM and CONTROL-M/Server as described in Table 5. See “Verifying operating system levels and patches” on page 38 ■ Ensure that your hardware. Table 4 Installation resource requirements Resource UNIX Windows Database administrator ■ Administrator passwords for existing database servers CONTROL-M/EM or CONTROL-M/Server database owner ■ You are prompted to provide a database owner user name You are prompted to provide a database owner password. memory.com/supportu/PAC_utility/index. ■ Ensure that operating system levels and patches are up-to-date. System administrator root user privileges ■ ■ ■ ■ ■ ■ ■ Mounting the DVD drive Defining user accounts Modifying system (kernel) parameters Granting authorization to necessary directories Running the check_req. ■ Consult the CONTROL-M Language Customization Guide to adjust locale settings to your UNIX platform.sh and orapostinst. Table 5 UNIX requirements for CONTROL-M (Part 1 of 2) Resource Specification Requirement Hardware AIX IBM RISC System/6000 HP-UX PA (RISC) or IA (Itanium). ■ If you are installing CONTROL-M/EM or CONTROL-M/Server on a BMC-supplied database server (dedicated Embedded PostgreSQL or dedicated Oracle). Solaris Sun SPARCstation Linux Intel Pentium 32 bit All systems DVD drive CONTROL-M/EM server components or CONTROL-M/Server with Embedded PostgreSQL 1 GB CONTROL-M/EM server components or CONTROL-M/Server without Embedded PostgreSQL 700 MB Memory Oracle Server ■ ■ ■ 36 CONTROL-M Installation Guide Small: 500 MB Medium: 1GB Large: 1. create the CONTROL-M/EM or CONTROL-M/Server UNIX user account as specified under “Preparing a CONTROL-M/EM or CONTROL-M/Server account on UNIX” on page 38.UNIX requirements ■ Modify UNIX system parameters as indicated in “Modifying system parameters” on page 190.5 GB . UNIX requirements Table 5 UNIX requirements for CONTROL-M (Part 2 of 2) Resource Specification Requirement CONTROL-M/EM server components or BMC recommends CONTROL-M/Server with Embedded PostgreSQL reserving three times the amount CONTROL-M/EM server of RAM in the components without system for swap Embedded PostgreSQL space. Setting environment variables in UNIX ■ Users of csh and tcsh should use the following syntax: setenv <envVar> <value> EXAMPLE setenv BMC_HOST_INSTALL myhost ■ Users of sh. CONTROL-M/Server without Embedded PostgreSQL Diskspace 1 GB for a new installation 300 MB for a new installation 700 MB for a new installation Oracle Server (dedicated) 7 GB Oracle /tmp directory (dedicated) 400 MB CONTROL-M/EM or CONTROL-M/Server database (tablespace) All database servers except Sybase: Sybase database server: ■ ■ ■ ■ Small: 3 GB Medium: 5 GB Large: 8 GB ■ ■ Small: 5 GB Medium: 10 GB Large: 15 GB. <value> is the value assigned to the environment variable. ksh. Chapter 2 Planning the CONTROL-M solution 37 . and bash should use the following syntax: <envVar>=<value> export <envVar> EXAMPLE BMC_HOST_INSTALL=myhost export BMC_HOST_INSTALL <envVar> is the name of the environment variable. follow the instructions in the accompanying readme file.bmc. due to changes that are applied to the operating systems. Otherwise. The check_req.UNIX requirements Verifying operating system levels and patches In order to verify that the operating system version.com/pub/control-m/opensystem/PANFT. run the check_req. BMC recommends that you download the latest version of this file from the following web site: ftp://ftp.Z file from the web site. “Mounting DVDs and CDs on UNIX computers”.tar. To verify operating systems and patches using the check_req. If you are using the check_req. this file may not be up-to-date. and UNIX kernel parameters are compatible with CONTROL-M requirements. However. you are advised that the product can be installed. Preparing a CONTROL-M/EM or CONTROL-M/Server account on UNIX The CONTROL-M/EM or CONTROL-M/Server account must include a home directory with sufficient disk space for installation of CONTROL-M components as shown in Table 5 on page 36.sh file.sh 4 Follow the prompts to complete the information as necessary. 5 If the operating system and patches meet CONTROL-M requirements. see Appendix I. 3 Use the following command to start the script from the CONTROL-M/EM or CONTROL-M/Server installation DVD: <dvdPath>/pre_req/check_req.sh file on the installation DVD. a list of missing requirements is displayed.sh file is located in the pre_req directory on the CONTROL-M/EM and CONTROL-M/Server installation DVDs. 6 If the script alerts you to a missing patch. continue with this procedure.01.6. check with your system administrator or database administrator to see if the patch is included in one of the bundled packages that are installed on your computer or database. For details of mount procedures for your UNIX platform.4.001 If you downloaded the pre_req. 38 CONTROL-M Installation Guide . 2 Mount the CONTROL-M/EM or CONTROL-M/Server installation DVD. maintenance level (patches).sh file 1 Log in as a root user. If a process exceeds its limit. For Oracle. Chapter 2 Planning the CONTROL-M solution 39 . Initial program The initial program for the CONTROL-M/EM or CONTROL-M/Server account must be specified as one of the following names or programs: ■ ■ ■ ■ ■ /bin/csh /bin/tcsh /bin/sh (CONTROL-M/EM only) /bin/ksh (CONTROL-M/EM only) /bin/bash (CONTROL-M/EM only) Setting limits for the CONTROL-M/EM or CONTROL-M/Server account on UNIX UNIX computers have predefined limits that are designed to limit or prevent the excessive use of resources by a single process.UNIX requirements The CONTROL-M/EM or CONTROL-M/Server account must have an administrator group name. On some operating systems. use the limits specified in Table 6. To avoid premature termination of running processes. this command is reserved for "Super Users" only. EXAMPLE /usr/sbin/useradd -u <numeric_user_id> -g <user_group> -d <user_home> -s <user_shell> <user_name> 2 Both users must have identical names and identical user IDs (UID). You can use the limit command to check the current limits in your computer. the operating system might kill the process without cleanup and without generating diagnostics. 3 Both users’ home directories should point to the same location on a shared disk. one on each node. perform the following: 1 Create two user accounts as shown in the following example. the administrator group name must be dba. For a cluster environment. Note: Do not set parameter to unlimited. descriptors The recommended value is 4096. Table 7 describes the Windows requirements for CONTROL-M/EM and CONTROL-M/Server. memoryuse maximum amount of memory to be used by a single process BMC recommends setting this value to unlimited. coredumpsize maximum size that a core dump can reach BMC recommends setting this value to datasize to generate a complete core dump if a failure occurs. Where to go from here Continue with Chapter 3. Table 7 Windows requirements for CONTROL-M/EM and CONTROL-M/Server (Part 1 of 3) Resource Hardware Specification ■ ■ ■ 40 CONTROL-M Installation Guide Requirement Computer: Pentium IV 1 GHz or higher Display: 16-bit (65536) colors or higher Storage Media: DVD drive .cfm. “Installing CONTROL-M/EM on UNIX” or Chapter 5. you must have Administrator privileges. maximum number of descriptors in use by a single process.Windows requirements Table 6 Limits for CONTROL-M/EM or CONTROL-M/Server Accounts on UNIX Parameter Description datasize maximum size of the data segment of a process Maximum values are as follows: ■ Solaris®: 2 GB ■ HP-UX®: 4 GB (using third and fourth quarter enabled) ■ AIX®: 2 GB stacksize maximum size of the stack segment of a process. To install CONTROL-M. “Installing CONTROL-M/Server”. Windows requirements Software and database compatibility information is listed at http://www. BMC recommends 400 MB on all UNIX computers.com/supportu/PAC_utility/index.bmc. 7 GB CONTROL-M/EM client components with Embedded PostgreSQL 2 GB for Vista 1 GB for XP CONTROL-M/EM client components without Embedded PostgreSQL 1.0 or later Chapter 2 Planning the CONTROL-M solution 41 . CONTROL-M/Server with 400 MB Embedded PostgreSQL 300 MB CONTROL-M/Server without Embedded PostgreSQL Oracle Server (dedicated) ■ 7 GB Oracle /tmp directory (dedicated) ■ 400 MB CONTROL-M/EM and CONTROL-M/Server database (tablespace) All database servers Sybase database except Sybase: server: ■ ■ ■ Related Software Small: 3 GB Medium: 5 GB Large: 8 GB ■ ■ ■ Small: 5 GB Medium: 10 GB Large: 15 GB Internet Explorer version 6.5 GB Full CONTROL-M/EM installation: 850 MB Client installation (including the Reporting Facility): 200 MB BMC Software ■ recommends that three times the CONTROL-M/EM without ■ Full CONTROL-M/EM installation: amount of RAM in Embedded PostgreSQL 850 MB the system be ■ Client installation (including the reserved for swap Reporting Facility): 200 MB space.Windows requirements Table 7 Windows requirements for CONTROL-M/EM and CONTROL-M/Server (Part 2 of 3) Resource Specification Requirement Memory CONTROL-M/EM server components with Embedded PostgreSQL 2 GB CONTROL-M/EM server components without Embedded PostgreSQL 1.7 GB for Vista 700 MB for XP CONTROL-M/Server with Embedded PostgreSQL 1 GB CONTROL-M/Server without Embedded PostgreSQL 700 MB Oracle Server ■ ■ ■ Diskspace CONTROL-M/EM with Embedded PostgreSQL ■ Small: 500 MB Medium: 1GB Large: 1. bmc. Select English (US) in Control Panel => Regional and Language Options to set the locale to English. For Windows 2003 this folder is: WINDOWS\System32. After installation you can reconfigure your computer for work with a non-English language.cfm. Select Western Europe and United States in Control Panel => Regional and Language Options for the system to receive all messages in English. see the CONTROL-M Language Customization Guide.Installation requirements for CONTROL-M/Agent Table 7 Windows requirements for CONTROL-M/EM and CONTROL-M/Server (Part 3 of 3) Resource Specification Requirement Environment Variables A reference to the WINNT\System32 folder must be in the PATH environment variable. 42 CONTROL-M Installation Guide . set the system locale and language settings to English before installing CONTROL-M: 1. you may decide not to install separate CONTROL-M/Agents. For the most current operating system compatibility information for this version. see the CONTROL-M Administrator Guide. 2. If you use this feature. “Installing CONTROL-M/EM on UNIX” or Chapter 5. Installation requirements for CONTROL-M/Agent NOTE CONTROL-M jobs can be submitted to remote hosts without having CONTROL-M/Agents installed on the remote host machines. Language Settings When working with non-English versions of Windows. ■ For information about configuring remote hosts. see the CONTROL-M Concepts Guide. “Installing CONTROL-M/Server”. For more information. Where to go from here Continue with Chapter 3.com/supportu/PAC_utility/index. The TEMP environment variable must indicate a path that exists on your computer. ■ For details about this feature and when to use it. see http://www. This requirement is necessary only for running Agent utilities. Java Runtime Environment Version 1. NOTE If more than one CONTROL-M/Agent is required on the same computer. 2 Kernel parameter values must be modified as specified in Table 9. Table 9 Kernel parameter requirement for CONTROL-M/Agent Parameter Additional values semmni Increase the current parameter value by 1 for each Agent to be installed on the computer. each one must be installed in a separate account. Chapter 2 Planning the CONTROL-M solution 43 . semmns 3 Define a CONTROL-M/Agent user account. Preparing for CONTROL-M/Agent installation on UNIX To ensure that you are ready to install CONTROL-M/Agent on UNIX 1 Check that the prerequisites described in “System requirements” on page 43 are met. It is not required to run Agent jobs.5 or later.System requirements System requirements Ensure that your computer meets the following requirements: Table 8 Minimum system requirements Requirement Value Memory 128 MB Disk Space In the CONTROL-M/Agent home directory the following amount of free disk space is needed: ■ UNIX: 50 MB ■ Windows: 60 MB Additional disk space is required for job for temporary files. verify that it is not running and that no jobs are currently executing because CONTROL-M/Agent will not recognize these jobs after the upgrade is complete. sh. You can also install more than one CONTROL-M/Agent on the same computer. The user can be a local user or an NIS user. NOTE ■ All computers in the CONTROL-M environment must be set to the same locale. see “Installing CONTROL-M/Agent on UNIX”. see the CONTROL-M Administrator Guide.) You can change this setting after the installation process is complete. For more information. A non-interactive (silent) installation and upgrade procedure is also available for CONTROL-M/Agent. 44 CONTROL-M Installation Guide . 5 Verify that your locale is set to English before beginning the installation. “Installing CONTROL-M/Agent”. ksh. NOTE The proclog and sysout directories can be placed on NFS as part of the post installation process. Preparing for CONTROL-M/Agent installation on Windows CONTROL-M/Agent can be installed and upgraded interactively or silently. see “Installing CONTROL-M/Agent on Windows”. or bash. (You can check this using the locale command. The initial program for the user must be defined as either csh. ■ If you are upgrading from an earlier version of CONTROL-M/Agent for UNIX. The permissions of the account home directory must allow read and execute permissions to all users and full permission to the account owner (755 as a minimum).Preparing for CONTROL-M/Agent installation on Windows CONTROL-M/Agent must be installed on a user account that is located on the local file system. 4 Ensure that the IPC subsystem is enabled. but the account home directory must be located on a local disc and not on NFS. For more information. For more information on installing multiple agents. Where to go from here Continue with Chapter 7. You can check its status by issuing the ipcs -a command. tcsh. For more information see “Setting CONTROL-M/Agent file permissions for NFS (UNIX)” on page 101. When CONTROL-M/Agent is installed. SAP). They must be defined during the installation. “Installing CONTROL-M/Agent”. Traditional Chinese. When creating a CONTROL-M database on an existing MSSQL database server with CJK support already present. you must choose the custom option. No changes are required for CONTROL-M Control Modules or CONTROL-M Options that existed before an upgrade. Additional CONTROL-M Control Modules (for example. you are explicitly asked if CJK character support is required for the new CONTROL-M database. CJK settings are inherited automatically from the database server.East Asian (CJK) language considerations Considerations for control modules CONTROL-M/Agents use control modules to interact with the operating system and with third party applications (for example. When you create a CONTROL-M database on an existing Oracle. can be installed afterwards. SAP. When installing a dedicated (BMC-supplied) Oracle database server. or Oracle Applications). you are explicitly asked if CJK character support is required. AFT. Japanese. or Sybase database server. When you create a CONTROL-M database on an existing PostgreSQL database server. East Asian (CJK) language considerations Support for East Asian languages (Simplified Chinese. During custom installation. For more information regarding CJK support. Where to go from here Continue with Chapter 7. the control module for the operating system (OS) is installed together with the Agent. CJK settings are not inherited automatically from the database server. and Korean) is provided for all installations at the database level. see the CONTROL-M Language Customization Guide. Chapter 2 Planning the CONTROL-M solution 45 . East Asian (CJK) language considerations 46 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple instances of CONTROL-M/EM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The silent installation procedure allows you set up a batch file with all the necessary parameter information to install CONTROL-M/EM using a single command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database server options . . . . . . The installation program offers you the following options: ■ Choice of database server: Embedded PostgreSQL (default). . . . . . . . . . . . . . . . . . . . . . Installing multiple database clients considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM server components . . . . . . . . . . .Chapter 3 3 Installing CONTROL-M/EM This following topics are discussed in this chapter: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM on Windows . . . . . . . Installing CONTROL-M/EM on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ensuring Oracle Availability on UNIX . . . . . . . . . . . . . . . . . . . . . . Installation parameters . . . . . . Naming multiple instances . . . Installing CONTROL-M/EM server and client components . . . Oracle. . . . . . . . . . . . . . . . . . . . . or Sybase Chapter 3 Installing CONTROL-M/EM 47 . . . . . . . . . . . . . . . . . . . . . . . . Database server options . . . . . Using CONTROL-M/EM Web Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 48 48 49 49 53 54 55 58 62 64 64 65 Overview Interactive and silent installation procedures are available to install CONTROL-M/EM on UNIX and on Windows. . . . . . . . . . . . . . . . . . . MSSQL. . . . . . . . . . . . . . . This is especially useful when the product needs to be installed on several computers using the same configuration. . . . . see “Installing CONTROL-M/EM on Windows” on page 53 Installing CONTROL-M/EM on UNIX NOTE You can download the installation ISO file from the BMC Electronic Product Distribution (EPD) web site: https://webapps. see “Installing CONTROL-M/EM on Windows” on page 53. see “Installing CONTROL-M/EM on UNIX” on page 48. A UNIX installation installs the CONTROL-M/EM server components. client components. All client components reside in a Windows environment.jsp You can burn the ISO file onto a CD/DVD and mount the media. To install on Windows. a dedicated Embedded PostgreSQL database server is automatically installed in the background as part of the CONTROL-M/EM installation – no interaction is required. For more information.with or without the Reporting Facility TIP The following default installation choices are recommended by BMC Software: ■ Database server: Embedded PostgreSQL ■ Database server configuration: Default ■ CONTROL-M/EM: Full or Client as required If you do not choose to use the recommended default installation. To install on UNIX. you must install a database server. 48 CONTROL-M Installation Guide . see “Other database options” on page 32.includes server components. and the Reporting Facility — Client .Installing CONTROL-M/EM on UNIX ■ Database server configuration: Default or Custom ■ CONTROL-M/EM: — Full .com/signon/content/logon. Database server options If you choose the default installation. For more information.bmc. The installation can be performed from the CD/DVD as outlined in this section. runs the installation from an installation script ■ Silent .sh from the installation DVD (see Appendix C). perform the following additional command: ■ lsnrctl start <listenerName> For Oracle databases supplied by BMC Software. <listenerName> is LSTNR_<instanceName> Installing CONTROL-M/EM server components There are two types of installation for installing CONTROL-M/EM Server components: ■ Interactive . ■ Install a CONTROL-M/EM database on an existing Sybase database server by running <dvdPath>/Sybase/setup. For information on silent installations. ■ Install a CONTROL-M/EM tablespace on an existing Oracle database server (see Appendix A).csh sqlplus "/as sysdba" startup exit If the Oracle Listener is down. see “Interactive installation” on page 50.allows you set up a batch file with the necessary parameter information to install CONTROL-M/EM using a single command For information on interactive installations. see “Silent installation” on page 51. Chapter 3 Installing CONTROL-M/EM 49 . you must log in to the Oracle database server account and perform the following commands: ■ ■ ■ ■ source .Ensuring Oracle Availability on UNIX If you wish to install CONTROL-M/EM on Oracle or Sybase. you must ensure that a database server is available by choosing one of the following options: ■ Install a dedicated Oracle database server with a CONTROL-M/EM tablespace (see Appendix A).oraenv. Ensuring Oracle Availability on UNIX If Oracle is down. sh WARNING If the security settings at your site do not allow the “ping” command to be used. For information about mounting a DVD. prepare the installation by first implementing the criteria discussed under “Creating cluster resources for UNIX” on page 151.Installing CONTROL-M/EM server components NOTE When you install the product on an existing PostgreSQL database that resides on Windows. For information on setting variables. set the BMC_SKIP_PING environment variable to Y before running setup. Interactive installation 1 Mount the CONTROL-M/EM installation DVD from the root user and log off the root user before continuing with the installation. the following message is displayed. The installation log can be found in the home directory of the CONTROL-M/EM account. for example: <emHome>/BMCINSTALL/log/<version>_trace. database <database> was created in the default location and not in the specified location <location> You can safely ignore this message. 4 If this is a cluster installation. filling in parameter values as necessary (see Table 10 on page 58). see “Setting environment variables in UNIX” on page 37. ensure that the database server is up and running (see “Ensuring Oracle Availability on UNIX” on page 49). “Mounting DVDs and CDs on UNIX computers”. 2 Install CONTROL-M/EM clients on Windows computers as necessary (see “Installing CONTROL-M/EM on Windows” on page 53).sh.log Where to go from here 1 Install the latest fix pack to apply the most recent software updates. see Appendix I. 50 CONTROL-M Installation Guide . 5 Use the following command to run the installation script. 3 If you are installing on Oracle. 2 Log on to the CONTROL-M/EM account. <dvdPath>/setup. 6 Follow the instructions on the screen. Explanations are provided in Table 10 on page 58. ensure that a CONTROL-M/EM database has been installed.Installing CONTROL-M/EM server components 3 Perform the post-installation configuration tasks specified in Chapter 4. To prepare the silent installation parameters file 1 Prepare the parameter information you will need for the installation. However no installation is performed. “Post installation for CONTROL-M/EM. If you select PostgreSQL. Silent installation is used to install CONTROL-M/EM server components from a parameters file. 4 If this is a cluster installation. The following stages are involved: ■ Preparing the parameters file This is accomplished by running a silent installation preparatory procedure from the installation DVD. The preparatory procedure behaves like the interactive installation procedure and prompts you to enter the same information. you must also complete the procedures listed under “Setting up the CONTROL-M/EM UNIX cluster environment” on page 157. Chapter 3 Installing CONTROL-M/EM 51 . You can reuse this parameters file to silently install CONTROL-M/EM server components on other computers. the CONTROL-M/EM database was prepared automatically. 2 On an existing database server. Silent installation WARNING CONTROL-M/EM can be installed silently only if the database component was also installed silently. the information you enter is stored in a parameters file. If you installed a BMC Software dedicated Oracle database server. this installation installs the database server automatically. Instead. ■ Running the installation using the prepared parameters file When the installation is run using the prepared parameters file. the CONTROL-M/EM server components are installed using the parameters you specified in the previous step. 8 Follow the interactive menu instructions specifying parameter values as requested.CTL. The installation parameters saved to ${HOME}/BMCINSTALL/PRODUCTS.sh. 52 CONTROL-M Installation Guide . set the BMC_SKIP_PING environment variable to Y before running setup. see “Setting environment variables in UNIX” on page 37.Installing CONTROL-M/EM server components 3 If you are installing on Oracle. 5 Log on to the CONTROL-M/EM account. <newDboPassword> is the dbo password that will be set. For information about mounting a DVD. 4 Mount the CONTROL-M/EM installation DVD from the root user and log off the root user before continuing with the installation.sh WARNING If the security settings at your site do not allow the “ping” command to be used. “Mounting DVDs and CDs on UNIX computers”. modify them in the parameters file manually. 2 Set the following environment variables (see “Setting environment variables in UNIX” on page 37 for your UNIX environment): ORG_DBO_PASSWORD to <temporaryPassword> DBO_PASSWORD to <newDboPassword> SA_PASSWORD to <sysAdminPassword> <temporaryPassword> is the temporary password given to the dbo during the database (silent) installation. 7 Issue the following command to activate the silent installation script: <dvdPath>/setup. 6 Set the environment variable BMC_SILENT_INSTALL to value Y. To install silently 1 Log on to the CONTROL-M/EM account. ensure that the database server is up and running (see “Ensuring Oracle Availability on UNIX” on page 49). If you want to change parameter values. see Appendix I. See “Setting environment variables in UNIX” on page 37 for your UNIX environment. For information on setting variables. com/signon/content/logon. 4 If this is a cluster installation. <parameterPath> is the full path to the silent installation file that was created in step 7 of “To prepare the silent installation parameters file” on page 51. 2 Install CONTROL-M/EM clients on Windows computers as necessary (see “Installing CONTROL-M/EM on Windows” on page 53). “Post installation for CONTROL-M/EM. Chapter 3 Installing CONTROL-M/EM 53 .sh -r <parameterPath> <dvdPath> is the path of the mounted DVD. 4 Restart CONTROL-M/EM. Installing CONTROL-M/EM on Windows NOTE You can download the installation ISO file from the BMC Electronic Product Distribution (EPD) web site: https://webapps.Installing CONTROL-M/EM on Windows <sysAdminPassword> is the system administrator password (required for a PostgreSQL installation). 3 Issue the following command: <dvdPath>/setup.bmc. The installation can be performed from the CD/DVD as outlined in this section. Where to go from here 1 Install the latest fix pack to apply the most recent software updates. close the current session and open a new one.jsp You can burn the ISO file onto a CD/DVD and mount the media. you must also complete the procedures listed under “Setting up the CONTROL-M/EM UNIX cluster environment” on page 157. Opening a new session activates the latest configuration settings. NOTE To work with CONTROL-M/Enterprise Manager. 3 Perform the post-installation configuration tasks specified in Chapter 4. ■ Install a Sybase client on the CONTROL-M/EM target computer to communicate with an existing Sybase database server (see your system administrator). ■ Perform an Oracle client installation (see Appendix B). you must first ensure that database server and client software is installed by choosing one of the following options: 54 ■ Perform an Oracle dedicated installation (see Appendix B). Clients can also be installed on other Windows computers to enable access to CONTROL-M/EM from several locations. ■ Install an MSSQL client on the CONTROL-M/EM target computer to communicate with an existing MSSQL database server (see your system administrator). MSSQL. ensure that the following criteria exist: ■ ■ The UNIX user under which the PosgreSQL database server is running must have write permissions to the data location directory. For an Oracle. The full installation and the client installation will install the necessary database server and client components – no interaction is required. or Sybase installation. If you intend to install more than one CONTROL-M/EM client on the same computer. Each CONTROL-M/EM client installation can optionally include an instance of the Reporting Facility. ■ Perform an Oracle existing installation (see Appendix B). a dedicated Embedded PostgreSQL database server is installed automatically in the background as part of the CONTROL-M/EM installation. The data location directory must be empty. CONTROL-M Installation Guide . refer to “Multiple instances of CONTROL-M/EM” on page 64.Database server options The full CONTROL-M/EM product (both server and client components) can be installed on Windows (this is usually performed on one computer only). Database server options If you choose the default installation. NOTE When installing CONTROL-M/EM using an existing PosgreSQL database server on UNIX. For more information see “Using CONTROL-M/EM Web Launch”. or Sybase. MSSQL. NOTE The simplest and efficient method of installing CONTROL-M/EM clients for CONTROL-M/EM users is by employing CONTROL-M/EM Web Launch. see “Interactive installation” on page 55. 4 Insert the installation DVD and run <dvdPath>\setup. NOTE If you are installing CONTROL-M/EM on an Embedded PostgreSQL database server. For more information on the silent installation. 2 Log on using an ID with Administrator privileges on the current computer.bat. Interactive installation 1 If your database server is Oracle.exe /v”BMC_SKIP_PING=”Y”” Chapter 3 Installing CONTROL-M/EM 55 .Installing CONTROL-M/EM server and client components Installing CONTROL-M/EM server and client components There are two types of installations ■ Interactive .runs the installation from an installation script ■ Silent . WARNING If the security settings at your site do not allow the “ping” command to be used. the setup. make sure that you follow the instructions under “Installing CONTROL-M/EM on Windows” on page 53.exe command must be issued from the command line as follows: setup. see “Silent installation” on page 56. the installation program installs the necessary database clients. 3 If this is a cluster installation.runs the installation from a batch file For more information on the interactive installation. prepare the installation by first implementing the criteria discussed under “Creating cluster resources for Windows” on page 154. The preparatory procedure behaves like the interactive installation procedure and prompts you to enter the same information. filling in parameter values as necessary (see Table 10 on page 58). complete the tasks specified for Windows in Chapter 4. Two stages are involved: 1. check the information in the %TEMP%\ctmem640_user_log. 56 CONTROL-M Installation Guide . Where to go from here If you selected the full installation option. Instead. CONTROL-M/EM can be installed silently only if the database component was also installed silently. MSSQL. CONTROL-M/EM is installed using the parameters you specified in the previous step. or Sybase. After the installation is complete. NOTE If you are installing CONTROL-M/EM on an Embedded PostgreSQL database server. Preparing the batch file This is accomplished by running a silent installation preparatory procedure from the installation DVD. Silent installation is used to install CONTROL-M/EM from a batch file. To prepare the silent installation batch file 1 If your database server is Oracle. Running the prepared batch file When the prepared batch file runs. You can reuse this batch file to silently install CONTROL-M/EM on other computers.txt file to ensure that the installation ended successfully. ensure that you follow the instructions under “Installing CONTROL-M/EM on Windows” on page 53. However no installation is performed. This option is not supported for Windows cluster environments.Installing CONTROL-M/EM server and client components 5 Follow the instructions on the screen. the information you enter is stored in a batch file. 2. the installation program installs the necessary database clients. “Post installation for CONTROL-M/EM. Silent installation WARNING On Oracle and Sybase. bat file must be modified as follows: “%Source_dir%setup. check the information in the %TEMP%\ctmem640_trace_log.bat file to a local drive to facilitate this change.Net Framework 2. After making the change.Installing CONTROL-M/EM server and client components 2 If the installation DVD will be accessed through a network.txt file to ensure that the installation ended successfully.exe”. select Save & Exit to save the parameters..exe /q:a /c:"install /l /q” 3 If the BMC_EM_silent. and run the following command: <dvdPath>\prep_silent.exe”/s /v”BMC_SILENT_INSTALL=\”Y\” BMC_SKIP_PING= \”Y”/l*v\”%InstallLogFile%\”” It is necessary to copy the prep_silent.bat. line in the prep_silent. 2 Run the following command from the installation DVD to install . you must first map the DVD drive and assign a drive letter.bat file from the local drive. navigate to the installation folder. 3 Insert the installation DVD into the mapped drive. 4 After selecting the type of installation required and entering the necessary parameters values at the prompts. Chapter 3 Installing CONTROL-M/EM 57 . the “%Source_dir%setup. run the modified prep_silent.bat file will be accessed through a network.0.bat 5 After the installation is complete. The parameters are saved to: %TEMP%\BMC_EM_silent.bat file now resides. and run the silent installation by issuing the following command: <path>\BMC_EM_silent. dotnetfx. 4 Open a command prompt window. navigate to the path where the BMC_EM_silent.. To install silently 1 Log on to the target computer using an ID with Administrator privileges. you must first map the DVD drive and assign a drive letter.bat WARNING If the security settings at your site do not allow the “ping” command to be used. for other databases:1) mode. complete the tasks specified for Windows in Chapter 4. The name must begin with a letter (A-Z. database <database> was created in the default location and not in the specified location <location> You can safely ignore this message. Installation parameters Table 10 provides a description of UNIX and Windows prompt or interactive and silent installation parameters. a-z) followed by up to 29 alpha-numeric characters (includes underscores). Other databases: Default (for PostgreSQL): LATIN1 EM_MSSQL_SRV_ CJK_CHK CONTROL-M/Enterprise Manager Database Name N/A Default (for other databases): 1 PROP_EM_SYB_MS When creating a new database SQL_DATABASE_ NAME Name for the CONTROL-M/EM database. the following message is displayed. “Post installation for CONTROL-M/EM. Table 10 UNIX and Windows interactive and silent installation parameters (Part 1 of 5) Interactive parameter or prompt CJK UNIX silent installation parameter name Windows silent installation parameter name [SETP]/BMC/PO PostgreSQL: STGRES/UTF_M ODE_STR EM_PG_SRV_CJK_ CHK Description Sets language mode to either standard (for PostgreSQL: Latin1.Installation parameters NOTE When you install the product on an existing PostgreSQL database on Windows. When communicating with an existing database: Name of the existing database schema to which to connect. for other databases: “ ” [empty string]) or western languages (for PostgreSQL: UTF8. Where to go from here If you selected the full installation option. 58 CONTROL-M Installation Guide . When communicating with an existing database Enter the existing port number for communication with the remote CORBA server. The value must be in the range 1025-65535. Data Device Physical Full Path File Name N/A Data Device Size N/A PROP_EM_SYB_MS Specify a new file name which SQL_DATA_DEVIC includes the full path to the physical E_LOCATION device where the CONTROL-M/EM database resides. You must take into consideration the number of jobs in the Active Jobs file. Chapter 3 Installing CONTROL-M/EM 59 . CORBA Naming Service Port Number [SETP]/BMC/EM PROP_EM_CORBA /CORBA_PORT_ _PORT NUMBER When creating a new database: Specify the port number for communication with the local CORBA server. P R O P _ E M _ S Y B _ S Q L _ D A T A _ S I Z E Amount of space (in MB) to allocate for the data portion of the database.Installation parameters Table 10 UNIX and Windows interactive and silent installation parameters (Part 2 of 5) Interactive parameter or prompt UNIX silent installation parameter name Windows silent installation parameter name Description CORBA Naming Service Host Name [SETP]/BMC/EM PROP_EM_CORBA /CORBA_HOST _HOST _NAME Host name of the machine running the remote CORBA server to which you want to connect. Database Administrator Login N/A PROP_EM_DBA_US Name of the database administrator.Installation parameters Table 10 UNIX and Windows interactive and silent installation parameters (Part 3 of 5) Interactive parameter or prompt UNIX silent installation parameter name Windows silent installation parameter name Data Location N/A PG_DATA_LOCATI Path to the POSTGRESQL ON CONTROL-M/EM tablespace location. Database Owner Password N/A PROP_EM_DBUSE R_PASSWORD When creating a new database: Password for the CONTROL-M/EM database owner. For Windows. When communicating with an existing database: Current password for the CONTROL-M/EM database owner. this parameter is informational only and cannot be changed during installation. a-z) followed by up to 7 alpha-numeric characters (includes underscores). Database Server Name 60 N/A CONTROL-M Installation Guide PROP_DB_LOGICA Name of the database server L_NAME_FROM_LI ST Note: The database server name for Sybase on Windows is restricted to a maximum of 22 characters. The password must begin with a letter (A-Z. a-z) followed by 5 to 29 alpha-numeric characters (includes underscores). ER Database Administrator Password N/A PROP_EM_DBA_PA Password of the database SSWORD administrator. . The installation will fail if this restriction is violated. The name must begin with a letter (A-Z. Full installation without creation of a new database: Name of an existing CONTROL-M/EM database schema owner to which to connect. Database Owner Login N/A PROP_EM_DBUSE R_NAME Description Full installation with creation of a new database: Name for the CONTROL-M/EM database schema owner. Installation parameters Table 10 UNIX and Windows interactive and silent installation parameters (Part 4 of 5) Interactive parameter or prompt UNIX silent installation parameter name Windows silent installation parameter name Database Server Type N/A PROP_DBSRV_DA TABASE_TYPE Description The database server brand name: Embedded POSTGRESQL. ORACLE. Default: medium. large). Port Number N/A PG_PORT_NUM The TCP/IP port that the POSTGRESQL database server listens to for communication from CONTROL-M/EM PostgreSQL Service user name N/A EM_NON_ADM_U SER Set a user name for the Windows Service. 0-9. Log Device Size N/A PROP_EM_SYB_SQ Amount of space (in MB) to allocate L_LOG_SIZE_ for the transaction log. Chapter 3 Installing CONTROL-M/EM 61 . PostgreSQL Service password N/A EM_NON_ADM_U SER_PASSWORD Set a password for the PostgreSQL Windows service according to the operating system security policy. Default: <drive>:\Program Files\BMC Software\CONTROL-M EM <version> Host Name Interface Name N/A PG_INTERFACE_N Host name of the computer on which AME the POSTGRESQL database server is installed (Installation DVD) PROP_DVD_LOCA Location of installation DVD TION Instance Name PROP_CTMEM_IN STANCE_NAME CONTROL-M/EM instance name Log Device Physical Full Path File Name N/A PROP_EM_SYB_MS Specify a new file name which SQL_LOG_DEVICE includes the full path to the physical device where the CONTROL-M/EM _LOCATION database log resides. The name can contain up to 20 alphanumeric characters (A-Z. medium. hyphens. and underscores). SYBASE. a-z. All selected components are installed in subdirectories under this directory. or MSSQL Default: POSTGRESQL Data Tablespace Size N/A PROP_EM_SYB_SQ Size of CONTROL-M/EM database L_DBSIZE (small. Destination Folder N/A PROP_INSTALLDI R The directory you specify in this window becomes the home folder for CONTROL-M/EM. The recommended amount is 1/3 of the data device size. see the CONTROL-M Administrator Guide. the CONTROL-M/EM client components. and CONTROL-M Configuration Manager are packaged on the web server. ■ Using CONTROL-M/EM Web Launch. the CONTROL-M/EM GUI. 62 CONTROL-M Installation Guide . CONTROL-M/Desktop. CONTROL-M/EM Web Launch works as follows: ■ CONTROL-M/EM is installed by the system administrator on a single computer ■ A web server is installed on the same computer as part of the CONTROL-M/EM full installation. each user can install the CONTROL-M/EM client components from the web using CONTROL-M/EM Web Launch.Using CONTROL-M/EM Web Launch Table 10 UNIX and Windows interactive and silent installation parameters (Part 5 of 5) Interactive parameter or prompt UNIX silent installation parameter name Windows silent installation parameter name Setup Type N/A PROP_TASK_SELE CTION Description Full CONTROL-M/Enterprise Manager ■ create database and install all components or ■ connect to existing database and install all components CONTROL-M/Enterprise Manager Client ■ installs client components on the local computer including the Reporting Facility as an option. Sybase Server Host Name N/A PROP_DB_SYBASE Host name of the computer on which _DBSERVER_HOST the Sybase database server is installed Sybase Server Query Port Number PROP_DB_SYBASE The TCP/IP port that the Sybase _DBSERVER_PORT database server listens to for communication from CONTROL-M/EM N/A Using CONTROL-M/EM Web Launch If your site runs CONTROL-M/EM client components on several desktops. For more information on CONTROL-M/EM Web Launch and how to package client components. Anytime a client component is started. the URL is embedded in the start command of each client component. set the DisableMSI parameter in the registry. B Ensure that the data type of the DisableMSI parameter is REG_DWORD and its value is 0. you must disable the User Account Control (UAC) before running Web Launch. C Save and exit the registry. 2 Ensure that Microsoft . When updates are available. the user can run CONTROL-M/EM from the Windows start menu.1 and 2. A Navigate to the HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer registry key. 5 Using the Registry editor.Using CONTROL-M/EM Web Launch ■ The system administrator supplies CONTROL-M/EM users with the URL for the packaged CONTROL-M/EM client applications. consult your system administrator.Net Framework runtime versions 1. To enable the installation of CONTROL-M/EM client components 1 With Windows Vista. 3 Obtain the CONTROL-M/EM client URL from your system administrator. ■ Users initiate the client installation through the URL. If you want to implement CONTROL-M/EM Web Launch on a cluster computer. the user is prompted to install them. 4 Activate the installation from the URL. create it. If the Installer directory does not exist under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows. ■ During installation. After the installation completes. ■ Web Launch packages do not overwrite existing user data when they are deployed NOTE CONTROL-M/EM Web Launch is not cluster-aware. WARNING Disabling the UAC affects the privileges of all applications running under Windows Vista. the web site is checked for updates.0 are installed on your computer. Chapter 3 Installing CONTROL-M/EM 63 . 4.1. Sybase.01 component. 6.1. ■ Database clients from different vendors (for example.03 components. instance name. The suggested name can be changed by the user. for example. MSSQL) can be installed as necessary on the same computer. The following rules apply: ■ Only one full installation instance of a supported version can be installed on a single computer. ■ Unlimited instances of 6. ■ For subsequent instance installations.2.01 cannot be installed on the same client computer when both packages are downloaded from the same URL (same host computer.03).Multiple instances of CONTROL-M/EM NOTE You are not required to have Administrator privileges on your computer to install a CONTROL-M/EM client using Web Launch. ■ Web Launch packages from CONTROL-M/EM versions 6. Multiple instances of CONTROL-M/EM Multiple instances of CONTROL-M/EM can be installed on a single Windows computer (supported versions include 6.01 and 6. ■ Cluster support is available only for the full installation. ■ A full installation of version 6.01. and 6. an instance name consisting of <hostName>_<instanceNumber> is suggested by the installation program. ■ Components (full installation or client) of previous versions must be installed before any 6. Oracle.4.01. Note that instance names must not contain any of the following characters: / \ : * ? "<>| CONTROL-M Installation Guide .01 clients (including clients with the Reporting Facility) can be installed.4.4. and port number).01 cannot be installed with any 6.01. 6.3.3. CTMEM_1. Naming multiple instances 64 ■ The first instance is named Default.4. CTMEM_2. Installing multiple database clients considerations Sybase If multiple Sybase clients are used.Installing multiple database clients considerations ■ If you uninstall the default instance.2. 3 Run setup.zip from the following site: ftp://ftp.com/pub/Database_Patches/Oracle 2 Open OracleSelector.2.01 with an Oracle 10. the next instance to be installed is named Default.01 or 6.3.exe to select the Oracle environment (Oracle home) you currently require.01.03 with an Oracle 9. Note that only one Oracle environment can be accessed at any one time.exe. 6. 6. Oracle If a CONTROL-M/EM version 6.1.01 or 6.2 Client (with Reporting Facility) is installed on a computer that has CONTROL-M/EM versions 6.3. Chapter 3 Installing CONTROL-M/EM 65 .bmc.zip and extract file setup. users will lose the ability to log in to the CONTROL-M/EM 6. You are not given the option of changing the name.1.i client (with Reporting Facility and CONTROL-M Configuration Manager) already installed. You can run setup.exe again any time you wish to switch between Oracle environments.01.4.03 environment. they must all be of the same version. To enable logging in to all installed environments 1 Download file OracleSelector. Installing multiple database clients considerations 66 CONTROL-M Installation Guide . . . Start the following components that are necessary to run CONTROL-M as prompted: ■ GUI Server ■ Global Alerts Server ■ Global Conditions Server 2 Navigate to the CONTROL-M/Server definition window by selecting Components -> New -> CONTROL-M/Server and Gateway from the Configuration Manager menu Chapter 4 Post installation for CONTROL-M/EM 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . you must connect CONTROL-M/EM to at least one instance of CONTROL-M/Server manually as follows: 1 On a Windows computer that has CONTROL-M/EM (full or client) installed. . . . . . . . . . . . . . . . . . . . . log in to CONTROL-M Configuration Manager (Start->Programs -> CONTROL-M Enterprise Manager <version> -> Default -> CONTROL-M Configuration Manager). . . . . . . Checking Java software . . . . . . . Importing WIN panel functionality (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 68 68 69 69 70 Starting up the CONTROL-M system After installing both CONTROL-M/EM and CONTROL-M/Server. . . . . . . . Setting startup options for CONTROL-M/EM services on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . Component communication for UNIX . . . . . . . . . . . . . . . . . . . . . . . Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 4 4 Post installation for CONTROL-M/EM The following topics are discussed in this chapter: Starting up the CONTROL-M system. . . . . . . . . . . . . . . . . . . . . . . . . . . Otherwise. see the CONTROL-M Administrator Guide. 6 If CONTROL-M/EM and CONTROL-M/Server were installed with the suggested default parameters. Component communication for UNIX Perform the following steps on each UNIX computer where CONTROL-M/EM components are installed: 1 Log in to the UNIX account for CONTROL-M/EM. you can accept the suggested defaults for CONTROL-M ID and Configuration Agent Port. For more information on configuring CORBA. 7 Click Next as required. choose any name you wish for the new CONTROL-M/Server 5 Enter the name of the host machine of the CONTROL-M Host (the computer where CONTROL-M/Server is installed). It is also used to configure CORBA.5 or higher installed on your computer. 2 After completing a CONTROL-M/EM client installation. Checking Java software Java software is required on both UNIX and Windows platforms.Checking Java software 3 Select Discover and click OK 4 In the Specifying CONTROL-M/Server parameters window. The “Discover” process detects and defines the new CONTROL-M/Server and its gateway in the Configuration Manager. you should use one of the following commands to verify that the database server is active: ■ ■ ■ 68 For PostgreSQL: psql -U <emDBO> (you will be prompted for the database owner password) For Oracle: sqlplus <emDBO>/<password> For Sybase: isql -U <emDBO> -P <password> CONTROL-M Installation Guide . see your system administrator. Ensure you have JRE version 1. Oracle installations only. Setting startup options for CONTROL-M/EM services on Windows Depending on which components were installed. ■ Type quit to exit the database server.Setting startup options for CONTROL-M/EM services on Windows <emDBO> is the database owner name under which CONTROL-M/EM was installed. Chapter 4 Post installation for CONTROL-M/EM 69 . Start CONTROLM/Server on each computer as necessary and check that communication with CONTROL-M/EM can be established (for example. see the CONTROL-M Administrator Guide. CONTROL-M/EM will not function correctly. the procedure should be performed on every computer that has CONTROL-M/EM client component(s) installed. For more information. For more information. For full functionality. choose the Activation Menu option. Table 11 CONTROL-M/EM services Service Installation type OracleEM1010EM6401TNSListener OracleServiceEM640 Oracle database server . Importing WIN panel functionality (optional) You can use the following procedure to display Microsoft Windows job parameters in the Job Editing form of CONTROL-M/EM and CONTROL-M/Desktop. and choose the Start All option to activate all CONTROL-M/EM components. you must first set up the CONTROL-M working environment. using the ping command). all or some of the Windows services listed in Table 11 will start automatically when the system is booted. and <password> is the database owner password. 5 Log in to one or more CONTROL-M/Server computers. These services are added to the computer during Oracle database installation. If they do not start. see the CONTROL-M Administrator Guide. 3 Enter the following command to verify that the CORBA service is active: ps -ef | grep <unixUser> | grep Naming_Service 4 Run the root_menu script. TAO NT Naming Service Full installation To start using CONTROL-M/EM. 5 Shut down and restart CONTROL-M/EM. Navigate to the Windows\Forms folder on the application CD. 70 CONTROL-M Installation Guide . 2 In CONTROL-M/Desktop. Where to go from here You have now completed the installation of CONTROL-M/EM. 3 A browse window is displayed. 4 Select the windows. choose Tools => Import Applications Forms.xml file and click Import.Where to go from here 1 Ensure that the CONTROL-M/Agent application CD is on a mapped drive. . . Interactive installation . . . . . . . . . . . . . . . . . . . MSSQL. . . . . . . Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 5 5 Installing CONTROL-M/Server NOTE BMC Software recommends that you verify that you have installed or upgraded to CONTROL-M/EM version 6. . . . . . . . . . Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interactive installation .01 before installing this version of CONTROL-M/Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/Server on Windows . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 72 73 74 74 76 80 81 82 82 84 Installation database server options The setup program installs CONTROL-M/Server with the following installation options: ■ Choice of database server: Embedded PostgreSQL (default). . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The following topics are discussed in this chapter: Installation database server options . . . . . . . . or Sybase ■ Database server configuration: Default or Custom Chapter 5 Installing CONTROL-M/Server 71 . . . . . . . . . . . Installing CONTROL-M/Server on UNIX NOTE The Custom database configuration option can be used either for an existing or dedicated installation. ensure that you know the PostgreSQL port and host. you must ensure that a database server is available by choosing one of the following options: 72 ■ Install a dedicated Oracle database server with a CONTROL-M/Server tablespace (see Appendix A). TIP You can get up and running quickly by choosing the default installation with Embedded PostgreSQL. Before installing CONTROL-M/Server with PostgreSQL in existing mode. CONTROL-M Installation Guide .sh from the installation DVD (see Appendix C). ■ Install a CONTROL-M/Server tablespace on an existing Oracle database server (see Appendix A). Interactive and silent installation procedures are available to install CONTROL-M/Server on UNIX and on Windows. The silent installation procedure allows you set up a parameters (UNIX) or batch (Windows) file with all the necessary parameter information to install CONTROL-M/Server using a single command. ■ Install a CONTROL-M/Server database on an existing Sybase database server by running <dvdPath>/Sybase/setup. You can receive this information by running the following command: set | grep PG If you wish to install CONTROL-M/Server on Oracle or Sybase. This is especially useful when the product needs to be installed on several computers using the same configuration. Installing CONTROL-M/Server on UNIX The default installation installs a dedicated Embedded PostgreSQL database server automatically in the background as part of the CONTROL-M/Server installation – no interaction is required. 6 Use the following command to run the installation script. you must log in to the Oracle database server account and perform the following commands: ■ ■ ■ ■ source .oraenv.Interactive installation Ensuring Oracle Availability on UNIX If Oracle is down. <dvdPath>/setup. 4 If you are installing on Oracle. see Appendix I.csh sqlplus "/as sysdba" startup exit If the Oracle Listener is down. For information about mounting a DVD. prepare the installation by first implementing the criteria discussed under “Creating cluster resources for UNIX” on page 151. perform the following additional command: ■ lsnrctl start <listenerName> For Oracle databases supplied by BMC Software. “Mounting DVDs and CDs on UNIX computers” on page 199.sh Chapter 5 Installing CONTROL-M/Server 73 . Explanations about parameters are provided in Table 12 on page 77. <listenerName> is LSTNR_<instanceName> Interactive installation 1 Prepare all the information you need for the installation. ensure that the database server is up and running (see “Ensuring Oracle Availability on UNIX” on page 73). 3 Log in to the CONTROL-M/Server account. 5 If this is a cluster installation. 2 Mount the CONTROL-M/Server installation DVD from the root user and log off the root user before continuing with the installation. The preparatory procedure behaves like the interactive installation procedure and prompts you to enter the same information. However no installation is performed.Where to go from here WARNING If the security settings at your site do not allow the “ping” command to be used. see “Setting environment variables in UNIX” on page 37. For information on setting variables. 7 Follow the instructions on the screen responding to the prompts as necessary. for example: <ctmHome>/BMCINSTALL/log/<version>_trace. “Post installation for CONTROL-M/Server”. close the current session and open a new one. Instead.sh. ■ 74 Running the installation using the prepared parameters file CONTROL-M Installation Guide . set the BMC_SKIP_PING environment variable to Y before running setup. Opening a new session activates the latest configuration settings. Silent installation Silent installation is used to install CONTROL-M/Server from a parameters file. 3 If this is a cluster installation.log Where to go from here 1 Install the latest fix pack to apply the most recent software updates. you must also complete the procedures listed under “Setting up the CONTROL-M/Server UNIX cluster environment” on page 183. NOTE To work with CONTROL-M/Server. the information you enter is stored in a parameters file. 2 Perform the post-installation configuration tasks specified in Chapter 6. The installation log can be found in the home directory of the CONTROL-M/Server account. The following stages are involved: ■ Preparing the parameters file This is accomplished by running a silent installation preparatory procedure from the installation DVD. “Mounting DVDs and CDs on UNIX computers” on page 199. 6 Set the environment variable BMC_SILENT_INSTALL to value Y. For information about mounting a DVD. See “Verifying operating system levels and patches” on page 38 for your UNIX environment. An embedded PostgreSQL database server is automatically installed with the default CONTROL-M/Server installation if no other database server is present. 3 If you are installing on Oracle. 4 Mount the CONTROL-M/Server installation DVD from the root user and log off the root user before continuing with the installation. To prepare the silent installation parameters file 1 Prepare the parameter information you will need for the installation. ensure that a CONTROL-M/Server database has been installed. Explanations are provided in Table 12 on page 77.sh WARNING If the security settings at your site do not allow the “ping” command to be used. the CONTROL-M/Server database was prepared automatically. Chapter 5 Installing CONTROL-M/Server 75 . 7 Issue the following command to activate the silent installation script: <dvdPath>/setup. 5 Log in to the CONTROL-M/Server account. The installation parameters are saved to ${HOME}/BMCINSTALL/PRODUCTS. For information on setting variables.Silent installation When the installation is run using the prepared parameters file. set the BMC_SKIP_PING environment variable to Y before running setup. ensure that the database server is up and running (see “Ensuring Oracle Availability on UNIX” on page 73). If you installed a BMC Software dedicated Oracle database server. 2 On an existing database server. You can reuse this parameters file to silently install CONTROL-M/Server on other computers. see “Setting environment variables in UNIX” on page 37. 8 Follow the interactive menu instructions specifying parameter values as requested.CTL.sh. see Appendix I. CONTROL-M/Server is installed using the parameters you specified in the previous step. you must also complete the procedures listed under “Setting up the CONTROL-M/Server UNIX cluster environment” on page 183. <sysAdminPassword> system administrator password (required for a PostgreSQL installation). Where to go from here 1 Install the latest fix pack to apply the most recent software updates. 3 If this is a cluster installation. 2 Perform the post-installation configuration tasks specified in Chapter 6. manually modify them in the parameters file. <parameterPath> is the full path to the silent installation file that was created in step 7of “To prepare the silent installation parameters file” on page 75. “Post installation for CONTROL-M/Server”. 2 Set the following environment variables (see “Verifying operating system levels and patches” on page 38 for your UNIX environment): ORG_DBO_PASSWORD to <temporaryPassword> DBO_PASSWORD to <newDboPassword> SA_PASSWORD to <sysAdminPassword> <temporaryPassword> is the temporary password given to the dbo during the database installation. 76 CONTROL-M Installation Guide .sh -r <parameterPath> <dvdPath> is the path of the mounted DVD. To install silently 1 Log in to the CONTROL-M/Server account.Where to go from here If you want to change parameter values. 3 Issue the following command: <dvdPath>/setup. <newDboPassword> is the dbo password that will be set. The value for this parameter must be a number from 1024 through 65533. Chapter 5 Installing CONTROL-M/Server 77 . Verify that the two port numbers are not used for any other purpose on the Server platform. UMBER Default: 2369 CONTROL-M/EM TCP/IP Port Number [SETP]/BMC/SERVER/OUTPUT_S PN CONTROL-M/EM TCP/IP port number.Where to go from here NOTE After completing the installation. Table 12 CONTROL-M/Server – UNIX database and application installation parameters (Part 1 of 4) Active installation parameter name Agent-to-Server Port Number Silent installation parameter name Description [SETP]/BMC/SERVER/AGENT_TO Listening port in the Server computer that _SERVER_PORT receives data from all Agent computers. Range: 1024-32767 Default: 2370 Data Device Physical Full Path File Name N/A Specify a new file name which includes the full path to the physical device where the CONTROL-M/EM database resides. The value specified must match the value assigned to the Agent-to-Server Port Number parameter on all Agent computers. CONTROL-M communicates with [SETP]/BMC/SERVER/INPUT_SPN CONTROL-M/EM using a pair of consecutive TCP/IP ports (for example. Default: LATIN1 CONTROL-M/Server Configuration Agent Configuration [SETP]/BMC/SERVER Agent Port Number /CTM_CONFIG_AGENT_PORT_N port number. Default: 7005 CJK [SETP]/BMC/POSTGRES/UTF_MO Sets language mode to either standard (Latin1) DE_STR or western languages (UTF8) mode. 2370 and 2371). This parameter specifies the lower of the two port numbers and must correspond to the value for TCP/IP Port Number in the CONTROL-M definition in the CONTROL-M/EM Data Centers window. Verify that this port number is not used for any other purpose in this Server computer. you must close the current session and open a new one before working with CONTROL-M/Server. The higher port passes data in the reverse direction. The lower port passes data from CONTROL-M to CONTROL-M/EM. Specify a numeric value between 1024 and 65535. Database scalability [SETP]/BMC/POSTGRES/DATABA Size of the CONTROL-M database (Small. The password must begin with a letter (A-Z. a-z) followed by up to 17 alpha-numeric characters (includes underscores). SE_SERVER_MEMORY_MODEL Medium. Large).Where to go from here Table 12 CONTROL-M/Server – UNIX database and application installation parameters (Part 2 of 4) Active installation parameter name Silent installation parameter name Description Data Directory Full Path [SETP]/BMC/POSTGRES/DATABA Full path to data directory (In the case of an SE_DATA_PATH existing installation. a-z) followed by 5 to 29 alphanumeric characters (includes underscores). Default: Medium Host Name Interface Name N/A Host name of the computer on which the PostgreSQL database server is installed Inter Process Communication Port Number [SETP]/BMC/SERVER /IPC_PORT Port number used for communication between CONTROL-M processes. Default: ctmuser Database Owner Password N/A Set a password for the CONTROL-M/Server database owner. the directory must exist and be empty. The name must begin with a letter (A-Z. This parameter replaces the Input Mailbox Key and Output Mailbox Key parameters in earlier versions of CONTROL-M/Server.) Database Administrator Password N/A Database Name [SETP]/BMC/POSTGRES/DATABA Database name to be created. SE_NAME Database Owner Login [SETP]/BMC/POSTGRES/DATABA Full installation with creation of a new SE_OWNER_NAME database: Password of the database administrator. Range: 1025-32767 Default: 6005 78 CONTROL-M Installation Guide . Name for the CONTROL-M/Server database schema owner. (Dual IP addresses are often specified for load balancing purposes). The default value for this parameter is the default host interface name defined in the CONTROL-M/Server computer operating environment. 192. N/A [SETP]/BMC/END_USER_LOG_FIL Progress log file E N/A [SETP]/BMC/DEV_USER_LOG_FIL Trace log file E PostgreSQL Server Host Name [SETP]/BMC/POSTGRES/DATABA Host name of the computer on which the SE_SERVER_HOST PostgreSQL database server is installed PostgreSQL Server Port Number [SETP]/BMC/POSTGRES/DATABA The TCP/IP port that the PostgreSQL database SE_SERVER_PORT_NUMBER server listens to for communication from CONTROL-M/EM.20). Note: ■ CONTROL-M does not support dual IP addresses for single computers in the DNS (Domain Naming System).186. Ethernet and Token-Ring). run the nslookup utility and verify that the domain name resolves to one IP address. If your operating system supports dual IP addresses.123. Default: 5432 Chapter 5 Installing CONTROL-M/Server 79 . specify the Virtual Server Name. Note: ■ When installing on a computer that supports clustering.Where to go from here Table 12 CONTROL-M/Server – UNIX database and application installation parameters (Part 3 of 4) Active installation parameter name Silent installation parameter name Description Local IP Host Interface Name [SETP]/BMC/SERVER/LOCAL_IP_ HOST Host interface name of the TCP/IP network interface card on the CONTROL-M/Server platform. This parameter can also be specified by its IP address (for example. This name is used for communication with CONTROL-M/Server and is typically the host name of the CONTROL-M/Server computer. It should be modified only if the CONTROL-M/Server platform contains more than one network interface card (for example. run the following command under a root user: <ctm_Home >/ctm_server/scripts/ctm_etcservices 2 At the message prompt. Default: 7006 System data location [SETP]/BMC/POSTGRES/DATABA (For dedicated installation only) – Full path to SE_SERVER_PATH the PostgreSQL system database Record port usage The /etc/services file contains a description of the usage of each port on the CONTROL-M/Server platform. The value specified must match the value assigned to the Server-to-Agent Port Number parameter (for this Agent) on the Agent computer. Proper maintenance of this file helps prevent conflicting usage of ports by various applications.conf CONTROL-M/Server can also be installed on an MSSQL database. type y to update the /etc/services file. Information on the PostgreSQL existing installation is in the following file: <CONTROL-M/Server with PostgreSQL Server folder>\pgsql\etc\pg_service. ensure that you know the PostgreSQL port and host. Installing CONTROL-M/Server on Windows The default installation installs a dedicated Embedded PostgreSQL database server automatically in the background as part of the CONTROL-M/Server installation – no interaction is required. Verify that this port number is not used in the Agent for any other purpose.Installing CONTROL-M/Server on Windows Table 12 CONTROL-M/Server – UNIX database and application installation parameters (Part 4 of 4) Active installation parameter name Silent installation parameter name Description Server-to-Agent Port Number [SETP]/BMC/SERVER/SERVER_T O_AGENT_PORT Listening port in the Agent computer that receives data from this Server computer. 1 To save all operations and communications parameters in the file etc/services. you must ensure that an MSSQL database server and necessary client software are installed before installing CONTROL-M/Server. Before installing CONTROL-M/Server with PostgreSQL in existing mode. 80 CONTROL-M Installation Guide . Ports reserved for CONTROL-M/Server use should be recorded here. Specify a numeric value between 1024 and 65535. In this case. ensure that the following criteria exist: ■ ■ The UNIX user under which the PosgreSQL database server is running must have write permissions to the data location directory. Chapter 5 Installing CONTROL-M/Server 81 .bat /vBMC_SKIP_PING=”Y” 4 Follow the instructions on the screen. 2 If this is a cluster installation. After the installation is complete. database <database> was created in the default location and not in the specified location <location> You can safely ignore this message. check the information in the %TEMP%\ctm640_user_log. filling in parameter values as necessary (see Table 13 on page 84).Interactive installation NOTE When installing CONTROL-M/Server using an existing PosgreSQL database server on UNIX. the setup.bat command must be issued from the command line as follows: setup. Interactive installation 1 Log in as a user that has administrator privileges on the current computer. the following message is displayed. WARNING If the security settings at your site do not allow the “ping” command to be used. 3 Insert the installation DVD and run setup. NOTE When you install the product on an existing PostgreSQL database on Windows.txt file to ensure that the installation ended successfully. The data location directory must be empty. prepare the installation by first implementing the criteria discussed under “Creating cluster resources for Windows” on page 154.bat. CONTROL-M/Server is installed using the parameters you specified in the previous step. and run the following command: <drive>\prep_silent. the information you enter is stored in a batch file. 2 Perform the post-installation configuration tasks specified in Chapter 6. The following stages are involved: ■ Preparing the batch file This is accomplished by running a silent installation preparatory procedure from the installation DVD. Instead. Silent installation is used to install CONTROL-M/Server from a batch file. ■ Running the prepared batch file When the prepared batch file is run. The preparatory procedure behaves like the interactive installation procedure and prompts you to enter the same information. 3 If this is a cluster installation. you must also complete the procedures listed under “Setting up the CONTROL-M/Server Windows cluster environment for PostgreSQL” on page 185. “Post installation for CONTROL-M/Server”. However no installation is performed. you must first map the DVD drive and assign a drive letter.Where to go from here Where to go from here 1 Install the latest fix pack to apply the most recent software updates. To prepare the silent installation batch file 1 If the installation DVD will be accessed through a network. 2 Insert the installation DVD into the mapped drive. You can reuse this batch file to silently install CONTROL-M/Server on other computers. Silent installation NOTE Silent installation of CONTROL-M/Server is not supported for Microsoft Windows cluster environments. navigate to the installation folder.bat 82 CONTROL-M Installation Guide . After making the change.txt file to ensure that the installation ended successfully. 2 If the BMC_CTMSRV_silent. NOTE When you install the product on an existing PostgreSQL database on Windows.bat 4 After the installation is complete. The parameters are saved to: %TEMP%\BMC_CTMSRV_silent.bat file will be accessed through a network. run the modified prep_silent. the “%Source_dir%setup. 3 Open a command prompt window. database <database> was created in the default location and not in the specified location <location> You can safely ignore this message. and run the silent installation by issuing the following command: <path>\BMC_CTMSRV_silent. navigate to the path where the BMC_CTMSRV_silent.bat file from the local drive.bat” /s /v”BMC_SILENT_INSTALL=\”Y\” BMC_SKIP_PING= \”Y” /l*v \”%InstallLogFile%\”” It is necessary to copy the prep_silent. the following message is displayed..bat”. To install silently 1 Log in to the target computer using an ID with administrator privileges. 3 After selecting the type of installation required and entering the necessary parameters values at the prompts. select Save & Exit to save the parameters.. line in the prep_silent.bat file to a local drive to facilitate this change. Chapter 5 Installing CONTROL-M/Server 83 . check the information in the %TEMP%\ctmsrv640_silent_log.bat file now resides.bat file must be modified as follows: “%Source_dir%setup.Silent installation WARNING If the security settings at your site do not allow the “ping” command to be used. you must first map the DVD drive and assign a drive letter.bat. Where to go from here Where to go from here 1 Install the latest fix pack to apply the most recent software updates. NAME 84 CONTROL-M Installation Guide Amount of space (in MB) to allocate for the data portion of the database. 2 Perform the post-installation configuration tasks specified in Chapter 6. you must also complete the procedures listed under “Setting up the CONTROL-M/Server Windows cluster environment for PostgreSQL” on page 185. You must take into consideration the number of jobs in the Active Jobs file. . Data Device Physical Full Path File Name CTMSRV_DATA_DEVI Specify a new filename that includes the full path to the CE_PATH physical device where the CONTROL-M/Server database resides. The value specified must match the value assigned to the Agent-to-Server Port Number parameter on all Agent computers. 2370 and 2371). a-z) followed by up to 29 alphanumeric characters (includes underscores). RT_NUM CONTROL-M communicates with CONTROL-M/EM using a pair of consecutive TCP/IP ports (for example. The lower port passes data from CONTROL-M to CONTROL-M/EM. The name Database Name NAME must begin with a letter (A-Z. 3 If this is a cluster installation. Verify that the two port numbers are not used for any other purpose on the Server platform. Table 13 CONTROL-M/Server – Windows database and application parameters (Part 1 of 3) Active installation parameter name Silent installation parameter name Agent-to-Server Port Number CTMSRV_AGENT_TO_ Listening port in the Server computer that receives data SERVER_PORT_NUM from all Agent computers. CONTROL-M/Server CTMSRV_DATABASE_ Name for the CONTROL-M/Server database. This parameter specifies the lower of the two port numbers and must correspond to the value for TCP/IP Port Number in the CONTROL-M definition in the CONTROL-M/EM Data Centers window. The higher port passes data in the reverse direction. Default: 7005 CONTROL-M/EM TCP/IP Port Number CTMSRV_CTMEM_PO CONTROL-M/EM TCP/IP Port Number. Description Range: 1024-32767 Default: 2370. “Post installation for CONTROL-M/Server”. Data Device Size CTMSRV_DATA_SIZE Database Administrator Login CTMSRV_DBA_USER_ Name of the database administrator. Verify that this port number is not used for any other purpose in this Server computer. Specify a numeric value between 1024 and 65535. Range: 1025-32767 Default: 6005 Chapter 5 Installing CONTROL-M/Server 85 . The name must begin with a letter (A-Z. All selected components are installed in subdirectories under this folder. a-z) followed by 5 to 29 alphanumeric characters (includes underscores). SERVER_NAME Data tablespace size CTMSRV_COMBO_DB Size of CONTROL-M/Server database (small. Set a password for the CONTROL-M/Server database owner. The folder you specify in this window becomes the home folder for CONTROL-M/Server. Database Owner Password CTMSRV_DBO_PASS WORD Database Server Name CTMSRV_DATABASE_ Name of the MSSQL database server. a-z) followed by up to 29 alphanumeric characters (includes underscores). Destination Folder INSTALLDIR Description Password of the database administrator. Default: medium.Where to go from here Table 13 CONTROL-M/Server – Windows database and application parameters (Part 2 of 3) Active installation parameter name Silent installation parameter name Database Administrator Password CTMSRV_DBA_PASS WORD Database Owner Login CTMSRV_DBO_USER_ Set a name for the CONTROL-M/Server database NAME schema owner. medium. Default: <drive>:\Program Files\BMC Software\CONTROL-MServer Inter Process Communication Port Number CTMSRV_IPC_PORT_ NUM Port number used for communication between CONTROL-M processes. The password must begin with a letter (A-Z. SIZE large). This parameter replaces the Input Mailbox Key and Output Mailbox Key parameters in earlier versions of CONTROL-M/Server. Server-to-Agent Port Number CTMSRV_SERVER_TO Listening port in the Agent computer that receives data _AGENT_PORT_NUM from this Server computer. The recommended amount is 1/3 of the data device size. Log Device Size CTMSRV_LOG_SIZE Amount of space (in MB) to allocate for the transaction log. Specify a numeric value between 1024 and 65535. PostgreSQL Service user name SRV_NON_ADM_USE R Set a user name for the PostgreSQL Windows Service. a-z. The default value for this parameter is the default host interface name defined in the CONTROL-M/Server computer operating environment. 192. Default: 7006 86 CONTROL-M Installation Guide . The name can contain up to 20 alphanumeric characters (A-Z. Log Device Physical Full Path File Name CTMSRV_LOG_DEVIC Specify a new filename that includes the full path to the E_PATH_ physical device where the CONTROL-M/Server database log resides.20). This name is used for communication with CONTROL-M/Server and is typically the host name of the CONTROL-M/Server computer. run the nslookup utility and verify that the domain name resolves to one IP address. It should be modified only if the CONTROL-M/Server platform contains more than one network interface card (for example. Note: ■ When installing on a computer that supports clustering. specify the Virtual Server Name. PostgreSQL Service password SRV_NON_ADM_USE R_PASSWORD Set a password for the PostgreSQL Windows service according to the operating system security policy. This parameter can also be specified by its IP address (for example. and underscores). The value specified must match the value assigned to the Server-to-Agent Port Number parameter (for this Agent) on the Agent computer. Note: ■ CONTROL-M does not support dual IP addresses for single computers in the DNS (Domain Naming System).186. If your operating system supports dual IP addresses. (Dual IP addresses are often specified for load balancing purposes). Ethernet and Token-Ring).Where to go from here Table 13 CONTROL-M/Server – Windows database and application parameters (Part 3 of 3) Active installation parameter name Silent installation parameter name Local IP Host Interface Name CTMSRV_LOCAL_IP_ HOST_INTERFACE_N AME Description Host interface name of the TCP/IP network interface card on the CONTROL-M/Server platform. Verify that this port number is not used in the Agent for any other purpose. hyphens.123. 0-9. . . . . . . 87 89 89 89 90 90 Modifying the automatic startup procedure for CONTROL-M/Server (UNIX) The database server and CONTROL-M/Server should be running at all times on the primary server platform. . . . . . . . . . . . Where to go from here. . . . . . Using NFS with CONTROL-M/Server (UNIX) . . . . . . . . . . . . . . . . . . . . . . . You can modify the startup procedure to ensure that the database server. . . Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows) . . . Chapter 6 Post installation for CONTROL-M/Server 87 . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Server. . . . . . . . . . . . . . . . . . . . . . . NOTE Do not perform this procedure when installing CONTROL-M/Server on a mirror (backup) environment. . . . BMC Software recommends that they be started at system startup time. and the CONTROL-M/Server Configuration Agent are started during system startup. . . . . . . .Chapter 6 Post installation for CONTROL-M/Server 6 The following topics are discussed in this chapter: Modifying the automatic startup procedure for CONTROL-M/Server (UNIX) . . . . . . . . . . . The command to copy the necessary startup instructions to your system startup directory is listed below. . . . . . . . . . . . . . . Persistent connection between CONTROL-M/Server and CONTROL-M/Agent . . . Setting the protocol version for the upgraded CONTROL-M/Agent . . . . . . d/S98ctm640 For Linux cp <ctmHome>/ctm_server/data/rc.d/S98<controlmUser> EXAMPLE cp /home/controlm/ctm_server/data/rc.d/<controlmUser>/sbin/rc2.<controlmUser> /etc/rc2.<controlmUser> EXAMPLE For a user called controlm.d/S98<controlmUser> EXAMPLE cp /home/controlm/ctm_server/data/rc.d/S98<controlmUser> EXAMPLE cp /home/controlm/ctm_server/data/rc.<controlmUser> /etc/ Open the /etc/inittab file in an editor.<controlmUser> /etc/rc. and append the following line at the end of the file.d/ctm640 ln -s /sbin/init.d/rc2.d/S98ctm640 For SuSE. run the following command after coping the file: >SuSEconfig 88 CONTROL-M Installation Guide .<controlmUser> /sbin/init.d/S98ctm640 For Solaris cp <ctmHome>/ctm_server/data/rc.ctm640 For HP-UX cp <ctmHome>/ctm_server/data/rc.ctm640 /etc/rc. specify the following command: cp /home/controlm/ctm_server/data/rc.d/rc2.d/ctm640 /sbin/rc2. <controlmUser>:2:respawn:/etc/rc.ctm640 /sbin/init.ctm640 /etc and in file /etc/inittab add: controlm:2:respawn:/etc/rc.ctm640 /etc/rc2.d/<controlmUser> ln -s /sbin/init.Modifying the automatic startup procedure for CONTROL-M/Server (UNIX) For AIX cp <ctmHome>/ctm_server/data/rc. select Parameter Customization => Parameters for Communicating with Specific Agent Platforms. diana. and ctm_server/temp directories to NFS. B 07 for version 6. 3 For older versions of CONTROL-M/Agent. For more details about how and when a persistent connection should be used.Persistent connection between CONTROL-M/Server and CONTROL-M/Agent Persistent connection between CONTROL-M/Server and CONTROL-M/Agent A persistent connection allows CONTROL-M/Server to maintain a constant connection with the CONTROL-M/Agent and can enable improved connectivity between Server and Agent.save.01. Chapter 6 Post installation for CONTROL-M/Server 89 .2. From the menu. set the Communication Protocol Version to: A 06 for version 6. ctm_server/status. Using NFS with CONTROL-M/Server (UNIX) 1 Verify that CONTROL-M/Server is shut down. ctm_server/proclog. 3 Delete the copied directories from the local disk. The Communicating with Specific Agent Platform (diana) menu is displayed. The following prompt is displayed: To view/modify communication parameters. see the CONTROL-M Administrator Guide. 2 Copy the ctm_server/proclog. for example. Setting the protocol version for the upgraded CONTROL-M/Agent Use the following steps to set the Protocol Version for an upgraded Agent in CONTROL-M/Server: 1 Enter the command ctm_menu to display the CONTROL-M Main Menu. enter node ID of Agent Platform: 2 Enter the node ID of a CONTROL-M/Agent.3.01. click OK. Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows) If after installation. Where to go from here You have now completed the installation of CONTROL-M/Server. perform the following action: 1 Open the Control Panel 2 Select system 3 In the System Properties window. select the Advanced tab 4 click the Environment Variables button 5 In the Environment Variables window.Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows) 4 Place a soft link on the local disk under the $HOME/ctm/ directory to point to the new NFS location for each of the copied directories. 90 CONTROL-M Installation Guide . CONTROL-M utilities are not recognized in command prompt mode. 5 Start CONTROL-M/Server. . . . . . . . . . . . . . . . . . . . 91 Silent installation or upgrade. . 98 Where to go from here . . . . . . . . . . . . . . . . . . . . . 95 Silent installation . . . . . . . . . . . . . . 4 If this is an upgrade installation. . . . . . . . . . . . . . . . . . . . . 100 Installing CONTROL-M/Agent on UNIX The following sections describe how to install and upgrade CONTROL-M/Agent for UNIX. . . . Interactive installation or upgrade 1 Ensure that the installation CD is mounted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Interactive installation or upgrade . . . . . . . . . . . . . . . . . . . . . 95 Installing CONTROL-M/Agent on Windows. . . . . . . . . . . . . . 93 Where to go from here . . . . . . ensure that CONTROL-M/Agent is not running Chapter 7 Installing CONTROL-M/Agent 91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The following topics are discussed in this chapter: Installing CONTROL-M/Agent on UNIX . . . . . . . . 3 Navigate to the target installation directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Log in as the root user. . . . . 95 Interactive installation or upgrade . . . . . . . . . . . .Chapter 7 7 Installing CONTROL-M/Agent This chapter describes how to install and upgrade CONTROL-M/Agent on UNIX and Windows. . . . . . . . . . . . . . . . . . . . . Use '|' to separate between host names. NOTE The installation log can be found in the home directory of the CONTROL-M/Agent account. If a previous version of CONTROL-M/Agent is detected.01_user. In this case. Description If the CONTROL-M/Server is in a cluster. Verify that this port number is not used in the Agent for any other purpose.6.log <agentHome> is the path of the CONTROL-M/Agent home directory. The value specified must match the value assigned to the Server-to-Agent Port Number parameter (for this Agent) in the CONTROL-M/Server configuration.Interactive installation or upgrade 5 Use the following command to run the installation script: <cdPath>/Unix/setup. filling in parameter values and fields as necessary. the parameters values from the previous version are used. Follow the instructions on the screen. Authorized CONTROL-M/Server Host 92 AUTHORIZED_CTRLM Specifies one or more CONTROL-M/Servers that will _HOSTS be authorized to submit jobs to this agent. CONTROL-M Installation Guide . Specify a numeric value between 1024 and 65535. Table 14 Installation Parameters .CONTROL-M/Agent on UNIX (Part 1 of 2) Active installation parameter name Silent installation parameter name Server to Agent Port number SRV_2_AGT_PORT Listening port in the Agent computer that receives data from this Server computer. Default: 7006 Primary CONTROL-M/Server Host CTRLM_HOST The host name of the computer on which CONTROL-M/Server is installed. The parameters and fields for this installation are described in Table 14.sh <cdPath> is the path of the mounted CD. the CONTROL-M/Server Network Name is required. for example: <agentHome>/BMCINSTALL/log/DRKAI.4. an upgrade is performed. Default: 7005. the information you enter is stored in a parameters file. Verify that this port number is not used for any other purpose in this Server computer. CONTROL-M/Agent is installed using the parameters you specified in the previous step. The preparatory procedure behaves like the interactive installation procedure and prompts you to enter the same information. However no installation is performed. The value specified must match the value assigned to the Agent-to-Server Port Number in the CONTROL-M/Server configuration. The locale must be already defined on the system. Silent installation or upgrade Silent installation is used to install or upgrade CONTROL-M/Agent from a parameters file. Chapter 7 Installing CONTROL-M/Agent 93 . “Post installation for CONTROL-M/Agent. Description Where to go from here 1 Install the latest fix pack to apply the most recent software updates. Specify a numeric value between 1024 and 65535. The following stages are involved: ■ Preparing the parameters file This is accomplished by running a silent installation preparatory procedure from the installation CD.Silent installation or upgrade Table 14 Installation Parameters . This parameter is used only with latin1 characters sets. 2 Perform the post-installation configuration tasks specified in Chapter 8. Locale AGT_LOCALE Set the locale to the local language. ■ Running the installation using the prepared parameters file When running the installation using the prepared parameters file.CONTROL-M/Agent on UNIX (Part 2 of 2) Active installation parameter name Silent installation parameter name Agent-to-Server Port Number AGT_2_SRV_PORT Listening port in the Server computer that receives data from all Agent computers. Instead. If a previous CONTROL-M/Agent installation is detected. To prepare the silent installation or upgrade parameters file 1 Prepare all the information you will need for the installation. 94 CONTROL-M Installation Guide . and bash shell users: BMC_SILENT_INSTALL=Y export BMC_SILENT_INSTALL For csh/tcsh shell users: setenv BMC_SILENT_INSTALL Y 6 Activate the installation script with the following command: <cdPath>/Unix/setup.sh 7 Follow the interactive menu instructions specifying parameter values as requested. 2 Log in as the root user. The installation parameters are saved to ${HOME}/BMCINSTALL/PRODUCTS. the current parameters and their values are displayed. 3 Navigate to the CONTROL-M/Agent target directory. ensure that CONTROL-M/Agent is not running 5 Set the environment variable named BMC_SILENT_INSTALL to Y as follows: For sh.Silent installation or upgrade TIP You can reuse the parameters file to silently install CONTROL-M/Agent on other computers. 4 If this is an upgrade installation. Parameter explanations are provided in Table 14 on page 92. ksh.CTL A copy of the parameters file is saved to ${HOME}/BMCINSTALL/installed/agent on each Agent installed. Where to go from here 1 Install the latest fix pack to apply the most recent software updates. “Post installation for CONTROL-M/Agent.sh -respond <parameterPath> <cdPath>is the path of the mounted CD. 2 Navigate to the CONTROL-M/Agent home directory. Chapter 7 Installing CONTROL-M/Agent 95 . <parameterPath> is the full path to the parameters file that was created as described under “To prepare the silent installation or upgrade parameters file” on page 94. Installing CONTROL-M/Agent on Windows Interactive installation or upgrade 1 Log in to a user account belonging to the local Administrators group.Where to go from here NOTE In a new installation you can modify parameter values by editing the parameter file using a text editor. you must add each parameter and its new value to the parameters file. 2 If CONTROL-M/Agent is monitored by an application (for example. To install silently 1 Log in as the root user. you must shut down the monitoring application before beginning an upgrade installation. BMC Software Patrol Agent) that ensures it remains running. 2 Perform the post-installation configuration tasks specified in Chapter 8. To change existing parameter values during an upgrade installation. 3 Use the following command to run the parameters file: <cdPath>/Unix/setup. you may receive a Microsoft warning about running the BMC Software installation file.txt Table 15 CONTROL-M/Agent – Installation parameters (Part 1 of 2) Parameter Description Agent Name CONTROL-M/Agent is identified by a logical name.6.txt For Itanium 64 Bit: %TEMP%\DRNDN. Local: Installs an Agent locally without joining it to the existing cluster environment. 3 If this is a cluster installation.bat.6.01_trace_log_win32. The parameters and fields for this installation are described in Table 15. You can safely ignore this message. and double-click Setup. This name is used in the command line for CONTROL-M/Agent utilities to indicate which agent should handle the command. 4 Follow the prompts to complete the installation.Interactive installation or upgrade 3 Insert the installation CD in the CD-ROM drive.txt ForAMD 64 Bit: %TEMP%\DRNDN. If the Autorun option is not enabled.01_trace_log_win64. NOTE Depending on your Windows security settings. 2 Perform the post-installation configuration tasks specified in Chapter 8.4. If the Autorun option is enabled. installation starts automatically and the opening screen is displayed. Setup Type Type of Agent installation on a cluster enabled environment: Cluster: Installs an Agent in a cluster enabled environment. 96 CONTROL-M Installation Guide . you must also complete the procedures listed under “Updating CONTROL-M/Agent system path information on cluster installations” on page 188. browse to the Windows folder on the CD-ROM drive.6. NOTE The installation log is located in the following folders: For 32 Bit: %TEMP%\DRNDN.4.4.01_trace_log_win64AMD. Where to go from here 1 Install the latest fix pack to apply the most recent software updates. “Post installation for CONTROL-M/Agent. click Change and Browse to the desired location. The value specified must match the value assigned to the Agent-to-Server Port Number parameter on CONTROL-M/Server. not IP addresses. Specify a numeric value between 1024 and 65535. If the CONTROL-M/Server is in a cluster. Primary CONTROL-M/ Server Host Indicates the host name of the computer where CONTROL-M/Server is installed. Authorized CONTROL-M/ Server Hosts Names of all CONTROL-M/Server hosts authorized to send requests to this Agent. The primary CONTROL-M/Server host must be included if it will send requests to this Agent. Select the Network resource Select the Network Name resource that was created for this Agent. Use the “|” symbol to separate host names. including backup hosts. Name of the computer hosting the CONTROL-M/Server that submits requests to this Agent. not an IP address. The value specified must match the value assigned to the Server-to-Agent Port Number parameter (for this Agent) on CONTROL-M/Server. Verify that this port number is not used for any other purpose. Default: Computer on which the installation was made. the CONTROL-M/Server Network Name is required. Default: 7005 Server-toAgent Port Number Listening port of this Agent that receives data from the Server.Interactive installation or upgrade Table 15 CONTROL-M/Agent – Installation parameters (Part 2 of 2) Parameter Description Destination Folder Indicates the location in which the Agent will be installed. Chapter 7 Installing CONTROL-M/Agent 97 . Agent-toServer Port Number Listening port in the Server computer that receives data this Agent. Verify that this port number is not used in the Server for any other purpose. To change the installation folder. Cluster Management This display-only field indicates the order in which clusters will perform failover handling. Note: Specify names. Specify a numeric value between 1024 and 65535. Default: Name of the primary CONTROL-M/Server host. Note: Specify a name. Select the Disk resource Select the Disk resource for this Agent. Do not include spaces between host names. Default: 7006 Clustering Parameters Select a group Highlight the virtual server group for which this Agent’s IP address and the Network Name were created. Insert the Installation CD.01Silent.01Silent. Run the following command: %TEMP%\DRNDN.4.6.mm> entry to the Start => Programs menu. If necessary. The silent installation procedure adds a CONTROL-M Agent <vv. Log in using a user ID having Administrator privileges on the current computer. UNC mapping can also be used. 98 CONTROL-M Installation Guide .bat file. Run (double-click) the prep_silent.bat file. This requires placing the parameters that you would normally enter in interactive mode into a file that is accessed by the silent installation procedure.4. 1 Prepare the installation parameters: A.bat C. D. Browse to the Windows folder of the CD-ROM drive. The silent installation procedure can be used to install a single Agent each time it is run. B. B.rr.01Silent.6. C.bat 2 Run the silent installation procedure: A. Check the %TEMP%\DRNDN6. The parameters are saved in the following file: %TEMP%\DRNDN.4. Ensure that the installation CD used in Step 1 is still available.txt file to ensure that the installation ended successfully. NOTE The same batch file can be copied to other computers and used to create several identical installations. you can modify the CD source mapping by altering the Auto_CD_ Image variable in the DRNDN.6.01_silent_log.4.Silent installation Silent installation The silent installation procedure can be used to install CONTROL-M/Agent as a batch job instead of using the interactive installation procedure. Silent installation Table 16 Silent installation parameters (Part 1 of 2) Parameter Description AgentName Logical name of this Agent installation. Default: 7006 Note: Specify a numeric value from 1024 to 65535. CTMAG_AgentToServerPort Port number used by the CONTROL-M/Agent platform for receiving data from the CONTROL-M/Server platform (Agent-to-Server port number). Embedded blanks are not allowed. Valid values are: ■ ■ CTMAG_DOMAIN Y – Jobs are submitted under the user and password specified by the CTMPWD utility. Default. TLVS2K038|VGW1K|FPB62G Note: Specify a computer name.|hostn. not an IP address. Default: 7005 Note: Specify a numeric value from 1024 to 65535. Default: Name of the computer where installation is performed.” (period) CTMAG_DFTRRT Default printer for job output (sysout) files.. Chapter 7 Installing CONTROL-M/Agent 99 . Domain from which the log in will be performed. DestinationFolder Name of the installation folder. Note: Specify a computer name.. Example. Valid values: <domainName> " " (Blank) “. CTMAG_TCP_Timeout TCP/IP Timeout (in seconds). CTMAG_PermittedServers List of authorized CONTROL-M/Servers. Valid values: numeric value greater than or equal to zero. N – Jobs are submitted under the current user and password. or specified by the owner identification settings in the CONTROL-M Configuration Manager. Default: <drive>\Program Files\BMC Software\CONTROL-M Agent\ <drive> identifies the drive where Program Files are defined in this computer CTMAG_ServerHostName Name of host computer for the primary CONTROL-M/Server that handles this Agent. CTMAG_ServerToAgentPort Port number used by the CONTROL-M/Server platform for receiving data from the CONTROL-M/Server platform (Server-to-Agent port number). Syntax: host1|host2|. Default: 60 CTMAG_LOGON_AS_USER Job submission method. The separator is a vertical line. Specify a printer name. not an IP address. These hosts are all authorized to submit jobs for processing. This name is used to differentiate between multiple installations of CONTROL-M/Agent on the same computer. including the primary CONTROL-M/Server. Specify a user account with full privileges in the administrative group. 100 CONTROL-M Installation Guide . user_company. User under which the CONTROL-M/Server service will run. for example. Default. see above). CTMAG_SRV_PASS User password. 2 Perform the post-installation configuration tasks specified in Chapter 8. Note: This option can be used only if the service is set to run under a specified user account (defined by specifying LOGONACCOUNTTYPE= "0". Valid values: ■ ■ CTMAG_SRV_USER Y – Job object statistics are sent to sysout. “Post installation for CONTROL-M/Agent.Where to go from here Table 16 Silent installation parameters (Part 2 of 2) Parameter Description CTMAG_JO_STATISTIC Flag that indicates whether job object statistics are sent to sysout. Default: 7009 Where to go from here 1 Install the latest fix pack to apply the most recent software updates. CTMAG_TRACKER_EVENT_ The tracker event port enables CONTROL-M/Agent to receive updates PORT regarding job status from all Control Modules that are associated with the current CONTROL-M/Agent. N – Job object statistics are not sent to sysout.com\user. . . . . . . . . . Changes to system files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade with CONTROL-M Option for Oracle Applications installed . .dat file and restart the Agent: PROCLOG_MODE 666 The permissions on NFS for both the sysout directory and the proclog directory must be 777. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from CONTROL-M/Agent version 6. . . . Modifying the automatic startup procedure for CONTROL-M/Agent . . . . . . . . .Chapter 8 Post installation for CONTROL-M/Agent 8 The following topics are discussed in this chapter: Setting CONTROL-M/Agent file permissions for NFS (UNIX) . . . . . . . . . .0. . . .dat file and restart the Agent: SYSOUT_MODE 666 If you have chosen to put the proclog directory on an NFS file system. . . . . . . . . . . . . Chapter 8 Post installation for CONTROL-M/Agent 101 . . . . . . . . . . . . . . . . . . . . . Where to go from here. . . add the following line to the ctm/data/OS. . . . . . . . . . . . . . . .1 or earlier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 102 102 103 103 103 104 104 Setting CONTROL-M/Agent file permissions for NFS (UNIX) If you have chosen to put the sysout directory on an NFS file system. . . . .2. . . Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows). . . . . . add the following line to the ctm/data/OS. . . Upgrade with CONTROL-M Option for PeopleSoft installed . . . . . . . . . . Modifying the automatic startup procedure for CONTROL-M/Agent BMC Software recommends that you start CONTROL-M/Agents automatically at system startup time. select the Advanced tab 4 click the Environment Variables button 5 In the Environment Variables window. rc. 102 CONTROL-M Installation Guide . CONTROL-M utilities are not recognized in command prompt mode. You should consult your system administrator for the correct commands with regard to CONTROL-M/Agent on the platform you are using.agent_user. Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows) If after installation. a ready-made startup script. perform the following action: 1 Open the Control Panel 2 Select system 3 In the System Properties window.Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows) In addition. NOTE CONTROL-M/Agents that were shut down manually are not restarted by the automatic startup procedure during a shutdown-restart operation. click OK. During installation of CONTROL-M/Agent. see “Setting the protocol version for the upgraded CONTROL-M/Agent” on page 89. is placed in <agentInstallDir>/ctm/scripts. Default: ctmagent <socketType> Socket type used for the service (stream for tcp).1 or earlier This section specifies the changes that are implemented when CONTROL-M/Agent is upgraded from previous versions.1 or earlier Upgrading from CONTROL-M/Agent version 6. $CONTROLM/ Path of CONTROL-M/Agent user home directory. perform the following steps before upgrading CONTROL-M/Agent to the new version. The following line is removed from the /etc/inetd.conf file or the /etc/xinetd. 2.2.0. Chapter 8 Post installation for CONTROL-M/Agent 103 .2. <agentExe> Path of CONTROL-M/Agent executable files.Upgrading from CONTROL-M/Agent version 6. The following line is removed from file /etc/services: <service> <portNumber>/<protocol> # CONTROL-M Agent <service>Agent service-name specified during installation.conf file: <service><socketType> tcp nowait root <agentExe> p_ctminetd -e I $CONTROLM/ctm/ <service> Agent service-name specified during installation. Changes to system files You should be aware of that the installation procedure modifies system files as follows: 1. Default: ctmagent <portNumber>Value specified for Server-to-Agent Port Number.0. <protocol>Protocol used for communication between the Server platform and the Agent platform (TCP only) Upgrade with CONTROL-M Option for Oracle Applications installed If CONTROL-M/Agent and CONTROL-M Option for Oracle Applications are installed on the same UNIX computer. Upgrade with CONTROL-M Option for PeopleSoft installed 1 Ensure that all jobs submitted to the CONTROL-M/Agent have ended. the status of running and submitted jobs will become UNKNOWN. 104 CONTROL-M Installation Guide . 2 Create another UNIX user account for the Option. Where to go from here You have now completed the installation of CONTROL-M/Agent. 2 If necessary. 5 Verify that the new Option is working properly. modify its . modify the CLASSPATH environment variable to point to the new location of the CONTROL-M Option for PeopleSoft files.cshrc file by removing all references to the <oldControl-mOption>/EXE directory. Upgrade with CONTROL-M Option for PeopleSoft installed Use the following procedure to enable the installed CONTROL-M Option for PeopleSoft to work with CONTROL-M/Agent after the upgrade: 1 Perform the CONTROL-M/Agent upgrade process as described in the CONTROL-M Installation Guide (this book). 4 Copy all files from the <oldControl-mOption>/DATA directory to the <newControl-mOption>/DATA directory. Otherwise. 6 Before upgrading the Agent. 3 Install the latest version of the Option on the new user account and configure its environment variables. . . . . . For more information. . . . 1. . 105 106 107 108 Testing the new installation You can test your new installation of the CONTROL-M solution by creating and running a simple job. . After ensuring the software is functioning properly you can remove the test job from the database. . . . . . . . . see “Removing the test data” on page 108. . . . . . . . . . . .Chapter 9 9 Running your first job The following topics are discussed in this chapter: Testing the new installation . . . . . . . . . . . . . . . . . . . . . . . . Use the CONTROL-M/EM GUI to check that the job was submitted and that it ran and completed correctly. . . . . . . . . . . . . . see “Monitoring the job” on page 107. . . . . . . . . . see “Creating and running a job” on page 106. . Creating and running a job. . . . . . . . . . . . . . . Removing the test data . . . . . . . . . . . . . . . . . For more information. . . . . . . . . . . . . . . . . . For more information. . . . . . . . . . . . 2. . . . . . . . . . . Chapter 9 Running your first job 105 . . . . . . . . . . . . . use the following procedure: NOTE You must complete the post-installation procedures before running your first job. . . To create and run your first job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring the job . . . . . . Use CONTROL-M/Desktop to create and submit a job. . ■ UNIX_JOB: to run a job on a UNIX/Linux server. 5 In the Apply Template field. NOTE If the server you need is not on the list. choose New => Online Workspace. For more information about creating and submitting a job see the CONTROL-M User Guide. EXAMPLE 106 ■ On Windows you could use the DIR command ■ On UNIX/Linux you could use the ls command CONTROL-M Installation Guide . use the CONTROL-M/Configuration Manager to check the server’s status. select OS from the list. enter the command that you want the job to perform. select Command from the list. 8 In the Job Name field. 4 From the Edit menu. enter a name for the job processing definition. choose New Job to open the job editing form. For more information see the CONTROL-M Administrator Guide. and click Login. To create and run a job 1 Open the CONTROL-M/Desktop by choosing Start->Programs -> CONTROL-M Enterprise Manager <version> -> Default -> CONTROL-M Configuration Manager) 2 Enter your user name and password. select one of the following: ■ WINDOWS_JOB: to run a job on a Windows server. select the server that will control the job. 10 In the Command field. select the CONTROL-M/GUI Server to which you want to connect. In this case. 3 From the File menu.Creating and running a job Creating and running a job This section explains how you can use the CONTROL-M/Desktop to create and manually submit a job. 9 In the Task Type field. the job will perform a directory command. 6 In the CONTROL-M field. 7 In the Job Type field. Inventory. Finance. For more information. 15 Click Order. fill in the fields that are required to set up jobs in CONTROLM: ■ Table: define an arbitrary scheduling table name. Payroll. an accounting application might have sub- categories Budget. For example. 16 In the Job Action Report window click Close. enter the user name of the person creating the job. 12 In the Owner field. The CONTROL-M/Desktop opens the Order/Force Parameters dialog. 13 In the Author field. select the CONTROL-M/GUI Server to which you want to connect. see the CONTROL-M User Guide. 3 From the File menu. For example: Accounting. choose Open Viewpoint to open a Viewpoint. To monitor a job 1 Open CONTROL-M/EM GUI by choosing Start => Programs => CONTROL-M Enterprise Manager 6. ■ Application: define an arbitrary name to describe a category of jobs.Monitoring the job 11 In the Hierarchy area.4. 2 Enter your user name and password. Chapter 9 Running your first job 107 . and click Login. all jobs must run under a scheduling table. 17 In the job editing form click Close. The Author field defaults to the logged on user for CONTROL-M/Desktop. enter the User ID for whom the job is executed or use the default supplied by the application. The CONTROL-M/Desktop opens the Job Action Report window which lists the jobs being ordered and information on the progress. and Receivables. ■ Group: define an arbitrary name that represents a subset of the category in the Application field. Monitoring the job This section describes how to monitor the progress and results of your job using CONTROL-M/EM GUI. A scheduling table groups jobs that are processed together. 14 Click Save & Order.01 => Default => CONTROL-M Enterprise Manager GUI. 108 CONTROL-M Installation Guide . select the CONTROL-M/GUI Server to which you want to connect. 2 Enter your user name and password. Removing the test data After you have verified that CONTROL-M/EM is working correctly. To remove the test data 1 Open CONTROL-M/Desktop by choosing Start => Programs => CONTROL-M Enterprise Manager 6. you have completed running your first job successfully. From the Analysis menu. 5 Double-click the server that is running the job. 6 Double-click the application you entered on the job definition window.4. Table 17 lists the possible colors and their related status. and click Login. The job hierarchy is displayed on the left side of the title bar. The color in the title bar of the entity indicates the status of the job. The application expands the group entity and shows the job you created.01 => Default => CONTROL-M Desktop. Table 17 Job status colors indicated by the color of a node’s title bar Color Status Gray Wait Condition Green Ended OK Yellow Executing Blue Wait Resource Pink Wait User Red Ended Not OK White Unknown If you have a green status. 7 Double-click the group you entered on the job definition window. you can remove the test data. TIP Use the Sysout menu option to view the output of the job.Removing the test data 4 In the CONTROL-M/Enterprise Manager ViewPoints window. choose Sysout. select All Jobs from the list and click OK. Removing the test data 3 From the Tools menu. CONTROL-M/Desktop displays a message asking for verification of the deletion. Chapter 9 Running your first job 109 . click Close. click Close. 4 In the Scheduling Table Manager window. CONTROL-M/Desktop opens the Table Action Report window which lists the status of the deletion. 8 In the Scheduling Table Manager window. 5 Click Delete. 7 In the Table Action Report window. 6 Click Yes to verify the deletion. CONTROL-M/Desktop opens the Scheduling Table Manager window. choose Scheduling Table Manager. TIP Double-click the table name to view the jobs in the selected table. select the table name you entered in your job definition. Removing the test data 110 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Cleaning up a failed Oracle installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 18 describes the ways that CONTROL-M can be installed with an Oracle database server. . . . . . 119 Installing an Oracle client using an on-site Oracle client (for CONTROL-M/EM only) 119 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Setting Oracle installation parameters . . . . . . . . . . . . . . . . . . . . . . . . 120 Performing a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation can be performed using interactive mode or silent mode. . . . . . . . .Appendix A Installing an Oracle database on UNIX A This appendix describes how to install an Oracle database server on UNIX for use with CONTROL-M. . . . . . . . . . . . 126 Cleaning up after a dedicated installation . . . . . . . . . . . . . . 117 Where to go from here . . . . . . . . . . . . . . . . . . 114 Installing on an existing database server . . . . 126 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . 119 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Performing post-installation cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Running the Oracle pre-installation script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Checking the installation log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Cleaning up after an existing installation . . . . . . . . The following topics are discussed in this appendix: Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Appendix A Installing an Oracle database on UNIX 111 . . . . . 114 Installing a dedicated database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Installing a tablespace using an on-site Oracle client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Installing a database server . . . . . . . . . . . 118 Installing an Oracle client (for CONTROL-M/EM only) . . . . . . . . . . . . . Oracle Client Installs only the Oracle client software. The existing database server must be Oracle Full Enterprise Edition. and inserts a CONTROL-M database schema.WARNING Oracle must be installed silently if you want to install CONTROL-M/EM or CONTROLM/Server silently. With customization – Allows modification of installation parameters. ensure that SELINUX=disabled in the /etc/sysconfig/selinux file. initiates an instance. ensure you have prepared everything necessary for the installation as described in Chapter 2. Before beginning. see the CONTROL-M /Enterprise Manager Migration Guide. Existing Installs an Oracle client only and inserts a CONTROL-M database schema on an existing database server. 112 CONTROL-M Installation Guide . If you are migrating from an earlier version of CONTROL-M/Server. WARNING Before installing Oracle on Red Hat Enterprise Linux AS/ES version 5. Supported Oracle database server and database client versions are listed in Table 2 on page 33. see the CONTROL-M/Server Migration Guide. If you are migrating from an earlier version of CONTROL-M/EM. This installation type can be performed only after the database schema for CONTROL-M exists on the Oracle database server. “Planning the CONTROL-M solution”. The following types of dedicated installation are available: ■ ■ Without customization – Uses default values for all Oracle Database parameters. . Table 18 Oracle installation types Installation Type Explanation Dedicated Installs full Oracle server and client software.0. Running the Oracle pre-installation script This script determines the database software (server or client) to be installed and sets the required defaults. Appendix A Installing an Oracle database on UNIX 113 . 2 Mount the CONTROL-M/EM or CONTROL-M/Server installation DVD as required. see Appendix I. 4 Prepare the parameter information you need before beginning the installation. 1 Log in to the root user and navigate to the CONTROL-M/EM or CONTROLM/Server user home directory. ensure that no processes are running in the background on the CONTROL-M/EM or CONTROL-M/Server account. 3 Run checkreq to verify that the UNIX server is properly configured. See explained in “Table 20.sh The <dvdPath> variable is the directory on which you mounted the CONTROL-M installation DVD.Preparing for installation Preparing for installation Table 19 Installation steps Step Instruction 1 Create the UNIX account. 5 Perform “Running the Oracle pre-installation script” on page 113. 7 Perform the “Performing post-installation cleanup” on page 127. Perform the “Installing on an existing database server” on page 115 to install a CONTROL-M Oracle database client on the local computer and a CONTROL-M tablespace on the Oracle database server. the account group should be dba. 2 Before starting the installation process. Ensure that no processes are running in the background on the account. 6 Oracle Server Oracle Client + tablespace Perform the “Installing a database server” on page 114 to install the full Oracle server and client software. For details of mount procedures for your UNIX platform. It must be run before performing any of the Oracle installations in this appendix. “Mounting DVDs and CDs on UNIX computers”. If you are installing a dedicated database server. 3 Enter the following command: <dvdPath>/Oracle/orapreinst. Oracle Database – UNIX installation parameters” on page 123. The size of each raw partition must be equal to the size of the tablespace plus 4 MB. Installing a dedicated database server enables you to install the full Oracle server and client software. Use the following procedure to perform the installation: 1 Prepare the parameter information you need before beginning the installation. prepare them before installation of the Oracle database server. Installing a database server You can either install a dedicated database server or an existing database server. For details of mount procedures for your UNIX platform. Installing an existing database server enables you to install a CONTROL-M Oracle database client on the local computer and a CONTROL-M/EM or CONTROLM/Server tablespace on the Oracle database server. Consult your system administrator for more information about raw partitions. The CONTROL-M Oracle database server can be installed on a raw partition or on a regular file system. see “Installing on an existing database server” on page 115. “Mounting DVDs and CDs on UNIX computers”. Parameters are explained in “Table 20. see Appendix I. Installing a dedicated database server This process installs a CONTROL-M Oracle database server on the local computer. 5 Log off the root account. Oracle Database log files must not be placed on a raw partition. 3 Mount the installation DVD. see “Installing a dedicated database server” on page 114. 2 Log in to the CONTROL-M/EM or CONTROL-M/Server account as necessary. For more information. 4 Use the following command to run the installation script from the installation directory: 114 CONTROL-M Installation Guide . If you want to use raw partitions for the CONTROL-M database devices. For more information. Oracle Database – UNIX installation parameters” on page 123.Installing a database server 4 Follow the directions on the screen. 7 After the Installation completed successfully message is displayed. Installing on an existing database server This process installs a CONTROL-M Oracle database client on the local computer and creates a CONTROL-M/EM (or CONTROL-M/Server) tablespace on an existing Oracle database server. as well as the name and password of the system administrator. and name of the existing Oracle database server. The location. A CONTROL-M/EM (or CONTROL-M/Server) tablespace and user are also installed.Installing on an existing database server <dvdPath>/Oracle/inst_oracle 5 Select one of the following installation choices. If you are using raw partitions or working with a UTF8 character set. Verification of existing Oracle components 1 Obtain the following for the new CONTROL-M/EM (or CONTROL-M/Server) database from your database administrator: ■ instance name ■ port number ■ system administrator login name ■ system administrator password Appendix A Installing an Oracle database on UNIX 115 . Where to go from here Continue with Chapter 3. 6 Follow the instructions on the screen. must be specified in the installation parameters. port number. you must choose Custom: ■ Default — Installs a CONTROL-M Oracle database server with default database parameters on the local computer. filling in parameter values as necessary. “Installing CONTROL-M/Server” as necessary. ■ Custom — Installs a CONTROL-M Oracle database server on the local computer and prompts you to specify your own database parameters. A CONTROL-M/EM (or CONTROLM/Server) tablespace and user are also installed. “Installing CONTROL-M/EM on UNIX” or Chapter 5. continue with “Performing post-installation cleanup” on page 127. NOTE The existing Oracle database instance must be running during installation and whenever CONTROL-M/EM or CONTROL-M/Server is operating. To display a list of existing tablespace names: A Log in as the database administrator. 4 Verify that this database is served by an Oracle Listener port running on the same computer on which the database is installed. 3 Obtain the correct dbaUser and dbaPassword from your database administrator and use the following command to verify that Oracle is running: sqlplus <dbaUser>/<dbaPassword> <dbaUser> is the name of the DBA account (Oracle default: system). B Type the following SQL instruction: SQL> select tablespace_name from dba_tablespaces. 116 CONTROL-M Installation Guide . <dbaPassword> is the DBA account password (Oracle default: manager). NOTE When creating more than one CONTROL-M installation using the same Oracle database server. B Type the following SQL instruction: SQL> select username from dba_users. 5 A unique tablespace name and a tablespace owner name (DBO) must be specified for each CONTROL-M database. you must specify a unique tablespace name and tablespace owner name for each installation. To display a list of existing usernames: A Log in as the database administrator. log in to the computer where the Oracle database server is installed.Installing on an existing database server ■ server name 2 Using the operating system account that installed the Oracle server. 0. see Appendix I. continue with “Performing post-installation cleanup” on page 127. The location and name of the existing Oracle installation. 5 Follow the instructions on the screen. “Installing CONTROL-M/EM on UNIX” or Chapter 5.2.Installing a tablespace using an on-site Oracle client Performing the existing database installation 1 Log in to the CONTROL-M/EM or CONTROL-M/Server account.3 database client should be used for this operation. Installing a tablespace using an on-site Oracle client At installations where business policy allows only Oracle supplied software to be used. Where to go from here Continue with Chapter 3. For details of mount procedures for your UNIX platform. and the system administrator password must be specified in the installation parameters. “Installing CONTROL-M/Server” as necessary. <dvdPath>/Oracle/inst_oracle 4 Select existing installation. 2 Mount the installation DVD. filling in parameter values as necessary. this process allows an on-site Oracle client to be used to facilitate CONTROLM/EM or CONTROL-M/Server installations on an Oracle database server. 6 After the Installation completed successfully message is displayed. 3 Use the following command to run the installation script. Appendix A Installing an Oracle database on UNIX 117 . WARNING ■ This is an advanced level option that should be used with care and only by qualified DBA personnel. The use of higher versions of Oracle is not recommended as they have not been tested by BMC Software. “Mounting DVDs and CDs on UNIX computers”. the system administrator name. ■ Oracle version 10. Where to go from here 1 Log in to the CONTROL-M/EM or CONTROL-M/Server account. “Installing CONTROL-M/EM on UNIX” or Chapter 5. “Installing CONTROL-M/Server” as necessary. WARNING When using USE_EXISTING_ORACLE. 6 Select an existing Oracle installation (you must use a supported Oracle version listed in Table 2 on page 33). 2 Mount the installation DVD. lib directories. see your database administrator. 3 Set the environment variable USE_EXISTING_ORACLE to value Y. ensure that all Oracle client binaries. “Mounting DVDs and CDs on UNIX computers”. filling in parameter values as necessary. 118 CONTROL-M Installation Guide . <dvdPath>/Oracle/inst_oracle 5 Select existing installation. and files have 640 protection. or if a list is available and you select the “Enter another value” option. See “Setting environment variables in UNIX” on page 37 for your UNIX environment. 4 Use the following command to run the installation script. or if a list is available and you select the “Enter another value” option. For more information. you are prompted to type a connection alias. see Appendix I. 9 After the Installation completed successfully message is displayed. If a list of connection aliases is not available. For details of mount procedures for your UNIX platform. 8 Follow the instructions on the screen. 7 Select a network connection alias. If a list of existing Oracle installation locations is not available. Where to go from here Continue with Chapter 3. continue with “Performing post-installation cleanup” on page 127. you are prompted to type a path to an Oracle installation. 03 client (only) to communicate with a CONTROL-M database. 1 Prepare the parameter information you need before beginning the installation. Installing an Oracle client using an on-site Oracle client (for CONTROL-M/EM only) This process enables the current account to use an existing Oracle version 10. 3 Use the following command to run the installation script. 6 After the Installation completed successfully message is displayed. 2 Log on to the CONTROL-M account. “Installing CONTROL-M/Server” as necessary. filling in parameter values as necessary. It should be used with care and in consultation with BMC Software qualified DBA personnel.Installing an Oracle client (for CONTROL-M/EM only) Installing an Oracle client (for CONTROL-M/EM only) This process installs a CONTROL-M Oracle database client to enable communication with an existing installation of CONTROL-M.2. Parameters are explained in “Table 20. Where to go from here Continue with Chapter 3. Oracle Database – UNIX installation parameters” on page 123. NOTE This is an advanced level option. 5 Follow the instructions on the screen. Appendix A Installing an Oracle database on UNIX 119 . <cdPath>/Oracle/inst_oracle 4 Select Client only installation. “Installing CONTROL-M/EM on UNIX” or Chapter 5. continue with “Performing post-installation cleanup” on page 127. Where to go from here The location and name of the existing Oracle installation, the database owner name, and the database owner password must be specified in the installation parameters. No database or CONTROL-M components are installed. The process checks the validity of the current definitions and defines the required environment variables necessary to establish communication with the CONTROL-M database. 1 Prepare the parameter information you need before beginning the installation. Parameters are explained in “Table 20, Oracle Database – UNIX installation parameters” on page 123. 2 Log on to the CONTROL-M account. 3 Set the environment variable USE_EXISTING_ORACLE to value Y. See “Setting environment variables in UNIX” on page 37 for your UNIX environment. 4 Use the following command to run the installation script. <cdPath>/inst_oracle 5 Select Client only installation. (“Using your existing Oracle software to communicate with an existing EM database.”) 6 Select an existing Oracle installation (you must use a supported Oracle version listed in Table 2 on page 33). If a list of existing Oracle installation locations is not available, or if a list is available and you select the “Enter another value” option, you are prompted to type a path to an Oracle installation. 7 Select a network connection alias. If a list of connection aliases is not available, or if a list is available and you select the “Enter another value” option, you are prompted to type in a connection alias. 8 Follow the instructions on the screen, filling in parameter values as necessary. 9 After the Installation completed successfully message is displayed, continue with “Performing post-installation cleanup” on page 127. Where to go from here Continue with Chapter 3, “Installing CONTROL-M/EM on UNIX” or Chapter 5, “Installing CONTROL-M/Server” as necessary. 120 CONTROL-M Installation Guide Performing a silent installation Performing a silent installation Silent installation is used to install Oracle from a batch file. The following stages are involved: ■ Preparing the parameters file This is accomplished by running a silent installation preparatory procedure from the installation DVD. The preparatory procedure behaves like the interactive installation procedure and prompts you to enter the same information. However, no installation is performed. Instead, the information you enter is stored in a file. ■ Using the prepared parameters file When the prepared parameters file is used with the silent installation program, Oracle is installed using the parameters you specified in the previous step. To prepare the silent installation batch file 1 Perform Oracle pre-installation as described in “Running the Oracle preinstallation script” on page 113. 2 Select one of the installation types described in this chapter and perform the steps required until reaching the inst_oracle command. Now run this command with the u flag. For example: <dvdPath>/Oracle/inst_oracle u The u flag prevents installation from being executed, and causes a parameter file to be generated instead. The following parameter file is generated in the $HOME/tmp directory: ■ 10201_Install_def.PARAMS 3 Continue to the end of the installation screens. 4 Using any text editor, open the parameters file and add the following two lines: ■ APP_PASS=<temporaryPassword> ■ SYSTEM_PASSWD=<databaseAdministratorPassword> <temporaryPassword> is the temporary password given to the dbo during the database installation. <databaseAdministratorPassword> is the dba password that will be set. Appendix A Installing an Oracle database on UNIX 121 Performing a silent installation For an existing installation, consult your database administrator. 5 Copy the parameter file to the computers on which you want to preform the silent installation. To install silently The silent installation script performs all necessary pre-installation and postinstallation activities as well as the installation itself. A system requirement check should be run before beginning the installation. NOTE If the paths to $HOME in the parameter file are different from the paths on the computer on which you prepared the silent installation, you may need to edit these parameters in the parameter file. 1 Confirm you have the necessary system requirements and run the check_req.sh script as specified in “Verifying operating system levels and patches” on page 38. 2 Mount the installation DVD. For details of mount procedures for your UNIX platform, see Appendix I, “Mounting DVDs and CDs on UNIX computers”. 3 Log in as root to the installation directory and run the following script (the script should be entered on a single command line): <dvdPath>/Oracle/silent_install_10.sh ora_home_dir=<oracleHome> paramfile=<parametersFileLocation> display=N <oracleHome> is the path to the UNIX account where Oracle will be installed. <parametersFileLocation> is the path and name of the parameters file. Installation progress is displayed on the monitor. WARNING ■ No checks are performed on the contents of the parameter files. If any parameter is incorrect, the installation will fail. The results of the pre-installation, installation, and post-installation procedures are recorded in the following logs: 122 ■ $HOME/silent_dir/orapreinst*.log ■ $HOME/silent_dir/orapostinst*.log CONTROL-M Installation Guide Where to go from here Where to go from here ■ If you are installing CONTROL-M/EM on Unix, continue with “Silent installation” on page 51 ■ If you are installing CONTROL-M/Server on Unix, continue with “Silent installation” on page 74 Setting Oracle installation parameters Table 20 Oracle Database – UNIX installation parameters (Part 1 of 4) Parameter or Prompt Description Data tablespace size for Size for the data files component: small (250 MB), medium (800 MB), or large both CONTROL-M/EM 2500 MB). and CONTROL-M/Server) Default: depends on the size (small, medium, or large) chosen for the database. Database log01 file name (full path) The default path to the first database log file is based on the Oracle database instance name. For example: When the instance name is Mxxx, the default path is: $HOME/oracle/oradata/Mxxx/<emuserlog01.dbf or ctmuserlog01.dbf >. Database log02 file name (full path) The default path to the second database log file is based on the Oracle database instance name. For example: When the instance name is Mxxx, the default path is: $HOME/oracle/oradata/Mxxx/<emuserlog02.dbf or ctmuserlog02.dbf >. Database redo log file size (2 files) for both CONTROL-M/EM and CONTROL-M/Server) Each Oracle database has two redo log files. These files are used to record all committed changes that are applied to the database, so that this information is available in case of a media failure. Size for each redo log file: small (150 MB), medium (250 MB), or large (400 MB). Default: depends on the size (small, medium, or large) chosen for the database. Database rollback segments tablespace file name (full path) The default path to the rollback segments tablespace file is based on the Oracle database instance name. For example: When the instance name is Mxxx, the default path is: $HOME/oracle/oradata/Mxxx/<emuserrbs.dbf or ctmuserrbs.dbf >. Database rollback segments tablespace size Default: 550 MB. Appendix A Installing an Oracle database on UNIX 123 EM Data tablespace name Name of the data tablespace that will be created on the existing Oracle database or instance.dbf > Database system tablespace size (for both CONTROL-M/EM and CONTROL-M/Server) Database temporary tablespace file name (full path) small (500 MB). 124 CONTROL-M Installation Guide . the default path is: $HOME/oracle/oradata/Mxxx/<emusersystem01. or large) chosen for the database. a-z) followed by up to 7 alphanumeric characters (includes underscores). medium (550 MB). Default: emuser or ctmuser. medium. For CONTROL-M/EM. both CONTROL-M/EM and CONTROL-M/Server) EM data file name or Ctm data file name The default path to the data tablespace file is based on the Oracle database instance name. or large) chosen for the database. medium.dbf or ctmusertemp01. Default: emuser or ctmuser. the name must begin with a letter (A-Z. This is the user used to log in to CONTROL-M/EM or CONTROL-M/Server. Default: $HOME/oracle/oradata/<EM640 or ctrlm>/emuserdata01. The default path to the temporary tablespace file is based on the Oracle database instance name. a-z) followed by up to 17 alphanumeric characters (includes underscores). medium (250 MB). the name must begin with a letter (A-Z. this parameter indicates the full path and file name for the Data file of the database. This file will be created during installation of the database. EM Database user or Ctm Database user Name of the CONTROL-M/EM database user (owner) to be created. the default path is: $HOME/oracle/oradata/Mxxx/<emusertemp01. The specified path must be an existing path for which the administrator of the existing Oracle instance has READ and WRITE permission. or large (600 MB). For example: When the instance name is Mxxx. Database temporary tablespace file size (for Default: depends on the size (small. Default: depends on the size (small. For installation using an existing Oracle Database server. or large (500 MB).Setting Oracle installation parameters Table 20 Oracle Database – UNIX installation parameters (Part 2 of 4) Parameter or Prompt Description Database system tablespace file name The default path to the system tablespace file is based on the Oracle database instance name. The file name must not be the name of an existing file. For example: When the instance name is Mxxx.dbf.dbf > small (100 MB).dbf or ctmusersystem01. This tablespace will contain the database data (name should start with Ctm Data tablespace name a letter followed by 1-24 alphanumeric characters). For CONTROL-M/Server. Setting Oracle installation parameters Table 20 Oracle Database – UNIX installation parameters (Part 3 of 4) Parameter or Prompt Description Oracle Database Instance Name Instance name of the CONTROL-M/EM database. Default: EM640. Instance name of the CONTROL-M/Server database. Default: ctrlm How do I find this value on an existing Oracle server? ■ Search for the listener.ora file in a location similar to the following: <oracleHome>/oracle/product/10.2.0.1/network/admin/ <oracleHome> is the folder in which the Oracle server is installed. ■ In this file, the value of the SID_NAME parameter is the instance name. If the SID_NAME parameter appears more than once in the listener.ora file, consult your Oracle database administrator to determine which name you should use. Notes: ■ The Oracle database instance name should not exceed 8 characters. ■ The Oracle database instance name cannot begin with a numeral. ■ The value "_" is not allowed for the SID_NAME ■ For installation using an existing Oracle database server, this parameter indicates the instance name of the existing database. Get this value from the DBA. Oracle LISTENER port number Communications port used by the Oracle database server to communicate with Oracle database. Default: 1521. How do I find an available port? If TCP/IP protocol is installed, the following command checks if a specific port is available: netstat -na | grep <portNumber>. The <portNumber> variable is the number of the required port. If this command returns no result, the port is available. Note: If your installation is using an existing Oracle database, get the appropriate port number from your database administrator (DBA). Oracle Server host name For installations that use an existing Oracle database server, Name or IP address of the computer on which the existing Oracle instance is located. Oracle SYSTEM password Password for the Oracle SYSTEM account. Usage: should start with a letter followed by 3-29 alphanumeric characters. Default: manager. Oracle SYSTEM User User name for the Oracle SYSTEM account. Default: SYSTEM. Note: This parameter is displayed only for an “existing Installation”. Appendix A Installing an Oracle database on UNIX 125 Checking the installation log Table 20 Oracle Database – UNIX installation parameters (Part 4 of 4) Parameter or Prompt Description CJK installation for CONTROL-M/Enterprise Manager (Y/N) Support for East Asian languages (Simplified Chinese, Traditional Chinese, Japanese, and Korean) Default: N - Latin1 (WE8ISO8859P1), Y - UTF8. Password for the CONTROL-M/EM database user (4 to 30 characters, alphanumeric). The characters are not displayed for security reasons. User password Note: This password can be changed at a later time. For more information, see, “Maintaining CONTROL-M/EM“, in the CONTROL-M Administrator Guide. NOTE Even if you do not modify any other parameters, you must modify the parameters relating to the existing database that do not have default values. Checking the installation log After installing Oracle database components, the following installation log directory is created in the home directory of the CONTROL-M/EM account: <ctmHomeDirectory>/log <ctmHomeDirectory> is the path of the CONTROL-M/EM user. The main installation log file is: trace.log Where to go from here Continue with Chapter 3, “Installing CONTROL-M/EM on UNIX” or Chapter 5, “Installing CONTROL-M/Server” as necessary. Cleaning up a failed Oracle installation Uninstalling and cleanup is necessary before re-running the existing Oracle installation. You must first remove the database components that were created by the failed installation. 126 CONTROL-M Installation Guide Cleaning up after a dedicated installation Cleaning up after a dedicated installation To clean up a dedicated installation, use the uninstall script provided on the installation DVD. Cleaning up after an existing installation To uninstall and clean up an existing installation 1 Run the uninstall program (see “Uninstalling a CONTROL-M Oracle database server from UNIX” on page 206). 2 Log in to the Oracle database server account as the database administrator. 3 If a username was already created, use the drop user <userName> cascade; command to delete it. 4 Depending on where and how the installation failed, a tablespace and a data file may have been created. Use the following commands to check if a <tablespaceName> (tablespace name) and <datafileName> (data file name) were created for the failed installation. col name for a50 select t.name,d.name from v$tablespace t,v$datafile d where d.ts# =t.ts# ; 5 If a tablespace was created: A Use the drop tablespace <tablespaceName> command to delete the tablespace. B Delete that data file associated with the dropped tablespace. WARNING Do not delete raw partitions. Performing post-installation cleanup The following procedure removes the temporary directories and files created by an Oracle database server setup. Appendix A Installing an Oracle database on UNIX 127 Performing post-installation cleanup 1 Log in as the root user. 2 Mount the CONTROL-M/EM installation DVD. For details of mount procedures for your UNIX platform, see Appendix I, “Mounting DVDs and CDs on UNIX computers”. 3 Enter the following command: <dvdPath>/Oracle/orapostinst.sh The <dvdPath> variable is the directory on which you mounted the CONTROLM/EM installation DVD. 4 If necessary, confirm the removal of files by entering y and pressing <enter>. 5 Log off the root user. 128 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . 130 131 131 131 133 134 135 136 139 WARNING Oracle must be installed silently if you want to install CONTROL-M/EM silently. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation can be performed using interactive mode or silent mode. . . . . . . . . . . . . . . . . . . . . . . . Setting Oracle installation parameters . . . . . . . . . . . . . Appendix B Installing an Oracle database on Windows 129 . . Running the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . .Appendix B Installing an Oracle database on Windows B This appendix describes how to install an Oracle database server on Windows for use with CONTROL-M/EM. . . . . . . Table 21 describes the different ways that CONTROL-M/EM can be installed with an Oracle database server. . . . . . . . . . . . . . . Installing a CONTROL-M/EM tablespace using an on-site Oracle client . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . Cleaning up a failed existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The following topics are discussed in this appendix: Preparing for installation . . . . . . . . . . . . . . . . Performing a silent installation . . . . . . . . . . . . . . . . . . . . . . . Oracle Database – Windows installation parameters” on page 136.com/support_home) solution SLN000015053002. The existing database server must be Oracle Full Enterprise Edition. “Planning the CONTROL-M solution”. With customization – Allows modification of installation parameters. download the Migration Toolkit and the CONTROL-M /Enterprise Manager Migration Guide from BMC Software Customer Support Web site (http://www. Supported Oracle database server and database client versions are listed in Table 2 on page 33. and inserts a CONTROL-M/EM database schema. See explained in “Table 23.bmc. 130 CONTROL-M Installation Guide . If you are migrating from an earlier version of CONTROL-M/EM. Before beginning. Existing Installs an Oracle client only and inserts a CONTROL-M/EM database schema on an existing database server. initiates an instance. Preparing for installation Table 22 Installation steps Step Instruction Prepare the parameter information you need before beginning the 1 installation. Two types of dedicated installation are available: ■ ■ Without customization – Uses default values for all Oracle Database parameters. This installation type can be performed only after the database schema for CONTROL-M/EM exists on the Oracle database server. NOTE All installation procedures must be performed directly on the local computer.Preparing for installation Table 21 Oracle installation options Installation type Explanation Dedicated Installs full Oracle server and client software. You must not use remote management software to perform any part of the Oracle installation. Oracle Client Installs only the Oracle client software. make sure you have prepared everything necessary for the installation as described in Chapter 2. 4 Follow the prompts to complete the installation. The parameters and values for this installation are described in Table 23 on page 136. this process allows an on-site Oracle client to be used to facilitate CONTROL-M/EM installations on an Oracle database server. the drive must be mapped using UNC mapping. “Installing CONTROL-M/EM on Windows”. If you are running the installation from a network drive. NOTE An Oracle installation menu is added to the Start => Programs menu. 2 Insert the CONTROL-M/EM installation DVD. Running the installation 1 Stop all applications on the computer on which the installation will run. 3 Navigate to the Oracle folder and run Setup.bat. Installing a CONTROL-M/EM tablespace using an on-site Oracle client At installations where business policy allows only Oracle supplied software to be used.Running the installation Table 22 Installation steps Step Instruction 2 Oracle Server Oracle Client + tablespace Perform the “Running the Perform the “Running the installation” on installation” on page 131 to install the page 131 to install a CONTROL-M Oracle full Oracle server and client software. Where to go from here Continue with Chapter 3. Appendix B Installing an Oracle database on Windows 131 . database client on the local computer and a CONTROL-M tablespace on the Oracle database server. 6 Navigate to the Oracle folder and run Setup. select HKEY_LOCAL_MACHINE=>SOFTWARE=>ORACLE. ■ Oracle version 10. WARNING Follow the instructions carefully.3 database client should be used for this operation. CONTROL-M/EM supports the Oracle database server and database client versions listed in Table 2 on page 33.0. select Run.2. 4 Right-click the right-hand pane of the Registry Editor window. 2 On the Oracle client computer. If you are running the installation from a network drive. The installation procedure detects the registry changes. Making incorrect changes can damage your system. The installation procedure prompts you for the name and password of the database administrator (DBA) of the existing database instance in which the new schema will be built.Installing a CONTROL-M/EM tablespace using an on-site Oracle client WARNING ■ This is an advanced level option that should be used with care and only by qualified DBA personnel. Type regedit and click OK to run the Registry Editor. the process checks the validity of the current definitions and defines the required environment variables necessary to establish communication with the CONTROL-M/EM database. 1 Review the following installation criteria before you begin the installation procedure: ■ ■ ■ The Oracle client software must already be installed and configured to connect the local user to the target database instance.bat. 5 Insert the CONTROL-M/EM installation DVD. Replace the default text with the string USE_EXISTING_ORACLE. The use of higher versions of Oracle is not recommended as they have not been tested by BMC Software. 3 In the Registry Editor window’s tree (left pane). the drive must be mapped using UNC mapping. that instance must run Oracle software releases certified by BMC Software for use with CONTROL-M/EM. from the Start menu. and choose New = > String Value. In addition to installing CONTROL-M/EM components. 132 CONTROL-M Installation Guide . When you install a CONTROL-M/EM database on an existing Oracle instance. However. CONTROL-M/EM database operation requires sqlplus. Appendix B Installing an Oracle database on Windows 133 . ■ Specify the size for the data files component Defaults: 250. Only Oracle Homes that are installed with sqlplus are displayed. B Select the connection string to use when establishing a connection to the Oracle Home. “Installing CONTROL-M/EM on Windows”. D Enter the username and password of the Oracle administrator. The new database owner name must not be the same one used for the Oracle database server. C Enter a name and a password for the new CONTROL-M/EM database (schema) owner. E Select the desired tablespace size. Where to go from here Continue with Chapter 3. ■ Specify Data Files Component Tablespace Name Default: <instanceName>_EM_USERS. your database administrator may have modified them. 8 Follow the instructions on the screen until The procedure is complete window is displayed. The specified path must exist on the database server host computer. To use an existing connection string that is not on the list. NOTE The tablespace name and location must be unique for the current database installation. choose Other and enter a connection string. and 2500 MB depending on data tablespace size. During the installation.Where to go from here 7 Select Installation on Existing server in the Oracle Installation Type window. you will be prompted to: A Select from the list of existing Oracle Homes. 800. ■ Specify the path for the data files component For example: D:\Oracle\oradata\<instanceName>\data01.dbf. These values are usually SYSTEM and MANAGER respectively. 2 Run inst_oracle. OracleInstallationParms_<timeStamp>.Performing a silent installation Performing a silent installation Silent installation is used to install Oracle from a batch file. To install silently NOTE Depending on differences between the current computer and computer on which you prepared the silent installation. you may have to edit some parameters (for example.txt is generated in the following folder: <drive>:\Program Files\BMC Software\Oracle\BMC_Products\ 3 Copy the parameter file to the computer(s) on which you want to preform the silent installation.txt from the computer on which it was prepared to the <drive>:\ Program Files\BMC Software\Oracle\BMC_Products folder on the local computer. 2. host name. To prepare the silent installation batch file 1 Navigate to <dvdPath>:\Oracle\OracleInstallationFiles\executables. the DBO name and password. You can reuse this batch file to silently install Oracle on other computers. Preparing the batch file This is accomplished by running a silent installation preparatory procedure from the installation DVD. Two stages are involved: 1. 2 Copy the silent installation parameter file. Running the prepared batch file When the prepared batch file runs.bat. etc. However no installation is performed.). OracleInstallationParms_<timeStamp>. Oracle is installed using the parameters you specified in the previous step. the information you enter is stored in a batch file. 134 CONTROL-M Installation Guide . The preparatory procedure behaves like the interactive installation procedure and prompts you to enter the same information. The parameter file. 1 Log on to the computer on which you want to perform the silent installation. Instead. The results of the installation is recorded in the following log: <oracleHome>:\Program Files\BMC Software\ Oracle\BMC_Logs\Oracle_<timeStamp>. you will need to create it. a message is displayed. Appendix B Installing an Oracle database on Windows 135 . Where to go from here Continue with CONTROL-M/EM Windows “Silent installation” on page 56.log WARNING No checks are performed on the contents of the parameter files. 4 Run the following file from the DVD drive: Oracle\OracleInstallationFiles\executables\OracleInstallation\ OracleInstallation. If any parameter is incorrect. the installation will fail. Upon completion. 3 Insert the CONTROL-M/EM installation DVD.Where to go from here If this folder does not exist.exe Installation progress is displayed on the monitor. The administrator is the default user when logging on to CONTROL-M/EM GUI for the first time. and the path must exist on the computer where the database server is installed. the database owner name specified in this window must not be the same as any existing user name for the Oracle database server. Default: MANAGER. Database Server 136 Password The password is required only for a Client installation. Normally. Note: For installation using an existing Oracle database server.Setting Oracle installation parameters Setting Oracle installation parameters Table 23 Oracle Database – Windows installation parameters (Part 1 of 4) Parameter Description Data File Component Name Data files component tablespace Name. or large (2500 MB). Database Owner Username Name of the CONTROL-M/EM database owner (user). Username Default: SYSTEM. The name must begin with a letter (A-Z. Location Path for the data files component. Default: emuser Note: When installing a new tablespace using an existing Oracle database server. the tablespace name must be unique for the current database installation. Password for the CONTROL-M/EM database owner. Note: For installation using an existing Oracle database server. Password Password of the Oracle Server Administrator. Enter the name of the database user that was defined when the CONTROL-M/EM Oracle tablespace was created. this is also the name of the CONTROL-M/EM administrator. Default: <instanceName>_EM_USERS. the tablespace location must be unique for the current database installation. . Default: <drive>:\Oracle\oradata\<instanceName>\data01.dbf. medium (800 MB). CONTROL-M Installation Guide Enter the password of the CONTROL-M/EM database owner that was defined when the CONTROL-M/EM Oracle tablespace was created. Default: depends on the size (small. Size Size for the data files component: small (250 MB). This value cannot be modified for installation of a dedicated database server. or large) chosen for the database. medium. a-z) followed by up to 7 alpha-numeric characters (includes underscores). Note: The value for this parameter is in the HOST parameter in the listener. Default: <osInstallDrive>:\Oracle The folder name must not include blanks. This installation type can be performed only after the tablespace for CONTROL-M/EM has been defined on the Oracle database server. Existing server Installs a tablespace for CONTROL-M/EM on an existing Oracle database server. not a number.2. consult your Oracle database administrator to determine the value you should use. How do I find this value on an existing Oracle server? 1. Default: EM640. consult your Oracle database administrator to determine which name you should use. Search for the listener. Instance Name Name of the database instance for the CONTROL-M/EM Database. This parameter is required only when installing a new database using an already installed (existing) Oracle database server. or if a parameter occurs more than once in the file.ora file. Oracle installation Dedicated server Type (without customization) Uses default values for all Oracle database parameters. Oracle client Installs a CONTROL-M Oracle client component only.ora file. If the SID_NAME parameter appears more than once in the listener. In this file. the value of the SID_NAME parameter is the instance name.ora file. Appendix B Installing an Oracle database on Windows 137 .Setting Oracle installation parameters Table 23 Oracle Database – Windows installation parameters (Part 2 of 4) Parameter Description Database Server Host Name Host name of the computer on which the Oracle database server is installed. There is no default. For more information about how to locate the listener. ■ The first character must be a letter. Maximum length: 8 characters.1/network/admin/samples (on UNIX) <oracleHome> is the folder in which the Oracle server is installed. Notes: ■ Use not more than 8 alphanumeric characters.ora file in a location similar to the following: <oracleHome>\Oracle\Ora1020\network\ADMIN\ (on Windows) <oracleHome>/Oracle/product/10. 2. see the Instance Name parameter in this table. Dedicated server (with customization) Allows you to modify Oracle database parameters. Destination Installation folder for the Oracle components.ora file on the server computer. If you cannot find the listener. dbf. Default: <OracleHome>:\Oracle\oradata\<instanceName>\system. Choose small.ora file.ora file on the server computer.dbf. Contact your System Administrator to verify the correct value. or large (200 MB). consult your Oracle database administrator to determine the value you should use. Size Size for each redo log file. Location System (Component) tablespace location. see the Instance Name parameter (above). Default: 330 MB for all data tablespace sizes. medium.dbf. medium. Default: depends on the size (small. Default: <OracleHome>:\Oracle\oradata\<instanceName>\redo01. or large) chosen for the database. medium (100 MB). medium (300 MB). If you cannot find the listener. Default: <OracleHome>:\Oracle\oradata\<instanceName>\redo02. or large.dbf. Choose small (50 MB). Tablespace Size The size specification for the CONTROL-M/EM database. or large) chosen for the database.Setting Oracle installation parameters Table 23 Oracle Database – Windows installation parameters (Part 3 of 4) Parameter Description Oracle Server TCP/IP Port Number Port number Default: 1521. Default: <OracleHome>:\Oracle\oradata\<instanceName>\rbs01. Rollback Component System Component Location Path for the rollback tablespace.ora file. Size Size for the rollback tablespace. Size System (Component) tablespace size: small (250 MB). Default: medium. Note: The value for this parameter is in the PORT parameter in the listener. medium. 138 CONTROL-M Installation Guide . or large (350 MB). Default: depends on the size (small. Redo Log Files # 1 Location Path for the first redo log file. For more information about how to locate the listener. or if a parameter occurs more than once in the file. # 2 Location Path for the second redo log file. medium (100 MB). No default. a tablespace and a data file may have been created. Appendix B Installing an Oracle database on Windows 139 . Do not delete raw partitions. You must first remove the database components that were created by the failed installation.name. Size Size for the for the temporary tablespace: small (50 MB).name from v$tablespace t. 5 If a tablespace was created: A Use the drop tablespace <tablespaceName> command to delete the tablespace. 2 Log on to the Oracle database server account as the database administrator. or large (200 MB).Cleaning up a failed existing installation Table 23 Oracle Database – Windows installation parameters (Part 4 of 4) Parameter Description Temporary Component Location Path for the Temporary Tablespace. or large) chosen for the database. Default: depends on the size (small. medium.ts# =t.d.txt file is on the target drive. B Delete that data file associated with the dropped tablespace. Upgrade Parameter Path If the OracleUpgradeParms.ts# . This file contains parameter settings that will be carried over to the new database during migration. To uninstall and cleanup the installation 1 Run the uninstall program (see “Uninstalling a CONTROL-M Oracle database server from Windows” on page 207). 3 Use the drop user <userName> cascade.dbf. an upgrade installation is assumed and the path to this file is displayed. 4 Depending on where and how the installation failed. Cleaning up a failed existing installation Uninstalling and cleanup is necessary before re-running the existing Oracle installation. command to delete the username that was used for the failed installation. Use the following commands to check if a <tablespaceName> (tablespace name) and <datafileName> (data file name) were created for the failed installation.v$datafile d where d. Default: <drive>:\Oracle\oradata\<instanceName>\temp01. col name for a50 select t. Cleaning up a failed existing installation 140 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . NOTE You should use the installation provided with this version of the product to ensure that the Sybase component is correct for the platform you are using. . . . . . . . . The following topics are discussed in this appendix: Interactive installation of the CONTROL-M database . . . . Otherwise the installation may fail. . . . . . . . . . . . . . . . . . . . . . . . . Appendix C Installing a CONTROL-M database with Sybase on UNIX 141 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interactive installation of the CONTROL-M database 1 Ensure that the Sybase database server is up and running. . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation parameters . . . . 141 142 142 144 144 WARNING The CONTROL-M database components must be installed silently if you want to install CONTROL-M/EM or CONTROL-M/Server silently. . . . . 2 Ensure that the client character-set matches the server character-set. . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . Silent installation of the CONTROL-M database . . . . . . . . . . . . . . . . . .Appendix C Installing a CONTROL-M database with Sybase on UNIX C This appendix describes how to install CONTROL-M (CONTROL-M/EM or CONTROL-M/Server) database that will utilize an existing Sybase client. . . Instead.sh 6 Follow the interactive menu instructions specifying parameter values as requested. However no installation is performed. Silent installation of the CONTROL-M database Silent installation is used to install CONTROL-M/EM server or CONTROLM/Server database components from a parameters file. The following stages are involved: ■ Preparing the parameters file This is accomplished by running a silent installation preparatory procedure from the installation DVD. You can reuse this parameters file to silently install the database components on other computers. 142 CONTROL-M Installation Guide . “Installing CONTROL-M/Server” as necessary. 4 Log on to the CONTROL-M/EM or CONTROL-M/Server account. the information you enter is stored in a parameters file. see Appendix I. For information about mounting a DVD. “Installing CONTROL-M/EM on UNIX” or Chapter 5. the database components are installed using the parameters you specified in the previous step. 5 Issue the following command to activate the installation script: <dvdPath>/Sybase/setup. Where to go from here Continue with Chapter 3.Where to go from here 3 Mount the CONTROL-M/EM or CONTROL-M/Server installation DVD from the root user and log off the root user before continuing with the installation. The preparatory procedure behaves like the interactive installation procedure and prompts you to enter the same information. “Mounting DVDs and CDs on UNIX computers”. ■ Running the installation using the prepared parameters file When the installation is run using the prepared parameters file. Appendix C Installing a CONTROL-M database with Sybase on UNIX 143 . 4 Log on to the CONTROL-M/EM or CONTROL-M/Server account. The installation parameters saved to ${HOME}/BMCINSTALL/products/products. “Mounting DVDs and CDs on UNIX computers”. 2 Ensure that the database server is up and running before beginning the database installation. See “Setting environment variables in UNIX” on page 37 for your UNIX environment. During a client installation this is the current database owner password. 3 Mount the CONTROL-M/EM or CONTROL-M/Server installation DVD from the root user and log off the root user before continuing with the installation. see Appendix I. Explanations are provided in Table 24 on page 144. For information about mounting a DVD.Silent installation of the CONTROL-M database To prepare the silent installation parameters file 1 Prepare the parameter information you will need for the installation.ctl.sh 7 Follow the interactive menu instructions specifying parameter values as requested. If you want to change parameter values. 5 Set the environment variable BMC_SILENT_INSTALL to value Y. To install silently 1 Log on to the CONTROL-M/EM or CONTROL-M/Server account. 6 Issue the following command to activate the silent installation script: <dvdPath>/Sybase/setup. 2 Set the following environment variables (see “Setting environment variables in UNIX” on page 37 for your UNIX environment): DBO_PASSWORD to <databaseOwnerPassword> SA_PASSWORD to <databaseAdministratorPassword> <databaseOwnerPassword> is the password that will be set for the owner of the new database. modify them in the parameters file manually. <parameterPath> is the full path to the silent installation file that was created in step 6 of “To prepare the silent installation parameters file” on page 143.sh -r <parameterPath> <dvdPath> is the path of the mounted DVD. This is relevant to an Existing installation mode only. continue with “Silent installation” on page 74 Installation parameters Table 24 UNIX interactive and silent installation parameters (Part 1 of 2) Interactive parameter or prompt Silent installation parameter name Description Database [SETP]/BMC/SYBASE/PRIVILEGE_ Database administrator login name. This is relevant to an Existing installation mode only. Default: sa Database administrator password. This is relevant NAME to an Existing installation mode only. Where to go from here ■ If you are installing CONTROL-M/EM on Unix. This is relevant TABASE_NAME to a client installation in a distributed system only. Database Owner Login (for client) [SETP]/BMC/SYBASE/CLIENT_DA Existing database owner login. .Where to go from here <databaseAdministratorPassword> is the database administrator password. Database Administrator Password Environment variable SA_PASSWORD Database Name [SETP]/BMC/SYBASE/DATABASE_ Database name to be created. Database Owner Login [SETP]/BMC/SYBASE/DATABASE_ Database owner login name that will be OWNER_LOGIN created. 3 Issue the following command: <dvdPath>/Sybase/setup. continue with “Silent installation” on page 51 ■ If you are installing CONTROL-M/Server on Unix. Database Owner Password Environment variable DBO_PASSWORD 144 CONTROL-M Installation Guide This is relevant to a client installation in a distributed system only. This is Administrator Login LOGIN relevant to an Existing installation mode only. LOG_DEVICE_PATH This is relevant to an Existing installation mode only. Installation mode [SETP]/BMC/SYBASE/INSTALLAT Installation mode values: Existing or Client ION_TYPE Default: Existing Installed Sybase root directory [SETP]/BMC/SYBASE/SOFTWARE_ Location of Sybase database software ROOT_DIRECTORY (server/client). Appendix C Installing a CONTROL-M database with Sybase on UNIX 145 . This is relevant to an Existing installation mode only. Log Device Size [SETP]/BMC/SYBASE/DATABASE_ Amount of space (in MB) to allocate for the LOG_DEVICE_SIZE transaction log. You must take into consideration the number of jobs in the Active Jobs file. This is relevant to an Existing SIZE_MODEL installation mode only. Installed Sybase server alias name [SETP]/BMC/SYBASE/DATABASE_ The Sybase alias name as listed in Sybase ALIAS_NAME interfaces file. Large). Data Device Size [SETP]/BMC/SYBASE/DATABASE_ Amount of space (in MB) to allocate for the DATA_DEVICE_SIZE data portion of the database. Medium. Log Device Full Path File Name [SETP]/BMC/SYBASE/DATABASE_ Full path to log device file name to be created.Installation parameters Table 24 UNIX interactive and silent installation parameters (Part 2 of 2) Interactive parameter or prompt Silent installation parameter name Description Data tablespace size [SETP]/BMC/SYBASE/DATABASE_ Size of the CONTROL-M database (Small. This is relevant to an Existing installation mode only. DATA_DEVICE_PATH This is relevant to an Existing installation mode only. Default: Medium Data Device Full Path File Name [SETP]/BMC/SYBASE/DATABASE_ Full path to data device file name to be created. Installation parameters 146 CONTROL-M Installation Guide . . . . . . . Database pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Once you have completed the database server and data files preparation. . . . . . Where to go from here . . . . . . . . . . . . . . . Creating cluster resources for UNIX. . . . . . . . . . . you can install CONTROL-M interactively or silently. . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the database for Windows .Appendix D Preparing clusters for database components D This appendix contains detailed information on how to prepare the database server and CONTROL-M database data files (tablespaces or data files). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 148 149 150 151 152 152 152 154 155 NOTE PostgreSQL clusters are detected and installed automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the database for UNIX If you want to install CONTROL-M in cluster environment. . . . . . . Creating cluster resources for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . you should first plan and prepare the configuration according to the information set out in this section. . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . Database post-installation . . . . . . . . . . . . . . . The following topics are discussed in this appendix: Preparing the database for UNIX . . . . and CONTROL-M for a cluster installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . on UNIX or Windows. . . . . . . . . . . . Database pre-installation . Appendix D Preparing clusters for database components 147 . . . . . . . . . . . . . . . . . . . . as described in this book. . . . . . . . . . . . . . . . . . . . . . . . . . Using the same or different resource group for the database server and the CONTROL-M database If the database server is to be implemented into the same resource group as CONTROL-M. For more information. the client can be located on the same file system as CONTROL-M or on a different file system. so it will be able to connect to a remote database server. use the following guidelines when choosing which resource group your database resources will belong to: 148 CONTROL-M Installation Guide . Some of the choices you need to consider are: ■ ■ ■ a dedicated or existing database server the same or different file systems for the database server and the CONTROL-M database the same or a different resource group for database server and the CONTROL-M software NOTE In a cluster environment. ■ When installing Oracle as the database server. You must also ensure that all Oracle client binaries. the database server and CONTROL-M database must always be running on the same node.Database pre-installation Before starting the installation of the CONTROL-M database. it is only necessary to install a database server on one node. Database pre-installation Using the same or different file systems for the database server and the CONTROL-M database The database server and the CONTROL-M database can be located on the same file system as CONTROL-M. and files have 640 protection. If you are using different file systems. as both accounts point to the same shared location. using the USE_EXISTING_ORACLE environment variable. lib directories. the file system on which the Oracle client is located must always be available to CONTROL-M. Use the following guidelines to determine where to locate the database server: ■ When implementing a CONTROL-M database server in dedicated mode. you must plan how the CONTROL-M database will be implemented. or on different file systems. see your database administrator. the database server is always installed within the same file system. When the implementation is performed using a single resource group. they can either be installed on the same file system or on different file systems as long as both members belong to the same resource group. there must be a dependency between the two resource groups. BMC Software recommends that you use only certified policy files to monitor the CONTROL-M database. Some cluster vendors supply policy files for popular applications. the database server can be implemented in either dedicated or existing mode. However. These features should be configured and administered by an experienced DBA. When using these solutions. such as Oracle. the CONTROL-M home directory path should be identical on the primary and standby hosts.Where to go from here ■ When the database server and CONTROL-M are implemented into the same resource group. the CONTROL-M tablespace can reside on a different file system. Where to go from here You can continue with “Installing CONTROL-M/EM server components” on page 49 or “Silent installation” on page 51. Detailed information about the silent installation procedure is explained in the silent installation section. which enables replicating the Oracle database content to a remote location. ■ When the database server is implemented into a different resource group from CONTROL-M and the implementation is done in a dedicated mode (in this case the database server and CONTROL-M should be located on different file systems). In this case. Application vendors often certify these policy files. Making additional database preference choices CONTROL-M can be implemented on a UNIX cluster that uses a database platform that is configured with additional database high availability features such as Oracle Data Guard (formerly known as Oracle Standby Server). so they will always be running on the same node. which enables you to install multiple instances of Oracle to access the same database simultaneously. ■ On a CONTROL-M installation with Embedded PostgreSQL. or Oracle Real Application Cluster (formerly known as Oracle Parallel Server). both file systems must belong to the same resource group. Appendix D Preparing clusters for database components 149 . Database post-installation Database post-installation Modifying the database network configuration files Sybase (interfaces file) 1 Use the following command to set the DISPLAY parameter to the local terminal address (the IP address of the PC running the telnet/x-window session. run the startdb script in the CONTROL-M/Server account but do not run the start_server script in the CONTROL-M/EM account. 3 Replace the database server host name with the virtual host name of the database resource group. ■ If CONTROL-M/EM is installed with a dedicated database. run the start_server script in the CONTROL-M/EM account but do not run the startdb script in the CONTROL-M/Server account. the following actions may be required: 150 ■ If CONTROL-M/Server is installed with a dedicated database.ora Configuring the policy file When CONTROL-M/Server and CONTROL-M/EM share the same database server (or Oracle instance). 2 Replace the host name with the virtual host name of the database resource group. vhem640 for CONTROL-M/EM 4 Replace the SYB_BACKUP database server host name with the virtual host name of the database resource group. vhem640 for CONTROL-M/EM) in the following files: ■ ■ $ORACLE_HOME/network/admin/tnsnames. vhem640 for CONTROL-M/EM Oracle 1 Ensure that the Oracle server is stopped and that none of the Oracle processes are running. for example. or the IP address of the UNIX console that is being used): setenv DISPLAY terminalAddress:0 2 Run the dsedit application. for example. CONTROL-M Installation Guide .ora $ORACLE_HOME/network/admin/listener. for example. BMC Software recommends that you use that file. you can set the BMC_HOST_INSTALL environment variable to the required host name before beginning the CONTROL-M/EM installation. In a cluster environment: Appendix D Preparing clusters for database components 151 .$CTM_ACC -c $CTM_DIR/ctm/scripts/shutdb Creating cluster resources for UNIX If a different host name is required for the installation rather than the default machine hostname. a multiple network environment). You can also use this variable if there is a possibility of choosing between two or more hosts (for example. use the following commands: # CONTROL-M/EM EM_ACC=em640 DBA_PASS=<emPass> # The CONTROL-M/EM database administrator password EM_DIR=/export1/em640 su .Creating cluster resources for UNIX The CONTROL-M database server can be shut down or started using the following scripts only if it is installed in a dedicated mode. use the following commands: # CONTROL-M/EM EM_ACC=em640 EM_DIR=/export1/em640 su . a cluster installation). For information on setting variables.$EM_ACC -c $EM_DIR/scripts/stop_server << PASSEOF $DBA_PASS PASSEOF exit # CONTROL-M/Server CTM_ACC=ctm640 CTM_DIR=/export2/ctm640 su . If the cluster vendor has a certified database policy file.$EM_ACC -c $EM_DIR/scripts/start_server # CONTROL-M/Server CTM_ACC=ctm640 CTM_DIR=/export2/ctm640 su . see “Setting environment variables in UNIX” on page 37.$CTM_ACC -c $CTM_DIR/ctm/scripts/startdb To stop the CONTROL-M database. To start the CONTROL-M database. or when there is a virtual network name representing a group of hosts (for example. and network name to the installation node. Only a database client is installed on the other node. ■ remote database configuration: The database is installed on a non-clustered server or on a cluster different from where CONTROL-M is installed.Where to go from here ■ Set the BMC_HOST_INSTALL environment variable to the virtual network name designated for the CONTROL-M/EM resource group. Database pre-installation Clustered This section describes a cluster configuration for: 152 ■ Microsoft SQL Server 2005 Enterprise Edition ■ Oracle Real Application Cluster (RAC). Preparing the database for Windows You can use the following types of implementations for the CONTROL-M database in a Windows cluster environment: ■ clustered configuration: A single database installation on the cluster can be accessed by both nodes. Where to go from here You can continue with “Installing CONTROL-M/EM server components” on page 49 or “Silent installation” on page 51. IP address. only database clients are installed on each of the CONTROL-M cluster nodes. CONTROL-M Installation Guide . ■ local database configuration: The database server is locally installed on one of the cluster nodes. ■ Move the disk name. Detailed information about the silent installation procedure is explained in the silent installation section. In this case. This will automatically configure CONTROL-M/EM and the TAO Naming Service to use this virtual network name. The database files are located on the shared disk and the database server availability is controlled by the cluster. The MSSQL Server services (one service is created on each cluster node) are named by default as the virtual server name.com/downloads/details.com/technology/products/database/clustering/RACWhitepapers.aspx?FamilyID=818234dc-a17b4f09-b282-c6830fead499&DisplayLang=en. In addition to the MSSQL services resources. NOTE If. installation of MSSQL Server Enterprise Edition on a Windows cluster automatically creates the network name and IP address resources in the selected resource group. After you prepare the system for installation.Database pre-installation Microsoft SQL (MSSQL) Server 2005 Enterprise Edition When you install MSSQL Enterprise Edition on a cluster. and then propagates the software onto the rest of the chosen nodes of the cluster.microsoft. the Oracle Universal Installer (OUI) presents the list of all cluster nodes. the software binaries of the product are placed on the local drives of each one of the selected nodes and the data files are placed on the assigned disk resource on the shared drive. enabling you to select a subset as targets. Oracle Enterprise Manager (the central managing console) is automatically installed and set up. In case of a node failure. the MSSQL services are stopped on the original (primary) node and started on the alternate node. Along with all the Oracle software. the workload of this node will be handled by the other node of the cluster. For more information about Oracle RAC installation. Then the OUI copies the Oracle software onto the first node. At that point. this means that the version you are installing is not the MSSQL Enterprise Edition and cannot be installed in cluster mode. Oracle Real Application Cluster (RAC) A normal Oracle installation consists of a single Oracle instance that accesses a database on the same computer system. When the MSSQL resource group is moved from one node to another. Appendix D Preparing clusters for database components 153 . during installation. For more information about installing MSSQL Server Enterprise Edition on Windows. the database creation wizard and the network configuration wizard will be automatically invoked. When the installation is finished. the MSSQL resource group becomes a virtual server and can be accessed by client applications using the virtual name. you see that the Virtual Server option in the Computer Name window is disabled. With RAC (formerly known as Oracle Parallel Server).html. see the Oracle installation documentation or the Oracle RAC whitepapers at http://www.oracle. multiple instances on different nodes can access the same database files simultaneously. see “SQL Server 2005 Failover Clustering White Paper” at http://www. IP. This configuration is common when database platforms reside in a centralized location. CONTROL-M Installation Guide . and Network Name resources must be online in the virtual server group where an instance of CONTROL-M on Microsoft Windows is to be installed. Creating cluster resources for Windows The CONTROL-M installation requires Disk. ■ Silent installation of CONTROL-M is not supported for Microsoft Windows cluster environments. you can install a database client on each of the cluster nodes and connect them to the remote database server. When you install CONTROL-M/EM to the same virtual server (resource group) as CONTROL-M/Server or MSSQL Server. In this type of implementation. Remote database configuration When the database server is located on a remote node (not one of the cluster nodes). ■ Disk. Network Name and IP Address virtual resources to be created before you begin. but it will not be maintained in a highly available manner. the database can be accessible to all the nodes in the cluster. The following conditions apply to cluster resources: 154 ■ Do not share the IP and Network Name resources that identify the cluster with a CONTROL-M cluster instance. Local database configuration This configuration is based on the concept of installing the database server on one of the cluster nodes and the database clients on the rest of the cluster nodes. However. This configuration is not recommended for CONTROL-M when implemented in a clustered configuration.Creating cluster resources for Windows NOTE Oracle high availability features are only relevant for CONTROL-M/Enterprise Manager. In this way. the availability of CONTROL-M in this type of configuration is tied to and dependent on the remote database server availability. They are automatically created by the CONTROL-M/Server or MSSQL Server installation. you do not need to manually create the Network Name and IP address cluster resources. you do not need to install additional database software on the cluster (besides the database client). Where to go from here You can continue with “Interactive installation” on page 55 or “Silent installation” on page 56. Select a group Highlight the virtual server group for which this CONTROL-M/EM instance IP address and the network name were created. TAO CORBA settings and CONTROL-M/EM server component parameters are configured to work with the virtual hostname that is provided by the user during the installation process. Select the Network resource Select the network name resource that was created for this CONTROL-M/EM instance.Where to go from here ■ CONTROL-M/EM must be installed on the shared disk that is designated for the CONTROL-M/EM resource group in the cluster environment. Detailed information about the silent installation procedure is explained in the silent installation section. Windows cluster installation parameters Table 25 Windows cluster parameters . Select the Disk resource Select the Disk resource for this CONTROL-M/EM instance. Appendix D Preparing clusters for database components 155 .for interactive installations only Parameter Description Cluster Management This “display-only” field indicates the order in which clusters will perform failover handling. ■ As part of the CONTROL-M/EM cluster aware installation procedure. Where to go from here 156 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating BMC Batch Impact Manager and CONTROL-M/Forecast cluster resources. . . . . . . . . . . . . . . . Installing BMC Batch Impact Manager on clusters . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M Configuration Manager administration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The following topics are discussed in this appendix: Setting up the CONTROL-M/EM UNIX cluster environment . . . . . Installing CONTROL-M/EM client components . . . . . . . . . . Appendix E Configuring CONTROL-M/EM clusters 157 . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up failover nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/Forecast on clusters . . . . . . . . . . Where to go from here . . . . . . . . . Create CONTROL-M/EM Gateway cluster resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the CONTROL-M/EM client components on Windows . . Set up the host and listener . . . . . . . . .Appendix E E Configuring CONTROL-M/EM clusters This appendix contains detailed information on how to configure clusters on CONTROL-M/EM. . . . . . . . . . . . . . . Cluster administration mode . . Cluster administration mode . . . . . Setting up the CONTROL-M/EM Windows cluster environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 158 159 160 171 172 174 174 175 176 178 179 180 180 181 Setting up the CONTROL-M/EM UNIX cluster environment You can control and monitor the CONTROL-M/EM server components by using either CONTROL-M Configuration Manager administration mode or cluster administration mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . These components are the GUI Server. the Global Alerts Server. and CONTROLM/Forecast.) The logical name support feature is enabled by setting the $BMC_HOST_INSTALL environment variable prior to starting the installation. define each of the CONTROLM/EM server components using the logical name assigned to BMC_EM_PROFILE_NAME.CONTROL-M Configuration Manager administration mode NOTE When defining the CONTROL-M/EM server components in the CONTROL-M Configuration Manager. 158 CONTROL-M Installation Guide . use the virtual host name as the component name for the servers that use CORBA communication protocol. This value will be used as the logical name for all CONTROL-M/EM server components you want to manage as a single group using CONTROL-M/EM Configuration Agent. 2 Using the CONTROL-M Configuration Manager. 3 For each CONTROL-M/EM server component you want to manage as a group: A Open the CONTROL-M/EM Component Window of the CONTROL-M Configuration Manager B Set the Host Name field in the Running on area to the value of the BMC_EM_PROFILE_NAME environment variable. Set the Name field in the Component area to the value of the BMC_EM_PROFILE_NAME environment variable CONTROL-M/EM Configuration Agent will now manage only those CONTROLM/EM server components whose Host Name is set to the BMC_EM_PROFILE_NAME value. To use CONTROL-M Configuration Manager administration mode 1 Ensure that the BMC_EM_PROFILE_NAME environment variable has the cluster virtual name as its value. CONTROL-M Configuration Manager administration mode CONTROL-M Configuration Manager administration mode uses the logical name support feature in the CONTROL-M/EM Configuration Agent and the CONTROL-M Configuration Server (see the CONTROL-M Administrator Guide for more information on CONTROL-M/EM Configuration Agent and CONTROL-M Configuration Server. the CONTROL-M Configuration Server. C For components that use CORBA. BMC Batch Impact Manager. Instead. see “Using CONTROL-M Configuration Manager administration mode” on page 161. Appendix E Configuring CONTROL-M/EM clusters 159 . To view process states from the CONTROL-M Configuration Manager 1 Ensure that the BMC_EM_PROFILE_NAME environment variable has the cluster virtual name as its value. the cluster software is used to start. according to the commands described in “Cluster administration mode” on page 162. 4 Start the CONTROL-M/EM Configuration Agent by executing the following script from the command line: start_config_agent For additional information about monitoring of the CONTROL-M/EM server components. 3 Define the “desired state” of each of the CONTROL-M/EM server components to ignored. stop. and monitor the CONTROL-M/EM server components. and a complete list of the processes names. In this mode.Cluster administration mode For additional details. see “Monitoring CONTROLM/EM processes” on page 164. 2 Using the CONTROL-M Configuration Manager. the CONTROL-M/EM server components should be defined as resources. CONTROL-M Configuration Manager and CONTROL-M/EM Configuration Agent are not used. define each of the CONTROLM/EM server components using the logical name assigned to BMC_EM_PROFILE_NAME. Cluster administration mode When managing CONTROL-M/EM server components in cluster administration mode. This value will be used as the logical name in the Running on and Component areas for all CONTROL-M/EM server components you want to manage as a single group using CONTROL-M/EM Configuration Agent. ■ When managing the CONTROL-M/EM Server components by cluster. If the failover time of the resource group is longer than the reconnection retries. This name represents the registered name of the CONTROL-M/EM Server component in the CORBA naming service repository. which is displayed after clicking Advanced. define the server components in the CONTROL-M Configuration Manager using the virtual host name as the component name. which should be the physical host name of the active node.Installing the CONTROL-M/EM client components on Windows Installing the CONTROL-M/EM client components on Windows 1 Ensure that the virtual host name (in the example: vhem640) is properly defined in the DNS or local hosts file so it can be accessed by name or IP address from Microsoft Windows. start the server component that uses CORBA using the -name parameter. the name is the physical host name of the computer. 160 CONTROL-M Installation Guide . and timeout. 4 The server name is automatically displayed once the connection to the CORBA Naming service is established. change these parameters in the CONTROL-M/EM reconnection panel of the options menu. use the virtual host name defined in the $BMC_HOST_INSTALL environment variable (during client installation. This name differs from the machine name value. enter the virtual host name as the location for the ■ ■ ■ ■ GUI Server CORBA Naming Service Database Server Name (when Installing client administration components) CONTROL-M Configuration Server 3 When logging on to the CONTROL-M/EM GUI. 2 During client installation. CONTROL-M/EM client components are configured to reconnect to the GUI Server upon disconnection. see “Configuring the policy file. By default. For additional information and examples. this variable is set to the virtual network name designated for the CONTROLM/EM resource group) to connect to the CORBA Naming repository. To register the CONTROL-M/EM Server components using the virtual host name (as referred to in the example: vhem640) use one of the following options: ■ When managing CONTROL-M/EM Server components using the CONTROLM Configuration Manager. This name is resolved by the network and should be identical to the name set in the environment variable.” 5 By default. where the value of the parameter should be the virtual host name (as referred to in the example: vhem640). The virtual host name should be entered in the Host Name field. $EM_ACC -c “$EM_DIR/app1/bin/ecs cms-name $EMDB_VNAME” & # Start the CONTROL-M/EM Configuration Agent and the CONTROL-M/EM Server components su .$EM_ACC -c "$EM_DIR/appl/bin/ecs ctl-U $EM_OWNER -P $EM_OWPD -C CMS -name $EMDB_VNAME -cmd stop” sleep 5 # Stop CONTROL-M EM CORBA Naming Service su . This step is performed automatically if the $BMC_HOST_INSTALL environment variable is set prior to starting the installation. Using CONTROL-M Configuration Manager administration mode To start the CONTROL-M/EM components. EM_ACC='em640' EM_OWNER='emuser' EM_OWPD='empass' EMDB_VNAME='vhem640' EM_DIR='/export1/em640' PLATFORM='<platform>' # Stop the CONTROL-M/EM Configuration Agent and all components su .$PLATFORM/orbadmin ns stop -local" sleep 5 Appendix E Configuring CONTROL-M/EM clusters 161 .Installing the CONTROL-M/EM client components on Windows Configuring the policy file Configure the policy file according to the instructions provided below for either the CONTROL-M Configuration Manager administration mode or the cluster administration mode. enter the following commands.$EM_ACC -c "$EM_DIR/appl/bin/ecs ctl -U $EM_OWNER -P $EM_OWPD -C Config_Agent -all cmd shutdown" # Stop CONTROL-M Configuration Server su .$EM_ACC -c $EM_DIR/scripts/start_config_agent NOTE Ensure that the BMC_EM_PROFILE_NAME environment variable is set in the account prior starting the CONTROL-M Configuration Server and the CONTROL-M/EM Configuration Agent. enter the following commands. To stop the CONTROL-M/EM components. EM_ACC='em640' EM_DIR='/export1/em640' EM_OWNER='emuser' EM_OWPD='empass' EMDB_VNAME='vhem640' HOSTNAME=`hostname` # Start CONTROL-M EM CORBA Naming Service su .$EM_ACC -c $EM_DIR/scripts/start_ns_daemon # Start CONTROL-M Configuration Server su .$EM_ACC -c "$EM_DIR/appl/ecs/bin. $EM_ACC -c "$EM_DIR/appl/bin/ecs gtw -dc $CTM_VNAME" 162 CONTROL-M Installation Guide .$EM_ACC -c "$EM_DIR/appl/bin/ecs gcsrv" # Start CONTROL-M EM Gateway su . EM_ACC='em640' EM_VNAME='vhem640' CTM_VNAME='vhctm640' EM_DIR='/export1/em640' # Start CONTROL-M EM CORBA Naming Service su . enter the following commands.$EM_ACC -c "$EM_DIR/appl/bin/ecs guisrv -name $EM_VNAME" # Start CONTROL-M EM Global Alerts Server su .Installing the CONTROL-M/EM client components on Windows NOTE Modify <platform> to the correct folder name according to the relevant platform vendor.$EM_ACC -c “$EM_DIR/scripts/start_ns_daemon” # Start CONTROL-M Configuration Server su .$EM_ACC -c “$EM_DIR/app1/bin/ecs cms -name $EMDB_VNAME” # Start CONTROL-M EM GUI Server su .$EM_ACC -c "$EM_DIR/appl/bin/ecs gasrv -name $EM_VNAME" # Start CONTROL-M EM Global Conditions Server su . _co Cluster administration mode To start the CONTROL-M/EM components. $EM_ACC -c "$EM_DIR/scripts/start_web_server.Installing the CONTROL-M/EM client components on Windows To stop the CONTROL-M/EM components.sh" Appendix E Configuring CONTROL-M/EM clusters 163 .$EM_ACC -c "$EM_DIR/appl/bin/ecs ctl-U $EM_OWNER -P $EM_OWPD -C CMS -name $EMDB_VNAME -cmd stop” sleep 5 # Stop CONTROL-M EM CORBA Naming Service su . ■ Create a Gateway resource for each CONTROL-M/Server that is connected to CONTROL-M/EM.$EM_ACC -c "$EM_DIR/appl/ecs/bin.$EM_ACC -c "$EM_DIR/appl/bin/ecs ctl -U $EM_OWNER -P $EM_OWPD -C GAS -name $EM_VNAME -cmd stop" sleep 3 # Stop CONTROL-M EM Global Conditions Server su . the CONTROLM/Server should be defined using the CONTROL-M Configuration Manager.$EM_ACC -c "$EM_DIR/appl/bin/ecs ctl -U $EM_OWNER -P $EM_OWPD -C GUI_Server -name $EM_VNAME -cmd stop" sleep 3 # Stop CONTROL-M EM Global Alerts Server su .$EM_ACC -c "$EM_DIR/appl/bin/ecs ctl -U $EM_OWNER -P $EM_OWPD -C GCS -M $HOSTNAME cmd stop" sleep 3 # Stop CONTROL-M EM Gateway su . Commands for starting the CONTROL-M Web Server: # Start the CONTROL-M Web Server EM_ACC='em640' EM_DIR='/export1/em640' su . In the resource command line. ■ Before defining the CONTROL-M/EM Gateway cluster resource. enter the following commands. indicate the CONTROL-M/Server name as a value to the -dc parameter.$PLATFORM/orbadmin ns stop -local" sleep 5 NOTE ■ Modify <platform> to the correct folder name according to the relevant platform vendor. EM_ACC='em640' EM_OWNER='emuser' EM_OWPD='empass' EM_VNAME='vhem640' HOSTNAME=`hostname` EM_DIR='/export1/em640' CTM_VNAME='vhctm640' PLATFORM='<platform>' # Stop CONTROL-M EM GUI Server su .$EM_ACC -c "$EM_DIR/appl/bin/ecs ctl -U $EM_OWNER -P $EM_OWPD -C Gateway -dc $CTM_VNAME -cmd stop" sleep 3 # Stop CONTROL-M Configuration Server su . gcsrv CONTROL-M/EM Configuration Agent ecs.maintag CONTROL-M Installation Guide . If the components are monitored by the cluster. Failover decisions should be made together with the database administrator.gasrv Gateway ecs. The cluster application should monitor all these processes and should switch the database application if any of them fails.$EM_ACC -c "$EM_DIR/scripts/stop_web_server. Table 27 164 CONTROL-M/EM processes CONTROL-M/EM component Process name GUI Server ecs.0. use the process names for the cluster monitoring definitions as specified in Table 27.sh" sleep 3 Monitoring Oracle database processes Oracle architecture (beginning with version 8.gtw -dc dcName Global Condition Server (GCS) ecs.x) is built on the mandatory processes shown in Table 26. and one optional process. Failover action decisions should be made together with the database administrator. Table 26 Oracle processes Oracle process Process name System Monitor ora_smon_instanceName Process Monitor ora_pmon_instanceName The cluster should monitor both these processes and should switch the database package if either process fails. Monitoring CONTROL-M/EM processes CONTROL-M/EM components can be monitored by the CONTROL-M/EM Configuration Agent or by the cluster.guisrv Global Alert Server (GAS) ecs.Installing the CONTROL-M/EM client components on Windows Commands for stopping the CONTROL-M Web Server: # Stop the CONTROL-M Web Server EM_ACC='em640' EM_DIR='/export1/em640' su . called listener. Installing the CONTROL-M/EM client components on Windows Table 27 CONTROL-M/EM processes CONTROL-M/EM component Process name TAO Naming Service Naming_Service -p ${HOME}/var/ns. Appendix E Configuring CONTROL-M/EM clusters 165 . 2 In the CONTROL-M Configuration Manager. the physical host name of the cluster node becomes unavailable. This configuration provides the ability to send life check communications to the CONTROL-M/EM Configuration Agent using the virtual host name.cms Troubleshooting a UNIX cluster installation This phase presents troubleshooting information for the following components: ■ ■ CONTROL-M/EM Configuration Agent Global Condition Server CONTROL-M/EM Configuration Agent In some cases. choose Tools => System Parameters.bimsrv CONTROL-M/Forecast ecs.forecastserver BMC Batch Discovery ecs. This configuration should only be used if the CONTROL-M/EM Configuration Agent appears in the CONTROL-M Configuration Manager as Not Responding after starting the CONTROL-M/EM Configuration Agent. In such case. To add a HostPort system parameter for the CONTROL-M/EM Configuration Agent: 1 Stop the CONTROL-M/EM Configuration Agent from root_menu or by running the command stop_config_agent from the shell prompt (this requires the CONTROL-M/EM DBO password).pid -u ${HOME}/var BMC Batch Impact Manager Server ecs.batchdiscovery CONTROL-M Configuration Manager ecs. after setting a virtual host name online. additional configuration is required for the CONTROL-M/EM Configuration Agent. the CONTROLM/EM Configuration Agent will listen on a random port that is chosen when the CONTROL-M/EM Configuration Agent starts. If a port other than zero is specified. which is specified in the format: virtualHostName:port By specifying 0 (zero) as the port number. a separate condition must be specified with the physical host names of each cluster node specified in the Host Name parameter. 7 Start the CONTROL-M/EM Configuration Agent. This configuration should only be used if the GCS failed to start after a failover. select the HostPort parameter and click New to open the “Add New Parameter” dialog box. In such case. after setting a virtual host name online. additional configuration is required for the GCS. Advanced field: Type Advanced field: Name Advanced field: Host Maint Agent * (the default value) * (the default value) NOTE If the installation of the CONTROL-M/EM components is distributed between additional hosts other then the cluster nodes. the CONTROLM/EM Configuration Agent will use the specified port number. the physical host name of the cluster node becomes unavailable. Global Condition Server In some cases.Installing the CONTROL-M/EM client components on Windows 3 In the general section. 6 Click Save. 166 CONTROL-M Installation Guide . 4 In the “Add New Parameter” dialog box. click Advanced. 5 Modify the following field values: Field Value Type Name Value General (the default value) HostPort (the default value) vhem640:0. Advanced field: Type GCS Advanced field: Name * (the default value) Advanced field: Host * (the default value) 7 Click Save. select the HostPort parameter and click New to open the “Add New Parameter” dialog box. choose Tools => System Parameters. ensure the following servers are not running: ■ ■ ■ ■ CONTROL-M/EM GUI Server Global Alerts Server BMC Batch Impact Manager Server (BIM) CONTROL-M/Forecast Appendix E Configuring CONTROL-M/EM clusters 167 . 5 In the “Add New Parameter” dialog box.Installing the CONTROL-M/EM client components on Windows To add a HostPort system parameter for the GCS: 1 Start the CONTROL-M Configuration Manager and change the desired state of the GCS to DOWN. 6 Modify the following field values: Field Value Type Name Value General (the default value) HostPort (the default value) vhem640:55443. which is specified in the format: virtualHostName:port Do not specify 0 as the port number. Manually reconfiguring TAO to use the Virtual Network name To manually reconfigure TAO: 1 On the first node. 3 In the CONTROL-M Configuration Manager. 8 Start the GCS using the CONTROL-M Configuration Manager. hostcla. click Advanced. 4 In the general section. 2 Ensure that the GCS is not running on any of the cluster nodes (ps -ef | grep gcs). x or later is used. Ensure that the port is available and is not used by other programs on any of the cluster nodes. 1 Log in to the CONTROL-M/EM account on the active node. and then click Finish. 2 Install BMC Batch Impact Manager according to the instructions provided in the CONTROL-M Business Service Management Solutions User Guide. and then click Next. and then click Next. enter the CONTROL-M/EM virtual host name. Ensure JRE version 1. 10 Start the TAO Naming Server by running the following command: start_ns_daemon Installing BMC Batch Impact Manager on clusters This procedure is optional.5. and click Next. 7 Enter the CONTROL-M/EM virtual host name (as referred to in the example: vhem640) and the relevant port (default: 13075). 8 Set CONTROL-M/EM ports or leave default settings. 9 Ensure all relevant entries in the summary reports refer to the virtual host name.” 3 Set the JAVA_HOME environment variable to the JRE installation directory.Installing the CONTROL-M/EM client components on Windows 2 Stop the CORBA Naming Service from the root_menu or by entering the following command: stop_ns_daemon The following message is displayed: Naming “Service was successfully stopped. It is intended only for customers who are licensed to use BMC Batch Impact Manager and have installed BMC Batch Impact Manager in the cluster environment. 4 Set the DISPLAY environment parameter to terminalAddress:0 5 Activate the Domain Configuration wizard by running the orbconfigure java utility. For information on setting variables. 168 CONTROL-M Installation Guide . see “Setting environment variables in UNIX” on page 37. 6 Modify the published address to the virtual host name. use the following parameter values: — Type: BIM — Machine Type: UNIX — GUI Server Name: <virtualHostName> — Machine Name: <virtualHostName > — Additional parameters: -name=<virtualHostName> NOTE <virtualHostName > should be the value defined for the BMC_EM_PROFILE_NAME environment variable ■ When using the cluster to manage CONTROL-M/EM components.Installing the CONTROL-M/EM client components on Windows 3 The target installation folder should be on the folder in which CONTROL-M/EM was installed on the shared disk. add the following commands to the policy file of CONTROL-M/EM: — To start the BMC Batch Impact Manager Server component.$EM_ACC -c "$EM_DIR/appl/bin/ecs ctl -U $EM_OWNER -P $EM_OWPD -C BIM -name $EM_VNAME -cmd stop" sleep 3 # Stop the Web Application Server (enter necessary commands) Appendix E Configuring CONTROL-M/EM clusters 169 .$EM_ACC -c "$EM_DIR/appl/bin/ecs bimsrv -name=$EM_VNAME -gsr=$EM_VNAME" & — To stop the BMC Batch Impact Manager Server component. enter the following commands: EM_ACC='em640' EM_OWNER='emuser' EM_OWPD='empass' EM_VNAME='vhem640' EM_DIR='/export1/em640' # Stop Batch Impact Manager Server su . 5 Follow the instructions below according to the method you use to manage CONTROL-M/EM components: ■ For CONTROL-M Configuration Manager. enter the following commands: EM_ACC='em640' EM_VNAME='vhem640' EM_DIR='/export1/em640' # Start the Web Application Server (enter necessary commands) # Start Batch Impact Manager Server su . 4 Deploy the BMC Batch Impact Manager web application according to the instructions provided in the CONTROL-M Business Service Management Solutions User Guide. 4 Follow the instructions below according to the method you use to manage CONTROL-M/EM components: 170 CONTROL-M Installation Guide . open a web browser in Microsoft Windows and enter the following URL: http://virtualName:8080/bim EXAMPLE http://vhem640:8080/bim 7 Click Advanced. 9 Click Add Host. 3 The target installation folder should be on the folder in which CONTROL-M/EM was installed on the shared disk. 8 Modify the following field values: Field Value Host By default. the host name indicates the physical host name of the cluster node. 10 Click Login to log on to BMC Batch Impact Manager.Installing the CONTROL-M/EM client components on Windows 6 After starting the CONTROL-M/EM resource group and the BMC Batch Impact Manager Web Application Server resources are up and running. Installing CONTROL-M/Forecast on clusters This procedure is optional. Replace the default host name with the CONTROL-M/EM virtual host name. It is intended only for customers who are licensed to use CONTROL-M/Forecast and have installed CONTROL-M/Forecast in the cluster environment. 2 Install CONTROL-M/Forecast according to the instructions provided in the CONTROL-M Business Service Management Solutions User Guide. 1 Log into the CONTROL-M/EM account on the active node. $EM_ACC -c "$EM_DIR/appl/bin/ecs forecastserver -n $EM_VNAME -gsr=$EM_VNAME" & — To stop the CONTROL-M/Forecast Server component. use the following parameter values: — Type: Forecast Server — Machine Type: UNIX — GUI Server Name: <virtualHostName> — Machine Name: <virtualHostName > — Additional parameters: -name=<virtualHostName> NOTE <virtualHostName > should be the value defined for the BMC_EM_PROFILE_NAME environment variable ■ When using the cluster to manage CONTROL-M/EM components. enter the following commands: # Start CONTROL-M Forecast Server EM_ACC='em640' EM_VNAME='vhem640' EM_DIR='/export1/em640' su .Where to go from here ■ For CONTROL-M Configuration Manager. add the following commands to the policy file of CONTROL-M/EM: — To start the CONTROL-M/Forecast Server component. enter the following commands: # Stop CONTROL-M EM Forecast Server EM_ACC='em640' EM_OWNER='emuser' EM_OWPD='empass' EM_VNAME='vhem640' EM_DIR='/export1/em640' su . Appendix E Configuring CONTROL-M/EM clusters 171 .$EM_ACC -c "$EM_DIR/appl/bin/ecs ctl -U $EM_OWNER -P $EM_OWPD -C Forecast_Server -name $EM_VNAME -cmd stop" sleep 3 Where to go from here You have now completed the installation of CONTROL-M/EM with clusters on UNIX using clusters. you do not need to manually create the Network Name and IP address cluster resources. ■ Silent installation of CONTROL-M/EM is not supported for Microsoft Windows cluster environments. To create the IP Address resource 1 From the Cluster Administrator interface. 3 In the New Resource window. EM640).Setting up the CONTROL-M/EM Windows cluster environment Setting up the CONTROL-M/EM Windows cluster environment Review the following notes if you will be installing CONTROL-M/EM in a Microsoft Windows cluster environment: ■ Do not share the IP and Network Name resources that identify the cluster with a CONTROL-M/EM cluster instance. select the relevant resource group. The CONTROL-M/EM installation requires Disk. use the following procedures to create these cluster resources and bring them online. 2 Right-click an empty space in the group and choose New => Resource. perform the following steps. 172 CONTROL-M Installation Guide . Network Name and IP Address virtual resources to be created before you begin. ■ Disk. When you install CONTROL-M/EM into a new resource group or a resource group that does not include Disk. C Select resource type IP Address. and Network Name resources must be online in the virtual server group where an instance of CONTROL-M/EM on Microsoft Windows is to be installed. and then click Next: A Enter the name that will be assigned to the IP address cluster resource (for example. B Enter a description for the IP address cluster resource (for example. D Ensure that the selected group is the CONTROL-M/EM resource group (by default. IP. EM640 – IP Address). Virtual IP Address). When you install CONTROL-M/EM to the same virtual server (resource group) as CONTROL-M/Server or MS-SQL Server. Network Name and IP Address resources. They are automatically created by the CONTROL-M/Server or MS-SQL Server installation. select the relevant resource group. 2 Right-click an empty space in the group and choose New => Resource. The New Resource window is displayed. C Select the Enable NetBIOS for this address check box. EM640 – Network Name). B Select Network type External. 6 In the Network Name Parameters window. and then click Next. and then click Next: A Enter the name that will be assigned to the Network Name cluster resource (for example. select the IP Address cluster resource that you are creating and click Add to add it to the resource dependencies list in the right column. 4 In the Possible Owners window. EM640). perform the following steps. and then click Finish. ensure that all the nodes on which the CONTROL-M/EM can be brought online are listed in the Possible owners column. click Next. and then click Next. D Ensure that the selected group is the CONTROL-M/EM resource group (by default.Setting up the CONTROL-M/EM Windows cluster environment 4 In the Possible Owners window. enter the name for the CONTROLM/EM virtual server. ensure that all the nodes on which the CONTROL-M/EM can be brought online are listed in the Possible owners column. To create the Network Name resource 1 From the Cluster Administrator interface. 5 In the Dependencies window. C Select resource type Network Name. B Enter a description for the Network Name cluster resource (for example. 5 In the Dependencies screen. 6 In the TCP/IP Address Parameters window. 3 In the New Resource window. EM640 – Network Name). The Subnet mask field is automatically set. Appendix E Configuring CONTROL-M/EM clusters 173 . perform the following steps. and then click Finish: A Enter the CONTROL-M/EM virtual IP address. ora and listener. These components are the GUI Server. Cluster administration mode NOTE When defining the CONTROL-M/EM server components in the CONTROL-M Configuration Manager. the CONTROL-M/EM server components should be defined as resources. the CONTROL-M Configuration Server. Set up the host and listener The cluster environment on Oracle required you to perform the following actions: 1 Change the HOST parameter to the virtual host name in the Oracle configuration files tnsnames. from the command prompt. When managing CONTROL-M/EM server components in cluster administration mode. according to the commands described in “Cluster administration mode” on page 162. In this mode. BMC Batch Impact Manager. 174 CONTROL-M Installation Guide . the Global Alerts Server. 3 To ensure the network name and IP address are published in the network. Instead. use the virtual host name as the component name for the servers that use CORBA communication protocol. stop. as defined in step 6 of the “To create the Network Name resource”task. 2 Stop and then restart the listener service.ora.Set up the host and listener To bring the resources online 1 From the Cluster Administrator interface. 2 Right-click the group and choose Bring Online. and CONTROLM/Forecast. The files are located in the <oracleHome>\ora1010\network\admin folder. ping the CONTROL-M/EM virtual server. select the CONTROL-M/EM resource group. the cluster software is used to start. CONTROL-M Configuration Manager and CONTROL-M/EM Configuration Agent are not used. and monitor the CONTROL-M/EM server components. exe Current directory <EM_ROOT>\bin Pending timeout in seconds 10 Dependencies Database resource Advanced Do not restart 5 Set the resource to the online state. Appendix E Configuring CONTROL-M/EM clusters 175 . Create CONTROL-M/EM Gateway cluster resource CONTROL-M/EM Gateway cluster resources must be defined manually after installation of CONTROL-M/EM had been completed as the location of CONTROLM/Server is not available during the installation. by creating a new generic application resource using the details in Table 28. see “Monitoring CONTROLM/EM processes” on page 164. and a complete list of the processes names. define each of the CONTROLM/EM server components using the logical name assigned to BMC_EM_PROFILE_NAME. This value will be used as the logical name for all CONTROL-M/EM server components you want to manage as a single group using CONTROL-M/EM Configuration Agent. 4 Define a cluster resource for the CONTROL-M/EM Configuration Agent. Table 28 Defining a cluster resource Resource attribute CONTROL-M-EM-Configuration-Agent Description CONTROL-M/EM Configuration Agent (for monitoring purposes only) Resource type generic application Group EM640 Command line <EM_ROOT>\bin\ecs_maintag.Create CONTROL-M/EM Gateway cluster resource To view process states from the CONTROL-M Configuration Manager 1 Ensure that the BMC_EM_PROFILE_NAME environment variable has the cluster virtual name as its value. 2 Using the CONTROL-M Configuration Manager. For additional information about monitoring of the CONTROL-M/EM server components. 3 Define the “desired state” of each of the CONTROL-M/EM server components to ignored. 2 Open a command prompt and navigate to the <rootFolder>\3rd folder on the installation DVD or CD. Table 29 CONTROL-M/EM Gateway resource definition Resource attribute CONTROL-M-EM-Gateway (CTM/SRVName) Description CONTROL-M/EM Gateway Resource type generic application Group EM640 Command line <EM_ROOT>\bin\ecs_gtw. IP address. Setting up failover nodes On each failover node. Create a new generic application resource using the details in Table 29.bat from the installation DVD 176 CONTROL-M Installation Guide . define a cluster resource for each gateway component. 4 Run Windows\3RD\setup.Setting up failover nodes To create the CONTROL-M/EM Gateway cluster resource 1 Define CONTROL-M/Server definition using the CONTROL-M Configuration Manager. 3 Ensure that the Disk. and Network Name resources are online on the failover node. 2 For each CONTROL-M/Server defined. The Desired State parameter for the gateway must be set to ignored. perform the following steps: 1 Verify that the owner of the CONTROL-M/EM cluster group is the primary node on which you installed the full CONTROL-M/EM installation.exe -dc dcName Current directory <EM_ROOT>\bin Pending timeout in seconds 10 Dependencies Database resource NOTE Before defining a CONTROL-M/EM Gateway cluster resource. the corresponding CONTROL-M/Server must first be defined using the Communication Administration window in CONTROL-M Configuration Manager. msc E From the command line (Start -> Run).msc F Browse to Security Setting -> Local Policies -> User Rights Assignments and select Log On as Service policy G Click Locations H Select the current node name I In Enter the object name to select. run secpol. C Issue the Bring Online command to bring the CONTROL-M/EM cluster group on this node online and D Verify that the current node is online in the Windows Cluster Administrator window. give Log On as a Services privileges to the local NT user that was created for PostgreSQL by performing the following steps: A From the command line (Start -> Run). Appendix E Configuring CONTROL-M/EM clusters 177 .msc B Locate PostgreSQL for CONTROL-M/EM 640 C Locate . enter a name for the this account service. B Verify that the disc on which you installed CONTROL-M/EM is accessible from this node.\<name of user> and save this name for later. 7 Check that the current node of CONTROL-M/EM cluster group is online by performing the following steps: A Issue the Move Group command to move the CONTROL-M/EM cluster group to the current node. 5 On a PostgreSQL installation. D Exit Service. run Services.Setting up failover nodes NOTE The following step applies only for a PostgreSQL installation. This name is the <name of user> you saved in step C 6 Restart the computer. change these parameters in the options menu of the CONTROL-M/EM reconnection panel. which is on the cluster machine. CONTROL-M/EM client components are configured to reconnect to the GUI server upon disconnection. use the virtual host name configured by the installation to connect to the CORBA Naming repository. If the failover time of the resource group is longer than the value for Max reconnection retries times the value for Wait seconds between reconnection attempts. is configured to function in a firewall environment and orbconfigure is activated. This name is resolved by the network and must be identical to the name configured by the CONTROL-M/EM cluster aware installation. use the database virtual host name) when you install the database client. use the virtual host name for the location of the CONTROL-M/EM. change the values for these parameters in the CONTROL-M/EM Reconnection panel of the Options menu. By default. CONTROL-M/EM client components are configured to reconnect to the GUI Server upon disconnection.Installing CONTROL-M/EM client components Installing CONTROL-M/EM client components When you install CONTROL-M/EM client components. which is displayed after clicking Advanced. 2 During client installation. 5 If the CONTROL-M/EM installation. the following commands must be executed from the cluster machine command line to correctly configure the local CONTROL-M/EM client components. Enter the virtual host name in the Host Name field. 1 Ensure that the virtual host name is properly defined in the DNS or host file so it can be accessed by name or IP address from Microsoft Windows. If the CONTROL-M/EM administration components (CONTROL-M Configuration Manager and Reporting facility) are installed as well. If the failover time of the resource group is longer than the reconnection retries and timeout. enter the virtual host name as the location for the: ■ ■ ■ CONTROL-M Configuration Server GUI Server CORBA Naming Service 3 When logging on to the CONTROL-M/EM GUI. 178 ■ orbadmin variable modify -scope GUI -value "iiop://" -ORBListenEndpoints ■ orbadmin variable modify -scope Desktop -value "iiop://" -ORBListenEndpoint ■ orbadmin variable modify -scope CLI -value "iiop://" -ORBListenEndpoints CONTROL-M Installation Guide . 4 By default. 4 Using the Cluster Administrator interface. For full information on installing BMC Batch Impact Manager. 6 Open the web browser and enter the following URL: http://virtualName:8080/bim Appendix E Configuring CONTROL-M/EM clusters 179 . BMC Batch Impact Manager should be installed on the primary node only. create the web application server resource in the CONTROL M/EM resource group. For more information. In a cluster environment.Installing BMC Batch Impact Manager on clusters ■ orbadmin variable modify -scope Sweep -value "iiop://" -ORBListenEndpoints The change is required because the CORBA configuration on the cluster nodes is configured to publish the CONTROL-M/EM virtual network name while the components of these clients run locally. 3 Deploy the BMC Batch Impact Manager web application according to the instructions provided in the CONTROL-M Business Service Management Solutions User Guide. 5 Bring online the BMC Batch impact Manager and the web application server cluster resources. see the CONTROL-M Business Service Management Solutions User Guide. It is intended only for customers who are licensed to use BMC Batch Impact Manager and will install BMC Batch Impact Manager in the cluster environment. 2 Install the web application server on the shared disk where the entire CONTROLM/EM installation was installed. To Configure the BMC Batch Impact Manager web application 1 Install BMC Batch Impact Manager according to the instructions provided in the CONTROL-M Business Service Management Solutions User Guide. Installing BMC Batch Impact Manager on clusters This procedure is optional. see the section on configuring CONTROL-M/EM in a firewall environment in the CONTROL-M Administrator Guide. It is intended only for customers who are licensed to use CONTROL-M/Forecast and will install CONTROL-M/Forecast in the cluster environment. In a cluster environment.Installing CONTROL-M/Forecast on clusters 7 Click Advanced. Replace the default host name with the CONTROL-M/EM virtual host name. For full information on installing CONTROL-M/Forecast. see the CONTROL-M Business Service Management Solutions User Guide. 180 CONTROL-M Installation Guide . To change the cluster resource properties 1 From the cluster administration application. open the BMC-BIM-Server Properties dialog box or the CONTROL-M-EM-Forecast Properties dialog box as required. 9 Click Add Host. CONTROL-M/Forecast should be installed on the primary node only. 2 Select the restart option button. 10 Click Login to log on to BMC Batch Impact Manager. the host name indicates the physical host name of the cluster node. the cluster resource properties must be changed manually from do not restart to restart. Installing CONTROL-M/Forecast on clusters This procedure is optional. 8 Modify the following field values: Field Value Host By default. Updating BMC Batch Impact Manager and CONTROLM/Forecast cluster resources If BMC Batch Impact Manager or CONTROL-M/Forecast were installed on a cluster. Where to go from here Where to go from here You have now completed the installation of CONTROL-M/EM with clusters on Windows using clusters. Appendix E Configuring CONTROL-M/EM clusters 181 . Where to go from here 182 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . change the Local IP Host Interface Name to the virtual host name in ctm_menu. . . . . . . . . The following topics are discussed in this appendix: Setting up the CONTROL-M/Server UNIX cluster environment . . . . . 185 Setting up the CONTROL-M/Server Windows cluster environment for PostgreSQL . . . . . . . 183 Configuring the policy file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Parameter Customization B select option 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Setting up failover nodes . . . . . . . . . . . . . . . . 184 Where to go from here . . . . . . . . . . . 184 Monitoring CONTROL-M/Server processes . . . . . . A from ctm_menu select option 6 . . . . . . . . . . . . . . . . . . . . . 185 Where to go from here . . .Appendix F Configuring CONTROL-M/Server clusters F This appendix contains detailed information on how to configure clusters on CONTROL-M/Server. . . . . .Communication and Operational Parameters Appendix F Configuring CONTROL-M/Server clusters 183 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Setting the virtual host name . . . . . . . . . . . . . . . . . . 186 Setting up the CONTROL-M/Server UNIX cluster environment Setting the virtual host name If CONTROL-M/Server is already installed on the shared disk. . . . . . . . . . . . . . . . . . . . . . dat). SU will shut down CONTROL-M/Server. Therefore.Configuring the policy file These changes will set the OS_PRM_HOSTNAME parameter of the CONTROL-M/Server configuration file (${HOME}/ctm_server/data/config. This change will not take effect until CONTROL-M/Server is restarted. When used in a cluster. enter the following commands. to the virtual host name as the parameter value. 184 CONTROL-M Installation Guide . CTM_ACC=ctm640 CTM_DIR=/export2/ctm640 #Stop CONTROL-M/Server Configuration Agent su . Monitoring CONTROL-M/Server processes CONTROL-M/Server monitors its own processes internally.$CTM_ACC -c $CTM_DIR/ctm_server/scripts/shut_ca #Stop CONTROL-M/Server su . The Supervisor process (SU) performs heartbeat monitoring of all other processes.$CTM_ACC -c $CTM_DIR/ctm_server/scripts/start_ctm To stop the CONTROL-M/Server. If these attempts are unsuccessful. enter the following commands. and monitors CONTROL-M/Server actions. the cluster software starts. SU will try several times to bring up the process. CTM_ACC=ctm640 CTM_DIR=/export2/ctm640 #Start CONTROL-M/Server Configuration Agent su . if the CONTROL-M/Server is defined on CONTROL-M Configuration Manager. If another process fails. Failover of the CONTROL M/Server resource group is not required if only one process fails. the CONTROL-M/Server desired state defined on CONTROL-M Configuration Manager should be set to value ignore. it is sufficient if you only monitor the SU process (/export2/ctm640/ctm_server/exe_Solaris/p_ctmsu).$CTM_ACC -c $CTM_DIR/ctm_server/scripts/start_ca #Start CONTROL-M/Server su . stops. Configuring the policy file To start the CONTROL-M/Server.$CTM_ACC -c $CTM_DIR/ctm_server/scripts/shut_ctm NOTE When CONTROL-M/Server is managed in a cluster. Where to go from here In addition, the CONTROL M/Server Configuration Agent should be monitored as well (/export2/ctm640/ctm_server/exe_Solaris/p_ctmca). To ensure that the SU processes do not become a single point of monitoring, one additional process, such as the RT (p_ctmrt), CO (p_ctmco), NS (p_ctmns), LG (p_ctmlg), or the TR (p_ctmtr) process, can be monitored. Where to go from here You have now completed the installation of CONTROL-M/Server on UNIX. Setting up the CONTROL-M/Server Windows cluster environment for PostgreSQL NOTE This section is relevant only for a PostgreSQL installation. Setting up failover nodes On each failover node, perform the following steps: 1 On the primary node, turn off all resources except the Disk, IP address, and Network Name and move the group to the failover node. 2 Ensure that only the Disk, IP address, and Network Name resources are online on the failover node. 3 Run 3RD\NonPGadmin.bat from the installation CD. NOTE The following step applies only for a PostgreSQL installation. 4 On a PostgreSQL installation, give Log On as a Services privileges to the local NT user that was created for PostgreSQL by performing the following steps: Appendix F Configuring CONTROL-M/Server clusters 185 Where to go from here A From the command line (Start -> Run), run Services.msc B Locate PostgreSQL for Server 640 C Locate .\<name of user> and save this name for later. D Exit Service.msc E From the command line (Start -> Run), run secpol.msc F Select Add User or Group and click Locations. G Select the current node name H In Enter the object name to select, enter a name for the this account service. This name is the <name of user> you saved in step C 5 Restart the computer. 6 Check that the current node of CONTROL-M/Server cluster group is online by performing the following steps: A Issue the Move Group command to move the CONTROL-M/Server cluster group to the current node. B Verify that the disc on which you installed CONTROL-M/Server is accessible from this node. C Issue the Bring Online command to bring the CONTROL-M/Server cluster group on this node online. D Verify that the current node is online in the Windows Cluster Administrator window. Where to go from here You have now completed the installation of CONTROL-M/Server with clusters on UNIX. 186 CONTROL-M Installation Guide Appendix G Configuring CONTROL-M/Agent clusters G This appendix contains detailed information on how to configure clusters on CONTROL-M/Agent. The following topics are discussed in this appendix: Considerations for a Microsoft Windows cluster environment . . . . . . . . . . . . . . . . . 187 Updating CONTROL-M/Agent system path information on cluster installations 188 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Considerations for a Microsoft Windows cluster environment Review the following notes if you will be installing CONTROL-M/Agent in a Microsoft Windows cluster environment: ■ Interactive upgrade installation on a cluster environment is supported from version 6.2.01 only. ■ Multiple Agents can be installed on the same virtual server group or in separate virtual server groups. ■ Select an Agent name that is different from the cluster Network Name or the name of one of its nodes. ■ Do not share the IP and Network Name resources that identify the cluster with an Agent. Appendix G Configuring CONTROL-M/Agent clusters 187 Updating CONTROL-M/Agent system path information on cluster installations ■ Agents that share the same IP and Network name resources must be associated with separate CONTROL-M/Servers. ■ Disk, IP, and Network Name resources must be online in the virtual server group where CONTROL-M/Agent is to be installed. ■ Silent installation and silent upgrade of CONTROL-M/Agent is not supported for Microsoft Windows cluster environments. Updating CONTROL-M/Agent system path information on cluster installations On Windows computers with cluster-enabled CONTROL-M/Agents, you must refresh the path on all failover nodes of the Agent. This allows Agent utilities run from the command line to use the correct path from the specific node. Perform the following steps to update the Windows path environment variables. This ensures that all path specifications for CONTROL-M/Agents are updated in the current Windows environment: 1 Choose Start => Settings => Control Panel => System 2 Click Environment Variables in the Advanced tab. 3 Click OK. Where to go from here You have now completed the installation of CONTROL-M/Agent with clusters. 188 CONTROL-M Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying system parameters . . . . Solaris 10 (for CONTROL-M/Server). . . . . . . . . . . . . . . . . . . . . . . . . . . AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix H Checking and modifying UNIX parameters 190 190 190 191 193 194 195 196 198 189 . . . . . . . . . . . . . . . . . Linux . . . . . . . . . . . . .Appendix H Checking and modifying UNIX parameters H This appendix describes how to check and modify CONTROL-M memory and kernel system parameters. . . . . . . . . . . . . . . . . . 9 (for CONTROL-M/EM and CONTROL-M/Server) . . . . . . . . . . . . . . . Solaris 8. . . . . . . . . . . . . . . . . . . . . . . . . . All platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The following topics are discussed in this appendix: Checking memory . . . . . . . . . . . . . . . . . . . . HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 CONTROL-M Installation Guide . Table 30 Checking available memory UNIX System How to check available RAM AIX Use the following command to determine the amount of available memory in Kilobytes: lsattr -El mem0 Divide the result by 1024 to get the number of MB. HP-UX Log in as the root user and use the following command to check how much RAM is supplied with your computer: # echo phys_mem_pages/D | adb /stand/vmunix /dev/kmem Divide the result by 256 to get the number of MB. the higher values should remain. If higher values for these parameters have already been specified for the database server. All platforms The parameters values shown in Table 31 must be added to the values specified for them in any of the other tables.Checking memory Checking memory The following table lists instructions for checking available memory on various UNIX platforms. Solaris prtconf -v |grep Memory Linux free Modifying system parameters Several UNIX system (kernel) parameters must be altered before installing CONTROL-M. do not change it. If the default value is more than required.4) Ulimit (for Embedded PostgreSQL) ■ ■ fsize: unlimited nofiles: >1024 HP-UX 1 Log in as the root user. Table 33 Kernel parameters for CONTROL-M – HP-UX with Embedded PostgreSQL (Part 1 of 2) Parameter Value semmni 200 semmns 800 Appendix H Checking and modifying UNIX parameters 191 . add 20 + the number of Agents and remote hosts that will be connected to CONTROL-M/Server + the number Agents with configuration definitions that differ from the default. add 100 + 6 times the number agents connected to the server + the number utilities running simultaneously. and navigate to Configurable Parameters. 2 Set the DISPLAY environment variable to <hostName>:0. 4 To change a parameter value: A Navigate to Modify Configurable Parameters in the Action Menu. select Kernel Configuration. 3 Type sam.HP-UX Table 31 Kernel parameters for CONTROL-M/Server – additional values Parameter Additional values semmni Add 20 + the number of Agents and remote hosts that will be connected to CONTROL-M/Server + the number Agents with configuration definitions that differ from the default. Table 32 Kernel parameters for CONTROL-M – values for all platforms Parameter Value semmnu (NPROC . semmnu For Solaris 9 (not Solaris 10). see “Setting environment variables in UNIX” on page 37. B Enter the desired value in the Formula/Value field. semmns For all platforms except Solaris 10.0 For information on setting variables. For more information about CONTROL-M definitions and ViewPoints. maxdsiz 1073741824 maxdsiz_64bit 2147483648 maxssiz 134217728 bytes maxssiz_64bit 1073741824 maxswapchunks 16384 max_thread_proc 512.4) semvmx 32768 CONTROL-M Installation Guide . This value is appropriate for a CONTROL-M installation with up to 50 CONTROL-M definitions. maxuprc ((NPROC*9)/10) msgmap (MSGTQL+2) msgmni NPROC msgseg 32767 msgtql NPROC ncallout (NKTHREAD+16) ncsize ((8*NPROC+2048)+VX_NCSIZE) nfile (15*NPROC+2048) nflocks 4096 ninode (8*NPROC+2048) nkthread (((NPROC*7)/4)+16) nproc 4096 semmap (SEMMNI+2) semmni 4096 semmns (SEMMNI*2) semmnu (NPROC . see the CONTROL-M User Guide. contact BMC Software Customer Support for the correct value of this parameter. Note: If your data center requires a larger configuration. 80 concurrently open ViewPoints.HP-UX Table 33 Parameter Value shmmax 600000000 shmmni 100 shmseg 16 Table 34 192 Kernel parameters for CONTROL-M – HP-UX with Embedded PostgreSQL (Part 2 of 2) Kernel parameters for CONTROL-M – HP-UX with Oracle (Part 1 of 2) Parameter Value ksi_alloc_max (NPROC*8) Eight times the value specified for the NPROC parameter. and 30 concurrent users. and 30 concurrent users. For more information about CONTROL-M definitions and ViewPoints. Note: If your data center requires a larger configuration. Table 36 Kernel parameters for CONTROL-M/Server – HP-UX with Sybase Parameter Value max_thread_proc 1024. see “Checking memory” on page 190. 2 Set the DISPLAY environment variable to <hostName>:0. For information about determining the amount of RAM on your computer. This value is appropriate for a CONTROL-M installation with up to 50 CONTROL-M definitions. 80 concurrently open ViewPoints. Appendix H Checking and modifying UNIX parameters 193 . 3 Enter the following command: smit aio 4 Select the Change/Show Characteristics of Asychronous I/O option.AIX Table 34 Kernel parameters for CONTROL-M – HP-UX with Oracle (Part 2 of 2) Parameter Value shmmax Half the amount of RAM (in bytes) on this computer. AIX Use the following steps to activate the RS/6000 Asynchronous I/O option: 1 Log in as the root user.0 For information on setting variables. see the CONTROL-M User Guide. shmmin 1 shmmni 512 shmseg 32 vps_ceiling 64 Table 35 Kernel parameters for CONTROL-M/EM – HP-UX with Sybase Parameter Value max_thread_proc 512. contact BMC Software Customer Support for the correct value of this parameter. see “Setting environment variables in UNIX” on page 37. 8 Press <F12> to exit from smit. Solaris 10 (for CONTROL-M/Server) Set kernel parameter semmni or project parameter max-sem-ids as described in the Solaris operating system instructions (not supplied by BMC Software). 6 Click Done.Solaris 10 (for CONTROL-M/Server) Enter the parameter values shown in Table 37. the AIX system need not be rebooted at the end of the procedure. the Maximum number of servers setting must be increased by one for every active device after the seventh. 10 Exit the shell prompt. 194 CONTROL-M Installation Guide . NOTE If State to be configured at system start is Available. No other kernel parameters should be set for Solaris 10. Control returns to the main Asynchronous I/O menu. 9 Log out. Table 37 Asynchronous I/O parameters – AIX Parameter Value Minimum number of servers 1 Maximum number of servers 10 Maximum number of requests I/O 4096 Server priority 39 ASYNC I/O state to be configured at system start Available State of fast path Enabled NOTE If your system uses more than seven hard disks for asynchronous I/O. 5 Click OK and wait for the operation to complete. 7 Select the Configure Defined Asynchronous I/O option. 9 (for CONTROL-M/EM and CONTROL-M/Server) Solaris 8. For Solaris 10 platforms. 1 Log in as a root user. Appendix H Checking and modifying UNIX parameters 195 . 3 For each kernel parameter you wish to set. add the following line to the /etc/system file: set shmsys:shminfo_shmseg=36 4 Restart the computer.Solaris 8. 2 Open the operating system configuration file /etc/system. 9 (for CONTROL-M/EM and CONTROL-M/Server) NOTE This procedure has been verified on Solaris 9. Table 38 Kernel parameters – Solaris with Embedded PostgreSQL Parameter Value semmni 200 semmns 800 semmsl 100 shmmax 600000000 shmmni 100 Table 39 Kernel parameters – Solaris with Oracle (Part 1 of 2) Parameter Module name Module abbreviation Minimum value shmmax shmsys shm 4294967295 shmmin shmsys shm 1 shmmni shmsys shm 100 shmseg shmsys shm 10 semmns semsys sem Twice the total number of Oracle processes (minimum: 1024). see Solaris documentation regarding Resource Controls. add a line to the /etc/system file using the following format: set <moduleName>:<moduleAbbreviation>info_<parameterName>=<value> EXAMPLE To set the shmseg parameter to 36. shmmni 100 semmni 200 semmns 800 semmsl 100 Table 42 196 Kernel parameters – Linux with Embedded PostgreSQL Kernel parameters– Linux with Oracle and Sybase (Part 1 of 2) Parameter Value semmsl 250 semmns 32000 semopm 100 semmni 128 CONTROL-M Installation Guide . Instructions on how to display the current parameter values are shown in Table 43.Linux Table 39 Kernel parameters – Solaris with Oracle (Part 2 of 2) Parameter Module name Module abbreviation Minimum value semmni semsys sem 100 semmsl semsys sem 260 semopm semsys sem 100 semvmx semsys sem 32768 Table 40 Kernel parameters – Solaris with Sybase Parameter Module name Module abbreviation Minimum value shmmax shmsys shm amount of available memory on this computer shmseg shmsys shm 10 semvmx semsys sem 32768 Linux 1 Log in as the root user. 2 The kernel parameters shown in Table 42 should be set to values greater than or equal to those displayed in the table.shmall 600000000 kernel.shmmax 600000000 kernel. Table 41 Parameter Value kernel. sem = 250 32000 100 128 fs. semmns. semmni.shmmax = 2147483648 kernel.61000 Table 43 Displaying kernel parameter values – Linux with Oracle and Sybase Parameter Command to display the parameter values semmsl.sem assigns values to four semaphore parameters in the following order: semmsl.conf file take effect after the next reboot. semopm.shmall = 2097152 kernel.Linux Table 42 Kernel parameters– Linux with Oracle and Sybase (Part 2 of 2) Parameter Value semvmx default set by system shmall 2097152 shmmax half the size of physical memory shmmni 4096 file-max 65536 ip_local_port_range 32768 .conf file take effect immediately without rebooting: /sbin/sysctl -p Appendix H Checking and modifying UNIX parameters 197 .ipv4. semopm. you can issue the following command to have the values in the /etc/sysctl.shmmni = 4096 kernel. shmmax.file-max = 65536 net. shmmni /sbin/sysctl -a | grep shm file-max /sbin/sysctl -a | grep file-max ip_local_port_range /sbin/sysctl -a | grep ip_local_port_range Changing kernel parameter values Using a text editor.ip_local_port_range = 32768 61000 NOTE kernel.conf file (you will need to create the file if it does not already exist): kernel. add the following lines to the /etc/sysctl. /sbin/sysctl -a | grep sem semmni shmall. All four values must be specified. The values specified in the /etc/sysctl. Alternatively. semmns. 198 CONTROL-M Installation Guide .Where to go from here Where to go from here Return to“UNIX requirements” on page 35. . . . . . . . . . . . . . Unmounting media devices . . . . . . . . . . . .“Solaris” on page 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The following topics are discussed in this appendix: Mounting media devices. . . . . . . . . . . . . . . . Where to go from here. . /<mediaDir> is the directory name of the mount point. . . . . . . . . . . Solaris. . . . . . . .“HP-UX” on page 200. . . . . . . . . 199 200 200 200 201 201 201 Mounting media devices To mount DVD or CD devices 1 Log in to the computer root account 2 Enter the command mkdir /<mediaDir> to create a mount point for the media. . . . . . . . 4 Verify that the media device was mounted successfully by running the command: mount | grep DVD | wc -l Appendix I Mounting DVDs and CDs on UNIX computers 199 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Apply the specific operating system commands for your specific platform (“AIX” on page 200. . . . . . . . . . . . . . . . .Appendix I Mounting DVDs and CDs on UNIX computers I This appendix describes how to mount DVDs and CDs (referred to in the appendix as media) on UNIX platforms. . . . . . . . . . . . . . . HP-UX . . . . . . . . . . . . . . . . . . . . . . AIX . . . . . . . . . . . . . . . . . . . . . . . Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .or “Linux” on page 201). . . . . . . . look for text similar to "HP DVD-ROM". HP-UX 1 Display the IO devices on your computer by running the command: /usr/sbin/ioscan -fnkC disk 2 In the resulting output. 2 Run ls -la /dev/cd*. identify the path to the media device under the Driver S/W State column (for example. In some circumstances (for example if a USB device is used). 200 CONTROL-M Installation Guide . identify the line that describes the media. /dev/dsk/c0t0d0. 3 Verify that /dev/cd0 exists."TEAC" under the Description column.Unmounting media devices The result should be 1. /dev/dsk/c1t2d0). Unmounting media devices To unmount DVD or CD devices on any platform 1 Issue the following command: umount <dvd_Path or cdPath> <dvdPath or cdPath> is the DVD or CD logical name AIX 1 Ensure that the PATH environment variable is set to /usr/sbin. 4 Run mount -rv cdrfs /dev/cd0 /<mediaDir>. 4 Run the mount command using the value identified in step 3. For example. 3 In the line that contains the media device. you may need to consult your system administrator to identify the media device. 5 Log out of the root account. " under the Description column. For example: mount -F hsfs -o ro /dev/dsk/c0t0d0s2 /<mediaDir>.. and issuing the mount command. /dev/dsk/c0t0d0. Appendix I Mounting DVDs and CDs on UNIX computers 201 . identify the path to the media device (for example. 4 Run the mount command using the value identified in step 3. enter the command: mount -t iso9660 -o ro /dev/cdrom /<mediaDir> Where to go from here Return to the point you were at before jumping to the current appendix. look for text similar to "Vendor: TOSHIBA Product: DVD-ROM SD-C2612. Linux Check if the media device is already mounted by inserting the media. Solaris Check if the media device is already mounted by inserting the media. it will appear on the resulting list.Solaris For example: # mount /dev/dsk/c0t0d0 /<mediaDir>.. If the media device is not mounted. If the media is already mounted. perform the following procedure: 1 Display the IO devices on your computer by running the command: iostat -En 2 In the resulting output. In some circumstances (for example if a USB device is used). identify the line that describes the media. waiting approximately 15 seconds. /dev/dsk/c1t2d0). 3 In the line that contains the media device. If the media is already mounted. For example. If the media device is not mounted. waiting approximately 15 seconds. you may need to consult your system administrator to identify the media device. and issuing the mount command. it will appear on the resulting list. Where to go from here 202 CONTROL-M Installation Guide . . . . . CONTROL-M/Forecast. . . . . . . . . For more information see the CONTROL-M Business Service Management Solutions User Guide. . . . . . . . . . . . . . . . . . . . . . . Uninstalling a CONTROL-M Oracle database server from Windows. . . . . . and BMC Batch Discovery will not function unless they are (re)installed after the reinstalled version of CONTROL-M/EM. . . . . . . .Appendix J Uninstalling CONTROL-M and database servers J The following topics are discussed in this appendix: Uninstalling CONTROL-M/EM from UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and BMC Batch Discovery should also be uninstalled. . . . . . . . . . . . . This especially applies if CONTROL-M/EM is to be uninstalled temporarily and then reinstalled as BMC Batch Impact Manager. . . Appendix J Uninstalling CONTROL-M and database servers 203 . . . . . . . . . CONTROLM/Forecast. . . . . . . . . . . . . Uninstalling CONTROL-M/Agent from Windows . . . . . . . . . . . . . . Uninstalling CONTROL-M/EM from Windows . . . . . . . . . . . . . . 204 205 205 206 206 207 208 208 The following procedures must be observed when uninstalling CONTROL-M/EM and related components from UNIX or Windows: ■ CONTROL-M/EM or CONTROL-M/Server must be uninstalled first before uninstalling the database server. . BMC Batch Impact Manager. . Uninstalling CONTROL-M/Server from Windows . . . . . . . . . . . . . . . . . . . ■ When CONTROL-M/EM is uninstalled. . . . . Uninstalling a CONTROL-M Oracle database server from UNIX . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Server from UNIX . . . . . . . . Uninstalling CONTROL-M/Agent from UNIX . . . . . . . select the Activation Menu. All active processes must be stopped. 204 CONTROL-M Installation Guide . 1 Log on to the CONTROL-M/EM account.sh The uninstall procedure checks if any CONTROL-M/EM processes are active before beginning the uninstallation process. once CONTROL-M/EM is installed. and stop the following processes: ■ ■ ■ CORBA Naming Service CONTROL-M/EM Configuration Agent CONTROL-M Configuration Server 4 Use the following command to run the uninstallation script: $HOME/BMCINSTALL/uninstall/ctmem_uninstall. and then the uninstall command must be run again. 2 Using the CONTROL-M Configuration Manager.Uninstalling CONTROL-M/EM from UNIX NOTE PostgreSQL is uninstalled automatically when CONTROL-M/EM is uninstalled from UNIX or Windows. displays a message if it encounters any active processes. and then stops. stop all occurrences of the following components: ■ ■ ■ ■ GAS GCS GUI Server gateways 3 Run the root_menu script. The reason for this is that the original CONTROL-M/EM database password supplied by BMC Software is changed during the installation of CONTROL-M/EM. it cannot be uninstalled and reinstalled in the same account without first uninstalling the CONTROL-M/EM database. Uninstalling CONTROL-M/EM from UNIX WARNING On Oracle database servers. 2 Stop the following Windows services: ■ TAO NT Naming Service ■ CONTROL-M/EM Configuration Agent ■ CONTROL-M Configuration Server ■ CONTROL-M Web Server 3 Select Start => Settings => Control Panel=> Add/Remove Programs. 2 Log in to the CONTROL-M/Server account. 5 Click Remove or Add/Remove to begin the uninstall procedure. see the CONTROL-M Administrator Guide). The reason for this is that the original CONTROL-M/Server database password supplied by BMC Software is changed during the installation of CONTROL-M/Server. it cannot be uninstalled and reinstalled in the same account without first uninstalling the CONTROL-M/Server database. once CONTROL-M/Server is installed. If multiple instances are installed. Uninstalling CONTROL-M/Server from UNIX WARNING On Oracle database servers. 1 Use the CONTROL-M Configuration Manager to shut down all CONTROLM/EM components. each instance is listed separately in the Add/Remove Programs window. Use the following procedure to completely remove all CONTROL-M/Server components from UNIX: 1 Shut down all CONTROL-M/Agent processes (for specific information. Appendix J Uninstalling CONTROL-M and database servers 205 .Uninstalling CONTROL-M/EM from Windows Uninstalling CONTROL-M/EM from Windows Use the following procedure to completely remove all CONTROL-M/EM components from Windows. 4 Select CONTROL-M/Enterprise Manager from the Currently installed programs list. 5 Click Remove or Add/Remove to begin the uninstall procedure. 4 Select CONTROL-M/Server from the "Currently installed programs" list. 4 After CONTROL-M/Server has been uninstalled. CONTROL-M/Server) before uninstalling. 2 Use the CONTROL-M Configuration Manager to shut down CONTROLM/Server. If multiple instances are installed. Uninstalling CONTROL-M/Server from Windows Use the following procedure to completely remove all CONTROL-M/Server components from Windows: 1 Shut down all CONTROL-M/Agent processes (for more information. 206 CONTROL-M Installation Guide . each instance is listed separately in the Add/Remove Programs window.sh The uninstall procedure checks that no CONTROL-M/Server process is active before beginning the uninstallation process. Uninstalling a CONTROL-M Oracle database server from UNIX WARNING Ensure that the database server is not shared with other CONTROL-M components (for example. see the CONTROL-M Administrator Guide). 3 Select Start => Settings => Control Panel=> Add/Remove Programs. you must delete its definition from the CONTROL-M Configuration Manager.Uninstalling CONTROL-M/Server from Windows 3 Use the following command to run the uninstallation script: $HOME/BMCINSTALL/uninstall/ctms_uninstall. Uninstalling a CONTROL-M Oracle database server from Windows 1 CONTROL-M/EM must be uninstalled first before uninstalling the database server (see “Uninstalling CONTROL-M/EM from UNIX”).sh 4 This program uninstalls all installed Oracle server or Oracle client components in the specified <oracleHome> folder A CONTROL-M/EM database installed on an existing Oracle database server (existing installation) cannot be removed with this script Uninstalling a CONTROL-M Oracle database server from Windows WARNING Ensure that the database server is not shared with other CONTROL-M components (for example. 1 CONTROL-M/EM must be uninstalled first before uninstalling the database server (see “Uninstalling CONTROL-M/EM from Windows”). CONTROL-M/EM) before uninstalling. Removal of the database needs to be done manually. Appendix J Uninstalling CONTROL-M and database servers 207 . 4 A CONTROL-M/EM database installed on an existing Oracle database server (existing installation) is not removed with this program. 2 Log on to the CONTROL-M/EM account 3 Use the following command to run the uninstallation script $HOME/BMCINSTALL/uninstall/uninstall_oracle. 2 Run the following program to uninstall Oracle: Start --> Programs --> Oracle-<oracleHome> --> Uninstall Oracle where <oracleHome> is the folder in which Oracle was installed 3 This program uninstalls all installed Oracle server or Oracle client components in the specified <oracleHome> folder. you are asked to confirm the your intention to uninstall.cpl 3 Select the CONTROL-M/Agent you wish to uninstall and follow the instructions. If not. 208 CONTROL-M Installation Guide . The uninstall procedure performs the following tasks: ■ shuts down and uninstalls CONTROL-M/Agent ■ uninstalls all CONTROL-M Control Modules ■ uninstalls all detected fix packs and patches Uninstalling CONTROL-M/Agent from Windows Use the following procedure to completely remove all CONTROL-M/Agent components from Windows: 1 Select Start => Run 2 Type the command: appwiz. 2 Navigate to the CONTROL-M/Agent home directory.Uninstalling CONTROL-M/Agent from UNIX Uninstalling CONTROL-M/Agent from UNIX Use the following procedure to completely remove all CONTROL-M/Agent components from UNIX: 1 Log in to the CONTROL-M/Agent computer as user root. uninstall is performed immediately. 3 Use the following command to run the uninstallation script: $HOME/BMCINSTALL/uninstall/ctma_uninstall.sh [-silent] If the -silent parameter is used. 29. 28. 187 Index 209 . 200 boot procedure 88 how to check available RAM 190 minimum requirements 36 setting asynchronous I/O 193 architecture of CONTROL-M components 20. 30 Asynchronous I/O AIX parameters 194 authorization CONTROL-M/Server user 81 authorization for installation 40 Authorized CONTROL-M/ Server Hosts CTM/Agent for Windows 97 B batch file 134 batch files 56 BMC Batch Impact Manager 168. 169 installing CONTROL-M/Forecast 170. 183. 84.sh script 38 Chinese language considerations 45 CJK 45 CJK character support 45 cleanup failed Oracle installation on UNIX 126 failed Oracle installation on Windows 139 Oracle on UNIX post-installation 127 client installation 54 Cluster administration mode 159. 27. 157.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Index Numerics 10103_Install_def. 180 Oracle Real Application Cluster (RAC) 153 preparation 147. 93 AIX 193. contacting 2 boot procedure AIX 88 CONTROL-M/Server 87 C character support. 26. 174 administration mode 158 administrator group name for Oracle 39 AG_AGCMN DATA_VAL CTM/Agent for Windows (silent) 99 AG_AGENT_TIMEOUT CTM/Agent for Windows (silent) 99 AG_ATCMN DATA_VAL CTM/Agent for Windows (silent) 99 AG_CTMPERM HOSTS_VAL CTM/Agent for Windows (silent) 99 AG_CTMSHOST _VAL CTM/Agent for Windows (silent) 99 AG_DFTPRT_VAL CTM/Agent for Windows (silent) 99 AG_DOMAIN_VAL CTM/Agent for Windows (silent) 99 AG_GON_AS_ USER_VAL CTM/Agent for Windows (silent) 99 AG_JO_ STATISTICS_ VAL CTM/Agent for Windows (silent) 100 AG_SRV_PASS CTM/Agent for Windows (silent) 100 AG_SRV_USER CTM/Agent for Windows (silent) 100 Agent Name parameter CTM/Agent for Windows 96 Agent-to-Server Port Number CTM/Agent for Windows 97 CTM/Server for Windows 77.PARAMS file 121 57365 TableTitle Table 1 Installation checklist for CONTROLM/EM (continued) 31 A administering server components 159. 179 BMC Batch Impact Manager Server 167 starting and stopping 169 BMC Batch Impact Manager web application 179 BMC Software. 25. CJK 45 check_req. 174 cluster 172 BMC Batch Impact Manager 179 environments 157 Installing BMC Batch Impact Manager 168. 24. 28. 184 CONTROL-M/Forecast 167 installing 170 installing on clusters 180 210 CONTROL-M Installation Guide CONTROL-M/Server boot procedure (UNIX) 87 job editing form 69 CONTROL-M/Server Data tablespace name parameter for Oracle 124 CONTROL-M/Server Database user parameter for Oracle 124 CONTROL-M/Server Host Name in CTM/Agent configuration 92 CONTROL-M/Server Port. online 42 Component communication 68 configuration AIX 194 Configure Defined Asynchronous I/O option 194 configuring database server 33 database servers 33 MSSQL server 34 Oracle 33 Sybase 34 control modules operating system 45 CONTROL-M components 20.Oracle 150 Database post-installation . 24. CTM/Agent parameter 93 conventions. 157. 29. 30 uninstalling Oracle server 206 CONTROL-M database starting and stopping 151 CONTROL-M Option for Oracle with CTM/Agent for UNIX 103 CONTROL-M/Agent Windows parameters 96 CONTROL-M/Desktop job editing form 69 CONTROL-M/EM account on UNIX 39 Administration facility 178 client components 178 multiple instances 64 Reporting facility 178 starting components 69 UNIX requirements 40 CONTROL-M/EM Configuration Agent 165 CONTROL-M/EM GUI Server 167 CONTROL-M/EM or CONTROL-M/Server data file name parameter for Oracle 124 CONTROL-M/EM processes 164. 183.Sybase 150 database preference choices 149 additional 149 database pre-installation 148 Database redo log file size parameter for Oracle 123 Database rollback parameters for Oracle 123 database server installing 114 Database server configuration 33 Database Server Host Name parameter for Oracle 137 Database Server Properties parameter for Oracle 136 database servers 54 Database system tablespace file name parameter for Oracle 124 Database system tablespace size parameter for Oracle 124 Database temporary tablespace file size parameter for Oracle 124 database temporary tablespace parameters for Oracle 124 databases installing Oracle on UNIX 111 installing Oracle on Windows 129 local configuration 154 multiple 65 remote configuration 154 server configurations 33 datasize parameter 40 .A B C D E F G H I J K L M N O P Q R S T U V W X Y Z resources for UNIX 151 Windows installation parameters 155 cluster configuration CTM/Agent for Windows 97 cluster environments setting up CONTROL-M/EM on Windows 172 Cluster Management parameter CTM/Agent for Windows 97 Cluster Management parameter for Windows cluster 155 Cluster preparation 147. 27. 26. 25. documentation 16 CORBA host name 59 CORBA Naming Service 59 coredumpsize parameter 40 ctm_etcservices command 80 customer support 2 D Data File Component parameter for Oracle 136 data tablespace size parameter for Oracle 123 database configurations for UNIX 147 for Windows 152 database instance name parameter for Oracle 125 Database log01 file name parameter for Oracle 123 Database log02 file name parameter for Oracle 123 Database Owner parameter for Oracle 136 Database post-installation . 187 cluster resources for UNIX 151 clustered database configuration 152 Commands 163 commands checking available memory 190 compatibility 40 compatibility information 35 compatibility information. 167 HP-UX 191. CTM/Server for Windows 85 dba administrator group name for Oracle 39 dedicated CONTROL-M database 148 dedicated installation 54 Oracle 112. 179 CONTROL-M/EM client components 63. 200 how to check available RAM 190 minimum requirements 36 I implementing CONTROL-M/EM 178 importing application forms 70 initial program for CONTROL-M/EM account 39 Installation 129 parameters installation checklist 31 client 54 dedicated 54 existing 54 Interactive 50 Interactive on Windows 55 resources required 35 roadmap 23 Silent 51. 178 CONTROL-M/EM on database servers 49 CONTROL-M/EM on other database servers 54 CONTROL-M/EM on UNIX 48 CONTROL-M/EM on Windows 54 CONTROL-M/Forecast 170 CONTROL-M/Forecast on clusters 170. 86 IP address 172 Index 211 . online 15 host names CORBA 59 Oracle parameter 137 Oracle server 125 Sybase 62 HostPort system parameter 165. 86 dump size limit parameter 40 E East Asian language considerations 45 echo command 190 electronic documentation 15 environment variables for UNIX 37 for Windows 42 etc/services file port numbers 80 existing CONTROL-M database 148 existing installation 54 F failover nodes 176 filename data tablespace 124 database system tablespace 124 G Global Alerts Server 167 Global Condition Server 166 Global Condition Server (GCS) 166 H Help. See parameters installation requirements 35 INSTALLDIR parameter CTM/Agent silent installation 99 installing Administrator privileges 40 BMC Batch Impact Manager on clusters 168. 180 CONTROL-M/Server componenets 49 database server 114 Oracle database on UNIX 112. 52 Silent for Oracle on Windows 134 silent on Windows 56 installation log Oracle 126 Installation parameters 144 installation parameters. version required 41 IP dual addresses 79. 86 Dual IP addresses 79. 130 default printer CTM/Agent for Windows (silent) 99 descriptors parameter for UNIX account 40 destination folder CTM/Agent for Windows 97 destination parameter for Oracle 137 DNS 79. 113 Oracle database on Windows 129 Oracle on Windows 129 required resources 35 installing a dedicated database server 114 installing Oracle on Windows 130 instance name Oracle on UNIX 125 Oracle on Windows 137 Interactive installation 50 Internet Explorer.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z DB_SERVER_HOSTNAME parameter. A B C D E F G H I J K L M N O P Q R S T U V W X Y Z J Japanese language considerations 45 Java 68 job editing form CTM/Agent for Windows 69 job output default printer 99 K kernel parameters Solaris 195 Korean language considerations 45 ksi_alloc_max parameter HP-UX with Oracle 192 L language settings CJK character support 45 Windows 42 Linux 196. 184 Monitoring CONTROL-M/EM processes 164 msgmap parameter HP-UX with Oracle 192 msgmni parameter HP-UX with Oracle 192 msgseg parameter HP-UX with Oracle 192 msgtql parameter HP-UX with Oracle 192 MSSQL server configuration 34 multiple databases 65 multiple instances of CONTROL-M/EM 64 N Name tablespace for Oracle data files (Windows) 136 naming multiple instances 64 ncallout parameter HP-UX with Oracle 192 ncsize parameter HP-UX with Oracle 192 Network Name 173 . 86 local database configuration 154 Local IP Host Interface Name CTM/Server for Windows 79. 201 hardware requirement 36 LISTENER port number 125 listener process 164 Load balancing dual IP addresses 79. 86 locale settings 42 location Oracle data file (Windows) 136 Oracle system component (Windows) 138 redo log files (Windows) 138 rollback component (Windows) 138 temporary component (Windows) 139 log files location of Oracle 126 Oracle 114 path for Oracle 123 redo logs for Oracle 123 Silent installation 122 size of redo 123 trace. CTM/Server for Windows 86 lsattr command 190 M max_thread_proc parameter 212 CONTROL-M Installation Guide HP-UX with Oracle 192 HP-UX with Sybase 193 maxdsiz parameter HP-UX with Oracle 192 maxdsiz_64bit parameter HP-UX with Oracle 192 Maximum number of servers AIX parameter 194 maxssiz parameter HP-UX with Oracle 192 maxssiz_64bit parameter HP-UX with Oracle 192 maxswapchunks parameter HP-UX with Oracle 192 maxuprc parameter HP-UX with Oracle 192 Memory 190 memory CONTROL-M/EM account 40 how to check available RAM 190 memoryuse parameter for UNIX 40 messages CTM/Agent for UNIX 92 Microsoft Windows installing Oracle 129 migration 22 mirroring 87 Modify Configurable Parameters option Action menu 191 modifying parameter values 191 monitoring CONTROL-M/EM processes 164.log for Oracle 126 LOG_PHYSICAL_DEVICE_FULLPATH_FILE_NAME parameter. 99 Oracle LISTENER 125 Oracle server TCP/IP 138 recording port usage 80 PostgreSQL 31 post-installation 69 Oracle database 150 Sybase database 150 pre-installation database 148 database for Windows 152 databases 148 Oracle script 113 raw partitions 114 Primary CONTROL-M/ Server Host CTM/Agent for Windows 97 privileges CONTROL-M/Server administrator 81 privileges. 10103_Install_def. for installer 40 product support 2 protocol version.PARAMS 121 parameter values modifying 191 parameters See also individual parameter names CONTROL-M/Agent for Windows 96 CTM/Agent for UNIX 92 CTM/Agent for Windows (silent) 99 for Oracle installation 123 Oracle installation parameters 136 Oracle on UNIX 123–126 Oracle on Windows 136–139 Windows and UNIX 58–62. after agent upgrade 89 prtconf command 190 publications. related 16 R RAC (Real Application Cluster. 154 removing the test data 108 requirements AIX 36 HP-UX 36 installation resources 35 Linux 36 Index 213 . 45 related publications 16 remote database configuration 152. 113 installing on Windows 130 LISTENER port number 125 log files 114 pre-installation script for UNIX 113 server port number for Windows 138 tablespace name check 116 Oracle availability on UNIX 49 Oracle Database Instance Name parameter for UNIX 125 Oracle database processes 164 Oracle Real Application Cluster 153 Oracle Real Application Cluster (RAC) 153 Oracle Server host name parameter for UNIX 125 Oracle SYSTEM password parameter for UNIX 125 Oracle SYSTEM User parameter for UNIX 125 OracleEM920EM6131TNSListener 69 OracleServiceEM613 service 69 OracleUpgradeParams.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z nfile parameter HP-UX with Oracle 192 nflocks parameter HP-UX with Oracle 192 ninode parameter HP-UX with Oracle 192 nkthread parameter HP-UX with Oracle 192 non-English versions of Windows 42 nproc parameter HP-UX with Oracle 192 O online Help 15 operating system requirements 38 operating systems requirements.txt file 139 orapostinst.sh script 127 P Parameter file 51 parameter file. Oracle) 153 raw partitions preparing for installation 114 recording port usage 80 Redo Log files parameter 138 redo log. See requirements Oracle 65 administrator group name 39 configuration 33 installation log file 126 installation parameters for UNIX 123 installation parameters for Windows 136 installation types for Windows 137 installing database on UNIX 112. 144–?? Windows cluster 155 passwords CONTROL-M/EM database owner 60 Oracle server for Windows 136 Oracle SYSTEM account for UNIX 125 Oracle user for UNIX 126 PATH environment variable for Windows 42 planning the CONTROL-M solution 23 policy file 161 port numbers CTM/Agent for Windows 97. file size 123 regional settings 42. sh script 207 uninstalling CONTROL-M Oracle server from UNIX 206 . 201 how to check available RAM 190 kernel parameters 195 minimum requirements 36 stacksize parameter 40 starting CONTROL-M/EM 69 startup options 69 support.log file 126 TRACKER_EVENT_PORT. 192 semmsl parameter Solaris with Oracle 196 semopm parameter Solaris with Oracle 196 semvmx parameter HP-UX with Oracle 192 Solaris with Oracle 196 Solaris with Sybase 196 Server-to-Agent port number CTM/Agent for Windows 97 setup types CTM/Agent for Windows 96 shmmax parameter HP-UX with Oracle 192. 191. 191. 193 Solaris with Oracle 195 Solaris with Sybase 196 Silent installation 51. customer 2 Sybase 65. 192 Solaris with Oracle 196 semmns parameter HP-UX with Oracle 43. 193. 141 configuration 34 syntax statement conventions 17 System account parameter for Oracle 125 System Component parameter for Oracle 138 system requirements.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z UNIX 36 Windows 40 resources required for installation 35 Rollback Component parameter for Oracle 138 rollback segment parameters for Oracle 123 RS/6000 Asynchronous I/O option 193 S security See also passwords installer privileges 40 Select a group parameter CTM/Agent for Windows 97 Select a group parameter for Windows cluster 155 Select the Disk resource parameter CTM/Agent for Windows 97 Select the Disk resource parameter for Windows cluster 155 Select the Network resource parameter CTM/Agent for Windows 97 Select the Network resource parameter for Windows cluster 155 semmap parameter HP-UX with Oracle 192 semmni parameter HP-UX with Oracle 43. CTM/Agent for Windows 100 troubleshooting 165 U uninstall_oracle. See requirements T tablespaces displaying names of 116 file name of temporary 124 rollback segments file name 123 size of temporary 124 size parameter 138 unique name and owner requirement 116 TAO 167 TAO NT Naming Service 69 technical support 2 temporary component parameter for Oracle 139 trace. 52 on Windows 56 Oracle on UNIX 121 Oracle on Windows 134 silent installation UNIX 74 Windows 82 size data tablespace 123 Database system tablespace 124 Oracle data file (Windows) 136 Oracle system component (Windows) 138 redo log files (Windows) 138 rollback component (Windows) 138 temporary component (Windows) 139 Solaris 195. 195 Solaris with Oracle 195 Solaris with Sybase 196 shmmin parameter HP-UX with Oracle 192. 195 Solaris with Oracle 195 shmmni parameter HP-UX with Oracle 193 Solaris with Oracle 195 shmseg parameter 214 CONTROL-M Installation Guide HP-UX with Oracle 192. 192 Solaris with Oracle 195 semmnu parameter HP-UX with Oracle 191. 193. xml file 70 WINNTSystem32 folder. Oracle installation parameter 126 usernames display existing 116 Oracle database on Windows 136 using resource groups 148 V verifying existing Oracle components 115 version agent communication protocol 89 Vista for Windows 63 vps_ceiling parameter HP-UX with Oracle 193 W web application BMC Batch Impact Manager 179 Web Launch 62 Windows compatibility information 40 Windows. PATH environment variable 42 Index 215 . See Microsoft Windows windows.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z CONTROL-M Oracle server from Windows 207 CONTROL-M/EM from UNIX 204 CONTROL-M/EM from Windows 205 CONTROL-M/Server from Windows 206 failed Oracle installation on UNIX 126 failed Oracle installation on Windows 139 Uninstalling Oracle installation 139 Unix Setting limits 39 UNIX installation parameters for Oracle 123 Silent 121 Upgrade Parameter Path parameter for Oracle 139 user password. A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 216 CONTROL-M Installation Guide . this list of conditions and the following disclaimer. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM. EXPRESS OR IMPLIED. FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. WHETHER IN AN ACTION OF CONTRACT. INDIRECT. merge. free of charge. DAMAGES OR OTHER LIABILITY. publish. sublicense. Ben Harris. OR CONSEQUENTIAL DAMAGES (INCLUDING. copy. INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY. LOSS OF USE. and/or sell copies of the Software. Thai Open Source License Copyright (c) 1998. TORT OR OTHERWISE. Justin Bradford. Nicolas Barry. Portions copyright Robert de Bath. Andreas Schultz. EXPRESS OR IMPLIED. Jeroen Massar. STRICT LIABILITY. to deal in the Software without restriction. WHETHER IN CONTRACT. JiBX License Copyright (c) 2003-2005. License Agreement that is applicable to the product. WITHOUT WARRANTY OF ANY KIND. distribute. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. Wez Furlong. are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. Permission is hereby granted. and to permit persons to whom the Software is furnished to do so. OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. EXEMPLARY. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE.Notes Third-Party Product Terms The following terms apply to third-party products that are included with or in a BMC Software product as described in the BMC Software. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. with or without modification. THE SOFTWARE IS PROVIDED "AS IS". this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Joris van Rantwijk. INCLUDING. distribute. SPECIAL. WITHOUT WARRANTY OF ANY KIND. ARISING FROM. OR PROFITS. 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted.. Neither the name of JiBX nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. free of charge. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT.A. to any person obtaining a copy of this software and associated documentation files (the "Software"). Inc. including without limitation the rights to use. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. Dennis M. sublicense. TORT OR OTHERWISE. 1999. BUT NOT LIMITED TO. subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. Delian Delchev. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES. and/or sell copies of the Software. to any person obtaining a copy of this software and associated documentation files (the "Software"). WHETHER IN AN ACTION OF CONTRACT. modify. subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. IN NO EVENT SHALL SIMON TATHAM BE LIABLE FOR ANY CLAIM. merge. copy. INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY. Redistributions in binary form must reproduce the above copyright notice. ARISING FROM. INCIDENTAL. PuTTY License PuTTY is copyright 1997-2005 Simon Tatham. including without limitation the rights to use. and to permit persons to whom the Software is furnished to do so. Notes . Sosnoski All rights reserved. to deal in the Software without restriction. publish. THE SOFTWARE IS PROVIDED "AS IS". Malcolm Smith. modify. DAMAGES OR OTHER LIABILITY. DATA. and CORE SDI S. BUT NOT LIMITED TO. Redistribution and use in source and binary forms. . . *93988* *93988* *93988* *93988* *93988* .