I suppose we are a little, but this is more general discussion for more than Websphere/Java folks so I placed it here. I will move it if so directed :-)
User actions are probably the way I will go based on what I discovered this weekend, but the question still stands about what would folks like to see for editing that they are bugged by today.
Understood on RTC 4.x. We're implementing 4.0.1 for work management and team requirements and testing currently. It's not always a simple road though. Even with training and guidance you have to adapt to your team style and processes.
I fully understand that my SVN solution is handling the source management aspect of the equation solely at this point, but I really want to equalize the source management process for my team on all platforms.
Possibly the right answer would be to fully adopt something like RTC SCM across the board, but right now we have our hands full just getting used to all the RTC modules and best practices.
I'll check out the PDF on your site for more info. Feel free to contact me offline if you want to discuss more.
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
date: Mon, 21 Jan 2013 00:14:50 -0500
from: Jeffrey Tickner <jtickner@xxxxxxxxxxxxxxxxx>
subject: Re: Remote Systems Explorer in RDP - What would you do to
make it better ?
First I'll say we are diverging into the wdsc list territory I think Chuck answered accurately for most admins and managers that direct access to introduce changes to production environments would not be welcome.
User actions in RDP can be defined to do almost whatever you want within your authority, certainly you could call programs that adopt authority so what you desire is possible now without even developing a plugin.
For working with one or more specific source members within RTC 4 the sparse loading is really slick once the infrastructure has been built.
But do you want change management in RDP or source management?
They are 2 different things, SVN only provides source management, similar to RTC, but RTC provides a much richer team communication environment.
There is package management in RTC 4, via the build process, and RTC 4 has enhanced the dependency build to the point that it is useful for file changes.
Change management is built on top of source management, providing a state full process of testing before deployment to production.
From my experience in CM this is rarely desired by developers but often required by other stakeholders.
There is rarely such thing as a quick field change on the i and most CM packages will help the developer build a complete set of impacted objects to deploy to test and then to production with minimal downtown.
In my experience if you give a developer a quick path to make a program change in production the next thing you know they are making a quick field change in production along with 99% of the programs impacted and the call about the 1% they missed comes at 2AM.
Speaking from experience of 15 years in CM and being woken up at 2AM...
As always if you want full intelligent management of dependencies during deployment of changes down to the ILE procedure level from RDP/RTC the then <vendor> the Arcad Rational Power Pack is the best solution http://public.dhe.ibm.com/common/ssi/ecm/en/rab14064usen/RAB14064USEN.PDF
Please only print this email if really necessary Jeffrey TICKNER Technical Resource jtickner@xxxxxxxxxxxxxxxxx
55, rue Adrast?e - Parc Altais F-74650 1, Phoenix Mill Lane - Suite 203 -
CHAVANOD Peterborough NH 03458 - USA
Tel. +33 (0)4 50 57 83 96 Tel. + 1 603 371 9074 ext 505
Cell. +33 (0)6 11 15 69 59 Toll. free +1 800 676 4709 ext 505
***This e-mail and its attached documents are confidential and intended solely for the use of the addressee(s). ARCAD Software can in no way be held responsible for any damage resulting from an incident involving security, integrity, virus or transmission delay. As the integrity of this message cannot be guaranteed on Internet, the ARCAD Software company cannot be held responsible for its contents. Any unauthorized use or dissemination is prohibited.***
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l
End of MIDRANGE-L Digest, Vol 12, Issue 143