Support > Installation Guide (R7) > Upgrade Wagby

I will explain the procedure when upgrading Wagby R7. Here, we call the currently running Web application "current system". The newly built web application is called "new system".

When upgrading Wagby version, please follow the following procedure.(If you rebuild using the same version of Wagby, skip this step and proceed to the next section.)

1. Back up the repository

We will back up the repository of the current system.It becomes a zip file starting with wrb_.Download this and keep it in any work folder.

2. Stopping the current system

Stop the current version of Wagby Designer and the applications that you built.

3. Installing a new Wagby

Multiple versions of Wagby can be installed on one development machine.Change the folder name and install it.(Eg Wagby-7.0.0 and Wagby-7.5.0)

If you purchase, after installationPlease apply license key of developer kit.You can apply the same license key to multiple versions of Wagby.

4. Restore (Restore Repository)

Launch the new version of Wagby Desinger.Load the repository obtained in step 1.

After loading, restore it with the "Restore" button.

Please note: You can not copy (or move) the old repository folder directly to the repository folder of the new version.Be sure to create a backup file that begins with wrb_ and restore it with the above restore processing.

5. The customize folder

Copy the contents of the customize folder created in the previous version directly into the customize folder of the new version.

When using an external database, the JDBC driver file is saved in the customize folder.Please remember to copy this to the new version as well.
As the version is upgraded, it may be necessary to modify the customization code.For details, please read the update history of each version.)

6. Full Build

Launch the new version of WagbyDesigner.Please clear the cache of the browser, log on to WagbyDesigner, and perform a full build.

We call the completed application "new system".In the next section, we will explain the replacement procedure.

The procedure for replacing the current system with the new system on the production server will be explained.The new system shall be generated by full build.The concrete replacement procedure is as follows.

  1. Stop the current system.
  2. Export all data contained in the current system.
  3. Change the folder name of the current system.(Example: wagbyapp is wagbyapp.old)
  4. Copy the new system to the server.
  5. To the new system, import the data exported in 2.
  6. Copy the settings of the current system to the new system.
  7. Copy the license key of the current system to the new system.
  8. Start up the new system.
  9. Confirm the connection to the new system.

The details are explained below.

1. Stop the current system

If you are registering to Windows service, please stop from Windows [Administrative Tools] and delete the service. If you are not registered to Windows service please execute wagbyapp \ bin \ shutdown.bat.

2. Export all data contained in the current system

If even one of the following cases applies, please follow this procedure.[More ...]

  • We upgraded Wagby.
  • Modification of model definition (addition/deletion of model or addition/deletion of model item) occurred.
  • I changed the data authority setting.
  • I use an internal database.
You can skip this procedure if you are using an external database and you have no model definition changes and you are using the same version of Wagby.

Please export by command line operation.

  1. Open a command prompt.
  2. Move to the bin folder included in the wagbyapp folder."cd C:\Wagby-7.12.1\wagbyapp\bin"
  3. Execute export_db.bat.Specify the output destination folder as an argument.Folder name is prefixed with "data_" and information of year, month, day, hour, minute and second continues."export_db.bat .. \ .. \ export \ data_20170301090000" This is a way to make it distinguishable when there are multiple data_folders.Actually, the character strings below data_ can be specified arbitrarily with half-width alphanumeric characters.
  4. If you are using an external database, use the drop_db.bat command to delete the table.(After replacing, it is to create a new table.)
  5. Exit the command prompt.

3. Change the folder name of the current system

Please change the folder name "wagbyapp" of current system to "wagbyapp.old". If "wagbyapp.old" already exists, please use a folder name which does not overlap like "wagbyapp.old20170301".

The reason not to delete the folder of the current system here is to make it possible to return to the old system promptly if there is a problem with the new system by any chance.

4. Copy the new system to the production server

Copy the new system you build to the server machine.Please make it the same folder name as the old system.This allows you to take over and use the same environment even if you are working with Apache or IIS.

5. Import data to the new system

If you performed "2. Export all data included in the current system", please follow the procedure below.

  1. Open a command prompt.
  2. Move to the bin folder included in the wagbyapp folder."cd C:\Wagby-7.12.1\wagbyapp\bin"
  3. Run import_db.bat.In the argument, specify the folder name (where the data you want to import is stored)."import_db.bat ..\..\export\data_20170301090000"
  4. Exit the command prompt.

6. Handling file type items

The file uploaded to the "File type" item is saved under the upload_dir folder of the current system.Move (or copy) the same folder to the new system.

7. Applying license key

In case of project license

Please copy "license key file" of the current system to the new system.The license key file is appschema - licensekey.xml in wagbyapp \ webapps \ $ (APPNAME) \ WEB - INF \ classes.

This is the case when using the same server.If you change the server machine, the license key will be newly acquired.

Unlimited development license

This step is unnecessary.Proceed to the next.

8. Start up the new system

To start up as a Windows service, register Windows service and start from Windows management tool.

Otherwise please run wagbyapp \ bin \ startup.bat.

9. Confirm connection

Enter the given address from the web browser.Log on with a specific account and confirm that the menu is displayed.

If logon processing fails, the database connection may have failed.Once you stop the new system, open the system.log in the wagbyapp/logs folder and check whether an error message is included.

Changing the following design information may affect the table definition.

  • Setting of group authority management.
  • Setting to update reference linkage item.
  • need to check.
  • Set the type of input item to text area.
  • Setting of unique constraint check.

If you change these settings (including canceling the settings), the table definition will be changed.In this case, you need to export and import the data.

Learn more

Please check whether there is a difference between wagbyapp \ webapps \ $ (APPNAME) \ WEB-INF \ export \ conf \ createddl of the current production environment and the file in the same folder of wagbyapp after building with version upgrade .If there is no difference, you can use the table as it is.

In version upgrade, there may be a change in the table of the system that is included in Wagby itself.In this case, it is a good idea to export the data only for this table, recreate the table (drop and create) and then import the data.

Import and export only the changed table

Export_db.bat and import_db.bat cover all tables.The entity of these commands is called InitLoader.jar.By directly manipulating InitLoader.jar, you can perform limited operations on the table.

When adding a new model, the idea of ​​data restoration is as follows.

It does not include option model

For the new system, restore (export) the data exported in the current system.An import model table is also prepared by the import command.

It means that the create table statement corresponding to the new system is executed.This includes models that you added.

Includes option model

  1. For the new system, restore (import) the data that was exported in the current system.
  2. Start the new system and log on with the system administrator (admin).
  3. Open the import export screen of management process.
  4. Let the import folder name be "data_init"Specify the added option model with a check box and import it.

In 1.,The data restored from the current system does not include the initial value of the added choice model.Therefore, for additional parts, specify the initial data (data_init) folder and import individually.A table is also created at this timing.

In the above explanation, model designation by screen operation was done, but command line operation is also possible.You can specify the table individually with the import command of InitLoader.jar.