6 Replies Latest reply on Jul 22, 2008 4:54 AM by Joram Barrez

    Schema for the current BI implementation?

    Heiko Braun Master

      Does someone know what the schema (DB) for the current BI impl. looks like? Where can I find it?

        • 1. Re: Schema for the current BI implementation?
          Ronald van Kuijk Master

          Heiko,

          afaik, there was no DB backend for the BI impl. They were just reports generated based on the current data. So in fact it was more of a half BI, half BAM implementation.

          • 2. Re: Schema for the current BI implementation?
            Tom Baeyens Master

             

            create table JBPM_LOG (
             ID_ bigint generated by default as identity (start with 1),
             CLASS_ char(1) not null,
             INDEX_ integer,
             DATE_ timestamp,
             TOKEN_ bigint,
             PARENT_ bigint,
             MESSAGE_ varchar(4000),
             EXCEPTION_ varchar(4000),
             ACTION_ bigint,
             NODE_ bigint,
             ENTER_ timestamp,
             LEAVE_ timestamp,
             DURATION_ bigint,
             NEWLONGVALUE_ bigint,
             TRANSITION_ bigint,
             CHILD_ bigint,
             SOURCENODE_ bigint,
             DESTINATIONNODE_ bigint,
             VARIABLEINSTANCE_ bigint,
             OLDBYTEARRAY_ bigint,
             NEWBYTEARRAY_ bigint,
             OLDDATEVALUE_ timestamp,
             NEWDATEVALUE_ timestamp,
             OLDDOUBLEVALUE_ double,
             NEWDOUBLEVALUE_ double,
             OLDLONGIDCLASS_ varchar(255),
             OLDLONGIDVALUE_ bigint,
             NEWLONGIDCLASS_ varchar(255),
             NEWLONGIDVALUE_ bigint,
             OLDSTRINGIDCLASS_ varchar(255),
             OLDSTRINGIDVALUE_ varchar(255),
             NEWSTRINGIDCLASS_ varchar(255),
             NEWSTRINGIDVALUE_ varchar(255),
             OLDLONGVALUE_ bigint,
             OLDSTRINGVALUE_ varchar(4000),
             NEWSTRINGVALUE_ varchar(4000),
             TASKINSTANCE_ bigint,
             TASKACTORID_ varchar(255),
             TASKOLDACTORID_ varchar(255),
             SWIMLANEINSTANCE_ bigint,
             primary key (ID_)
            )
            


            • 4. Re: Schema for the current BI implementation?
              Heiko Braun Master

              What's all this?

              OLDBYTEARRAY_ bigint,
               NEWBYTEARRAY_ bigint,
               OLDDATEVALUE_ timestamp,
               NEWDATEVALUE_ timestamp,
               OLDDOUBLEVALUE_ double,
               NEWDOUBLEVALUE_ double,
               OLDLONGIDCLASS_ varchar(255),
               OLDLONGIDVALUE_ bigint,
               NEWLONGIDCLASS_ varchar(255),
               NEWLONGIDVALUE_ bigint,
               OLDSTRINGIDCLASS_ varchar(255),
               OLDSTRINGIDVALUE_ varchar(255),
               NEWSTRINGIDCLASS_ varchar(255),
               NEWSTRINGIDVALUE_ varchar(255),
               OLDLONGVALUE_ bigint,
               OLDSTRINGVALUE_ varchar(4000),
               NEWSTRINGVALUE_ varchar(4000),
              


              • 5. Re: Schema for the current BI implementation?
                Joram Barrez Master

                Heiko:

                The schema Tom posted is the table to which currently all 'process events' are persisted.

                The 'oldvalue - newvalue' columns represent process variable changes. So if a var value changes, the change is reflected in the JBPM_LOG table (do note that jBPM logging can be set off by configuration)

                • 6. Re: Schema for the current BI implementation?
                  Joram Barrez Master

                  And with 'process events' I don't mean the process event implementations (eg node_enter etc), but everything that happens that is related with a process.