93988

CONTROL-M Installation 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 713 918 8000
Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000
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 customer_support@bmc.com. (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
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 ContractsPasswordAdministration@bmc.com. (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 password@bmc.com. (Asia-Pacific) Contact your BMC sales representative or your local BMC office.
Contents
About this book Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1 Introducing the CONTROL-M solution 15 16 16 17 17 19 19 21 21 21 22 22 23 23 31 32 32 35 35 40 42 43 43 44 45 47 47 48 48 49 49 53 54 55
CONTROL-M architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Agents and remote hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M Control Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Planning the CONTROL-M solution
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Installing CONTROL-M/EM
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ensuring Oracle Availability on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM server components . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM server and client components . . . . . . . . . . . . . . . . .
Contents
Installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Using CONTROL-M/EM Web Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Multiple instances of CONTROL-M/EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Naming multiple instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Installing multiple database clients considerations . . . . . . . . . . . . . . . . . . . . . . . . . 65 Chapter 4 Post installation for CONTROL-M/EM 67
Starting up the CONTROL-M system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Checking Java software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Component communication for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Setting startup options for CONTROL-M/EM services on Windows . . . . . . . . . . . . . 69 Importing WIN panel functionality (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Chapter 5 Installing CONTROL-M/Server 71
Installation database server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Installing CONTROL-M/Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Installing CONTROL-M/Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Chapter 6 Post installation for CONTROL-M/Server 87
Modifying the automatic startup procedure for CONTROL-M/Server (UNIX) . . . . 87 Persistent connection between CONTROL-M/Server and CONTROL-M/Agent. . . 89 Setting the protocol version for the upgraded CONTROL-M/Agent . . . . . . . . . . . . . 89 Using NFS with CONTROL-M/Server (UNIX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows) . . . . . . . . . . . . . . 90 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Chapter 7 Installing CONTROL-M/Agent 91
Installing CONTROL-M/Agent on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Interactive installation or upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Silent installation or upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Installing CONTROL-M/Agent on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Interactive installation or upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Chapter 8
Post installation for CONTROL-M/Agent
101 101 102 102 103 103 103 104 104 105 105 106 107 108 111
Setting CONTROL-M/Agent file permissions for NFS (UNIX) . . . . . . . . . . . . . . . . . Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows) . . . . . . . . . . . . . . . . Modifying the automatic startup procedure for CONTROL-M/Agent . . . . . . . . . . Upgrading from CONTROL-M/Agent version 6.2.0.1 or earlier. . . . . . . . . . . . . . . . Changes to system files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade with CONTROL-M Option for Oracle Applications installed . . . . . . . Upgrade with CONTROL-M Option for PeopleSoft installed . . . . . . . . . . . . . . . Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 9 Running your first job
Testing the new installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating and running a job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the test data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A Installing an Oracle database on UNIX
Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Running the Oracle pre-installation script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Installing a database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Installing a dedicated database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Installing on an existing database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Installing a tablespace using an on-site Oracle client . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Installing an Oracle client (for CONTROL-M/EM only) . . . . . . . . . . . . . . . . . . . . . . . 119 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Performing a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Setting Oracle installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Checking the installation log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Cleaning up a failed Oracle installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Cleaning up after a dedicated installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Cleaning up after an existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Performing post-installation cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Appendix B Installing an Oracle database on Windows 129 130 131 131 131 133 134 135 136
7
Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a CONTROL-M/EM tablespace using an on-site Oracle client . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Oracle installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Cleaning up a failed existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Appendix C Installing a CONTROL-M database with Sybase on UNIX 141
Interactive installation of the CONTROL-M database . . . . . . . . . . . . . . . . . . . . . . . . . 141 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Silent installation of the CONTROL-M database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Appendix D Preparing clusters for database components 147
Preparing the database for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Database pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Database post-installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Creating cluster resources for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Preparing the database for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Database pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Creating cluster resources for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Appendix E Configuring CONTROL-M/EM clusters 157
Setting up the CONTROL-M/EM UNIX cluster environment . . . . . . . . . . . . . . . . . . 157 CONTROL-M Configuration Manager administration mode . . . . . . . . . . . . . . . 158 Cluster administration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Installing the CONTROL-M/EM client components on Windows . . . . . . . . . . . 160 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Setting up the CONTROL-M/EM Windows cluster environment. . . . . . . . . . . . . . . 172 Set up the host and listener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Cluster administration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Create CONTROL-M/EM Gateway cluster resource. . . . . . . . . . . . . . . . . . . . . . . 175 Setting up failover nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Installing CONTROL-M/EM client components . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Installing BMC Batch Impact Manager on clusters. . . . . . . . . . . . . . . . . . . . . . . . . 179 Installing CONTROL-M/Forecast on clusters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Updating BMC Batch Impact Manager and CONTROL-M/Forecast cluster resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Appendix F Configuring CONTROL-M/Server clusters 183
Setting up the CONTROL-M/Server UNIX cluster environment . . . . . . . . . . . . . . . 183 Setting the virtual host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Configuring the policy file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Monitoring CONTROL-M/Server processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Setting up the CONTROL-M/Server Windows cluster environment for PostgreSQL . 185
8 CONTROL-M Installation Guide
Setting up failover nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Appendix G Configuring CONTROL-M/Agent clusters 187
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 Appendix H Checking and modifying UNIX parameters 189 190 190 190 191 193 194 195 196 198 199 199 200 200 200 201 201 201 203 204 205 205 206 206 207 208 208 209
Checking memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solaris 10 (for CONTROL-M/Server). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solaris 8, 9 (for CONTROL-M/EM and CONTROL-M/Server) . . . . . . . . . . . . . Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix I Mounting DVDs and CDs on UNIX computers
Mounting media devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unmounting media devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix J Uninstalling CONTROL-M and database servers
Uninstalling CONTROL-M/EM from UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/EM from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Server from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Server from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling a CONTROL-M Oracle database server from UNIX . . . . . . . . . . . . . . . Uninstalling a CONTROL-M Oracle database server from Windows. . . . . . . . . . . . Uninstalling CONTROL-M/Agent from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Agent from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . Index
Contents
10
Figures
CONTROL-M scheduling solution for distributed systems . . . . . . . . . . . . . . . . . . . . . Full CONTROL-M installation roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/EM installation on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/EM installation on UNIX continued . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/EM installation on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/EM installation on Windows continued . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Server installation on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Server installation on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 24 25 26 27 28 29 30
Figures
11
12
Tables
Installation checklist for CONTROL-M/EM, CONTROL-M/Server, and CONTROLM/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Alternative database servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Database server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Installation resource requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 UNIX requirements for CONTROL-M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Limits for CONTROL-M/EM or CONTROL-M/Server Accounts on UNIX . . . . . . 40 Windows requirements for CONTROL-M/EM and CONTROL-M/Server . . . . . . . 40 Minimum system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Kernel parameter requirement for CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . 43 UNIX and Windows interactive and silent installation parameters . . . . . . . . . . . . . . 58 CONTROL-M/EM services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 CONTROL-M/Server UNIX database and application installation parameters . . 77 CONTROL-M/Server Windows database and application parameters . . . . . . . . . 84 Installation Parameters - CONTROL-M/Agent on UNIX . . . . . . . . . . . . . . . . . . . . . . 92 CONTROL-M/Agent Installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Silent installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Job status colors indicated by the color of a nodes title bar . . . . . . . . . . . . . . . . . . . . 108 Oracle installation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Oracle Database UNIX installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Oracle installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Oracle Database Windows installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . 136 UNIX interactive and silent installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Windows cluster parameters - for interactive installations only . . . . . . . . . . . . . . . . 155 Oracle processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 CONTROL-M/EM processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Defining a cluster resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 CONTROL-M/EM Gateway resource definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Checking available memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Kernel parameters for CONTROL-M/Server additional values . . . . . . . . . . . . . . 191 Kernel parameters for CONTROL-M values for all platforms . . . . . . . . . . . . . . . . 191 Kernel parameters for CONTROL-M HP-UX with Embedded PostgreSQL . . . . 191 Kernel parameters for CONTROL-M HP-UX with Oracle . . . . . . . . . . . . . . . . . . . 192 Kernel parameters for CONTROL-M/EM HP-UX with Sybase . . . . . . . . . . . . . . . 193 Kernel parameters for CONTROL-M/Server HP-UX with Sybase . . . . . . . . . . . . 193 Asynchronous I/O parameters AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Kernel parameters Solaris with Embedded PostgreSQL . . . . . . . . . . . . . . . . . . . . . 195 Kernel parameters Solaris with Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Tables 13
Kernel parameters Solaris with Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Kernel parameters Linux with Embedded PostgreSQL . . . . . . . . . . . . . . . . . . . . . . 196 Kernel parameters Linux with Oracle and Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Displaying kernel parameter values Linux with Oracle and Sybase . . . . . . . . . . . 197
14
About this book

This book describes how to install version 6.4.01 of the CONTROL-M (CONTROLM/EM, CONTROL-M/Server, CONTROL-M/Agent) product. Like most BMC documentation, this book is available in printed and online formats. To request additional printed books or to view online books and notices (such as release notes and technical bulletins), see the Customer Support website at http://www.bmc.com/support_home. Some product shipments also include the online books on a documentation CD.
NOTE
Online books are formatted as PDF or HTML files. To view, print, or copy PDF books, use the free Adobe Reader from Adobe Systems. If your product installation does not install the reader, you can obtain the reader at http://www.adobe.com.
The software also offers online Help. To access Help, press F1 within any product or click the Help button in graphical user interfaces (GUIs).
About this book
15
Related publications
Related publications
The following related publications are related to CONTROL-M:
Category User Guides Document

Description
CONTROL-M User Guide CONTROL-M for z/OS User Guide
CONTROL-M/M concepts, features, facilities, and operating instructions A guide to the CONTROL-M production control system in a mainframe environment. how to define and manage CONTROL-M job processing definitions, monitor services, predict completion schedules, 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
CONTROL-M Business Service Management Solutions User Guide
Reference Guides
CONTROL-M Parameter Guide CONTROL-M Utility Guide
Administrator Guides
CONTROL-M Administrator Guide
defines tasks that the CONTROL-M administrator must perform to define, monitor and maintain the full CONTROL-M environment.
Conventions
This book uses the following special conventions:
All syntax, operating system terms, and literal examples are presented in this typeface. Variable text in path names, system messages, or syntax is displayed in italic text:
testsys/instance/fileName
The symbol => connects items in a menu sequence. For example, Actions => Create Test instructs you to choose the Create Test command from the Actions menu.
16
Syntax statements
Syntax statements
The following example shows a sample syntax statement:
COMMAND KEYWORD1 [KEYWORD2 | KEYWORD3] KEYWORD4={YES | NO} fileName...
The following table explains conventions for syntax statements and provides examples:
Item Items in italic type represent variables that you must replace with a name or value. If a variable is represented by two or more words, initial capitals distinguish the second and subsequent words. Brackets indicate a group of optional items. Do not type the brackets when you enter the option. A comma means that you can choose one or more of the listed options. You must use a comma to separate the options if you choose more than one option. Braces indicate that at least one of the enclosed items is required. Do not type the braces when you enter the item. Example alias databaseDirectory serverHostName [tableName, columnName, field] [-full, -incremental, -level] (UNIX)
{DBDName | tableName} UNLOAD device={disk | tape, fileName | deviceName} {-a | -c} (UNIX)
A vertical bar means that you can choose only one of the listed items. In the example, you would choose either commit or cancel. An ellipsis indicates that you can repeat the previous item or items as many times as necessary.
{commit | cancel} {-commit | -cancel} (UNIX) columnName . . .
Support
In addition to release notes that accompany this product, up-to-date, essential, 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.bmc.com/support_home BMC Software recommends that you access this location before you install this product.
About this book
17
Support
18
Chapter
1
19 21 21 21 22 22
Introducing the CONTROL-M solution

This following topics are discussed in this chapter: CONTROL-M architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Agents and remote hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M Control Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONTROL-M architecture
CONTROL-M is a unified, enterprise-wide, dynamic system that offers a comprehensive solution to production control requirements for batch processing. CONTROL-M executes batch jobs such as scripts or programs, that can be executed either at the operating-system level or under a packaged external application, such as an ABAP program in the SAP application. After you provide CONTROL-M with scheduling and processing instructions for each job, the jobs are able to run. Figure 1 illustrates the CONTROL-M solution and how each component fits into it.
Chapter 1
19
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/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 products 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
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:
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.
22
Chapter
2
23 31 32 32 35 35 40 42 43 43 44 45
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
Figure 2
Full CONTROL-M installation roadmap
page 48
page 53
page 72
page 80
page 91
page 95
24
Figure 3
CONTROL-M/EM installation on UNIX
page 31
page 113
page 113
page 48
page 48
25
Figure 4
CONTROL-M/EM installation on UNIX continued
page 55 page 131
page 55
page 67
page 67
26
Figure 5
CONTROL-M/EM installation on Windows
page 31
page 53
page 55
page 67
27
Figure 6
CONTROL-M/EM installation on Windows continued
page 129
page 131
page 53
page 55
page 131
page 67
28
Figure 7
CONTROL-M/Server installation on UNIX
page 31
page 72
page 113
page 113
page 72
page 87
29
Figure 8
CONTROL-M/Server installation on Windows
page 31
page 80
page 87
30
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. You should review the installation checklists for CONTROL-M/EM, CONTROL-M/Server, and CONTROL-M/Agent for the products you want to install. Table 1 Installation checklist for CONTROL-M/EM, CONTROL-M/Server, and CONTROL-M/Agent (Part 1 of 2)
Where to go 1 Figure 2 If you have not yet done so, identify the CONTROL-M products that will be installed on your system as part of the overall solution for example, CONTROL-M/EM, CONTROL-M/Server, CONTROL-M/Agent Install database components.
Check Step Task
Table 2
BMC Software Embedded PostgreSQL (default) For a non-default installation, install the necessary database components. Table 3 Installation requirements for CONTROL-M/EM and CONTROL-M/Server on page 35 See the release notes For UNIX, see UNIX requirements on page 35
3 4
Select a database server. Ensure that you have all the resources necessary for the installation Identify the installation DVD for the product and platform. Perform pre-installation checks
5 6
Note: A pre-installation check is provided For Windows, see Windows for UNIX installations requirements on page 40 7 (Optional) Review migration and East Asian language considerations
For migration, see Migration considerations on page 22. For Asian language considerations, see East Asian (CJK) language considerations on page 45
Install the product
Chapter 3, Chapter 5, Chapter 7
31
Database installation options
Table 1
Installation checklist for CONTROL-M/EM, CONTROL-M/Server, and CONTROL-M/Agent (continued) (Part 2 of 2)

Where to go Chapter 4, Chapter 6, Chapter 8 see the CONTROL-M /Enterprise Manager Migration Guide and Migration Toolkit. see the CONTROL-M/Server Migration Guide and Migration Toolkit. Download both from BMC Software Customer Support Web site (http://www.bmc.com/support_ home) solution SLN000015053002. 9 10 Perform post-installation procedures Migrate data from previous version (optional)
Check Step Task
Database installation options

The recommended option is CONTROL-M installed on a dedicated Embedded PostgreSQL database server supplied by BMC Software.
Other database options

Depending on the specific database requirements at your site, CONTROL-M can also be installed on the following alternative database servers:
an Oracle database server supplied by BMC Software Oracle, Sybase, 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). An existing installation refers to installation of a database client that connects it to a customer owned, or a BMC supplied, database server already on site.
NOTE
For the PostgreSQL existing installation option, use only an existing installation supplied by BMC Software. The device folder must be empty in order to proceed with the installation.
32
Table 2 provides information about alternative database servers. Table 2 Alternative database servers
UNIX with EM or Server Database Component Supported Supplied Windows with EM Supported Supplied Version 10.2.0.3 Windows with Server Supported Supplied N/A N/A
Oracle server & client Version 10.1.0.x Version 10.2.0.3 Version Version 10.2.0.x 10.1.0.x Version 11.x Version 10.2.0.x Version 11.x Sybase client Version 12.5.x Version 15.x N/A Version 12.5.x Version 15.x
N/A
N/A
N/A
Note: a false database is full alarm can occur in Sybase 12 below version 12.5.4 and in Sybase 15 below version 15.0.1. MSSQL client N/A N/A Version 2005 N/A Version 2005 N/A
Table 3 provides supported configurations for all database servers. Table 3 Database server configuration (Part 1 of 2)
Specifications

Database Type Embedded PostgreSQL (UNIX and Window) Oracle (UNIX and Window)
Dedicated BMC Remote (existing) A BMC-supplied Oracle database server or an existing Oracle full enterprise edition database server must be present. You can not use Oracle Standard edition servers. You must install an Oracle client on each account that hosts a full CONTROL-M/EM or CONTROL-M/Server installation. 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.
33
Table 3
Database server configuration (Part 2 of 2)

Specifications
Database Type Sybase (UNIX and Window)
You must use an existing Sybase database server with 8-KB paging with the following minimum parameter values:

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. Database client version 15.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. The Sybase database server and client is not part of the installation package and must exist at your site before you install CONTROL-M. An MSSQL based installation must always be performed using an existing English language MSSQL database server version 2005. MSSQL is not provided by BMC Software. In addition to the database server, MSSQL clients must be installed on any computer that hosts CONTROL-M/EM or CONTROL-M/Server. If you install CONTROL-M/EM or CONTROL-M/Server on a computer with an existing MSSQL server, you do not need to install the MSSQL Client.
MSSQL (Windows only)
34
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. Table 4
Resource Database administrator CONTROL-M/EM or CONTROL-M/Server database owner System administrator root user privileges
Installation resource requirements

UNIX

Windows
Administrator passwords for existing database servers You are prompted to provide a database owner user name You are prompted to provide a database owner password. Mounting the DVD drive Defining user accounts Modifying system (kernel) parameters Granting authorization to necessary directories Running the check_req.sh script (Oracle only) Running the orapreinst.sh and orapostinst.sh scripts N/A
Administrator privileges 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. Operating system and database compatibility information is listed at: http://www.bmc.com/supportu/PAC_utility/index.cfm. Consult the CONTROL-M Language Customization Guide to adjust locale settings to your UNIX platform. Ensure that operating system levels and patches are up-to-date. See Verifying operating system levels and patches on page 38 Ensure that your hardware, memory, and disk space meet the minimum requirements for CONTROL-M/EM and CONTROL-M/Server as described in Table 5.
Chapter 2 Planning the CONTROL-M solution 35
UNIX requirements
Modify UNIX system parameters as indicated in Modifying system parameters on page 190. If you are installing CONTROL-M/EM or CONTROL-M/Server on a BMC-supplied database server (dedicated Embedded PostgreSQL or dedicated Oracle), 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 for CONTROL-M (Part 1 of 2)
Specification AIX HP-UX Solaris Linux All systems Requirement IBM RISC System/6000 PA (RISC) or IA (Itanium). Sun SPARCstation Intel Pentium 32 bit DVD drive 1 GB
Table 5
Resource Hardware
Memory
CONTROL-M/EM server components or CONTROL-M/Server with Embedded PostgreSQL CONTROL-M/EM server components or CONTROL-M/Server without Embedded PostgreSQL Oracle Server
700 MB
Small: 500 MB Medium: 1GB Large: 1.5 GB
36
UNIX requirements
Table 5
Resource Diskspace
UNIX requirements for CONTROL-M (Part 2 of 2)

Specification Requirement 1 GB for a new installation
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. CONTROL-M/Server without Embedded PostgreSQL Oracle Server (dedicated) Oracle /tmp directory (dedicated) CONTROL-M/EM or CONTROL-M/Server database (tablespace)
300 MB for a new installation
700 MB for a new installation
7 GB 400 MB 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.
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, ksh, 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. <value> is the value assigned to the environment variable.
37
UNIX requirements
Verifying operating system levels and patches

In order to verify that the operating system version, maintenance level (patches), and UNIX kernel parameters are compatible with CONTROL-M requirements, run the check_req.sh file. The check_req.sh file is located in the pre_req directory on the CONTROL-M/EM and CONTROL-M/Server installation DVDs. However, due to changes that are applied to the operating systems, this file may not be up-to-date. BMC recommends that you download the latest version of this file from the following web site: ftp://ftp.bmc.com/pub/control-m/opensystem/PANFT.6.4.01.001 If you downloaded the pre_req.tar.Z file from the web site, follow the instructions in the accompanying readme file. If you are using the check_req.sh file on the installation DVD, continue with this procedure.
To verify operating systems and patches using the check_req.sh file 1 Log in as a root user. 2 Mount the CONTROL-M/EM or CONTROL-M/Server installation DVD.
For details of mount procedures for your UNIX platform, see Appendix I, Mounting DVDs and CDs on UNIX computers.
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
4 Follow the prompts to complete the information as necessary. 5 If the operating system and patches meet CONTROL-M requirements, you are
advised that the product can be installed. Otherwise, a list of missing requirements is displayed.
6 If the script alerts you to a missing patch, 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.
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.
38
UNIX requirements
The CONTROL-M/EM or CONTROL-M/Server account must have an administrator group name. For Oracle, the administrator group name must be dba. For a cluster environment, perform the following:
1 Create two user accounts as shown in the following example, one on each node. 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). 3 Both users home directories should point to the same location on a shared disk.
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. If a process exceeds its limit, the operating system might kill the process without cleanup and without generating diagnostics. To avoid premature termination of running processes, use the limits specified in Table 6. You can use the limit command to check the current limits in your computer. On some operating systems, this command is reserved for "Super Users" only.
39
Windows requirements
Table 6
Parameter datasize
Limits for CONTROL-M/EM or CONTROL-M/Server Accounts on UNIX

Description 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 coredumpsize
maximum size of the stack segment of a process. BMC recommends 400 MB on all UNIX computers. 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.
descriptors
maximum number of descriptors in use by a single process. The recommended value is 4096. Note: Do not set parameter to unlimited.
memoryuse
maximum amount of memory to be used by a single process BMC recommends setting this value to unlimited.
Where to go from here

Continue with Chapter 3, Installing CONTROL-M/EM on UNIX or Chapter 5, Installing CONTROL-M/Server.
Software and database compatibility information is listed at http://www.bmc.com/supportu/PAC_utility/index.cfm. To install CONTROL-M, you must have Administrator privileges. Table 7 describes the Windows requirements for CONTROL-M/EM and CONTROL-M/Server. Table 7
Resource Hardware
Windows requirements for CONTROL-M/EM and CONTROL-M/Server (Part 1 of 3)

Specification

Requirement
Computer: Pentium IV 1 GHz or higher Display: 16-bit (65536) colors or higher Storage Media: DVD drive
40
Table 7
Resource Memory

Specification CONTROL-M/EM server components with Embedded PostgreSQL CONTROL-M/EM server components without Embedded PostgreSQL CONTROL-M/EM client components with Embedded PostgreSQL CONTROL-M/EM client components without Embedded PostgreSQL CONTROL-M/Server with Embedded PostgreSQL CONTROL-M/Server without Embedded PostgreSQL Oracle Server Requirement 2 GB
1.7 GB
2 GB for Vista 1 GB for XP 1.7 GB for Vista 700 MB for XP 1 GB 700 MB
Small: 500 MB Medium: 1GB Large: 1.5 GB Full CONTROL-M/EM installation: 850 MB Client installation (including the Reporting Facility): 200 MB
Diskspace
CONTROL-M/EM with Embedded PostgreSQL
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. CONTROL-M/Server with 400 MB Embedded PostgreSQL CONTROL-M/Server without Embedded PostgreSQL Oracle Server (dedicated) Oracle /tmp directory (dedicated) CONTROL-M/EM and CONTROL-M/Server database (tablespace) 300 MB
7 GB 400 MB
All database servers Sybase database except Sybase: server:

Related Software
Internet Explorer version 6.0 or later
41
Installation requirements for CONTROL-M/Agent
Table 7
Resource

Specification Requirement A reference to the WINNT\System32 folder must be in the PATH environment variable. For Windows 2003 this folder is: WINDOWS\System32. The TEMP environment variable must indicate a path that exists on your computer.
Environment Variables
Language Settings When working with non-English versions of Windows, set the system locale and language settings to English before installing CONTROL-M: 1. Select Western Europe and United States in Control Panel => Regional and Language Options for the system to receive all messages in English. 2. Select English (US) in Control Panel => Regional and Language Options to set the locale to English. After installation you can reconfigure your computer for work with a non-English language. For more information, see the CONTROL-M Language Customization Guide.

Continue with Chapter 3, Installing CONTROL-M/EM on UNIX or Chapter 5, Installing CONTROL-M/Server.
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. If you use this feature, you may decide not to install separate CONTROL-M/Agents.

For details about this feature and when to use it, see the CONTROL-M Concepts Guide. For information about configuring remote hosts, see the CONTROL-M Administrator Guide.
For the most current operating system compatibility information for this version, see http://www.bmc.com/supportu/PAC_utility/index.cfm.
42
System requirements
System requirements
Ensure that your computer meets the following requirements: Table 8
Memory Disk Space
Minimum system requirements

Value 128 MB 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. Version 1.5 or later. This requirement is necessary only for running Agent utilities. It is not required to run Agent jobs.
Requirement
Java Runtime Environment
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.
2 Kernel parameter values must be modified as specified in Table 9.

Table 9
Parameter
Kernel parameter requirement for CONTROL-M/Agent

Additional values Increase the current parameter value by 1 for each Agent to be installed on the computer.
semmni semmns
3 Define a CONTROL-M/Agent user account. NOTE

If more than one CONTROL-M/Agent is required on the same computer, each one must be installed in a separate account.
43
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. The user can be a local user or an NIS user, but the account home directory must be located on a local disc and not on NFS. 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). The initial program for the user must be defined as either csh, tcsh, sh, ksh, or bash.
NOTE
The proclog and sysout directories can be placed on NFS as part of the post installation process. For more information see Setting CONTROL-M/Agent file permissions for NFS (UNIX) on page 101.
4 Ensure that the IPC subsystem is enabled. You can check its status by issuing the
ipcs -a command.
5 Verify that your locale is set to English before beginning the installation. (You can
check this using the locale command.) You can change this setting after the installation process is complete.
NOTE

All computers in the CONTROL-M environment must be set to the same locale. If you are upgrading from an earlier version of CONTROL-M/Agent for UNIX, 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.
A non-interactive (silent) installation and upgrade procedure is also available for CONTROL-M/Agent. For more information, see Installing CONTROL-M/Agent on UNIX.

Continue with Chapter 7, Installing CONTROL-M/Agent.
Preparing for CONTROL-M/Agent installation on Windows

CONTROL-M/Agent can be installed and upgraded interactively or silently. For more information, see Installing CONTROL-M/Agent on Windows. You can also install more than one CONTROL-M/Agent on the same computer. For more information on installing multiple agents, see the CONTROL-M Administrator Guide.
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, SAP). When CONTROL-M/Agent is installed, the control module for the operating system (OS) is installed together with the Agent. Additional CONTROL-M Control Modules (for example, SAP, AFT, or Oracle Applications), can be installed afterwards. No changes are required for CONTROL-M Control Modules or CONTROL-M Options that existed before an upgrade.

Continue with Chapter 7, Installing CONTROL-M/Agent.

Support for East Asian languages (Simplified Chinese, Traditional Chinese, Japanese, and Korean) is provided for all installations at the database level. When installing a dedicated (BMC-supplied) Oracle database server, you must choose the custom option. During custom installation, you are explicitly asked if CJK character support is required. When you create a CONTROL-M database on an existing PostgreSQL database server, CJK settings are not inherited automatically from the database server. They must be defined during the installation. When you create a CONTROL-M database on an existing Oracle, or Sybase database server, CJK settings are inherited automatically from the database server. When creating a CONTROL-M database on an existing MSSQL database server with CJK support already present, you are explicitly asked if CJK character support is required for the new CONTROL-M database. For more information regarding CJK support, see the CONTROL-M Language Customization Guide.
45
46
Chapter
3
47 48 48 49 49 53 54 55 58 62 64 64 65
Installing CONTROL-M/EM
This following topics are discussed in this chapter: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ensuring Oracle Availability on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM server components . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM server and client components . . . . . . . . . . . . . . . . . Installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using CONTROL-M/EM Web Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple instances of CONTROL-M/EM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming multiple instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing multiple database clients considerations . . . . . . . . . . . . . . . . . . . . . . . . .
Overview
Interactive and silent installation procedures are available to install CONTROL-M/EM on UNIX and on Windows. 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. This is especially useful when the product needs to be installed on several computers using the same configuration. The installation program offers you the following options:
Choice of database server: Embedded PostgreSQL (default), MSSQL, Oracle, or Sybase
Chapter 3
47
Installing CONTROL-M/EM on UNIX
Database server configuration: Default or Custom CONTROL-M/EM: Full - includes server components, client components, and the Reporting Facility Client - 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, you must install a database server. For more information, see Other database options on page 32.
To install on UNIX, see Installing CONTROL-M/EM on UNIX on page 48. To install on Windows, 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.bmc.com/signon/content/logon.jsp You can burn the ISO file onto a CD/DVD and mount the media. The installation can be performed from the CD/DVD as outlined in this section.
A UNIX installation installs the CONTROL-M/EM server components. All client components reside in a Windows environment. For more information, see Installing CONTROL-M/EM on Windows on page 53.
Database server options

If you choose the default installation, a dedicated Embedded PostgreSQL database server is automatically installed in the background as part of the CONTROL-M/EM installation no interaction is required.
48
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). Install a CONTROL-M/EM tablespace on an existing Oracle database server (see Appendix A). Install a CONTROL-M/EM database on an existing Sybase database server by running <dvdPath>/Sybase/setup.sh from the installation DVD (see Appendix C).

If Oracle is down, you must log in to the Oracle database server account and perform the following commands:

source .oraenv.csh sqlplus "/as sysdba" startup exit
If the Oracle Listener is down, 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 - runs the installation from an installation script Silent - 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 Interactive installation on page 50. For information on silent installations, see Silent installation on page 51.
Chapter 3 Installing CONTROL-M/EM 49
NOTE
When you install the product on an existing PostgreSQL database that resides on Windows, the following message is displayed. database <database> was created in the default location and not in the specified location <location> You can safely ignore this message.
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. For information about mounting a DVD, see Appendix I, Mounting DVDs and CDs on UNIX computers.
2 Log on to the CONTROL-M/EM account. 3 If you are installing on Oracle, ensure that the database server is up and running
(see Ensuring Oracle Availability on UNIX on page 49).
4 If this is a cluster installation, prepare the installation by first implementing the

criteria discussed under Creating cluster resources for UNIX on page 151.
5 Use the following command to run the installation script.

<dvdPath>/setup.sh
WARNING
If the security settings at your site do not allow the ping command to be used, set the BMC_SKIP_PING environment variable to Y before running setup.sh. For information on setting variables, see Setting environment variables in UNIX on page 37.
6 Follow the instructions on the screen, filling in parameter values as necessary (see
Table 10 on page 58). The installation log can be found in the home directory of the CONTROL-M/EM account, for example: <emHome>/BMCINSTALL/log/<version>_trace.log
Where to go from here 1 Install the latest fix pack to apply the most recent software updates. 2 Install CONTROL-M/EM clients on Windows computers as necessary (see
Installing CONTROL-M/EM on Windows on page 53).
3 Perform the post-installation configuration tasks specified in Chapter 4, Post

installation for CONTROL-M/EM.
4 If this is a cluster installation, you must also complete the procedures listed under
Setting up the CONTROL-M/EM UNIX cluster environment on page 157.
Silent installation
WARNING
CONTROL-M/EM can be installed silently only if the database component was also installed silently.
Silent installation is used to install CONTROL-M/EM server 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. 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 parameters file.
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. You can reuse this parameters file to silently install CONTROL-M/EM server components on other computers.
To prepare the silent installation parameters file 1 Prepare the parameter information you will need for the installation.
Explanations are provided in Table 10 on page 58.
2 On an existing database server, ensure that a CONTROL-M/EM database has been

installed. If you select PostgreSQL, this installation installs the database server automatically. If you installed a BMC Software dedicated Oracle database server, the CONTROL-M/EM database was prepared automatically.
Chapter 3
51
3 If you are installing on Oracle, ensure that the database server is up and running
4 Mount the CONTROL-M/EM installation DVD from the root user and log off the
root user before continuing with the installation. For information about mounting a DVD, see Appendix I, Mounting DVDs and CDs on UNIX computers.
5 Log on to the CONTROL-M/EM account. 6 Set the environment variable BMC_SILENT_INSTALL to value Y. See Setting
environment variables in UNIX on page 37 for your UNIX environment.
7 Issue the following command to activate the silent installation script:

<dvdPath>/setup.sh
WARNING
8 Follow the interactive menu instructions specifying parameter values as requested.

The installation parameters saved to ${HOME}/BMCINSTALL/PRODUCTS.CTL. If you want to change parameter values, modify them in the parameters file manually.
To install silently 1 Log on to the CONTROL-M/EM account. 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. <newDboPassword> is the dbo password that will be set.
52
Installing CONTROL-M/EM on Windows
<sysAdminPassword> is the system administrator password (required for a PostgreSQL installation).
3 Issue the following command:

<dvdPath>/setup.sh -r <parameterPath> <dvdPath> is the path of the mounted DVD. <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.
4 Restart CONTROL-M/EM. Where to go from here 1 Install the latest fix pack to apply the most recent software updates. 2 Install CONTROL-M/EM clients on Windows computers as necessary (see
Installing CONTROL-M/EM on Windows on page 53).
3 Perform the post-installation configuration tasks specified in Chapter 4, Post

installation for CONTROL-M/EM.
Setting up the CONTROL-M/EM UNIX cluster environment on page 157.
NOTE
To work with CONTROL-M/Enterprise Manager, close the current session and open a new one. Opening a new session activates the latest configuration settings.
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.bmc.com/signon/content/logon.jsp You can burn the ISO file onto a CD/DVD and mount the media. The installation can be performed from the CD/DVD as outlined in this section.
Chapter 3
53
The full CONTROL-M/EM product (both server and client components) can be installed on Windows (this is usually performed on one computer only). Clients can also be installed on other Windows computers to enable access to CONTROL-M/EM from several locations. Each CONTROL-M/EM client installation can optionally include an instance of the Reporting Facility. If you intend to install more than one CONTROL-M/EM client on the same computer, refer to Multiple instances of CONTROL-M/EM on page 64.

If you choose the default installation, a dedicated Embedded PostgreSQL database server is installed automatically in the background as part of the CONTROL-M/EM installation. The full installation and the client installation will install the necessary database server and client components no interaction is required.
NOTE
When installing CONTROL-M/EM using an existing PosgreSQL database server on UNIX, 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. The data location directory must be empty.
For an Oracle, MSSQL, or Sybase installation, you must first ensure that database server and client software is installed by choosing one of the following options:
Perform an Oracle dedicated installation (see Appendix B). Perform an Oracle existing installation (see Appendix B). Perform an Oracle client installation (see Appendix B). Install an MSSQL client on the CONTROL-M/EM target computer to communicate with an existing MSSQL database server (see your system administrator). Install a Sybase client on the CONTROL-M/EM target computer to communicate with an existing Sybase database server (see your system administrator).
54
Installing CONTROL-M/EM server and client components

There are two types of installations
Interactive - runs the installation from an installation script Silent - runs the installation from a batch file
For more information on the interactive installation, see Interactive installation on page 55. For more information on the silent installation, see Silent installation on page 56.
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. For more information see Using CONTROL-M/EM Web Launch.
1 If your database server is Oracle, MSSQL, or Sybase, make sure that you follow the
instructions under Installing CONTROL-M/EM on Windows on page 53.
NOTE
If you are installing CONTROL-M/EM on an Embedded PostgreSQL database server, the installation program installs the necessary database clients.
2 Log on using an ID with Administrator privileges on the current computer. 3 If this is a cluster installation, prepare the installation by first implementing the
criteria discussed under Creating cluster resources for Windows on page 154.
4 Insert the installation DVD and run <dvdPath>\setup.bat. WARNING

If the security settings at your site do not allow the ping command to be used, the setup.exe command must be issued from the command line as follows: setup.exe /vBMC_SKIP_PING=Y
Chapter 3
55
Table 10 on page 58). After the installation is complete, check the information in the %TEMP%\ctmem640_user_log.txt file to ensure that the installation ended successfully.

If you selected the full installation option, complete the tasks specified for Windows in Chapter 4, Post installation for CONTROL-M/EM.
Silent installation
WARNING
On Oracle and Sybase, CONTROL-M/EM can be installed silently only if the database component was also installed silently.
Silent installation is used to install CONTROL-M/EM from a batch file. This option is not supported for Windows cluster environments. Two stages are involved: 1. Preparing the batch 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 batch file. 2. Running the prepared batch file When the prepared batch file runs, CONTROL-M/EM is installed using the parameters you specified in the previous step. You can reuse this batch file to silently install CONTROL-M/EM on other computers.
To prepare the silent installation batch file 1 If your database server is Oracle, MSSQL, or Sybase, ensure that you follow the
instructions under Installing CONTROL-M/EM on Windows on page 53.
NOTE
If you are installing CONTROL-M/EM on an Embedded PostgreSQL database server, the installation program installs the necessary database clients.
56
2 If the installation DVD will be accessed through a network, you must first map the
DVD drive and assign a drive letter.
3 Insert the installation DVD into the mapped drive, navigate to the installation
folder, and run the following command: <dvdPath>\prep_silent.bat
WARNING
If the security settings at your site do not allow the ping command to be used, the %Source_dir%setup.exe... line in the prep_silent.bat file must be modified as follows: %Source_dir%setup.exe/s /vBMC_SILENT_INSTALL=\Y\ BMC_SKIP_PING= \Y/l*v\%InstallLogFile%\ It is necessary to copy the prep_silent.bat file to a local drive to facilitate this change. After making the change, run the modified prep_silent.bat file from the local drive.
4 After selecting the type of installation required and entering the necessary
parameters values at the prompts, select Save & Exit to save the parameters. The parameters are saved to: %TEMP%\BMC_EM_silent.bat.
To install silently 1 Log on to the target computer using an ID with Administrator privileges. 2 Run the following command from the installation DVD to install .Net Framework
2.0.
dotnetfx.exe /q:a /c:"install /l /q
3 If the BMC_EM_silent.bat file will be accessed through a network, you must first
map the DVD drive and assign a drive letter.
4 Open a command prompt window, navigate to the path where the

BMC_EM_silent.bat file now resides, and run the silent installation by issuing the following command: <path>\BMC_EM_silent.bat
5 After the installation is complete, check the information in the

%TEMP%\ctmem640_trace_log.txt file to ensure that the installation ended successfully.
Chapter 3
57
Installation parameters
NOTE
When you install the product on an existing PostgreSQL database on Windows, the following message is displayed. database <database> was created in the default location and not in the specified location <location> You can safely ignore this message.

If you selected the full installation option, complete the tasks specified for Windows in Chapter 4, Post installation for CONTROL-M/EM.
Table 10 provides a description of UNIX and Windows prompt or interactive and silent installation parameters. Table 10 UNIX and Windows interactive and silent installation parameters (Part 1 of 5)
UNIX silent installation parameter name Windows silent installation parameter name
Interactive parameter or prompt
Description Sets language mode to either standard (for PostgreSQL: Latin1; for other databases: [empty string]) or western languages (for PostgreSQL: UTF8; for other databases:1) mode. Default (for PostgreSQL): LATIN1
CJK
[SETP]/BMC/PO PostgreSQL: STGRES/UTF_M ODE_STR EM_PG_SRV_CJK_ CHK Other databases: EM_MSSQL_SRV_ CJK_CHK
Default (for other databases): 1
CONTROL-M/Enterprise Manager Database Name
N/A
PROP_EM_SYB_MS When creating a new database SQL_DATABASE_ NAME Name for the CONTROL-M/EM database. The name must begin with a letter (A-Z, a-z) followed by up to 29 alpha-numeric characters (includes underscores). When communicating with an existing database: Name of the existing database schema to which to connect.
58
Table 10
UNIX and Windows interactive and silent installation parameters (Part 2 of 5)

UNIX silent installation parameter name Windows silent installation parameter name
Interactive parameter or prompt CORBA Naming Service Host Name CORBA Naming Service Port Number
Description Host name of the machine running the remote CORBA server to which you want to connect. When creating a new database: Specify the port number for communication with the local CORBA server. The value must be in the range 1025-65535. When communicating with an existing database Enter the existing port number for communication with the remote CORBA server.
[SETP]/BMC/EM PROP_EM_CORBA /CORBA_HOST _HOST _NAME [SETP]/BMC/EM PROP_EM_CORBA /CORBA_PORT_ _PORT NUMBER
Data Device Physical Full Path File Name
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. 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. You must take into consideration the number of jobs in the Active Jobs file.
Data Device Size
N/A
Chapter 3
59
Table 10

UNIX silent installation parameter name N/A Windows silent installation parameter name
Interactive parameter or prompt Data Location
Description
PG_DATA_LOCATI Path to the POSTGRESQL ON CONTROL-M/EM tablespace location. For Windows, this parameter is informational only and cannot be changed during installation. PROP_EM_DBA_US Name of the database administrator. ER PROP_EM_DBA_PA Password of the database SSWORD administrator. PROP_EM_DBUSE R_NAME Full installation with creation of a new database: Name for the CONTROL-M/EM database schema owner. The name must begin with a letter (A-Z, a-z) followed by up to 7 alpha-numeric characters (includes underscores). Full installation without creation of a new database: Name of an existing
Database Administrator Login Database Administrator Password Database Owner Login
N/A N/A N/A
CONTROL-M/EM database
schema owner to which to connect. Database Owner Password N/A PROP_EM_DBUSE R_PASSWORD When creating a new database: Password for the CONTROL-M/EM database owner. The password must begin with a letter (A-Z, a-z) followed by 5 to 29 alpha-numeric characters (includes underscores). When communicating with an existing database: Current password for the CONTROL-M/EM database owner. Database Server Name N/A 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 installation will fail if this restriction is violated.
60
Table 10

UNIX silent installation parameter name N/A Windows silent installation parameter name PROP_DBSRV_DA TABASE_TYPE
Interactive parameter or prompt Database Server Type
Description The database server brand name: Embedded POSTGRESQL, ORACLE, SYBASE, or MSSQL Default: POSTGRESQL
Data Tablespace Size
N/A
PROP_EM_SYB_SQ Size of CONTROL-M/EM database L_DBSIZE (small, medium, large). Default: medium. PROP_INSTALLDI R The directory you specify in this window becomes the home folder for CONTROL-M/EM. All selected components are installed in subdirectories under this directory. Default: <drive>:\Program Files\BMC Software\CONTROL-M EM <version>
Destination Folder
N/A
Host Name Interface Name (Installation DVD) Instance Name Log Device Physical Full Path File Name
N/A
PG_INTERFACE_N Host name of the computer on which AME the POSTGRESQL database server is installed PROP_DVD_LOCA Location of installation DVD TION PROP_CTMEM_IN STANCE_NAME CONTROL-M/EM instance 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. PROP_EM_SYB_SQ Amount of space (in MB) to allocate L_LOG_SIZE_ for the transaction log. The recommended amount is 1/3 of the data device size. PG_PORT_NUM The TCP/IP port that the POSTGRESQL database server listens to for communication from CONTROL-M/EM Set a user name for the Windows Service. The name can contain up to 20 alphanumeric characters (A-Z, a-z, 0-9, hyphens, and underscores). Set a password for the PostgreSQL Windows service according to the operating system security policy.
Log Device Size
N/A
Port Number
N/A
PostgreSQL Service user name
N/A
EM_NON_ADM_U SER
PostgreSQL Service password
N/A
EM_NON_ADM_U SER_PASSWORD
Chapter 3
61
Using CONTROL-M/EM Web Launch
Table 10

UNIX silent installation parameter name N/A Windows silent installation parameter name PROP_TASK_SELE CTION
Interactive parameter or prompt Setup Type
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 PROP_DB_SYBASE The TCP/IP port that the Sybase _DBSERVER_PORT database server listens to for communication from CONTROL-M/EM
Sybase Server Query Port Number
N/A

If your site runs CONTROL-M/EM client components on several desktops, each user can install the CONTROL-M/EM client components from the web using CONTROL-M/EM Web Launch. 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. Using CONTROL-M/EM Web Launch, the CONTROL-M/EM client components, CONTROL-M/Desktop, the CONTROL-M/EM GUI, and CONTROL-M Configuration Manager are packaged on the web server. For more information on CONTROL-M/EM Web Launch and how to package client components, see the CONTROL-M Administrator Guide.
62
The system administrator supplies CONTROL-M/EM users with the URL for the packaged CONTROL-M/EM client applications. Users initiate the client installation through the URL. After the installation completes, the user can run CONTROL-M/EM from the Windows start menu. During installation, the URL is embedded in the start command of each client component. Anytime a client component is started, the web site is checked for updates. When updates are available, the user is prompted to install them. Web Launch packages do not overwrite existing user data when they are deployed
NOTE
CONTROL-M/EM Web Launch is not cluster-aware. If you want to implement CONTROL-M/EM Web Launch on a cluster computer, consult your system administrator.
To enable the installation of CONTROL-M/EM client components 1 With Windows Vista, you must disable the User Account Control (UAC) before
running Web Launch.
WARNING
Disabling the UAC affects the privileges of all applications running under Windows Vista.
2 Ensure that Microsoft .Net Framework runtime versions 1.1 and 2.0 are installed
on your computer.
3 Obtain the CONTROL-M/EM client URL from your system administrator. 4 Activate the installation from the URL. 5 Using the Registry editor, set the DisableMSI parameter in the registry. A Navigate to the
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer registry key. If the Installer directory does not exist under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows, create it.
B Ensure that the data type of the DisableMSI parameter is REG_DWORD and its
value is 0.
C Save and exit the registry.
Chapter 3
63
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.
Multiple instances of CONTROL-M/EM

Multiple instances of CONTROL-M/EM can be installed on a single Windows computer (supported versions include 6.4.01, 6.3.01, 6.2.01, and 6.1.03). The following rules apply:
Only one full installation instance of a supported version can be installed on a single computer. Components (full installation or client) of previous versions must be installed before any 6.4.01 component. Unlimited instances of 6.4.01 clients (including clients with the Reporting Facility) can be installed. A full installation of version 6.4.01 cannot be installed with any 6.1.03 components. Database clients from different vendors (for example, Sybase, Oracle, MSSQL) can be installed as necessary on the same computer. Cluster support is available only for the full installation. Web Launch packages from CONTROL-M/EM versions 6.3.01 and 6.4.01 cannot be installed on the same client computer when both packages are downloaded from the same URL (same host computer, instance name, and port number).
Naming multiple instances
The first instance is named Default. For subsequent instance installations, an instance name consisting of <hostName>_<instanceNumber> is suggested by the installation program, for example, CTMEM_1, CTMEM_2. The suggested name can be changed by the user. Note that instance names must not contain any of the following characters: / \ : * ? "<>|
64
Installing multiple database clients considerations
If you uninstall the default instance, the next instance to be installed is named Default. You are not given the option of changing the name.

Sybase
If multiple Sybase clients are used, they must all be of the same version.
Oracle
If a CONTROL-M/EM version 6.4.01 with an Oracle 10.2 Client (with Reporting Facility) is installed on a computer that has CONTROL-M/EM versions 6.3.01, 6.2.01 or 6.1.03 with an Oracle 9.i client (with Reporting Facility and CONTROL-M Configuration Manager) already installed, users will lose the ability to log in to the CONTROL-M/EM 6.3.01, 6.2.01 or 6.1.03 environment.
To enable logging in to all installed environments 1 Download file OracleSelector.zip from the following site:
ftp://ftp.bmc.com/pub/Database_Patches/Oracle
2 Open OracleSelector.zip and extract file setup.exe. 3 Run setup.exe to select the Oracle environment (Oracle home) you currently
require. You can run setup.exe again any time you wish to switch between Oracle environments. Note that only one Oracle environment can be accessed at any one time.
Chapter 3
65
66
Chapter
4
67 68 68 69 69 70
Post installation for CONTROL-M/EM

The following topics are discussed in this chapter: Starting up the CONTROL-M system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Java software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component communication for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting startup options for CONTROL-M/EM services on Windows. . . . . . . . . . . . . Importing WIN panel functionality (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting up the CONTROL-M system

After installing both CONTROL-M/EM and CONTROL-M/Server, 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). 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
67
Checking Java software
3 Select Discover and click OK 4 In the Specifying CONTROL-M/Server parameters window, 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).
6 If CONTROL-M/EM and CONTROL-M/Server were installed with the suggested

default parameters, you can accept the suggested defaults for CONTROL-M ID and Configuration Agent Port. Otherwise, see your system administrator.
7 Click Next as required. The Discover process detects and defines the new
CONTROL-M/Server and its gateway in the Configuration Manager.
Checking Java software

Java software is required on both UNIX and Windows platforms. It is also used to configure CORBA. Ensure you have JRE version 1.5 or higher installed on your computer. For more information on configuring CORBA, see the CONTROL-M Administrator Guide.
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. 2 After completing a CONTROL-M/EM client installation, you should use one of the
following commands to verify that the database server is active:
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>
68
Setting startup options for CONTROL-M/EM services on Windows
<emDBO> is the database owner name under which CONTROL-M/EM was installed, and <password> is the database owner password.
Type quit to exit the database server.
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, choose the Activation Menu option, and choose the Start
All option to activate all CONTROL-M/EM components.
5 Log in to one or more CONTROL-M/Server computers. Start CONTROLM/Server on each computer as necessary and check that communication with CONTROL-M/EM can be established (for example, using the ping command). For more information, see the CONTROL-M Administrator Guide.
Setting startup options for CONTROL-M/EM services on Windows

Depending on which components were installed, all or some of the Windows services listed in Table 11 will start automatically when the system is booted. If they do not start, CONTROL-M/EM will not function correctly. Table 11
Service OracleEM1010EM6401TNSListener OracleServiceEM640 TAO NT Naming Service
CONTROL-M/EM services
Installation type Oracle database server - Oracle installations only. These services are added to the computer during Oracle database installation. Full installation
To start using CONTROL-M/EM, you must first set up the CONTROL-M working environment. For more information, see the CONTROL-M Administrator Guide.
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. For full functionality, the procedure should be performed on every computer that has CONTROL-M/EM client component(s) installed.
Chapter 4
69
1 Ensure that the CONTROL-M/Agent application CD is on a mapped drive. 2 In CONTROL-M/Desktop, choose Tools => Import Applications Forms. 3 A browse window is displayed. Navigate to the Windows\Forms folder on the
application CD.
4 Select the windows.xml file and click Import. 5 Shut down and restart CONTROL-M/EM.

You have now completed the installation of CONTROL-M/EM.
70
Chapter
Installing CONTROL-M/Server
NOTE
BMC Software recommends that you verify that you have installed or upgraded to CONTROL-M/EM version 6.4.01 before installing this version of CONTROL-M/Server.
The following topics are discussed in this chapter: Installation database server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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), MSSQL, Oracle, 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.
TIP
You can get up and running quickly by choosing the default installation with Embedded PostgreSQL.
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. 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. Before installing CONTROL-M/Server with PostgreSQL in existing mode, ensure that you know the PostgreSQL port and host. 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, 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/Server tablespace (see Appendix A). Install a CONTROL-M/Server tablespace on an existing Oracle database server (see Appendix A). Install a CONTROL-M/Server database on an existing Sybase database server by running <dvdPath>/Sybase/setup.sh from the installation DVD (see Appendix C).
72

If Oracle is down, you must log in to the Oracle database server account and perform the following commands:

source .oraenv.csh sqlplus "/as sysdba" startup exit
If the Oracle Listener is down, perform the following additional command:
lsnrctl start <listenerName>
For Oracle databases supplied by BMC Software, <listenerName> is LSTNR_<instanceName>
1 Prepare all the information you need for the installation. Explanations about
parameters are provided in Table 12 on page 77.
2 Mount the CONTROL-M/Server installation DVD from the root user and log off
the root user before continuing with the installation. For information about mounting a DVD, see Appendix I, Mounting DVDs and CDs on UNIX computers on page 199.
3 Log in to the CONTROL-M/Server account. 4 If you are installing on Oracle, ensure that the database server is up and running
5 If this is a cluster installation, prepare the installation by first implementing the

criteria discussed under Creating cluster resources for UNIX on page 151.

<dvdPath>/setup.sh
73
WARNING
7 Follow the instructions on the screen responding to the prompts as necessary.

The installation log can be found in the home directory of the CONTROL-M/Server account, for example: <ctmHome>/BMCINSTALL/log/<version>_trace.log

1 Install the latest fix pack to apply the most recent software updates. 2 Perform the post-installation configuration tasks specified in Chapter 6, Post
installation for CONTROL-M/Server.
Setting up the CONTROL-M/Server UNIX cluster environment on page 183.
NOTE
To work with CONTROL-M/Server, close the current session and open a new one. Opening a new session activates the latest configuration settings.
Silent installation
Silent installation is used to install CONTROL-M/Server from a parameters file. The following stages are involved:
Running the installation using the prepared parameters file
74
Silent installation
When the installation is run using the prepared parameters file, CONTROL-M/Server is installed using the parameters you specified in the previous step. You can reuse this parameters file to silently install CONTROL-M/Server on other computers.
2 On an existing database server, ensure that a CONTROL-M/Server database has

been installed. An embedded PostgreSQL database server is automatically installed with the default CONTROL-M/Server installation if no other database server is present. If you installed a BMC Software dedicated Oracle database server, the CONTROL-M/Server database was prepared automatically.
3 If you are installing on Oracle, ensure that the database server is up and running
4 Mount the CONTROL-M/Server installation DVD from the root user and log off
the root user before continuing with the installation. For information about mounting a DVD, see Appendix I, Mounting DVDs and CDs on UNIX computers on page 199.
5 Log in to the CONTROL-M/Server account. 6 Set the environment variable BMC_SILENT_INSTALL to value Y. See Verifying
operating system levels and patches on page 38 for your UNIX environment.

<dvdPath>/setup.sh
WARNING

The installation parameters are saved to ${HOME}/BMCINSTALL/PRODUCTS.CTL.
75
If you want to change parameter values, manually modify them in the parameters file.
To install silently 1 Log in to the CONTROL-M/Server account. 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. <newDboPassword> is the dbo password that will be set. <sysAdminPassword> system administrator password (required for a PostgreSQL installation).

<dvdPath>/setup.sh -r <parameterPath> <dvdPath> is the path of the mounted DVD. <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.

Setting up the CONTROL-M/Server UNIX cluster environment on page 183.
76
NOTE
After completing the installation, you must close the current session and open a new one before working with CONTROL-M/Server.
Table 12
CONTROL-M/Server UNIX database and application installation parameters (Part 1 of 4)

Silent installation parameter name
Active installation parameter name

Agent-to-Server Port Number
Description
[SETP]/BMC/SERVER/AGENT_TO Listening port in the Server computer that _SERVER_PORT receives data from all Agent computers. The value specified must match the value assigned to the Agent-to-Server Port Number parameter on all Agent computers. Verify that this port number is not used for any other purpose in this Server computer. Specify a numeric value between 1024 and 65535. Default: 7005
CJK
[SETP]/BMC/POSTGRES/UTF_MO Sets language mode to either standard (Latin1) DE_STR or western languages (UTF8) mode. Default: LATIN1
CONTROL-M/Server Configuration Agent Configuration [SETP]/BMC/SERVER Agent Port Number /CTM_CONFIG_AGENT_PORT_N port number. UMBER Default: 2369 CONTROL-M/EM TCP/IP Port Number [SETP]/BMC/SERVER/OUTPUT_S PN CONTROL-M/EM TCP/IP port number.
CONTROL-M communicates with [SETP]/BMC/SERVER/INPUT_SPN CONTROL-M/EM using a pair of consecutive TCP/IP ports (for example, 2370 and 2371). The lower port passes data from CONTROL-M to CONTROL-M/EM. The higher port passes data in the reverse direction. 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 the two port numbers are not used for any other purpose on the Server platform. The value for this parameter must be a number from 1024 through 65533. 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.
77
Table 12

Silent installation parameter name

Data Directory Full Path Database Administrator Password Database Name Database Owner Login
Description
[SETP]/BMC/POSTGRES/DATABA Full path to data directory (In the case of an SE_DATA_PATH existing installation, the directory must exist and be empty.) N/A Password of the database administrator.
[SETP]/BMC/POSTGRES/DATABA Database name to be created. SE_NAME [SETP]/BMC/POSTGRES/DATABA Full installation with creation of a new SE_OWNER_NAME database: Name for the CONTROL-M/Server database schema owner. The name must begin with a letter (A-Z, a-z) followed by up to 17 alpha-numeric characters (includes underscores). Default: ctmuser
Database Owner Password
N/A
Set a password for the CONTROL-M/Server database owner. The password must begin with a letter (A-Z, a-z) followed by 5 to 29 alphanumeric characters (includes underscores).
Database scalability [SETP]/BMC/POSTGRES/DATABA Size of the CONTROL-M database (Small, SE_SERVER_MEMORY_MODEL Medium, Large). Default: Medium Host Name Interface Name Inter Process Communication Port Number N/A [SETP]/BMC/SERVER /IPC_PORT Host name of the computer on which the PostgreSQL database server is installed Port number used for communication between CONTROL-M processes. This parameter replaces the Input Mailbox Key and Output Mailbox Key parameters in earlier versions of CONTROL-M/Server. Range: 1025-32767 Default: 6005
78
Table 12

Silent installation parameter name [SETP]/BMC/SERVER/LOCAL_IP_ HOST

Local IP Host Interface Name
Description
Host interface name of the TCP/IP network interface card on the CONTROL-M/Server platform. This name is used for communication with CONTROL-M/Server and is typically the host name of the CONTROL-M/Server computer. The default value for this parameter is the default host interface name defined in the CONTROL-M/Server computer operating environment. This parameter can also be specified by its IP address (for example, 192.123.186.20). It should be modified only if the CONTROL-M/Server platform contains more than one network interface card (for example, Ethernet and Token-Ring). Note: CONTROL-M does not support dual IP addresses for single computers in the DNS (Domain Naming System). If your operating system supports dual IP addresses, run the nslookup utility and verify that the domain name resolves to one IP address. (Dual IP addresses are often specified for load balancing purposes). Note: When installing on a computer that supports clustering, specify the Virtual Server Name.
N/A N/A PostgreSQL Server Host Name PostgreSQL Server Port Number
[SETP]/BMC/END_USER_LOG_FIL Progress log file E [SETP]/BMC/DEV_USER_LOG_FIL Trace log file E [SETP]/BMC/POSTGRES/DATABA Host name of the computer on which the SE_SERVER_HOST PostgreSQL database server is installed [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. Default: 5432
79
Installing CONTROL-M/Server on Windows
Table 12

Silent installation parameter name [SETP]/BMC/SERVER/SERVER_T O_AGENT_PORT

Server-to-Agent Port Number
Description
Listening port in the Agent computer that receives data from this Server computer. The value specified must match the value assigned to the Server-to-Agent Port Number parameter (for this Agent) on the Agent computer. Verify that this port number is not used in the Agent for any other purpose. Specify a numeric value between 1024 and 65535. 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. Ports reserved for CONTROL-M/Server use should be recorded here. Proper maintenance of this file helps prevent conflicting usage of ports by various applications.
1 To save all operations and communications parameters in the file etc/services, run
the following command under a root user: <ctm_Home >/ctm_server/scripts/ctm_etcservices
2 At the message prompt, type y to update the /etc/services file.
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. Before installing CONTROL-M/Server with PostgreSQL in existing mode, ensure that you know the PostgreSQL port and host. Information on the PostgreSQL existing installation is in the following file:
<CONTROL-M/Server with PostgreSQL Server folder>\pgsql\etc\pg_service.conf
CONTROL-M/Server can also be installed on an MSSQL database. In this case, you must ensure that an MSSQL database server and necessary client software are installed before installing CONTROL-M/Server.
NOTE
When installing CONTROL-M/Server using an existing PosgreSQL database server on UNIX, 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. The data location directory must be empty.
1 Log in as a user that has administrator privileges on the current computer. 2 If this is a cluster installation, prepare the installation by first implementing the
criteria discussed under Creating cluster resources for Windows on page 154.
3 Insert the installation DVD and run setup.bat. WARNING

If the security settings at your site do not allow the ping command to be used, the setup.bat command must be issued from the command line as follows: setup.bat /vBMC_SKIP_PING=Y
Table 13 on page 84). After the installation is complete, check the information in the %TEMP%\ctm640_user_log.txt file to ensure that the installation ended successfully.
NOTE
81

Setting up the CONTROL-M/Server Windows cluster environment for PostgreSQL on page 185.
Silent installation
NOTE
Silent installation of CONTROL-M/Server is not supported for Microsoft Windows cluster environments.
Silent installation is used to install CONTROL-M/Server from a batch file. The following stages are involved:
Preparing the batch 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 batch file.
Running the prepared batch file When the prepared batch file is run, CONTROL-M/Server is installed using the parameters you specified in the previous step. You can reuse this batch file to silently install CONTROL-M/Server on other computers.
To prepare the silent installation batch file 1 If the installation DVD will be accessed through a network, you must first map the
DVD drive and assign a drive letter.
2 Insert the installation DVD into the mapped drive, navigate to the installation
folder, and run the following command: <drive>\prep_silent.bat
82
Silent installation
WARNING
If the security settings at your site do not allow the ping command to be used, the %Source_dir%setup.bat... line in the prep_silent.bat file must be modified as follows: %Source_dir%setup.bat /s /vBMC_SILENT_INSTALL=\Y\ BMC_SKIP_PING= \Y /l*v \%InstallLogFile%\ It is necessary to copy the prep_silent.bat file to a local drive to facilitate this change. After making the change, run the modified prep_silent.bat file from the local drive.
3 After selecting the type of installation required and entering the necessary
parameters values at the prompts, select Save & Exit to save the parameters. The parameters are saved to: %TEMP%\BMC_CTMSRV_silent.bat.
To install silently 1 Log in to the target computer using an ID with administrator privileges. 2 If the BMC_CTMSRV_silent.bat file will be accessed through a network, you
must first map the DVD drive and assign a drive letter.
3 Open a command prompt window, navigate to the path where the

BMC_CTMSRV_silent.bat file now resides, and run the silent installation by issuing the following command: <path>\BMC_CTMSRV_silent.bat
4 After the installation is complete, check the information in the

%TEMP%\ctmsrv640_silent_log.txt file to ensure that the installation ended successfully.
NOTE
83

Setting up the CONTROL-M/Server Windows cluster environment for PostgreSQL on page 185. Table 13 CONTROL-M/Server Windows database and application parameters (Part 1 of 3) Silent installation parameter name Description

Agent-to-Server Port Number
CTMSRV_AGENT_TO_ Listening port in the Server computer that receives data SERVER_PORT_NUM from all Agent computers. The value specified must match the value assigned to the Agent-to-Server Port Number parameter on all Agent computers. Verify that this port number is not used for any other purpose in this Server computer. Specify a numeric value between 1024 and 65535. Default: 7005 CTMSRV_CTMEM_PO CONTROL-M/EM TCP/IP Port Number. RT_NUM CONTROL-M communicates with CONTROL-M/EM using a pair of consecutive TCP/IP ports (for example, 2370 and 2371). The lower port passes data from CONTROL-M to CONTROL-M/EM. The higher port passes data in the reverse direction. 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 the two port numbers are not used for any other purpose on the Server platform. Range: 1024-32767 Default: 2370.
CONTROL-M/EM TCP/IP Port Number
CONTROL-M/Server CTMSRV_DATABASE_ Name for the CONTROL-M/Server database. The name Database Name NAME must begin with a letter (A-Z, a-z) followed by up to 29 alphanumeric characters (includes underscores). Data Device Physical Full Path File Name Data Device Size 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. CTMSRV_DATA_SIZE Amount of space (in MB) to allocate for the data portion of the database. You must take into consideration the number of jobs in the Active Jobs file.
Database Administrator Login
CTMSRV_DBA_USER_ Name of the database administrator. NAME
84
Table 13
CONTROL-M/Server Windows database and application parameters (Part 2 of 3) Silent installation parameter name
CTMSRV_DBA_PASS WORD

Database Administrator Password Database Owner Login
Description
Password of the database administrator.
CTMSRV_DBO_USER_ Set a name for the CONTROL-M/Server database NAME schema owner. The name must begin with a letter (A-Z, a-z) followed by up to 29 alphanumeric characters (includes underscores). CTMSRV_DBO_PASS WORD Set a password for the CONTROL-M/Server database owner. The password must begin with a letter (A-Z, a-z) followed by 5 to 29 alphanumeric characters (includes underscores).
Database Owner Password
Database Server Name Data tablespace size Destination Folder
CTMSRV_DATABASE_ Name of the MSSQL database server. SERVER_NAME CTMSRV_COMBO_DB Size of CONTROL-M/Server database (small, medium, SIZE large). Default: medium. INSTALLDIR The folder you specify in this window becomes the home folder for CONTROL-M/Server. All selected components are installed in subdirectories under this folder. 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. This parameter replaces the Input Mailbox Key and Output Mailbox Key parameters in earlier versions of CONTROL-M/Server. Range: 1025-32767 Default: 6005
85
Table 13
CONTROL-M/Server Windows database and application parameters (Part 3 of 3) Silent installation parameter name
CTMSRV_LOCAL_IP_ HOST_INTERFACE_N AME

Local IP Host Interface Name
Description
Host interface name of the TCP/IP network interface card on the CONTROL-M/Server platform. This name is used for communication with CONTROL-M/Server and is typically the host name of the CONTROL-M/Server computer. The default value for this parameter is the default host interface name defined in the CONTROL-M/Server computer operating environment. This parameter can also be specified by its IP address (for example, 192.123.186.20). It should be modified only if the CONTROL-M/Server platform contains more than one network interface card (for example, Ethernet and Token-Ring). Note: CONTROL-M does not support dual IP addresses for single computers in the DNS (Domain Naming System). If your operating system supports dual IP addresses, run the nslookup utility and verify that the domain name resolves to one IP address. (Dual IP addresses are often specified for load balancing purposes). Note: When installing on a computer that supports clustering, specify the Virtual Server Name.
Log Device Physical Full Path File Name Log Device Size
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. CTMSRV_LOG_SIZE Amount of space (in MB) to allocate for the transaction log. The recommended amount is 1/3 of the data device size. Set a user name for the PostgreSQL Windows Service. The name can contain up to 20 alphanumeric characters (A-Z, a-z, 0-9, hyphens, and underscores). Set a password for the PostgreSQL Windows service according to the operating system security policy.
PostgreSQL Service user name PostgreSQL Service password Server-to-Agent Port Number
SRV_NON_ADM_USE R SRV_NON_ADM_USE R_PASSWORD
CTMSRV_SERVER_TO Listening port in the Agent computer that receives data _AGENT_PORT_NUM from this Server computer. The value specified must match the value assigned to the Server-to-Agent Port Number parameter (for this Agent) on the Agent computer. Verify that this port number is not used in the Agent for any other purpose. Specify a numeric value between 1024 and 65535. Default: 7006
86
Chapter
6
87 89 89 89 90 90
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) . . . . Persistent connection between CONTROL-M/Server and CONTROL-M/Agent . . Setting the protocol version for the upgraded CONTROL-M/Agent . . . . . . . . . . . . . Using NFS with CONTROL-M/Server (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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. BMC Software recommends that they be started at system startup time. You can modify the startup procedure to ensure that the database server, CONTROL-M/Server, and the CONTROL-M/Server Configuration Agent are started during system startup. The command to copy the necessary startup instructions to your system startup directory is listed below.
NOTE
Do not perform this procedure when installing CONTROL-M/Server on a mirror (backup) environment.
Chapter 6
Post installation for CONTROL-M/Server
87
Modifying the automatic startup procedure for CONTROL-M/Server (UNIX)
For AIX
cp <ctmHome>/ctm_server/data/rc.<controlmUser> /etc/ Open the /etc/inittab file in an editor, and append the following line at the end of the file. <controlmUser>:2:respawn:/etc/rc.<controlmUser>
EXAMPLE
For a user called controlm, specify the following command:
cp /home/controlm/ctm_server/data/rc.ctm640 /etc
and in file /etc/inittab add:

controlm:2:respawn:/etc/rc.ctm640
For HP-UX
cp <ctmHome>/ctm_server/data/rc.<controlmUser> /sbin/init.d/<controlmUser> ln -s /sbin/init.d/<controlmUser>/sbin/rc2.d/S98<controlmUser>
EXAMPLE
cp /home/controlm/ctm_server/data/rc.ctm640 /sbin/init.d/ctm640
ln -s /sbin/init.d/ctm640 /sbin/rc2.d/S98ctm640
For Solaris
cp <ctmHome>/ctm_server/data/rc.<controlmUser> /etc/rc2.d/S98<controlmUser>
EXAMPLE
cp /home/controlm/ctm_server/data/rc.ctm640 /etc/rc2.d/S98ctm640
For Linux
cp <ctmHome>/ctm_server/data/rc.<controlmUser> /etc/rc.d/rc2.d/S98<controlmUser>
EXAMPLE
cp /home/controlm/ctm_server/data/rc.ctm640 /etc/rc.d/rc2.d/S98ctm640
For SuSE, run the following command after coping the file:
>SuSEconfig
88
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. For more details about how and when a persistent connection should be used, see the CONTROL-M Administrator Guide.
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. From the
menu, select Parameter Customization => Parameters for Communicating with Specific Agent Platforms. The following prompt is displayed: To view/modify communication parameters, enter node ID of Agent Platform:
2 Enter the node ID of a CONTROL-M/Agent, for example, diana. The

Communicating with Specific Agent Platform (diana) menu is displayed.
3 For older versions of CONTROL-M/Agent, set the Communication Protocol

Version to:
A 06 for version 6.2.01. B 07 for version 6.3.01.
Using NFS with CONTROL-M/Server (UNIX)

1 Verify that CONTROL-M/Server is shut down. 2 Copy the ctm_server/proclog, ctm_server/proclog.save, ctm_server/status, and
ctm_server/temp directories to NFS.
3 Delete the copied directories from the local disk.

Chapter 6 Post installation for CONTROL-M/Server 89
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.
5 Start CONTROL-M/Server.

If after installation, CONTROL-M utilities are not recognized in command prompt mode, 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, click OK.

You have now completed the installation of CONTROL-M/Server.
90
Chapter
Installing CONTROL-M/Agent
This chapter describes how to install and upgrade CONTROL-M/Agent on UNIX and Windows. The following topics are discussed in this chapter: Installing CONTROL-M/Agent on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Interactive installation or upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Silent installation or upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Installing CONTROL-M/Agent on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Interactive installation or upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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. 2 Log in as the root user. 3 Navigate to the target installation directory. 4 If this is an upgrade installation, ensure that CONTROL-M/Agent is not running
Chapter 7
91
5 Use the following command to run the installation script:

<cdPath>/Unix/setup.sh <cdPath> is the path of the mounted CD. Follow the instructions on the screen, filling in parameter values and fields as necessary. The parameters and fields for this installation are described in Table 14. If a previous version of CONTROL-M/Agent is detected, an upgrade is performed. In this case, the parameters values from the previous version are used.
NOTE
The installation log can be found in the home directory of the CONTROL-M/Agent account, for example: <agentHome>/BMCINSTALL/log/DRKAI.6.4.01_user.log <agentHome> is the path of the CONTROL-M/Agent home directory.
Table 14
Installation Parameters - CONTROL-M/Agent on UNIX (Part 1 of 2)

Silent installation parameter name SRV_2_AGT_PORT Description Listening port in the Agent computer that receives data from this Server computer. 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. Verify that this port number is not used in the Agent for any other purpose. Specify a numeric value between 1024 and 65535. Default: 7006 The host name of the computer on which CONTROL-M/Server is installed. If the CONTROL-M/Server is in a cluster, the CONTROL-M/Server Network Name is required.
Active installation parameter name Server to Agent Port number
Primary CONTROL-M/Server Host
CTRLM_HOST
Authorized CONTROL-M/Server Host
AUTHORIZED_CTRLM Specifies one or more CONTROL-M/Servers that will _HOSTS be authorized to submit jobs to this agent. Use '|' to separate between host names.
92
Silent installation or upgrade
Table 14
Installation Parameters - CONTROL-M/Agent on UNIX (Part 2 of 2)

Silent installation parameter name AGT_2_SRV_PORT Description Listening port in the Server computer that receives data from all Agent computers. The value specified must match the value assigned to the Agent-to-Server Port Number in the CONTROL-M/Server configuration. Verify that this port number is not used for any other purpose in this Server computer. Specify a numeric value between 1024 and 65535. Default: 7005. Set the locale to the local language. The locale must be already defined on the system. This parameter is used only with latin1 characters sets.
Active installation parameter name Agent-to-Server Port Number
Locale
AGT_LOCALE

installation for CONTROL-M/Agent.

Silent installation is used to install or upgrade CONTROL-M/Agent 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 CD. 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 parameters file.
Running the installation using the prepared parameters file When running the installation using the prepared parameters file, CONTROL-M/Agent is installed using the parameters you specified in the previous step.
Chapter 7
93
TIP
You can reuse the parameters file to silently install CONTROL-M/Agent on other computers.
To prepare the silent installation or upgrade parameters file 1 Prepare all the information you will need for the installation.
Parameter explanations are provided in Table 14 on page 92.
2 Log in as the root user. 3 Navigate to the CONTROL-M/Agent target directory. 4 If this is an upgrade installation, ensure that CONTROL-M/Agent is not running 5 Set the environment variable named BMC_SILENT_INSTALL to Y as follows:
For sh, ksh, 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

If a previous CONTROL-M/Agent installation is detected, the current parameters and their values are displayed. The installation parameters are saved to ${HOME}/BMCINSTALL/PRODUCTS.CTL A copy of the parameters file is saved to ${HOME}/BMCINSTALL/installed/agent on each Agent installed.
94
NOTE
In a new installation you can modify parameter values by editing the parameter file using a text editor. To change existing parameter values during an upgrade installation, you must add each parameter and its new value to the parameters file.
To install silently 1 Log in as the root user. 2 Navigate to the CONTROL-M/Agent home directory. 3 Use the following command to run the parameters file:
<cdPath>/Unix/setup.sh -respond <parameterPath> <cdPath>is the path of the mounted CD. <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

1 Log in to a user account belonging to the local Administrators group. 2 If CONTROL-M/Agent is monitored by an application (for example, BMC
Software Patrol Agent) that ensures it remains running, you must shut down the monitoring application before beginning an upgrade installation.
Chapter 7
95
3 Insert the installation CD in the CD-ROM drive.

If the Autorun option is enabled, installation starts automatically and the opening screen is displayed. If the Autorun option is not enabled, browse to the Windows folder on the CD-ROM drive, and double-click Setup.bat.
NOTE
Depending on your Windows security settings, you may receive a Microsoft warning about running the BMC Software installation file. You can safely ignore this message.
4 Follow the prompts to complete the installation.

Updating CONTROL-M/Agent system path information on cluster installations on page 188. The parameters and fields for this installation are described in Table 15.
NOTE
The installation log is located in the following folders: For 32 Bit: %TEMP%\DRNDN.6.4.01_trace_log_win32.txt For Itanium 64 Bit: %TEMP%\DRNDN.6.4.01_trace_log_win64.txt ForAMD 64 Bit: %TEMP%\DRNDN.6.4.01_trace_log_win64AMD.txt
Table 15
Parameter
CONTROL-M/Agent Installation parameters (Part 1 of 2)

Description CONTROL-M/Agent is identified by a logical name. This name is used in the command line for CONTROL-M/Agent utilities to indicate which agent should handle the command. Type of Agent installation on a cluster enabled environment: Cluster: Installs an Agent in a cluster enabled environment. Local: Installs an Agent locally without joining it to the existing cluster environment.
Agent Name
Setup Type
96
Table 15
Parameter
CONTROL-M/Agent Installation parameters (Part 2 of 2)

Description Indicates the location in which the Agent will be installed. To change the installation folder, click Change and Browse to the desired location.
Destination Folder Primary CONTROL-M/ Server Host
Indicates the host name of the computer where CONTROL-M/Server is installed. Name of the computer hosting the CONTROL-M/Server that submits requests to this Agent. If the CONTROL-M/Server is in a cluster, the CONTROL-M/Server Network Name is required. Note: Specify a name, not an IP address. Default: Computer on which the installation was made.
Authorized CONTROL-M/ Server Hosts
Names of all CONTROL-M/Server hosts authorized to send requests to this Agent, including backup hosts. The primary CONTROL-M/Server host must be included if it will send requests to this Agent. Use the | symbol to separate host names. Do not include spaces between host names. Note: Specify names, not IP addresses. Default: Name of the primary CONTROL-M/Server host.
Agent-toServer Port Number Server-toAgent Port Number Clustering Parameters
Listening port in the Server computer that receives data this Agent. The value specified must match the value assigned to the Agent-to-Server Port Number parameter on CONTROL-M/Server. Verify that this port number is not used in the Server for any other purpose. Specify a numeric value between 1024 and 65535. Default: 7005 Listening port of this Agent that receives data from the Server. 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. Specify a numeric value between 1024 and 65535. Default: 7006 Select a group Select the Disk resource Select the Network resource Cluster Management Highlight the virtual server group for which this Agents IP address and the Network Name were created. Select the Disk resource for this Agent. Select the Network Name resource that was created for this Agent. This display-only field indicates the order in which clusters will perform failover handling.
Chapter 7
97
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. This requires placing the parameters that you would normally enter in interactive mode into a file that is accessed by the silent installation procedure. The silent installation procedure can be used to install a single Agent each time it is run.
1 Prepare the installation parameters:

A. Log in using a user ID having Administrator privileges on the current computer. B. Insert the Installation CD. C. Browse to the Windows folder of the CD-ROM drive. D. Run (double-click) the prep_silent.bat file. The parameters are saved in the following file: %TEMP%\DRNDN.6.4.01Silent.bat
2 Run the silent installation procedure:

A. Ensure that the installation CD used in Step 1 is still available. B. Run the following command: %TEMP%\DRNDN.6.4.01Silent.bat C. Check the %TEMP%\DRNDN6.4.01_silent_log.txt file to ensure that the installation ended successfully. The silent installation procedure adds a CONTROL-M Agent <vv.rr.mm> entry to the Start => Programs menu.
NOTE
The same batch file can be copied to other computers and used to create several identical installations. If necessary, you can modify the CD source mapping by altering the Auto_CD_ Image variable in the DRNDN.6.4.01Silent.bat file. UNC mapping can also be used.
98
Silent installation
Table 16 Parameter
Silent installation parameters (Part 1 of 2) Description

Logical name of this Agent installation. This name is used to differentiate between multiple installations of CONTROL-M/Agent on the same computer. Name of the installation folder. Default: <drive>\Program Files\BMC Software\CONTROL-M Agent\ <drive> identifies the drive where Program Files are defined in this computer Name of host computer for the primary CONTROL-M/Server that handles this Agent. Default: Name of the computer where installation is performed. Note: Specify a computer name, not an IP address. List of authorized CONTROL-M/Servers, including the primary CONTROL-M/Server. These hosts are all authorized to submit jobs for processing. Syntax: host1|host2|...|hostn. The separator is a vertical line. Embedded blanks are not allowed. Example, TLVS2K038|VGW1K|FPB62G Note: Specify a computer name, not an IP address.
AgentName
DestinationFolder
CTMAG_ServerHostName
CTMAG_PermittedServers
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). Default: 7005 Note: Specify a numeric value from 1024 to 65535.
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). Default: 7006 Note: Specify a numeric value from 1024 to 65535.
CTMAG_TCP_Timeout CTMAG_LOGON_AS_USER
TCP/IP Timeout (in seconds). Valid values: numeric value greater than or equal to zero. Default: 60 Job submission method. Valid values are:
Y Jobs are submitted under the user and password specified by the CTMPWD utility, or specified by the owner identification settings in the CONTROL-M Configuration Manager. N Jobs are submitted under the current user and password. Default.
CTMAG_DOMAIN
Domain from which the log in will be performed. Valid values: <domainName> " " (Blank) . (period)
CTMAG_DFTRRT
Default printer for job output (sysout) files. Specify a printer name.
Chapter 7
99
Table 16 Parameter
Silent installation parameters (Part 2 of 2) Description

Flag that indicates whether job object statistics are sent to sysout. Valid values:

CTMAG_JO_STATISTIC
Y Job object statistics are sent to sysout. Default. N Job object statistics are not sent to sysout.
CTMAG_SRV_USER
User under which the CONTROL-M/Server service will run. Specify a user account with full privileges in the administrative group, for example, user_company.com\user. Note: This option can be used only if the service is set to run under a specified user account (defined by specifying LOGONACCOUNTTYPE= "0", see above).
CTMAG_SRV_PASS
User password.
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. Default: 7009

100
Chapter
8
101 102 102 103 103 103 104 104
Post installation for CONTROL-M/Agent

8
The following topics are discussed in this chapter: Setting CONTROL-M/Agent file permissions for NFS (UNIX) . . . . . . . . . . . . . . . . . Checking CONTROL-M utilities accessibility on CONTROL-M/Server and CONTROL-M/Agent (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the automatic startup procedure for CONTROL-M/Agent . . . . . . . . . . Upgrading from CONTROL-M/Agent version 6.2.0.1 or earlier. . . . . . . . . . . . . . . . Changes to system files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade with CONTROL-M Option for Oracle Applications installed . . . . . . . Upgrade with CONTROL-M Option for PeopleSoft installed . . . . . . . . . . . . . . . Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting CONTROL-M/Agent file permissions for NFS (UNIX)

If you have chosen to put the sysout directory on an NFS file system, add the following line to the ctm/data/OS.dat file and restart the Agent: SYSOUT_MODE 666 If you have chosen to put the proclog directory on an NFS file system, add the following line to the ctm/data/OS.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.
Chapter 8 Post installation for CONTROL-M/Agent
101
In addition, see Setting the protocol version for the upgraded CONTROL-M/Agent on page 89.

If after installation, CONTROL-M utilities are not recognized in command prompt mode, 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, click OK.
Modifying the automatic startup procedure for CONTROL-M/Agent

BMC Software recommends that you start CONTROL-M/Agents automatically at system startup time. You should consult your system administrator for the correct commands with regard to CONTROL-M/Agent on the platform you are using. During installation of CONTROL-M/Agent, a ready-made startup script, rc.agent_user, is placed in <agentInstallDir>/ctm/scripts.
NOTE
CONTROL-M/Agents that were shut down manually are not restarted by the automatic startup procedure during a shutdown-restart operation.
102
Upgrading from CONTROL-M/Agent version 6.2.0.1 or earlier
Upgrading from CONTROL-M/Agent version 6.2.0.1 or earlier

This section specifies the changes that are implemented when CONTROL-M/Agent is upgraded from previous versions.
Changes to system files

You should be aware of that the installation procedure modifies system files as follows: 1. The following line is removed from the /etc/inetd.conf file or the /etc/xinetd.conf file: <service><socketType> tcp nowait root <agentExe> p_ctminetd -e I $CONTROLM/ctm/ <service> Agent service-name specified during installation. Default: ctmagent <socketType> Socket type used for the service (stream for tcp). <agentExe> Path of CONTROL-M/Agent executable files. $CONTROLM/ Path of CONTROL-M/Agent user home directory. 2. The following line is removed from file /etc/services: <service> <portNumber>/<protocol> # CONTROL-M Agent <service>Agent service-name specified during installation. Default: ctmagent <portNumber>Value specified for Server-to-Agent Port Number. <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, perform the following steps before upgrading CONTROL-M/Agent to the new version.
Chapter 8 Post installation for CONTROL-M/Agent
103
Upgrade with CONTROL-M Option for PeopleSoft installed
1 Ensure that all jobs submitted to the CONTROL-M/Agent have ended. Otherwise,
the status of running and submitted jobs will become UNKNOWN.
2 Create another UNIX user account for the Option. 3 Install the latest version of the Option on the new user account and configure its
environment variables.
4 Copy all files from the <oldControl-mOption>/DATA directory to the

<newControl-mOption>/DATA directory.
5 Verify that the new Option is working properly. 6 Before upgrading the Agent, modify its .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).
2 If necessary, modify the CLASSPATH environment variable to point to the new

location of the CONTROL-M Option for PeopleSoft files.

You have now completed the installation of CONTROL-M/Agent.
104
Chapter
9
105 106 107 108
Running your first job

The following topics are discussed in this chapter: Testing the new installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating and running a job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the test data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Testing the new installation

You can test your new installation of the CONTROL-M solution by creating and running a simple job. To create and run your first job, use the following procedure:
NOTE
You must complete the post-installation procedures before running your first job.
1. Use CONTROL-M/Desktop to create and submit a job. For more information, see Creating and running a job on page 106. 2. Use the CONTROL-M/EM GUI to check that the job was submitted and that it ran and completed correctly. For more information, see Monitoring the job on page 107. After ensuring the software is functioning properly you can remove the test job from the database. For more information, see Removing the test data on page 108.
Chapter 9
105
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. For more information about creating and submitting a job see the CONTROL-M User Guide.
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 the CONTROL-M/GUI Server to
which you want to connect, and click Login.
3 From the File menu, choose New => Online Workspace. 4 From the Edit menu, choose New Job to open the job editing form. 5 In the Apply Template field, select one of the following:
WINDOWS_JOB: to run a job on a Windows server. UNIX_JOB: to run a job on a UNIX/Linux server.
6 In the CONTROL-M field, select the server that will control the job. NOTE
If the server you need is not on the list, use the CONTROL-M/Configuration Manager to check the servers status. For more information see the CONTROL-M Administrator Guide.
7 In the Job Type field, select OS from the list. 8 In the Job Name field, enter a name for the job processing definition. 9 In the Task Type field, select Command from the list. 10 In the Command field, enter the command that you want the job to perform. In this
case, the job will perform a directory command.
EXAMPLE

On Windows you could use the DIR command On UNIX/Linux you could use the ls command
106
Monitoring the job
11 In the Hierarchy area, fill in the fields that are required to set up jobs in CONTROLM:
Table: define an arbitrary scheduling table name; all jobs must run under a
scheduling table. A scheduling table groups jobs that are processed together.
Application: define an arbitrary name to describe a category of jobs. For
example: Accounting, Inventory, Payroll.
Group: define an arbitrary name that represents a subset of the category in the Application field. For example, an accounting application might have sub-
categories Budget, Finance, and Receivables.
12 In the Owner field, enter the User ID for whom the job is executed or use the
default supplied by the application.
13 In the Author field, enter the user name of the person creating the job. The Author
field defaults to the logged on user for CONTROL-M/Desktop.
14 Click Save & Order. The CONTROL-M/Desktop opens the Order/Force

Parameters dialog.
15 Click Order. The CONTROL-M/Desktop opens the Job Action Report window
which lists the jobs being ordered and information on the progress.
16 In the Job Action Report window click Close. 17 In the job editing form click Close.
Monitoring the job

This section describes how to monitor the progress and results of your job using CONTROL-M/EM GUI. For more information, see the CONTROL-M User Guide.
To monitor a job 1 Open CONTROL-M/EM GUI by choosing Start => Programs => CONTROL-M
Enterprise Manager 6.4.01 => Default => CONTROL-M Enterprise Manager GUI.
3 From the File menu, choose Open Viewpoint to open a Viewpoint.
Chapter 9
107
Removing the test data
4 In the CONTROL-M/Enterprise Manager ViewPoints window, select All Jobs

from the list and click OK.
5 Double-click the server that is running the job. The job hierarchy is displayed on
the left side of the title bar.
6 Double-click the application you entered on the job definition window. 7 Double-click the group you entered on the job definition window. The application
expands the group entity and shows the job you created. The color in the title bar of the entity indicates the status of the job. Table 17 lists the possible colors and their related status. Table 17
Color Gray Green Yellow Blue Pink Red White
Job status colors indicated by the color of a nodes title bar

Status Wait Condition Ended OK Executing Wait Resource Wait User Ended Not OK Unknown
If you have a green status, you have completed running your first job successfully.
TIP
Use the Sysout menu option to view the output of the job. From the Analysis menu, choose Sysout.

After you have verified that CONTROL-M/EM is working correctly, you can remove the test data.
To remove the test data 1 Open CONTROL-M/Desktop by choosing Start => Programs => CONTROL-M
Enterprise Manager 6.4.01 => Default => CONTROL-M Desktop.
3 From the Tools menu, choose Scheduling Table Manager. CONTROL-M/Desktop

opens the Scheduling Table Manager window.
4 In the Scheduling Table Manager window, select the table name you entered in
your job definition.
TIP
Double-click the table name to view the jobs in the selected table.
5 Click Delete. CONTROL-M/Desktop displays a message asking for verification of

the deletion.
6 Click Yes to verify the deletion. CONTROL-M/Desktop opens the Table Action
Report window which lists the status of the deletion.
7 In the Table Action Report window, click Close. 8 In the Scheduling Table Manager window, click Close.
Chapter 9
109
110
Appendix
Installing an Oracle database on UNIX

A
This appendix describes how to install an Oracle database server on UNIX for use with CONTROL-M. Table 18 describes the ways that CONTROL-M can be installed with an Oracle database server. Installation can be performed using interactive mode or silent mode. The following topics are discussed in this appendix: Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Running the Oracle pre-installation script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Installing a database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Installing a dedicated database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Installing on an existing database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Installing a tablespace using an on-site Oracle client . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Installing an Oracle client (for CONTROL-M/EM only) . . . . . . . . . . . . . . . . . . . . . . . 119 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Performing a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Setting Oracle installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Checking the installation log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Cleaning up a failed Oracle installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Cleaning up after a dedicated installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Cleaning up after an existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Performing post-installation cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Appendix A Installing an Oracle database on UNIX
111
WARNING
Oracle must be installed silently if you want to install CONTROL-M/EM or CONTROLM/Server silently.
WARNING
Before installing Oracle on Red Hat Enterprise Linux AS/ES version 5.0, ensure that SELINUX=disabled in the /etc/sysconfig/selinux file.
Table 18
Dedicated
Oracle installation types

Explanation Installs full Oracle server and client software, initiates an instance, and inserts a CONTROL-M database schema. The following types of dedicated installation are available:

Installation Type
Without customization Uses default values for all Oracle Database parameters. With customization Allows modification of installation parameters.
Existing
Installs an Oracle client only and inserts a CONTROL-M database schema on an existing database server. The existing database server must be Oracle Full Enterprise Edition. Installs only the Oracle client software. This installation type can be performed only after the database schema for CONTROL-M exists on the Oracle database server.
Oracle Client
Before beginning, ensure you have prepared everything necessary for the installation as described in Chapter 2, Planning the CONTROL-M solution. Supported Oracle database server and database client versions are listed in Table 2 on page 33. If you are migrating from an earlier version of CONTROL-M/EM, see the CONTROL-M /Enterprise Manager Migration Guide. If you are migrating from an earlier version of CONTROL-M/Server, see the CONTROL-M/Server Migration Guide.
112
Preparing for installation

Table 19
1 2 3
Installation steps
Step Instruction
Create the UNIX account. If you are installing a dedicated database server, the account group should be dba. Before starting the installation process, ensure that no processes are running in the background on the CONTROL-M/EM or CONTROL-M/Server account. Run checkreq to verify that the UNIX server is properly configured.
Prepare the parameter information you need before beginning the installation. See explained in Table 20, Oracle Database UNIX installation parameters on page 123.
Perform Running the Oracle pre-installation script on page 113. Oracle Server Perform the Installing a database server on page 114 to install the full Oracle server and client software. Oracle Client + tablespace 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.
5 6
Perform the Performing post-installation cleanup on page 127.
Running the Oracle pre-installation script

This script determines the database software (server or client) to be installed and sets the required defaults. It must be run before performing any of the Oracle installations in this appendix.
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 account.
2 Mount the CONTROL-M/EM or CONTROL-M/Server installation DVD as

required. 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/orapreinst.sh The <dvdPath> variable is the directory on which you mounted the CONTROL-M installation DVD.
113
Installing a database server
4 Follow the directions on the screen. 5 Log off the root account.
Installing a database server

You can either install a dedicated database server or an existing database server. Installing a dedicated database server enables you to install the full Oracle server and client software. For more information, see Installing a dedicated database server on page 114. 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. For more information, see Installing on an existing database server on page 115.
Installing a dedicated database server

This process installs a CONTROL-M Oracle database server on the local computer. The CONTROL-M Oracle database server can be installed on a raw partition or on a regular file system. If you want to use raw partitions for the CONTROL-M database devices, prepare them before installation of the Oracle database server. The size of each raw partition must be equal to the size of the tablespace plus 4 MB. Oracle Database log files must not be placed on a raw partition. Consult your system administrator for more information about raw partitions. Use the following procedure to perform the installation:
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 in to the CONTROL-M/EM or CONTROL-M/Server account as necessary. 3 Mount the installation DVD. For details of mount procedures for your UNIX
platform, see Appendix I, Mounting DVDs and CDs on UNIX computers.
4 Use the following command to run the installation script from the installation
directory:
114
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, you must choose Custom:
Default Installs a CONTROL-M Oracle database server with default database parameters on the local computer. A CONTROL-M/EM (or CONTROLM/Server) tablespace and user are also installed. 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 CONTROL-M/Server) tablespace and user are also installed.
6 Follow the instructions on the screen, filling in parameter values as necessary. 7 After the Installation completed successfully message is displayed, continue with
Performing post-installation cleanup on page 127.

Continue with Chapter 3, Installing CONTROL-M/EM on UNIX or Chapter 5, Installing CONTROL-M/Server as necessary.

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. The location, port number, and name of the existing Oracle database server, as well as the name and password of the system administrator, must be specified in the installation parameters.
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
115
server name
2 Using the operating system account that installed the Oracle server, log in to the
computer where the Oracle database server is installed.
NOTE
The existing Oracle database instance must be running during installation and whenever CONTROL-M/EM or CONTROL-M/Server is operating.
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). <dbaPassword> is the DBA account password (Oracle default: manager).
4 Verify that this database is served by an Oracle Listener port running on the same
computer on which the database is installed.
5 A unique tablespace name and a tablespace owner name (DBO) must be specified
for each CONTROL-M database. To display a list of existing tablespace names:
A Log in as the database administrator. B Type the following SQL instruction:

SQL> select tablespace_name from dba_tablespaces; To display a list of existing usernames:
A Log in as the database administrator. B Type the following SQL instruction:

SQL> select username from dba_users;
NOTE
When creating more than one CONTROL-M installation using the same Oracle database server, you must specify a unique tablespace name and tablespace owner name for each installation.
116
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. 2 Mount the installation DVD. For details of mount procedures for your UNIX

4 Select existing installation. 5 Follow the instructions on the screen, filling in parameter values as necessary. 6 After the Installation completed successfully message is displayed, continue with

Installing a tablespace using an on-site Oracle client

At installations where business policy allows only Oracle supplied software to be used, 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.
WARNING
This is an advanced level option that should be used with care and only by qualified DBA personnel. Oracle version 10.2.0.3 database client should be used for this operation. The use of higher versions of Oracle is not recommended as they have not been tested by BMC Software.
The location and name of the existing Oracle installation, the system administrator name, and the system administrator password must be specified in the installation parameters.
117
1 Log in to the CONTROL-M/EM or CONTROL-M/Server account. 2 Mount the installation DVD. For details of mount procedures for your UNIX
3 Set the environment variable USE_EXISTING_ORACLE to value Y. See Setting

WARNING
When using USE_EXISTING_ORACLE, ensure that all Oracle client binaries, lib directories, and files have 640 protection. For more information, see your database administrator.

5 Select existing installation. 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 a connection alias.

118
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 Log on to the CONTROL-M account. 3 Use the following command to run the installation script.
<cdPath>/Oracle/inst_oracle
4 Select Client only installation. 5 Follow the instructions on the screen, filling in parameter values as necessary. 6 After the Installation completed successfully message is displayed, continue with

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.2.03 client (only) to communicate with a CONTROL-M database.
NOTE
This is an advanced level option. It should be used with care and in consultation with BMC Software qualified DBA personnel.
119
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.
2 Log on to the CONTROL-M account. 3 Set the environment variable USE_EXISTING_ORACLE to value Y. See Setting

<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.

120
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.
121
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
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:
$HOME/silent_dir/orapreinst*.log $HOME/silent_dir/orapostinst*.log
122
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)
Description Parameter or Prompt
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.
123
Table 20
Oracle Database UNIX installation parameters (Part 2 of 4)

Description The default path to the system 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/<emusersystem01.dbf or ctmusersystem01.dbf >
Parameter or Prompt Database system tablespace file name
Database system tablespace size (for both CONTROL-M/EM and CONTROL-M/Server) Database temporary tablespace file name (full path)
small (500 MB), medium (550 MB), or large (600 MB). Default: depends on the size (small, medium, or large) chosen for the database. The default path to the temporary 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/<emusertemp01.dbf or ctmusertemp01.dbf >
small (100 MB), medium (250 MB), or large (500 MB). Database temporary tablespace file size (for Default: depends on the size (small, medium, or large) chosen for the database. 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. Default: $HOME/oracle/oradata/<EM640 or ctrlm>/emuserdata01.dbf. For installation using an existing Oracle Database server, this parameter indicates the full path and file name for the Data file of the database. The specified path must be an existing path for which the administrator of the existing Oracle instance has READ and WRITE permission. The file name must not be the name of an existing file. This file will be created during installation of the database. EM Data tablespace name Name of the data tablespace that will be created on the existing Oracle database or instance. This tablespace will contain the database data (name should start with Ctm Data tablespace name a letter followed by 1-24 alphanumeric characters). Default: emuser or ctmuser. EM Database user or Ctm Database user Name of the CONTROL-M/EM database user (owner) to be created. This is the user used to log in to CONTROL-M/EM or CONTROL-M/Server. For CONTROL-M/EM, the name must begin with a letter (A-Z, a-z) followed by up to 7 alphanumeric characters (includes underscores). For CONTROL-M/Server, the name must begin with a letter (A-Z, a-z) followed by up to 17 alphanumeric characters (includes underscores). Default: emuser or ctmuser.
124
Table 20

Description 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.
Parameter or Prompt Oracle Database Instance Name
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 Oracle SYSTEM password
For installations that use an existing Oracle database server, Name or IP address of the computer on which the existing Oracle instance is located. 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.
125
Checking the installation log
Table 20

Description Support for East Asian languages (Simplified Chinese, Traditional Chinese, Japanese, and Korean) Default: N - Latin1 (WE8ISO8859P1), Y - UTF8.
Parameter or Prompt CJK installation for CONTROL-M/Enterprise Manager (Y/N) User password
Password for the CONTROL-M/EM database user (4 to 30 characters, alphanumeric). The characters are not displayed for security reasons. 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

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.
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.
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.

<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
Appendix
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. Installation can be performed using interactive mode or silent mode. The following topics are discussed in this appendix: Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a CONTROL-M/EM tablespace using an on-site Oracle client . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Oracle installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cleaning up a failed existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 131 131 131 133 134 135 136 139
WARNING
Oracle must be installed silently if you want to install CONTROL-M/EM silently.
Appendix B
129
Table 21
Dedicated
Oracle installation options

Explanation Installs full Oracle server and client software, initiates an instance, and inserts a CONTROL-M/EM database schema. Two types of dedicated installation are available:

Installation type
Without customization Uses default values for all Oracle Database parameters. With customization Allows modification of installation parameters.
Existing
Installs an Oracle client only and inserts a CONTROL-M/EM database schema on an existing database server. The existing database server must be Oracle Full Enterprise Edition. Installs only the Oracle client software. This installation type can be performed only after the database schema for CONTROL-M/EM exists on the Oracle database server.
Oracle Client
Before beginning, make sure you have prepared everything necessary for the installation as described in Chapter 2, Planning the CONTROL-M solution. Supported Oracle database server and database client versions are listed in Table 2 on page 33. If you are migrating from an earlier version of CONTROL-M/EM, download the Migration Toolkit and the CONTROL-M /Enterprise Manager Migration Guide from BMC Software Customer Support Web site (http://www.bmc.com/support_home) solution SLN000015053002.
NOTE
All installation procedures must be performed directly on the local computer. You must not use remote management software to perform any part of the Oracle installation.

Table 22 Installation steps Step Instruction Prepare the parameter information you need before beginning the 1 installation. See explained in Table 23, Oracle Database Windows installation parameters on page 136.
130
Running the installation
Table 22
2
Installation steps
Oracle Client + tablespace
Step Instruction
Oracle Server 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. database client on the local computer and a CONTROL-M tablespace on the Oracle database server.
Running the installation

1 Stop all applications on the computer on which the installation will run. 2 Insert the CONTROL-M/EM installation DVD. If you are running the installation
from a network drive, the drive must be mapped using UNC mapping.
3 Navigate to the Oracle folder and run Setup.bat. 4 Follow the prompts to complete the installation. The parameters and values for
this installation are described in Table 23 on page 136.
NOTE
An Oracle installation menu is added to the Start => Programs menu.

Continue with Chapter 3, Installing CONTROL-M/EM on Windows.
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, this process allows an on-site Oracle client to be used to facilitate CONTROL-M/EM installations on an Oracle database server.
Appendix B
131
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. Oracle version 10.2.0.3 database client should be used for this operation. The use of higher versions of Oracle is not recommended as they have not been tested by BMC Software.
In addition to installing CONTROL-M/EM components, 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. 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. When you install a CONTROL-M/EM database on an existing Oracle instance, that instance must run Oracle software releases certified by BMC Software for use with CONTROL-M/EM. CONTROL-M/EM supports the Oracle database server and database client versions listed in Table 2 on page 33.
2 On the Oracle client computer, from the Start menu, select Run. Type regedit and
click OK to run the Registry Editor.
WARNING
Follow the instructions carefully. Making incorrect changes can damage your system.
3 In the Registry Editor windows tree (left pane), select

HKEY_LOCAL_MACHINE=>SOFTWARE=>ORACLE.
4 Right-click the right-hand pane of the Registry Editor window, and choose New =
> String Value. Replace the default text with the string USE_EXISTING_ORACLE. The installation procedure detects the registry changes.
5 Insert the CONTROL-M/EM installation DVD. If you are running the installation
from a network drive, the drive must be mapped using UNC mapping.
6 Navigate to the Oracle folder and run Setup.bat.
132
7 Select Installation on Existing server in the Oracle Installation Type window. 8 Follow the instructions on the screen until The procedure is complete window is
displayed. During the installation, you will be prompted to:
A Select from the list of existing Oracle Homes. CONTROL-M/EM database

operation requires sqlplus. 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. To use an existing connection string that is not on the list, choose Other and enter a connection string.
C Enter a name and a password for the new CONTROL-M/EM database (schema)
owner. The new database owner name must not be the same one used for the Oracle database server.
D Enter the username and password of the Oracle administrator. These values are
usually SYSTEM and MANAGER respectively. However, your database administrator may have modified them.
E Select the desired tablespace size. NOTE

The tablespace name and location must be unique for the current database installation. The specified path must exist on the database server host computer.
Specify Data Files Component Tablespace Name Default: <instanceName>_EM_USERS. Specify the path for the data files component For example: D:\Oracle\oradata\<instanceName>\data01.dbf. Specify the size for the data files component Defaults: 250, 800, and 2500 MB depending on data tablespace size.

Continue with Chapter 3, Installing CONTROL-M/EM on Windows.
Appendix B
133

Silent installation is used to install Oracle from a batch file. Two stages are involved: 1. Preparing the batch 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 batch file. 2. Running the prepared batch file When the prepared batch file runs, Oracle is installed using the parameters you specified in the previous step. You can reuse this batch file to silently install Oracle on other computers.
To prepare the silent installation batch file 1 Navigate to <dvdPath>:\Oracle\OracleInstallationFiles\executables. 2 Run inst_oracle.bat.
The parameter file, OracleInstallationParms_<timeStamp>.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.
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, the DBO name and password, host name, etc.).
1 Log on to the computer on which you want to perform the silent installation. 2 Copy the silent installation parameter file,
OracleInstallationParms_<timeStamp>.txt from the computer on which it was prepared to the <drive>:\ Program Files\BMC Software\Oracle\BMC_Products folder on the local computer.
134
If this folder does not exist, you will need to create it.
3 Insert the CONTROL-M/EM installation DVD. 4 Run the following file from the DVD drive:
Oracle\OracleInstallationFiles\executables\OracleInstallation\ OracleInstallation.exe Installation progress is displayed on the monitor. Upon completion, a message is displayed. The results of the installation is recorded in the following log: <oracleHome>:\Program Files\BMC Software\ Oracle\BMC_Logs\Oracle_<timeStamp>.log
WARNING
No checks are performed on the contents of the parameter files. If any parameter is incorrect, the installation will fail.

Continue with CONTROL-M/EM Windows Silent installation on page 56.
Appendix B
135

Table 23 Parameter
Data File Component
Oracle Database Windows installation parameters (Part 1 of 4) Description

Name Data files component tablespace Name. Default: <instanceName>_EM_USERS. Note: For installation using an existing Oracle database server, the tablespace name must be unique for the current database installation. Location Path for the data files component. Default: <drive>:\Oracle\oradata\<instanceName>\data01.dbf. Note: For installation using an existing Oracle database server, the tablespace location must be unique for the current database installation, and the path must exist on the computer where the database server is installed. Size Size for the data files component: small (250 MB), medium (800 MB), or large (2500 MB). Default: depends on the size (small, medium, or large) chosen for the database.
Database Owner
Username
Name of the CONTROL-M/EM database owner (user). Normally, this is also the name of the CONTROL-M/EM administrator. The administrator is the default user when logging on to CONTROL-M/EM GUI for the first time. Enter the name of the database user that was defined when the CONTROL-M/EM Oracle tablespace was created. The name must begin with a letter (A-Z, a-z) followed by up to 7 alpha-numeric characters (includes underscores). Default: emuser Note: When installing a new tablespace using an existing Oracle database server, the database owner name specified in this window must not be the same as any existing user name for the Oracle database server.
Password The password is required only for a Client installation. Database Server Username Password
Password for the CONTROL-M/EM database owner. Enter the password of the CONTROL-M/EM database owner that was defined when the CONTROL-M/EM Oracle tablespace was created. Default: SYSTEM. This value cannot be modified for installation of a dedicated database server. Password of the Oracle Server Administrator. Default: MANAGER.
136
Table 23 Parameter

Host name of the computer on which the Oracle database server is installed. This parameter is required only when installing a new database using an already installed (existing) Oracle database server. Note: The value for this parameter is in the HOST parameter in the listener.ora file on the server computer. If you cannot find the listener.ora file, or if a parameter occurs more than once in the file, consult your Oracle database administrator to determine the value you should use. There is no default. For more information about how to locate the listener.ora file, see the Instance Name parameter in this table.
Database Server Host Name
Destination
Installation folder for the Oracle components. Default: <osInstallDrive>:\Oracle The folder name must not include blanks.
Instance Name
Name of the database instance for the CONTROL-M/EM Database. Maximum length: 8 characters. Default: EM640. How do I find this value on an existing Oracle server? 1. Search for the listener.ora file in a location similar to the following: <oracleHome>\Oracle\Ora1020\network\ADMIN\ (on Windows) <oracleHome>/Oracle/product/10.2.1/network/admin/samples (on UNIX) <oracleHome> is the folder in which the Oracle server is installed. 2. 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: Use not more than 8 alphanumeric characters. The first character must be a letter, not a number.
Oracle installation Dedicated server Type (without customization) Dedicated server (with customization) Existing server Oracle client
Uses default values for all Oracle database parameters.
Allows you to modify Oracle database parameters.
Installs a tablespace for CONTROL-M/EM on an existing Oracle database server. Installs a CONTROL-M Oracle client component only. This installation type can be performed only after the tablespace for CONTROL-M/EM has been defined on the Oracle database server.
Appendix B
137
Table 23 Parameter

Port number Default: 1521. Contact your System Administrator to verify the correct value. Note: The value for this parameter is in the PORT parameter in the listener.ora file on the server computer. If you cannot find the listener.ora file, or if a parameter occurs more than once in the file, consult your Oracle database administrator to determine the value you should use. For more information about how to locate the listener.ora file, see the Instance Name parameter (above).
Oracle Server TCP/IP Port Number
Redo Log Files
# 1 Location
Path for the first redo log file. Default: <OracleHome>:\Oracle\oradata\<instanceName>\redo01.dbf. Path for the second redo log file. Default: <OracleHome>:\Oracle\oradata\<instanceName>\redo02.dbf. Size for each redo log file. Choose small (50 MB), medium (100 MB), or large (200 MB). Default: depends on the size (small, medium, or large) chosen for the database.
# 2 Location
Size
Rollback Component
Location
Path for the rollback tablespace. Default: <OracleHome>:\Oracle\oradata\<instanceName>\rbs01.dbf. Size for the rollback tablespace. Default: 330 MB for all data tablespace sizes. System (Component) tablespace location. Default: <OracleHome>:\Oracle\oradata\<instanceName>\system.dbf. System (Component) tablespace size: small (250 MB), medium (300 MB), or large (350 MB). Default: depends on the size (small, medium, or large) chosen for the database.
Size System Component Location
Size
Tablespace Size
The size specification for the CONTROL-M/EM database. Choose small, medium, or large. Default: medium.
138
Cleaning up a failed existing installation
Table 23 Parameter

Location Path for the Temporary Tablespace. Default: <drive>:\Oracle\oradata\<instanceName>\temp01.dbf. Size for the for the temporary tablespace: small (50 MB), medium (100 MB), or large (200 MB). Default: depends on the size (small, medium, or large) chosen for the database.
Temporary Component
Size
Upgrade Parameter Path
If the OracleUpgradeParms.txt file is on the target drive, an upgrade installation is assumed and the path to this file is displayed. This file contains parameter settings that will be carried over to the new database during migration. No default.

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.
To uninstall and cleanup the installation 1 Run the uninstall program (see Uninstalling a CONTROL-M Oracle database
server from Windows on page 207).
2 Log on to the Oracle database server account as the database administrator. 3 Use the drop user <userName> cascade; command to delete the username that was
used for the failed installation.
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. Do not delete raw
partitions.
Appendix B
139
140
Appendix
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.
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. Otherwise the installation may fail.
The following topics are discussed in this appendix: Interactive installation of the CONTROL-M database . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Silent installation of the CONTROL-M database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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.
Interactive installation of the CONTROL-M database

1 Ensure that the Sybase database server is up and running. 2 Ensure that the client character-set matches the server character-set.
Appendix C Installing a CONTROL-M database with Sybase on UNIX
141
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. For information about mounting a DVD, see Appendix I, Mounting DVDs and CDs on UNIX computers.
4 Log on to the CONTROL-M/EM or CONTROL-M/Server account. 5 Issue the following command to activate the installation script:
<dvdPath>/Sybase/setup.sh

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:
Running the installation using the prepared parameters file When the installation is run using the prepared parameters file, the database components are installed using the parameters you specified in the previous step. You can reuse this parameters file to silently install the database components on other computers.
142
Silent installation of the CONTROL-M database
2 Ensure that the database server is up and running before beginning the database
installation.
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. For information about mounting a DVD, see Appendix I, Mounting DVDs and CDs on UNIX computers.
4 Log on to the CONTROL-M/EM or CONTROL-M/Server account. 5 Set the environment variable BMC_SILENT_INSTALL to value Y. See Setting

<dvdPath>/Sybase/setup.sh

The installation parameters saved to ${HOME}/BMCINSTALL/products/products.ctl. If you want to change parameter values, modify them in the parameters file manually.
To install silently 1 Log on to the CONTROL-M/EM or CONTROL-M/Server account. 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. During a client installation this is the current database owner password.
143
<databaseAdministratorPassword> is the database administrator password.

<dvdPath>/Sybase/setup.sh -r <parameterPath> <dvdPath> is the path of the mounted DVD. <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.
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
Table 24 UNIX interactive and silent installation parameters (Part 1 of 2)
Description Interactive parameter or prompt Silent installation parameter name
Database [SETP]/BMC/SYBASE/PRIVILEGE_ Database administrator login name. This is Administrator Login LOGIN relevant to an Existing installation mode only. Default: sa Database Administrator Password Database Name Database Owner Login Database Owner Login (for client) Database Owner Password Environment variable SA_PASSWORD Database administrator password. This is relevant to an Existing installation mode only.
[SETP]/BMC/SYBASE/DATABASE_ Database name to be created. This is relevant NAME to an Existing installation mode only. [SETP]/BMC/SYBASE/DATABASE_ Database owner login name that will be OWNER_LOGIN created. This is relevant to an Existing installation mode only. [SETP]/BMC/SYBASE/CLIENT_DA Existing database owner login. This is relevant TABASE_NAME to a client installation in a distributed system only. Environment variable DBO_PASSWORD This is relevant to a client installation in a distributed system only.
144
Table 24
UNIX interactive and silent installation parameters (Part 2 of 2)

Description
Interactive parameter or prompt Silent installation parameter name
Data tablespace size [SETP]/BMC/SYBASE/DATABASE_ Size of the CONTROL-M database (Small, Medium, Large). This is relevant to an Existing SIZE_MODEL installation mode only. Default: Medium Data Device Full Path File Name Data Device Size [SETP]/BMC/SYBASE/DATABASE_ Full path to data device file name to be created. DATA_DEVICE_PATH This is relevant to an Existing installation mode only. [SETP]/BMC/SYBASE/DATABASE_ Amount of space (in MB) to allocate for the DATA_DEVICE_SIZE data portion of the database. You must take into consideration the number of jobs in the Active Jobs file. This is relevant to an Existing installation mode only. [SETP]/BMC/SYBASE/INSTALLAT Installation mode values: Existing or Client ION_TYPE Default: Existing [SETP]/BMC/SYBASE/SOFTWARE_ Location of Sybase database software ROOT_DIRECTORY (server/client). [SETP]/BMC/SYBASE/DATABASE_ The Sybase alias name as listed in Sybase ALIAS_NAME interfaces file. [SETP]/BMC/SYBASE/DATABASE_ Full path to log device file name to be created. LOG_DEVICE_PATH This is relevant to an Existing installation mode only. [SETP]/BMC/SYBASE/DATABASE_ Amount of space (in MB) to allocate for the LOG_DEVICE_SIZE transaction log. This is relevant to an Existing installation mode only.
Installation mode Installed Sybase root directory Installed Sybase server alias name Log Device Full Path File Name Log Device Size
145
146
Appendix
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), and CONTROL-M for a cluster installation. Once you have completed the database server and data files preparation, you can install CONTROL-M interactively or silently, on UNIX or Windows, as described in this book. The following topics are discussed in this appendix: Preparing the database for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database post-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating cluster resources for UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the database for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating cluster resources for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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, you should first plan and prepare the configuration according to the information set out in this section.
Appendix D
147
Database pre-installation
Before starting the installation of the CONTROL-M database, you must plan how the CONTROL-M database will be implemented. 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, as both accounts point to the same shared location, it is only necessary to install a database server on one node.
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, or on different file systems. Use the following guidelines to determine where to locate the database server:
When implementing a CONTROL-M database server in dedicated mode, the database server and CONTROL-M database must always be running on the same node. When installing Oracle as the database server, using the USE_EXISTING_ORACLE environment variable, the client can be located on the same file system as CONTROL-M or on a different file system. If you are using different file systems, the file system on which the Oracle client is located must always be available to CONTROL-M, so it will be able to connect to a remote database server. You must also ensure that all Oracle client binaries, lib directories, and files have 640 protection. For more information, see your database administrator.
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, use the following guidelines when choosing which resource group your database resources will belong to:
148
When the database server and CONTROL-M are implemented into the same 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. When the implementation is performed using a single resource group, the database server can be implemented in either dedicated or existing mode. 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), there must be a dependency between the two resource groups, so they will always be running on the same node. On a CONTROL-M installation with Embedded PostgreSQL, the database server is always installed within the same file system. However, the CONTROL-M tablespace can reside on a different file system. In this case, both file systems must belong to the same resource group.
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), which enables replicating the Oracle database content to a remote location, or Oracle Real Application Cluster (formerly known as Oracle Parallel Server), which enables you to install multiple instances of Oracle to access the same database simultaneously. These features should be configured and administered by an experienced DBA. When using these solutions, the CONTROL-M home directory path should be identical on the primary and standby hosts. Some cluster vendors supply policy files for popular applications, such as Oracle. Application vendors often certify these policy files. BMC Software recommends that you use only certified policy files to monitor the CONTROL-M database.

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.
Appendix D
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, or the IP address of the UNIX console that is being used):
setenv DISPLAY terminalAddress:0
2 Run the dsedit application. 3 Replace the database server host name with the virtual host name of the database
resource group, for example, vhem640 for CONTROL-M/EM
4 Replace the SYB_BACKUP database server host name with the virtual host name
of the database resource group, for example, vhem640 for CONTROL-M/EM
Oracle 1 Ensure that the Oracle server is stopped and that none of the Oracle processes are
running.
2 Replace the host name with the virtual host name of the database resource group,
for example, vhem640 for CONTROL-M/EM) in the following files:

$ORACLE_HOME/network/admin/tnsnames.ora $ORACLE_HOME/network/admin/listener.ora
Configuring the policy file

When CONTROL-M/Server and CONTROL-M/EM share the same database server (or Oracle instance), the following actions may be required:
If CONTROL-M/Server is installed with a dedicated database, run the startdb script in the CONTROL-M/Server account but do not run the start_server script in the CONTROL-M/EM account. 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.
150
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. If the cluster vendor has a certified database policy file, BMC Software recommends that you use that file. To start the CONTROL-M database, use the following commands:
# CONTROL-M/EM EM_ACC=em640 EM_DIR=/export1/em640 su - $EM_ACC -c $EM_DIR/scripts/start_server # CONTROL-M/Server CTM_ACC=ctm640 CTM_DIR=/export2/ctm640 su - $CTM_ACC -c $CTM_DIR/ctm/scripts/startdb
To stop the CONTROL-M database, 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 - $EM_ACC -c $EM_DIR/scripts/stop_server << PASSEOF $DBA_PASS PASSEOF exit # CONTROL-M/Server CTM_ACC=ctm640 CTM_DIR=/export2/ctm640 su - $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, you can set the BMC_HOST_INSTALL environment variable to the required host name before beginning the CONTROL-M/EM installation. You can also use this variable if there is a possibility of choosing between two or more hosts (for example, a multiple network environment), or when there is a virtual network name representing a group of hosts (for example, a cluster installation). For information on setting variables, see Setting environment variables in UNIX on page 37. In a cluster environment:
Appendix D
151
Set the BMC_HOST_INSTALL environment variable to the virtual network name designated for the CONTROL-M/EM resource group. This will automatically configure CONTROL-M/EM and the TAO Naming Service to use this virtual network name. Move the disk name, IP address, and network name to the installation node.

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.
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. The database files are located on the shared disk and the database server availability is controlled by the cluster. local database configuration: The database server is locally installed on one of the
cluster nodes. 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. In this case, only database clients are installed on each of the CONTROL-M cluster nodes.
Clustered
This section describes a cluster configuration for:
Microsoft SQL Server 2005 Enterprise Edition Oracle Real Application Cluster (RAC).
152
Microsoft SQL (MSSQL) Server 2005 Enterprise Edition

When you install MSSQL Enterprise Edition on a cluster, 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. The MSSQL Server services (one service is created on each cluster node) are named by default as the virtual server name. When the MSSQL resource group is moved from one node to another, the MSSQL services are stopped on the original (primary) node and started on the alternate node. In addition to the MSSQL services resources, installation of MSSQL Server Enterprise Edition on a Windows cluster automatically creates the network name and IP address resources in the selected resource group. At that point, the MSSQL resource group becomes a virtual server and can be accessed by client applications using the virtual name.
NOTE
If, during installation, you see that the Virtual Server option in the Computer Name window is disabled, this means that the version you are installing is not the MSSQL Enterprise Edition and cannot be installed in cluster mode. For more information about installing MSSQL Server Enterprise Edition on Windows, see SQL Server 2005 Failover Clustering White Paper at http://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b4f09-b282-c6830fead499&DisplayLang=en.
Oracle Real Application Cluster (RAC)

A normal Oracle installation consists of a single Oracle instance that accesses a database on the same computer system. With RAC (formerly known as Oracle Parallel Server), multiple instances on different nodes can access the same database files simultaneously. In case of a node failure, the workload of this node will be handled by the other node of the cluster. After you prepare the system for installation, the Oracle Universal Installer (OUI) presents the list of all cluster nodes, enabling you to select a subset as targets. Then the OUI copies the Oracle software onto the first node, and then propagates the software onto the rest of the chosen nodes of the cluster. Along with all the Oracle software, Oracle Enterprise Manager (the central managing console) is automatically installed and set up. When the installation is finished, the database creation wizard and the network configuration wizard will be automatically invoked. For more information about Oracle RAC installation, see the Oracle installation documentation or the Oracle RAC whitepapers at
http://www.oracle.com/technology/products/database/clustering/RACWhitepapers.html.
Appendix D
153
Creating cluster resources for Windows
NOTE
Oracle high availability features are only relevant for CONTROL-M/Enterprise Manager.
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. In this way, the database can be accessible to all the nodes in the cluster, but it will not be maintained in a highly available manner. This configuration is not recommended for CONTROL-M when implemented in a clustered configuration.
Remote database configuration

When the database server is located on a remote node (not one of the cluster nodes), you can install a database client on each of the cluster nodes and connect them to the remote database server. In this type of implementation, you do not need to install additional database software on the cluster (besides the database client). This configuration is common when database platforms reside in a centralized location. However, the availability of CONTROL-M in this type of configuration is tied to and dependent on the remote database server availability.
Creating cluster resources for Windows

The CONTROL-M installation requires Disk, Network Name and IP Address virtual resources to be created before you begin. When you install CONTROL-M/EM to the same virtual server (resource group) as CONTROL-M/Server or MSSQL Server, you do not need to manually create the Network Name and IP address cluster resources. They are automatically created by the CONTROL-M/Server or MSSQL Server installation. The following conditions apply to cluster resources:
Do not share the IP and Network Name resources that identify the cluster with a CONTROL-M cluster instance. Disk, IP, 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. Silent installation of CONTROL-M is not supported for Microsoft Windows cluster environments.
154
CONTROL-M/EM must be installed on the shared disk that is designated for the CONTROL-M/EM resource group in the cluster environment. As part of the CONTROL-M/EM cluster aware installation procedure, 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.
Windows cluster installation parameters

Table 25
Parameter Cluster Management Select a group Select the Disk resource
Windows cluster parameters - for interactive installations only

Description This display-only field indicates the order in which clusters will perform failover handling. Highlight the virtual server group for which this CONTROL-M/EM instance IP address and the network name were created. Select the Disk resource for this CONTROL-M/EM instance.
Select the Network resource Select the network name resource that was created for this CONTROL-M/EM instance.

You can continue with Interactive installation on page 55 or Silent installation on page 56. Detailed information about the silent installation procedure is explained in the silent installation section.
Appendix D
155
156
Appendix
E
157 158 159 160 171 172 174 174 175 176 178 179 180 180 181
Configuring CONTROL-M/EM clusters

This appendix contains detailed information on how to configure clusters on CONTROL-M/EM. The following topics are discussed in this appendix: Setting up the CONTROL-M/EM UNIX cluster environment . . . . . . . . . . . . . . . . . . CONTROL-M Configuration Manager administration mode . . . . . . . . . . . . . . . Cluster administration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the CONTROL-M/EM client components on Windows . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up the CONTROL-M/EM Windows cluster environment . . . . . . . . . . . . . . Set up the host and listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cluster administration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create CONTROL-M/EM Gateway cluster resource . . . . . . . . . . . . . . . . . . . . . . Setting up failover nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/EM client components . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC Batch Impact Manager on clusters . . . . . . . . . . . . . . . . . . . . . . . . Installing CONTROL-M/Forecast on clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating BMC Batch Impact Manager and CONTROL-M/Forecast cluster resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
Appendix E
157
CONTROL-M Configuration Manager administration mode
NOTE
When defining the CONTROL-M/EM server components in the CONTROL-M Configuration Manager, use the virtual host name as the component name for the servers that use CORBA communication protocol. These components are the GUI Server, the CONTROL-M Configuration Server, the Global Alerts Server, BMC Batch Impact Manager, and CONTROLM/Forecast.
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 logical name support feature is enabled by setting the $BMC_HOST_INSTALL environment variable prior to starting the installation.
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. 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, define each of the CONTROLM/EM server components using the logical name assigned to BMC_EM_PROFILE_NAME.
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.
C For components that use CORBA, 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.
Cluster administration mode
For additional details, see Using CONTROL-M Configuration Manager administration mode on page 161.

When managing CONTROL-M/EM server components in cluster administration mode, CONTROL-M Configuration Manager and CONTROL-M/EM Configuration Agent are not used. Instead, the cluster software is used to start, stop, and monitor the CONTROL-M/EM server components. In this mode, the CONTROL-M/EM server components should be defined as resources, according to the commands described in Cluster administration mode on page 162.
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. 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.
3 Define the desired state of each of the CONTROL-M/EM server components to

ignored.
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, and a complete list of the processes names, see Monitoring CONTROLM/EM processes on page 164.
Appendix E
159
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.
2 During client installation, 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, use the virtual host name defined
in the $BMC_HOST_INSTALL environment variable (during client installation, this variable is set to the virtual network name designated for the CONTROLM/EM resource group) to connect to the CORBA Naming repository. The virtual host name should be entered in the Host Name field, which is displayed after clicking Advanced. This name is resolved by the network and should be identical to the name set in the environment variable.
4 The server name is automatically displayed once the connection to the CORBA
Naming service is established. This name represents the registered name of the CONTROL-M/EM Server component in the CORBA naming service repository. By default, the name is the physical host name of the computer. 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, define the server components in the CONTROL-M Configuration Manager using the virtual host name as the component name. This name differs from the machine name value, which should be the physical host name of the active node. When managing the CONTROL-M/EM Server components by cluster, start the server component that uses CORBA using the -name parameter, where the value of the parameter should be the virtual host name (as referred to in the example: vhem640).
For additional information and examples, see Configuring the policy file.
5 By default, CONTROL-M/EM client components are configured to reconnect to

the GUI Server upon disconnection. If the failover time of the resource group is longer than the reconnection retries, and timeout, change these parameters in the CONTROL-M/EM reconnection panel of the options menu.
160

Configure the policy file according to the instructions provided below for either the CONTROL-M Configuration Manager administration mode or the cluster administration mode.
Using CONTROL-M Configuration Manager administration mode

To start the CONTROL-M/EM components, enter the following commands.
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/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/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. This step is performed automatically if the $BMC_HOST_INSTALL environment variable is set prior to starting the installation.
To stop the CONTROL-M/EM components, enter the following commands.

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 - $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/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 - $EM_ACC -c "$EM_DIR/appl/ecs/bin.$PLATFORM/orbadmin ns stop -local" sleep 5
Appendix E
161
NOTE
Modify <platform> to the correct folder name according to the relevant platform vendor.
_co

To start the CONTROL-M/EM components, enter the following commands.
EM_ACC='em640' EM_VNAME='vhem640' CTM_VNAME='vhctm640' EM_DIR='/export1/em640' # 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/app1/bin/ecs cms -name $EMDB_VNAME # Start CONTROL-M EM GUI Server su - $EM_ACC -c "$EM_DIR/appl/bin/ecs guisrv -name $EM_VNAME" # Start CONTROL-M EM Global Alerts Server su - $EM_ACC -c "$EM_DIR/appl/bin/ecs gasrv -name $EM_VNAME" # Start CONTROL-M EM Global Conditions Server su - $EM_ACC -c "$EM_DIR/appl/bin/ecs gcsrv" # Start CONTROL-M EM Gateway su - $EM_ACC -c "$EM_DIR/appl/bin/ecs gtw -dc $CTM_VNAME"
162
To stop the CONTROL-M/EM components, enter the following commands.

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 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 GAS -name $EM_VNAME -cmd stop" sleep 3 # Stop CONTROL-M EM Global Conditions 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 - $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 - $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 - $EM_ACC -c "$EM_DIR/appl/ecs/bin.$PLATFORM/orbadmin ns stop -local" sleep 5
NOTE

Modify <platform> to the correct folder name according to the relevant platform vendor. Before defining the CONTROL-M/EM Gateway cluster resource, the CONTROLM/Server should be defined using the CONTROL-M Configuration Manager. Create a Gateway resource for each CONTROL-M/Server that is connected to CONTROL-M/EM. In the resource command line, indicate the CONTROL-M/Server name as a value to the -dc parameter.
Commands for starting the CONTROL-M Web Server:

# Start the CONTROL-M Web Server EM_ACC='em640' EM_DIR='/export1/em640' su - $EM_ACC -c "$EM_DIR/scripts/start_web_server.sh"
Appendix E
163
Commands for stopping the CONTROL-M Web Server:

# Stop the CONTROL-M Web Server EM_ACC='em640' EM_DIR='/export1/em640' su - $EM_ACC -c "$EM_DIR/scripts/stop_web_server.sh" sleep 3
Monitoring Oracle database processes

Oracle architecture (beginning with version 8.0.x) is built on the mandatory processes shown in Table 26, and one optional process, called listener. The cluster application should monitor all these processes and should switch the database application if any of them fails. Failover action decisions should be made together with the database administrator. Table 26 Oracle processes
Process name ora_smon_instanceName ora_pmon_instanceName
Oracle process System Monitor Process Monitor
The cluster should monitor both these processes and should switch the database package if either process fails. Failover decisions should be made together with the database administrator.
Monitoring CONTROL-M/EM processes

CONTROL-M/EM components can be monitored by the CONTROL-M/EM Configuration Agent or by the cluster. If the components are monitored by the cluster, use the process names for the cluster monitoring definitions as specified in Table 27. Table 27
GUI Server Global Alert Server (GAS) Gateway Global Condition Server (GCS) CONTROL-M/EM Configuration Agent
CONTROL-M/EM processes
Process name ecs.guisrv ecs.gasrv ecs.gtw -dc dcName ecs.gcsrv ecs.maintag
CONTROL-M/EM component
164
Table 27
CONTROL-M/EM processes
Process name Naming_Service -p ${HOME}/var/ns.pid -u ${HOME}/var ecs.bimsrv ecs.forecastserver ecs.batchdiscovery ecs.cms
CONTROL-M/EM component TAO Naming Service BMC Batch Impact Manager Server CONTROL-M/Forecast BMC Batch Discovery CONTROL-M Configuration Manager
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, after setting a virtual host name online, the physical host name of the cluster node becomes unavailable. In such case, additional configuration is required for the CONTROL-M/EM Configuration Agent. This configuration provides the ability to send life check communications to the CONTROL-M/EM Configuration Agent using the virtual host name. 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.
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).
2 In the CONTROL-M Configuration Manager, choose Tools => System Parameters.
Appendix E
165
3 In the general section, select the HostPort parameter and click New to open the Add
New Parameter dialog box.
4 In the Add New Parameter dialog box, click Advanced. 5 Modify the following field values:
Field Value General (the default value) HostPort (the default value)
Type Name Value
vhem640:0, which is specified in the format:

virtualHostName:port By specifying 0 (zero) as the port number, 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, the CONTROLM/EM Configuration Agent will use the specified port number.
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, a separate condition must be specified with the physical host names of each cluster node specified in the Host Name parameter.
6 Click Save. 7 Start the CONTROL-M/EM Configuration Agent. Global Condition Server
In some cases, after setting a virtual host name online, the physical host name of the cluster node becomes unavailable. In such case, additional configuration is required for the GCS. This configuration should only be used if the GCS failed to start after a failover.
166
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.
2 Ensure that the GCS is not running on any of the cluster nodes (ps -ef | grep gcs). 3 In the CONTROL-M Configuration Manager, choose Tools => System Parameters. 4 In the general section, select the HostPort parameter and click New to open the Add
New Parameter dialog box.
5 In the Add New Parameter dialog box, click Advanced. 6 Modify the following field values:
Field 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. Advanced field: Type Advanced field: Name Advanced field: Host GCS * (the default value) * (the default value)
Type Name Value
7 Click Save. 8 Start the GCS using the CONTROL-M Configuration Manager.
Manually reconfiguring TAO to use the Virtual Network name

To manually reconfigure TAO: 1 On the first node, hostcla, 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
167
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.
3 Set the JAVA_HOME environment variable to the JRE installation directory.

Ensure JRE version 1.5.x or later is used. For information on setting variables, see Setting environment variables in UNIX on page 37.
4 Set the DISPLAY environment parameter to terminalAddress:0 5 Activate the Domain Configuration wizard by running the orbconfigure java
utility.
6 Modify the published address to the virtual host name, enter the CONTROL-M/EM
virtual host name, 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), and then click Next.
Ensure that the port is available and is not used by other programs on any of the cluster nodes.
8 Set CONTROL-M/EM ports or leave default settings, and then click Next. 9 Ensure all relevant entries in the summary reports refer to the virtual host name,
and then click Finish.
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. 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.
1 Log in to the CONTROL-M/EM account on the active node. 2 Install BMC Batch Impact Manager according to the instructions provided in the
CONTROL-M Business Service Management Solutions User Guide.
168
3 The target installation folder should be on the folder in which CONTROL-M/EM

was installed on the shared disk.
4 Deploy the BMC Batch Impact Manager web application according to the
instructions provided in the CONTROL-M Business Service Management Solutions User Guide.
5 Follow the instructions below according to the method you use to manage
CONTROL-M/EM components:
For CONTROL-M Configuration Manager, 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, add the following commands to the policy file of CONTROL-M/EM: To start the BMC Batch Impact Manager Server component, 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 - $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 - $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
169
6 After starting the CONTROL-M/EM resource group and the BMC Batch Impact
Manager Web Application Server resources are up and running, open a web browser in Microsoft Windows and enter the following URL: http://virtualName:8080/bim
EXAMPLE
http://vhem640:8080/bim
7 Click Advanced. 8 Modify the following field values:

Field Value
Host
By default, the host name indicates the physical host name of the cluster node. Replace the default host name with the CONTROL-M/EM virtual host name.
9 Click Add Host. 10 Click Login to log on to BMC Batch Impact Manager.
Installing CONTROL-M/Forecast on clusters

This procedure is optional. It is intended only for customers who are licensed to use CONTROL-M/Forecast and have installed CONTROL-M/Forecast in the cluster environment.
1 Log into the CONTROL-M/EM account on the active node. 2 Install CONTROL-M/Forecast according to the instructions provided in the
3 The target installation folder should be on the folder in which CONTROL-M/EM

was installed on the shared disk.
4 Follow the instructions below according to the method you use to manage
CONTROL-M/EM components:
170
For CONTROL-M Configuration Manager, 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, add the following commands to the policy file of CONTROL-M/EM: To start the CONTROL-M/Forecast Server component, enter the following commands:
# Start CONTROL-M Forecast Server EM_ACC='em640' EM_VNAME='vhem640' EM_DIR='/export1/em640' su - $EM_ACC -c "$EM_DIR/appl/bin/ecs forecastserver -n $EM_VNAME -gsr=$EM_VNAME" &
To stop 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 - $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

You have now completed the installation of CONTROL-M/EM with clusters on UNIX using clusters.
Appendix E
171
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. Disk, IP, 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. Silent installation of CONTROL-M/EM is not supported for Microsoft Windows cluster environments.
The CONTROL-M/EM installation requires Disk, Network Name and IP Address virtual resources to be created before you begin. When you install CONTROL-M/EM to the same virtual server (resource group) as CONTROL-M/Server or MS-SQL Server, you do not need to manually create the Network Name and IP address cluster resources. They are automatically created by the CONTROL-M/Server or MS-SQL Server installation. When you install CONTROL-M/EM into a new resource group or a resource group that does not include Disk, Network Name and IP Address resources, use the following procedures to create these cluster resources and bring them online.
To create the IP Address resource 1 From the Cluster Administrator interface, select the relevant resource group. 2 Right-click an empty space in the group and choose New => Resource. 3 In the New Resource window, perform the following steps, and then click Next: A Enter the name that will be assigned to the IP address cluster resource (for
example, EM640 IP Address).
B Enter a description for the IP address cluster resource (for example, Virtual IP
Address).
C Select resource type IP Address. D Ensure that the selected group is the CONTROL-M/EM resource group (by
default, EM640).
172
4 In the Possible Owners window, ensure that all the nodes on which the
CONTROL-M/EM can be brought online are listed in the Possible owners column, and then click Next.
5 In the Dependencies window, click Next. 6 In the TCP/IP Address Parameters window, perform the following steps, and then
click Finish:
A Enter the CONTROL-M/EM virtual IP address. The Subnet mask field is

automatically set.
B Select Network type External. C Select the Enable NetBIOS for this address check box. To create the Network Name resource 1 From the Cluster Administrator interface, select the relevant resource group. 2 Right-click an empty space in the group and choose New => Resource. The New
Resource window is displayed.
3 In the New Resource window, perform the following steps, and then click Next: A Enter the name that will be assigned to the Network Name cluster resource (for
example, EM640 Network Name).
B Enter a description for the Network Name cluster resource (for example, EM640
Network Name).
C Select resource type Network Name. D Ensure that the selected group is the CONTROL-M/EM resource group (by
default, EM640).
4 In the Possible Owners window, ensure that all the nodes on which the
CONTROL-M/EM can be brought online are listed in the Possible owners column, and then click Next.
5 In the Dependencies screen, 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.
6 In the Network Name Parameters window, enter the name for the CONTROLM/EM virtual server, and then click Finish.
Appendix E
173
Set up the host and listener
To bring the resources online 1 From the Cluster Administrator interface, select the CONTROL-M/EM resource
group.
2 Right-click the group and choose Bring Online. 3 To ensure the network name and IP address are published in the network, ping the
CONTROL-M/EM virtual server, as defined in step 6 of the To create the Network Name resourcetask, from the command prompt.
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.ora and listener.ora. The files are located in the <oracleHome>\ora1010\network\admin folder.
2 Stop and then restart the listener service.

NOTE
When defining the CONTROL-M/EM server components in the CONTROL-M Configuration Manager, use the virtual host name as the component name for the servers that use CORBA communication protocol. These components are the GUI Server, the CONTROL-M Configuration Server, the Global Alerts Server, BMC Batch Impact Manager, and CONTROLM/Forecast.
When managing CONTROL-M/EM server components in cluster administration mode, CONTROL-M Configuration Manager and CONTROL-M/EM Configuration Agent are not used. Instead, the cluster software is used to start, stop, and monitor the CONTROL-M/EM server components. In this mode, the CONTROL-M/EM server components should be defined as resources, according to the commands described in Cluster administration mode on page 162.
174
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. 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.
3 Define the desired state of each of the CONTROL-M/EM server components to

ignored.
4 Define a cluster resource for the CONTROL-M/EM Configuration Agent, by

creating a new generic application resource using the details in Table 28. Table 28 Defining a cluster resource
CONTROL-M-EM-Configuration-Agent CONTROL-M/EM Configuration Agent (for monitoring purposes only) generic application EM640 <EM_ROOT>\bin\ecs_maintag.exe <EM_ROOT>\bin 10 Database resource Do not restart
Resource attribute Description Resource type Group Command line Current directory Pending timeout in seconds Dependencies Advanced
5 Set the resource to the online state.

For additional information about monitoring of the CONTROL-M/EM server components, and a complete list of the processes names, see Monitoring CONTROLM/EM processes on page 164.
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.
Appendix E
175
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. The Desired State parameter for the gateway must be set to ignored.
2 For each CONTROL-M/Server defined, define a cluster resource for each gateway
component. Create a new generic application resource using the details in Table 29. Table 29 CONTROL-M/EM Gateway resource definition
CONTROL-M-EM-Gateway (CTM/SRVName) CONTROL-M/EM Gateway generic application EM640 <EM_ROOT>\bin\ecs_gtw.exe -dc dcName <EM_ROOT>\bin 10 Database resource
Resource attribute Description Resource type Group Command line Current directory Pending timeout in seconds Dependencies
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.

On each failover node, 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.
2 Open a command prompt and navigate to the <rootFolder>\3rd folder on the

installation DVD or CD.
3 Ensure that the Disk, IP address, and Network Name resources are online on the
failover node.
4 Run Windows\3RD\setup.bat from the installation DVD
176
NOTE
The following step applies only for a PostgreSQL installation.
5 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:
A From the command line (Start -> Run), run Services.msc B Locate PostgreSQL for CONTROL-M/EM 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 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, enter a name for the this account service.
This name is the <name of user> you saved in step C
6 Restart the computer. 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.
B Verify that the disc on which you installed CONTROL-M/EM is accessible from
this node.
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.
Appendix E
177
Installing CONTROL-M/EM client components
Installing CONTROL-M/EM client components

When you install CONTROL-M/EM client components, use the virtual host name for the location of the CONTROL-M/EM. If the CONTROL-M/EM administration components (CONTROL-M Configuration Manager and Reporting facility) are installed as well, use the database virtual host name) when you install the database client. By default, CONTROL-M/EM client components are configured to reconnect to the GUI server upon disconnection. If the failover time of the resource group is longer than the reconnection retries and timeout, change these parameters in the options menu of the CONTROL-M/EM reconnection panel.
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.
2 During client installation, 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, use the virtual host name
configured by the installation to connect to the CORBA Naming repository. Enter the virtual host name in the Host Name field, which is displayed after clicking Advanced. This name is resolved by the network and must be identical to the name configured by the CONTROL-M/EM cluster aware installation.
4 By default, CONTROL-M/EM client components are configured to reconnect to

the GUI Server upon disconnection. 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, change the values for these parameters in the CONTROL-M/EM Reconnection panel of the Options menu.
5 If the CONTROL-M/EM installation, which is on the cluster machine, is

configured to function in a firewall environment and orbconfigure is activated, the following commands must be executed from the cluster machine command line to correctly configure the local CONTROL-M/EM client components.
orbadmin variable modify -scope GUI -value "iiop://" -ORBListenEndpoints orbadmin variable modify -scope Desktop -value "iiop://" -ORBListenEndpoint orbadmin variable modify -scope CLI -value "iiop://" -ORBListenEndpoints
178
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. For more information, see the section on configuring CONTROL-M/EM in a firewall environment in the CONTROL-M Administrator Guide.

This procedure is optional. 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. In a cluster environment, BMC Batch Impact Manager should be installed on the primary node only. For full information on installing BMC Batch Impact Manager, see the CONTROL-M Business Service Management Solutions User Guide.
To Configure the BMC Batch Impact Manager web application 1 Install BMC Batch Impact Manager according to the instructions provided in the
2 Install the web application server on the shared disk where the entire CONTROLM/EM installation was installed.
3 Deploy the BMC Batch Impact Manager web application according to the
instructions provided in the CONTROL-M Business Service Management Solutions User Guide.
4 Using the Cluster Administrator interface, create the web application server
resource in the CONTROL M/EM resource group.
5 Bring online the BMC Batch impact Manager and the web application server
cluster resources.
6 Open the web browser and enter the following URL:

http://virtualName:8080/bim
Appendix E
179
7 Click Advanced. 8 Modify the following field values:

Field Value
Host
By default, the host name indicates the physical host name of the cluster node. Replace the default host name with the CONTROL-M/EM virtual host name.
9 Click Add Host. 10 Click Login to log on to BMC Batch Impact Manager.

This procedure is optional. 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, CONTROL-M/Forecast should be installed on the primary node only. For full information on installing CONTROL-M/Forecast, see the CONTROL-M Business Service Management Solutions User Guide.
Updating BMC Batch Impact Manager and CONTROLM/Forecast cluster resources

If BMC Batch Impact Manager or CONTROL-M/Forecast were installed on a cluster, the cluster resource properties must be changed manually from do not restart to restart.
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.
2 Select the restart option button.
180

You have now completed the installation of CONTROL-M/EM with clusters on Windows using clusters.
Appendix E
181
182
Appendix
Configuring CONTROL-M/Server clusters

F
This appendix contains detailed information on how to configure clusters on CONTROL-M/Server. The following topics are discussed in this appendix: Setting up the CONTROL-M/Server UNIX cluster environment . . . . . . . . . . . . . . . 183 Setting the virtual host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Configuring the policy file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Monitoring CONTROL-M/Server processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Setting up the CONTROL-M/Server Windows cluster environment for PostgreSQL . 185 Setting up failover nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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, change the Local IP Host Interface Name to the virtual host name in ctm_menu.
A from ctm_menu select option 6 - Parameter Customization B select option 1 - Communication and Operational Parameters
Appendix F
183
These changes will set the OS_PRM_HOSTNAME parameter of the CONTROL-M/Server configuration file (${HOME}/ctm_server/data/config.dat), to the virtual host name as the parameter value. This change will not take effect until CONTROL-M/Server is restarted.

To start the CONTROL-M/Server, enter the following commands.
CTM_ACC=ctm640 CTM_DIR=/export2/ctm640 #Start CONTROL-M/Server Configuration Agent su - $CTM_ACC -c $CTM_DIR/ctm_server/scripts/start_ca #Start CONTROL-M/Server su - $CTM_ACC -c $CTM_DIR/ctm_server/scripts/start_ctm
To stop the CONTROL-M/Server, enter the following commands.

CTM_ACC=ctm640 CTM_DIR=/export2/ctm640 #Stop CONTROL-M/Server Configuration Agent su - $CTM_ACC -c $CTM_DIR/ctm_server/scripts/shut_ca #Stop CONTROL-M/Server su - $CTM_ACC -c $CTM_DIR/ctm_server/scripts/shut_ctm
NOTE
When CONTROL-M/Server is managed in a cluster, the cluster software starts, stops, and monitors CONTROL-M/Server actions. When used in a cluster, if the CONTROL-M/Server is defined on CONTROL-M Configuration Manager, the CONTROL-M/Server desired state defined on CONTROL-M Configuration Manager should be set to value ignore.
Monitoring CONTROL-M/Server processes

CONTROL-M/Server monitors its own processes internally. Failover of the CONTROL M/Server resource group is not required if only one process fails. The Supervisor process (SU) performs heartbeat monitoring of all other processes. If another process fails, SU will try several times to bring up the process. If these attempts are unsuccessful, SU will shut down CONTROL-M/Server. Therefore, it is sufficient if you only monitor the SU process (/export2/ctm640/ctm_server/exe_Solaris/p_ctmsu).
184
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.

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.

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
185
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.

You have now completed the installation of CONTROL-M/Server with clusters on UNIX.
186
Appendix
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.

You have now completed the installation of CONTROL-M/Agent with clusters.
188
Appendix
Checking and modifying UNIX parameters

H
This appendix describes how to check and modify CONTROL-M memory and kernel system parameters. The following topics are discussed in this appendix: Checking memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solaris 10 (for CONTROL-M/Server). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solaris 8, 9 (for CONTROL-M/EM and CONTROL-M/Server) . . . . . . . . . . . . . Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 190 190 191 193 194 195 196 198
Appendix H Checking and modifying UNIX parameters
189
Checking memory
Checking memory
The following table lists instructions for checking available memory on various UNIX platforms. Table 30
AIX
Checking available memory

How to check available RAM 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.
UNIX System
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.
Solaris Linux
prtconf -v |grep Memory free
Modifying system parameters

Several UNIX system (kernel) parameters must be altered before installing CONTROL-M.
All platforms
The parameters values shown in Table 31 must be added to the values specified for them in any of the other tables. If higher values for these parameters have already been specified for the database server, the higher values should remain.
190
HP-UX
Table 31
Parameter semmni
Kernel parameters for CONTROL-M/Server additional values

Additional values 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. For all platforms except Solaris 10, 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. For Solaris 9 (not Solaris 10), add 100 + 6 times the number agents connected to the server + the number utilities running simultaneously.
semmns
semmnu
Table 32
Parameter semmnu
Kernel parameters for CONTROL-M values for all platforms

Value (NPROC - 4)

Ulimit (for Embedded PostgreSQL)
fsize: unlimited nofiles: >1024
HP-UX
1 Log in as the root user. 2 Set the DISPLAY environment variable to <hostName>:0.0
For information on setting variables, see Setting environment variables in UNIX on page 37.
3 Type sam, select Kernel Configuration, and navigate to Configurable Parameters. 4 To change a parameter value: A Navigate to Modify Configurable Parameters in the Action Menu. B Enter the desired value in the Formula/Value field. If the default value is more
than required, do not change it. Table 33
Parameter semmni semmns
Kernel parameters for CONTROL-M HP-UX with Embedded PostgreSQL (Part 1 of 2)

Value 200 800
191
HP-UX
Table 33
Parameter shmmax shmmni shmseg
Kernel parameters for CONTROL-M HP-UX with Embedded PostgreSQL (Part 2 of 2)

Value 600000000 100 16
Table 34
Parameter
Kernel parameters for CONTROL-M HP-UX with Oracle (Part 1 of 2)

Value (NPROC*8) Eight times the value specified for the NPROC parameter. 1073741824 2147483648 134217728 bytes 1073741824 16384 512. This value is appropriate for a CONTROL-M installation with up to 50 CONTROL-M definitions, 80 concurrently open ViewPoints, and 30 concurrent users. Note: If your data center requires a larger configuration, contact BMC Software Customer Support for the correct value of this parameter. For more information about CONTROL-M definitions and ViewPoints, see the CONTROL-M User Guide. ((NPROC*9)/10) (MSGTQL+2) NPROC 32767 NPROC (NKTHREAD+16) ((8*NPROC+2048)+VX_NCSIZE) (15*NPROC+2048) 4096 (8*NPROC+2048) (((NPROC*7)/4)+16) 4096 (SEMMNI+2) 4096 (SEMMNI*2) (NPROC - 4) 32768
ksi_alloc_max maxdsiz maxdsiz_64bit maxssiz maxssiz_64bit maxswapchunks max_thread_proc
maxuprc msgmap msgmni msgseg msgtql ncallout ncsize nfile nflocks ninode nkthread nproc semmap semmni semmns semmnu semvmx
192
AIX
Table 34
Parameter shmmax
Kernel parameters for CONTROL-M HP-UX with Oracle (Part 2 of 2)

Value Half the amount of RAM (in bytes) on this computer. For information about determining the amount of RAM on your computer, see Checking memory on page 190. 1 512 32 64
shmmin shmmni shmseg vps_ceiling
Table 35
Parameter
Kernel parameters for CONTROL-M/EM HP-UX with Sybase

Value 512. This value is appropriate for a CONTROL-M installation with up to 50 CONTROL-M definitions, 80 concurrently open ViewPoints, and 30 concurrent users. Note: If your data center requires a larger configuration, contact BMC Software Customer Support for the correct value of this parameter. For more information about CONTROL-M definitions and ViewPoints, see the CONTROL-M User Guide.
max_thread_proc
Table 36
Parameter
Kernel parameters for CONTROL-M/Server HP-UX with Sybase

Value 1024.
max_thread_proc
AIX
Use the following steps to activate the RS/6000 Asynchronous I/O option:
1 Log in as the root user. 2 Set the DISPLAY environment variable to <hostName>:0.0
For information on setting variables, see Setting environment variables in UNIX on page 37.

smit aio
4 Select the Change/Show Characteristics of Asychronous I/O option.

Appendix H Checking and modifying UNIX parameters 193
Solaris 10 (for CONTROL-M/Server)
Enter the parameter values shown in Table 37. Table 37

Parameter Minimum number of servers Maximum number of servers Maximum number of requests I/O Server priority ASYNC I/O state to be configured at system start State of fast path
Asynchronous I/O parameters AIX

Value 1 10 4096 39 Available Enabled
NOTE
If your system uses more than seven hard disks for asynchronous I/O, the Maximum number of servers setting must be increased by one for every active device after the seventh.
5 Click OK and wait for the operation to complete. 6 Click Done. Control returns to the main Asynchronous I/O menu. 7 Select the Configure Defined Asynchronous I/O option. 8 Press <F12> to exit from smit. 9 Log out. 10 Exit the shell prompt. NOTE
If State to be configured at system start is Available, the AIX system need not be rebooted at the end of the procedure.
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). No other kernel parameters should be set for Solaris 10.
194
Solaris 8, 9 (for CONTROL-M/EM and CONTROL-M/Server)
Solaris 8, 9 (for CONTROL-M/EM and CONTROL-M/Server)

NOTE
This procedure has been verified on Solaris 9. For Solaris 10 platforms, see Solaris documentation regarding Resource Controls.
1 Log in as a root user. 2 Open the operating system configuration file /etc/system. 3 For each kernel parameter you wish to set, 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, add the following line to the /etc/system file: set shmsys:shminfo_shmseg=36
4 Restart the computer.

Table 38
Parameter semmni semmns semmsl shmmax shmmni
Kernel parameters Solaris with Embedded PostgreSQL

Value 200 800 100 600000000 100
Table 39
Parameter shmmax shmmin shmmni shmseg semmns
Kernel parameters Solaris with Oracle (Part 1 of 2)

Module name shmsys shmsys shmsys shmsys semsys Module abbreviation Minimum value shm shm shm shm sem 4294967295 1 100 10 Twice the total number of Oracle processes (minimum: 1024).
195
Linux
Table 39
Parameter semmni semmsl semopm semvmx
Kernel parameters Solaris with Oracle (Part 2 of 2)

Module name semsys semsys semsys semsys Module abbreviation Minimum value sem sem sem sem 100 260 100 32768
Table 40
Parameter shmmax
Kernel parameters Solaris with Sybase

Module name shmsys Module abbreviation Minimum value shm amount of available memory on this computer 10 32768
shmseg semvmx
shmsys semsys
shm sem
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. Instructions on how to display the current parameter values are shown in Table 43. Table 41
Parameter kernel.shmall kernel.shmmax kernel.shmmni semmni semmns semmsl
Kernel parameters Linux with Embedded PostgreSQL

Value 600000000 600000000 100 200 800 100
Table 42
Parameter semmsl semmns semopm semmni
Kernel parameters Linux with Oracle and Sybase (Part 1 of 2)

Value 250 32000 100 128
196
Linux
Table 42
Parameter semvmx shmall shmmax shmmni file-max
Kernel parameters Linux with Oracle and Sybase (Part 2 of 2)

Value default set by system 2097152 half the size of physical memory 4096 65536 32768 - 61000
ip_local_port_range
Table 43
Parameter
Displaying kernel parameter values Linux with Oracle and Sybase

Command to display the parameter values
semmsl, semmns, semopm, /sbin/sysctl -a | grep sem semmni shmall, shmmax, shmmni file-max ip_local_port_range /sbin/sysctl -a | grep shm /sbin/sysctl -a | grep file-max /sbin/sysctl -a | grep ip_local_port_range
Changing kernel parameter values

Using a text editor, add the following lines to the /etc/sysctl.conf file (you will need to create the file if it does not already exist): kernel.shmall = 2097152 kernel.shmmax = 2147483648 kernel.shmmni = 4096 kernel.sem = 250 32000 100 128 fs.file-max = 65536 net.ipv4.ip_local_port_range = 32768 61000
NOTE
kernel.sem assigns values to four semaphore parameters in the following order: semmsl, semmns, semopm, semmni. All four values must be specified.
The values specified in the /etc/sysctl.conf file take effect after the next reboot. Alternatively, you can issue the following command to have the values in the /etc/sysctl.conf file take effect immediately without rebooting: /sbin/sysctl -p
197

Return toUNIX requirements on page 35.
198
Appendix
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. The following topics are discussed in this appendix: Mounting media devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unmounting media devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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.
/<mediaDir> is the directory name of the mount point.
3 Apply the specific operating system commands for your specific platform (AIX
on page 200,HP-UX on page 200,Solaris on page 201,or Linux on page 201).
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
Unmounting media devices
The result should be 1.
5 Log out of the root account.
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. 2 Run ls -la /dev/cd*. 3 Verify that /dev/cd0 exists. 4 Run mount -rv cdrfs /dev/cd0 /<mediaDir>.
HP-UX
1 Display the IO devices on your computer by running the command:
/usr/sbin/ioscan -fnkC disk
2 In the resulting output, identify the line that describes the media. For example,
look for text similar to "HP DVD-ROM","TEAC" under the Description column. In some circumstances (for example if a USB device is used), you may need to consult your system administrator to identify the media device.
3 In the line that contains the media device, identify the path to the media device
under the Driver S/W State column (for example, /dev/dsk/c0t0d0, /dev/dsk/c1t2d0).
4 Run the mount command using the value identified in step 3.

Solaris
For example: # mount /dev/dsk/c0t0d0 /<mediaDir>.
Solaris
Check if the media device is already mounted by inserting the media, waiting approximately 15 seconds, and issuing the mount command. If the media is already mounted, it will appear on the resulting list. If the media device is not mounted, perform the following procedure:
1 Display the IO devices on your computer by running the command:

iostat -En
2 In the resulting output, identify the line that describes the media. For example,
look for text similar to "Vendor: TOSHIBA Product: DVD-ROM SD-C2612..." under the Description column. In some circumstances (for example if a USB device is used), you may need to consult your system administrator to identify the media device.
3 In the line that contains the media device, identify the path to the media device (for
example, /dev/dsk/c0t0d0, /dev/dsk/c1t2d0).
4 Run the mount command using the value identified in step 3.

For example: mount -F hsfs -o ro /dev/dsk/c0t0d0s2 /<mediaDir>.
Linux
Check if the media device is already mounted by inserting the media, waiting approximately 15 seconds, and issuing the mount command. If the media is already mounted, it will appear on the resulting list. If the media device is not mounted, enter the command: mount -t iso9660 -o ro /dev/cdrom /<mediaDir>

Return to the point you were at before jumping to the current appendix.
Appendix I Mounting DVDs and CDs on UNIX computers 201
202
Appendix
J
204 205 205 206 206 207 208 208
Uninstalling CONTROL-M and database servers

J
The following topics are discussed in this appendix: Uninstalling CONTROL-M/EM from UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/EM from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Server from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Server from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling a CONTROL-M Oracle database server from UNIX . . . . . . . . . . . . . . . Uninstalling a CONTROL-M Oracle database server from Windows. . . . . . . . . . . . Uninstalling CONTROL-M/Agent from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Agent from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . .
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. When CONTROL-M/EM is uninstalled, BMC Batch Impact Manager, CONTROLM/Forecast, 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, CONTROL-M/Forecast, and BMC Batch Discovery will not function unless they are (re)installed after the reinstalled version of CONTROL-M/EM. For more information see the CONTROL-M Business Service Management Solutions User Guide.
Appendix J Uninstalling CONTROL-M and database servers
203
Uninstalling CONTROL-M/EM from UNIX
NOTE
PostgreSQL is uninstalled automatically when CONTROL-M/EM is uninstalled from UNIX or Windows.
Uninstalling CONTROL-M/EM from UNIX

WARNING
On Oracle database servers, once CONTROL-M/EM is installed, it cannot be uninstalled and reinstalled in the same account without first uninstalling the CONTROL-M/EM database. 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.
1 Log on to the CONTROL-M/EM account. 2 Using the CONTROL-M Configuration Manager, stop all occurrences of the
following components:

GAS GCS GUI Server gateways
3 Run the root_menu script, select the Activation Menu, 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.sh
The uninstall procedure checks if any CONTROL-M/EM processes are active before beginning the uninstallation process, displays a message if it encounters any active processes, and then stops. All active processes must be stopped, and then the uninstall command must be run again.
204
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.
1 Use the CONTROL-M Configuration Manager to shut down all CONTROLM/EM components.
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. 4 Select CONTROL-M/Enterprise Manager from the Currently installed programs
list. If multiple instances are installed, each instance is listed separately in the Add/Remove Programs window.
5 Click Remove or Add/Remove to begin the uninstall procedure.
Uninstalling CONTROL-M/Server from UNIX

WARNING
On Oracle database servers, once CONTROL-M/Server is installed, it cannot be uninstalled and reinstalled in the same account without first uninstalling the CONTROL-M/Server database. 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.
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, see the
CONTROL-M Administrator Guide).
2 Log in to the CONTROL-M/Server account.
205
Uninstalling CONTROL-M/Server from Windows
3 Use the following command to run the uninstallation script:

$HOME/BMCINSTALL/uninstall/ctms_uninstall.sh
The uninstall procedure checks that no CONTROL-M/Server process is active before beginning the uninstallation process.
4 After CONTROL-M/Server has been uninstalled, you must delete its definition
from the CONTROL-M Configuration Manager.
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, see the
CONTROL-M Administrator Guide).
2 Use the CONTROL-M Configuration Manager to shut down CONTROLM/Server.
3 Select Start => Settings => Control Panel=> Add/Remove Programs. 4 Select CONTROL-M/Server from the "Currently installed programs" list. If
multiple instances are installed, each instance is listed separately in the Add/Remove Programs window.
5 Click Remove or Add/Remove to begin the uninstall procedure.
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, CONTROL-M/Server) before uninstalling.
206
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).
2 Log on to the CONTROL-M/EM account 3 Use the following command to run the uninstallation script
$HOME/BMCINSTALL/uninstall/uninstall_oracle.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, CONTROL-M/EM) before uninstalling.
1 CONTROL-M/EM must be uninstalled first before uninstalling the database

server (see Uninstalling CONTROL-M/EM from Windows).
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.
4 A CONTROL-M/EM database installed on an existing Oracle database server

(existing installation) is not removed with this program. Removal of the database needs to be done manually.
207
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. 2 Navigate to the CONTROL-M/Agent home directory. 3 Use the following command to run the uninstallation script:
$HOME/BMCINSTALL/uninstall/ctma_uninstall.sh [-silent]
If the -silent parameter is used, uninstall is performed immediately. If not, you are asked to confirm the your intention to uninstall. 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.cpl 3 Select the CONTROL-M/Agent you wish to uninstall and follow the instructions.
208
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.PARAMS file 121 57365 TableTitle Table 1 Installation checklist for CONTROLM/EM (continued) 31 architecture of CONTROL-M components 20, 24, 25, 26, 27, 28, 29, 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
A
administering server components 159, 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, 84, 93 AIX 193, 200 boot procedure 88 how to check available RAM 190 minimum requirements 36 setting asynchronous I/O 193
B
batch file 134 batch files 56 BMC Batch Impact Manager 168, 179 BMC Batch Impact Manager Server 167 starting and stopping 169 BMC Batch Impact Manager web application 179 BMC Software, contacting 2 boot procedure AIX 88 CONTROL-M/Server 87
C
character support, CJK 45 check_req.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, 174 cluster 172 BMC Batch Impact Manager 179 environments 157 Installing BMC Batch Impact Manager 168, 169 installing CONTROL-M/Forecast 170, 180 Oracle Real Application Cluster (RAC) 153 preparation 147, 157, 183, 187
Index
209
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, 157, 183, 187 cluster resources for UNIX 151 clustered database configuration 152 Commands 163 commands checking available memory 190 compatibility 40 compatibility information 35 compatibility information, 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, 24, 25, 26, 27, 28, 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, 184 CONTROL-M/Forecast 167 installing 170 installing on clusters 180 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. CTM/Agent parameter 93 conventions, 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 - Oracle 150 Database post-installation - 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
210
DB_SERVER_HOSTNAME parameter. CTM/Server for Windows 85 dba administrator group name for Oracle 39 dedicated CONTROL-M database 148 dedicated installation 54 Oracle 112, 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, 86 Dual IP addresses 79, 86 dump size limit parameter 40
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, 52 Silent for Oracle on Windows 134 silent on Windows 56 installation log Oracle 126 Installation parameters 144 installation parameters. See parameters installation requirements 35 INSTALLDIR parameter CTM/Agent silent installation 99 installing Administrator privileges 40 BMC Batch Impact Manager on clusters 168, 179 CONTROL-M/EM client components 63, 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, 180 CONTROL-M/Server componenets 49 database server 114 Oracle database on UNIX 112, 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, version required 41 IP dual addresses 79, 86 IP address 172
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, online 15 host names CORBA 59 Oracle parameter 137 Oracle server 125 Sybase 62 HostPort system parameter 165, 167 HP-UX 191, 200 how to check available RAM 190 minimum requirements 36
Index
211
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, 201 hardware requirement 36 LISTENER port number 125 listener process 164 Load balancing dual IP addresses 79, 86 local database configuration 154 Local IP Host Interface Name CTM/Server for Windows 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.log for Oracle 126 LOG_PHYSICAL_DEVICE_FULLPATH_FILE_NAME parameter. CTM/Server for Windows 86 lsattr command 190
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, 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
M
max_thread_proc parameter
212
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 for Oracle installation 123 Oracle installation parameters 136 Oracle on UNIX 123126 Oracle on Windows 136139 Windows and UNIX 5862, 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, 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, for installer 40 product support 2 protocol version. after agent upgrade 89 prtconf command 190 publications, related 16
O
online Help 15 operating system requirements 38 operating systems requirements. 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, 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.txt file 139 orapostinst.sh script 127
R
RAC (Real Application Cluster, Oracle) 153 raw partitions preparing for installation 114 recording port usage 80 Redo Log files parameter 138 redo log, file size 123 regional settings 42, 45 related publications 16 remote database configuration 152, 154 removing the test data 108 requirements AIX 36 HP-UX 36 installation resources 35 Linux 36
P
Parameter file 51 parameter file, 10103_Install_def.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
Index
213
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 HP-UX with Oracle 192, 193 Solaris with Oracle 195 Solaris with Sybase 196 Silent installation 51, 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, 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, customer 2 Sybase 65, 141 configuration 34 syntax statement conventions 17 System account parameter for Oracle 125 System Component parameter for Oracle 138 system requirements. See requirements
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, 191, 192 Solaris with Oracle 196 semmns parameter HP-UX with Oracle 43, 191, 192 Solaris with Oracle 195 semmnu parameter HP-UX with Oracle 191, 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, 193, 195 Solaris with Oracle 195 Solaris with Sybase 196 shmmin parameter HP-UX with Oracle 192, 193, 195 Solaris with Oracle 195 shmmni parameter HP-UX with Oracle 193 Solaris with Oracle 195 shmseg parameter
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.log file 126 TRACKER_EVENT_PORT. CTM/Agent for Windows 100 troubleshooting 165
U
uninstall_oracle.sh script 207 uninstalling CONTROL-M Oracle server from UNIX 206
214
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, 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. See Microsoft Windows windows.xml file 70 WINNTSystem32 folder, PATH environment variable 42
Index
215
216
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, Inc., License Agreement that is applicable to the product.
JiBX License
Copyright (c) 2003-2005, Dennis M. Sosnoski All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 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. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
PuTTY License
PuTTY is copyright 1997-2005 Simon Tatham. Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry, Justin Bradford, Ben Harris, Malcolm Smith, and CORE SDI S.A. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, 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. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SIMON TATHAM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Thai Open Source License

Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, 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. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Notes
*93988* *93988* *93988* *93988*

*93988*

93988

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

93988

Transféré par

Droits d'auteur :

Formats disponibles

CONTROL-M Installation Guide

Contacting BMC Software

United States and Canada

Outside United States and Canada

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC

License key and password information

CONTROL-M Installation Guide

CONTROL-M Installation Guide

Post installation for CONTROL-M/Agent

CONTROL-M Installation Guide

CONTROL-M Installation Guide

CONTROL-M Installation Guide

About this book

About this book

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

CONTROL-M Installation Guide

{commit | cancel} {-commit | -cancel} (UNIX) columnName . . .

About this book

CONTROL-M Installation Guide

Introducing the CONTROL-M solution

Introducing the CONTROL-M solution

CONTROL-M scheduling solution for distributed systems

CONTROL-M Installation Guide

CONTROL-M/Agents and remote hosts

Introducing the CONTROL-M solution

CONTROL-M Control Modules

CONTROL-M Control Modules

CONTROL-M Installation Guide

Planning the CONTROL-M solution

Using the CONTROL-M installation roadmap

Chapter 2 Planning the CONTROL-M solution

Using the CONTROL-M installation roadmap

Full CONTROL-M installation roadmap

CONTROL-M Installation Guide

Using the CONTROL-M installation roadmap

CONTROL-M/EM installation on UNIX

Chapter 2 Planning the CONTROL-M solution

Using the CONTROL-M installation roadmap

CONTROL-M/EM installation on UNIX continued

page 55 page 131

CONTROL-M Installation Guide

Using the CONTROL-M installation roadmap

CONTROL-M/EM installation on Windows

Chapter 2 Planning the CONTROL-M solution

Using the CONTROL-M installation roadmap

CONTROL-M/EM installation on Windows continued

CONTROL-M Installation Guide

Using the CONTROL-M installation roadmap

CONTROL-M/Server installation on UNIX

Chapter 2 Planning the CONTROL-M solution

Using the CONTROL-M installation roadmap

CONTROL-M/Server installation on Windows

CONTROL-M Installation Guide

Using the Installation checklist

Using the Installation checklist

Check Step Task

Install the product

Chapter 3, Chapter 5, Chapter 7

Chapter 2 Planning the CONTROL-M solution