Author: vanto
Date: Mon Dec 10 21:26:49 2012
New Revision: 1419786
URL: http://svn.apache.org/viewvc?rev=1419786&view=rev
Log:
fix formatting.
Modified:
ode/site/trunk/content/upgrading-ode.mdtext
Modified: ode/site/trunk/content/upgrading-ode.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/upgrading-ode.mdtext?rev=1419786&r1=1419785&r2=1419786&view=diff
==============================================================================
--- ode/site/trunk/content/upgrading-ode.mdtext (original)
+++ ode/site/trunk/content/upgrading-ode.mdtext Mon Dec 10 21:26:49 2012
@@ -1,23 +1,24 @@
Title: Upgrading ODE
-<div class="alert alert-note"><h4 class="alert-heading">You shall backup</h4>
- ODE upgrade procedures usually consist in:
- # backing up your database
- # checking your backup
- # double-checking your backup
- # running the required SQL upgrade script
- # deploying your new ODE war.
- # copying all the previous configuration and deployed processes (with the
corresponding markers).
-
- h2. From 1.3.3 to 1.3.4
-
- First, apply SQLs to denormalize LARGE_DATA table from here:
[https://issues.apache.org/jira/browse/ODE-694]
-
- Then, please apply following updates:
-
-
- {code}
+<div class="alert alert-note"><h4 class="alert-heading">You shall
backup</h4></div>
+
+ODE upgrade procedures usually consist in:
+
+* backing up your database
+* checking your backup
+* double-checking your backup
+* running the required SQL upgrade script
+* deploying your new ODE war.
+* copying all the previous configuration and deployed processes (with the
corresponding markers).
+
+## From 1.3.3 to 1.3.4
+
+First, apply SQLs to denormalize LARGE_DATA table from here:
[https://issues.apache.org/jira/browse/ODE-694]
+
+Then, please apply following updates:
+
+ :::sql
alter table BPEL_XML_DATA add SIMPLE_VALUE varchar2(255);
-
+
create table ODE_JOB_BAK as select * from ODE_JOB;
alter table ODE_JOB add instanceId number(37);
alter table ODE_JOB add mexId varchar(255);
@@ -32,52 +33,47 @@ Title: Upgrading ODE
alter table ODE_JOB add detailsExt blob;
update ODE_JOB oj set detailsExt = (select details from ODE_JOB where
jobid = oj.jobid);
alter table ODE_JOB drop column details;
-
- {code}
-
- h2. From 1.3.2 to 1.3.3
-
- None
-
-
- h2. From 1.2 to 1.3.2
-
- If you're currently using ODE *1.2* and are upgrading to 1.3.2, please run
the following queries.
-
- h3. For OpenJPA database schema
- {code:sql}
+
+## From 1.3.2 to 1.3.3
+
+None
+
+
+## From 1.2 to 1.3.2
+
+If you're currently using ODE *1.2* and are upgrading to 1.3.2, please run the
following queries.
+
+### For OpenJPA database schema
+
+ :::sql
create table ODE_SCHEMA_VERSION (VERSION integer);
insert into ODE_SCHEMA_VERSION values (5);
-
+
alter table ODE_MESSAGE_EXCHANGE add column (SUBSCRIBER_COUNT integer);
alter table ODE_MESSAGE_ROUTE add column (ROUTE_POLICY character
varying(255));
- {code}
-
- h3. For Hibernate database schema
-
- (Mind the table names)
-
- {code:sql}
+
+### For Hibernate database schema
+
+(Mind the table names)
+
+ :::sql
create table ODE_SCHEMA_VERSION(VERSION integer);
insert into ODE_SCHEMA_VERSION values (5);
-
+
alter table BPEL_MESSAGE_EXCHANGE add column (SUBSCRIBER_COUNT integer);
alter table BPEL_SELECTORS add column (ROUTE_POLICY character
varying(255));
- {code}
-
-
- h2. from 1.1 to 1.2
-
- The upgrade path from 1.1 to 1.2 is relatively simple as there haven't any
major change in the database or runtime models. Still, if you use the Hibernate
database schema, one column has been added so you will need to execute the
following upgrade script (make sure to *backup before* to prevent any data
loss):
-
- {code:sql}
+
+## From 1.1 to 1.2
+
+The upgrade path from 1.1 to 1.2 is relatively simple as there haven't any
major change in the database or runtime models. Still, if you use the Hibernate
database schema, one column has been added so you will need to execute the
following upgrade script (make sure to *backup before* to prevent any data
loss):
+
+ :::sql
alter table BPEL_SELECTORS add column (PROC_TYPE varchar(255));
update BPEL_PROCESS p, BPEL_CORRELATOR c, BPEL_SELECTORS s set s.PROC_TYPE
= ('{' + p.type_ns + '}' + p.type_name) where s.CORRELATOR = c.CID and
c.PROCESS_ID = p.PROCID;
- {code}
-
- The update statement is only necessary if you have currently running
instances. Note that if you're using the default OpenJPA database schema, no
database modifications are necessary. Once this is done, it's fairly simple:
-
- * Redeploy your new ODE 1.2 WAR.
- * Copy all the previous configuration and deployed processes (with the
corresponding markers).
-
- That's it\!
+
+The update statement is only necessary if you have currently running
instances. Note that if you're using the default OpenJPA database schema, no
database modifications are necessary. Once this is done, it's fairly simple:
+
+* Redeploy your new ODE 1.2 WAR.
+* Copy all the previous configuration and deployed processes (with the
corresponding markers).
+
+That's it\!
