Is Implementer fairly separated from that process? I mean, you've
constructed the list of members you're going to work with using filters, so
you type those in again to check-out and then select them manually again
from the big list of everything you have checked out to promote them to
production?
From: Dave Shaw <daveshaw@xxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 08/21/2013 01:41 PM
Subject: Re: [WDSCI-L] Working with projects
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
We have a project system with an in-house tool we call I5DE that creates a
project library and project library list for each project. In RDi, most of
us create a separate connection for each project, which calls an api to set
the defined library list. We then create project filter pools and filters
over the project library. We use Implementer to check the sources and
objects for the project out to the project library, make the changes using
RDi (or green screen, for those who haven't moved up to RDi yet), test in
the project libraries using data extracted from production into the project
library, promote the approved changes using Implementer, and then delete
the completed projects - libraries, filters, pools, and connections.
Production is locked - we can't change it, but many of use have reference
filter pools and filters for finding things we need in production, for when
we can't remember names well enough to use Ctrl-Shift-A. Works fairly
well, although copies of large data files in the project libraries make it
something of a space hog at times.
Dave Shaw
Mohawk Industries
________________________________
From: Paul Bailey <PaulBailey@xxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Sent: Wednesday, August 21, 2013 10:18 AM
Subject: Re: [WDSCI-L] Working with projects
I use source member filters in the Remote Systems Explorer perspective to
group together source members in a "project". They link directly to the
server source, so bypass that extra step of promotion with iProjects. With
careful and consistent naming of the filters you can keep control of your
work history.
Expanding on that, I use multiple connections to the same IBM i (to control
library lists) and multiple profiles (to separate old, current and "on
hold" projects.)
You don't get to move projects around easily (you need to select the
contained source members and operate on them that way) but this is the most
comfortable method for me that I've found so far.
I'm always eager to learn of other people's setups.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
midrange.com
