I summarize frequently asked questions and answers about Wagby R7.
Depending on the network environment, even if the extension ".exe" version is downloaded, it may be replaced with ".zip".In that case please manually change the extension to ".exe" and install.
The downloaded file may be damaged.Delete the browser's temporary file and cookies, then download again.
Could not contact localhost:8919. Tomcat may not be running.Some virus checking software and others use Tomcat.Please disable the virus check software and try it.
It may be improved by rebooting the PC.
Please pause these software, restart the PC, please try.If it is improved, please consider changing the use software to another one.
Please try the following procedure when using Windows OS.
cd Desktop\Wagby-7.x.x\wagbydesigner\binYou can move (Karen and folder) by typing.Please enter the version number of installed Wagby in "xx" part.
catalina.bat runNormally, a separate window starts up, and Tomcat starts to run.However, in case of an error, some message may be displayed here.Please send this screen capture when using technical support.
Please check whether the following message is included in the startup screen of the built application.
Context startup failed due to previous error
When this message is displayed, application startup has failed.Please check the following points.
Please clear your Google Chrome cache and reload it.[About clearing the cache ...]
Operation may become unstable due to the influence of anti-virus software.Please invalidate antivirus software once and check whether it works or not.
Or specify the folder where Wagby was installed as "Excluded files (folder)" with antivirus software.If you can also specify "Exclude process", please exclude "java".
It may occur when you manipulate the repository folder directly without using Designer.
When copying and pasting directly the folder containing the information of the item a 1 of the model A (the folder in which the item information is stored in the repository folder) and copying it to the folder of the model B, the model item There was a report that it became impossible to add it.
In Designer, internal number change processing is carried out when adding, deleting and moving items.Internal processing has occurred because the processing was not done.
[Correspondence] Migration toolMigrating the repository with.In the case of migration between versions, please install another Wagby by changing the installation folder name.
The following error message may be displayed on the console during the build process such as generation/compilation of the source code and table creation of the database.
System resources are insufficient. Please investigate in the next stack trace for details. java.lang.OutOfMemoryError: GC overhead limit exceeded
Memory is insufficient in WagbyDesigner's build process."Repository> Tuning>Adjust memory size at build timePlease read.
Virus check software may be affected.
When ESET Smart Security was running on a development machine running Wagby Designer, there was a report that reading of the repository fails due to the HTTP scanner function of the software.
[Correspondence] Trouble was avoided by turning off this function in "Advanced setting> HTTP scanner setting" of ESET Smart Security or specifying the subnet of LAN by "protocol filtering".
The following messages may be left in the error log.
Java.lang.IllegalStateException: Failed to initialize the repository folder.
1. An error message is recorded in the Tomcat console running WagbyDesigner or logs / catalina.out.First of all, please check this content.
2. The initial repository file repository / branches / wrb_20140115_0000001.zip may not exist.Or you can not read files.The problem of file access rights is also considered.
3. Are you using the old repository file wrb_20140115_0000001.zip included in the repository / branches folder?This file differs depending on the version of Wagby installed.Be sure to use the files included during installation.
Copying the repository file (repository / trunk) you used so far to the new Wagby repository folder in the Wagby version upgrade etc.can not.
"Repository> Designer function · Other tools> Repository backup and restoreFollow the procedure of "Please do as follows.
Please check the wagbydesiger / logs / system.log file.It may be understood from an error message.
If you change the license key from project license to unlimited development license, you need to convert the repository you have been using for unlimited development license.For details, please contact Wagby Reseller.
Unlimited development license and project license can not be used together.
License keys for different PCs are used.Please copy the correct license key.
This repository can not be loaded on your PC.Since it is necessary to convert the repository, please contact Wagby sales partner.
When using the trial kit (free evaluation license), the following message may be displayed.
In the trial kit, the size of the application that can be built (the total number of model items) is restricted.Please do the following correspondence.
Wagby The license key (wagby-licensekey.xml) obtained from the reseller is placed directly under the folder where you installed Wagbyoverwrite saveTo do.
In Designer, "Model information could not be loaded due to licensing problem.If you see the message "Please confirm the following points."
Wagby The license key (wagby-licensekey.xml) obtained from the reseller is placed directly under the folder where you installed Wagbyoverwrite savePlease check whether it is.
There was a report that the message "org.apache.jasper.JasperException: Can not compile class of JSP" appears in the log of running Web application.
[Correspondence] Real time scanning of virus check software was a problem.It was solved by stopping the same function.
If it runs in the development environment but an error occurs in the production environment, please check the following.
The folder to run startup.bat (or startup.sh) must be wagbyapp/bin.
When using Unix OS such as Linux, Mac OS / X etc, please confirm the following points.
Make sure startup.sh and shutdown.sh have execute permission.Execution right can be granted using the chmod command.
chmod u+x *.sh
Wagby assumes that it starts from the "bin" folder as the starting point.
To start WagbyDesigner, please move to wagbydesigner / bin folder and run startup.sh.
Likewise, please also run startup.sh after moving the build application (described later) to the wagbyapp / bin folder.
After running startup.sh, you can check the log at the console with the following command.(The following example shows this command in the wagbydesigner or wagbyapp folder.)
tail -f logs/system.log
If build time is slow, please check the following points.
It is recommended to use 64bit OS and 64bit Java.
Even when using 64 bit OS, the build time will be slow if there are few actual installed memory.It is recommended to install 4 Gbyte or more memory on the development machine.
By excluding the Wagby R7 installation folder from "checked" into the virus check software, the build speeds up.
By using SSD instead of HDD, build time can be further increased.
If the message in Figure 6 is displayed, initialize the table first after logging on to the Web application.
After logging on to the Web application, a warning about the number of data items may be displayed as shown in Fig. 7.In this case as well, please initialize the table.
In Figure 8, select "Import and Export" from the management processing menu.
Select the data for importing data_init for initialization and execute the import process with all models as import target.Please keep checking "Initialize table".This recreates the table and initializes the data.
If the import succeeds successfully, a message like the one shown in Figure 9 will be displayed.This completes initialization.
When Wagby is upgraded, older files are loaded in the user's Web browser, and screen display may not be performed correctly.Please clear the "cache" of the web browser by the following procedure.
Please use Google Chrome for Wagby Designer.