Oracle Cloud Infrastructure Documentation

Defining a Custom Product

Use the "Bring your own product" functionality of Fleet Application Management that considers an example of adding a third-part product such as Apache Tomcat to the list of supported products in your tenancy.

In this step, you set up the foundation so that Fleet Application Management can recognize the support for Apache Tomcat.
  1. Create a product.
    For example, name the product Apache Tomcat and specify the version as 10.1.30.
  2. Establish a software patch type for the product.
    This step is essential for supporting patch and lifecycle management. Fleet Application Management should be aware of the types of patches available for Apache Tomcat. The patch types can align with the terminology used by Fleet Application Management or be customized based on the product.
    For example, managing patching needs for Apache Tomcat might involve categories such as Critical Patch Update, Bug Fix, Security Enhancement, and more, assuming that critical patch update is supported for Apache Tomcat.
  3. Generate a custom credential name to uniquely identify the credentials for Apache Tomcat.
    When conducting a lifecycle management operation, such as scanning for software on an instance or connecting to the server spawned by the software, credentials are required. This custom credential name must be specified.
  4. After the patch types and credential names are created, associate them with the Apache Tomcat product by updating the product definition.