Anything outside the VirtualHost tags will affect all websites of the apache webserver. Any line starting with a hash '#' is a comment.
Here's the content from the otrs.conf configuration file;


#############################################################################
# --
# added for OTRS (http://otrs.org/)
# $Id: apache2-httpd.include.conf,v 1.18.2.2 2011/03/20 08:37:54 mb Exp $
# --


# activate this if you are using an Oracle database
#SetEnv ORACLE_HOME /path/to/your/oracle/
#SetEnv ORACLE_SID YOUR_SID
#SetEnv NLS_LANG AMERICAN_AMERICA.UTF8
#SetEnv NLS_DATE_FORMAT 'YYYY-MM-DD HH24:MI:SS'


<VirtualHost *:80>

    ServerAdmin admin@mydomain.com
    DocumentRoot "/opt/otrs/var/httpd/htdocs/"
    ServerName support
    ServerAlias support.mydomain.com
    ErrorLog "/var/log/httpd/otrs-error_log"
    CustomLog "/var/log/httpd/otrs-access_log" common

        # agent, admin and customer frontend
        ScriptAlias /otrs/ "/opt/otrs/bin/cgi-bin/"
        Alias /otrs-web/ "/opt/otrs/var/httpd/htdocs/"


        # if mod_perl is used
        <IfModule mod_perl.c>

            # load all otrs modules
            Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl

            # Apache::Reload - Reload Perl Modules when Changed on Disk
            PerlModule Apache2::Reload
            PerlInitHandler Apache2::Reload
            PerlModule Apache2::RequestRec

            # set mod_perl2 options
            <Location /otrs>
        #        ErrorDocument 403 /otrs/customer.pl
                ErrorDocument 403 /otrs/index.pl
                SetHandler  perl-script
                PerlResponseHandler ModPerl::Registry
                Options +ExecCGI
                PerlOptions +ParseHeaders
                PerlOptions +SetupEnv
                Order allow,deny
                Allow from all
            </Location>

        </IfModule>



        # directory settings
        <Directory "/opt/otrs/bin/cgi-bin/">
            AllowOverride None
            Options +ExecCGI -Includes
            Order allow,deny
            Allow from all
        </Directory>
        <Directory "/opt/otrs/var/httpd/htdocs/">
            AllowOverride None
            Order allow,deny
            Allow from all
        </Directory>

        <IfModule mod_headers.c>
            <Directory "/opt/otrs/var/httpd/htdocs/skins/*/*/css-cache">
                <FilesMatch "\.(css|CSS)$">
                    Header set Cache-Control "max-age=2592000 must-revalidate"
                </FilesMatch>
            </Directory>

            <Directory "/opt/otrs/var/httpd/htdocs/js_new/js-cache">
                <FilesMatch "\.(js|JS)$">
                    Header set Cache-Control "max-age=2592000 must-revalidate"
                </FilesMatch>
            </Directory>
        </IfModule>

</VirtualHost>

#############################################################################





On 7 February 2014 16:17, Rory <rclerkin@gmail.com> wrote:
I have done this previously by using Virtual Hosts in the apache configuration.

I set up the apache web server to handle virtual hosts as normal. I then created a separate config file for otrs (otrs.conf) and added this to the httpd.conf using the Include directive of the httpd.conf (Include conf/extra/otrs.conf)

I'll send a follow up mail with the content of the otrs.conf which I used as it may get caught by spam filters and you'd miss out on the little bit of info in this mail.

Kind regards,
Rory Clerkin

On 7 February 2014 15:04, James Carroll <james.carroll@idmworks.com> wrote:
I'd like to install some other things on my OTRS host (namely Nagios and a Maven repository) and am concerned about conflicting ports and services, etc. 

Anyone have any insights or done this before?  Anywhere that I can get more details on how OTRS is configured from a webserver/port perspective so I can avoid conflicts?

Thanks,

--
IDMWORKS
James Carroll
Newark, DE
O: 888-687-0436 x709
C: 302.339.2703
F: 917.591.1525
E: james.carroll@idmworks.com
W: www.idmworks.com
------
The information contained in this email message and any attachment may be privileged, confidential, proprietary or otherwise protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.

---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs