The OBE build system is highly configurable and can easily be adapted to run on any J2EE application server that is supported by XDoclet. The OBE server runtime is known to work with the following application servers:
JBoss 3.2.3+ JBoss 4.0.1+ (but not JBoss 4.0) WebLogic 7.x WebLogic 8.x Note that of these, only JBoss 4.0.1 supports Servlet 1.3 as required by the OBE Web-based Worklist Handler client ------------------------------------------------------------------------------------------
2、運行obe的應用服務器的資源配置（這段內容說明了運行obe所需要的數據源、JMS隊列以及JAAS） ------------------------------------------------------------------------------------------ Configure the application server, to ensure that the resources required by OBE will be available. The resources required include:
One DataSource, JNDI name (default 'MySQLDS') to match Two JMS Queues, JNDI names 'OBEAsyncRequest' and 'OBEApplicationEvent'. One JAAS Configuration, default name 'other' ------------------------------------------------------------------------------------------
3、關于運行obe的JBoss服務器的配置（這段內容說明了如何配置Jboss應用服務器） ------------------------------------------------------------------------------------------ OBE provides some preconfigured resources for use with JBoss, under ${staging.dir}/j2ee/jboss. The conf and deploy Directories can be copied to the ${as.dir}/server/default directory - you will need to rename / edit the *-ds.xml data source definition file in the conf directory to suit your database type and connection properties. The 'default' server configuration should be adequate for most purposes. Do not use the 'minimal' server configuration - it does not provide all the J2EE container functionality required by OBE.
Note that OBE provides a modified version of the Castor XML library that fixes certain critical bugs, so it is necessary either to delete the one that comes with JBoss in ${jboss.home}/server/default/deploy/snmp-adaptor.sar, or to replace it with the OBE version (castor-0.9.5.3.jar) if you wish to use the JBoss SNMP adaptor. This incompatibility is the result of the JBoss UnifiedClassLoader3 merging the classpaths of the various J2EE applications. ------------------------------------------------------------------------------------------
################################################## ### 運行環境說明 ################################################## 1、操作系統：Windows2000 pro 2、JBoss(4.0.1):(http://sourceforge.net/project/showfiles.phpgroup_id=22866&package_id=16942&release_id=305380) 3、MySQL(4.14):(http://www.mysql.com) 4、JDBC驅動程序:我使用的是mysql-connector-java-3.1.7-bin.jar，最新的驅動程序可以在(http://dev.mysql.com/downloads/connector/j)下載
################################################## ### 在MySQL中創建運行obe需要的數據庫、用戶名和密碼 ################################################## mysql>create database obe; mysql>grant all on *.* to obe@localhost identified by 'obe' with grant option;
<!-- $Id: mysql-ds.xml,v 1.3.2.1 2004/12/01 11:46:00 schrouf EXP $ --> <!-- Datasource config for MySQL using 3.0.9 available from: http://www.mysql.com/downloads/api-jdbc-stable.Html -->
<datasources> <local-tx-datasource> <jndi-name>DefaultDS</jndi-name> <connection-url>jdbc:mysql://localhost:3306/obe</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> <user-name>obe</user-name> <password>obe</password> <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name> <!-- sql to call when connection is created <new-connection-sql>some arbitrary sql</new-connection-sql> --> <!-- sql to call on an existing pooled connection when it is oBTained from pool <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql> -->
<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) --> <metadata> <type-mapping>mySQL</type-mapping> </metadata> </local-tx-datasource> </datasources> ------------------------------------------------------------------------------------------ 4、由于$JBOSS_HOME/server/default/deploy目錄下的hsqldb-ds.xml文件配置的數據源也為DefaultDS,所以必須把這個文件刪除掉
