Tuesday, March 25, 2008

Settings, attributes and option default values

The ControlTier 3.1 framework includes a pretty elegant set of rules and conventions for managing the options used in command handlers. Whereas prior to 3.1 the delivery of model data values into a particular command context was fairly unstructured, there is now an ordered set of steps to achieve this that offers the predictability of an established order of precedence.

Reviewing the following excerpt from a module's type XML:
<?xml version="1.0" encoding="UTF-8"?>

<!--
type-xml.generated.date: Wed Mar 07 11:53:24 PST 2007
type-xml.generator.class: com.controltier.shared.cli.ConvertTypeRDFToXML
type-xml.author: $Author$
type-xml.id: $Id$
-->

<types xmlns:cmd="http://open.controltier.com/base/Modules/Commands#" xmlns:module="http://open.controltier.com/base/Modules#" xmlns:type="http://open.controltier.com/base/Types#">
.
.
.

<type role="concrete" uniqueInstances="true" name="HsqldbRdbJavaHome" order="Setting">
<description>JAVA_HOME to use to run a Hypersonic SQL database server instance</description>
<supertype>
<typereference name="HsqldbRdbSetting"/>
</supertype>
<attributes>
<attribute name="hsqldbRdbJavaHome" type-property="settingValue"/>
</attributes>
</type>

.
.
.

<type role="concrete" uniqueInstances="true" name="HsqldbRdb" order="Service">
<description>A Hypersonic SQL database service</description>

<supertype>
<typereference name="Rdb"/>
</supertype>

<attributes>
<attribute-default name="hsqldbRdbJavaHome" value="${env.JAVA_HOME}"/>
.
.
.
</attributes>

<constraints>
<dependency-constraint enforced="false" kind="child">
<allowedtypes>
.
.
.
<typereference name="HsqldbRdbJavaHome"/>
.
.
.
</allowedtypes>
<singletontypes>
.
.
.
<typereference name="HsqldbRdbJavaHome"/>
.
.
.
</singletontypes>
.
.
.
</constraints>
.
.
.
<commands>
.
.
.
<command name="startService" description="Start the Hypersonic SQL database server instance" command-type="AntCommand">
<opts>
.
.
.
<opt parameter="javahome" description="Value of JAVA_HOME" required="false" property="opts.javahome" defaultproperty="entity.attribute.hsqldbRdbJavaHome" default="${env.JAVA_HOME}" type="string"/>
</opts>
</command>
.
.
.
</commands>
</type>
</types>

... starting from the startService command definition:
  • By convention, the goal is to make every configurable property used by a command's implementation available via an option definition.
  • Each option's property (in this case "property=opts.javahome") contains a value potentially provided from one of a number of sources in the following order of precedence:
  1. The value can be provided via the command line when the command is executed, otherwise ...
  2. The value will be initialized from a default property (i.e. defaultproperty="entity.attribute.hsqldbRdbJavaHome") if it is specified and exists, or ...
  3. The default value specified as an option attribute (default="${env.JAVA_HOME}") will be used.
  • If none of these sources are satisfied the option property is left unset, or, if the "required" attribute is set to "true", command execution fails.
This said, note how the default property is assigned using an "entity attribute" property value which arises from the Workbench project (i.e. the type/object model) as follows:
  • The properties intrinsic to each type can be assigned a general attribute name.
  • By convention, a setting type's "value" is assigned such a name (in this case the "HsqldbRdbJavaHome" setting type defines the "hsqldbRdbJavaHome" attribute naming the setting's value.
  • Adding the setting as an allowed singleton resource of the deployment type whose command implementation(s) wish to exploit it makes an attribute value available to objects of that type (see the constraints tab of the type page, and the properties tab of the object page for each module for the list of entity attributes).
Finally, note that entity attribute properties constructed in this fashion can receive values in the following ways:
  1. A resource relationship is setup and the entity attribute value is imported from the setting object.
  2. No such relationship is established and a so called "type level default attribute" value defined directly in the type.xml is used instead (the "attribute-default" value of "${env.JAVA_HOME}" in this case).
So, in summary, the value of "opts.javahome" in the example will come from one of the following sources in order of precedence:
  1. A value provided on the command line when the command is executed.
  2. A HsqldbRdbJavaHome setting value (from a child resource).
  3. The type level attribute default value allowed by the HsqldbRdb type's constraints.
  4. In cases where no type level attribute default value exists, the default value specified on the command's option definition (redundant in this case).
Anthony Shortland.
anthony@controltier.com

Here comes CTL -- a new automation tool with deep roots

We're happy to announce the initial release of our latest project, CTL.

What is CTL?
CTL is a flexible distributed control dispatching framework that enables you to break management processes into reusable control modules and execute them in distributed fashion over the network.

What does CTL do?
CTL helps you leverage your current scripts and tools to easily automate any kind of distributed systems management or application provisioning task. Its good for simplifiying large-scale scripting efforts or as another tool in your toolbox that helps you speed through your daily mix of ad-hoc administration tasks.

What are CTL's features?
CTL has many features, but the general highlights are:

* Execute sophisticated procedures in distributed environments - Aren't you tired of writing and then endlessly modifying scripts that loop over nodes and invoke remote actions? CTL dispatches actions to remote controllers with network transparency (over SSH), parallelism, and error handling already built in.

* Comes with pre-built utilities - CTL comes with pre-built utilities so you don't have to script actions like file distribution or process and port checking.

* Define your own automation using the tools/languages you already know - New controller modules are defined in XML and your scripting can be done in multiple scripting languages (Perl, Python, etc.), *nix shell, Windows batch, and/or Ant.

* Cross platform administration - CTL is Java-based, works on *nix and Windows.

What is CTL's relationship to other ControlTier projects?
AntDepo and CTL share the same code roots. CTL is a re-factoring and enhancement of the original AntDepo code base. While AntDepo is primarily used as a component within the larger ControlTier Application Service Provisioning System, CTL is designed to be fully usable as a standalone tool.

In the future, CTL will replace AntDepo within the ControlTier Application Service Provisioning System.

If you are new to ControlTier's automation tools, CTL is definitely where you want to start.

As always, please jump on the mailing list to tell us what you think, ask questions, or provide feedback. We always love hearing from our users (seriously!).

EDIT:
1. For more information about the motivation behind the CTL tools, check out this post on the dev2ops.org blog.

2. All information on how to use CTL can now be found on the ControlTier Wiki.

Wednesday, March 19, 2008

Converting Settings for use with ProjectBuilder

I recently posted the procedure for converting modules to ProjectBuilder. This handles any Deployment and Package sub-types you may have in your Workbench project, but there is still the question of what to do about project specific Setting sub-types (Nodes are handled implicitly by depot-setup, of course).

As it turns out, there's no method of automatically converting Setting sub-types, just a set of rules and conventions we follow to manually add settings definitions to existing type.xml files:
  • By convention settings type definitions are added to the type.xml of the module that most logically "owns" them (i.e. usually the module that uses them).
  • Also by convention, we group related sets of settings as sub-types of an abstract "container" type (though this is certainly not required), so the first type to add might be something like:
    <type role="abstract" uniqueInstances="true" name="JBossSetting" order="Setting">
    <description>A JBoss Setting</description>

    <supertype>

    <typereference name="Setting"/>

    </supertype>

    <constraints>

    <dependency-constraint enforced="false" kind="parent">

    <allowedtypes>

    <typereference name="JBossServer"/>

    </allowedtypes>

    </dependency-constraint>

    </constraints>

    </type>

  • Note that the only type attributes allowed for settings are "settingType", "settingValueEncrypted", "settingValue", and "referrers". This dictates what you can include in the attributes and constraints section of the type definition.
  • Next, add each setting type to the type.xml. e.g:
    <type role="concrete" uniqueInstances="true" name="JBossJavaHome" order="Setting">
    <description>JAVA_HOME for JBoss</description>
    <supertype>
    <typereference name="JBossSetting"/>
    </supertype>
    <attributes>
    <attribute name="javaHome" type-property="settingValue"/>
    </attributes>
    <constraints>
    <dependency-constraint enforced="false" kind="parent">
    <allowedtypes>
    <typereference name="JBossServer"/>
    </allowedtypes>
    </dependency-constraint>
    </constraints>
    </type>

One thing to bear in mind is that constraint references to types that are defined in separate modules (most often the case with Setting sub-types) are resolved only when all the types are loaded into the project. Using ProjectBuilder's "load-library" command (or loading a seed from the Workbench administration page) is the most obvious way to achieve this without the order in which modules are added to the project being significant.

Anthony Shortland,
anthony@controltier.com

Friday, March 07, 2008

An example JBoss build and deployment project

[Edit: also see the demo section of the ControlTier Wiki for an up to date version of this]

(It was when I posted these notes to our Google group that I realized that there's real value in being able to post HTML. With that in mind. I'm re-posting here complete with links and formatting!)

These notes document using the ControlTier Elements Solution Library to build and deploy Sun's "Duke's Bank" sample application (from their J2EE 1.4 Tutorial) to JBoss 4.0.3SP1 following the "Getting Started with JBoss 4.0" guide. I've tested the project on Windows 2003 Server R2 and CentOS 4.5 (and it can also be easily adapted to run on other Unix/Linux platforms). You'll need around 4GB of disk space and 1GB of memory on a reasonably up-to-date system.

The basic idea was to implement the instructions from chapter 4 as a Workbench project building and deploying the sample application to a development environment on the (single) node (localhost) that's also running Workbench and Jobcenter.

1) Install
  • Install the latest version of the Java 1.5 SDK available from Sun into "$CTIER_ROOT/pkgs" (for use both by ControlTier - instead of Java 1.4 - and the Dukes Bank application).
  • Create a new ControlTier project called "DukesBank" (JBoss 4.0 J2EE 1.4 "Duke's Bank" sample application project) using Workbench.
  • Download the Elements Solution Library 1.0 seed from Sourceforge and "Import" it using the Workbench administration page (note that you can also check out the library's source and use ProjectBuilder to build and load the library).
2) Configure
  • Configure a ProjectBuilder object and download from Sourceforge and load into Workbench either the Linux or Windows version of the objects as required (note that on Unix/Linux it is assumed installation will occur to "~/dukesbank", while on Windows to "C:\dukesbank") by cutting and pasting the appropriate commands:

    $ ad -p DukesBank -m Deployment -c Register -- -name elements -type ProjectBuilder -basedir $CTIER_ROOT/src/elements -installroot $CTIER_ROOT/target/elements -install
    .
    .
    .
    For more information about this object run: ad -p DukesBank -t ProjectBuilder -o elements -c Get-Properties -- -print
    [command.timer.Deployment.Register: 4.150 sec]

    $ ad -p DukesBank -t ProjectBuilder -o elements -c load-objects -- -format projectxml -filename $CTIER_ROOT/src/elements/demo/DukesBank/objects/linux.xml
    Loading "/home/demo/ctier/src/elements/demo/DukesBank/objects/linux.xml" ...
    1 file(s) have been successfully validated.
    Processing /home/demo/ctier/src/elements/demo/DukesBank/objects/linux.xml to /home/demo/ctier/antdepo/depots/DukesBank/deployments/ProjectBuilder/elements/var/null226801341.xml
    Loading stylesheet /home/demo/ctier/antdepo/depots/DukesBank/lib/ant/modules/ProjectBuilder/lib/load-objects/projectxml/project.xsl
    Mapping XML to properties ...
    Collecting object attributes ...
    Batching object attribute updates ...
    Batching resource and referrer updates ...
    Executing batch update ...
    [command.timer.load-objects: 20.873 sec]
    load-objects completed. execution time: 20.873 sec.

    C:\>ad -p DukesBank -m Deployment -c Register -- -name elements -type ProjectBuilder -basedir %CTIER_ROOT%\src\elements -installroot %CTIER_ROOT%\target\elements -install
    .
    .
    .
    [command.timer.Deployment.Register: 2.359 sec]

    C:\ctier\tmp>ad -p DukesBank -t ProjectBuilder -o elements -c load-objects -- -format projectxml -filename windows.xml
    Loading "C:\ctier\tmp/windows.xml" ...
    1 file(s) have been successfully validated.
    Processing C:\ctier\tmp\windows.xml to C:\ctier\antdepo\depots\DukesBank\deployments\ProjectBuilder\elements\var\null580203106.xml
    Loading stylesheet C:\ctier\antdepo\depots\DukesBank\lib\ant\modules\ProjectBuilder\lib\load-objects\projectxml\project.xsl
    Mapping XML to properties ...
    Collecting object attributes ...
    Batching object attribute updates ...
    Batching resource and referrer updates ...
    Executing batch update ...
    [command.timer.load-objects: 6.906 sec]
    load-objects completed. execution time: 6.906 sec.

  • Download the required third-party packages from the Internet and upload them to Workbench via their "PlatformZip" and "JBossZip" object pages: apache-ant-1.7.0-bin.zip, J2EE 1.4 Tutorial Update 7, jbossj2ee-src.zip (note that you must unpack the required Zip archive from the downloaded Zip), and jboss-4.0.3SP1.zip. (Note: Make sure that you set the DAV directory path to "/pkgs/DukesBank/zip/zips" to match the object XML when uploading the package files).
  • Install the objects:

    $ depot-setup -p DukesBank -a install
    "Install" command running for object: (AntBuilder) development
    "Install" command running for object: (ProjectBuilder) elements
    "Install" command running for object: (Updater) development
    "Install" command running for object: (Site) development
    "Install" command running for object: (JBossServer) development

    C:\>depot-setup -p DukesBank -a install
    "Install" command running for object: (AntBuilder) development
    "Install" command running for object: (ProjectBuilder) elements
    "Install" command running for object: (Updater) development
    "Install" command running for object: (Site) development
    "Install" command running for object: (JBossServer) development
  • Download the sample job definitions from Sourceforge and install them into Jobcenter using "Upload Job XML File ..." via the "Create a new Job ..." page.
3) Run
  • Deploy the packages that support building the application using Ant and deploy and start the empty JBoss server instance (you'll be able to pick up the JBoss server page at http://localhost:8180 since JBoss is configured to run on non-default ports to avoid colliding with Workbench):

    [jboss@development dukesbank]$ ad -p DukesBank -t Updater -o development -c Deploy -- -resourcetype 'AntBuilder|Site'
    Start: "Run the coordinated deployment cycle across the configured Sites." commands: dispatchCmd
    begin workflow command (1/1) -> "dispatchCmd -command Deploy -resourcename .* -resourcetype AntBuilder|Site" ...
    dispatching command: "Deploy " to: (AntBuilder) development, (Site) development ...
    .
    .
    .
    dispatched command: Deploy completed for: (AntBuilder) development, (Site) development
    end workflow command (1/1) -> "dispatchCmd -command Deploy -resourcename .* -resourcetype AntBuilder|Site"
    [command.timer: 29.828 sec]
    Completed: execution time: 29.828 sec

    C:\>ad -p DukesBank -t Updater -o development -c Deploy -- -resourcetype "AntBuilder|Site"
    Start: "Run the coordinated deployment cycle across the configured Sites." commands: dispatchCmd
    begin workflow command (1/1) -> "dispatchCmd -command Deploy -resourcename .* -resourcetype AntBuilder|Site" ...
    dispatching command: "Deploy " to: (Site) development, (AntBuilder) development ...
    .
    .
    .
    dispatched command: Deploy completed for: (Site) development, (AntBuilder) development
    end workflow command (1/1) -> "dispatchCmd -command Deploy -resourcename .* -resourcetype AntBuilder|Site"
    [command.timer: 41.531 sec]
    Completed: execution time: 41.531 sec

    (Note that this command can also be run from Jobcenter using the "development.Deploy" job and setting the "resourcetype" to "AntBuilder|Site" from the "Choose Options and Run Job ..." page).
  • Edit the client JNDI properties file in the J2EE Tutorial source to adjust the hard-coded naming provider port (this is necessary since JBoss is deployed using non-default ports to avoid colliding with Workbench):

    $ pwd
    .../dukesbank/j2eetutorial14/examples/bank/dd/client
    $ diff jndi.properties jndi.properties.orig
    3c3
    < url="jnp://localhost:1199"> java.naming.provider.url=jnp://localhost:1099
  • Run the application build and deployment cycle to build the Duke's Bank application from source, initialize the database schema and deploy to JBoss:

    $ ad -p DukesBank -t Updater -o development -c BuildAndDeploy -- -buildstamp 20080222.0
    Start: "Run the coordinated end-to-end the build and deployment processes across the configured Builders and Sites.." commands: Build,Change-Dependencies,Deploy ...
    begin workflow command (1/3) -> "Build -buildstamp 20080222.0" ...
    Start: "Run the coordinated build cycle across the configured Builders." Beginning build process with the following builders: (AntBuilder) development ...
    workflow command (1/1) -> "dispatchCmd -buildstamp 20080222.0 -command Build -resourcetype [^\.]*Builder -dispatchOptions buildstamp" ...
    .
    .
    .
    Completed: execution time: 31.322 sec
    end workflow command (3/3) -> "Deploy -buildstamp 20080222.0"
    [command.timer.DukesBank.Updater.development.BuildAndDeploy: 2:14.950 sec]
    Completed: End-to-end build and update process completed: Build,Change-Dependencies,Deploy. execution time: 2:14.950 sec

    C:\>ad -p DukesBank -t Updater -o development -c BuildAndDeploy -- -buildstamp 20080222.0
    Start: "Run the coordinated end-to-end the build and deployment processes across the configured Builders and Sites.." commands: Build,Change-Dependencies,Deploy ...
    begin workflow command (1/3) -> "Build -buildstamp 20080222.0" ...
    Start: "Run the coordinated build cycle across the configured Builders." Beginning build process with the following builders: (AntBuilder) development ...
    workflow command (1/1) -> "dispatchCmd -buildstamp 20080222.0 -command Build -resourcetype [^\.]*Builder -dispatchOptions buildstamp" ...
    .
    .
    .
    Completed: execution time: 11.313 sec
    end workflow command (3/3) -> "Deploy -buildstamp 20080222.0"
    [command.timer.DukesBank.Updater.development.BuildAndDeploy: 2:06.844 sec]
    Completed: End-to-end build and update process completed: Build,Change-Dependencies,Deploy. execution time: 2:06.844 sec

    (Note that this command can also be run from Jobcenter using the "development.BuildAndDeploy" job and setting the "buildstamp" from the "Choose Options and Run Job ..." page).
If you don't want to go through this setup process, I've prepared a CentOS 4.5 VMware virtual machine with the demonstration installed and ready to roll that I plan to post to Sourceforge imminently. I'll also post the DukesBank project archive file if you'd like to avoid the type/object model setup steps and cut right to the chase finishing up configuration and running the demonstration.

Thanks,

Anthony.

Elements module library source re-structured

I've just restructured the Elements module library source on Moduleforge to establish its own separate trunk, branches and tags.

The trunk has been copied from the 1.0 branch, and in addition I've established a new 2.0 working branch as a copy of the trunk.

New development will proceed on the 2.0 branch aimed at integrating an out of the box end-to-end Java Server build and deployment solution based on:
  • CVS and Subversion source code control
  • Cruise Control based continuous integration
  • Ant and Maven based builds
  • Tomcat and JBoss application servers
  • HSQLDB and Derby Java based databases
In addition, we plan to formally integrate and document the Duke's Bank sample application as a demonstration application.

By the way, I'm the only one who likes the name "elements" it seems, but there doesn't seem to be any constructive alternative "short" names out there that aren't acronyms that have already been grabbed by the Java guys (JSSL, JSL, etc)!

The "full" name of the library is "Java Server Module Library". Any ideas for a catchy moniker that could supplant "elements" in the source base, etc? Or, like me, are you satisfied with the "elemental" appropriateness of the existing name? Or, more likely, do give a toss at all?

Thanks,

Anthony.

Thursday, March 06, 2008

Converting Workbench modules for use with ProjectBuilder

ProjectBuilder is one of the key new features of ControlTier 3.1. This base type allows architects and administrators to manage their projects as a set of (XML) source using development tools of choice as opposed to solely using Workbench.

The thing is, many people already have sets of modules created under Workbench and therefore need to convert them for use with ProjectBuilder. Since this process is not currently well documented on Open.ControlTier, here's a quick cheat sheet:
  • Setup a minimal ProjectBuilder object for your project. By convention, the ProjectBuilder is given a library name ("mymodules" in this case) that reflects the combined intent of the set of modules it manages.

    $ ad -p MyProject -t ProjectBuilder -o mymodules -c Register -- -basedir \${env.CTIER_ROOT}/src/mymodules -installroot \${env.CTIER_ROOT}/target/mymodules -install
    .
    .
    .
    For more information about this object run: ad -p MyProject -t ProjectBuilder -o mymodules -c Get-Properties -- -print


    [command.timer.Deployment.Register: 4.123 sec]
  • By the way, the base directory is usually put under source code control to provide version management for the module source. A good example of this is the structure of the Elements Module Library source on ModuleForge.
  • Create the minimal base directory structure:

    $ mkdir -p $CTIER_ROOT/src/mymodules/modules
  • Copy in the latest version of your module(s) from Workbench's WebDAV working directory (Note that these commands assume you are setting up a ProjectBuilder development environment on the same system where Workbench is deployed. This need not always be the case):

    $ cd $CTIER_ROOT/src/mymodules/modules
    $ cp -r $CATALINA_BASE/webapps/webdav/MyProject/modules/MyBuilder .


  • Convert the module's RDF files to type XML format:

    $ ad -p MyProject -t ProjectBuilder -o mymodules -c convert-rdf -- -type MyBuilder
    .
    .
    .
    convert-rdf completed. execution time: 0.888 sec.

  • Remove extraneous RDF and property files from the module source:

    $ rm MyBuilder/*.rdf MyBuilder/*.properties
  • Test building the module from source and uploading it to the project:

    $ ad -p MyProject -t ProjectBuilder -o mymodules -c build-type -- -type MyBuilder -upload
    Building type using the buildmodule.xml via classloader

    converting type.xml for module: MyBuilder

    packaging module: MyBuilder

    Building jar: /home/anthony/ctier/target/mymodules/modules/MyBuilder-1.jar

    calling repoImport ...

    processing files in directory: /home/anthony/ctier/target/mymodules/modules

    Uploading jar: /home/anthony/ctier/target/mymodules/modules/MyBuilder-1.jar to server: localhost ...

    [command.timer.repoImport: 3.058 sec]

    repoImport completed. execution time: 3.058 sec.

    [command.timer.build-type: 4.112 sec]

    build-type completed. execution time: 4.112 sec.

QED.

Anthony Shortland.

Friday, February 29, 2008

Initial "Duke's Bank" JBoss demonstration application posted

One of the key ways that ControlTier's commercial activities directly benefit our Open Source community is via the Solution Libraries maintained at the Moduleforge project.

The experience gained implementing solutions for our commercial customers is made generally available via these libraries, making Moduleforge the means of kick-starting projects by supplementing the base types/modules distributed with the ControlTier framework.

One example of these libraries is "Elements" - a "grab bag" of modules largely concerned with automating the Java server application build and deployment life-cycle with modules covering continuous integration with CruiseControl, builders such as Ant and Maven, application servers such as Tomcat and JBoss, and associated services such as Apache web server and Apache MQ.

There's plenty of work left to extend the scope of Elements to cover a broader set of technologies as well as improve the standard of the solution libraries documentation.

We made a solid step in the right direction this week by releasing notes on using the library to build and deploy Sun's "Duke's Bank" sample application (from their J2EE 1.4 Tutorial) to JBoss 4.0.3SP1, thus providing a clear example to JBoss users of the benefits of using ControlTier.

The plan is to make "Duke's Bank" the primary sample application of a major revision of Elements dubbed the "Java Server Solution Library" that we're preparing ahead of next month's SaasSCon in Santa Clara.

Anthony Shortland.
anthony@controltier.com



Saturday, February 09, 2008

Upgrading to ControlTier 3.1-rc2

For those of you who are upgrading an existing ControlTier installation, Anthony has posted a set of tips on the mailing list to ensure things go smoothly.

You can find them here:
http://groups.google.com/group/controltier/browse_thread/thread/40fbdf43139d2f3c?hl=en

If you aren't already subscribed to the mailing list (run by google groups), I suggest doing so. Its a timely source of information and the quickest way to communicate with project developers.

ControlTier 3.1-rc2 Released

Download it here: http://sourceforge.net/project/platformdownload.php?group_id=151079

What's New since 3.1-rc1:

A Maven 2 plugin was created for antdepo, and a Maven archetype was created to support using maven to build a ControlTier Library Jar.

Changes since 3.1-rc1:

bugfix: Change-Dependencies command used by Updaters now correctly allows multiple package files with the same type and version when allowMultiples is true, but the dependency constraints between the deployment and its packages is not exactly specified.

bugfix: a bug preventing Transform creation was fixed.

Installer:

Improve ability to do 'upgrade' installations.

Base types:

Builder repoImport command now supports a 'separator' cli option, allowing the separator between package base and version to be something other than the default of a hyphen character '-'. Also added as an attribute named 'packageSeparator' which can be set with an appropriate Setting subtype. Some typo fixes.

Builder Subversion support improved: scmModule parameter was not being used in some cases.

ProjectBuilder: The meaning of the 'basedir' commmand-line flag was changed to be the top-level directory containing the modules directory.

Wednesday, February 06, 2008

ATG Commerce Solution Library 1.3 update posted to ModuleForge

One of the key lines of business for ControlTier is delivering automated provisioning solutions for ATG based e-commerce sites. Over the last three years we've been building up best-practice implementation skills that we've distilled into a freely available integrated solution library. 

I'm happy to announce that we've just posted a significant update to version 1.3 of our ATG Commerce Platform Solution Library to Moduleforge. This release consolidates the results of a good six months work focussing on JBoss based ATG build and deployment management with a number of key customers including ATG On-Demand Hosting Services themselves.

The release includes detailed documentation on how to build a demonstration code and data provisioning solution based on the Pioneer Cycling sample application running on JBoss, Solid and Linux. This demonstration is a solid starting point for anyone interested reviewing the functionality of our Solution Library; in fact, our consultants build on the Solution Library as the foundation for building custom solutions to meet our clients' site-specific requirements.

Please go ahead and post feedback on the release here or at our main discussion group.

Thanks,

Anthony Shortland,
ControlTier Software, Inc.