Installing and configuring the Application Server for PXE-based provisioning

The following sections describe how to install and configure the Application Server for PXE-based provisioning:

Prerequisites

The Application Server must have connectivity to the database server.

Required software

The Application Server installer must be copied to the Application Server. The installer name is in the following format: BBSA<version-platform>.<file_type>
For example: BBSA82-WIN32.exe

Steps

1. Run the Application Server installer file. Complete the installer panels as follows:
   • Select the Full installation option.
   • For the certificate password, type any value. (This value is not used again.)
   • Select Configure Application Server.
   • Select the database type that your site is using (SQL or Oracle).

   • Enter the following database-specific information.

     The following password values are examples. You can use different passwords.

     Platform	Information
     SQL Server	Database server: The server name or IP address Database port: 1433 (unless you configured a nonstandard port ) Database name: BladeLogic User ID: bladelogic Password: bladelogic
     Oracle	Database server: The server name or IP address Database port: 1521 (unless you configured a nonstandard port) SID: bladelogic User ID: bladelogic Password: sa

   • For file server, enter the server name on which the file server agent was installed.
   • For file server location, use the default path. Allow the installation program to create a directory if it does not exist.
   • For SMTP and SNMP, skip these options.
   • For the RBACAdmin and BLAdmin user passwords, type bladelogic for both.
2. Wait for the installation to finish.
3. Verify that the following services are started. If they are not, start them:
   • BladeLogic Application Server

   • BladeLogic RSCD agent

     A third service, the Process Spawner, is not required for provisioning.

     The following example shows the three BMC Server Automation services in a Microsoft Windows services list.
     

     A Windows system might return a timeout error message saying that the service is taking too long to start. In that case, wait a little longer. Then refresh the Services window and verify that the services started.

4. Verify that the service startups are successful. A successful startup results in log entries in the <BladeLogic_install_dir>\NSH\br\appserver.logsimilar to the following:

   \[22 Mar 2010 16:37:13,917\] \[main\] \[INFO\] \[::\] \[\] Hostname = blapp-rhel-01
   OS Name = Linux
   Version = 2.6.18-164.el5
   Architecture = i386
   Number of Processors Available to JVM = 1
   JRE Version = 1.6.0_13 from Sun Microsystems Inc.
   JRE Data Model = 32-bit
   JRE VM Name = Java HotSpot(TM) Client VM
   Maximum JVM Memory (B) = 1,059,258,368
   Total JVM Memory (B) = 132,120,576
   Free JVM Memory (B) = 52,187,800
   Used JVM Memory (B) = 79,932,776
   Maximum File Descriptors = 1,024
   Used File Descriptors = 258
   FIPS 140-2 Mode = enabled
   \\
   BLManager Current Time = Mon Mar 22 16:37:13 EDT 2010
   BLManager Started = Mon Mar 22 16:37:10 EDT 2010
   BLManager PID = 1848
   \\
   \[22 Mar 2010 16:37:13,921\] \[main\] \[INFO\] \[::\] \[\] Accepting requests...
   \[22 Mar 2010 16:37:13,922\] \[main\] \[INFO\] \[::\] \[\] Ready.
   

5. Browse to the following directory: <BladeLogic_install_dir>\NSH\bin
6. (Optional) To load prepackaged content, run blcontent.exe.
   A command prompt window appears, and the file runs for 1 minute or more, depending on processing conditions on the host. This file populates the database with sample data, such as groups, folders, smart groups, sample roles, authorization profiles, and access control list (ACL) templates.