Browse Prior Art Database

Self-installing build which conditionally targets both development and production environments Disclosure Number: IPCOM000012171D
Original Publication Date: 2003-Apr-15
Included in the Prior Art Database: 2003-Apr-15
Document File: 3 page(s) / 76K

Publishing Venue



Disclosed is a technique that generates a self-installing build which conditionally targets both development and production environments.

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

Page 1 of 3

  Self-installing build which conditionally targets both development and production environments

  Purchasers of IBM WebSphere Commerce must customize the base product to create a commerce site that is specific to their business requirements. To accomplish this, they will need a team of developers. Each developer is provided with a development environment where customization assets such as Enterprise JavaBeans(EJBs), Java classes, JavaServe Pages(JSPs), database scripts, and Extensible Markup Language(XML) documents can be created and modified. These assets will need to be collected from the individual developers and deployed to the production environment. These assets will also need to be distributed back to the developers to ensure that they are all working with the same environment. This process of moving assets from one or more development environments to the production environment and to the other development environments tends to be very error prone and often requires many manual steps. Various file assets need to be moved to various locations, configuration files need to be updated, database scripts need to be executed, deployment and configuration commands need to be invoked. Since the development environment is different from the production environment, two sets of manual instructions are required. The result is development environments are often inconsistent from each other and inconsistent with the production environment.

This disclosure describes a technique for consolidating all of the customization assets into a single self-installing archive that knows how to install itself in both the production environment and the development environment. An automated daily build process will package all of the assets into a JAR file that contains a program which automates all of the steps required to install these assets onto either the production environment or the development environment.

This technique has the following advantages: self- contained, easy for distribution self-installing, no manual steps repeatable install easily extended and modified

The first step of this technique is to ensure that all of the developed assets are being stored in a source control system. This centralizes the assets in one place. Automated daily builds extract all of the assets from the source control system and build them. Java files are compiled into class files, class files are then packed into jar files and all of the assets are packaged into a single jar file that contains a program that will perform the environment specific install. When you wish to upgrade a system to the latest build level, you simply copy the self-installing jar to the target system and issue "java -jar build_mmddyy.jar". This will invoke the install program that is contained in the jar. The install program will analyze the target environment and perform the install steps appropriate to that environment. The IBM WebSphere Commerce development environment being describe...