Apertium scalable service - Revision history

Francis Tyers: Redirected page to Apertium-apy

2018-03-07T08:39:16Z

Redirected page to Apertium-apy

2018-03-07T08:38:51Z

2012-03-24T11:27:48Z

Category:Documentation in English

2010-02-18T11:09:39Z

2009-12-21T07:23:16Z

2009-11-05T12:42:38Z

2009-11-05T12:41:40Z

Introduction

2009-11-05T12:41:26Z

2009-11-05T09:51:09Z

2009-11-05T09:13:30Z

@@ Line 415: / Line 415: @@
 [[Category:Development]]
 [[Category:Services]]
+[[Category:Documentation in English]]

@@ Line 1: / Line 1: @@
 =Introduction=
-This is the wiki page of '''ApertiumScalableServer''', a scalable architecture to provide translation web services based on Apertium.
+This is the wiki page of '''ApertiumScalableServer''', a scalable architecture to provide translation web services based on Apertium. This project has been moved to [[ScaleMT]], a new architecture that supports different translation engines, document translation (odt and rtf at the moment), a new XML-RPC API, etc. Please check [[ScaleMT]] if you want a more feature-rich and tested software.
 =User manual=

@@ Line 1: / Line 1: @@
 =Introduction=
-This is the wiki page of '''ApertiumServer''', a scalable architecture to provide translation web services based on Apertium.
+This is the wiki page of '''ApertiumScalableServer''', a scalable architecture to provide translation web services based on Apertium.
 =User manual=

← Older revision	Revision as of 12:42, 5 November 2009
(No difference)

@@ Line 18: / Line 18: @@
 ==Getting it==
-At the moment, the only way to get the applications is downloading its source code and compiling them. You'll need to download the source code of three projects from the Apertium svn repository. Before executing the following commands, be sure you have [http://subversion.tigris.org/ Subversion] installed.
+At the moment, the only way to get the applications is downloading its source code and compiling them. You'll need to download the source code of three projects from the Apertium svn repository. Before executing the following command, be sure you have [http://subversion.tigris.org/ Subversion] installed.
 <pre>
-svn co http://apertium.svn.sourceforge.net/svnroot/apertium/branches/gsoc2009/vitaka/ApertiumServerRMIInterfaces
+svn co http://apertium.svn.sourceforge.net/svnroot/apertium/trunk/apertium-scalable-service
-svn co http://apertium.svn.sourceforge.net/svnroot/apertium/branches/gsoc2009/vitaka/ApertiumServerSlave
-svn co http://apertium.svn.sourceforge.net/svnroot/apertium/branches/gsoc2009/vitaka/ApertiumServerRouter
 </pre>

@@ Line 120: / Line 120: @@
 To keep track of registered users and give them higher priority, their data are stored in a MySQL database. Database connection properties are configured in [http://java.sun.com/javaee/technologies/persistence.jsp?intcmp=3282 JPA] configuration file:''WEB-INF/classes/META-INF/persistence.xml''. By default, it connects to a database called '''ApertiumWSUsers''' on localhost, with username '''apertium''' and password '''apertium'''.
+===Port summary===
+Be sure these ports are reachable, since they are needed by the system to work.
+Machine running ''ApertiumServerRouter'':
+* RMIRegistry port. By default, it is 1098. If you want to use another port for running RMIRegistry, change the property ''rmi_registry_port''.
+* RMI remote object port. The port where the object that communicates with ''ApertiumServerSlave'' instances listens. By default it is 1432, but can be changed by editing the property ''requestrouter_rmi_port''.
+* HTTP port. The port which the web server listens to.
+Machine running ''ApertiumServerSlave'':
+* RMIRegistry port: 1099.
+* RMI remote object port. The port where the object that communicates with ''ApertiumServerRouter'' listens. By default it is 1331, but it can be changed with the option ''-RMIPort <port-number>'' when running ''ApertiumServerSlave''.
 ===Logging===