|
|||||
| Chapter 3. Running OpenWFE | |||||
|---|---|---|---|---|---|
| Prev | Next | ||||
Table of Contents
This chapter focuses on getting your freshly downloaded OpenWFE release running. Customization and extensions will be described in further chapters.
OpenWFE's components are server side components
Some problem resolutions. It seems that with 1.4.2 JDKs those trouble vanished. And we've made lots of efforts to make OpenWFE work "out of the box".
I experienced this with the JDK 1.4.1_03 on GNU/Linux : upon logging in as 'alice' or any other user, the system replied with 'User hasn't any rights on any store'.
(same problem with JDK 1.4.1_04 on GNU/Linux...)
I looked at the logs/worklist.log and remarked that the system threw a AccessControlException when trying to access 2 system properties.
The solution is to edit the file $JAVA_HOME/jre/lib/security/java.policy and to add two lines :
permission java.util.PropertyPermission "entityExpansionLimit", "read";
permission java.util.PropertyPermission "disallowDoctypeDecl", "read";
before the final line :
};
The best alternative is ./bin/owfe-suite.sh, it silently starts the OpenWFE suite. On Windows, the start command is owfe-suite.bat. You should be able to double-click this .bat file and the whole OpenWFE suite will start.
You can run owfe-suite.sh from anywhere, it will detect its position. You can override this position by setting the environment variable $OPENWFE_HOME
By default, OpenWFE uses the ISO-8859-1 encoding when generating XML documents (for storing expressions and workitems in the filesystem or for dispatching a workitem to a participant.
The start scripts of a freshly unpacked OpenWFE release include a commented out line for setting the encoding. This line can be found at the beginning of owfe-suite.sh, owfe-suite.bat, ...
If you are using Xlob (for persistence to database), do not forget that the encoding choice has to be compatible with the encoding used by the database.
Make sure that all those scripts are runnable (chmod a+x *.sh) On the windows platform, of course, you have to run the .bat files by double-clicking on them.
When the output of each script has stabilized, you can point your browser towards http://localhost:7080/webclient/