[Djigzo users] Multipe Djigzo Instances

Manuel Faux Manuel.Faux at securesolutions.at
Wed Apr 13 13:11:49 CEST 2011


Hi,

Where is the system variable djigzo-web.home used? Is it really necessary to set this variable? Is it possible to set it per Tomcat context?

Kind regards,
Manuel Faux

Hope the Mail can be seen this time. ;)

-----Original Message-----
From: users-bounces at lists.djigzo.com [mailto:users-bounces at lists.djigzo.com] On Behalf Of Martijn Brinkers
Sent: Friday, February 25, 2011 12:46 PM
To: users at lists.djigzo.com
Subject: Re: [Djigzo users] Multipe Djigzo Instances

On 02/25/2011 10:46 AM, Manuel Faux wrote:
> Hi,
>
> I want to run multiple Djigzo instances on one server with one Postfix installation. What I did so far is the following:
>
>
> -          Copied the Djigzo files in one folder for each instance
>
> -          Created one database for each instance
>
> -          Configured each instance to use its database in the hibernate.cfg.xml
>
> -          Configured an individual SOAP port for each instance
>
> -          Deployed the backend for each Djigzo instance (this was a bit tricky, because I had to modify djigzo-web to allow overruling some configuration values via the Tomcat context (feel free to contact me to hand over you the sources) because each instance has to use an own SOAP port)
>
> -          Added the content filter pipe to Postfix's master.cf for each instance
>
> -          Added the inet TCP socket for each instance in master.cf
>
> -          Created one init script for each instance
>
> This setup works so far, but I'm unsure if I've forgotten something or some other things will interfere. I am aware of the fact I cannot use Djigzo-Web to configure Postfix anymore or to view the logs, does anyone see other limitations?

How does Postfix decide which back-end to use? based on sender domain?

You should be able to manage Postfix and see the log files from the Web GUI but each instance modifies the same Postfix config and shows the same log file.

Instead of modifying djigzo-web to use a different soap port you can specify the soap port in the Tomcat context file
(/etc/tomcat6/Catalina/localhost):

<Context docBase="/usr/share/djigzo-web/djigzo.war" unpackWAR="false">
    <Parameter name="djigzo.system.properties"
value="djigzo-web.spring.authenticator.config=spring-default-authenticator.xml
djigzo.ws.server.port=12345"
override="false"/>
</Context>

The <Parameter> setting overrides the <context-param> setting for "djigzo.system.properties" in web.xml. In the above example, the soap port is set to 12345.

> Is there a documented way, how to chroot Djigzo?

Djigzo runs on Java (OpenJDK) so you should chroot the complete OpenJDK runtime. This is probably possible although I'm not sure whether it's worth the effort since Java is very secure (unless you use Web Applets in your browser but no one is using that any more :).

Kind regards,

Martijn

--
Djigzo open source email encryption



More information about the Users mailing list