multiple OTRS instances - on Apache 2.0 only?

Hi,
I'm using multiple instances of OTRS on my test system and I had the same
problem.
The problem is that Apache and mod_perl keep in memory perl programs to
increase performances.
But, in this way, you can't have two instances because only one Confg.pm
will be loaded by Apache.
So, the solution is to force Apache to read the file each time you connect
to OTRS.
If you read the program

Hi, Pascal Gouttebel wrote:
I'm using multiple instances of OTRS on my test system and I had the same problem.
The problem is that Apache and mod_perl keep in memory perl programs to increase performances. But, in this way, you can't have two instances because only one Confg.pm will be loaded by Apache. So, the solution is to force Apache to read the file each time you connect to OTRS. If you read the program
, you will see at the begining the line use Kernel::Config; The command "use" says that you will use the Kernel/Config.pm which is in memory. Replace this line by : do "/opt/otrs/Kernel/Config.pm"; The command "do" force Apache to reload the file each time. You must enter the complete path. In this way, Apache will reload the good Config.pm and you will have the good informations about databse.
Good idea Pascal! :) A other way would be a second apache on port 8080 and the first apache with mod_proxy (so the first apache is just a proxy to the second one). Also a other way (in case the second is just a test setup) to use plain cgi (without mod_perl). This is slower but then you have an working second setup.
Pascal Gouttebel - EPT Luxembourg Pascal_Gouttebel at ept.lu
Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!

Martin Edenhofer wrote:
Replace this line by : do "/opt/otrs/Kernel/Config.pm"; The command "do" force Apache to reload the file each time. You must enter the complete path. In this way, Apache will reload the good Config.pm and you will have the good informations about databse.
A other way would be a second apache on port 8080 and the first apache with mod_proxy (so the first apache is just a proxy to the second one).
Also a other way (in case the second is just a test setup) to use plain cgi (without mod_perl). This is slower but then you have an working second setup.
OK, thanks for suggestions. In a meantime I realised that I don't really need two (or more) instances of OTRS - I just need one admin backend, and many customer backends (with different themes, logos etc.), which I think can be easily achieved. Tomek ---------------------------------------------------------------------- Startuj z INTERIA.PL!!! >>> http://link.interia.pl/f1837
participants (3)
-
Martin Edenhofer
-
Pascal Gouttebel
-
Tomasz Chmielewski