11 Provisioning Oracle Beehive

Oracle Beehive Provisioning Application enables you to install Oracle Beehive from Oracle Enterprise Manager Grid Control. Oracle Beehive uses the Provisioning Advisor Framework for the purpose.

The following topics are covered:

Introduction to Oracle Beehive Provisioning Application
Provisioning Oracle Beehive

Introduction to Oracle Beehive Provisioning Application

Oracle Beehive Provisioning Application consists of the following components:

Provisioning Advisor Framework
Software Library
Job System

Provisioning Advisor Framework

Provisioning Advisor Framework (PAF) provides a seamless process to integrate tasks that are associated with an application. The framework automates, orchestrates, and tracks the tasks of various applications, such as installers, upgrade assistants, and custom scripts.

PAF is built on top of the Enterprise Manager Grid Control structure. This structure comprises of Oracle Management Server (OMS), Job System, Oracle Enterprise Manager (EM) Repository, Agent and the Software Library. PAF uses an XML file called the Deployment Procedure (DP) as an input from an application. The different tasks of the application are broken down and listed in the Deployment Procedure. Each individual task is referred to as a step. A step could be further classified based on the task it performs. The step could be a manual step that requires user interaction or could be a host command step that runs a command on a specified list of targets. A group of step is referred to as a Phase. This feature enables the execution of a group of steps either in parallel or serially on the target nodes. A Deployment Procedure Engine maintains the state of the procedure while executing the phases and steps in the supplied DP.

The following figure illustrates the Provisioning Advisor Framework architecture:

Figure 11-1 Provisioning Advisor Framework Architecture

Description of "Figure 11-1 Provisioning Advisor Framework Architecture"

Software Library

The Software Library is an infrastructure entity for storing and retrieving files and packages. This provides a common repository for storing software binaries, scripts and other files that are used by provisioning, cloning, and other applications.

Job System

Enterprise Manager Job System is a repository-based system that enables you to schedule and execute jobs on target computers. The Job System supports preconfigured job types, such as OS Commands and File Transfer. The Job System also enables the applications to create job types.

Provisioning Oracle Beehive

Note:

Before provisioning Oracle Beehive Release 1 (1.4.3) for Solaris, follow these steps:

Unzip the file bhprereqpsolaris.zip from beeprov.par:

cd <Oracle Management Server home>/sysman/prov/paf
unzip beeprov.par compEntities/bhprereq-solaris.zip

Unzip the file prerequisite.properties from bhprereq-solaris.zip:

cd compEntities
unzip bhprereq-solaris.zip
  bhprereq/prereqs/prerequisite.properties

Edit the file bhprereq/prereqs/prerequisite.properties and remove bee/s_bee_prereq.xml from the first line.
Zip the edited bhprereq/prereqs/prerequisite.properties in the file bhprereq-solaris.zip:
```
zip bhprereq-solaris.zip
  bhprereq/prereqs/prerequisite.properties
```
Log on to Oracle Enterprise Manager Grid Control. Select the Deployments tab. Select Provisioning from the menu bar. Expand Components from the table. Expand Oracle Components. Expand Beehive Provisioning. Expand 1.4.3. Expand solaris64. Select Prerequisite Component. Click the Edit button. In the Edit Component page. click the Upload File tab. Upload the updated bhprereq-solaris.zip file from <Oracle Management Server home>/sysman/prov/paf/compEntities.

Notes:

For versions of Oracle Beehive Release 1 (1.3) and earlier, if you are installing Oracle Beehive with Oracle Beehive Provisioning Application, and you are not on the sudoers list of the target computer, follow these steps:

Select the Deployments tab. Click Deployment Procedures (from the Deployment Procedure Manager section). Select Oracle Beehive Release 1 Deployment and click Create Like.
In the Create Like Procedure page, fill in the fields as follows:

In the TreeTable, select Verify and fix Beehive system requirements. Change the Run Privilege to Normal (from sudo).
Click Save.
Follow the steps in this section, except run this copy of Oracle Beehive Provisioning Application.

For Oracle Beehive Release 1 (1.4), you do not have to be on the sudoers list of the target computer.

Follow these steps to run Oracle Beehive Provisioning Application:

Select the Deployments tab.
Click Deployment Procedures (from the Deployment Procedure Manager section).
Select Oracle Beehive Release 1 Deployment.
Click Schedule Deployment....

Oracle Beehive Provisioning Application will present you with the following pages in which you will enter required parameters for Oracle Beehive installation:

Target List Page
Upload
Install Inputs Page
Credentials/Schedule Page
Summary Page

Notes:

The parameters are similar to the installation procedure described in "Oracle Beehive (Standard Installation) Sequence of Screens" in "Oracle Beehive Install Wizard" in the Oracle Beehive Installation Guide of your operating system.

For Oracle Enterprise Manager Grid Control Release 4 (10.2.0.4) only, ensure that the information you input in the following pages contain only ASCII characters.

Target List Page

The following describes the parameters for the Target List page:

Host targets for Oracle Beehive installation: Select the hosts on which you want to install Oracle Beehive. You may select more than one host, add a host to the list, and remove a host from the list.

Upload

If you have not already uploaded a zipped installable version of Oracle Beehive to Oracle Beehive Enterprise Manager Grid Control Software Library, this page will prompt you to do so.

Linux and UNIX-Based Operating Systems

Upload the zipped installable version of Oracle Beehive from <Oracle Beehive installation media directory>/install/beehive_home.zip.

Microsoft Windows

Upload the zipped installable version of Oracle Beehive from <Oracle Beehive installation media directory>\install\beehive_home.zip.

Note:

When you install Oracle Beehive Provisioning Application, a zipped installable version of Oracle Beehive is automatically uploaded to Oracle Enterprise Manager Grid Control Software Library. However, it will only upload a version of Oracle Beehive for the same operating system as Oracle Beehive Provisioning Application.

Consequently, if you want to install Oracle Beekeeper for an operating system different than the one already in the software library, you will first have to upload a zipped installable version of Oracle Beehive for that operating system.

Install Inputs Page

The following describes the parameters for the Install Inputs page:

Install Input
- Oracle home: Specify the directory where you want to install Oracle Beehive. You must specify a new Oracle home directory for each new installation of Oracle Beehive.
Database Details: Specify the following details of an existing Oracle Database instance that will be used by this installation. Refer to the module "Oracle Beehive Database Requirements" in the Oracle Beehive Installation Guide of your operating system for database requirements for Oracle Beehive Release 1.

Oracle RAC Notes:
If you are specifying details for an Oracle Real Application Cluster (Oracle RAC) database, ensure that you have entered the following information correctly; Oracle Beehive Provisioning Application will not verify it by trying to connect to each database host. Instead, Oracle Beehive Provisioning Application constructs the connect descriptor with the database information you provide, then verifies if the connect descriptor can reach the database.
If you are installing Oracle Beehive in a high availability environment (you are installing multiple instances of Oracle Beehive) with the provisioning application, and you are using an Oracle RAC database, you may only use test certificates; you may not use self-signed certificates in this situation.
- Hostname and Port: Specify the fully qualified domain name (FQDN) of the host where the target database is running followed by the database listener port.
  
  For example, if the host name is foo, its domain is abc.com, and the database listener port is 1521, then you must enter the following:
  
  foo.abc.com:1521
  Note:
  In case of an Oracle RAC database, use the following format:
```
virtual_host1:virtual_port1^virtual_host2:virtual_port2^ ...
```
- Service Name: Enter the service name for the Oracle Database. This is the same as the global database name, and must be unique across all databases. This is also the same as the Service Name the Oracle Beehive Install Wizard asks you when you choose to install Oracle Beehive against an existing database.
  
  In the Oracle Beehive Installation Guide of your operating system, refer to "Installing Oracle Beehive Against an Existing Database" for more information. Refer to "Database Information" in "Oracle Beehive Install Wizard" for more information about the service name.
- Username: Specify the administrative user name (that can perform database administration tasks) for the database instance. Typically, this user is the SYS account.
- Password: Enter the password for the Oracle database administrative user account that you specified in the Username field.
Enterprise Information
- Enterprise: Specify the name for the new enterprise you want to create. An enterprise is the top-level container for all users and objects. An enterprise may contain any number of organizations and workspaces.
  
  The enterprise name is typically a company name, such as Oracle.
  
  In Oracle Beehive Release 1, an Oracle Beehive deployment may have only one enterprise.
- Organization: Specify the name of the organization to be created and added to the enterprise you specified previously. An organization is a logical grouping of users, groups, workspaces, and resources at a level lower than the enterprise level. Later, you may add any number of organizations to the enterprise you specified previously.
  
  The organization is typically a sub-level or department under the enterprise, such as Sales or Accounting.
- Instance Name: Specify the name of the instance for this Oracle Beehive installation. The instance name is used during server configuration.
  
  The full name of an Oracle Beehive instance consists of the instance, host, and domain names. For example, if you name your instance myinstance1, your host is myhost, and your domain is example.com, the full name of your instance will be myinstance1.myhost.example.com.
  
  Note:
  Only enter the instance name; do not specify the host and domain name. Oracle Beehive will append the host and domain name to the instance name. For example, you would specify myinstance1, not myinstance1.myhost.example.com.
  All Oracle Beehive Release 1 instances must have a unique name.
- Site: Specify the name of the site. A site consists of all Oracle Beehive services and service instances and the database they use.
  
  A site is typically a reference to a physical location, such as Headquarters or Montreal.
  
  In Oracle Beehive Release 1, an Oracle Beehive deployment may have only one site.
beeadmin Credentials
- Password: Specify and confirm the password for the beeadmin user. The oc4jadmin and bpeladmin users will have the same password.
- Confirm Password: Re-enter the password you entered in the previous field.
Oracle Beehive Schema Information
- Password: Use this screen to specify and confirm the password for the new database schema that will be created and used by the Oracle Beehive instance.
- Confirm Password: Re-enter the password you entered in the previous field.

Credentials/Schedule Page

The following describes the parameters for the Credentials/Schedule page:

Oracle Home Credentials: The user credentials you will specify on this page must already exist on the target nodes. Also, ensure that the specified user is a part of the osinstall group.

Note:
Ensure that you have entered the following user credentials correctly; Oracle Beehive Provisioning Application will not verify them.
- Specify Credentials for: Specify the Oracle homes that the Provisioning Application will access with the credentials (username and password) that you will specify in the following fields.
  - Username, Password, and Confirm Password: Specify the username and the password of the user that can access the Oracle homes you specified in Specify Credentials for.
Schedule
- One Time (Immediately): Starts the installation immediately
- One Time (Later): Starts the installation at the specified time. If you do not want the procedure to start immediately, select this option and use the Time Zone, Start Date, and Start Time to schedule the procedure. If you change the date or time to a time in the future, the procedure will start on the specified date and time.
- Grace Period
  - Indefinite: Use this option if you want the Oracle Management Service to continue to attempt to start the patching job for an infinite amount of time.
  - End After n Hours m Minutes: In addition, you can specify the End After option of Grace Period to allow the Oracle Management Service to continue to attempt to start the job up to the specified time. This is useful, if the Oracle Management Agent is down and the Oracle Management Service is unable to start the patching job, because if the patching job is not started within the allotted time frame, the Oracle Management Service marks the patching job as skipped.

Summary Page

Review the installation parameters in the Summary page and click Finish to start the installation of Oracle Beehive.