OPS 3.0 hasn't been tested with these versions of WebLogic, but you may want to try the following instructions for OPS 2.8.
Installing Orbeon PresentationServer
1. Downloading
Orbeon PresentationServer (OPS) can be downloaded from http://www.orbeon.com/community/downloads.
2. System Requirements
To install OPS you need an application server that runs on Java version 1.4.2 (or later) and implements the Servlet API 2.3 (or later). OPS has been tested on the following application servers:
- Apache Tomcat 5.5.4 (JDK 1.5.0)
- BEA WebLogic Server 9.1 (JRockit)
- IBM WebSphere 6
- JOnAS 4.6.6 (Tomcat 5.5.12, JDK 1.5.0)
- JBoss 4.0
Please contact us if you have questions about support for other application servers or versions.
3. Installing OPS on Apache Tomcat
-
Assuming that
TOMCAT_HOMErepresents the location of your Tomcat installation: create a newTOMCAT_HOME/webapps/opsdirectory. -
Unzip
ops.warin theopsdirectory you just created. -
With Tomcat 5, move
xercesImpl.jarandxmlParserAPIs.jarfromcommon/endorsedtoserver/lib. This way Xerces will be available to Tomcat, but it won't override the version of Xerces and standard XML APIs that comes with OPS. -
You can now start Tomcat, and access
http://localhost:8080/ops/to test your installation (replacinglocalhostand8080with the host name and port number of your Tomcat installation if different from the default), or perform one of the optional installation steps below. -
Optionally, to run the authentication example:
-
Open
TOMCAT_HOME/webapps/ops/WEB-INF/web.xmland uncomment thesecurity-constraint,login-configandsecurity-roledeclarations at the end of the file. -
Open
TOMCAT_HOME/conf/server.xmland uncomment the following declaration:<Realm className="org.apache.catalina.realm.MemoryRealm" /> -
Edit
TOMCAT_HOME/conf/tomcat-users.xmland replace the content of this by with:<tomcat-users> <role rolename="administrator"/> <user username="admin" password="password" roles="administrator"/> </tomcat-users>
-
Open
4. Installing OPS on BEA WebLogic 9.1
-
Select a directory where you want to store your web application. Let's assume the path you chose is
C:/WebApps/ops. -
Unzip
ops.warintoC:/WebApps/ops. There should now be a directory calledWEB-INFunderC:/WebApps/ops. -
Start WebLogic's adminstration console.
-
Use the console to install a new Web application. When prompted to select a WAR file, point to the directory
C:/WebApps/ops. When prompted for a context path, choose a value such asops. Complete the installation and start the web application. -
You should now be able to access the OPS examples by pointing your browser to the address of your WebLogic server followed by the context path you chose, for example:
http://localhost:7001/ops/.
5. Installing OPS on BEA WebLogic 7.0 and 8.1
-
Assume that
DOMAINrepresents your WebLogic domain directory (typicallyc:\bea\user_projects). Create a new directory:DOMAIN\applications\orbeon. -
Unzip
ops.warin theorbeondirectory you just created. -
Edit the
startWeblogic.cmd(inDOMAIN) and changeset STARTMODE=truetoset STARTMODE=false. This starts WebLogic in development mode. In development mode, WebLogic automatically loads and deploys the content of theapplicationdirectory. If you don't want to start the server in development mode, you have to explicitly declare a Web application in theconfig.xml. -
To improve performance on WebLogic (highly recommended!):
-
Start WebLogic (e.g. with
startWebLogic.cmd) -
Make sure you can access the OPS examples with your browser (by going
to
http://localhost:7001/orbeon/) - Stop WebLogic
-
Open the
config.xmlfile in an editor. Look for the<WebAppComponent Name="orbeon">element and add the attribute:ServletReloadCheckSecs="-1". This will prevent WebLogic from checking if a servlet has changed in the application and will make OPS much faster.
-
Start WebLogic (e.g. with
-
Optionally, to run the authentication example:
-
Open
DOMAIN/applications/orbeon/WEB-INF/web.xmland uncomment thesecurity-constraint,login-configandsecurity-roledeclarations at the end of the file. - Go to the WebLogic Console with a browser.
-
Create a new user named
adminwith a password of your choice.
-
Open
-
Once OPS is properly installed, you can start WebLogic as usual with the
startWeblogic.cmdscript (inDOMAIN).
6. Installing OPS on IBM WebSphere 6
-
Launch WebSphere server.
- On Windows go to Control Panel, Administrative Tools, Services. Look for IBM WebSphere Application Server and make sure it is started.
-
On Linux/UNIX, assuming that
WSAS_HOMErepresents the location of your WebSphere installation, runWSAS_HOME/profiles/default/bin/startServer.sh server1.
-
Log in to the administrative console.
- Got to
http://localhost:9060/ibm/console/. - The default administrator login is
admin.
- Got to
-
Install and deploy OPS (
ops.war).- Click on Applications / Install New Application.
-
Select the
ops.warto upload, choose a context path like/ops(from now on we will assume this was your choice). - Hit "next" until you get to the end of the wizard, then hit "finish". You can leave the defaults everywhere while going through the wizard.
- Save the configuration.
- Click on Applications / Enterprise Applications.
- Select
ops_warand click on the "start" button.
-
Run and modify the examples.
- Go to
http://localhost:9080/ops/. -
You can view the log from OPS in
WSAS_HOME/profiles/default/logs/server1/SystemOut.log. -
You can modify the examples resources as the application sever is
running and see the results of your modifications on the fly. The
resources are stored under
WSAS_HOME/profiles/default/installedApps/yourmachineNode01Cell/ orbeon_war.ear/ops.war/WEB-INF/resources. For instance, try to modifyexamples/tutorial/hello1/view.xhtml: replace "Hello World!" by your own message, and reload the page in the browser to see the result.
- Go to
7. Installing OPS on JBoss 4.0
-
Assuming that
JBOSS_HOMErepresents the location of your JBoss installation: create a newJBOSS_HOME/server/default/deploy/ops.wardirectory. -
Unzip
ops.warin theops.wardirectory you just created. -
Edit
JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xmland change the value in<attribute name="UseJBossWebLoader">fromfalsetotrue. -
Start JBoss by running
JBOSS_HOME/bin/run.bat(orrun.shon UNIX). -
Run and modify the examples.
- Go to
http://localhost:8080/ops/ -
You can modify the examples resources as the application sever is
running and see the results of your modifications on the fly. The
resources are stored under
JBOSS_HOME/server/default/deploy/ops.war/WEB-INF/resources.
- Go to
-
Optionally, to run the authentication sample:
-
Open
JBOSS_HOME/server/default/deploy/ops.war/WEB-INF/web.xmland uncomment thesecurity-constraint,login-configandsecurity-roledeclarations at the end of the file. -
Open
JBOSS_HOME/server/default/deploy/ops.war/WEB-INF/jboss-web.xmland uncomment thesecurity-domainelement near the end of bottom of the file. -
Open
JBOSS_HOME/server/default/conf/login-config.xmland add the following aplication policy to the list of policies :<application-policy name="orbeon-demo"> <authentication> <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required"> <module-option name="usersProperties">orbeon-demo-users.properties</module-option> <module-option name="rolesProperties">orbeon-demo-roles.properties</module-option> </login-module> </authentication> </application-policy>
-
Open
8. Security
For security reasons, you might want to run OPS under a Security Manager. Java's Security Manager allows you to control the Java sandbox and which resources the application can access. When installed correctly, the Security Manager can prevent unauthorized code to execute malicious actions, such as deleting files on the server or initializing network connections. For more information, please read the Security in Java 2 SDK 1.2 tutorial and the Security Manager API.
Follow the steps below to install the Security Manager:
- Download the policy file.
-
Append the permissions to the application server
policy file. The table lists the policy file for
the supported servers.
Apache Tomcat catalina.policy BEA Weblogic weblogic.policy IBM WebSphere was.policy Sun ONE server.policy -
Add the following system properties to the server startup script.
- oxf.home: Location of the OPS exploded WAR file
- oxf.resources: Location of OPS resources directory
-
Modify the startup script to enable the security
manager. Add the following system properties:
- -Djava.security.manager
- -Djava.security.policy=="path to the policy file"