Alias Path
Nexacro Platform uses the following alias paths for setting paths on the user PC.
Alias Path Name | Actual Path Name |
---|---|
%nexacro% | %PROGRAMFILES%\nexacro\14 |
%USERAPP% | %LOCALAPPDATA%LOW\nexacro\14 \data\data\[packageName]\files\nexacro\ (Android) \Library\Caches\nexacro\ (iOS) |
%UPDATE% | %USERAPP%\Update |
%CACHE% | %USERAPP%\Cache |
%WEBDEPLOY SETUP% | Server Context root |
%WEBDEPLOY PROJECT% | Server Context root |
%WEBDEPLOY FRAMEWORK% | %WEBDEPLOY PROJECT%\nexacro14lib\framework |
%WEBDEPLOY COMPONENT% | %WEBDEPLOY PROJECT%\nexacro14lib\component |
%WEBDEPLOY RESOURCE% | %WEBDEPLOY PROJECT%\nexacro14lib\resources |
%WEBDEPLOY THEME% | %WEBDEPLOY PROJECT%\_theme_ |
This alias path can be used when inputting distribution information paths or path information in application programs.
Actual path names can vary according to product versions or license policies of relevant countries.
nexacro.xml
The nexacro.xml file is XML used to contain information for each user. The file path is as follows.
%USERAPP%
Relative Path
Relative Path Support for Paths in Projects
The chart below shows the types of major paths and relative path support, and service usage path support (Service::a.xfdl format path).
File Type | Category | Relative Path | Supports Service Usage Path | |
---|---|---|---|---|
Support | Standard Path | |||
Typedefinition | Component UpdateURL 1 | Y | TypeDefintion | Y |
Service Path | Y | TypeDefintion | N | |
GlobalVariable | Image | Y | GlobalVariable | Y |
XADL | TypeDefinition 2 | Y | XADL | N |
GlobalVariable | Y | XADL | Y | |
Engine path 3 | Y | XADL | N | |
Licenese path 4 | Y | XADL | N | |
Themeid | Y | XADL | Y |
Component UpdateURL
A path for the server to update components. It also corresponds to the TypeDefinition Update UpdateUrl in tool.
However, if its domain (for rexample, http://a.b.c/path > a.b.c) isn't matched with the XADL path, update is not available. If XADL has a local path, update is available regardless of the domain information.
TypeDefinition
Paths for services. It also corresponds to TypeDefinition Services url in tool.
Engine path
A path to update the engine. It also means ADL engineurl in tool. However, if its domain is not matched with the XADL path, update is not available. If XADL has a local path, update is available regardless of the domain information.
Licenese path
A path to check the license before reading the Typedefinition.
It means ADL licenseurl in Tool.
However, its domain should be not matched with the XADL path. If XADL has a local path, the license will be checked regardless of the domain.
Plugin Method
The following table describes the types of paths set to HTML, as well as relative paths support, when running Nexacro Platform HTML plugIn method.
Classification (HTML) | Item | HTML Relative Path | XADL Relative Path | Service Ssage Path Support |
---|---|---|---|---|
CODEBASE | SetupEngine.cab | N/A | N/A | N/A |
nexacro14_Launcher.cab | N/A | N/A | N/A | |
SetupEngine | Xadlpath property | supported | N/A | N/A |
NexacroLauncherAX | Xadlpath property | supported | N/A | N/A |
Loadingimage property | supported | N/A | N/A | |
Splashimage property | supported | N/A | N/A | |
makeshortcut() | supported | N/A | N/A |
4GL doesn't support those relative paths. Only HTML supports those paths.
The standard paths for HTML relative paths are HTML paths.