Deploying with ApplinX

To deploy the ApplinX application

1. Export the ApplinX application's configuration and entities (refer to Managing an application). A GXAR file is created in the defined target folder.
2. Import the exported file to the target ApplinX server (refer to Managing an application).
   Note: In the production environment it is possible to use the export file as a read only repository.
3. Confirm that the option to trace files is disabled (refer to Application Properties>Host Tab Parameters>Record section). It is recommended not to produce trace files when in production, as this can affect performance.
4. Edit and configure the log settings (refer to Server Properties>Log). It is recommended to set the Log Level field to Warning.
5. When relevant, follow the steps detailed in Deploying an ApplinX Web Application.

To deploy the ApplinX server as a WAR file (Java web archive)

1. Right-click on the relevant application and choose Deployment Manager for J2EE.... The Deployment Manager wizard is displayed.
   
2. Ensure that the ApplinX server option is selected.
3. Click Next. The Select ApplinX Applications screen is displayed.
   
4. Select the Web applications to deploy.
5. Select the Export Software AG's proprietary Web Services component (WS-Stack) when using Web services, and WS-Stack has not already been installed.
6. Click Next. The Select Package Parameters screen is displayed.
   
7. From the list of Application Servers select the server to which you are going to deploy ApplinX server.
8. Enter the WAR file name, the destination folder where the output file will be placed and the JDK folder (ensure that the JAVA_HOME parameter points to the JDK installation folder).
9. Click Next. The Configure ApplinX Server on Target Machine screen is displayed.
   
10. In this screen, configure the ApplinX server parameters to be used on the target machine: the ports, and the license file.

To deploy the web application:

1. Right-click on the relevant application and choose Deployment Manager for J2EE.... The Deployment Manager wizard is displayed.
   
2. Ensure that the ApplinX for JSP Web application option is selected.
3. Click Next. The Select ApplinX Application screen is displayed.
   
4. Select whether to deploy a new application or HTML emulation, or a project from within the workbench, or a project from a different location.
5. Select Include source files to include the Java files as well as the compiled classes. Click Next. The Select Package Parameters screen is displayed.
   
6. From the list of Application Servers, select the server to which you are going to deploy ApplinX server.

   Enter the WAR file name, the destination folder where the output file will be placed and the JDK folder (ensure that the JAVA_HOME parameter points to the JDK installation folder).

   Note: When selecting WebLogic, you need to manually extract the content of the generated ZIP archive file.
7. Click Next. The Select Target ApplinX Server screen is displayed.
   
8. In this screen, enter the ApplinX server and the port with which the Web application will connect. Also enter the ApplinX application name.
9. Click Finish.
10. In the console area, it is possible to see whether the process succeeded or failed. The WAR file created should be placed in your Web server directory.

Consider changing the following for production use

1. Change the framework logging according to your needs either by accessing the "Framework Configuration Editor" or in config/gx_logConfig.xml file. For example: <category additivity="false" name="com.sabratec"> <level value=" ERROR"/> <!-- Sets the log to Errors only --> <appender-ref ref="FRAMEWORK_LOG"/> </category>

   Possible values are:

   • INFO - Normal
   • WARN - Warnings
   • ERROR - Errors only
   • DEBUG - Debug
2. Disable the Performance monitor either by accessing the "Framework Configuration Editor" or in config/gx_appConfig.xml file set the WritePerformanceLog to false (this is the default configuration).
3. Disable the Javascript log using the config/gx_clientConfig.xml by setting LogLevel to 0 and ShowLogConsole to false (this is the default configuration).
4. Remove "Framework Configuration Editor" link from index page: delete the folder z_admin and remove the link to "configuration editor" from the index page.

To deploy both the ApplinX server and jsp web application

1. Right-click on the relevant application and choose Deployment Manager for J2EE.... The Deployment Manager wizard is displayed.
   
2. Ensure that the Both - ApplinX server and JSP Web application option is selected.
3. Click Next. The Select ApplinX Application screen is displayed.
   
4. Select the ApplinX application to deploy. Click Next. The Select ApplinX Web Application screen is displayed.
   
5. Select whether to deploy a new application or HTML emulation, or a project from within the workbench, or a project from a different location.
6. Select Include source files to include the Java files as well as the compiled classes. Click Next. The Select Package Parameters screen is displayed.
   
7. From the list of Application Servers select the server to which you are going to deploy ApplinX server.

   Enter the WAR file name, the destination folder where the output file will be placed and the JDK folder (ensure that the JAVA_HOME parameter points to the JDK installation folder).

   Note: When selecting WebLogic, you need to manually extract the content of the generated ZIP archive file.
8. Click Next. The Configure ApplinX Server on Target Machine screen is displayed.
   
9. In this screen, configure the ApplinX server parameters to be used on the target machine: the ports, and the license file.
10. Click Finish.
11. In the console area, it is possible to see whether the process succeeded or failed. The WAR file created should be deployed to your Java Application Server.

Consider changing the following for production use

1. Change the framework logging according to your needs either by accessing the "Framework Configuration Editor" or in config/gx_logConfig.xml file. For example: <category additivity="false" name="com.sabratec"> <level value=" ERROR"/> <!-- Sets the log to Errors only --> <appender-ref ref="FRAMEWORK_LOG"/> </category>

   Possible values are:

   • INFO - Normal
   • WARN - Warnings
   • ERROR - Errors only
   • DEBUG - Debug
2. Disable the Performance monitor either by accessing the "Framework Configuration Editor" or in config/gx_appConfig.xml file set the WritePerformanceLog to false (this is the default configuration).
3. Disable the Javascript log using the config/gx_clientConfig.xml by setting LogLevel to 0 and ShowLogConsole to false (this is the default configuration).
4. Remove "Framework Configuration Editor" link from index page: delete the folder z_admin and remove the link to "configuration editor" from the index page.

To deploy the web application

1. Copy the entire Web application into a temporary working folder.
2. In the config/gx_logConfig.xml file edit the Logger settings according to your needs (enable/disable the log, target path and log level). For example: <logger name="com.sabratec"> <level value="INFO"/> <!"sets the log to normal mode <appender-ref ref="FRAMEWORK_LOG"/> </logger>

   When you do not require the performance log, ensure that the last two category nodes in the XML file are commented.

3. Change the definition of designMode in config/gx_appConfig.xml to false.
4. Change the definition of the serverURL and applicationName in config/gx_appConfig.xml to the target server.
5. Copy the updated folder to the relevant Web server.
6. Map this folder as a virtual directory under the server.