Installation Guide for ADempiere on IBM i

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.


This installation guide has been written for setting up ADempiere on IBM i or i5/OS, the native operating systems of IBM Power Systems and System i. Either JBoss or WebSphere can be used as the application server, though performance testing has shown that WebSphere is faster and more reliable on installations that may require 50 or more concurrent users.


  • Posterita not supported
  • WebStore not supported

Tested ADempiere versions

  • 3.4.0


  • IBM Power System, System i or iSeries
  • IBM i or i5/OS
  • WebSphere Application Server (on native partition)
  • Two partitions setup – IBM i for Application Server and Linux for Database (SLES 10.1 recommended)
  • Eclipse IDE for Java EE Developers (installed on Linux partition or separate machine with Linux or Windows)
  • You must be able to log in as the administrator in both partitions (root in Linux, qsecofr in IBM i)

Linux Partition Setup

IBM Java installation

Sun does not support Power5 and Power6 processors, IBM Java is required instead. IBM-JAVA2-PPC64-SDK-5.0 can be downloaded from here. You will need to register with IBM if you have not already, which entitles you to free access to other software, white papers and red books.

Once you have downloaded the file you will need to install it with the following command:

 rpm –Uvh ibm-java2-ppc64-sdk-5.0-5.1.ppc64.rpm

Java should be be installed in a directory similar to /opt/ibm/java2-ppc64-50. This can be checked with the following command:

 /opt/ibm/java2-ppc64-50/bin/java -version


Ensure that your setup has the following packages installed as they are required for compiling PL/Java. If you are using SLES 10 this can be done though Software Management in Yast 2 (Control Center -> Software -> Software Management):

  • GCC-JAVA - gcc-java 4.1.0-28.4 (Must install)
  • C compiler run time library - libgcc
  • 64bit C compiler runtime library - libgcc-64bit
  • Java Runtime Library for GCJ - libgcj
  • 64bit Java Runtime Library for GCJ - libgcj-64bit
  • GCC Preprocessor - cpp

In Software Management, verify that the following packages are installed for the PostgreSQL DBMS:

  • Postgresql-server
  • Postgresql-dlevel
  • Postgreslibs-64bit
  • Postgresqllibs
  • Postgresql-jdbc

If you are using a Linux distribution other than SLES 10, you may need to download and install PostgreSQL manually. If you are using SLES 10.1 but cannot find the required packages, you will need to add the following repositories to Yast 2:

Once the files have been installed, start the PostgreSQL server with the following command:

 /etc/init.d/postgresql start

If it does not already exist, create a new user called postgres:

 createuser – P postgres

Change the password of postgres and switch to that user:

 passwd postgres
 su – postgres

Create a database user called adempiere in PostgreSQL and create the adempiere database by entering the following on the command line:

 CREATE USER adempiere WITH PASSWORD 'adempiere';

You will now need to compile and install PL/Java.


Make sure you are logged in as root and set the JAVA_HOME environment variable to the directory where java was installed, for example:

 export JAVA_HOME=/opt/ibm/java2-ppc64-50

Download the PL/Java source code, which is available from here

Save the archive to the /opt directory and then extract it:

 cd /opt
 tar zxfv pljava-1.3.0.tar.gz
 cd pljava-1.3.0

The following steps will compile pljava and build the required object files and jar files:

 make USE_GCJ=1
 mkdir -p /usr/share/pljava  
 install -m 644 build/pljava.jar /usr/share/pljava 
 install -m 644 build/deploy.jar /usr/share/pljava  
 install -m 755 build/objs/ /usr/share/pljava  
 cat > /etc/ <<EOF 

If you prefer you can do this step manually by creating the /usr/share/pljava directory and manually copying over 'pljava.jar deploy.jar and' and setting the required permissions with chmod. You will then need to create a postgres.conf file in /etc/ and add required java directories as listed above.

Rebuild the library list with:


Ensure your '' has been set with the following:

 ldconfig -p |grep

You should get something like: (libc6,64bit) => /opt/ibm/java2-ppc64-50/jre/bin/classic/ If the command returns nothing check the /etc/ file and verify that the directories are correct.

Modify postgresql.conf in /var/lib/pgsql/data (remember to uncomment #the lines): add these lines:

 custom_variable_classes = 'pljava' 
 pljava.classpath = '/usr/share/pljava/pljava.jar' 

Modify the following: listen_addresses = '*' # if you want to log in from the internet port = 5432

dynamic_library_path = '$libdir' to dynamic_library_path = '$libdir:/usr/share/pljava'

then modify pg_hba.conf in /var/lib/pgsql/data. The result will look something like this:

 #local is for Unix domain socket connections only
 local   all         all                               trust 
 # IPv4 local connections:
 host    all         all          trust
 host    all         all          trust
 host    all         all         appserver/32          trust
 # IPv6 local connections:
 host    all         all         ::1/128               trust
 host    adempiere   adempiere             trust

Restart the postgreSQL server by running the following command:

 /etc/init.d/postgresql restart

(NOTE: You will need to restart the postgresql server every time you update the ph_hba.conf file for the changes to take effect)

Then install pljava into Database by running:

 java -cp /usr/share/pljava/deploy.jar:/usr/share/pgsql/postgresql-8.1-404.jdbc3.jar \
 org.postgresql.pljava.deploy.Deployer -install -user adempiere -database adempiere \
 -password adempiere

Database Table Setup

Download ADempiere and extract it to a temporary directory. Change to this directory and run the script:


All of the tables required for ADempiere will be generated via this script, which may take several minutes to complete.

The database should now be ready to communicate with the Application Server.

IBM i partition setup

Download ADempiere onto the Linux partition and decompress it using:

 gunzip Adempiere_340s.tar.gz

Transfer the archive to the native partition using ftp using binary mode:

 ftp <servername>
 cd /
 put Adempiere_340s.tar

Extract the archive using pax. Do NOT use tar as IBM I uses a different character set and the binary files will be corrupted:

 pax –r –C 819 –f Adempiere.tar

Export the JAVA_HOME and ADEMPIERE_HOME environment variables, make sure that JAVA_HOME points to version 1.5 of java:

 export ADEMPIERE_HOME=/Adempiere
 export JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit
 java –version

(NOTE: It is strongly recommended that you use use /Adempiere as your adempiere installation directory. Using other directories may result in problems that are difficult to fix otherwise.)

Copy the adempiere environment properties template into the adempiere environment properties file with the following command:


Edit the file and make the following changes. You may need to ftp the file to the Linux partition and back in order to edit it:

 JAVA_HOME=/ QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit

Make a directory for the key store and generate a key for ADempiere using the IBM Java keytool, as follows:

 Mkdir keystore
 $JAVA_HOME/bin/keytool –genkey –keyalg rsa –alias adempiere –dname “CN=localhost, 
 OU=ADempiere Bazaar, O=AdempiereUser, L=Sydney, S=NSW, C=AU” –keypass adempiere 
 –validity 999 –keystore /Adempiere/keystore/myKeystore –storepass adempiere

Run the ADempiere setup with the following command:

 Chmod 744

Once the installation has completed successfully you have the option of fixing JBoss or migrating to WebSphere Application Server.

Running JBoss

In order to run JBoss in IBM I a few configuration changes are necessary.

Edit the file (either natively or by transferring to another partition server with ftp) ADEMPIERE_HOME/jboss/server/adempiere/deploy/jbossweb-tomcat55.sar/server.xml. You will need to add the following argument to the tag below the comment :

 algorithm = IbmX509

Edit ADEMPIERE_HOME/utils/ and remove the ‘-server’ options from JAVA_OPTS.

Migrating to WebSphere

Change the working directory to: ADEMPIERE_HOME\jboss\server\adempiere\deploy\adempiere.ear

Package the exploded ear into a compressed file using:

 jar cvfM adempiere.ear *

Use ftp to transfer the packaged ear file to the machine where you have Eclipse installed. Open eclipse and go to file -> import. Select J2EE -> ear file. Locate the compressed ear file and use all of the default settings. Do NOT select a target runtime. Click Finish.

Open up the application deployment descriptor (adempiere -> earContent -> META-INF -> application.xml) and make the following modifications:

  • Add in a document type descriptor tag directly before the application tag:
 <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN"
  • Remove all of the parameters from the application tag.
  • Add the next two lines directly beneath the application tag if they are not already present
 <description>ADempiere Applications</description>
  • Remove the following lines completely from the file:

Find the module for adempiereWebCM.war and change the context root to home, as shown below:

  • Remove the following completely from the file:

Open up the deployment descriptor for adempiereApps.war (adempiereApps ->WebContent -> WEB-INF -> web.xml) and make the following modifications:

  • Add in a document type definition tag directly before the web-app tag:
 <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "">
  • Remove all of the parameters from the web-app tag

Open up the manifest file for adempiereRoot.jar (adempierRoot_EJB -> ejbModule -> META-INF -> MANIFEST>MF and make the following modifications:

  • Delete the following section:
 Name: META-INF/jaws.xml
 SHA1-Digest: vb2Dx67PF/Qhr9XGrx03Of8tjdw=
  • Delete the following section:
 Name: META-INF/jboss.xml
 SHA1-Digest: FF5ayoXZ7BfYVDld/IMvvHqpvEg=

Delete the following files from the adempiereRoot_EJB -> ejbModule -> META-INF folder:

  • jaws.xml
  • jboss.xml

Open up the deployment descriptor for adempiereRoot.war (adempiereRoot_WEB ->WebContent -> WEB-INF -> web.xml) and make the following modifications:

  • Add in a document type definition tag directly before the web-app tag:
 <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "">
  • Remove all of the parameters from the web-app tag

Open up the deployment descriptor for adempiereWebCM.war (adempiereWebCM ->WebContent -> WEB-INF -> web.xml) and make the following modifications:

  • Add in a document type definition tag directly before the web-app tag:
 <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "">
  • Remove all of the parameters from the web-app tag
  • Swap the order of the <mime-mapping> and the <welcome-file-list> tags

Open up the deployment descriptor for adempiereWebStore (adempiereWebStore ->WebContent -> WEB-INF -> web.xml) and make the following modifications:

  • Add in a document type definition tag directly before the web-app tag:
 <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "">
  • Remove all of the parameters from the web-app tag
  • Move the mime-mapping tag to above the welcome-file-list tag
  • Delete the Posterita project, including its contents, from the solution.
  • Right Click on the Adempiere Project and select Export -> Ear File. Choose a directory and click finish.

Open up your web browser from the machine with new ear. Go to the WebSphere Administration Console and follow these steps to install the ear into the application server:

  • Go to Enterprise Applications -> Install New Application
  • Browse for the ear file that was exported from Eclipse and click next
  • Accept the installation options and click Next
  • Select all of the modules to be mapped to the server by ticking all of the boxes and click next.
  • Provide the JNDI names as adempiere/Status and adempiere/Server respectively and click next.
  • Specify the target resource JNDIs as adempiere/Status, adempiere/StatusLocal, adempiere/Status and adempiere/ServerLocal and click next.
  • Accept the default configuration for Map virtual hosts for Web modules by clicking next.
  • A summary will be displayed, click finish.


Upgrading to WebSphere Application Server v6.1.0.17

If you have a slightly older version of WebSphere Application Server, it is highly recommended that you upgrade to v6.1.0.17 before attempting deployment. This is a straight forward process that can be performed by visiting IBM Fix Central. You will need to access the site from a browser that is on a machine that can access the server on which the installation is being performed as the file will be downloaded directly onto the server using the browser's machine as a proxy.

At the site simply parameters for your installation, in this example the parameters were:

 Product family: System i
 Product: IBM i, i5/OS, and OS/400
 Ordering Option: Groups, Hiper and Cumulative Fixes
 OS Level: V5R4

Next you will be prompted to login with an IBM ID (which can be obtained for free). Following this a list of fixes will be listed. Select SF99323 WebSphere App Server v6.1 Level 17 and add it to the download list, click continue. You will be prompted for the necessary details needed to access the server. Once the download has completed the fix needs to by entering into the <WebSphere-Path>/Base/bin directory in qsh and executing the fixpack as follows:


EJB Deploy Error ADMA0086E

If you upgraded your WebSphere Application Server version and you had previously attempted an ADempiere deploy on the prior version of the application server, there is a strong chance you will receive this error. It occurs when the server is upgraded, but the configuration fails to update. To overcome this problem find the configuration directory using:

 ./ejbdeploy -log

Now delete all files the configuration directory except config.ini if it exists.

For more information about this problem visit