Oracle Fleet Patching and Provisioning Architecture

Oracle Fleet Patching and Provisioning architecture consists of an Oracle Fleet Patching and Provisioning Server and any number of Oracle Fleet Patching and Provisioning Clients and targets.

Oracle recommends deploying the Oracle Fleet Patching and Provisioning Server in a multi-node cluster so that it is highly available. Oracle FPP Server supports single-node deployment, but it is not recommended.

Note:

You can not configure Oracle FPP Server on an Oracle Restart server.

The Oracle Fleet Patching and Provisioning Server cluster is a repository for all data, of which there are primarily two types:

  • Gold images
  • Working copies and clients
  • Metadata related to users, roles, permissions, and identities

The Oracle Fleet Patching and Provisioning Server (FPPS) acts as a central server for provisioning Oracle Database homes, Oracle Grid Infrastructure homes, and other application software homes, making them available to the cluster hosting the Oracle Fleet Patching and Provisioning Server and to the Oracle Fleet Patching and Provisioning Client (FPPC) clusters, their targets, and non-client targets.

Users operate on the Oracle Fleet Patching and Provisioning Server or Oracle Fleet Patching and Provisioning Client to request deployment of Oracle homes or to query gold images. When a user makes a request for an Oracle home, specifying a gold image, the Oracle Fleet Patching and Provisioning Client communicates with the Oracle Fleet Patching and Provisioning Server to pass on the request. The Oracle Fleet Patching and Provisioning Server processes the request by taking appropriate action to instantiate a copy of the gold image, and to make it available to the Oracle Fleet Patching and Provisioning Client cluster using available technologies such as Oracle Advanced Cluster File System (Oracle ACFS) and local file systems.