ESB.NET Core PreRequisites and Installation Instructions(Mina's blog)

ESB Management Console - 1600x1200 screen resolution recommended for running/viewing the Management Console.

You can also couple it with Windows Workflow to build a rudimentary BPM system.

To be officially released when the .NET Framework 3.0 is released (and we get some time here to do it!!!).



DOWNLOAD DETAILS
Lightweight Distributed Enterprise Service Bus. Build 5.1.0.0 deployment package.
You will also need the pre-requisite software listed below before installing & running ESB.NET.
Note that WSE 2.x is no longer supported. WSE 3 is required.

Recommended configuration

• Windows 2003 Enterprise* Server Required Components
• MSMQ - Private Queues - no AD required
• Microsoft .NET Framework 2.0
• IIS - ASP.NET 2.0

PreRequisites

• WSE3.0 - For WSE3.0 Transport adaptor
• Microsoft.NET Framework 3.0 - For WCF Transport adaptor
• IE Web Controls - For Management Console

Installation

Method 1 - Run Installer - Optional one time only install
Running the Installer copies all files into the selected directory and registers a component for MSMQ Triggers.
You then run Setup.cmd (see below) to setup the IIS Virtual Directories.
You can omit Step 5 below if you do this step.

Method 2 - Multi-Instance configuration - Run to setup multiple instances.

Step 1 - Run Setup.cmd

To Create Virtual Directories, run: Source\ESB\Base\Solutions\Main\Setup\Setup.cmd
(or the setup.cmd in the root directory which calls this)
Note:
After you run the installation script, Source\ESB\Base\Solutions\Main\Setup\Setup.cmd, you will have something like the following in IIS:

Windows XP deployment (Instead of Win2k3)
Also, if running under Windows XP, you may want to create a different user for the ASP.NET services to run under, in which case, make the following change to your machine.config file (in the %windir%\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG directory).
<system.web>

<processModel autoConfig="true" userName="ESBUser" password="ESBPassword"/>


This will create the Virtual Directory Tree as shown above.
The two key Virtual Directories are:
Management
and
CoreInternetTransportAdaptors

Step 2 Create App Pool in IIS

After you run the scripts to create the IIS Virtual Directories, create an app pool (IIS6) and add the Virtual Directories to that app pool. Do it at the ESB level to save you having to do this multiple times. Assign the user for this app pool full NTFS priviliges to the ESB tree in the file system. Also, in the IIS directory security for those Virtual Directories, use the ESBUser account for the anonymous website access as well. You can later tighten security further as required.

• SQL Server 2000 or 2005 (Enterprise, Standard, Express, MSDE)

Step 3 - Create DB manually

Create Database, Default database name (in config files etc.) is ESBLog.

Step 4 - Run DB Script

Source\ESB\Base\Solutions\Main\Setup\InstallScripts\Database\ESBLog_SQL2k.sql

or, if you have SQL Server 2005 and want to be able to use XQuery to do rudimentary BAM (& use the soon to be released lightweight BAM Service Adaptor), run the following script

Source\ESB\Base\Solutions\Main\Setup\InstallScripts\Database\ESBLog_SQL2k5.sql

Note: You will have to manually delete any existing tables if you've already run the ESBLog_SQL2k.sql script. These are the two tables - ESBLog and ESBLogSummary tables.

which uses XML datatypes instead of the standard varchar datatype. You will also have to set the following value to true (default config setting).

<add key="MsSqlLogger.IsMsSql2005" value="true"/>

Check out the blogs on sample XQuery queries to query your log data. You can then use this as-is or in conjunction with a BAM Service adaptor to form the basis of BAM functionality.

Step 5 - Setup MSMQ Triggers & Trigger Rules Configuration

MSMQTriggersEntryPoint Required for all async processing

Run:
MSMQTriggers_Deploy.reg - MSMQ Triggers & Trigger Rules.

and
Source\ESB\Base\Solutions\Main\Setup\ESBNETASyncTransportInstall\Release\ESBNETASyncTransportInstall.msi

*Windows 2003 Enterprise required only for Network Load Balancing feature.



You may also wish to use some of the WSE Trace Tools to view messages entering and leaving ESB.NET.

Step 6 - Optional if you are running Sharepoint

If you're running the ESB services on a Sharepoint website, then you will need to do the following:

1. Exclude the ESB virtual directory from the Sharepoint managed sites by doing the following:
2. In the Sharepoint admin website,
3. Select "Configure Virtual Server Settings"
4. Select "Default Website" or whatever website you've installed ESB.NET to
5. Under "Virtual Server Management" select "Define Managed Paths"
6. In the "Add a new path" textbox, type in "/ESB"
7. In the radio button list, select "Exclude"
8. Click OK. The entry should be listed in the list of excluded paths above.
9. Exclude the "webctrl_client" virtual directory in the same way. This is used by the IE Web Controls and will not be required in future.
10. Change the trust levels in the Sharepoint web.config file (usually in C:\Inetpub\wwwroot\web.config as shown below)

<!--<trust level="WSS_Minimal" originUrl="" processRequestInApplicationTrust="false" />-->
<trust level="Full" originUrl="" processRequestInApplicationTrust="false" />
11. Enable Session State...
... by adding this line in the Sharepoint web.config file (usually in C:\Inetpub\wwwroot\web.config as shown below but commented out, so all you should need to do is uncomment it)

<add name="Session" type="System.Web.SessionState.SessionStateModule"/>

and also changing the value of the enableSessionState attribute to true.

<pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="false" enableEventValidation="false">

posted on 2007-04-09 09:34 Ahao_Oristand 阅读(591) 评论(0)  编辑  收藏