Rational Team Concert (RTC) is gaining in popularity these days, and we are certainly seeing more and more of it in our business. RTC provides several benefits and features that span development silos. Traditionally, an IT shop would have a different SCM and build system for distributed systems, more for .NET, and yet something completely different for enterprise platforms (mainframe, AS/400). We've blogged a lot about the build engine for RTC for the distributed systems. Now, we want to introduce you to the build system for System i/z, and how RTC handles build and promotion and deployment.
Rational Team Concert: Using the Enterprise Extensions component promotion feature
First, let's get you started with an overview of the component promotion. A component is a piece of the application that usually results in a load module, a Java WAR file, or Java JAR file. In this case, we are talking about a load module.
Rational Team Concert: Using the Enterprise Extensions work item package and deployment feature
Next, we can talk about how atomic changes at the work item level can be deployed without deploying the whole component.
Then, these next two videos go into further detail about how to promote change sets associated with work items and change requests.
Rational Team Concert: Using Enterprise Extensions work item promotion feature Part 1
Rational Team Concert: Using Enterprise Extensions work item promotion feature Part 2
Now most of that material was specific to the System z mainframe, but it does share much in common with IBM i as well. These next articles show more about IBM i applications specifically. Note these will take you direct to the Jazz.net site.