2018 up to now | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2007

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [QF-Test] Question : How to Instrument the JRE on the fly?

  • Subject: Re: [QF-Test] Question : How to Instrument the JRE on the fly?
  • From: Laurent Dolle <ldolle@?.com>
  • Date: Thu, 5 Jul 2007 10:43:29 +0200

Hi Stéphane,

Usually, InstallAnywhere uses a special *.vm file (located in ...\resource\installer_vms\) to wrap the JRE.
We have discovered empirically that such files can be opened with Winzip (other zip tools will probably work also). So my advice would be to create your own *.vm file by using an already manually instrumented JRE.

Hope this is enough for you to understand.

Laurent Dollé
Thales Security Solutions & Services, on behalf of:
Amadeus - Global Core - Java Middleware
+33 (0)4 97 15 34 24

Stéphane Savariau <ssavariau@?.com>
[QF-Test] Question : How to Instrument the JRE on the fly?

Stéphane Savariau <ssavariau@?.com>  

Sent by: qftest-list-bounces@?.de  
05/07/2007 09:38

Context :
With QFTEST 2.0, I’m currently designing a test-set that deploy one of our product with InstallAnywhere.
The installation behavior of this application deployment is the following:
Just before the end of installation process, the setup launch a java application (Database configuration) that uses the freshly installed JRE.
My problem:  
I would like to instrumentate this freshly installed jre. But every way I used failed.
1-      I have tried to instrumentate with QFTEST Console, but unfortunately, the setup delete all files if already exist. So that the instrumentation is lost. I have to manage instrumentation manually and this is a blocking issue for full automation deployment.
2-      I tried to  copy the correct files at the correct place (as we did previously with QFTest 1.06) but QFTEST indicates that the JRE is not correctly instrumentate.
Accessibility.properties in <product name>\jre\lib
Qfconnect.jar in <product name>\jre\lib\ext
Update qfconnect.properties with correct properties
Something missing here?
Is it possible to instrumentate on the fly a specific JRE?
If yes, could you please indicates the step by step and/or needed files?
Thanks in advance.
Stephane S
qftest-list mailing list