View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

ERP 2.50:Upgraders Testing

Contents

Introduction

This document explains the procedure for testing an Openbravo ERP upgrade from a 2.40 release to a 2.50 release and from a 2.50 release to another 2.50 release. (there is a document that explains how-to upgrade from previous releases).

Compatibility

This test should be repeated on the four supported environments:

Note:PostgreSQL 8.2 is not supported since 2.50

Upgrading a customized 2.40 release

Step 1 - Installing

The first step is to install the Openbravo ERP starting release. You may choose among published releases (i.e. Installers) or public branches (i.e. svn checkouts).

Installation instructions are provided at ERP/2.40/Openbravo_ERP_installation.

Step 2 - Customizing

Note: You can bypass this step if you have an already customized dmp file

Running scripts

Create the tables used for customizing with this Oracle script or this PostgreSQL script. Remember to replace tad with your db username if you changed the default.

Then create customized functions IMP_VENTAS and IMP_VENTAS_TOTAL running the script for Oracle or for PostgreSQL.

Setting up Openbravo ERP

Follow this steps:

Note:As an additional test, you may try to add a new PL and/or modifying an existent function

    [java] 507  [main] ERROR org.openbravo.data.Sqlc - SQL error in query: 
    [java]         SELECT C_Roomattend.AD_Client_ID, 
    [java] (CASE WHEN C_Roomattend.AD_Client_ID IS NULL THEN ' ' ELSE  (COALESCE(TO_CHAR(table1.Name),' ') ) END) AS AD_Client_IDR, 
    [java] C_Roomattend.AD_Org_ID, 
    [java] (CASE WHEN C_Roomattend.AD_Org_ID IS NULL THEN ' ' ELSE  (COALESCE(TO_CHAR(table2.Name),' ') ) END) AS AD_Org_IDR, 
    [java] C_Roomattend.Typeattender, 
    [java] (CASE WHEN C_Roomattend.Typeattender IS NULL THEN ' ' ELSE  ( COALESCE(TO_CHAR(list1.name), ' ') ) END) AS TypeattenderR, 
    [java] C_Roomattend.Department, 
    [java] (CASE WHEN C_Roomattend.Department IS NULL THEN ' ' ELSE  ( COALESCE(TO_CHAR(list2.name), ' ') ) END) AS DepartmentR, 
    [java] C_Roomattend.C_Bpartner_ID, 
    [java] (CASE WHEN C_Roomattend.C_Bpartner_ID IS NULL THEN ' ' ELSE  (COALESCE(TO_CHAR(table3.Name),' ') ) END) AS C_Bpartner_IDR, 
    [java] C_Roomattend.Meetingrole, 
    [java] C_Roomattend.C_Roomschedule_ID, 
    [java] (CASE WHEN C_Roomattend.C_Roomschedule_ID IS NULL THEN ' ' ELSE  () END) AS C_Roomschedule_IDR, 

the problem is that you do not marked one column as Identifier for C_Roomattend table.

Adding custom code

Copy this code on your AppsOpenbravo/srcClient/org/openbravo/erpCommon/ad_reports folder.

Step 3 - Running the upgrader

Last step is to run the upgrader. You can take a look at ERP/2.50/Upgrading_From_2.40.

Before running the upgrader, please verify:

Rollbacking

In the case of a failure during the process, it is often needed to restart the upgrader again. It is not necessary to start from step 1.

For rolling back:

drop user TAD cascade; 

After this, the testing can skip Step 1 and Step 2 and start on Step 3.

Issues to verify

Verify Database XML files

This test will verify that migrated database XML files match with the same XML files on a fresh new installation.

See also File Distribution

Steps
Expected differences

The model and sourcedata folders are supposed to be identical.

Additional verification

Is a good practice, specially when differences were found, to also compare XML files backed up prior exporting with the new installation XMLs. That will add info to developers about what upgrading step has the error.

Run an acceptance test and verify bugs

Upgrading a customized 2.50 release

Step 1 - Installing

The first step is to install the Openbravo ERP starting release. You may choose among published releases (i.e. Virtual Appliance) or public branches (i.e. svn checkouts). Installation instructions are provided at ERP/2.50/Openbravo_ERP_Installation

Step 2 - Customizing

You have the Rooms module and several localization packs to choose. No need to manually modifications.

Step 3 - Running the upgrader

Upgrading is like installing a module. The module in this case is an .obx file of new 2.50 release. In some cases the new release can be found as a module in the Central Repository

Rollbacking

In the case of a failure during the process, you can restore the application from the zip file generated during step 3.

Issues to verify

Run an acceptance test and verify bugs

Retrieved from "http://wiki.openbravo.com/wiki/ERP_2.50:Upgraders_Testing"

This page has been accessed 3,313 times. This page was last modified on 4 April 2012, at 13:53. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.