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.60

Install > SA Core installation > Install additional slice component bundles

Installing additional slice component bundles

You can install additional Slice Component bundles on an existing SA Core in order to improve the scalability. To install an addition Slice Component bundle to an installed SA core, perform the following tasks.

Note When adding a new Slice Component bundle to an existing core, SA services are restarted on all servers that are part of the core.

On any core server in the SA Core in which you plan to install the additional Slice Component bundle, run the install script, specifying the Core Description File (CDF) you generated when you installed the core by using the -c argument and the full path to the file:
/<distro>/opsware_installer/hpsa_install.sh -c /usr/tmp/hpsa_cdf.xml
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.
You see a screen similar to the following:
```
Specify Hosts to Install
```
```
========================
```
```
 
```
```
Currently specified hosts:
```
```
 
```
```
       192.168.136.36 (oracle_sas)
```
```
       192.168.136.38 (slice)
```
```
       192.168.136.39 (infrastructure)
```
```
       192.168.136.40 (osprov)
```
```
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, <p>revious, <h>elp, <q>uit): 1
```
```
Enter number of hosts to add (or enter "0" to edit the list): 1
```
Enter 1 to add the IP address of the server that will host the additional Slice Component bundle.
In third-party certificate mode, make sure that all the SA Core and Satellite hosts define the hostnames of all Core or Satellite hosts at the beginning of their /etc/hosts file. Otherwise, the SA installation will fail.
Listing these hostnames in the /etc/hosts file enables SA to generate correct certificate signing requests (CSRs) for the SA hosts.

Example: to install an SA mesh with the following topology,
16.77.42.65 (oracle_sas, truth_mm_overlay) 16.77.41.24 (infrastructure, word_uploads) 16.77.43.252 (slice, osprov) 16.77.45.21 (satellite)
add the following lines at the beginning of the /etc/hosts file for 16.77.42.65, 16.77.41.24 and 16.77.43.252:
16.77.42.65 hostname1.example.com hostname1
16.77.41.24 hostname2.example.com hostname2 16.77.43.252 hostname3.example.com hostname3
The 16.77.45.21 (satellite) server does not need to be listed here because this server is part of the mesh and not part of the Core.
For example:
```
Adding hosts
```
```
============
```
```
 
```
```
Parameter 5 of 5
```
```
Hostname / IP []: 192.168.136.43
```
All values are entered. Do you wish to continue? (Y/N) [Y]: Y
After you have specified the host server’s IP address, the Specify Hosts to Install screen looks similar to this:
```
Specify Hosts to Install
```
```
========================
```
```
 
```
```
Currently specified hosts:
```
```
 
```
```
       192.168.136.36 (oracle_sas)
```
```
       192.168.136.38 (slice)
```
```
       192.168.136.39 (infrastructure)
```
```
       192.168.136.40 (osprov)
```
```
       192.168.136.43
```
```
 
```
```
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, <p>revious, <h>elp, <q>uit): c
```
Note that the last IP address in the list is the IP address you just entered however, no component is assigned to that IP address for installation.
To assign the Slice Component bundle to the IP address you just specified, enter c and press Enter to continue.
You are prompted to provide the host password for each host in the list.
The installer validates each password, then you see messages displayed as the installer prepares the server for installation.

When the set up completes, you see a screen similar to the following:

Install Type

============

1. Typical Primary Core

Enter the option number or one of the following directives

(<p>revious, <h>elp, <q>uit): 1

Accept the default.

The Install Type is stored in the Core Definition File (CDF) when you install the SA First Core and is the default for subsequent installations and upgrades. You cannot use a Typical Installation type for the SA Core and a Custom Installation type for subsequent installations. Both installs must be of the same Installation type.

You see a screen similar to the following:

Host/Component Layout

=====================

Installed Components

Oracle RDBMS for SAS                                 : 192.168.136.36

Model Repository, First Core                         : 192.168.136.36

Core Infrastructure Components                       : 192.168.136.39

Slice                                                : 192.168.136.38

OS Provisioning Components                           : 192.168.136.40

Software Repository - Content (install once per mesh): 192.168.136.39

------------------------------------------

Select a component to assign

1. Slice

Enter the number of the component or one of the following directives

(<c>ontinue, <p>revious, <h>elp, <q>uit): 1

In this case, since all other components have already been installed and only the Slice Component bundle can have multiple instances, only the Slice option is displayed. Select 1 and press Enter.

You see a screen similar to the following:

Host Assignment for Slice

=========================

1 ( ) 192.168.136.36

2 ( ) 192.168.136.39

3 ( ) 192.168.136.40

4 ( ) 192.168.136.43

Enter the number of the host or one of the following directives

(<c>ontinue, <a>ll, <u>nselect all, <p>revious, <h>elp, <q>uit): 4

Enter the line number associated with the IP address you specified above. An asterisk appears next to your selection.

Host Assignment for Slice

=========================

1 ( ) 192.168.136.36

2 ( ) 192.168.136.39

3 ( ) 192.168.136.40

4 (*) 192.168.136.43

Enter the number of the host or one of the following directives

(<c>ontinue, <a>ll, <u>nselect all, <p>revious, <h>elp, <q>uit): c

Enter c then press Enter to continue.

You see a screen similar to the following:

Host/Component Layout

=====================

Installed Components

Oracle RDBMS for SAS                                 : 192.168.136.36

Model Repository, First Core                         : 192.168.136.36

Core Infrastructure Components                       : 192.168.136.39

Slice                                                : 192.168.136.38

OS Provisioning Components                           : 192.168.136.40

Software Repository - Content (install once per mesh): 192.168.136.39

------------------------------------------

Select a component to assign

1. Slice [192.168.136.43]

Enter the number of the component or one of the following directives

(<c>ontinue, <p>revious, <h>elp, <q>uit): c

Enter c then press Enter to continue.

Select the same TLS version as on the primary core and press Enter to continue.
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 (<p>revious, <h>elp, <q>uit)[3]:

You see a screen similar to the following where you can modify installation parameters if necessary:

Interview Parameters

====================

Navigation keys:

Use <ctrl>p to go to the previous parameter.

Use <ctrl>n to go the next parameter.

Use <tab> to view help on the current parameter.

Use <ctrl>c to abort the interview.

All prompts have values.  What would you like to do:

1. Re-enter values

2. Continue

Enter the option number or one of the following directives

(<c>ontinue, <p>revious, <h>elp, <q>uit): c

Enter c then press Enter to continue.

After a prerequisite check, the Slice Component bundle is installed on the host you specified. You see some messages displayed as the installation proceeds and a completion message when the installation is finished.

In third-party certificate mode, SA installs the OCT (Opsware Cert Tool) component on the Model Repository server before the Core installation begins. The OCT component will generate the Certificate Signing Requests (CSRs) for the certificates required for the current installation configuration. After OCT install, follow the following two additional steps before the SA installation begins:
1. Enter the location where you want the OCT component to generate the *.csr files.
  Select path where to generate CSRs
  =============================
  Specify the path on the Model Repository server where SA will generate the CSR files
  [/var/tmp/csrFiles]:
  CSRs were generated in the /var/tmp/csrFiles directory on the server that hosts the Model Repository component [192.168.136.39].
  Please have them signed by your CA. You can resume the install process after all CSRs are signed.
  Make sure you copy all certificates in the same directory on the core's Model Repository server.
  You will be prompted for the path to this directory in the next step of the install process.
  Submit these files to your CA for signing and place the issued certificates in a folder of your choice.
  After generating the cryptographic material, SA places the CSRs created for that instance in a subfolder named by date. For example: csr_2017-05-02.08:21:05 csr_2017-05-02.08:22:10. Any new CSRs are placed in the dedicated folder that you provide during the installer interview.
  When providing the third-party certificates, make sure to follow the certificate format and naming requirements described in the SA certificates format.
2. Provide the location where you have placed the custom certificates signed by your CA. The installer checks that the path is correct and that all required certificates are available.
  Enter the path to the directory containing the custom certificates. ===================================================================
  Path to the directory containing the certificates. [/var/tmp/certificateFiles]:
  SA now generates a new cryptographic material containing your signed certificates. The cryptographic material is then copied it on all hosts in the mesh.

Send Help Center feedback