Configuring Oracle Fleet Patching and Provisioning Clients

Oracle Fleet Patching and Provisioning (Oracle FPP) client configuration includes configuring network, creating client data file, and creating an Oracle FPP client.

Creating an Oracle FPP Client

Users operate on an Oracle Fleet Patching and Provisioning (Oracle FPP) Client to perform tasks such as requesting deployment of Oracle homes and querying gold images.

On the Oracle Fleet Patching and Provisioning Server as the Grid home owner, create the client data file, as follows:
```
$ rhpctl add client -client client_cluster_name [-clusternamealias 
cluster_name_alias] -toclientdata path
```
RHPCTL creates the client data file in the directory path you specify after the -toclientdata flag. The name of the client data file is client_cluster_name .xml.

Note:
Oracle recommends that you specify a unique client_cluster_name and it must match the cluster name of the client cluster where you run step 4. If the client cluster name is not unique, then you can specify a cluster name alias.
Copy the client data file that you created in the previous step to a directory on the client cluster that has read/write permissions to the Grid home owner on the Oracle Fleet Patching and Provisioning Client.

Optional: Generate a P12 file from the security certificate that you want to use for the Oracle FPP Server configuration.

$ openssl pkcs12 -export -inkey ${SERVER_KEY} -passin pass:${PASS} -in ${SERVER_CRT} 
-name orakey -certfile ${CA_CRT} -caname cakey -out ${P12_FILE} -password pass:${P12_PASS}

Create the Oracle FPP Client by running the following command as root on the client cluster:
```
# srvctl add rhpclient -clientdata path_to_client_data
-diskgroup disk_group_name -storage base_path
-enableTLS YES -p12certpath P12_file_absolute_path 
-certname custom_cert_name [additional options]
```
If you want to provision working copies to Oracle ACFS storage on this cluster, and you have already created a disk group for this purpose, then specify this disk group in the preceding command. In this case, also specify a storage path which will be used as a base path for all mount points when creating Oracle ACFS file systems for storing working copies.

Note:
Once you configure a disk group on a Fleet Patching and Provisioning Client, you cannot remove it from or change it in the Fleet Patching and Provisioning Client configuration. The only way you can do either (change or remove) is to completely remove the Fleet Patching and Provisioning Client using the srvctl remove client command, and then add it back with a different disk group, if necessary. Before you remove a Fleet Patching and Provisioning Client, ensure that you remove all registered users from this cluster and all working copies provisioned on this cluster.

Use the enableTLS parameter to enable TLS and specify the custom security certificate name.
Start the Fleet Patching and Provisioning Client, as follows:
```
$ srvctl start rhpclient
```
Check the status of the Fleet Patching and Provisioning Client, as follows:
```
$ srvctl status rhpclient
```

Enabling and Disabling Oracle FPP Clients

On the Fleet Patching and Provisioning Server, you can enable or disable a Fleet Patching and Provisioning Client.

Fleet Patching and Provisioning Clients communicate with the Fleet Patching and Provisioning Server for all actions. You cannot run any RHPCTL commands without a connection to a Fleet Patching and Provisioning Server.

To enable or disable a Fleet Patching and Provisioning Client, run the following command from the Fleet Patching and Provisioning Server cluster:

$ rhpctl modify client -client client_name -enabled TRUE | FALSE

To enable a Fleet Patching and Provisioning Client, specify -enabled TRUE. Conversely, specify -enabled FALSE to disable the client. When you disable a Fleet Patching and Provisioning Client cluster, all RHPCTL commands from that client cluster will be rejected by the Fleet Patching and Provisioning Server, unless and until you re-enable the client.

Note:

Disabling a Fleet Patching and Provisioning Client cluster does not disable any existing working copies on the client cluster. The working copies will continue to function and any databases in those working copies will continue to run.

Deleting a Oracle FPP Client

Use the following procedure to delete a Fleet Patching and Provisioning Client.

Before deleting the Fleet Patching and Provisioning Client, you must first delete the working copies and users on the Fleet Patching and Provisioning Server, as follows:
1. Query the list of working copies that have been provisioned on the Fleet Patching and Provisioning Client cluster.
  
  Run the following command:
```
$ rhpctl query workingcopy -client client_name
```
2. Delete each of the working copies listed in the output of the preceding command.
  
  Run the following command for each working copy and specify the name of the working copy you want to delete:
```
$ rhpctl delete workingcopy -workingcopy working_copy_name
```
3. Query the list of users from the Fleet Patching and Provisioning Client cluster.
  
  Run the following command:
```
$ rhpctl query user -client client_name
```
4. Delete the users listed in the output of the preceding command, as follows:
  
  Run the following command and specify the name of the user you want to delete and the name of the client:
```
$ rhpctl delete user -user user_name -client client_name
```
On the Fleet Patching and Provisioning Client cluster, delete the client, as follows:
1. Stop the Fleet Patching and Provisioning Client daemon.
  
  Run the following command:
```
$ srvctl stop rhpclient
```
2. Delete the Fleet Patching and Provisioning Client configuration.
  
  Run the following command:
```
$ srvctl remove rhpclient
```
Delete the client site configuration on the Fleet Patching and Provisioning Server cluster.

Run the following command and specify the name of the client:
```
$ rhpctl delete client -client client_name
```