Jython Framework: Using a template

This IBM product plugin enables integration with and provisioning of WebSphere Application Server services via a Jython framework.

This section covers the simple case where you use the templates to create the deployment files, and the data dictionary when you want to update the configuration at a later date.


This plugin contains a number of orchestration tasks that augment the core task framework to allow deployment of WebSphere ear/war files and their associated configurations.


A number of templates are available when you create a new project.

Templates are available to create/update the following WebSphere Artifacts:

  • Create multiple JDBC Provider and Data Sources template
  • Create cluster template. Includes Web Container, JVM settings (Process, Logging, Transaction), Object Cache, Cluster scaling settings (vertical/horizontal), Replication Domains, Port Allocation, Trace Service settings etc.
  • Create deployable Enterprise application template. Includes Classloading policies, Module start orders etc.
  • Create an entire environment. Allows the selection of Applications to deploy, cluster creation/update, Multiple Database Providers and Data Sources, Url Providers and URLs, Work Managers, Object Caches, Application level security, custom TAI, Namespace Bindings, WebSphere Variables, Virtual Hosts, Shared Libraries, Core Groups, SIB Settings, PMI Settings etc.
  • Cell Level template. Create cell level security, Users, Groups, Federated Repositories, LDAP configuration, Custom JAAS Entries And Login Modules, Custom TAI, SSL Key and trust stores, Dynamic SSL Configuration etc.

The template will also allow you to select from one of the standard orchestrations to use with this template, if you don't want to create the orchestration yourself through the project orchestration tab. You can use the provided template as a "starting point" and amend it later through the project orchestration tab.

On saving the panel once the fields are filled in, all necessary configuration is generated in the projects. The completed environment definition can be used to perform a deployment to the target, which will create or update the scoped WebSphere objects such as database providers, clusters, jms providers etc. This configuration can also be used as the basis to "clone" further downstream environments in the same or other cells.

The configuration is then packaged into a versioned "Deployment Archive" for later deployment to one or more target environments.

The configuration files can be amended over time and built into versioned packages (that mirror the tags or labels in your Scm system) to allow for a set of packages to be built up. The user may then deploy whichever package, at whichever version they require to any of the supported target environments, rolling forward or back as required.

Editing template values

If a project is created from a template, then all the "changing" properties are already stored in the data dictionary file.

In order to edit any of the template values you just need to go under the "Orchestration" tab to the "Data Dictionary" tab. Here you'll be able to modify any of the values you previously set when creating the project.


This is separately licensed plugin that is not shipped with the framework. Please contact MidVision sales to obtain a copy of this plugin. This plugin interacts with IBM software, which may require a separate license.