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。
还有内部匿名类的用法，抽空看看。
记得老师说过，能够很好的在程序中使用反射机制，是判断中级程序员和高级程序员的一个重要区别。他说是某个项目经理这么说的，管他呢，总之好好学习就是了。
留下来的需要讲解的东西：反射机制的效率一般都很低，如何结合缓存机制提高它的效率问题。
时间比较紧，有空再修改