Since I am unemployed and not having anything better to do with my time I decided I would check out "Apache JMeter" by Emily H. Halili (Packt, 2008).
It's a light read and I found that Chapter 7 (Advanced Features) was the most helpful to myself as I am not a n00b to JMeter. However, I felt that Chapter 7 would have been better served if BeanShell processing would have been tackled. I've found from my load testing experience in the past that at some point the return HTML is gonna have to be sliced and diced and data extracted that cannot be done with a simple RegEx extraction (like what is covered in Chapter 7 of the book).
Other than that, I think that if you are a total n00b to JMeter it isn't half bad as a simple introduction to using JMeter for performance/load testing. There's a lot more to performance/load testing than the book covers such as metrics collection, number crunching, et cetera but the book doesn't purport itself to be the end all be all of explaining performance/load testing so I can't complain.
Three stars.
Thursday, December 11, 2008
Wednesday, December 3, 2008
And that job is toast!
Well. Got laid off today with 20 other folks from the Dallas area. Cannot say that I am surprised. Good thing I've been saving up for this possibility. Didn't get to keep the Uberlaptop of Powah (and I wasn't gonna pay the $3700 to keep it).
I don't expect to get another job in December but I have some possibilities lined up in January. What am I gonna do with that time? Hmmmm. Wasn't GTA IV just released? Too bad I don't have a machine capable of playing the PC version and I'm not going to pay for a console while laid off just to play GTA IV.
I have no doubt that my load testing adventure will continue in January.
One thing for sure. The past seven months has been a waste. Thanks a lot, VT. Same back atcha.
I don't expect to get another job in December but I have some possibilities lined up in January. What am I gonna do with that time? Hmmmm. Wasn't GTA IV just released? Too bad I don't have a machine capable of playing the PC version and I'm not going to pay for a console while laid off just to play GTA IV.
I have no doubt that my load testing adventure will continue in January.
One thing for sure. The past seven months has been a waste. Thanks a lot, VT. Same back atcha.
Thursday, November 13, 2008
Hey. What's going on in this blog?
Hey. What's going on in this blog?
Not a damn thing.
*sigh*
Not even working on WiX stuff right now. Working on manually deploying with NAnt, which is fine with me as it is proven that it works time after time. I suspect that MercScum is gonna wanna go back to WiX after initial deployment prototyping. I mean, why stick with something that is proven and works, right?
Not a damn thing.
*sigh*
Not even working on WiX stuff right now. Working on manually deploying with NAnt, which is fine with me as it is proven that it works time after time. I suspect that MercScum is gonna wanna go back to WiX after initial deployment prototyping. I mean, why stick with something that is proven and works, right?
Tuesday, October 28, 2008
Almost there... Stay on target...
Getting closer to getting the first general WiX task done.
I now have WiX creating my user, adding that user to the Administrators group (No comments from the peanut gallery, please!) and then creating a custom AppPool and creating a Web Application that is bound to that custom AppPool with a created VDir. Pretty nifty.
Here is what it looks like so far:
Of course, you can't see the reference to the Administrators group that is up at the top of the .wxs file under the Package element (see previous post). It is starting to come together.
I now have WiX creating my user, adding that user to the Administrators group (No comments from the peanut gallery, please!) and then creating a custom AppPool and creating a Web Application that is bound to that custom AppPool with a created VDir. Pretty nifty.
Here is what it looks like so far:
1: <Component Id="MySoftwareRequirements" Guid="{SOME-VALID-GUID}">
2: <CreateFolder/>
3: <util:User Id="MySoftwareUser" Name="MySoftwareUser" Password="supersekrit">
4: <util:GroupRef Id="Administrators"/>
5: </util:User>
6: <iis:WebSite Id = "DefaultWebSite"
7: Description = "DefaultWebSite"
8: Directory = "MySoftwareSubDir">
9: <iis:WebAddress Id = "AllUnassigned" Port="80" />
10: <iis:WebDirProperties Id = "WebVirtualDirProperties"
11: Execute = "yes"
12: Script = "yes"
13: Read = "yes"
14: WindowsAuthentication = "no"
15: AnonymousAccess = "yes"
16: AnonymousUser = "MySoftwareUser"
17: IIsControlledPassword = "no" />
18: </iis:WebSite>
19: <iis:WebAppPool Id="MySoftware" Identity="other" Name="MySoftware" User="MySoftwareUser"/>
20: <iis:WebVirtualDir Id = "MySoftwareVDir"
21: Alias = "MySoftwareVDir"
22: Directory = "MySoftwareSubDir"
23: WebSite = "DefaultWebSite"
24: DirProperties = "WebVirtualDirProperties">
25: <iis:WebApplication Id = "WebApplication"
26: Name = "MySoftware"
27: WebAppPool = "MySoftware" />
28: </iis:WebVirtualDir>
29: </Component>
Of course, you can't see the reference to the Administrators group that is up at the top of the .wxs file under the Package element (see previous post). It is starting to come together.
More WiX stuff: Creating a user and adding them to a group.
Now that I am able to successfully create a new user I need to add that user to the Administrators group. Yeah, I hear you already, "That's a major security issue!" and I would tend to agree but this has been "mandated" by MercScum so there isn't much I can do about it.
Anyhoo. To do it I had do the following.
After the Product and Package element declarations I had to add a Group element, like this:
It took some trial and error to find out where to put the util:Group element. The documentation says that it is a child of the Product element but I couldn't put it directly after. It had to go under the Package element. Good to know!
In my previously declared util:User element I had to nest a GroupRef element so the entire bit of XML reads like this:
I was able to create the .msi and installed it on a VM and it worked like a charm. Luckily I only banged my head against the WiX brick wall for a few hours this time, unlike the create a new user head-banging. I suspect everything else will start to fall into place now that I am getting more comfortable with WiX and XML in general. Yes, I've managed to be in industry for almost 20 years without having to bow down to the great XML monster but now I am paying the price for being behind the curve. Back in my day we had CSVs and we liked 'em!
Anyhoo. To do it I had do the following.
After the Product and Package element declarations I had to add a Group element, like this:
1: <Product Id="{F0C1692F-2D79-4D46-9BDF-DCBAD1DBCDDB}" Language="1033" Manufacturer="SomeManufacturer" Name="SomeProduct" UpgradeCode="{SOME-VALID-GUID}" Version="1.0.0.0">
2: <Package Compressed="yes" InstallerVersion="200" />
3: <util:Group Id="Administrators" Name="Administrators" />
It took some trial and error to find out where to put the util:Group element. The documentation says that it is a child of the Product element but I couldn't put it directly after. It had to go under the Package element. Good to know!
In my previously declared util:User element I had to nest a GroupRef element so the entire bit of XML reads like this:
1: <Component Id="RequiredUser" Guid="{SOME-VALID-GUID}">
2: <util:User Id="NewUser" Name="NewUserName" Password="supersekrit">
3: <util:GroupRef Id="Administrators"/>
4: </util:User>
5: <CreateFolder/>
6: </Component>
I was able to create the .msi and installed it on a VM and it worked like a charm. Luckily I only banged my head against the WiX brick wall for a few hours this time, unlike the create a new user head-banging. I suspect everything else will start to fall into place now that I am getting more comfortable with WiX and XML in general. Yes, I've managed to be in industry for almost 20 years without having to bow down to the great XML monster but now I am paying the price for being behind the curve. Back in my day we had CSVs and we liked 'em!
Monday, October 27, 2008
Can I has user created by WiX?
Ok. I'm starting to get this stuff figured out.
The User tag is part of WixUtilExtension.dll but it is not enough to simply reference WixUtilExtension on the command line.
You must also add an XML name space reference in the .wxs file. Also, another gotcha. The namespace spelling is different from the WixUtilExtension spelling. D'oh!
I had to add the following:
Now, the User tag that I created has to have the "util" prefix to let the linker know that the User tag is being referenced for the WixUtilExtension:
Notice that I had to add the CreateFolder tag in my User tag to prevent error ICE18. Otherwise, it'll fail and make me cry.
I was able to link with candle with a "-ext WixUtilExtension.dll" reference and the wixobj was created and with the CreateFolder I avoided the dreaded ICE18 error. I was also able to create my .msi and I will test that tomorrow on my VM.
Wasn't that all intuitively obvious?
My thanks go out to the wix-users listserv that pointed out where I was banging my head against the brick wall of wix. Now with this information I should be able to go forward with the other tasks required and be a tad bit more efficient with WiX (Finally!).
The User tag is part of WixUtilExtension.dll but it is not enough to simply reference WixUtilExtension on the command line.
You must also add an XML name space reference in the .wxs file. Also, another gotcha. The namespace spelling is different from the WixUtilExtension spelling. D'oh!
I had to add the following:
1: <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"
2: xmlns:util="http://schemas.microsoft.com/wix/UtilExtension">
Now, the User tag that I created has to have the "util" prefix to let the linker know that the User tag is being referenced for the WixUtilExtension:
1: <Component Id="RequiredUser" Guid="{SUPER-DUPER-GUID}">
2: <util:User Id="UserStuff" Name="UserStuff" Password="supersekrit" />
3: <CreateFolder/>
4: </Component>
Notice that I had to add the CreateFolder tag in my User tag to prevent error ICE18. Otherwise, it'll fail and make me cry.
I was able to link with candle with a "-ext WixUtilExtension.dll" reference and the wixobj was created and with the CreateFolder I avoided the dreaded ICE18 error. I was also able to create my .msi and I will test that tomorrow on my VM.
Wasn't that all intuitively obvious?
My thanks go out to the wix-users listserv that pointed out where I was banging my head against the brick wall of wix. Now with this information I should be able to go forward with the other tasks required and be a tad bit more efficient with WiX (Finally!).
My head hurts...
*bangs head against desk*
Search for creating users with WiX and you see the handy dandy User tag.
Go ahead and try that with WiX v3. Doesn't work?
Google the documentation. Aha! I need the sca.wixlib and associated sca*.dll files?
Search for files.
Not shipped with v3?
Hmmmm...
Download WiX v2.
Try using with WiX v3.
"The extension 'sca.wixlib' could not be loaded."
*continue to bang head against desk*
Now off to try this again with WiX v2. Can't use heat to harvest files? Guess I need to re-learn the process with tallow.
*continue to bang head against desk*
Do some more Googling. Hey, automated tasks are in the Wix*Extension.dlls. That's what I thought but couldn't get to load with -ext. Hmmmmm?
Some more Googling and reading of blogs. Oh, you can't just use the Wix*Extension.dll by name. Needs full path. Ok. That's not so bad.
Which Wix*Extension.dll has the task for using with the User tag? Dunno. I'll just copy all Wix*Extension.dll to my subdir and try 'em all.
Oops. WinDifxAppExtension.dll can't be loaded? Remove it from command line.
Oops. WixIsolatedAppExtension.dll can't be loaded. Remove it from command line.
Will by User tag be recognized now? *crosses fingers* Let's give it a try!
8<--------------------------------------------------
C:\SomeProduct\SP\Dist>candle -o SP.wixobj SP.wxs -ext WixDifxAppExtension.dll -ext WixDirectXExtension.dll -ext WixFirewallExtension.dl
l -ext WixGamingExtension.dll -ext WixIIsExtension.dll -ext WixMsmqExtension.dll -ext WixNetFxExtension.dll -ext WixPSExtension.dll
-ext WixSqlExtension.dll -ext WixUIExtension.dll -ext WixUtilExtension.dll -ext WixVSExtension.dll
Microsoft (R) Windows Installer Xml Compiler version 3.0.4318.0
Copyright (C) Microsoft Corporation. All rights reserved.
SP.wxs
C:\SomeProduct\SP\Dist\SP.wxs(461) : error CNDL0005 : The Component element contains an unexpected child element 'User'.
-------------------------------------------------->8
Fsck.
*sigh*
Hey. Wasn't I hired to be the performance SME? Hmmmm. What happened to that?
Search for creating users with WiX and you see the handy dandy User tag.
Go ahead and try that with WiX v3. Doesn't work?
Google the documentation. Aha! I need the sca.wixlib and associated sca*.dll files?
Search for files.
Not shipped with v3?
Hmmmm...
Download WiX v2.
Try using with WiX v3.
"The extension 'sca.wixlib' could not be loaded."
*continue to bang head against desk*
Now off to try this again with WiX v2. Can't use heat to harvest files? Guess I need to re-learn the process with tallow.
*continue to bang head against desk*
Do some more Googling. Hey, automated tasks are in the Wix*Extension.dlls. That's what I thought but couldn't get to load with -ext. Hmmmmm?
Some more Googling and reading of blogs. Oh, you can't just use the Wix*Extension.dll by name. Needs full path. Ok. That's not so bad.
Which Wix*Extension.dll has the task for using with the User tag? Dunno. I'll just copy all Wix*Extension.dll to my subdir and try 'em all.
Oops. WinDifxAppExtension.dll can't be loaded? Remove it from command line.
Oops. WixIsolatedAppExtension.dll can't be loaded. Remove it from command line.
Will by User tag be recognized now? *crosses fingers* Let's give it a try!
8<--------------------------------------------------
C:\SomeProduct\SP\Dist>candle -o SP.wixobj SP.wxs -ext WixDifxAppExtension.dll -ext WixDirectXExtension.dll -ext WixFirewallExtension.dl
l -ext WixGamingExtension.dll -ext WixIIsExtension.dll -ext WixMsmqExtension.dll -ext WixNetFxExtension.dll -ext WixPSExtension.dll
-ext WixSqlExtension.dll -ext WixUIExtension.dll -ext WixUtilExtension.dll -ext WixVSExtension.dll
Microsoft (R) Windows Installer Xml Compiler version 3.0.4318.0
Copyright (C) Microsoft Corporation. All rights reserved.
SP.wxs
C:\SomeProduct\SP\Dist\SP.wxs(461) : error CNDL0005 : The Component element contains an unexpected child element 'User'.
-------------------------------------------------->8
Fsck.
*sigh*
Hey. Wasn't I hired to be the performance SME? Hmmmm. What happened to that?
Subscribe to:
Posts (Atom)
Posts
