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 :

template_<template_description>:

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.
• This ibm_wasndv9_standalone repository contains these child directories: amazon, ibmcloud, and vmware.
• These child directories contain a terraform directory, which contains the template for the WebSphere Application Server deployment.
• This directory also contains the camvariables.json file, which is the parameters file that is used to customize the deployment experience.

cookbook_<middleware_product>:

These repositories contain the Chef based automation that is used for the installation and configuration of the corresponding software.

• The cookbook_<middleware_product> directory contains the required files: README.md, attributes.json, components.json, metadata.rb, and recipes.json.
• It also contains several subdirectories which contain the required files for the cookbook:
  • attributes: This directory contains the attributes files: default.rb and internal.rb.
  • 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 prereq.rb, install.rb, gather_evidence.rb, fixpack.rb, harden.rb, and more.
  • resources: This directory contains resources to be used with the LWRPs under the provider directory.

Chef cookbooks

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 .

What's Next

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.

• Terraform Template Overview
• Template Cloud Parameters
• Template Middleware Parameters