Difference between revisions of "Launching the Application Server"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(Start Application Server)
m (Change intro)
 
(14 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Getting further HELP==
+
{{Breadcrumb|Table of Contents|Getting Started|next=Launching the ADempiere Application}}
 +
[[Category:User documentation]]
 +
[[Category:Installation]]
  
*Further requests for assistance please direct to the [http://sourceforge.net/forum/forum.php?forum_id=610547 HELP Forum]. This wiki provides only written and publishable support.
+
== Start Application Server ==
*Further private, local, or commercial assistance can be sought at [[ADempiere#World-wide Directory|World-wide Directory]] where consultants all over register themselves. The fee charges are up to the respective consultants and under their own responsilibity or control.
+
Before launching the Application Server, you should already have completed:
*Please adhere to our bazaar [[etiquette]] to enjoy better support from us.
+
* [[Database Server Installation & Setup]]
 +
* [[Application Server Installation & Setup]]
 +
* [[Initialize the ADempiere Database]]
  
== Complete ADempiere Server Install ==
+
If the above are completed, you can start the JBoss-based ADempiere Application Server.  For demonstrations, its fine to launch the server from a console. For production systems, its best to use a method that will keep the server running after the user has logged off.
Before to start, you should have steps accomplished:
+
* Database installed (i.e. Oracle 10g, Oracle 10gXE, PostgreSQL)
+
* Java [http://java.sun.com/javase/downloads/index.jsp JDK1.5.x] installed.
+
* [[InstallServer|ADempiere Server installed]].
+
* [[CreateDatabase|ADempiere Database created]].
+
  
== Start Application Server ==
+
=== From the Console ===
You can now start the JBoss based ADempiere Application Server.
+
To run the ADempiere Server from a console, open up a console window and go to the ''$ADEMPIERE_HOME/utils'' directory. Run the script ''RUN_Server2[.bat|.sh]''
To do it, go to console command and go to ''utils'' directory into your $ADEMPIERE_HOME. The run the script '''RUN_Server2'' (.bat or .sh depending of your S.O.)
+
.
 
Then you will see the RUN_Server2 output, such as:
 
Then you will see the RUN_Server2 output, such as:
  
 
[[Image:IS_RUN_Server2.PNG|center]]
 
[[Image:IS_RUN_Server2.PNG|center]]
  
Please check that threre should be NO errors here. You can take a look into the logs to verify this (they are located at $ADEMPIERE_HOME/jboss/server/adempiere/logs).
+
If the server started with no errors, you can move on to [[Launching the ADempiere Application]].
  
The most commons problems are with the ports, when some of them are used. In this case, you check the ports where you are receiving error. Typical conficts ports are:  
+
=== As a Service on Windows Operating Systems ===
 +
For windows operating systems, the ADempiere Application Server can be installed as a service and scripts are provided for this purpose. Open a DOS shell with Administrative Privileges, navigate to %ADEMPIERE_HOME%\utils\windows and run:
 +
* ''Adempiere_Service_Install.bat'' for 32-bit systems; or
 +
* ''Adempiere_Service_Install_64.bat'' for 64-bit systems (since 380LTS hotfix 2). 
 +
 
 +
The install sets the start-up options as manual.  You will need to open the Services Window (Control Panel→Administrative Tools→Services) to set the properties so the service starts automatically or manually as required for your implmentation.
 +
 
 +
(Since 380LTS hotfix 2)
 +
On 64-bit systems, the service will log the full console output to %ADEMPIERE_HOME%\jboss\bin\run.log. As a result, run.log may get  large over time. To prevent this, comment out the CONSOLE appender-ref in the %ADEMPIERE_HOME%\jboss\server\adempiere\conf\jboss-log4j.xml file:
 +
 
 +
<root>
 +
      <appender-ref ref="CONSOLE"/>
 +
      <appender-ref ref="FILE"/>
 +
</root>
 +
 
 +
Once the Service is running, you can move on to [[Launching the ADempiere Application]].
 +
 
 +
=== Using nohup on Linux Systems ===
 +
For other operating systems, check <ADEMPIERE_HOME>/utils/unix or use the Linux nohup command (no hangup) as follows:
 +
 
 +
nohup ./RUN_Server2.sh &
 +
 
 +
To see the output of the server, use
 +
 
 +
cat nohup.out | more
 +
 
 +
or
 +
 
 +
tail nohup.out
 +
 
 +
If the server started with no errors, you can move on to [[Launching the ADempiere Application]].
 +
 
 +
=== Trouble Shooting ===
 +
Check the logs for errors. They are located at $ADEMPIERE_HOME/jboss/server/adempiere/logs or $ADEMPIERE_HOME/jboss/bin.
 +
 
 +
The most common problems are with ports already in use. Typical conflicting ports are:  
  
 
:* HTTP: 80, 443, 8080, 8443
 
:* HTTP: 80, 443, 8080, 8443
 
:* RMI : 1098, 1099
 
:* RMI : 1098, 1099
  
'''Any port conflict when starting the Application Server must be solved.'''
+
For Linux users: sometimes it helps to restart the workstation/server and execute RUN_Server2 as root.
 +
 
 +
'''Any port conflict when starting the Application Server must be resolved!'''
  
[[Category:OnLineHelp]]
+
If you have errors related to the database, check that the database has been installed, ADempiere data imported and that the database server is running.

Latest revision as of 06:38, 19 April 2015

Table of Contents{{#if: Getting Started| | Getting Started }}{{#if: | | [[{{{3}}}]] }}{{#if: | | [[{{{4}}}]] }}{{#if: | | [[{{{5}}}]] }} | Launching the Application Server{{#if: Launching the ADempiere Application| | Launching the ADempiere Application }} ⇒

Start Application Server

Before launching the Application Server, you should already have completed:

If the above are completed, you can start the JBoss-based ADempiere Application Server. For demonstrations, its fine to launch the server from a console. For production systems, its best to use a method that will keep the server running after the user has logged off.

From the Console

To run the ADempiere Server from a console, open up a console window and go to the $ADEMPIERE_HOME/utils directory. Run the script RUN_Server2[.bat|.sh] . Then you will see the RUN_Server2 output, such as:

IS RUN Server2.PNG

If the server started with no errors, you can move on to Launching the ADempiere Application.

As a Service on Windows Operating Systems

For windows operating systems, the ADempiere Application Server can be installed as a service and scripts are provided for this purpose. Open a DOS shell with Administrative Privileges, navigate to %ADEMPIERE_HOME%\utils\windows and run:

  • Adempiere_Service_Install.bat for 32-bit systems; or
  • Adempiere_Service_Install_64.bat for 64-bit systems (since 380LTS hotfix 2).

The install sets the start-up options as manual. You will need to open the Services Window (Control Panel→Administrative Tools→Services) to set the properties so the service starts automatically or manually as required for your implmentation.

(Since 380LTS hotfix 2) On 64-bit systems, the service will log the full console output to %ADEMPIERE_HOME%\jboss\bin\run.log. As a result, run.log may get large over time. To prevent this, comment out the CONSOLE appender-ref in the %ADEMPIERE_HOME%\jboss\server\adempiere\conf\jboss-log4j.xml file:

<root>
     <appender-ref ref="CONSOLE"/>
     <appender-ref ref="FILE"/>
</root>

Once the Service is running, you can move on to Launching the ADempiere Application.

Using nohup on Linux Systems

For other operating systems, check <ADEMPIERE_HOME>/utils/unix or use the Linux nohup command (no hangup) as follows:

nohup ./RUN_Server2.sh &

To see the output of the server, use

cat nohup.out | more

or

tail nohup.out

If the server started with no errors, you can move on to Launching the ADempiere Application.

Trouble Shooting

Check the logs for errors. They are located at $ADEMPIERE_HOME/jboss/server/adempiere/logs or $ADEMPIERE_HOME/jboss/bin.

The most common problems are with ports already in use. Typical conflicting ports are:

  • HTTP: 80, 443, 8080, 8443
  • RMI : 1098, 1099

For Linux users: sometimes it helps to restart the workstation/server and execute RUN_Server2 as root.

Any port conflict when starting the Application Server must be resolved!

If you have errors related to the database, check that the database has been installed, ADempiere data imported and that the database server is running.