ESB Guidance Setup Walk through (DRAFT)

prerequisites:

SETUP BAM
SETUP UDDI on SERVER 2003

install updates.
install entlib 3.1
install dundas web chart

PROCESS:

1. UNPACK THE SOURCE
2. CREATE THE TWO DATABASES USING THE SCRIPTS (ADMIN AND EXCEPTION) in “\Source\Samples\Management Portal\SQL\esb.administration database.sql” and
“\Source\Exception Handling\SQL\ESB.ExceptionHandling.Database\Create Scripts\EsbExceptionDb_CREATE.sql”

3. OPEN THE PROJECT SOLUTION, NEED TO MAKE CHANGES TO LINES 1088, 1233 IN ProcessFault.cs, and LINE 316 in ExceptionMgmt.cs to allow the ALL.Exceptions SEND PORT HANDLE NON-STANDARD DATE FORMATS. (ref http://www.codeplex.com/esb/WorkItem/View.aspx?WorkItemId=4430)

4. OPEN THE FILE \Source\Core\Install\Scripts\PREPROCESSINGCORE.VBS IN A TEXT EDITOR, CHANGE THE USER ID AND PASSWORD TO THE CREDENTIALS WHICH THE BIZTALK HOST INSTANCE RUNS UNDER.

5. RUN THE FILE \Source\Core\Install\Scripts\PREPROCESSINGCORE.VBS

6. THE ABOVE FILE SHOULD SETUP VIRTUAL DIRECTORIES FOR ALL OF THE ESB GUIDANCE WEB SERVICES, HOWEVER I HAD TO MANUALLY DO THIS. THE WEB SERVICES AND APP POOLS ARE AS FOLLOWS (THESE ARE ALL IN \SOURCE\):

\Services\ESB.ExceptionHandlingServices (ESBAppPool)
\Services\ESB.ExceptionHandlingServices.WCF (ESBWcfAppPool)
\Services\ESB.ItineraryServices (ESBAppPool)
\Services\ESB.ItineraryServices.WCF (ESBWcfAppPool)
\Services\ESB.ItineraryServices.Response (ESBAppPool)
\Services\ESB.ItineraryServices.Response.WCF (ESBWcfAppPool)
\Services\ESB.ResolverServices (ESBNetworkAppPool)
\Services\ESB.ResolverServices.WCF (ESBNetworkAppPool)
\Services\ESB.TransformServices (ESBAppPool)
\Services\ESB.TransformServices.WCF (ESBWcfAppPool)
\Services\ESB.BizTalkOperationsService (ESBNetworkAppPool)
\Services\ESB.UDDIService (ESBNetworkAppPool) 8.

7. RUN THE FILE \Source\Core\Install\Scripts\1.Install_Prerequisites.cmd

8. FOR THE ABOVE YOU MAY NEED TO CONFIGURE IIS FOR NEGOTIATION IF YOU GET AN ERROR RUNNING THE INSTALL SCRIPTS: http://www.codeplex.com/esb/Thread/View.aspx?ThreadId=18149

9. RUN THE FILE \Source\Core\Install\Scripts\1.CORE_CreateBizTalkApplication.cmd

10. CHANGE THE ALL.Exceptions SEND PORT TO POINT TO EXCEPTION DATABASE ON THE LOCAL MACHINE

11. In BTSNTSvc.exe.config, below the <configuration> element, add:
<configSections>
  <section name=”xlangs”
           type=”Microsoft.XLANGs.BizTalk.CrossProcess.XmlSerializationConfigurationSectionHandler,
                 Microsoft.XLANGs.BizTalk.CrossProcess” />
</configSections>

12. In BTSNTSvc.exe.config, above the closing </configuration> element, add:
<xlangs>
  <Configuration>
    <AppDomains AssembliesPerDomain=”10″>
      <DefaultSpec SecondsIdleBeforeShutdown=”1200″
                   SecondsEmptyBeforeShutdown=”1800″/>
      <AppDomainSpecs>
        <AppDomainSpec Name=”Microsoft.Practices.ESB”>
          <BaseSetup>
            <ConfigurationFile>
              [path]\Microsoft.Practices.ESB.PipelineComponents.config
            </ConfigurationFile>
          </BaseSetup>
        </AppDomainSpec>
      </AppDomainSpecs>
      <PatternAssignmentRules>
        <PatternAssignmentRule
                AssemblyNamePattern=”Microsoft.Practices.ESB.*”
                AppDomainName=”Microsoft.Practices.ESB” />
      </PatternAssignmentRules>
    </AppDomains>
  </Configuration>
</xlangs>

13. In c:\windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config, below the opening <configSections> element, add:
<sectionGroup name=”ESBProcessor”>
  <section name=”Resolver”
           type=”System.Configuration.DictionarySectionHandler,
                 System,Version=2.0.0.0,Culture=neutral,
                 PublicKeyToken=b77a5c561934e089″/>
  <section name=”AdapterProvider”
           type=”System.Configuration.DictionarySectionHandler,
                 System,Version=2.0.0.0,Culture=neutral,
                 PublicKeyToken=b77a5c561934e089″/>
  <section name=”ItineraryCache” 
           type=”System.Configuration.DictionarySectionHandler,
                 System,Version=2.0.0.0,Culture=neutral,
                 PublicKeyToken=b77a5c561934e089″/>
  <section name=”Cache”
           type=”System.Configuration.DictionarySectionHandler,
                 System,Version=2.0.0.0,Culture=neutral,
                 PublicKeyToken=b77a5c561934e089″/>
</sectionGroup>

14. In c:\windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config, above the closing </configuration> element, add:
  <ESBProcessor>
    <Resolver>
       <add key=”UDDI” value=”Microsoft.Practices.ESB.Resolver.UDDI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a” />
       <add key=”WSMEX” value=”Microsoft.Practices.ESB.Resolver.WSMEX, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a” />
       <add key=”XPATH” value=”Microsoft.Practices.ESB.Resolver.XPATH, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a” />
       <add key=”STATIC” value=”Microsoft.Practices.ESB.Resolver.STATIC, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a” />
       <add key=”BRE” value=”Microsoft.Practices.ESB.Resolver.BRE, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a” />
    </Resolver>
    <AdapterProvider>
       <add key=”WCF-WSHttp” value=”Microsoft.Practices.ESB.Adapter.WcfWSHttp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a” />
       <add key=”WCF-BasicHttp” value=”Microsoft.Practices.ESB.Adapter.WcfBasicHttp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a” />
       <add key=”FTP” value=”Microsoft.Practices.ESB.Adapter.FTP, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a” />
       <add key=”FILE” value=”Microsoft.Practices.ESB.Adapter.FILE, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a” />
       <add key=”MQSeries” value=”Microsoft.Practices.ESB.Adapter.MQSeries, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a” />
    </AdapterProvider>
    <ItineraryCache>
       <add key=”timeout” value=”120″ />
    </ItineraryCache>
    <Cache>
       <add key=”UDDI” value=”600″ />
       <add key=”WSMEX” value=”600″ />
    </Cache>
  </ESBProcessor>

15. Open the portal \Source\Samples\Management Portal\ESB.Portal\esb.portal.sln solution and remove and re add the reference to dundas web chart.

16. Build the portal solution and make sure it compiles.

17. Create a IIS website and point it at the existing directory C:\source\Source\Samples\Management Portal\ESB.Portal\. Turn off anonymous access and enable integrated windows authentication. Make sure it is running under asp.net 2.

18. to test the portal create a new “biztalk application user” and “biztalk server administrator” to test.

b.

Technorati tags: , ,

Leave a Reply

Your email address will not be published. Required fields are marked *