| Both sides previous revision Previous revision Next revision | Previous revision |
| docs:2500_config_apps:4300_runtime_exec [2022/08/25 00:00] – ↷ Page moved from 2500_config_apps:4300_runtime_exec to docs:2500_config_apps:4300_runtime_exec administrator | docs:2500_config_apps:4300_runtime_exec [2025/06/12 03:59] (current) – Change to AwareIM aware_support3 |
|---|
| ====== Building Runtime Executable ====== | ====== Building Runtime Executable ====== |
| |
| <note>This feature is only available in the Aware IM Developer Edition.</note> | <callout type="primary" icon="true" title="note"> This feature is only available in the AwareIM Developer Edition.</callout> |
| |
| If you want to sell applications configured with //**Aware IM**// you can use the "Build Executable" feature to prepare the system for your end users with your own product name and copyright. | If you want to sell applications configured with //**AwareIM**// you can use the "Build Executable" feature to prepare the system for your end users with your own product name and copyright. |
| |
| To do this select the business space version containing the final configuration of your application and select the "Build Executable" menu item from the "Version" menu. //**Aware IM**// will display the "Build Executable" dialog. Enter the following information in the dialog: | To do this select the business space version containing the final configuration of your application and select the "Build Executable" menu item from the "Version" menu. //**AwareIM**// will display the "Build Executable" dialog. Enter the following information in the dialog: |
| |
| ===== Name of the application ===== | ===== Name of the application ===== |
| ===== Other resources ===== | ===== Other resources ===== |
| |
| If your application requires any other resources (such as images used in the ''[[3100_actions:0270_import_document|IMPORT DOCUMENT]]'' action), move these resources into a separate directory and specify the name of this directory. Make sure that these resources are referred to using '../OtherResources', for example | If your application requires any other resources (such as images used in the ''[[a_f:a:import_document|IMPORT DOCUMENT]]'' action), move these resources into a separate directory and specify the name of this directory. Make sure that these resources are referred to using '../OtherResources', for example |
| |
| <code aim>IMPORT DOCUMENT Statement.StatementDocument FROM '../OtherResources/myfile.doc'</code> | <code aim>IMPORT DOCUMENT Statement.StatementDocument FROM '../OtherResources/myfile.doc'</code> |
| ===== Custom JAR’s location ===== | ===== Custom JAR’s location ===== |
| |
| If your application requires any custom JAR files (for example if you write your own Java extensions – see [[2000_concepts:0900_prod_feats:0800_extending_awareim|Extending Aware IM]] and [[3500_prog_ref:0000_start|Aware IM Programmer’s Reference]]), move these JAR files into a separate directory and specify the name of this directory. This value is optional. | If your application requires any custom JAR files (for example if you write your own Java extensions – see [[docs:2000_concepts:0900_prod_feats:0800_extending_awareim|Extending AwareIM]] and [[docs:3500|Programmers Reference Guide]]), move these JAR files into a separate directory and specify the name of this directory. This value is optional. |
| |
| ===== JDK location ===== | ===== JDK location ===== |
| |
| If you are building an application for the Linux platform and your current operating system is not Linux, you need to download the Linux JDK1.4 or later(( The license of Sun Microsystems does not allow distributing the complete JDK. However, //**Aware IM**// only requires Java Runtime environment (JRE) and the file tools.jar (you can take it from the JDK and put into the lib directory of the JRE – this file can be freely distributed together with the JRE). )) and specify the directory where it is stored. | If you are building an application for the Linux platform and your current operating system is not Linux, you need to download the Linux JDK1.4 or later(( The license of Sun Microsystems does not allow distributing the complete JDK. However, //**AwareIM**// only requires Java Runtime environment (JRE) and the file tools.jar (you can take it from the JDK and put into the lib directory of the JRE – this file can be freely distributed together with the JRE). )) and specify the directory where it is stored. |
| |
| Once you provide the required values and press OK //**Aware IM**// will build the executable (for Windows platform) or zip file (for Linux and Mac OS X platforms) in the output directory that you specified. You can distribute this executable or zip file to your end users. | Once you provide the required values and press OK //**AwareIM**// will build the executable (for Windows platform) or zip file (for Linux and Mac OS X platforms) in the output directory that you specified. You can distribute this executable or zip file to your end users. |
| |
| <note>When you install the runtime application you will not be able to run the Configuration Tool. If you want users to be able ton run the Configuraton Tool install the standalone Configuration Tool on the runtime machine or copy the AwareIM/ConfigTool directory from your development machine to the runtime machine.</note> | <callout type="primary" icon="true" title="note"> When you install the runtime application you will not be able to run the Configuration Tool. If you want users to be able ton run the Configuraton Tool install the standalone Configuration Tool on the runtime machine or copy the AwareIM/ConfigTool directory from your development machine to the runtime machine.</callout> |
| |
| <note>If you are distributing an application for Mac OS X platform you can take the resulting zip file to the Mac platform, unpack it and create an application bundle and/or distributable package out of it (see Mac OS X manuals for details). You can then distribute the application bundle or package to your customers. If you decide to distribute the application as an original zip file, you will need to provide startup instructions in a readme file. Customers will need to unpack the zip file, start the Mac OS X Terminal application, change to the ''BIN'' directory and run the startAwareIM.sh script.</note> | <callout type="primary" icon="true" title="note"> If you are distributing an application for Mac OS X platform you can take the resulting zip file to the Mac platform, unpack it and create an application bundle and/or distributable package out of it (see Mac OS X manuals for details). You can then distribute the application bundle or package to your customers. If you decide to distribute the application as an original zip file, you will need to provide startup instructions in a readme file. Customers will need to unpack the zip file, start the Mac OS X Terminal application, change to the ''BIN'' directory and run the startAwareIM.sh script.</callout> |
| |
| |