The Nexacro Platform execution environment must be installed on users' Windows PCs prior to downloading and running applications that use it.
The Nexacro Platform execution environment can be downloaded through HTTP or offline, using a manual procedure.
Phases of Distribution
Distribution of the Runtime version covers up to a call for the first HTML file after the engine distribution. Nexacro Platform application users should abide by the process order for HTML files and JavaScript files described herein.
Nexacro Platform Engine Distribution
This installs the Nexacro Platform engine, which manages all stages of distribution.
Install the engine by downloading it from the web or by receiving an execution file ".exe". If you download the file from a web browser, use the CAB file provided by our company.
Integrated Framework and Component Library Distribution
A framework will be distributed as a resource file to the Framework DLL file distributed with the engine.
Application Distribution
Applications developed by developers will be distributed. Component modules are distributed as well.
Application distribution uses networks efficiently through the "Intelligent Cache" technique.
Distribution Flow
Most of the distribution process is performed by the Nexacro Platform Engine. The Nexacro Platform Engine is usually installed on the user device as a CAB file through a web browser. However, if the CAB process fails, separate exe files are provided.
Cabinet files as well as the classid, and CodeBase attributes—which are presented in this chapter—can vary according to product versions or license policies of relevant countries. Therefore, please check the nexacro14_VersionInfo_XXX.txt file that is bundled in the product package.
Phase 1 : Nexacro Platform Engine Setup
From the Web browser, the Nexacro Platform Engine is installed using the CAB file (nexacro14_SetupEngine_N.cab). However, this method requires the insertion of the following coding.
<HTML> <HEAD> <TITLE> Plugin sample page </TITLE> <BODY> <object id="NexacroAXCtrl" classid="clsid:3CF3951B-34BD-4E22-933B-AE2BE0FA8941" CodeBase="./nexacro14_SetupEngine_N.cab#VERSION=2014,7,11,2"> </object> </BODY> </HTML>
The version number corresponds to the module version being set up. Refer to the VersionInfo file distributed with the product.
Phase 2 : Setting Nexacro Platform Application Program Execute Environment
To run an application program, you need the ADL file which has the environment information of application program. This is because the nexacro platform Engine downloads and analyzes the ADL file for application program distribution and composition.
The ADL (Application Definition Language) file defines the elements needed to configure application programs. It is saved with the xadl extension and includes the information about the TypeDefinition and GlobalVariable as a JavaScript file when distributed.
The ADL also defines other elements such as the basic screen arrangement, component and object composition and theme composition.
Phase 3 : Application Program Execution
After configuring the application program according to the ADL file, the Nexacro Platform Engine downloads and outputs the UI screen.
An FDL file (Form Definition Language) with an xfdl extension is saved and provided as a JavaScript file during distribution. It contains the UI information and the logic information to be processed within a screen.
Setup Files
Various files needed for the Nexacro Platform distribution are also included in the setup files, such as modules, licenses and functions.
Modules
The following are the main modules included in the nexacro platform setup file.
Module Setup File | Modules |
---|---|
nexacro14_SetupDeveloper_N.exe | • Nexacro Platform Engine (nexacro.exe + library dll) • nexacro14lib (JavaScript) • Nexacro Studio |
nexacro14_SetupEngine_N.exe nexacro14_SetupEngine_N.cab | • Nexacro Platform Engine • nexacroax14.dll • nexacrolauncherax14.dll |
nexacro14_Launcher_N.cab | • nexacrolauncherax14.dll |
License files
Following are the types of license files.
License file | Description |
---|---|
nexacro14_server_license.xml | Provides file in XML format In the same place as X-API jar file or in classes folder Checked when X-API, HTML5 is running |
nexacro14_client_license.xml | Provided as a file in XML format Placed in route approachable by web Sets relevant file route and file name in license URL of ADL Checked when runtime and widget is running |
Tool License | Provided as a file in Product Key format Help of Nexacro Studio – Registered in about Nexacro Studio. |
Functions of Main Modules
The following are the main functions of the distributed modules.
Module Name | Main Function |
---|---|
nexacrolauncherax | Downloads icon image Creates shortcuts Drives Nexacro Platform Engine |
nexacroax | Drives Nexacro Platform Engine on web browser |
Types of Nexacro Platform Distributions
The distribution of the Nexacro Platform differs according to in what form Nexacro Platform Runtime is executed.
Runtime Execution Form
The Runtime Execution is separated into two forms according to how the core part of Nexacro Platform Runtime, the engine, is run. These are “Execution Version Execution” and “Web Browser Plugin Version Execution”.
These execution forms are further differentiated based on how the distribution is performed.
- Execution Version Execution
The Nexacro Platform is run as another window by launcher and exe file.
- Web Browser Plug-in Version Execution
The Nexacro Platform runtime is run as an embedded form on the web browser.
Distribution by Web Browser Plug-in is processed independently. This could provide unpredictable results.
If you want to use a web browser for the execution, consider using Nexacro Platform HTML5 version.
Types of Basic Distribution
Distribution of Nexacro Platform can be divided into three distribution types, depending on the Nexacro Platform execution form:
Plugin distribution
Launcher distribution
exe distribution
These are compared in the following chart.
Type Category | Web Browser Plugin Distribution | Launcher Distribution | exe Distribution |
---|---|---|---|
Running window | Web Browser | Nexacro Platform Runtime | Nexacro Platform Runtime |
Setup file | nexacro14_SetupEngine_N.cab | nexacro14_SetupEngine_N.cab | nexacro14_SetupEngine_N.exe |
nexacro14_SetupEngine_N.exe nexacro14_Launcher_N.cab | |||
Engine execution | Nexacro Platform ActiveX execution | nexacrolauncherax execution | nexacro.exe execution |
Usage of shortcut | None | Create shortcut | Use shortcut |
To use shortcuts, create the shortcuts using Launcher, and execute them by clicking on the corresponding icon using exe execution.
Version Administration
Most distributions are directed by the Nexacro Platform Engine. However, because the engine is usually distributed through web browser, how are upgrades distributed? The Nexacro Platform engine upgrades by itself.
Engine Upgrade Information Registration
The ADL files have the upgrade information about the engine, as illustrated in the following figure of the ADL property screen in Nexacro Studio.
The following table lists the property details.
Property Name | Description |
---|---|
enginesetupkey | Product key of the setup file When using Nexacro Platform Engine, you do not need to enter any value. However, when the developer is writing a separate setup file, the product key of the particular setup file is entered here. |
engineurl | Path to the server URL with an existing setup file |
engineversion | Version of the setup file |
licenseurl | Designates the path to the license file |
The following HTML code shows the relationship between the value used in the HTML file when the engine was installed and the ADL property value.
<HTML> <HEAD> <TITLE>Plugin sample page </TITLE> <BODY> <object id="NexacroAXCtrl" classid="clsid:3CF3951B-34BD-4E22-933B-AE2BE0FA8941" CodeBase="./nexacro14_SetupEngine_N.cab# ← engineurl VERSION="2014,7,11,2"> ← engineversion </object> </BODY> </HTML>
Executing Nexacro Platform Engine Upgrade
After inputting the ADL property value with Nexacro Studio and uploading the ADL file to the distribution server, the Nexacro Platform Engine will automatically upgrade after comparing the engine URL and engine version value in this ADL file with the Nexacro Platform engine that is already installed.
The version of the already installed engine can be checked in Settings/Add or remove program.
When upgrading Nexacro Platform engine, the Nexacro Platform Engine will be rerun.