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 DETAILSLightweight 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:
- Exclude the ESB virtual directory from the Sharepoint managed sites by doing the following:
- In the Sharepoint admin website,
- Select "Configure Virtual Server Settings"
- Select "Default Website" or whatever website you've installed ESB.NET to
- Under "Virtual Server Management" select "Define Managed Paths"
- In the "Add a new path" textbox, type in "/ESB"
- In the radio button list, select "Exclude"
- Click OK. The entry should be listed in the list of excluded paths above.
- 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.
- 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">
新報告的內容安排如下：
1.?????
系統總體技術架構圖
SOA
（具體圖附在最后了）
1)?????
簡要介紹每個抽象層和模塊的功能作用
2)?????
系統功能分解圖
類圖
????????????????
用來說明整個系統的詳細功能
用例圖
2.?????
詳細構造每個抽象層，介紹每個抽象層中的工作重點及成果等
1)?????
展示服務層
2)?????
業務流程層
A.??????
提取出系統中的業務場景
B.??????
根據
A
畫出具體簡要的工作流圖
C.??????
（待續）
3)?????
服務接口層
該層是整個系統設計的關鍵層。（服務的設計過程我們在這里詳細介紹，不過這里也存在很多的問題，我在理解上就不夠透徹，寫出來給人的感覺也是比較理論化，并不象是實際成果。內容上也比較多，如何有效的簡化）
編排服務層
業務服務層
連通服務層
應用服務層
在這一部分得出系統的服務詳細劃分圖。
其中，連通服務層中主要介紹一下企業服務總線
ESB
，詳細的敘述了
ESB
中網關的設計過程。（但是項目中沒有實現該部分）
4)?????
應用層：主要根據應用服務層中設計的應用服務來實現其功能
5)?????
數據資源層：介紹資源存儲信息等。
3.
簡單介紹
WebService
的實現??
??????? 需求描述：首先有Computable()這么一個類，其中有些方法比如：add，sub，div等等，然后我們現在想要對這些方法進行一些處理，對每個方法的操作添加日志信息，那么我們如何做才能夠很好的實現這樣一個功能呢，如何保證代碼的可擴展性，提高代碼的質量呢
interface?Computerable()
{
????? Object?Compute();
}???????
??????? 前端控制器的概念，提到了一個例子，飯店中服務員與廚師。服務員將客人?需要的飯菜情況的單子給前臺，然后由前臺負責將她分配給空閑的廚師，然后菜做好了廚師告訴前臺，由前臺告訴服務員菜該送到哪個客人那里。前臺在這里就是一個前端控制器Front Controller。
???????? 還有內部匿名類的用法，抽空看看。
??????? 記得老師說過，能夠很好的在程序中使用反射機制，是判斷中級程序員和高級程序員的一個重要區別。他說是某個項目經理這么說的，管他呢，總之好好學習就是了。
????????留下來的需要講解的東西：反射機制的效率一般都很低，如何結合緩存機制提高它的效率問題。
時間比較緊，有空再修改