Comments for Odecee http://www.odecee.com.au Fast Simple Software Fri, 18 Nov 2011 01:04:24 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on Wrestling with RAM relationships by Using RAM to Record Deployment Histories | odecee blogs http://www.odecee.com.au/blog/2011/the-trouble-with-ram-relationships/#comment-150 Using RAM to Record Deployment Histories | odecee blogs Fri, 18 Nov 2011 01:04:24 +0000 http://blog.odecee.com.au/?p=338#comment-150 [...] An important point to note is that the link between the Deployment History and the Component is not a RAM relationship. Instead it is a set of attributes within the Deployment History that describe the Component that was deployed, I.e. Name and version. The reason for this “soft” link is to do with the complexities of managing relationships when new versions of an Asset are created. A description of these complexities, with regards to the use of Release Assets, is provided in my previous blog. [...] [...] An important point to note is that the link between the Deployment History and the Component is not a RAM relationship. Instead it is a set of attributes within the Deployment History that describe the Component that was deployed, I.e. Name and version. The reason for this “soft” link is to do with the complexities of managing relationships when new versions of an Asset are created. A description of these complexities, with regards to the use of Release Assets, is provided in my previous blog. [...]

]]> Comment on Performance Unit Test; a development concern by The Performance Architect | odecee blogs http://www.odecee.com.au/blog/2008/performance-unit-test-a-development-concern/#comment-128 The Performance Architect | odecee blogs Thu, 17 Nov 2011 23:42:27 +0000 http://apollo.odecee.com.au/blogs/?p=22#comment-128 [...] Component Performance Testing patterns.  An implementation of this pattern is what l call the Performance Unit Test which l discuss in detail in my blog [...] [...] Component Performance Testing patterns.  An implementation of this pattern is what l call the Performance Unit Test which l discuss in detail in my blog [...]

]]> Comment on Rational Asset Manager – Schema for Release Management by Using RAM to Record Deployment Histories | odecee blogs http://www.odecee.com.au/blog/2011/rational-asset-manager-schema-design/#comment-142 Using RAM to Record Deployment Histories | odecee blogs Mon, 14 Nov 2011 05:14:26 +0000 http://blog.odecee.com.au/?p=277#comment-142 [...] designing the Rational Asset Manager (RAM) schema to support Release Mangement we have been extensively using the Release and Component Assets. However, the use of the Deployment [...] [...] designing the Rational Asset Manager (RAM) schema to support Release Mangement we have been extensively using the Release and Component Assets. However, the use of the Deployment [...]

]]> Comment on Handling memory within iterations in LoadRunner by Raman Jain http://www.odecee.com.au/blog/2011/handling-memory-within-iterations-in-loadrunner/#comment-154 Raman Jain Mon, 10 Oct 2011 06:57:23 +0000 http://blog.odecee.com.au/?p=334#comment-154 Thats great. I am looking forward to see that code here. If I am not wrong RPT use its own proprietary scripting language. Thats great.
I am looking forward to see that code here. If I am not wrong RPT use its own proprietary scripting language.

]]> Comment on Handling memory within iterations in LoadRunner by John Natsioulas http://www.odecee.com.au/blog/2011/handling-memory-within-iterations-in-loadrunner/#comment-153 John Natsioulas Mon, 10 Oct 2011 04:08:54 +0000 http://blog.odecee.com.au/?p=334#comment-153 Hi Raman. Yes, well aware of the VTS within LR. Have utilized it a number of times with LR in the past, especially for unique parameter requirements (once implemented it's a lot easier to maintain data between runs). Recently have been using Rational Performance Tester(RPT), and the way RPT and LR handle parameters is slightly different (but that's another topic). In any case for RPT, a colleague has come up with a nice utility that cleans out datapools in RPT between test runs. I'm sure he will be blogging on this soon. Hi Raman. Yes, well aware of the VTS within LR. Have utilized it a number of times with LR in the past, especially for unique parameter requirements (once implemented it’s a lot easier to maintain data between runs). Recently have been using Rational Performance Tester(RPT), and the way RPT and LR handle parameters is slightly different (but that’s another topic). In any case for RPT, a colleague has come up with a nice utility that cleans out datapools in RPT between test runs. I’m sure he will be blogging on this soon.

]]> Comment on Handling memory within iterations in LoadRunner by Raman Jain http://www.odecee.com.au/blog/2011/handling-memory-within-iterations-in-loadrunner/#comment-152 Raman Jain Thu, 06 Oct 2011 07:13:44 +0000 http://blog.odecee.com.au/?p=334#comment-152 Nice Article. To add on further... (1) There is a utility available from HP called VTS which can be used for all such sort of requirements like handling the dynamic parameters and using the parameters created during runtime through parameters and variables without pre defining them in file or so. It is quite easy to implement also and decently maintain dynamic memory allocation and de locations. (2) I personally used a different way of handling it a long back when I was not aware about VTS. I created a flat file with fields:- VuserName,ParamFeed Vname1, value1, Vname1,value2, Vname2,value3, Vname2,value4, I wrote a c program to seek the required value (Vname1) inside that file by using file functions. and the moment when it was found the program searched the value between the 2 consecutive ','s and saved it in a string. On completion of iteration the program was deleting the same line from the file itself and was replacing it with some garbage value so that the index of the rows should not change. Nice Article. To add on further…

(1) There is a utility available from HP called VTS which can be used for all such sort of requirements like handling the dynamic parameters and using the parameters created during runtime through parameters and variables without pre defining them in file or so. It is quite easy to implement also and decently maintain dynamic memory allocation and de locations.

(2) I personally used a different way of handling it a long back when I was not aware about VTS. I created a flat file with fields:-
VuserName,ParamFeed
Vname1, value1,
Vname1,value2,
Vname2,value3,
Vname2,value4,
I wrote a c program to seek the required value (Vname1) inside that file by using file functions. and the moment when it was found the program searched the value between the 2 consecutive ‘,’s and saved it in a string. On completion of iteration the program was deleting the same line from the file itself and was replacing it with some garbage value so that the index of the rows should not change.

]]> Comment on Handling memory within iterations in LoadRunner by harinder seera http://www.odecee.com.au/blog/2011/handling-memory-within-iterations-in-loadrunner/#comment-151 harinder seera Thu, 08 Sep 2011 08:20:24 +0000 http://blog.odecee.com.au/?p=334#comment-151 Pretty cool. Sometime simple way of doing thing is a better way :) Pretty cool. Sometime simple way of doing thing is a better way :)

]]> Comment on Wrestling with RAM relationships by Des Drury http://www.odecee.com.au/blog/2011/the-trouble-with-ram-relationships/#comment-149 Des Drury Thu, 01 Sep 2011 04:53:15 +0000 http://blog.odecee.com.au/?p=338#comment-149 Hi Gili, Thanks for your comments. I've created a new forum post asking about what may be in the pipeline to improve our use of RAM realtionships. https://jazz.net/forums/viewtopic.php?p=63800#63800 Hi Gili,

Thanks for your comments. I’ve created a new forum post asking about what may be in the pipeline to improve our use of RAM realtionships.

https://jazz.net/forums/viewtopic.php?p=63800#63800

]]> Comment on Wrestling with RAM relationships by Gili Mendel http://www.odecee.com.au/blog/2011/the-trouble-with-ram-relationships/#comment-148 Gili Mendel Wed, 31 Aug 2011 17:29:01 +0000 http://blog.odecee.com.au/?p=338#comment-148 Yes. What RAM has at this point, is the lowest hanging fruit. RAM has no semantics regarding relationships today (may be a small hard coded one for the dependency one). We have some ideas of how to solve these particular problems... and will welcome any (generic) recommendations. If you start a thread on the RAM forum on Jazz.net https://jazz.net/forums/viewforum.php?f=12&sid=3637f00e85f00465c5b15f19f0c7f62c we will definitely listen. Yes. What RAM has at this point, is the lowest hanging fruit. RAM has no semantics regarding relationships today (may be a small hard coded one for the dependency one).

We have some ideas of how to solve these particular problems… and will welcome any (generic) recommendations. If you start a thread on the RAM forum on Jazz.net https://jazz.net/forums/viewforum.php?f=12&sid=3637f00e85f00465c5b15f19f0c7f62c we will definitely listen.

]]> Comment on Wrestling with RAM relationships by Oscar Huseyin http://www.odecee.com.au/blog/2011/the-trouble-with-ram-relationships/#comment-147 Oscar Huseyin Wed, 31 Aug 2011 11:39:58 +0000 http://blog.odecee.com.au/?p=338#comment-147 Hey Des, Sounds like this was an explicit design decision made by the RAM engineers. I'm struggling to see why this design decision could have been made as the only reason why l can think this would be a design feature is to treat all components versions as new components, where the concept of "updating" a version of a component is not built into RAM as a specific use-case. Hmmm. Even modelling documents (instead of software components) does not seem to fit the requirements l would have on an Asset Management system as you will find the "update" document (or component) version an important, and frequently used, use-case. Im glad that RAM has the capabilities to extend its functionality to implement these advanced approaches. I would love to see your solution one day! Oscar Hey Des,

Sounds like this was an explicit design decision made by the RAM engineers. I’m struggling to see why this design decision could have been made as the only reason why l can think this would be a design feature is to treat all components versions as new components, where the concept of “updating” a version of a component is not built into RAM as a specific use-case. Hmmm. Even modelling documents (instead of software components) does not seem to fit the requirements l would have on an Asset Management system as you will find the “update” document (or component) version an important, and frequently used, use-case. Im glad that RAM has the capabilities to extend its functionality to implement these advanced approaches. I would love to see your solution one day!

Oscar

]]>