Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Server Automation10.51

Install > SA Core installation > Installing SA Core with a remote customer-supplied Oracle database

Installing SA Core with a remote customer-supplied Oracle database

This section describes installing all SA components on the same host with an existing remote non-SA-supplied Oracle database.

Note
Because this layout uses a customer supplied database, the remote Oracle database must have been installed and configured as described in Non-SA-supplied Oracle software and database setup before you begin the SA Core installation.

Note
Before starting the SA installation process, it is also required to manually install and configure the Oracle Client software on the server that will host the Model Repository SA component. Details with Oracle Client required configurations can be found in the Non-SA-supplied Oracle software and database setup section.

You can use the right-hand column to indicate that a phase is completed:

Core installation phases
Phase	Complete
Phase 1: Preparing to install the SA Core
Phase 2: Run the SA installer
Phase 3: Specify Core components Host/Select installation type
Phase 4: Select the interview type and provide SA parameter values
Phase 5: Install the SA components

Phase 1: Preparing to install the SA Core

You will need the SA Product Software media and the Agent and Utilities media.
The server on which the SA Core Components are to be installed must be running a supported Red Hat Enterprise Linux or SUSE Enterprise Server Linux operating system. See the SA 10.51 Support and Compatibility Matrix.
On the server where you will install the SA, mount the following media: Product Software (primary) and Agent and Utilities (upload) or NFS-mount a directory that contains a copy of the media:
Open a terminal window and log in as a user with root privileges.
Change to the root directory:
cd /

Note: The SA Installer must have read/write root access to the directories in which the SA components, including NFS-mounted network appliances are to be installed.

Phase 2: Run the SA installer

On the server on which you plan to install SA and the Oracle database, run the install script:

/<distro>/opsware_installer/hpsa_install.sh

where <distro> is the full path to the Product Software (primary) media.

You see messages displayed on screen as the SA Installer loads the required files.

Logs for the installation are automatically stored. See Installer logs.

Phase 3: Specify Core components Host/Select installation type

The following menu appears:
Specify Hosts to Install ========================
Currently specified hosts:
192.168.136.36 (this is the IP address of the host on which the installer is invoked)
Please select one of the following options:
1. Add/edit host(s) 2. Delete host(s)
Enter the option number or one of the following directives: (<c>ontinue, revious, <h>elp, <q>uit)
Since this sample installation uses the host, the installer is invoked for all Core Components. Type c and press Enter to continue. You can invoke the installation from a remote machine by selecting 2 to delete the localhost IP address followed by 1 to add the remote host IP address.
When you are satisfied with the entries, press C to continue.
At this point, the SA Installer attempts to set up NFS mounts to the installation media and prepare the server for installation.
The following menu appears:
Install Type ============
1. Typical Primary Core 2. Custom Primary Core 3. Typical Secondary Core 4. Custom Secondary Core
Enter the option number or one of the following directives: (revious, <h>elp, <q>uit)
Enter 1 (Typical Primary Core) and Enter to continue.
The following menu appears:
Oracle Installation ===================
1. Install Oracle with SA 2. Use Existing Oracle Database
Enter the option number or one of the following directives: (revious, <h>elp, <q>uit)
Enter 2 (Use Existing Oracle Database) and press Enter to continue.
Select the TLS version.
Cryptographic Protocol Selection for the Server Automation Components [WARNING] Please make sure that all the cores and satellites from the mesh are at the same TLS level. ======================================================================== 1. TLSv1 2. TLSv1.1 3. TLSv1.2 Enter the option number or one of the following directives (revious, <h>elp, <q>uit)[2]:
Select 2 (TLSv1.1) and press Enter to continue.

Phase 4: Select the interview type and provide SA parameter values

The following menu appears:
Interview Type ==============
1. Simple Interview 2. Advanced Interview 3. Expert Interview
Enter the option number or one of the following directives: (revious, <h>elp, <q>uit)
Enter 1 (Simple Interview) and Enter to continue.
You are prompted to supply values for the following SA parameters:
- opsware_admin user (truth.oaPwd): an SA administrator password (the default username is admin).
 Note: The password you specify here will be used as the default password for all SA features that require a password until you explicitly change the defaults.
- crypto.hash_algorithm: The hashing algorithm [SHA1, SHA224, SHA256, SHA384, SHA512] for SA cryptographic module.
- crypto.key_length: the key length [2048 or 4096] used for hashing algorithm of SA cryptographic module.
- decrypt_passwd: A password for the SA cryptographic material.
- truth.dcNm: A name for your SA facility.
- windows_util_loc: The location for the Microsoft Patching utilities.
Note: These utilities are required if you plan to use SA to install Windows operating system patches/hotfixes and/or to manage Windows-based servers with SA. If you do not intend to use SA for these tasks, you can bypass the upload of these files by entering “none”. However, if in future you decide to use SA for Windows patching or to manage Windows servers, you will be required to install these files from the SA Client. For information about uploading these files from the SA Client, see the "Server Patching" in the SA 10.51 Use section.
- db.host: the IP address of the remote database server.
- db.sid: the SID of the Oracle instance containing the Model Repository
- db.port: the port on which the database is listening
- word.store.host: The IP address of the NFS server for the Software Repository.
- word.store.path: The absolute path on the NFS server for Software Repository
 (/var/opt/opsware/word)
For more information about these parameters, see the SA Core parameter reference.
You see these prompts (the prompts display one at a time); after you provide a value and press enter, and if the value is acceptable, the next prompt displays:
Interview Parameters ====================
Navigation Keys: Use <Ctrl>P to go to the previous parameter. Use <Ctrl>N to go to the next parameter. Use >Tab> to view help on the current parameter. Use <Ctrl>C to interrupt the interview.
Parameter 1 of 15 (truth.oaPwd) Please enter the password for the opsware_admin user. This is the password used to connect to the Oracle database. If you are installing Oracle with SA the opsware_admin user will be created with this password. Make sure the password complexity matches the security guidelines in your organization.: []
```
Parameter 2 of 15(fips.mode)
Do you want SA to be in FIPS mode? (y/n) [n]: n
```
```
 
```
```
Parameter 3 of 15: (crypto.hash_algorithm)
Please enter the hashing algorithm for SA cryptographic module. Press TAB for a list of possible values. [SHA256]:
```
```
 
```
```
Parameter 4 of 15: (crypto.key_length)
Please enter the key length [2048 or 4096] used for hashing algorithm of SA cryptographic module. [2048]: 
```
```
 
```
```
Parameter 5 of 15 (decrypt_passwd)
Please enter the password for the cryptographic material.: []
```
Parameter 6 of 15 (truth.dcNm) Please enter the short name of the facility where the Opsware Installer is being run (no spaces).: []
Parameter 7 of 15 (windows_util_loc)
Please enter the directory path containing the Microsoft patching utilities. Press Ctrl-I for a list of required files or enter “none” if you do not wish to upload the utilities at this time (none).: []
Note: Uploading the Microsoft patching utilities is optional, however, if you expect to have Windows-based managed servers, you should follow the instructions for obtaining these files as described in System requirements for installation .
Parameter 8 of 15 (db.host)
Please enter the IP address of the database host: []
```
Parameter 9 of 15 (truth.servicename)
Please enter the service name of the Model Repository instance in the facility where Opsware Installer is being run [truth.rose2]: 
```
```
 
```
```
Parameter 10 of 15 (db.sid)
Please enter the SID of the Oracle instance containing the Model Repository [truth]:
```
```
 
```
```
Parameter 11 of 15 (db.port)
Please enter the port on which the database is listening. [1521]:
```
```
Parameter 12 of 15 (db.orahome)
Please enter the path of the ORACLE_HOME directory of your Model Repository (truth) server. [/u01/app/oracle/product/12.1.0.2/db_2]:
```
```
 
```
```
Parameter 13 of 15 (word.store.host)
Please enter the IP address of the NFS server for the Software Repository. For satellite installs, please enter the IP address of the Software Repository Cache. [192.168.136.39]: 
```
```
 
```
```
Parameter 14 of 15 (word.store.path)
Please enter the absolute path on the NFS server for Software Repository 
[/var/opt/opsware/word]: 
```
```
 
```
```
Parameter 15 of 15 (bootagent.host)
Please enter the OS Provisioning Boot Server ip or hostname [192.168.136.49]:
```
You are asked to re-enter any required passwords for confirmation.
When you have supplied values for all parameters, the following message displays:
```
All parameters have values. Do you wish to finish the interview? (y/n):
```
Enter y and press Enter to continue. If you enter n, you are presented with each parameter again with the value you entered as the default. You can then change the value or accept the default. If you need to exit the installation, press Ctrl-C.
You can now install the SA Components.

Phase 5: Install the SA components

The following screen appears:
Install Components ============== Model Repository, First Core Core Infrastructure Components Slice OS Provisioning Components Software Repository - Content (install once per mesh)
Enter the option number or one of the following directives: (<c>ontinue, revious, <h>elp, <q>uit)
Enter c and press Enter to begin the prerequisite checks.

Note: Before SA begins the SA component installation, it performs prerequisite checks that the host on which you are installing SA meets the minimum requirements for the installation. The check ensures that required packages are installed, required environment variables are set, sufficient disk space is available, and so on. If your host fails the prerequisite check, the installation can fail or core performance may be negatively affected. If your host fails the prerequisite check, the installation will fail with an error message that describes the problem. Correct the problem and retry the installation or, if you are unable to resolve the problem, contact HPE Support.

If the prerequisite check completes successfully, you may still see some messages similar to the following:
Prerequisite Checks ==============
Results for <IP_address>:
 WARNING Insufficient swap space (18 GBytes). 24 Gbytes is the recommended for Oracle.
 WARNING File system ‘/’ has 29447 MBytes available and 154050 is recommended.
 WARNING Nothing listening at db.host:db.port (ip_address). Note: Can be ignored if core install will be performed using hpsa_install script.
Enter the option number or one of the following directives: (<c>ontinue, revious, <h>elp, <q>uit)
The Prerequisite check identifies WARNINGs and/or FAILUREs. FAILUREs can cause a failed or incomplete installation and must be resolved before continuing the installation. WARNINGs allow you to continue the installation, however, core performance may be negatively affected if you continue without resolving them.
If your server passes the prerequisite check, enter c and press Enter to begin the installation.
You see many messages displayed as the installation progresses, unless the installation fails, these messages are purely informational. The installation can take several hours based on the performance of your server. When the installation completes, you the Core Description File (CDF) is automatically saved.

Post-installation tasks

You must now complete the tasks described in SA Core post-installation tasks.

Send Help Center feedback