Oracle Private Cloud Appliance (PCA) licensing is an important part of infrastructure planning for teams deploying or maintaining the platform. The Release 2.3 licensing manual distinguishes software restricted to use with PCA from separately licensed Oracle products and third-party technologies governed by their own terms. For industrial organizations using private-cloud infrastructure to support engineering, operations, or plant applications, understanding those boundaries helps keep software inventories, deployment decisions, and compliance reviews aligned.
The manual applies to PCA Release 2.3 and describes license entitlements, restrictions, prerequisites, special rights, and separately licensed technology. It is a licensing reference rather than a deployment or architecture guide. The terms that apply to a particular installation should be checked against the applicable license agreement and order documents.
How Oracle Private Cloud Appliance licensing is structured
The manual groups PCA software into several licensing categories. Some software is integrated with the appliance and has a restricted-use license. Other Oracle software is licensed separately, while open-source and third-party components may be covered by individual notices and licenses. These distinctions matter because inclusion in an appliance does not, by itself, mean that every component can be used for any purpose or on any system.
Integrated software is tied to PCA
Unless separate license terms expressly apply, software or programmable code embedded in PCA, or specifically supplied by Oracle as integrated software for PCA, is restricted to use solely with the appliance. The manual lists Oracle Software Defined Networking, Oracle Fabric Manager, Oracle ZFS Storage Appliance Cloning, and Oracle ZFS Storage Appliance Replication as examples of integrated software.
The restriction does not cover every item associated with the appliance. The manual excludes diagnostic, maintenance, repair, and technical-support code, as well as separately licensed applications, operating systems, development tools, and system-management software. It also identifies Integrated Software Options that may be embedded, installed, or activated on PCA but must be ordered separately for an additional fee. Teams should therefore confirm a component’s status rather than infer its rights from whether it appears in the appliance environment.
Included software may have specific use limits
The manual states that Java SE Server JRE 1.8.0_73 is included with PCA for running PCA applications. Use of Java SE in another way, or use of a different Java SE version, is subject to the terms referenced in the document. Oracle VM Manager is also included, with use restricted solely to PCA.
These examples illustrate why software inventories should record more than product names. For each component, teams can document the version, where it is installed, its operational purpose, and any license condition that limits its use. This is particularly useful when infrastructure supports multiple environments, such as production applications, engineering systems, or test workloads.
Separate licenses and third-party notices
The Release 2.3 manual identifies Oracle Linux and Oracle VM as separately licensed software, with terms set out in the document. It also explains that some software may contain third-party technology. Depending on the notices and documentation accompanying a component, that technology may be covered by the general agreement or by separate terms. The applicable component-level license should be consulted when those terms are provided.
The third-party notices section covers software included in PCA base software and in hardware and software products used with PCA. Its contents include Tinyproxy 1.8.3, Oracle Hardware Management Pack, Java SE Runtime Environment 8, Oracle VM, network and server products, and Oracle ZFS Storage Appliance products. The breadth of this list is a reminder that compliance review may involve both the appliance software and the components associated with its supporting hardware.
Tinyproxy 1.8.3 is identified as part of the PCA controller software and provided under GNU General Public License version 2 (GPLv2). The manual reproduces the license, including conditions relevant to copying, modifying, and distributing covered software. In general, those conditions distinguish running software from distributing copies or modified versions. Organizations should review the actual license and component notices before redistribution or modification; the manual is not a substitute for that review.
Practical steps for engineering and operations teams
Licensing checks can be incorporated into existing infrastructure governance rather than treated as a one-time purchasing task. A focused review can help teams recognize when a change in deployment, version, or distribution may require closer examination.
- Maintain a component inventory. Record PCA software, versions, and related hardware or software products, then compare the inventory with the licensing manual and component notices.
- Separate restricted-use and separately licensed items. Flag software limited to PCA and identify products or options that have separate licensing requirements.
- Review changes before implementation. Check licensing implications when changing Java versions, using software outside its stated PCA purpose, or introducing a component into another environment.
- Check distribution and modification obligations. For open-source components such as Tinyproxy, review the applicable license before redistributing binaries or modified code, including any source-code and notice requirements.
- Retain supporting records. Keep relevant order documents, license terms, software notices, and review decisions accessible to engineering, procurement, and compliance stakeholders.
The manual also directs customers with questions about license rights and obligations to consult their Oracle sales representative, the referenced Software Investment Guide, or Oracle License Management Services. Those channels are appropriate when a planned use does not clearly fit the documented terms.
Conclusion: make licensing part of infrastructure planning
For PCA Release 2.3, the central operational lesson is to distinguish software restricted to the appliance from separately licensed Oracle products and third-party components with their own terms. That distinction can affect installation choices, version changes, reuse, and redistribution. By maintaining an accurate software inventory and checking the relevant license before changing how a component is used, industrial automation teams can make infrastructure decisions with a clearer understanding of their obligations. The Release 2.3 manual is a dated, product-specific reference, so teams should confirm the terms that apply to their own agreement and deployment.