ESB Toolkit 2.1 installation on BizTalk Server 2010

Pre-requisite for ESB 2.1

·         Microsoft Windows 2008 Server SP1/ SP2

·         .NET framework 3.5 SP1

·         IIS 7.0

·         Microsoft SQL Server 2008

·         Microsoft BizTalk Server 2009/2010

·         Visual Studio 2008 SP1/ 2010

·         Microsoft Chart Controls for .NET Framework 3.5 (This would be used by ESB Portal)

(http://www.microsoft.com/download/en/details.aspx?id=14422)

·         Microsoft Enterprise Library 4.1

Note: If your machine has Microsoft Enterprise Library 5.0 installed it would be advisable to un-install 5.0 and install Microsoft Enterprise Library 4.1 (http://www.microsoft.com/download/en/details.aspx?id=6228) as the ESB solution targets 4.1 version.

     1)    Install Microsoft ESB Toolkit 2.1 (http://www.microsoft.com/download/en/details.aspx?id=11847)

This will install the tools and samples.

     2)    Navigate to Start à All Programs à Microsoft BizTalk Server 2010 ESB Toolkit

Click Install Itinerary designer extension to register the itinerary designer extension in Visual Studio 2010

     3)    Verify whether the installation was successful by;

Open Visual Studio 2010 and check whether you see an option to create an ESB itinerary

     4)    Open BizTalk admin console and;

·         Import Microsoft.Practices.ESB.CORE64.msi into the Applications node (remember to select Overwrite resources). Continue the installer to install the assemblies into GAC.

If you get an error like;

There is a problem with this Window Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor.

This implies there is a problem GACing the assemblies. At this point all assemblies except Microsoft.Practices.ESB.ExceptionHandling.PipelineComponents.dll are in the GAC.

o    To GAC the above, navigate to the folder where the installer had dumped all the assemblies which were to be GACed. Default location is "C:\Program Files (x86)\Generated by BizTalk".

o    Navigate to C:\Program Files (x86)\Generated by BizTalk\Microsoft.Practices.ESB\<GUID Folder>\ and extract ITEM~14. This will have Microsoft.Practices.ESB.ExceptionHandling.PipelineComponents.dll which can be dragged to the GAC.

·         Clear "C:\Program Files (x86)\Generated by BizTalk" folder

·         Import Microsoft.Practices.ESB.ExceptionHandling64 into the Applications node (remember to select Overwrite resources). Continue the installer to install the assemblies into GAC.

If you get an error like;

There is a problem with this Window Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor.

Ignore this error as all required assemblies have been GACed.

·         Clear "C:\Program Files (x86)\Generated by BizTalk" folder

·         Import Microsoft.Practices.ESB.JMS into the Applications node (remember to select Overwrite resources). Continue the installer to install the assemblies into GAC.

If you get an error like;

There is a problem with this Window Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor.

This implies there is a problem GACing the assemblies. At this point all assemblies except Microsoft.Practices.ESB.JMS.PipelineComponents.dll are in the GAC.

o    To GAC the above, navigate to the folder where the installer had dumped all the assemblies which were to be GACed. Default location is "C:\Program Files (x86)\Generated by BizTalk".

o    Navigate to C:\Program Files (x86)\Generated by BizTalk\ Microsoft.Practices.JMS\<GUID Folder>\ and extract ITEM~0. This will have Microsoft.Practices.ESB.JMS.PipelineComponents.dll which can be dragged to the GAC.

·         Clear "C:\Program Files (x86)\Generated by BizTalk" folder

·         For safety place the pipeline components assemblies i.e.

o    Microsoft.Practices.ESB.JMS.PipelineComponents

o    Microsoft.Practices.ESB.ExceptionHandling.PipelineComponents

; Into "C:\Program Files\Microsoft BizTalk Server 2010\Pipeline Components"

     5)    Navigate to "C:\Program Files\Microsoft BizTalk ESB Toolkit 2.1" and extract ESBSource.zip file. This would create the ESBSource solutions folder with a Keys subfolder having the assembly key files and Source subfolder with the actual ESB solution

     6)    We need to create an assembly key file to be used by the ESB solution. To do that open Visual Studio command prompt and type in;

sn -k "C:\Program File\Microsoft BizTalk ESB Toolkit 2.1\ESBSource\Keys\Microsoft.Practices.ESB.snk"

     7)    Navigate to "C:\Program Files\Microsoft BizTalk ESB Toolkit 2.1\ESBSource\Source\Samples\Management Portal\ESB.Portal"

Open ESB.Portal solution and re-build the solution.

Do NOT proceed unless the solution builds successfully. You may have to fix some references to get the solution in a compiled state.

     8)    Next we have to change the script execution policy as we are going to run some scripts to install the portal solution.

Navigate to Start à All Programs à Accessories à Windows PowerShell and click on Windows PowerShell.

·         At the prompt type get-executionpolicy which will display the current execution policy.

·         If it says Restricted we have to change it to Unrestricted as follows:

o    At the prompt type in set-executionpolicy Unrestricted

Since the portal solution scripts may target any version of Windows PowerShell we have to set the execution policies for both the x64 and x86 versions. So,

 Navigate to Start à All Programs à Accessories à Windows PowerShell and click on Windows PowerShell (x86)

·         At the prompt type in get-executionpolicy which will display the current execution policy.

·         If it says Restricted we have to change it to Unrestricted as follows:

o    At the prompt type in set-executionpolicy Unrestricted

      9)    Navigate to "C:\Program Files\Microsoft BizTalk ESB Toolkit 2.1\ESBSource\Source\Samples\Management Portal\Install\Scripts" and double click on Management_Install.cmd

This would install the portal and create all the required virtual directories in the IIS

     10)  Open IIS and make sure ESB.Portal virtual directory is created under Sites\Default Web Site.

Ensure that it is pointing to the correct folder i.e. "C:\Program Files\Microsoft BizTalk ESB Toolkit 2.1\ESBSource\Source\Samples\Management Portal\ESB.Portal"

     11)  Select ESB.Portal node and in the page on the right hand side double click Authentication.

Ensure that Windows Authentication is Enabled.

     12)  Navigate to "C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bin\" and double click on ESBConfigurationTool.exe.

Note: ESBConfigurationTool works in a linear way i.e. Exception Management, Database is configured first followed by Exception Management, Exception Web Services followed by ESB Core Components, Itinerary Database followed by ESB Core Components, Core Web Services and finally the Configuration. Also each of the features have to be configured separately i.e. Hit "Apply Configuration" after each step rather than trying to configure all features in one go.

·         Open ESB Configuration à Exception Management à Database

o    Check Enable Exception Management Database and specify the Database server name

o    Click on Apply Configuration

·         Open ESB Configuration à Exception Management à Exception Web Services

o    Check Enable Exception Services

o    Provide the user name, password details and Click on Apply Configuration

·         Open ESB Configuration à ESB Core Components à Itinerary Database

o    Check Itinerary Database and specify the Database server name

o    Click on Apply Configuration

·         Open ESB Configuration à ESB Core Components à Core Web Services

o    Check Enable Core Services

o    Provide the user name, password details and Click on Apply Configuration

·         Open ESB Configuration à Configuration

o    Make sure File Configuration Source is selected. (This option will save all the settings to ESB.config file)

     13)  Add all portal user names to BizTalk Isolated Host Users, BizTalk Application Users, SSO Administrator and SSO Affiliate Administrator groups.

     14)  Deploy the portal bam tables. Open a command prompt and navigate to "C:\Program Files\Microsoft BizTalk Server 2010\Tracking". Run the following commands to deploy the bam tables:

·         bm.exe deploy-all -DefinitionFile:"C:\Program Files\Microsoft BizTalk ESB Toolkit 2.1\Bam\Microsoft.BizTalk.ESB.BAM.Itinerary.xml"

·         bm.exe deploy-all -DefinitionFile:"C:\Program Files\Microsoft BizTalk ESB Toolkit 2.1\Bam\Microsoft.BizTalk.ESB.BAM.Exceptions.xml"

If you get an error like;

Deploying View... ERROR: The BAM deployment failed. The BAM Star Schema database has not been configured. Run bm.exe setup-databases to configure the database.

It was because the BAM Star Schema and analysis services have not yet been configured.

o    Open Run and type in Configuration or alternatively open the BizTalk Server Configuration

o    Click on Bam Tools in the BizTalk Server Configuration window.

o    Check Enable Analysis Service for BAM aggregations  and specify an appropriate Server Name for Bam Analysis Database  (optional) and BAM Star Schema Database

o    Click on Apply Configuration to create the databases.

o    Before running the bm deploy command again we have to grant ourselves access to the newly created BAM Star Schema.

Open SQL Management Studio à Database Instance à Security à Logins and double click on <Your Installation ID>.

In the Login properties window select User Mapping node and check on BAMStarSchema.

In the Database role membership pane for BAMStarSchema check public, db_datareader, db_datawriter and Click OK

o    Run bm.exe deploy-all -DefinitionFile:"C:\Program Files\Microsoft BizTalk ESB Toolkit 2.1\Bam\Microsoft.BizTalk.ESB.BAM.Exceptions.xml" again

     15)  Exception management portal relies on ExceptionService.svc WCF service. IIS 7.0 installation does not have a script map for .svc files and hence they have to be registered explicitly as follows:

Open a command prompt and navigate to "C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation"

Run the following command: ServiceModelReg.exe -r –y

     16)  Restore the execution policy to Restricted i.e.

Navigate to Start à All Programs à Accessories à Windows PowerShell and click on Windows PowerShell

Run set-executionpolicy Restricted
Navigate to Start à All Programs à Accessories à Windows PowerShell and click on Windows PowerShell  (x86)

Run set-executionpolicy Restricted

     17)  Restart IIS and SQL Server.

     18)  Verify whether ESB 2.1 installation-configuration was successful by opening  a browser with the following url:

http://localhost/ESB.Portal/Reports/Reports.aspx

Other Errors

      1)    On opening the ESB Management portal if you get an error message pointing to the event viewer and the event viewer message says "assembly Microsoft.Practices.ESB.Portal.Global not found", this means that the ESB portal solution build has been un-successful i.e. Step (11) has to be re-visited

      2)    On opening the ESB Management portal you get an error message pointing to the event viewer and the event viewer message says "could not load type System.ServiceModel.Activation.HttpModule", this means that because of the order of the software installation on your machine i.e. IIS installed after .Net framework the .net version has not been registered with IIS.

To fix this problem;

Open a command prompt, navigate to "C:\Windows\Microsoft.NET\Framework\v4.0.30319 (or the version installed on your machine)" and run the following command

aspnet_regiis.exe –iru

      3)    If there are still any problems with the installation try the following links
      http://dgoins.wordpress.com/2010/05/01/esb-toolkit-management-portal-installation-notes-from-the-field-2/

http://msdn.microsoft.com/en-us/library/ee236738(BTS.10).aspx

Read More

Pre-requisite for BAM Portal

One of the important pre-requisites before trying to configure BAM portal on your machine is the installation of IIS 6 extensions. Following steps should be followed before configuring the BAM portal via the BizTalk configuration tool.

·         Right click My computer  and click Manage

·         Expand Roles and select Web Server (IIS) node

·         Scroll through Role Services and check status of IIS 6 Management Compatibility role service

·         If status is Installed then close the windows

·         If status is Not Installed then right click Web Server (IIS) node and select Add Role Services

·         Select IIS 6 Management Compatibility node and complete the installation

Read More

Hobbies and Interests

Several years ago I wrote an article summarising some of the key points I keep in mind while interviewing candidates for a test team. The article is called "Hiring Software Testers in an Information Age" and is available as a PDF on my main site. The article was originally targetted to recruiters who kept asking me for advice on hiring software testers and they would always be surprised at the level of detail that I went through in describing what it takes to hire a good person for a testing position.

Conversations with recruiters over coffee would always start the same. I would say something like: if you are just trying to find a warm body to fill a position, then you don't need to hear what I have to say.  If you want to hire someone who thinks and has a good chance of fitting in with the culture of the team and organisation to provide value, then it is a complex problem that requires insights into what the position actually involves.

There are about a dozen different checkpoints that I go through when considering and interviewing candidates, and the paper I wrote touched on some of the major points but not all of them.  Actually, I even removed some of them from the article as early drafts had too much information.  My intention was to get some of the important points across without writing a book.

Recently, a colleague and friend, Michael Mahlberg tweeted the following:

RT @NolanBushnell: At Atari we hired based on hobbies and not grades in school. We ended up with the best engineering group in the world.

I liked that comment and followed up with a supporting tweet:

On Hiring: if a résumé or cover letter doesn't describe Hobbies or other Interests, I usually skip it.

This sparked some conversation on twitter and I want to elaborate on my comment here.


First off, it is important to know that I place myself in the Context-Driven School of Testing. The principles of this 'school' puts the focus on the people working together to help deliver the right solution.  One of the things I have noticed over the last 22 years in the software industry is that the best testers are the ones who care about testing. They have fun with it. They believe they are working to improve things for the customer. They have a drive and motivation that lets them ignore or put up with a lot of crap that is dumped on them by unhealthy organisations and ignorant individuals.

Unfortunately, that kind of motivation, passion or drive doesn't come across on a standard résumé. I can spot it straight away when I am talking with someone, but how do you communicate it in a standard functional résumé?  In general, I don't see it in the "technical skills" or job description sections that focus on accomplishments and other task-oriented details. The majority of the time I notice evidence or hints of passion and motivation in the cover letter, if anywhere at all.

So, when I am hiring for a test team, a team that I want to integrate well with the rest of development and the organisation, a team that I want to focus on building human relationships as well as exercise systems and scientific thinking in their quality investigations, a team that I want to encourage fun and respect for their hard work in providing valuable information to help make timely decisions, where do I start when I am looking at a stack of résumés and job applications?

People who submit cover letters go to the top of the pile. People who include "Hobbies and Interests" in their résumés are next. People who don't submit a cover letter and don't tell me anything other than a bunch of dry technical information and job details are put at the bottom of the list and often fall right off the pile.

Having a cover letter or a "Hobbies and Interests" section doesn't guarantee an interview but your chances of having me give you a quick call are higher. So, what's the deal with this "Hobbies and Interests" section anyway?

Johanna Rothman wrote an awesome book called "Hiring the Best Knowledge Workers, Techies & Nerds." If you don't have a copy yet, and you are in the business of hiring technical people, I highly recommend you get a copy of this book.  Johanna is an awesome person and a terrific writer. She writes a few blogs and I learn a lot from them.

Johanna wrote a good blog post back in 2004 titled "Tips for Reviewing Resumes". One of the points she wrote in that post says: "Hobbies or other personal information. This stuff isn’t relevant to the job and should not be part of how you select candidates."

I partly agree with this sentence. I really don't care about personal information in an application. By "personal information" I mean things like marital status, age, sex, or anything else that the government might use to classify you in their census demographics charts.

What about hobbies and other interests? Things like: playing music (e.g. piano or guitar), likes to read, play video games, do magic, go cycling, martial arts, improv, and so on.

This stuff I find both interesting and relevant! Why? Creativity, passion and (skill) transference.

I am looking to hire people -- intelligent, thinking, caring, fun people and not drones. I honestly don't know whether the stuff I'm reading on your application is true, embellished or fabricated. I want to get an idea of the whole picture of who you are. I will test you for your technical ability during the interview, so I'm not worried about that part.  Finding someone who has the right mindset and will fit in with the rest of the team is harder to grasp from technical details and job accomplishments alone.

Based on how I currently understand, apply and teach Software Testing, I like to find candidates who exercise both their creative and analytical parts of their minds -- i.e. people who are right and left-brained (to use a dated, flawed model of the human mind). When I read through the candidate's hobbies and interests, I build a list of assumptions that I can check in a phone call or in-person interview.

Assumptions might be things like:

• if I see someone who likes to do creative things like play music, sing, knit, et cetera, these are right-brained/creative activities. This is a good sign that the candidate might be good at Exploratory Testing as I do it.


• if I see someone who participates in theatre, improv or role-playing games, then they may be good at user profiling and test design.


• if someone likes to read, this may tell me that they are learners and continue to feed their imaginations. This is also a good sign for Exploratory Testing, and I am happy to ask them about the kinds of books they read.


• sometimes their interests may align very well with the interests of the organisation and the product or solution in development. Things like playing video games or participating in sports are really good hobbies to have if the hiring company makes games or develops solutions for the Sports industry. 

There are too many examples for me to list here. The point is that sometimes the Hobbies and Interests section can provide me with insights that I won't get from the Work Experience, Technical Skills or Education sections of a résumé alone. I look for evidence of creativity, motivation, passion, balance, feeding imagination, professional activities, community involvement, and so on. Sometimes, the skills they develop in their hobbies are directly transferable to the testing tasks required -- e.g. learning, observation, relationship-building, organisation, analysis, design, problem-solving, and so on. Sometimes they aren't - it depends on the individual.

These are all assumptions, I know, so I treat them like assumptions. I make note of them and ask about them in phone calls and interviews.

If I like the candidate and hire them, I use their hobbies/interests as examples when coaching them on testing theory, models and practices. Since the hobby is familiar to them, I find this is a really powerful teaching technique. I also encourage them to come up with their own testing analogies using knowledge and experiences they are familiar with. It raises their self-confidence and helps them to remember abstract ideas in their own terms.

The likelihood of me finding a Testing Superstar by skimming through résumés is pretty slim. The likelihood of me finding a candidate who I can help become a Testing Superstar is much higher if I can learn more about them in their job application; learn more about what makes them a unique, creative, passionate individual who cares about others, doing excellent work, providing value and enjoying life.

But that's just me. All interviewers are different. Your mileage may vary.

When in doubt, I suggest candidates be themselves. If you are penalised in a hiring process for it, you don't want to work there anyway. You are allowed to have a life. Work is just a part of it.

Read More