Setting up the Default Application Server node

This topic provides instructions for installing the Default Application Server node through an interactive installation wizard. This topic includes the following sections:

• • About the unified product installer
  • Before you begin
  • To install the Default Application Server Node
  • Where to go from here

About the unified product installer

The unified product installer guides you though the configuration and installation of the following components in the Default Application Server node:

• Application Server
• Database (Oracle Server for Linux or Microsoft SQL Server for Windows)
• File server
• BMC Server Automation Console
• RSCD agent
• BLCLI
• Network Shell
• PXE Server
• TFTP Server

In addition, the unified product installer installs Compliance Content add-ons, which provide you with out-of-the-box component templates for compliance with regulatory standards and best-practice policies.

Before you begin

Ensure that your environment meets the requirements discussed in Requirements-for-installing-on-Microsoft-Windows and Requirements-for-installing-on-UNIX-and-Linux.

To install the Default Application Server Node

1. Download and extract the installation package appropriate for the operating system level and hardware platform in a temporary directory. The package follows the naming convention BBSA<version>-<platform>.zip, and contains the unified product installation program files.
2. Extract the RSCDAgent.zip file and copy the rscd folder to one of the following locations before running the unified product installer (The unified product installer uses the RSCD installers while installing or upgrading BMC Server Automation in your environment):
   • (Windows) <temporary location>/files/installer/
   • (Linux):  
     • For version 8.6.00 or 8.6.00.001:  <temporary location>/files/installers
     • For version 8.6.01 and later:  <temporary location>/Disk1/files

3. If you are on a Linux machine, assign executable permission to the temporary directory by entering the following command:

   chmod +x -R <temporary directory> 

   In addition, if the temporary directory is at the end of a path (that is, has at least one parent directory), assign read permission to the others class for all directories in the path. To do this, execute the following command on the top-level directory in the path:

   chmod o+r -R <top-level directory>

4. Navigate to the temporary directory and run the installation file for BMC Server Automation (setup.exe for Windows or setup.bin for Linux).

   Note

   For Linux, BMC recommends that you execute the installation as a root user. Do not execute the installation file from a non-root account.

   By default, the database created during installation uses the CHAR (CHARACTER) data type, which is based on the ASCII character set. If you prefer to have string data stored using the NCHAR (NATIONAL CHARACTER) data type, which is based on the Unicode character set and UTF8 encoding, run the installation file with the following option: -J NLS_CHAR_SET=NCHAR. The option for choosing the character data type is not yet available on the Database page in the installation wizard.

   Follow the instructions in the installation wizard and click Next until the Database page appears. Enter the following database configuration information:

   Field Name	Description
   Host Name or IP Address	Host name or IPv4 address of the server running the database. Note that if your server is on an IPv6 address system you can only enter the host name of the server.
   Port	Port that the database listens on. The default port is 1521 for Oracle Database and 1433 for SQL Database.
   Database Name	Name of the database instance
   User Name	User name that the database needs to authenticate your connection
   User Password	Password assigned to the user ID
   Advanced	Select this option to indicate that you are providing a custom connection string. Type the database connection string in the field adjacent to the Advanced check box. Examples of connections string are as follows:   Connection string for an Oracle database server: jdbc:oracle:thin:@<DBSERVER>:<PORT>:<SID> <DBSERVER> is the name or IP address of the database server <PORT> is the port used to communicate with the database <SID> is the database ID used to identify the Oracle database Connection string for a SQL database server: jdbc:sqlserver://<DBSERVER>:<PORT>;DatabaseName=<DBNAME>;SelectMethod=cursor <DBSERVER> is the name or IP address of the database server <PORT> is the port used to communicate with the database <DBNAME> is the database name used to identify the SQL database

   Note

   If your default Application Server node is running Windows, you can only connect it to a Microsoft SQL database server. Similarly, if your default Application Server node is running Linux, you can only connect it to an Oracle database server.

   In case of Linux, you can use the Oracle Express database edition shipped with BMC Server Automation, for testing purposes, in the evaluation period. However, you must upgrade to Oracle Enterprise edition, after the evaluation period is over. Note that 123456 is the default password set for the sys as sysdba user in Oracle XE, BMC recommends that you change the default password after installation for security reasons.

5. Click Next. A summary of the database parameters, default installation location, and file server parameters is displayed.

   Click Update Configuration to customize the following parameters:

   Field Name	Description
   Installation Directory
   Destination Directory	Directory where BMC Server Automation is installed. The default path is /opt/bmc/bladelogic for Linux and C:\Program Files\BMC Software\BladeLogic\ for Windows.
   File Server information
   Install file server on a separate host	Select this option if you do not want to use the local machine as your file server. Ensure that you have reviewed the requirements for installing a separate file server, in Requirements-for-installing-on-Microsoft-Windows and Requirements-for-installing-on-UNIX-and-Linux.
   Host Name/IP Address	Host name or IPv4 address of the file server. Note that if your server is on an IPv6 address system, you enter only the host name of the server.
   Repository Path	Directory on the file server where data is stored.
   RSCD Agent is already installed on specified separate file server machine as per documentation	Select this option if an RSCD Agent has been installed on a separate file server host computer. For information about manually installing the RSCD Agent on the separate file server, see Installing-an-RSCD-agent-Windows or Installing-only-the-RSCD-agent-Linux-and-UNIX. Note: To install a Linux file server with a Windows default Application server, click here.
   If you are installing the file server on a separate machine
   File Server OS	Select the operating system running on the file server host computer.
   If you are installing the file server on a Windows machine
   File server administrator user name	User name with administrator permissions
   File server administrator password	Password of the user with administrator permissions
   Confirm File server administrator password	Confirm the password of the user with administrator permissions
   If you are installing the file server on a Linux machine
   File server super-user name	User name with superuser permissions
   File server super-user password	Password of the user with superuser permissions
   Confirm File server super-user password	Confirm the password of the user with superuser permissions
   Ports
   Application Server Base Port	Application Server ports are normally configured from a base port, with 9800 being the default base port. Arbitrary port assignments can be made in all cases. For more information, see Application Server ports.
   Passwords
   Certificate Password	The BMC Server Automation Application Server installation program needs a certificate password to generate a self-signed X.509 certificate. Note: Communication between BMC Server Automation and servers being provisioned between the Application Server and the process spawner uses the Transport Layer Security (TLS) protocol and X.509 certificates. The password must be at least 6 characters. For more information about certificates and the TLS protocol, see Authentication.  The default password is password. BMC Server Automation does not recommend using the default password, so you can specify a different password in this field.
   BLAdmin Password	BMC Server Automation creates a built-in user called BLAdmin during the installation process. The BLAdmin user is only assigned the BLAdmins role. To activate the default user, it must be assigned a password and granted access to servers in your network. You can use the RBAC Manager folder to perform these actions, but to start the console the first time, you must define a password for the BLAdmin user. For more information, see RBACAdmin-and-BLAdmin-users. The default password is password. BMC Server Automation does not recommend using the default password, so you can specify a different password in this field.
   RBAC Admin Password	BMC Server Automation creates a built-in user called RBACAdmin during the installation process. The RBACAdmin user is only assigned the RBACAdmins role. To activate the default user, it must be assigned a password and granted access to servers in your network. You can use the RBAC Manager folder to perform these actions, but to start the console the first time, you must define a password for the RBACAdmin user. For more information, see RBACAdmin-and-BLAdmin-users. The default password is password. BMC Server Automation does not recommend using the default password, so you can specify a different password in this field.    .
   Agent Mapping
   Agent mapping local super user	The name of the local super user — root or root-equivalent user on Linux, local Administrator or Administrator-equivalent local user on Windows — to which the RSCD Agent should map incoming connections during the installation. The default is root on Linux and Administrator on Windows.

6. Click Next.The unified product installer installs the Default Application Server node on your machine.

   Note

   The installation log file, bsainstallupgrade.log, is stored in %TEMP% (on Windows) or in /tmp (on Linux). For more information about the log files created by the unified product installer, see the Troubleshooting section.

Where to go from here

After completing the setup of the default Application Server node, you might need to perform the following tasks:

• Resetting user passwords:
  If you did not specify new passwords for the BLAdmin and RBACAdmin users during the installation, consider changing their passwords now, so that they do not continue to use the out-of-box default passwords. For information about performing this task, see Resetting-RBAC-users-passwords.
• Resetting security settings:
  During installation, default security settings are applied to the Application Server and file server. BMC recommends that you adjust the security level on the Application Server host computer and the file server host computer after completing the installation. For more information, see the Security requirements section in the Requirements-for-installing-on-Microsoft-Windows  and Requirements-for-installing-on-UNIX-and-Linux topics.

• Installing and upgrading RSCD agent

  (For BMC Server Automation 8.6 SP1 and later) The unified product installer automatically installs agent installer jobs and depot objects such as agent installers and agent bundles that can be used for installing or upgrading agents on servers in the environment. The agent installers, agent bundles, and agent installer jobs are present in the following locations:

  Object	Depot Path	Can be used for
  Installers	/Depot/BMC Maintenance/Agent Installers/	Agent install and upgrade
  Bundles	/Depot/BMC Maintenance/Agent Bundles/	Agent upgrade
  Jobs	/BMC Maintenance/Agent Installer Jobs/	Agent upgrade

  For more information about using these objects, see Installing one or more agents using the BMC Server Automation Console and Upgrading-RSCD-agents.

  Warning

  Modifying the name or path of these depot objects may cause errors in the agent installation process.

• Manually start the Application Server on SuSE 11
  On SuSE 11, the Application Server does not start automatically at the end of the installation. You must start the Application Server manually at the end of the installation using the following command:
  /etc/init.d/blappserv start

To help you get started with logging on and using your new installation of BMC Server Automation, see Launching-BMC-Server-Automation.