Browse Prior Art Database

A system and method to share Jython utility projects among IBM Software Assembly Toolkit deployments

IP.com Disclosure Number: IPCOM000200323D
Publication Date: 2010-Oct-05
Document File: 1 page(s) / 27K

Publishing Venue

The IP.com Prior Art Database

Abstract

The IBM Software Assembly Toolkit (ISAT) is a tool that helps developers build installation, deployment and configuration packages. Using ISAT, a developer can develop individual Deployment Accelerators (DAs) to perform a single task (e.g. "Create a database" or "install DB2 client". These Deployment Accelarators can be combined and packaged with other Solution Accelerators to form an overall Solution Deployment.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Page 01 of 1

A system and method to share Jython utility projects among IBM Software Assembly Toolkit deployments

The IBM* Software Assembly Toolkit (ISAT) is a tool that helps developers build installation, deployment and configuration packages. Using ISAT, a developer can develop individual Deployment Accelerators (DAs) to perform a single task (e.g. "Create a database" or "install DB2** client". These Deployment Accelarators can be combined and packaged with other Solution Accelerators to form an overall Solution Deployment.

While ISAT contains a rudimentary solution for sharing variables and for sharing java code via shared libraries, there is no ISAT mechanism for sharing code for other languages, like jacl or jython which are used for WebSphere*** Application Server configuration. This invention discusses a means for sharing

jacl or other scriptin

To share jython, or other code within ISAT,

1. Create an ISAT deployment accelerator, DA1, that copies the target shared file, U1 (e.g could be a

y

choose the Windows Temp directory as a location.

2. Within the deployment accelerator DA1, create a variable, V1, that contains the file path to that file.

3. Use DA1 in any solution deployment, SD1, that requires the utility routines found in U1. This can be done in the following way:

a. Insert DA1 as a task in Solution Deployment SD1.

b. Override and share the variable V1 from DA1 into SD1. It is not necessary to rename the variable.

c. Compose a second deployment accelerator DA2, which executes a script U2....