|
This is a synopsis of my experience with RTC 3.0
I downloaded RTC 3.0, to give it a whirl with WDSC and my beloved IBM i.
Tried to install it on my Windows 7 PC. Went well until it was time to
run the setup wizard. It insists that my PC be known to the network at
mypc.someorg.tld It isn't. ipconfig shown my name as mypc without a
domain name and what's more, I'm apparently unreachable from the network
by that name. So now I can uninstall it from my PC.
But! There's an IBM i RTC server as well. Which requires Websphere App
Server; even though Apache and Tomcat are supported under Windows, they
are not supported for the i. Assuming I could convince the right people
to allow me to run WAS, I'd probably be blamed for every performance
problem from now until the end of time. Maybe I'll go that route, but
my margin of success looks thin, given we're using Apache/Tomcat already.
This might seem like whining; if so, I apologise. I'd love to run an
IBM product to help me convince my team to at least start tinkering with
collaborative source code management. It seems overly complex to me,
and I'm not afraid to run Cygwin binaries (grep, sed, tr) in a DOS .bat
file to automate importing data from external sources. I can't imagine
trying to turn this loose on someone who's hesitant about /looking/ at
RD Power.
My RTC experience meter remains at zero.
--buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.