If I may butt into this with a related question?

I have downloaded RDP V8 and RAD Standard Edition for Websphere V8 and
have been trying to use the Packing Utility to create a repository for
installation via HTTP server. One of the options to include is the WAS 6.1
Test environment, which according to the documentation is part of the
above RAD version, but it keeps asking for Disk 1 of WAS 6.1 Test
So, I have done some googling and cannot find a reference to getting this
option as a download, Anyone got any ideas about where to look or if I am
doing something wrong?


Senior Technical Consultant
SMART Team Leader

Royal Pavilion, Wellesley Road, Aldershot, Hampshire, GU11 1PZ, UK.
Financial Services EMEA | p:+44 1252 536681 | f:+44 1252 534022 | m:+44
7827 843323 | josulli4@xxxxxxx | www.csc.com/uk

CSC â This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. NOTE: Regardless of content, this e-mail shall not
operate to bind CSC to any order or other contract unless pursuant to
explicit written agreement or government initiative expressly permitting
the use of e-mail for such purpose â CSC Computer Sciences Limited â
Registered Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire,
GU11 1PZ, UK â Registered in England No: 0963578

Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
23/12/2010 18:09
Re: [WDSCI-L] Combining RBD & RDI

Maybe this will help: think of each component (RBD, RDP, RAD) as a
feature. RDP provides the RPG development tools. RBD provides EGL.
RAD provides Java EE (non-EGL). If you want to develop just RPG green
screen, you install RDP only. If you want to do RPG and EGL, you
install RDP and RBD. If you want to do Java EE with RPG business logic,
you install RDP and RAD.

We in the i community had some packaged pieces. WDSC7 was basically RPG
and Java EE (what today would be RDP and RAD). RDi was just RPG
development tools, the same as RDP. RDi-SOA was RDi with EGL, so you
need RDP and RBD for equivalent functionality.

Does that help?


Could IBM possibly make this any more confusing?? Joe you did a great
of explaining it but it still almost as clear as mud.


From: Joe Pluta<joepluta@xxxxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
for System i& iSeries<wdsci-l@xxxxxxxxxxxx>
Date: 12/22/2010 10:00 PM
Subject: Re: [WDSCI-L] Combining RBD& RDI
Sent by: wdsci-l-bounces@xxxxxxxxxxxx

This is exactly correct. The idea behind the entire Rational delivery
mechanism is that you can buy separate components and then install them
together to create a workbench. For example, to enable the approximate
capabilities of the old WDSC you would install RDP and RAD together;
this gives you RPG development tools and Java EE development. The
RDi-SOA equivalent is an installation of RDP and RBD.

Note that you should also be able to install a second component into an
existing installation of another component. For example, installing RBD
into an existing RDP is (nearly) the same as installing them together,
although as Duane notes installing them together is probably faster.
You can also install fix packs at the same time; this is especially
helpful for network installs.

One caveat: there is currently a mismatch between RDP and RBD that will
NOT allow you to install RBD into RDP, although you can install RDP into
RBD or install them together. Well, technically you can install RBD
into RDP, but the workbench will not come up and you have to uninstall
RBD to get your RDP back. That should be fixed sometime in Q1.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.