Component installation cheat sheet for Linux and Oracle environments

This cheat sheet topic provides a list of the steps required to install BMC Server Automation components in a Linux/Oracle environment. Note that cheat sheet topics are targeted to experienced BMC Server Automation users, and do not include relevant planning and prerequisite information. If you are not an experienced user, see the topics in the Preparing-for-installation section to review the required planning information for installation.

This topic includes the following sections:

• Configure the Oracle database instance
• Run the script for creating an Oracle user
• Run the schema creation script
• Install the agent on the file server
• Related topics
• Install the Application Server
• Run the post-install configuration utility
• Connect to the Application Server
• Related topic

Configure the Oracle database instance

To configure the Oracle database for BMC Server Automation, do the following:

• Edit the init.ora file to set the following initialization parameters:
  • db_block_size must be set to 8192
  • Processes must be set to at least 200
    Ideally, the number of processes should be 30 to 40 greater than the total number of job-related and nonjob-related database connections configured for all Application Servers in your environment.
    If you are running BMC BladeLogic Decision Support for Server Automation, the number of processes should ideally be 20 to 30 higher than the total number of job-related and nonjob-related database connections.
    For more information about configuring Application Servers, see Configuring-the-Application-Server.
    All other configuration parameters can be set at the discretion of the database administrator.
• If the database is configured for the UTF8 or AL32UTF8 character set (NLS_CHARACTERSET parameter) in a LATIN-1 locale, and the CHAR schema is used as an underlying persistent schema, set the NLS_LENGTH_SEMANTICS parameter of the database to CHAR to prevent column field overflow. Set this parameter before you run the master schema script to set up the database schema.
• Ensure that all synonyms are public.

_{Back to top}

Run the script for creating an Oracle user

1. Create the directory to be used for the tablespace for the new schema.
   BMC recommends creating a directory on a disk separate from the Oracle system tables located at .../oradata/<SID>. 
2. Copy installation scripts from the db_scripts directory into the directory that you created for the tablespace. For details on the db_scripts directory, see Downloading-the-installation-files. The relevant scripts appear in the /db_scripts/oracle/ and /db_scripts/oracle/schema directories. 
3. Change (cd) to /db_scripts/oracle/schema.

4. (Optional) If required by your company policy, you can modify the create_oracle_instance.sql script to revoke the RESOURCE and UNLIMITED TABLE SPACE privileges, and replace them with more granular privileges.

   • EXECUTE ON DBMS_LOCK (required for carrying out a handshake between BMC Server Automation database and the BMC BladeLogic Decision Support for Server Automation ETL during database clean up.)
   • CONNECT
   • CREATE VIEW
   • RESOURCE 

   Click here if your company policy does not allow you to grant the RESOURCE privilege to BLADELOGIC.

   If your company policy does not allow you to grant the RESOURCE privilege to BLADELOGIC, revoke the RESOURCE privilege and provide the following granular privileges instead:

   • CREATE TRIGGER
   • CREATE SEQUENCE
   • CREATE TYPE
   • CREATE PROCEDURE
   • CREATE CLUSTER
   • CREATE OPERATOR
   • CREATE INDEXTYPE
   • CREATE TABLE

   • SELECT ANY DICTIONARY
   • UNLIMITED TABLESPACE

   Click here if your company policy does not allow you to grant the UNLIMITED TABLESPACE privilege to BLADELOGIC.

   If your company policy does not allow you to grant the UNLIMITED TABLESPACE privilege to BLADELOGIC, revoke the UNLIMITED TABLESPACE privilege and provide the following granular privilege on the relevant tabelspaces (BLADELOGIC and BLADELOGIC_INDEX) instead:
   Grant UNLIMITED QUOTA on <tablespace>

5. Modify the create_oracle_instance.sql script and change the path for data files to match the directory you created for the tablespace for the new schema.

   Note: Be sure to change both the CREATE TABLESPACE and ALTER DATABASE commands. You must change the path in four places.

6. Start SQL*Plus using a user name that has sysdba privileges. For example, you might enter the following commands:

   sqlplus /nolog
   SQL> connect sys/manager as sysdba

7. Run the create_oracle_instance.sql script by using the following commands:

   SQL> @create_oracle_instance.sql
   SQL> exit

_{Back to top}

Run the schema creation script

1. Change (cd) to /db_scripts/oracle.

2. Log on to the BMC Server Automation database by using the following command: sqlplus <bl_user>/<bl_pwd>@<bl_tns_entry>Replace the variables with the following values:
   

   Variable	Value
   <bl_user>	Logon name of the BMC Server Automation database user that you created inTo set up an Oracle database user
   <bl_pwd>	BMC Server Automation database user password. Do not specify a password that begins with an equal sign (=).
   <bl_tns_entry>	tns entry for the BMC BladeLogic database instance

   
   

3. Start a log and run the master script that corresponds to the character sets for which your database is configured.
   

   SQL> spool create_bladelogic_schema.log
   SQL> start <master_script.sql> <BL_DATA> <BL_INDEX>
   SQL> spool off

   Replace the variables with the following values:
   

   Variable	Value
   <master_script.sql>	oracle_master.sql if your database is configured for char/varchar character sets or oracle_nchar_master.sql if your database is configured for nchar/nvarchar character sets
   <BL_DATA>	BMC Server Automation data tablespace name. This name must match the data tablespace name in the create_oracle_instance.sql script (by default, BLADELOGIC).
   <BL_INDEX>	BMC Server Automation index tablespace name. This name must match the index tablespace name in the create_oracle_instance.sql script (by default, BLADELOGIC_INDEX).

4. After executing the master script, check the create_bladelogic_schema.log file for errors.

_{Back to top}

Install the agent on the file server

BMC Server Automation uses the file server to store the contents of files included in snapshots, Network Shell scripts, BLPackages, software packages, and other types of information that is not easily stored in the database. The file server must have a RSCD agent installed on it, as described in the following procedure.

1.  Navigate to the directory containing installation files and run the installation script for the RSCD agent. Script names follow the convention: RSCDversion-platform. For a list of all the different agent installation files for the various platforms, see Installation-programs-for-BMC-Server-Automation.
   You must execute the installation from a root shell. Do not execute the installation script from a non-root account.
2. The following message is displayed:
   Please choose the installation directory. [/opt/bmc/bladelogic]
3. To install the RSCD agent in /opt/bmc/bladelogic, press Enter. Or enter another directory path.
    A message prompts you to choose a language for the installation program.
4. Enter the number representing the language that you want to use for the installation.
    A welcome message is displayed.
5. Press Enter.
    The following message is displayed:
    Do you agree to the terms of the license agreement (y for Yes) ?

6. Press y.
   The following message is displayed:

   ============== Select Installation Components =============
   Server Utilities
   1 - RSCD Agent
   9 - Start the installation
   A - Select all components
   Select component
7. Enter 1.
    A plus sign (+) appears next to the RSCD Agent to indicate you have chosen to install it.
8. Enter 9.
    A message is displayed, asking you if you want to continue.
9. Enter y.

10. Follow the instructions in the installation script.
    Installation is complete. The agent starts automatically.

    Note

    If you have enabled Security-Enhanced Linux (SELinux), during the agent installation you are prompted to allow the installer to alter settings for SELinux. These setting changes modify the security settings to allow assets to be deployed successfully. If you do not allow the installer to alter SELinux settings, or you enable SELinux after the agent installation, you must disable SELinux or run the following commands to allow assets to be deployed successfully:

    setsebool -P allow_execstack=1
    setsebool -P allow_execmod=1

    For additional information on restricting access to RSCD agents, see How BMC Server Automation grants access to RSCD agents.

_{Back to top}

Install the Application Server

In a UNIX environment, if the Application Server and the File Server are on the same box, use only the Application Server installer, not the separate RSCD agent installer for the file server.

1. Navigate to the directory containing installation files and run the installation script for BMC Server Automation. (Script names follow the convention: BBSAversion-platform.) BMC recommends that you execute the installation from a root shell. Do not execute the installation script from a non-root account.

2. Follow the instructions in the installation script.

   Note

   • To avoid permission issues with bladmin, do not install a local installation beneath the root home directory.
   • If you are setting up VMware ESX servers, you must define certain properties that allow the Application Server to communicate with a web service which accesses the ESX server's virtual infrastructure. For more information on configuring an ESX server, see Setting-up-a-VMware-vSphere-environment.

   • If you have enabled Security-Enhanced Linux (SELinux), during the agent installation you are prompted to allow the installer to alter settings for SELinux. These setting changes modify the security settings to allow assets to be deployed successfully. If you do not allow the installer to alter SELinux settings, or you enable SELinux after the agent installation, you must disable SELinux or run the following commands to allow assets to be deployed successfully:

     setsebool -P allow_execstack=1
     setsebool -P allow_execmod=1

_{Back to top}

Run the post-install configuration utility

The Post-Install Configuration wizard consolidates the minimum configuration steps that must be performed to set up an Application Server. 

1. To start the Post-Install Configuration wizard, do one of the following:
   • Perform an installation that includes installation of the Application Server. The installation program gives you the option of launching the wizard at the end of the installation procedure.
   • From the Windows Start menu, select Programs > BMC Software > BladeLogic Server Automation Suite > Utilities > Application Server Configuration Wizard.
   • Start the wizard manually by running one of the following commands in the directory where BMC Server Automation is installed. Enter the following:

     • (Windows)

       bin\blappconf.exe

     • (UNIX)

       ./br/blappconf

       Note

       If you invoke the wizard without passing the -install flag, the wizard displays configuration settings that have already been entered for the Application Server and allow you to change those settings.

       The configuration wizard opens.

2. Read the introductory page and click Next. The Database page appears.
3. Choose a Database Type (either Oracle or SQL Server).
4. If you are not using a custom connection string, provide the following database configuration information (and do not select the Advancedoption):
   • Database Server — Host name or IP address (IPv4 or IPv6) of the server running the database.

   • Database Port— Port the database listens on. By default a BMC Server Automation installation uses the following database ports:
   • Database Name — Microsoft SQL server database name. By default, the database name is bladelogic . (This option is only available for SQL server databases.)
   • SID — System ID of the Oracle database. (This option is only available for Oracle databases.)
   • User ID — User name that the database needs to authenticate your connection.
   • Password — Password assigned to the user ID.
     or...
      If you are using a custom connection string, provide the following database configuration information:
   • User ID — User name that the database needs to authenticate your connection.
   • Password — Password assigned to the user ID.
   • Advanced — Select this option to indicate that you are providing a custom connection string.
   • Connection String — Type the custom connection string in the field below the Advanced check box.
5. Click Next. The File Server page appears.
6. Provide the following file server configuration information:
   • File Server Name — Host name or IP address (IPv4 or IPv6) of the server where data is stored. By default, the file server is created on the same machine as the Application Server.
   • File Server Storage Location — Directory on the file server where data is stored. By default, the directory of the file server is <appserverInstallDirectory>/storage.
7. Click Next. The Notification Servers page appears.
8. Provide information identifying an email server by entering the following under SMTP Options:
   • SMTP Server — Name or IP address (IPv4 or IPv6) of the host managing email. (SMTP stands for simple mail transfer protocol.)
   • E-mail From — email address from which BMC Server Automation-generated email is sent. BMC Server Automation jobs can generate email upon their completion.
9. If you are using SNMP trap notifications, provide information identifying the SNMP server by entering the following under SNMP Options:
   • SNMP Server — Name or IP address (IPv4 or IPv6) of the host to which SNMP traps should be sent.
   • SNMP Port — The port on the SNMP server that listens for SNMP traps. By default, the port is set to the standard SNMP port of 162.
10. Click Next. The User Passwords page appears.
11. Under both RBACAdmin User and BLAdmin User, enter a password and then retype the password to confirm your entry. If a password is already set, you cannot enter a password.
     Passwords are used to authenticate the RBACAdmin and BLAdmin users through the SRP authentication protocol.
     The RBACAdmin user has full permission to manage roles and users in the RBAC Manager workspace in the BMC Server Automation Console, where you can assign permissions for all BMC Server Automation users. The BLAdmin user has Read access for all system objects within BMC Server Automation. For more information about the RBACAdmin and BLAdmin users, see RBACAdmin-and-BLAdmin-users.
12. Click Finish.

_{Back to top}

 Install the console on your client system

_{Back to top}

Connect to the Application Server

From the directory where BMC Server Automation is installed (for example, /opt/bmc/BladeLogic/CM), enter ./rcp/launcher.sh.

1. Using the Authentication profile tab, select an authentication profile.
2. If you:
   • Possess a valid cached session credential, skip this step and go to the next step.
   • Are using Active Directory/Kerberos (ADK) or public key infrastructure (PKI) authentication, skip this step and go to the next step.
   • Are using SRP, LDAP, or SecurID authentication, enter your user name and password. For SecurID, your password consists of a PIN followed by the current token code displayed on your RSA SecurID token.
   • Are using Domain Authentication, enter your user name and domain. The domain name must always be capitalized. If you are defined as a member of the default realm, you do not have to enter a domain name. For information about how to set up the default realm for Domain Authentication, see Configuring-Domain-Authentication.

3. To change the setting for caching session credentials or the display language, click Options. The logon window expands to show additional options in a tabbed format. By default the Generaltab is open.

   Save credential for this session	Saves a session credential between sessions. By default, this option is not checked. The setting for this option remains in effect for future logons until you change the setting. If a session credential is already cached, this option is dimmed.
   Language	Displays your choice of language (either your previous choice or your acceptance of the installation default). Select a new display language for the console or keep the current user preference. The selection remains in effect as your default language for future logons until you make a new choice.

4. Click Connect.
   If the Application Server presents the BMC Server Automation Console with an X.509 certificate that is not trusted, a security alert appears. Most Application Servers use self-signed certificates, so typically you encounter this dialog box the first time you access a particular Application Server.
5. If a security alert does not display, skip this step and go to the next step. If a security alert describes an untrusted certificate, do one of the following:
   • To return to the logon dialog box, click No. You can cancel the logon session or use a different authentication profile to log on.
   • To accept the unknown certificate and proceed with the logon, click Yes.
   • To examine details about the certificate, click View Certificate. For more information about this procedure, see Viewing-an-untrusted-certificate. After examining the certificate, click Yes or No, as described above.
6. If multiple roles are associated with your user name, the Assume Role dialog box appears. From this dialog box, for Select Role, choose the role you want to use. 
   If you prefer, you can switch roles later at any time during a session. (See Switching-roles.)

7. Click OK. The BMC Server Automation Console appears.

   Note

   When the console starts, by default it loads certain types of information by running a background operation. The Show background operations icon in the lower right corner of the console indicates a background process is running. For information about background processes, see Running-background-operations.

_{Back to top}

Related topic

Component-installation-cheat-sheet-for-Microsoft-Windows-and-SQL-Server-environments