Hi Ike, I have several OTRS installed at same box & database engine every OTRS must be installed with its own folder & tables Carlos _____ De: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] En nombre de Ike Nnabugwu Enviado el: Martes, 15 de Abril de 2008 07:36 p.m. Para: otrs@otrs.org Asunto: [otrs] Two instances of OTRS I am tasked with implementing two instances of otrs on the same box,using the same apache and database.If this questions has been answered,please point me to where I can look it up.If not,I will appreciate some pointers.Thanks.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, Ike Nnabugwu schrieb:

I am tasked with implementing two instances of otrs on the same box,using the same apache and database.If this questions has been answered,please point me to where I can look it up.If not,I will appreciate some pointers.Thanks.

...may I ask what do you intend to achieve with this setting? Anyway, there's no problem in running two or more OTRS in the same apache. But if the two OTRS-instances really should use the same data base then they it's quite likely that something will get screwed up: (1) the two instances have different configuration and probably different system-ids, but run the same db-generic-agents (2) both instances use the same mailacounts, but due to different system-ids instance A will not be able to assign follow-ups for tickets initially created by instance B (if the ticket number contains the system id) (3) if the two instances uses different TicketCounter.logs it may happen that a ticket number will be generated twice, even though the ticket number is unique in the data base this will cause a very ugly error (4) you may install some addon-packages in instance A which are stored in the data base. however, instance B is not updated an will miss some files... If you meant, that the two OTRS instances just use the same DBMS but different data bases, then it's not a problem at all :). regards, Torsten Thau - -- Torsten Thau, Dipl. Inform. c.a.p.e. IT Labs GbR - Annaberger Str. 240 - D-09125 Chemnitz phone: +49 371 5347 623 cell: +49 176 66 680 680 personal pgp-key: 0x93E0A174 fax: +49 371 5347 625 http://www.cape-it.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFICbNrvXo8m5PgoXQRAmLZAJ9ekqEJW8tVChSEihuiTEOSILkHhACdFDET T8pClKXJiByKHJmRCUwic0U= =vKC+ -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, Ike Nnabugwu schrieb:

I am tasked with implementing two instances of otrs on the same box,using the same apache and database.If this questions has been answered,please point me to where I can look it up.If not,I will appreciate some pointers.Thanks.

...may I ask what do you intend to achieve with this setting? Anyway, there's no problem in running two or more OTRS in the same apache. But if the two OTRS-instances really should use the same data base then they it's quite likely that something will get screwed up: (1) the two instances have different configuration and probably different system-ids, but run the same db-generic-agents (2) both instances use the same mailacounts, but due to different system-ids instance A will not be able to assign follow-ups for tickets initially created by instance B (if the ticket number contains the system id) (3) if the two instances uses different TicketCounter.logs it may happen that a ticket number will be generated twice, even though the ticket number is unique in the data base this will cause a very ugly error (4) you may install some addon-packages in instance A which are stored in the data base. however, instance B is not updated an will miss some files... If you meant, that the two OTRS instances just use the same DBMS but different data bases, then it's not a problem at all :). http://faq.otrs.org/otrs/public.pl?Action=PublicFAQ&CategoryID=31&ItemID=289 regards, Torsten Thau - -- Torsten Thau, Dipl. Inform. c.a.p.e. IT Labs GbR - Annaberger Str. 240 - D-09125 Chemnitz phone: +49 371 5347 623 cell: +49 176 66 680 680 personal pgp-key: 0x93E0A174 fax: +49 371 5347 625 http://www.cape-it.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIC0vevXo8m5PgoXQRAjfNAJ9tGc3NbigGp6qCBK+7EyHi5WfhagCdG6f6 AtRiLqTNyeUJuQzeqfSyQGo= =+tmp -----END PGP SIGNATURE-----