The fourth (and last but not least) step in the WOTI process is: Step 4 - Record Progress, Set an Example and Act as a Change Agent in the organization. It might not sound that exciting, but we're confident the results will eventually be thrilling!
We've recorded our progress on a weekly basis since we started, tracking our Inbox and Outbox.
The WOTI program began in the middle of week 1 on Wednesday, February 1st (see Fig 1). In Fig 2, the data for week 1 is extrapolated and adjusted to estimate the numbers of e-mails for the missing two days to build a full week. Note that the left side access are the team totals for our inboxes, while the right side axis is our team totals for our outboxes:
We are already seeing some encouraging results!
We are moving in the right direction with lower incoming and outgoing e-mail although we are not yet ready to scream victory ... We are going through a learning process as we continue to educate people on the value of WOTI. This requires passion, persistence and patience! (It took Luis Suarez time before he moved to the Canary Islands! Where would you be if your Inbox were empty?)
We strive to set ourselves as examples, but still act in our own way as change agents in this effort. We exchange our experiences, brainstorm and share knowledge on a weekly basis about what worked for each of us.
Leading organizational change with a great idea like WOTI requires a fundamental belief that there are long term values for ourselves and the overall organization and it is very rewarding to see everyday new adopters of the WOTI way of doing business! We hope that you are also on your way with your own WOTI initiative in your organization, and we'll be very happy to hear about your progress and look forward to learning from each other.
In the meantime, recording is in progress and we'll continue to update you with our findings and experiences in future blogs ...
Our interview today comes from Amsterdam to highlight Bertrand Durou. As another presenter for next week's IBM Innovate2010 conference, Bertrand will be speaking on "Closing the Loop: From Support Request to ALMRequest and Back with Client Lifecycle Management on IBM Rational ClearQuest ". Plus, meet Bertrand at the Support Cafe' (agenda here) where he'll be demoing Service Request (SR) and helping clients get enabled managing PMRs on-line with SR. Check out his interview below so you'll have things to talk about when you meet him next week in Orlando at Innovate2010! Tell us a little about yourself: who are you, what is your role in Rational Client Support? I am Bertrand Durou: 39, French working in Amsterdam, living with a Spanish wife and 2 kids... The job role is KT program manager. I'm teaching and leading troubleshooting methodology. But that's really only one small aspect of what I do everyday...
How long have you been working for IBM and Rational? 10 years this year, 5 in Rational, and 5 in IBM Rational.
What are you currently working on? Feeding this questionnaire
What project are you the most proud of? Lately and without doubt, the implementation in MTS organization, which end up with an Award in 2009. With this implementation, the design/architecture of a "sustaining engineering" workflow based on ClearQuest, and presented at Innovate 2010 Are you a gadget person? What type of gadgets do you use? I'm the proud owner of a Nokia 6021... I can call from anywhere in Europe and send sms
What is your favorite part of working for Rational Client Support? Working with a diverse and multi-national teams... And Clients. Totally different perspective everyday.
What are you passionate about? My family
Tell me about the biggest problem you've solved? Problem with ODBC connections since upgrading to the latest OS400 release... I had no knowledge of this set of technologies, but helped out the Engineer during the training workshop to separate in 4 different distinct problems, and fix the most important one during the workshop
How do you define success? The way the client is defining it at the beginning of the call
If you were stuck on a technology deprived island, what single technology could you not live without? ... None. Maybe a boat to go to a technology island
What is on your nightstand with regard to reading? Magasin Géneral et Le Photographe
This topic comes up frequently. Sometimes a customer will have a set of existing service tests and the server has been changed to require TLS 1.2 and the service tests no longer work. Or the customer is trying to record a new service test using the General Service Client and can't get a valid response after invoking the request.
The error message reported by RPT will be similar to:
RPWY0002E An exception occurred in com.ibm.rational.test.lt.models.wscore.transport.impl.HttpTransporterImpl
The default value used by General Service Client is SSL_TLS. However RPT will not use the property com.ibm.jsse2.overrideDefaultProtocolbut use the property com.ibm.rational.test.lt.soa.ssl.protocols instead
We need to set this property in two separate places so it can be used for recording as well as playback
Like for recording we need to set the same -Dcom.ibm.rational.test.lt.soa.ssl.protocols=TLSv1.2 for the playback engine of the test. The only way to do this in RPT is
to put the test in a schedule, then configure the schedule to run on a location instead of local computer. Then we add the -Dcom.ibm.rational.test.lt.soa.ssl.protocols=TLSv1.2 as a property of the location.
1. install the RPT Agent, on the same machine as RPT workbench is OK.
2. create a schedule
3. put the test in the schedule
4. on the group of the schedule click "Run this group on the following locations (0) defined)"
5. Do Add...New
6. Create an Agent location using the location that shows up in the Agent Status icon
7. Add a property for this location with the value RPT_VMARGS= -Dcom.ibm.rational.test.lt.soa.ssl.protocols=TLSv1.2
8. run the schedule
The playback should now work. Remember the test will never be able to be run standalone any more if TLS 1.2 is required, it must be run in a schedule using an agent and a RPT_VMARGS set for that agent following the steps above
When using the RQM/RFT integration, you may run into a problem running RFT scripts from RQM when using Shared Location, which results in this error:
The script cannot be executed
You have this problem even though the RQM/RFT integration is set up correctly and the RFT script itself works fine.
RFT scripts run from RQM fail with the "The script cannot be executed" error, but the same scripts run from RFT itself work fine.
If you reconfigure the problem script to use Local instead of Shared Location, the script runs fine from RQM.
In the RQM adapter console, the RFT command used by RQM has a UNC or network path in the -datastore switch instead of a local path to a local temporary location.
This problem happens on machines that are missing a Microsoft VC++ Redistributable required by RFT's RQM adapter, which prevents a DLL file (rftrqmcomm.dll) from loading. The RQM adapter relies on rftrqmcomm.dll to get the temporary location where RQM copied the RFT scripts that were in the shared location. The -datastore switch of the RFT command used by RQM should never have a network path as its value -- if it does, that indicates a problem with the integration or the system hosting the RQM adapter.
How to determine whether you are having this problem
Enable debug logging for the RQM adapter. Then start the RQM adapter, reproduce the problem, and check the RFT command used by RQM -- if the -datastore switch has a network path, you might be having this problem. Proceed to the next step.
With the RQM adapter still running, start Process Explorer and use its Find command to search for rftrqmcomm.dll. If nothing is found, that indicates this DLL was not loaded by the RQM adapter, and that you are having this problem.
(If you cannot run Process Explorer but the test from #1 indicates you may be having this problem, go ahead and follow the steps to resolve the problem.)
Resolving this problem
The RQM adapter requires a new enough version of the 32-bit Microsoft Visual C++ 2005 Redistributable. This can be obtained here. Installing the missing redistributable will resolve this problem.