OpsProjectWebservicesInstall

Introduction

OPS Project is the core of Open Project Services, it offers access to WebDav and ldap through webservices and can archive .ics files. The webservices are called by other parts of OPS: the mailclient and timesheet client plugins, OPS admin and the openoffice add-ons.

Requirements

Before you can deploy OPS Project, you will need the following peripherals in place:

• OpenLDAP server with a back-hdb backend and with OPS schema's (conf/ops.schema) and settings
• Jakarta Tomcat (we have not tested other servers)
• IMAP mail server (for ops shared mail, we have tested on Courier IMAP)
• The OpsEmail IMAP Proxy (see OpsEmailImapProxy)
• WebDAV (for storing the .ics timesheet files, see WebDavInstallation)

Get and install OPS Project Webservices

You can find all ops downloads, including ops_project, on the ops Source Forge homepage: http://sourceforge.net/projects/ops/. You can choose either to use a stable release, available as a compressed folder, or to deploy the newest version off the sourceforge svn (subversion repository). Before actually deploying the application, you will then have to configure it to work with your IMAP, LDAP and webDAV server, by updating the settings files in /WEB-INF/opsproject.properties in the project directory.

To deploy OPS Project webservices:

1. Assert that all Requirements are met
2. Get ops_project, either a stable release or deploy the newest version off the sourceforge svn (subversion repository). Choose:
   • stable release: go to project homepage>Download>Server components and download the newest ops-projectserver-webservices .war
   • latest & greatest: run svn checkout https://ops.svn.sourceforge.net/svnroot/ops/server/ops_project/trunk/ . to build in the current directory
3. Follow the instructions in deploy.txt (this file is inside the project folder)

You can test if the deployment went succesfull by surfing to "http://[Ops server address]:8080/ops_project/services/OpsProject?wsdl". This should display an XML overview of the webservices.

-- IvanaCace - 19 Jan 2009

Adding a certificate to Java

We need to put the Certifiacte Authority's certificate (cacert) in the Java trusted keystore so it will be accepted when connecting from Java to LDAP. The following line will import a certificate to your Java trusted keystore(Note that you need to create/locate your own certificate and adjust the command so it fits your installations directories)

<java home dir>/bin/keytool -keystore <java home dir>/jre/lib/security/cacerts 
     -import -file <certificate location>/<cerificate name> -alias <certificate alias>

Note: This is a 1 line command.

Additionally we need to import the SSL-certificate from the OPS IMAP proxy, so the webservices can connect connect to the IMAP server. This can be done using the same command. Use "-file ops_client.cer" instead of the CA certificate, also specify a different alias.

This diagram shows how the certificates are used.

Upgrading

When upgrading please remember to backup the configuration of the webservices (and possibly the logging) before you undeploy the webapp. The backed-up files can be used in the new version of the webservices after deployment. It is possible that a new version of the webservices has more options to configure, so check the new versions first.

-- BastiaanGrutters - 14 Oct 2005