Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Setting up the Ignite environment for provisioning

This section describes how to set up a HP-UX Ignite environment for use in BMC Server Automation provisioning.

Before you begin

  • You must have a working Ignite environment, configured for and stocked with all of the operating system installation files you want to use to provision target servers.
  • The Ignite master must be running version 7.4. x or later of the RSCD agent. For information on installing or upgrading the agent, see Installing-only-the-RSCD-agent-Linux-and-UNIX or Upgrading-RSCD-agents.

Note

For successful provisioning, an RSCD agent must be running on the Ignite master. This agent must be licensed for use with both NSH and BMC Server Automation.

To set up Ignite

  1. On the Ignite master, select or create a directory to use as a BMC Server Automation staging directory. This directory holds copies of the configuration files that BMC Server Automation generates. By convention, this directory is called /export.
     Make a note of this directory. You need it when you configure BMC Server Automation for Ignite. (Specifically, you need to specify this staging directory in the STAGING_DIR_PATH property when you define your Ignite data store instances.)
    Directly beneath this staging directory, create a /Bladelogic/rscd subdirectory.
    For example, if the staging directory is called /export, the directory structure is:
    /export/Bladelogic/rscd
  2. Obtain the HP-UX agent installer file. For example, RSCD820-341-HPUX11.SH.
     You can download this file from the BMC Support site.
    This file installs an RSCD agent on each target computer being provisioned.
  3. Rename the RSCD820-341-HPUX11.SH file to rscd.sh, and copy rscd.sh to the newly created Bladelogic/rscd directory.
  4. Create a response file for the installation of the RSCD agent and store the response file in the newly created Bladelogic/rscd directory. The response file is called nsh-install-defaults.
     For information about creating an nsh-install-defaults file, see Creating an installation defaults file for Linux or UNIX agents.
  5. Confirm that the Bladelogic/rscd directory on the Ignite master contains the following files:
    rscd.sh
    nsh-install-defaults

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*