Installing Adapter Pack

WCF LOB Adapter SDK SP2

System Requirements

Supported Operating Systems: Windows Server 2003 R2 Enterprise Edition (32-Bit x86); Windows Server 2003 R2 Standard Edition (32-bit x86); Windows Server 2003 Service Pack 2; Windows Server 2008
Supported Platforms: x86 and x64
Prerequisite Software Requirement
You must install this software prior to installing the WCF LOB Adapter SDK.
a. Microsoft .NET Framework 3.5 SP1
b. Microsoft Visual Studio 2005 or Microsoft Visual Studio 2008

Note: You require this only if you want to either build custom adapters or develop solutions that use the adapters built using the WCF LOB Adapter SDK.

c. Microsoft BizTalk Server 2006 R2 or Microsoft BizTalk Server 2009

Note: You require this only if you want to use the adapters with BizTalk.

Start Installation

1. Download the setup files from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkID=96184 to a temporary location on your computer.

2. Run WCF LOB Adapter SDK SP2 x86. exe
3. Set extract location and select Unzip.

4. To start the installation wizard, navigate to the folder containing the setup files and click AdapterFramework.msi (for an x86-based platform) or AdapterFramework64.msi (for an x64-based platform).
If a previous version of the WCF LOB Adapter SDK is detected, you will be prompted to upgrade the existing installation. To continue with an upgrade installation, click Ok; otherwise, click Cancel to exit the installation.

5. On the Welcome screen, click Next.

6. If you accept the license agreement, click Next.

7. In the Choose Setup Type dialog box, select the type of installation you want:

• To install the run time and tools, click Typical.
• To select the features that you want to install and the installation location, select Custom.

To install the base WCF LOB Adapter SDK run-time features, select Runtime.

To install the WCF LOB Adapter SDK development tools including the Adapter Development Wizard, Visual Studio Plug-in for generating a .NET Proxy (Add Adapter Service Reference Visual Studio Plug-in) and BizTalk Add-in for generating XML Schemas in a BizTalk Project (Consume Adapter Service BizTalk Project Add-in), select Tools.

To install the sample Contoso and Echo adapters, select Samples.

• To install all the features, click Complete.

8. Click Install.

9. Specify whether you want to receive automatic updates related to the WCF LOB Adapter SDK; select Use Microsoft Update when I check for updates (recommended), click OK

Installing Microsoft BizTalk Adapter Pack 2_0

1. Download the setup files from the Microsoft Download Center at http://www.microsoft.com/downloads/details.aspx?FamilyID=76736BA7-3C05-4436-9353-1C33F9005194&displaylang=en to a temporary location on your computer.

2. Run Microsoft BizTalk Adapter Pack 2_0 Evaluation x86.exe
3. Set extract location and select Unzip. From the root location of the installation CD, double-click AdaptersSetup.msi (for an x86-based platform) or AdaptersSetup64.msi (for an x64-based platform).

4. Read the information on the Welcome screen, and then click Next.

5. Read and accept the end-user license agreement (EULA), and then click Next.

6. In the Choose Setup Type dialog box:

To install the most common features, click Typical.

To select the adapters you want to install, click Custom, and then proceed to the next step.

To install all the features, click Complete.

Important
To install only the adapter that you will use to interface with your enterprise application, you should perform a Custom installation.

Note
For this release, Typical and Complete options essentially perform the same action.

7. Click Install.

8. In the Customer Experience Improvement Program dialog box specify I don't want to join the program at this time and click OK.

Configure BizTalk for the new Adapters

Now that the new Adapters have been installed you expect them to appear in BizTalk Administration Console, nope!

1. Right click on Adapters, select New then select Adapter...

2. Select the first adapter in the drop down list WCF-SQL and give it the same name of WCF-SQL

3. Click OK.

4. Click OK.
5. Repeat steps on 1-4 for each adapter in the drop down list.

ESB 2.0 Toolkit install batch File

Assumption

Assumptions are made that everything is installed on the one server.
The following applications are installed in their default locations

· Office 2007
· vs2008
· sql 2008
· biztalk 2009
· WSS 3.0
· UDDI is not installed.

Directory setup

Biztalk2009 contains the contents of the biztalk 2009 ISO (for the UDDI install).
BizTalkESBToolKit2_0 contains all the msi required to install ESB 2.0 toolkit plus an unzip.ps1 script.
BizTalkESBToolKit2_0\projectFiles contains files that which replace source files to build on x86 platform.

Installing UDDI

Uncheck Launch Microsoft UDDI Servers Configuration

The configuring UDDI dialog will appear select custom configuration. Make sure that require SSL for publication to this UDDI Services site is not selected

Apply configuration and close configuration window when finished

SQLXML 4.0 SP1

Click Run

ESB Configuration Tool

Microsoft.Practices.ESB.UDDIPublisher.exe select n

Dynamic Resolution Install enter username and password for current user

Biztalk ESB UDDI Publishing Service

Batch File Script

c:
"c:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe" -i

IISRESET

[BASEINSTALLDIR]Biztalk2009\setup /SetupXml [BASEINSTALLDIR]Biztalk2009\UDDI_x86\Setup.xml
"C:\Program Files\Microsoft UDDI Services\config\Configuration.exe"

IISRESET

[BASEINSTALLDIR]BizTalkESBToolkit2_0\MSChart.exe /passive
[BASEINSTALLDIR]BizTalkESBToolkit2_0\VsSDK_sfx.exe /passive
[BASEINSTALLDIR]BizTalkESBToolkit2_0\sqlxml_40_SP1.msi /passive
"[BASEINSTALLDIR]BizTalkESBToolKit2_0\BizTalk ESB Toolkit 2.0 Docs.msi" /passive
"[BASEINSTALLDIR]BizTalkESBToolKit2_0\BizTalk ESB Toolkit 2.0-x86.msi" /passive

BTSTASK Importapp -Package:"c:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Microsoft.Practices.ESB.CORE.msi" /ApplicationName:Microsoft.Practices.ESB /overwrite
"c:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Microsoft.Practices.ESB.Core.msi" /passive

BTSTASK Importapp -Package:"c:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Microsoft.Practices.ESB.JMS.msi" /ApplicationName:Microsoft.Practices.JMS /overwrite
"c:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Microsoft.Practices.ESB.JMS.msi" /passive

"c:\Program Files\Microsoft BizTalk Server 2009\Tracking\bm.exe" deploy-all -DefinitionFile:"C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bam\Microsoft.BizTalk.ESB.BAM.Exceptions.xml"
"c:\Program Files\Microsoft BizTalk Server 2009\Tracking\bm.exe" deploy-all -DefinitionFile:"C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bam\Microsoft.BizTalk.ESB.BAM.Itinerary.xml"

cd "C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bin\"
ESBConfigurationTool.exe

cd "c:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bin"
Microsoft.Practices.ESB.UDDIPublisher.exe
cd [BASEINSTALLDIR]

powershell.exe [BASEINSTALLDIR]BizTalkESBToolKit2_0\unzip.ps1 'c:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\ESBSource.zip' 'C:\Projects\Microsoft.Practices.ESB\'

attrib -r -s -h "C:\Projects\Microsoft.Practices.ESB\\Keys\*.*" /d /s
attrib -r -s -h "C:\Projects\Microsoft.Practices.ESB\\Source\*.*" /d /s

[BASEINSTALLDIR]BizTalkESBToolKit2_0\sn.exe -k "C:\Projects\Microsoft.Practices.ESB\Keys\Microsoft.Practices.ESB.snk"

copy [BASEINSTALLDIR]BizTalkESBToolKit2_0\ProjectFiles\Web.config "C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\" /Y
copy [BASEINSTALLDIR]BizTalkESBToolKit2_0\ProjectFiles\ESB.AlertService.csproj "C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.AlertService\" /Y
copy [BASEINSTALLDIR]BizTalkESBToolKit2_0\ProjectFiles\Setup.vdproj "C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.AlertService.Install\" /Y

"c:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.com" "C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.AlertService\ESB.AlertService.sln" /build Debug
"c:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.com" "C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.UDDI.PublisherService\ESB.UDDI.PublisherService.sln" /build Debug

"C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.AlertService.Install\Debug\setup.exe" /passive
"C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\\ESB.UDDI.PublisherService.Install\Debug\setup.exe" /passive

cd "C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install\Scripts\"
Management_Install.cmd

cd "c:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\"
devenv.exe /InstallVSTemplates "c:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplates\CSharp\1033\ItineraryDsl.zip"
devenv.exe /InstallVSTemplates "c:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplates\VisualBasic\1033\ItineraryDsl.zip"

2006 to 2009 Upgrade failed due to BizTalk Group name changed

 

If you change the name of your BizTalk group from BizTalk Group to something else i.e. TestBiztalkGroup. The upgrade will fail.



Upgrade Prerequisites

1. If you have Developer Tools and SDK installed as part of your 2006 R2 installation the upgrade requires Microsoft Visual Studio 2008 with Service Pack 1.

   

2. Stop the following Services
   1. World Wide Web Publishing Service
   2. Rule Engine Update Service
   3. Stop All Biztalk Host Instances

   The steps to produce upgrade failure.

   Note: From an administration point of view backup/image all machines and objects that will be effected in the upgrade just in case something goes wrong. Trust me it can happen and has happened.

   

   Select Install Microsoft Biztalk Server 2009 on this computer.

   Select Next on the Customer Information dialog.

   Select Yes, I accept the terms of the license agreement then Next on the License Agreement dialog.

   

   BizTalk Installation will detect that there is already a BizTalk 2006 R2 installation and will perform an upgrade. Now when you scroll to the bottom of the screen you will notice that there are only 2 databases present BizTalkMgmtDb and BizTalkRuleEngineDB.

   Note: this is where you should stop continuing the upgrade and go back to BizTalk Server Administration and change the custom BizTalk Group name back to BizTalk Group.

   I am continuing to show what will happen.

   Select Next on the Upgrade Summary dialog.

   Select Next on the Redistributable Prerequisites dialog.

   

   Select Upgrade on the Summary dialog.

   Everythings looks like it is installing fine until you see this screen

   

   Log File Errors

   (I have copied and pasted just the errors as log file is to large)

   [11:36:55 AM Info] Upgrade required for MGMTDB Database=BizTalkMgmtDb Server=BIZT2006TO2009

   [11:36:55 AM Warning] Failed to resolve database: Alias=MSGBOXDB, Error: 0

   [11:36:55 AM Warning] Failed to resolve database: Alias=TRACKINGDB, Error: 0

   [11:36:55 AM Warning] Failed to resolve database: Alias=BAMPRIMARYIMPORTDB, Error: 0

   [11:36:55 AM Warning] Failed to resolve database: Alias=BAMARCHIVE, Error: 0

   [11:36:55 AM Warning] Failed to resolve database: Alias=BAMSTARSCHEMADB, Error: 0

   [11:36:55 AM Warning] Failed to resolve database: Alias=TPMDB, Error: 0

   [11:36:55 AM Info] Resolved database: Alias=RULEENGINEDB.

   [11:36:55 AM Info] Upgrade required for RULEENGINEDB Database=BizTalkRuleEngineDb Server=BIZT2006TO2009

   [11:36:55 AM Warning] Failed to resolve database: Alias=BAMALERTSAPPLICATIONDB, Error: 0

   [11:36:55 AM Warning] Failed to resolve database: Alias=BAMALERTSINSTANCEDB, Error: 0

   [11:43:33 AM Info] MSI command line: ADDLOCAL=Documentation,BizTalk,WMI,Engine,Runtime,MOT,MSMQ,MsEDIAS2,MsEDIAS2StatusReporting,WCFAdapter,InfoWorkerApps,BAMPortal,WcfAdapterAdminTools,AdminTools,AdminAndMonitoring,MonitoringAndTracking,BizTalkAdminSnapIn,HealthActivityClient,BAMTools,PAM,AdditionalApps,SSOAdmin,SSOServer,RulesEngine,WssAdapterWS,OLAPNS,FBAMCLIENT,BAMEVENTAPI INSTALLDIR="C:\Program Files\Microsoft BizTalk Server 2006\" UPGRADE=1 PIDKEY="J6T48XCF7KQCGKDQV8874BJYB" USERNAME="Stargate" COMPANYNAME="Stargate Group" FILESINUSEERROR=""

   [11:43:33 AM Info] MSI command line is ADDLOCAL=Documentation,BizTalk,WMI,Engine,Runtime,MOT,MSMQ,MsEDIAS2,MsEDIAS2StatusReporting,WCFAdapter,InfoWorkerApps,BAMPortal,WcfAdapterAdminTools,AdminTools,AdminAndMonitoring,MonitoringAndTracking,BizTalkAdminSnapIn,HealthActivityClient,BAMTools,PAM,AdditionalApps,SSOAdmin,SSOServer,RulesEngine,WssAdapterWS,OLAPNS,FBAMCLIENT,BAMEVENTAPI INSTALLDIR="C:\Program Files\Microsoft BizTalk Server 2006\" UPGRADE=1 PIDKEY="J6T48XCF7KQCGKDQV8874BJYB" USERNAME="Stargate" COMPANYNAME="Stargate Group" FILESINUSEERROR=""

   [11:45:07 AM Error] AdminUpgrade::PostInstallUpgrade exception ErrorCode:-1061151936 Message:The MessageBox database does not have the correct version.

   [11:45:07 AM Info] AdminUpgrade: aborted message agent updates === Logging started at: 11:45:07 AM Tuesday, 4 August 2009 Build: 3.8.368.0 Calling process: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\EBZ15455.tmp\Setup.exe === The current user is BIZT2006TO2009\Administrator. Computer name: BIZT2006TO2009 OS Version: 5.2 Build: 3790 Service Pack: 2.0 Suite: 274 Product Type: 3

   [11:45:07 AM Info] PostInstall upgrade component for Feature: WMI, returned message: The MessageBox database does not have the correct version.

   [11:45:07 AM Error] PostInstall upgrade component for Feature: WMI failed. Error: c0c01b40

   [11:45:07 AM Info] Called FreeLibrary for WMI. Exiting CallPostInstallDllComponent.

   [11:45:07 AM Error] f:\bt\890\private\source\setup\prod\btssetup\voyager\setuphook\bts04upgrade.cpp(2808): 0XC0C01B40

   [11:45:07 AM Error] Error in postinstall upgrade, Error: Configuration Upgrade component for Feature: WMI returned: The MessageBox database does not have the correct version. ., Hresult: c0c01b40

   [11:45:07 AM Error] f:\bt\890\private\source\setup\prod\btssetup\voyager\setuphook\bts04upgrade.cpp(2684): 0XC0C01B40

   [11:45:07 AM Info] PostHook function completed upgrading to BizTalk Server 2009

   [11:45:07 AM Info] PostHook function failed upgrading to BizTalk Server 2009 with hr = c0c01b40

   [11:45:07 AM Info] Storing recovery info for TaskInfo at stage 3

   [11:45:07 AM Error] f:\bt\890\private\source\setup\prod\btssetup\voyager\setuphook\posthook.cpp(336): 0XC0C01B40

   [11:45:07 AM Info] Posthook function returned: -1061151936.

   [11:45:07 AM Info] Posthook function failed and returned the following error message: Configuration Upgrade component for Feature: WMI returned: The MessageBox database does not have the correct version. .

   [11:45:07 AM Error] Some exception may have occured while performing the post upgrade configuration. The details are : Configuration Upgrade component for Feature: WMI returned: The MessageBox database does not have the correct version. .

   [11:45:07 AM Error] Some exception may have occured while performing the post upgrade configuration. The details are : Configuration Upgrade component for Feature: WMI returned: The MessageBox database does not have the correct version. .

   [11:45:07 AM Error] f:\bt\890\private\source\common\prod\btscommon\setup\wizard\exe\progressdlg.cpp(1489): FAILED hr = c0c01b40 === Logging stopped: 11:48:24 AM Tuesday, 4 August 2009 ===

   The problem know is that you can not perform the upgrade again because there is no BizTalk 2006 R2 left and your system is corrupted.

   

   Solution

   

   Change the BizTalk Group name back to BizTalk Group

   

   Start the upgrade process again when you get to the Update Summary you will see the following.

   

   In this upgrade there are only 4 database. If you have HWS,BAM and other BizTalk components installed there will be more databases.

   

Itinerary Service For Messaging Extender

Step 1 - Creating a new Itinerary Service
Add Reference Microsoft.Practices.ESB.Itinerary from Microsoft BizTalk ESB Toolkit 2.0\Bin

implement Microsoft.Practices.ESB.Itinerary.IMessagingService.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.Practices.ESB.Itinerary;
using Microsoft.BizTalk.Component.Interop;
using Microsoft.BizTalk.Message.Interop;

namespace Sandbox.ESB
{
    class LoggingService: IMessagingService
    {
        public IBaseMessage Execute(IPipelineContext context, IBaseMessage msg, string resolverString, IItineraryStep step)
        {
            throw new NotImplementedException();
        }
        
        public bool ShouldAdvanceStep(IItineraryStep step, IBaseMessage msg)
        {
            throw new NotImplementedException();
        }
        
        public string Name
        {
            get { throw new NotImplementedException(); }
        }
        
        public bool SupportsDisassemble
        {
            get { throw new NotImplementedException(); }
        }
    }
}

The following site http://msdn.microsoft.com/en-us/library/ee250158%28BTS.10%29.aspx explains each of the following methods that need to be implemented

Step 2 Add the Itineray Service to the ESB.config

<itineraryService id="00000000-0012-0004-1973-000000000001" name="Sandbox.ESB.Services.Logging" type="Sandbox.ESB.LoggingService, Sandbox.ESB, Version=1.0.0.0, Culture=neutral, PublicKeyToken=354cb85f9213cd3b" scope="Messaging" stage="AllReceive"/>

Step 3

Now in visual studio drop a Itinerary Service, select the Itinerary Service Extender to be Messaging Messaging Extender...

When you go to chose the Service Name your Service should appear in the drop down list. If not it is possible that the ESB is configured to be using the SSO. Since the esb.config has changed, SSO does not automatically update itself. Go to Microsoft BizTalk ESB Toolkit 2.0\Bin\ESBConfigurationTool.exe and unconfigure and reconfigure SSO or just point to the file configuration source.

logon profile not working

If you experience these windows vista errors:

Windows cannot log you on because your profile cannot be loaded. Check that you are connected to the network, and that your network is functioning correctly.
Windows cannot load the user's profile but has logged you on with the default profile for the system.
Windows cannot load the locally stored profile. Possible causes of this error include insufficient security rights or a corrupt local profile.
The winlogon notification subscriber failed a notification event.
The winlogon notification subscriber failed a critical notification event.
The content source cannot be accessed.
The winlogon notification subscriber failed a notification event.

Solution to fix your user profile
http://www.vistax64.com/tutorials/130095-user-profile-service-failed-logon-user-profile-cannot-loaded.html

Regards

Java Development

If you ever have to do some java development, how do you get started?

Development
IDE: http://www.netbeans.org/

hosting java web applications is done via glassfish (https://glassfish.dev.java.net/ ) on the dev machine this should be automatically be installed with netbeans IDE.

Test and Production
Install Sun GlassFish Enterprise Server (formerly Sun Java System Application Server) http://www.sun.com/software/products/appsrvr
Download http://java.sun.com/javaee/downloads/index.jsp?userOsIndex=6&userOsId=windows&userOsName=Windows
Installation bug when trying to run glassfish as a service. http://wiki.glassfish.java.net/Wiki.jsp?page=FaqRunAsWindowsService

Deploying web application to Test and Production
Right click on solution and select Clean and Build

Navigate to your solution\dist directory a filename.war will be created this is the equivalent to an msi file. Login to glassfish admin

Navigate to web applications and select deploy

Browse to .war file and select OK

Windows Service Installer

Creating Sample Service

Bellow are the steps required to create the sample .NET Service

1. Startup Visual Studio, and select the C Sharp node under Project Types. Under Templates, select Windows Service and name the project MyWinService.
2. Under Solution Explorer, select the file name Service1.cs, and change it to MyWinService.cs under Properties section.
3. Open MyWinService.cs in design mode. Right-Click on the design area and choose Add Installers. This will place two components called ServiceProcessInstaller1 and ServiceInstaller1 onto the design area.
4. Select ServiceInstaller1, change its name to MyWinServiceInstaller. Also change the ServiceName from Service1 to MyWinService.
5. Select ServiceProcessInstaller1, and change its name to MyWinServiceProcessInstaller.

Create Setup Project

1. On the Solution node right click and Add-> New Project.
2. In Add New Project dialog, navigate to Project Types->Other Project Types->Setup and Deployment and select Template Setup Project. Set Name to MyWinServiceInstaller.
3. Right click on MyWinServiceInstaller and select Add->Project Output.
4. In Add Project Output Group dialog select MyWinService Project in the drop down list and select Primary output.
5. Create Custom action by right clicking on MyWinServiceInstaller->View->Custom Actions. The Custom Actions tab will appear. Custom actions will install/uninstall the service instead of manually running installutil.
6. Right click on Install->Add Custom Action. In the Select Item in Project dialog navigate to Application Folder->Primary output from MyWinService.
7. Repeat step 6 for uninstall.

Build install project and install msi.