Application Server Installation and Setup
Last updated
Last updated
This page is directed at System Administrators who need to install the ADempiere Application Server in a network environment where the database server could be running on a separate network server and the clients run on remote computers.
Before continuing, ensure you have installed a suitable database (i.e. Oracle 10g, Oracle 10gXE, PostgreSQL, MySQL) and that the database server is running. See Database Server Installation & Setup.
Download each of the following packages:
Java SE Development Kit - Get the latest from http://www.oracle.com/. You only need the JDK without JavaFX, EE or NetBeans bundles.
ADempiere Latest Release - Download the latest ADempiere from here.
ADempiere Patches - Any patches or customization jars to apply.
Install the JAVA JDK with the default installation settings. Say OK to install the follow-on JRE as well. Carefully note the full path for the JDK directory (e.g: C:\Program Files\java\jdk1.5.0_19) and the JRE directory that you have just installed.
| | Note:There may well be a number of JDK and JRE directories, so choose the right one! The JDK should include the JRE. | | :--- | :--- |
The ADempiere scripts rely on the existence of a system environment variable JAVA_HOME. When the scripts call java, they use the full path as JAVA_HOME/bin/java so it is important that this variable exist.
Following the instructions for your system, add a new System Variable JAVA_HOME for your new JDK directory. Set JAVA_HOME to C:\Program Files\Java\jdk1.7.0_25 (or whatever your JDK directory is called).
According to your OS, append the following JDK path to the system path:
%JAVA_HOME%\bin or
$JAVA_HOME/bin
There is no install script. Just extract the ADempiere archive to a suitable location: (e.g. c: or /u01/). For reference, call this directory ADEMPIERE_ROOT. You should end up with the files in a folder like ADEMPIERE_ROOT\Adempiere. For reference, call this folder ADEMPIERE_HOME.
Patches are a combination of *.jar files, which replace *.jar files in the ADEMPIERE_HOME\lib directory, and migration scripts which update the database. In the Patches directory on Source Forge, there may be more than one type of *.jar that needs patching. If you downloaded one or more patch files, replace the existing file with the downloaded one, changing its name to match. For example, copy the *_patches_*.jar file to ADEMPIERE_HOME\lib\patches.jar, overwriting the existing file. See the detailed instructions in Patches Installation.
If you have a customization.jar with customized code or a packages.jar file with supporting *.jar files, add them to the ADEMPIERE_HOME\lib directory, overwriting the existing files.
For migration scripts which end in .xml, store these in the ADEMPIERE_HOME/migration directory.
The Application Server is configured by a utility RUN_Setup.(sh/bat) found in the ADEMPIERE_HOME directory. This utility launches a tool where the configuration settings can be set and tested. Once everything passes the tests, the configuration is saved and the software repackages itself with the new settings. You can then launch the Application Server.
You can rerun this utility as many times as you like until everything is correct.
In a command shell with administrative privileges, run the script RUN_Setup, located in the ADEMPIERE_HOME directory. The ADempiere Server Setup window should appear as shown below:
The Setup window opens and loads its values from the file AdempiereEnv.properties. It looks for this file in the ADEMPIERE_HOME directory. If the environment variable ADEMPIERE_HOME is not set or is null, it will look in the directory defined in the system property "user.dir".
Fill in the setup window fields as follows:
Java
Java Home: select the SDK Java Home location (e.g. C:\jdk1.5.0_05). This should be the same as the JAVA_HOME environment variable.
Java VM: the Java Virtual Engine Vendor (Default= Sun).
Adempiere
ADempiere Home: is the base directory where the distribution files are located (e.g. C:\Adempiere). This should be the same a the ADEMPIERE_HOME environment variable.
KeyStore Password: ADempiere requires a SSL certificate. It automatically creates a certificate in the key store $ADEMPIERE_HOME/keystore/myKeystore with the keystore password entered. The self certified certificate created has the alias adempiere and uses the same password as the keystore. You can replace the certificate used with the Java "keytool" (see Java tool documentation).
Application Server
Application Server: is the name, URL or IP of your server PC (Don't use localhost). The Application Server defaults to the server currently running the program. Avoid using IP addresses - use the DNS name of the server.
Web Port: The web port that the Application Server will listen on. Access to the application server will be through a URL similar to http://myApplicationServer:webport (http://appserver:8088\. Please keep in mind that, under Linux/Unix, ports under 1000 need root privileges. If you use Apache as a front end, you may need to use ports like 8080 or 8088 - basically, find a free port. The default ports is 80
SSL: The secure socket layer port. The default is 443. If that is not available try another value such as 4443 or 8443.
JNP Port: The Java Name Provider and Remote Method Invocation(RMI) port. The Default ports are 1099 (1098).
Database Server
Database Server: The Database Server defaults to the server currently running the program. Avoid using IP addresses - use the DNS name of the server. Localhost can be used only if the database server is running on the same machine as the Application Server and client software. For Oracle, the Service names are discovered. You can overwrite the entries if they are not correct.
Database Name:
PosgreSQL: PostgreSQL database name
Oracle: SID/Service name. Oracle 10g/11g default: orcl, OracleXE default: xe
Database Type: select the database you have installed (i.e. Oracle 10g, Oracle 10gXE, PostgreSQL).
Database Port: select the port for connect to database.(i.e. Oracle use 1521 as standard port, PostgreSQL 5432, etc.)
System Password:
Oracle: Password for the system user.
PostgreSQL: Password for the postgres user.
Database User: The application database user name, default is adempiere.
Database Password: The application database password, default is adempiere.
Mail Server (See notes below)
Server: _**_the mail server (e.g. smtp.gmail.com)
Port: the mail server port for sending mail
Protocol: the protocol to use, SMTP or IMAP
Admin E-Mail: The email to use as the From address
Encryption Type: The type of encryption to use
Auth. Mechanism: how the account is authorized. Login is the default.
Mail User: the mail user login name
Mail Password: the mail user password
Mail setup is optional but a server does have to be identified. The Setup Tool will finish successfully whether the mail tests work or not. You can maintain the mail server connection in the Application on a Client basis from the Client Window. If you don't want to setup mail or don't have an SMTP server, just enter a valid server - the field defaults to the local computer name. As long as the server exists, the setup will finish successfully.
After you fill the Setup fields, press the Test button to verify them. As the test progresses, you will see the boxes checked (√). Only if all the parameters are verified will you will not be able to save them. If an entry cannot be verified, a pop-up window stating the error will be displayed Fix it and test again.
If, for example, the Application Server name is wrong, then you will see a message such as:
When all the tests pass (you can see the boxes checked: √ ):
press the Save button. This will save the settings to the AdempiereEnv.properties file in the ADEMPIERE_HOME directory.
After you accept the license, you will see the dialog:
Press the OK button to continue and take a look into the log. Make sure that you see the BUILD SUCCESSFUL and Done, such as:
If something is wrong, you can fix it and rerun the script until everything is correct.
Once the setup is complete, you can move on to Initialize the ADempiere Database.
Application Server * Database Server is the name, URL or IP of your server PC.
JNP Port = 1099 error means that a previous service is running. Kill it. Also, since this is the first port that is tested, it could also mean that you have a mismatch between your host name (in the hosts file) and your actual IP address. Fix it in "/etc/hosts" (linux)
Database Port = 1521 error can be solved by restarting DB machine.
System & Database Passwords are those defined when you setup your Database.
Mail Server is optional. RUN_Setup can still finish without it.
If you receive the following message:
You should check your java environment variables. Check that the JAVA_HOME system environment variable points to the correct directory.
If you receive the following message from the installer:
it is likely that you have some other web server running or, if your are using Linux, you need the appropriate privileges.
The default ports are: 80 for http connections and 443 for SSL connections. This message means that the user is not allowed to use the port, likely because it is already used by another application. Change the port to something else. WebPort 8088 and SSL 4443 are recommended. If you are using Linux, remember that ports under 1000 need root privileges. If you are using Oracle database, port 8080 might be used.
Another possible error is Server Setup Error Error JNP Port (Not correct: JNP Port = 1099) OK
The JNP Port = 1099 error can be caused by another process which is already attached to that TCP port. Take a look what process is using this port and so you can take steps to stop it. It can also be caused by a mismatch between your IP address and the entry in your hosts file. See /etc/hosts(linux) or %SystemRoot%/system32/drivers/etc/hosts(windows).
This error is usually related to a DNS problem. It is possible to complete the setup using IP addresses when installing with PostgreSQL. Make sure you have a working DNS environment or add an entry in /etc/hosts(linux) or %SystemRoot%/system32/drivers/etc/hosts(windows).
Initialize the ADempiere Database is the next thing after Install Server.
Launching the ADempiere Application to perform the Client-Server client install which is the next thing to do after completing the Database setup.
Initial Client Setup is the starting business setup within ADempiere.
Getting Started Tutorial on how to setup and configure ADempiere for single computer operation (database, application and client all on the same machine).
Tutorials on many things from basic to advanced.
| | Note: Avoid spaces in the directory path. The batch scripts do not like directory names with spaces. If using a ADEMPIERE_ROOT with multiple directories, avoid directory names with spaces. | | :--- | :--- |
| | Note:It is a good idea to rename the existing *.jar file to something like patches.jar.old before you replace it with the the new file | | :--- | :--- |
| | Note: In case you are changing settings on an existing Application Server, make sure that the Application Server is shut down before you start. Otherwise you will get port errors during the testing. You can shut down the Application server by running the script RUN_Server2Stop.(sh/bat) from ADEMPIERE_HOME/utils or by stopping the "service". | | :--- | :--- |
| | Note:The setup process creates a file named Adempiere.properties. This is the main configuration file for your Client. You can copy this file and pass it as a variable when you start ADempiere using the command line interface parameter-DPropertyFile=AdempiereProduction.properties. If you create several files you can use them to easily switch between development, test and production environments, for example. | | :--- | :--- |
| | Note:The software only needs a method to send email. There is no ability to read email in the application. | | :--- | :--- |
| | Note:To find the IP address of your server try the following in a command script:Linux /sbin/ifconfigWindows IPCONFIG | | :--- | :--- |
