Middleware Content Templates
After you configure your runtime environments, you can proceed to the content in Middleware Template Library in the Managed services interface to deploy a middleware content. Middleware Content automation are represented in Managed services by the Terraform Template format. These templates are made available through a set of private GitHub repositories .
Before you begin
Read the Managed services Content topic and complete the steps to configure your content runtime environments.
Middleware Template Library
The Middleware Content automation leverages two types of content from this repository :
This library repository contains predefined Terraform templates that are used when provisioning a Middleware Template.
This repository contains separate directories for available middleware. For example:
- This repository might be named
ibm_wasndv9_standalone, which contains the templates for a WebSphere standalone topology.
ibm_wasndv9_standalonerepository contains these child directories:
- These child directories contain a
terraformdirectory, which contains the template for the WebSphere Application Server deployment.
directory also contains the
camvariables.jsonfile, which is the parameters file that is used to customize the deployment experience.
These repositories contain the Chef based automation that is used for the installation and configuration of the corresponding software.
cookbook_<middleware_product>directory contains the required files:
- It also contains several subdirectories which contain the required files for the cookbook:
attributes: This directory contains the attributes files:
libraries: This directory contains chef libraries to extend the cookbook functionality.
providers: This directory contains cookbook Lightweight Resource Providers (LWRPs) to extend cookbook functionality
recipes: This directory contains the recipes for the cookbook, such as
harden.rb, and more.
resources: This directory contains resources to be used with the LWRPs under the provider directory.
IBM-created Chef cookbooks use a common structure to provide a consistent experience. Each cookbook repository holds the automation for a single product. When possible, a cookbook will support multiple versions of a product offering, as well as support for multiple operating systems.
Cookbook and Template Versions
Currently templates supported and versions, see IBM-CAMHub-Open/IBM-CAMHub-Open repository .
Proceed to Deploying a Middleware template to know more about deploying a middleware template.
Proceed to these section if you want to know more about middleware templates in GitHub repositories and and how it relates to relates to Terraform.