Content stack - Tomcat

Version 2
    Share:|

    Introduction

     

    Purpose of this document is to reference BSA contents that have been build to well work together and to manage a specific service which is here tomcat. In BSA, when we want to manage a service it is better to target a component rather than a server as:

    1. you can have multi instance of a service on a server, and multi service on a server. For example, several tomcat instance and a data base on the same server.
    2. you may need to associate specific properties to a service instance and not to a server.

     

    So a content stack is composed of a component template that define at least the properties that will be useful to manage the service, some provisioning action to create the service and some management actions.

     

    This stack can be used with Release Process Management following integration stack: Continuous Deployment with BSA - RPM/RLM 4.x

     

    Component template

     

    Component template to import in BSA: Tomcat

     

    Provisioning actions

     

    Blade ZipKit - Tomcat Deploy binaries - LinuxThis package is to deploy the tomcat binaries to a Linux OS. It doesn't create or start any Tomcat instance.
    Blade ZipKit - Tomcat create and start instance - LinuxThis package is to create and start tomcat instance owned by a non root user part of tomcat group. This package doesn't deploy the tomcat binaries that need to be already on the target.

     

    Management actions

     

    Blade ZipKit - Tomcat Deploy application - UnixThis package is for deploying application from an archive file to a tomcat instance. Target has to be the server where the instance is running or a component associated to this server.
    Blade ZipKit - Tomcat undeploy application - UnixThis package is for undeploying an application from a tomcat instance. Target has to be the server where the instance is running or a component associated to this server