Website Downloads Documentation Knowledgebase Wiki Issue tracker Commercial support

Changes between Daisy 1.5.1 (rev. 3446) and Daisy 2.0 RC (rev. 3856)

Revision 3842 (Mar 16, 2007)

Upgraded to final jBPM 3.2 release. Apparently the schema changed a bit, so drop the workflow tables by executing the following SQL on the daisyrepository database.

Warning: this will remove all your workflow data.

delete from daisy_system where propname = 'jbpm_schema_version';

SET FOREIGN_KEY_CHECKS=0;
drop table JBPM_ACTION;
drop table JBPM_BYTEARRAY;
drop table JBPM_BYTEBLOCK;
drop table JBPM_COMMENT;
drop table JBPM_DECISIONCONDITIONS;
drop table JBPM_DELEGATION;
drop table JBPM_EVENT;
drop table JBPM_EXCEPTIONHANDLER;
drop table JBPM_ID_GROUP;
drop table JBPM_ID_MEMBERSHIP;
drop table JBPM_ID_PERMISSIONS;
drop table JBPM_ID_USER;
drop table JBPM_JOB;
drop table JBPM_LOG;
drop table JBPM_MODULEDEFINITION;
drop table JBPM_MODULEINSTANCE;
drop table JBPM_NODE;
drop table JBPM_POOLEDACTOR;
drop table JBPM_PROCESSDEFINITION;
drop table JBPM_PROCESSINSTANCE;
drop table JBPM_RUNTIMEACTION;
drop table JBPM_SWIMLANE;
drop table JBPM_SWIMLANEINSTANCE;
drop table JBPM_TASK;
drop table JBPM_TASKACTORPOOL;
drop table JBPM_TASKCONTROLLER;
drop table JBPM_TASKINSTANCE;
drop table JBPM_TOKEN;
drop table JBPM_TOKENVARIABLEMAP;
drop table JBPM_TRANSITION;
drop table JBPM_VARIABLEACCESS;
drop table JBPM_VARIABLEINSTANCE;
SET FOREIGN_KEY_CHECKS=1;

Revision 3787 (Mar 1, 2007)

Incompatible change in workflow (initial value scripts), you need to drop the jBPM data.

Warning: this will remove all your workflow data, I assume nobody is using this for real yet.

delete from daisy_system where propname = 'jbpm_schema_version';

SET FOREIGN_KEY_CHECKS=0;
drop table JBPM_ACTION;
drop table JBPM_BYTEARRAY;
drop table JBPM_BYTEBLOCK;
drop table JBPM_COMMENT;
drop table JBPM_DECISIONCONDITIONS;
drop table JBPM_DELEGATION;
drop table JBPM_EVENT;
drop table JBPM_EXCEPTIONHANDLER;
drop table JBPM_ID_GROUP;
drop table JBPM_ID_MEMBERSHIP;
drop table JBPM_ID_PERMISSIONS;
drop table JBPM_ID_USER;
drop table JBPM_JOB;
drop table JBPM_LOG;
drop table JBPM_MODULEDEFINITION;
drop table JBPM_MODULEINSTANCE;
drop table JBPM_NODE;
drop table JBPM_POOLEDACTOR;
drop table JBPM_PROCESSDEFINITION;
drop table JBPM_PROCESSINSTANCE;
drop table JBPM_RUNTIMEACTION;
drop table JBPM_SWIMLANE;
drop table JBPM_SWIMLANEINSTANCE;
drop table JBPM_TASK;
drop table JBPM_TASKACTORPOOL;
drop table JBPM_TASKCONTROLLER;
drop table JBPM_TASKINSTANCE;
drop table JBPM_TOKEN;
drop table JBPM_TOKENVARIABLEMAP;
drop table JBPM_TRANSITION;
drop table JBPM_VARIABLEACCESS;
drop table JBPM_VARIABLEINSTANCE;
SET FOREIGN_KEY_CHECKS=1;

Revision 3783 (Feb 27, 2007)

A small change to the previous commit, ${siteName} becomes ${site}:

<target path="/daisy/extensions/workflow/workflow-manager">
  <configuration>
      
    [ ... ]

    <taskURL>http://localhost:8888/daisy/${site}/workflow/performTask?taskId=${taskId}</taskURL>
  </configuration>
</target>

Revision 3779 (Feb 27, 2007)

Workflow: added link to open task to the task notification mail. Therefore, add the <taskURL> element to the myconfig.xml as illustrated below.

<target path="/daisy/extensions/workflow/workflow-manager">
  <configuration>
      
    [ ... existing stuff ...]

    <taskURL>http://localhost:8888/daisy/${siteName}/workflow/performTask?taskId=${taskId}</taskURL>
  </configuration>
</target>

Revision 3778 (Feb 23, 2007)

Mail templates for workflow notification have been added. Therefore, add the <mailTemplates> element to the myconfig.xml as illustrated below. 

<target path="/daisy/extensions/workflow/workflow-manager">
  <configuration>
      
    [ ... existing stuff ...]

    <!-- Where to look for workflow mail templates -->
    <mailTemplates>
      <!-- built-in templates (loaded from the classpath) -->
      <location>resource:/org/outerj/daisy/workflow/serverimpl/mailtemplates/</location>
      <!-- custom templates in the datadir -->
      <location>${daisy.datadir}/templates/workflow/</location>
    </mailTemplates>
  </configuration>
</target>

Revision 3728 (Feb 12, 2007)

Upgrade to ActiveMQ 4.1.0. This version uses a newer version of spring-xbean for reading its xml configuration files which are in use for Daisy. This makes the reading of the configuration a little stricter which calls for a change to the activemq-conf.xml files.

In <DAISYDATA_DIR>/conf/activemq-conf.xml

The standard activemq configuration provided by Daisy starts with this

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://activemq.org/config/1.0">
  <broker useJmx="true" brokerName="DaisyJMS" useShutdownHook="false">
    <plugins>
...

The xml namespace should not be placed on the bean element but on the broker element.

<?xml version="1.0" encoding="UTF-8"?>
<beans>
  <broker useJmx="true" brokerName="DaisyJMS" useShutdownHook="false"
          xmlns="http://activemq.org/config/1.0">
    <plugins>
...

Revision 3718 (Feb 9, 2007)

Upgraded to jBPM 3.2beta2 (final 3.2 is expected soon).

The database schema changed a bit. Since no-one probably has important workflow data yet, you can simply drop the current schema as follows, and it will be reinstalled the next time the repository server is started:

delete from daisy_system where propname = 'jbpm_schema_version';

SET FOREIGN_KEY_CHECKS=0;
drop table JBPM_ACTION;
drop table JBPM_BYTEARRAY;
drop table JBPM_BYTEBLOCK;
drop table JBPM_COMMENT;
drop table JBPM_DECISIONCONDITIONS;
drop table JBPM_DELEGATION;
drop table JBPM_EVENT;
drop table JBPM_EXCEPTIONHANDLER;
drop table JBPM_ID_GROUP;
drop table JBPM_ID_MEMBERSHIP;
drop table JBPM_ID_PERMISSIONS;
drop table JBPM_ID_USER;
drop table JBPM_LOG;
drop table JBPM_MESSAGE;
drop table JBPM_MODULEDEFINITION;
drop table JBPM_MODULEINSTANCE;
drop table JBPM_NODE;
drop table JBPM_POOLEDACTOR;
drop table JBPM_PROCESSDEFINITION;
drop table JBPM_PROCESSINSTANCE;
drop table JBPM_RUNTIMEACTION;
drop table JBPM_SWIMLANE;
drop table JBPM_SWIMLANEINSTANCE;
drop table JBPM_TASK;
drop table JBPM_TASKACTORPOOL;
drop table JBPM_TASKCONTROLLER;
drop table JBPM_TASKINSTANCE;
drop table JBPM_TIMER;
drop table JBPM_TOKEN;
drop table JBPM_TOKENVARIABLEMAP;
drop table JBPM_TRANSITION;
drop table JBPM_VARIABLEACCESS;
drop table JBPM_VARIABLEINSTANCE;
SET FOREIGN_KEY_CHECKS=1;

Also reinstall sample workflows: in the Daisy Wiki in the Administration console, choose "Manage process definitions" followed by "Reinstall sample workflows".

In case you want to keep your current workflow data, see the schema upgrade statements in the file release.notes.html, part of the jBPM 3.2 download. Execute those statements and also update the jbpm_schema_version setting in the daisy_system table to "3.2".

Revision 3668 (Jan 26, 2007)

Merge of BRANCH_DEREF into trunk. See also this mail.

Database changes to be applied:

alter table document_variants
   add column link_search VARCHAR(100) not null after lang_id,
   add index (link_search)
;
show warnings;

update document_variants set link_search = concat(doc_id, '-', ns_id, '@', branch_id, ':', lang_id);
show warnings;

Revision 3607 (Jan 9, 2007)

This revision introduces a user called 'workflow'.

Edit your myconfig.xml and add the following in the configuration of the workflow-manager:

<workflowUser login="workflow" password="defaultpwd"/>

See also the example in the myconfig.xml.template if unsure.

Also, create this user in Daisy (via the wiki admin console or a script). Give the user the Administrator role as default role. For development setups, you should leave the password to 'defaultpwd' for convenience.

Note that if the workflow user does not exist, the repository server will still start up (without workflow available), so you can add this user after upgrading to this SVN version.

For automated installs, daisy-repository-init supports a new property called workflowUserPassword.

Revision 3551 (Nov 13, 2006)

Merge of BRANCH_WORKFLOW into trunk. See also this mail and this mail.

Database changes to be applied:

CREATE TABLE wfpool_sequence
(
    maxid BIGINT
) Type=InnoDB;

CREATE TABLE wf_pools
(
    id BIGINT NOT NULL,
    name_ VARCHAR (100) NOT NULL,
    description VARCHAR (255),
    last_modified DATETIME NOT NULL,
    last_modifier BIGINT NOT NULL,
    updatecount BIGINT NOT NULL,
    PRIMARY KEY(id),
    UNIQUE (name_)
) Type=InnoDB;

CREATE TABLE wf_pool_members
(
    pool_id BIGINT NOT NULL,
    user_id BIGINT NOT NULL,
    added DATETIME NOT NULL,
    adder BIGINT NOT NULL,
    PRIMARY KEY(pool_id,user_id),
    FOREIGN KEY (pool_id) REFERENCES wf_pools (id),
    INDEX wf_pool_members_I_1 (user_id)
) Type=InnoDB;

Add the following to the myconfig.xml:

  <target path="/daisy/extensions/workflow/workflow-manager">
    <configuration>
      <jbpm>
        <hibernate>
          <properties>
            <entry key="hibernate.dialect">org.hibernate.dialect.MySQLInnoDBDialect</entry>
          </properties>
        </hibernate>
      </jbpm>
    </configuration>
  </target>

In <wiki data dir>/daisy.xconf, inside the <extensions> element, add the following tag:

<extension name="WorkflowManager"
           class="org.outerj.daisy.workflow.clientimpl.RemoteWorkflowManagerProvider"/>
Comments (0)
Advertisement

Daisy hosting, installation, support. Workshops and turnkey Daisy CMS projects. Get Daisy from its creators.

outerthought.org

Downloads provided by

SourceForge.net Logo

Open source stats