OSWorkflow + oracle 配置
来源:互联网 发布:电脑网络不好怎么办 编辑:程序博客网 时间:2024/04/28 07:32
本文所讲的例子是对OSWorkflow网站例子程序的完善和补充,osworkflow自带例子主要是针对内存中运行的工作流,用户,组,工作流 实例都是在内存中的。由于实际工作中,用户及组的信息是要入库的,所以本文主要讲解:OSWorkflow数据库方面的配置。读者可以先在官方下载 OSWorkflow的例子,再按以下方法修改相关配置。
我运行本例子时用的软件版本是
osworkflwo2.8.0
oracle 10g
jdk 1.5
tomcate 5.5.12
如果要成功运行本例子, 有一个地方要特别注意, 那就是oracle的驱动程序ojdbc14.jar一定要放在 Tomcate5.X / common/lib 这个目录下。
在下载的zip包中,有一个osworkflow-2.8.0-example.war包,可以直接在容器中解压运行。
修改如下配置文件:
1.osworkflow.xml修改成如下:该文件负责工作相关信息入库配置。
<osworkflow>
<!--
<persistence class="com.opensymphony.workflow.spi.memory.MemoryWorkflowStore"/>
-->
<persistence class="com.opensymphony.workflow.spi.jdbc.JDBCWorkflowStore">
<!-- For jdbc persistence, all are required. -->
<property key="datasource" value="jdbc/DefaultDS"/>
<!-- 注意:本配置是基于oracle数据库,如果是其他数据库,请修改entry.sequence和step.sequence对应的value -->
<property key="entry.sequence"
value="SELECT seq_os_wfentry.nextval FROM dual" />
<property key="entry.table" value="OS_WFENTRY"/>
<property key="entry.id" value="ID"/>
<property key="entry.name" value="NAME"/>
<property key="entry.state" value="STATE"/>
<property key="step.sequence"
value="SELECT seq_os_currentsteps.nextval FROM dual" />
<property key="history.table" value="OS_HISTORYSTEP"/>
<property key="current.table" value="OS_CURRENTSTEP"/>
<property key="historyPrev.table" value="OS_HISTORYSTEP_PREV"/>
<property key="currentPrev.table" value="OS_CURRENTSTEP_PREV"/>
<property key="step.id" value="ID"/>
<property key="step.entryId" value="ENTRY_ID"/>
<property key="step.stepId" value="STEP_ID"/>
<property key="step.actionId" value="ACTION_ID"/>
<property key="step.owner" value="OWNER"/>
<property key="step.caller" value="CALLER"/>
<property key="step.startDate" value="START_DATE"/>
<property key="step.finishDate" value="FINISH_DATE"/>
<property key="step.dueDate" value="DUE_DATE"/>
<property key="step.status" value="STATUS"/>
<property key="step.previousId" value="PREVIOUS_ID"/>
</persistence>
<factory class="com.opensymphony.workflow.loader.XMLWorkflowFactory">
<property key="resource" value="workflows.xml" />
</factory>
</osworkflow>
<!--
<persistence class="com.opensymphony.workflow.spi.memory.MemoryWorkflowStore"/>
-->
<persistence class="com.opensymphony.workflow.spi.jdbc.JDBCWorkflowStore">
<!-- For jdbc persistence, all are required. -->
<property key="datasource" value="jdbc/DefaultDS"/>
<!-- 注意:本配置是基于oracle数据库,如果是其他数据库,请修改entry.sequence和step.sequence对应的value -->
<property key="entry.sequence"
value="SELECT seq_os_wfentry.nextval FROM dual" />
<property key="entry.table" value="OS_WFENTRY"/>
<property key="entry.id" value="ID"/>
<property key="entry.name" value="NAME"/>
<property key="entry.state" value="STATE"/>
<property key="step.sequence"
value="SELECT seq_os_currentsteps.nextval FROM dual" />
<property key="history.table" value="OS_HISTORYSTEP"/>
<property key="current.table" value="OS_CURRENTSTEP"/>
<property key="historyPrev.table" value="OS_HISTORYSTEP_PREV"/>
<property key="currentPrev.table" value="OS_CURRENTSTEP_PREV"/>
<property key="step.id" value="ID"/>
<property key="step.entryId" value="ENTRY_ID"/>
<property key="step.stepId" value="STEP_ID"/>
<property key="step.actionId" value="ACTION_ID"/>
<property key="step.owner" value="OWNER"/>
<property key="step.caller" value="CALLER"/>
<property key="step.startDate" value="START_DATE"/>
<property key="step.finishDate" value="FINISH_DATE"/>
<property key="step.dueDate" value="DUE_DATE"/>
<property key="step.status" value="STATUS"/>
<property key="step.previousId" value="PREVIOUS_ID"/>
</persistence>
<factory class="com.opensymphony.workflow.loader.XMLWorkflowFactory">
<property key="resource" value="workflows.xml" />
</factory>
</osworkflow>
2. osuser.xml修改成如下:该文件负责用户及组的入库配置。
注意:datasource可能必须是java:comp/env/jdbc/DefaultDS
<opensymphony-user>
<provider class="com.opensymphony.user.provider.jdbc.JDBCAccessProvider">
<property name="user.table">os_user</property>
<property name="group.table">os_group</property>
<property name="membership.table">os_membership</property>
<property name="user.name" >username</property>
<property name="user.password">passwordhash</property>
<property name="group.name">groupname</property>
<property name="membership.userName" >username</property>
<property name="membership.groupName">groupname</property>
<!-- <property name="datasource">jdbc/DefaultDS</property>-->
<property name="datasource">java:comp/env/jdbc/DefaultDS</property>
</provider>
<provider class="com.opensymphony.user.provider.jdbc.JDBCCredentialsProvider">
<property name="user.table">os_user</property>
<property name="group.table">os_group</property>
<property name="membership.table">os_membership</property>
<property name="user.name" >username</property>
<property name="user.password">passwordhash</property>
<property name="group.name">groupname</property>
<property name="membership.userName" >username</property>
<property name="membership.groupName">groupname</property>
<!-- <property name="datasource">jdbc/DefaultDS</property>-->
<property name="datasource">java:comp/env/jdbc/DefaultDS</property>
</provider>
<provider class="com.opensymphony.user.provider.jdbc.JDBCProfileProvider">
<property name="user.table">os_user</property>
<property name="group.table">os_group</property>
<property name="membership.table">os_membership</property>
<property name="user.name" >username</property>
<property name="user.password">passwordhash</property>
<property name="group.name">groupname</property>
<property name="membership.userName" >username</property>
<property name="membership.groupName">groupname</property>
<!-- <property name="datasource">jdbc/DefaultDS</property>-->
<property name="datasource">java:comp/env/jdbc/DefaultDS</property>
</provider>
<!--
<provider class="com.opensymphony.user.provider.memory.MemoryAccessProvider" />
<provider class="com.opensymphony.user.provider.memory.MemoryCredentialsProvider" />
<provider class="com.opensymphony.user.provider.memory.MemoryProfileProvider" />
-->
<!--
Authenticators can take properties just like providers.
This smart authenticator should work for 'most' cases - it dynamically looks up
the most appropriate authenticator for the current server.
-->
<authenticator class="com.opensymphony.user.authenticator.SmartAuthenticator" />
</opensymphony-user>
<provider class="com.opensymphony.user.provider.jdbc.JDBCAccessProvider">
<property name="user.table">os_user</property>
<property name="group.table">os_group</property>
<property name="membership.table">os_membership</property>
<property name="user.name" >username</property>
<property name="user.password">passwordhash</property>
<property name="group.name">groupname</property>
<property name="membership.userName" >username</property>
<property name="membership.groupName">groupname</property>
<!-- <property name="datasource">jdbc/DefaultDS</property>-->
<property name="datasource">java:comp/env/jdbc/DefaultDS</property>
</provider>
<provider class="com.opensymphony.user.provider.jdbc.JDBCCredentialsProvider">
<property name="user.table">os_user</property>
<property name="group.table">os_group</property>
<property name="membership.table">os_membership</property>
<property name="user.name" >username</property>
<property name="user.password">passwordhash</property>
<property name="group.name">groupname</property>
<property name="membership.userName" >username</property>
<property name="membership.groupName">groupname</property>
<!-- <property name="datasource">jdbc/DefaultDS</property>-->
<property name="datasource">java:comp/env/jdbc/DefaultDS</property>
</provider>
<provider class="com.opensymphony.user.provider.jdbc.JDBCProfileProvider">
<property name="user.table">os_user</property>
<property name="group.table">os_group</property>
<property name="membership.table">os_membership</property>
<property name="user.name" >username</property>
<property name="user.password">passwordhash</property>
<property name="group.name">groupname</property>
<property name="membership.userName" >username</property>
<property name="membership.groupName">groupname</property>
<!-- <property name="datasource">jdbc/DefaultDS</property>-->
<property name="datasource">java:comp/env/jdbc/DefaultDS</property>
</provider>
<!--
<provider class="com.opensymphony.user.provider.memory.MemoryAccessProvider" />
<provider class="com.opensymphony.user.provider.memory.MemoryCredentialsProvider" />
<provider class="com.opensymphony.user.provider.memory.MemoryProfileProvider" />
-->
<!--
Authenticators can take properties just like providers.
This smart authenticator should work for 'most' cases - it dynamically looks up
the most appropriate authenticator for the current server.
-->
<authenticator class="com.opensymphony.user.authenticator.SmartAuthenticator" />
</opensymphony-user>
3. 加入propertyset.xml文件,该文件是工作流中所有属性入库的配置文件,有点像Hibernate的hbm映射文件:
<propertysets>
<propertyset name="jdbc"
class="com.opensymphony.module.propertyset.database.JDBCPropertySet">
<arg name="datasource" value="java:comp/env/jdbc/DefaultDS"/>
<arg name="table.name" value="OS_PROPERTYENTRY"/>
<arg name="col.globalKey" value="GLOBAL_KEY"/>
<arg name="col.itemKey" value="ITEM_KEY"/>
<arg name="col.itemType" value="ITEM_TYPE"/>
<arg name="col.string" value="STRING_VALUE"/>
<arg name="col.date" value="DATE_VALUE"/>
<arg name="col.data" value="DATA_VALUE"/>
<arg name="col.float" value="FLOAT_VALUE"/>
<arg name="col.number" value="NUMBER_VALUE"/>
</propertyset>
</propertysets>
<propertyset name="jdbc"
class="com.opensymphony.module.propertyset.database.JDBCPropertySet">
<arg name="datasource" value="java:comp/env/jdbc/DefaultDS"/>
<arg name="table.name" value="OS_PROPERTYENTRY"/>
<arg name="col.globalKey" value="GLOBAL_KEY"/>
<arg name="col.itemKey" value="ITEM_KEY"/>
<arg name="col.itemType" value="ITEM_TYPE"/>
<arg name="col.string" value="STRING_VALUE"/>
<arg name="col.date" value="DATE_VALUE"/>
<arg name="col.data" value="DATA_VALUE"/>
<arg name="col.float" value="FLOAT_VALUE"/>
<arg name="col.number" value="NUMBER_VALUE"/>
</propertyset>
</propertysets>
在webapp目录下,在META-INF目录中新建一个context.xml。参考如下
<?xml version="1.0" encoding="UTF-8"?>
<Context reloadable="true" crossContext="true">
<Resource name="jdbc/DefaultDS" auth="Container"
type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@127.0.0.1:1521:ora9i" username="oswf"
password="oswf" maxActive="10" maxIdle="5" maxWait="-1" />
</Context>
<Context reloadable="true" crossContext="true">
<Resource name="jdbc/DefaultDS" auth="Container"
type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@127.0.0.1:1521:ora9i" username="oswf"
password="oswf" maxActive="10" maxIdle="5" maxWait="-1" />
</Context>
- OSWorkflow + oracle 配置
- osworkflow与Oracle数据连接配置
- OSWorkflow数据库配置
- osworkflow配置说明
- OSWorkFlow深入浅出(2)---配置
- OSWorkflow学习笔记 JDBC配置
- osworkflow配置及演示DEMO
- OSWorkFlow
- osworkflow
- OSWorkflow
- OSWorkflow
- osworkflow
- 配置OSWorkFlow通过Hibernate持久化
- 在myeclipse下配置osworkflow的环境
- 配置OSWorkFlow通过Hibernate持久化
- osworkflow基于JDBC存储实现的表结构(oracle)
- osworkflow的流程定义文件的type怎么配置?
- 今天被osworkflow的数据库配置(mysql)困住了
- 一个好友推荐的简单实现
- HAPPY QUESTION 的问题
- symbian sms 需要的库文件 etelbgsm.h and etelgprs.h
- 如何改掉口味过重的毛病
- 最大间隙问题
- OSWorkflow + oracle 配置
- 阿格流斯之踵
- 瑞星2008主动防御体系分析
- 公平的法律
- 面试自我介绍时应掌握的三个要点
- 存储过程以及函数加密
- 日常饮食最常见的七大错误
- 广为流传的一个关于项目管理的通俗讲解
- Hello World