This page contains instructions for installing the xProcess web server, which is distributed as a java web application. For your convenience, we supply the server configured in its own instance of Apache Tomcat and a java runtime environment. All you have to do is unzip, enter configuration details in a properties file, then start the server.
The default port for the Web Server is 8081.
1. Network access to the SVN repository containing xProcess data source.
2. SVN account created for the xProcess Web Server. This must be a different account from the one used by the xProces workflow server (if installed).
3. Java servlet container. Each server has been tested with Apache Tomcat v5.5.20. For your convenience the server is distributed with Tomcat and a java runtime environment. All you have to do is unzip, enter configuration details in a properties file, then start the server.
See Getting Started for a complete overview of how to set up xProcess for a team. This is a summary of the work that should be done before configuring the Web Server:
1. Configure SVN repository in a place with network access from web server, workflow server, and all users who will use the rich-client.
2. Create SVN accounts as follows:
3. Before you start the xProcess Web Server there must be a datasource in the Repository. Use the xProcess Rich Client to create a datasource and:
4. Configure the web server and make sure that users can successfully log in. (detailed on the rest of this page)
In our example we have a shared data source in an SVN repository with this url: http://myserver/svn/projects/jupiter/ds1
We will be installing the servers on a linux box, in a directory /servers/ On a windows machine this might be C:/servers.
We have created SVN login accounts for our servers: web-server/web-server.
The web server requires a Java 6 runtime, and is usually distributed with one. No further downloads are necessary. By default when Tomcat launches it starts to look for a JDK within the Tomcat directory itself.
For further information about the Java runtime, see http://java.sun.com/javase/
The web server provides the participant web client and the scheduler server (a controller for preserving unconfirmed effort).
|repository.url||the url of your xProcess Data Source in SVN repository. In our example this is http://myserver/svn/projects/jupiter/ds1|
|repository.user||account for the web server to access the SVN repository. In our example this is web-server|
|repository.password||password for access to SVN repository. In our example this is web-server|
|local.dir||path to the local root directory where the server will create a local working copy of Data Source, and log files. The default is ../../, the install directory|
|license.path||path to xProcess license. The default is ../../conf/license.lic|
|logging.file.level||logging level for log files. Default is FINEST.|
|logging.console.level||logging level for the server console. Default is FINEST.|
|scheduler.server||whether the web server is to be used as the Scheduler
Server. The default is true.
If set to false another machine in the network should be configured to take this role.
|scheduler.server.cron||a cron expression indicating a time when all projects will be
rescheduled as part of the scheduler server routine. A time just
after midnight is recommended. Default is 0 0 1 * * ?
See http://quartz.sourceforge.net/ for documentation.
|license.manager.users.path||path to the file that defines the users who can access the web client. The default is ../../conf/users.xml See section 3 for details of the format of this file.|
|update.trigger.start||time in milliseconds between server statup and the first SVN update. Recommend is: 60000|
|update.trigger.repeat||time in milliseconds between SVN updates. Recommend is: 60000|
<?xml version="1.0" encoding="UTF-8"?> <xprocess> <datasource url="http://location/of/repository "> <!-- admin --> <role accountname="user1" perspective="admin" /> <!-- participant --> <role accountname="user1" perspective="participant" /> <!-- executive --> <role accountname="user1" perspective="executive" /> </datasource> </xprocess>
If you launch the xProcess Web Server and find you made a mistake in a configuration file, after you correct the mistake:
This will check-out a fresh version of your Datasource.