News

Tweets













Velocity - Installation Phase

Velocity - Installation Phase

Today I have proceeded with the installation of the MS Velocity CTP3.

I would like to mention that first one needs to verify one's system for prerequisites. Basically the most up to date components as a Service Pack of the Windows OS and the latest .Net Framework are needed, also PowerShell 1.0 is a required component because the administration can be later done using PowerShell applets.

I also recommend reading the velocity_help.chm file that can be downloaded separately. It includes very valuable information on the ways of installing the product. It helped me to understand the concepts of the implementation and make decisions about how I want Velocity configured in my environment.

Because my goal was to experiment with Velocity and because it was a CTP I have decided to install it and its shared cache on my computer locally using the Folder Share mode. By the way it is a very acceptable scenario for a production system too.

I have made a folder of my choice shared accepting the defaults and without doing any special security settings. Need to note here that the setup will add the Network Service to it allowing change and read operations.

The actual download was actually small so in a few seconds I was presented with the setup screen and asked to fill in the basic info as the project installation location.

Overall, the installation tool is very intuitive, so one should feel comfortable about the whole setup process.

Next, I was asked by the Windows Firewall if to allow communicating with the Velocity instance and I agreed.

Then, while the main installation window continued running, a Cache Host Configuration screen (above) popped up that contained initial set up information parameters. I have changed the settings to reflect my choice. One small side note I would like to mention: if you are installing on a local machine to a shared folder you will need to type the path to it in as UNC path.

Next I was able to test the settings and name my cluster instance. At this stage I saw two MS SQL Server Compact databases named ClusterConfig.sdf and ConfigStore.sdf created in the shared folder.

I was able to see the final success message on the installer tool and a shortcut put onto the Desktop leading to the PowesShell based Administration tool for Microsoft Distributed Cache.

That's it, I am ready to test the waters!


Friday, May 1, 2009 10:55 AM

Feedback

No comments posted yet.


Post A Comment
Title:
Name:
Email:
Comment:
Verification: