Tasks to be Performed before the App Builder Installation

These are required tasks before installing the App Builder to the server. Common tasks and additional tasks for installing the App Builder are required, depending on the deployment target.

App Builder Installation Common

Install Tomcat (WAS) after installing JDK.

In this document, JDK 11, Tomcat version 9 was used.

Android

Install Android SDK. You can run the SDK Manager after installing the Android Studio or download the command-line tool to install the SDK.

In this document, Android 13(API 33) was used.

iOS, macOS

Install the required SDK after installing Xcode. Since Xcode cannot be installed on any other operating system besides macOS, you need a device that can run macOS.

In this document, Xcode(Build 15C500b), iOS SDK(17.2), OS X SDK(14.2) was used.

App Builder Installation

App Builder is provided as the WAR (Web application ARchive) file. Deploy the provided WAR file (appbuilder.war) according to each WAS environment.

In this document, Tomcat version 9 was used. The explanation is based on the corresponding version.

Deploy the WAR file

Copy the appbuilder.war file to the [webapps] folder and start the Tomcat server. Check that the appbuilder folder is created in the webapps path and stop the Tomcat server.

Configure the management console

Open the environment.xml.js file in the [webapps\appbuilder\nexacro_ui] folder with the text editor and edit the part marked as "HOST:PORT" with the URL to be used.

nexacro._addService("svcUrl", "JSP", "http://HOST:PORT/appbuilder", "none", null, "", "0", "0");
nexacro._addService("svcUrl", "JSP", "http://127.0.0.1:8080/appbuilder", "none", null, "", "0", "0");

Start H2 Database

Run the runH2DB batch file from the [webapps/appbuilder/WEB-INF/package/h2/bin] folder to start the H2 Database and display the administrative console. Do not use the management console window. Close the open web browser window.

In the case of using the Windows operating system, creating the required files in the corresponding folder when first starting the H2 Database may cause an error if you do not have administrative privileges, depending on the Tomcat installation path. In the case of errors, you must run the batch file with administrative privileges enabled.

Set encoding

Korean may not be displayed properly in some environments. In that case, add an encoding setting. Open the catalina.bat file under the [bin] folder and modify it as follows.

set "JAVA_OPTS=%JAVA_OPTS% %LOGGING_CONFIG% -Dfile.encoding=UTF8"

Depending on the Tomcat version, the catalina.bat file may not be used. In that case, run Tomcat7w.exe, the executable file, under the [bin] folder and a window for setting Tomcat properties will appear. Add the "-Dfile.encoding=UTF8" item to the [Java > Java Options] item in the window.

Start the server

Delete the appbuilder.war file copied to the [webapps] folder and restart the Tomcat server.

Access the management console

Open the web browser and enter the URL below to check if you can access the management console. The URL to enter is the modified URL in the pbuilder_ui.xadl.js file.

http://xxx.xxx.xxx.xxx:8080/appbuilder