Starting the Application
In Windows, use the shortcuts in the Start button menu to start an Application Server or mediation server, and (after the Application Server has a few minutes to start) the application itself.
Start UNIX applications after logging out, and logging back in either from the installed icon on the desktop, or from a command line. You must log out and re-log in after installation for desktop icons to function in Solaris.
Since disabling legacy web services enhances performance, they are disabled by default. To enable them, add the following line to $OWARE_USER_ROOT/owareapps/installprops/lib/installed.properties:
If you are not using legacy web services, disabling them enhances performance.
The following command lines all assume you run . /etc/.dsienv before running them, to set the environment correctly. The commands:
You can not run a mediation server and an Application Server on the same host. If no separate mediation servers are detected, the Application Server will act as a mediation server.
You must log out and back in for common desktop menu items to function. To support NIS, the menu configuration for the Common Desktop do not have any explicit paths to the installation directory. The menu actions rely on environment variables that will not exist for the desktop environment until the user logs out and back in after installing the product.
If a mediation server fails to start up with an
ENetworkFailure, delete all files in the oware\temp
directory manually to successfully start the mediation server.
If either application server or mediation server fails to start, particularly after an interruption in service, like a power failure, delete this directory’s contents: oware\jboss*\server\oware\data