Setting up the Apache Webserver

Hi,

I have been deploying HTML files to a certain area on the Teamsite server (Solaris) e.g. /tmp/htdocs. I want to be able to request these pages through a http call and be able to view the page in a browser.

So far, all I understand is that I have to make some changes to the port numbers in IWHOME/iw-webd/conf/httpd.conf file and point the document root to e.g./tmp/htdocs. At the moment the document root is pointing to IWHOME/iw-web/htdocs.

Im not entirely sure if I am following the correct procedures to set up the apache webserver. Would appreciate any help.

Thanks
Mashuk

Find more posts tagged with

Comments

Adam Stoller

iw-webd - which is Apache - is exclusively for the use of TeamSite.
You are also supposed to provide and configure your own "customer web server" which may or may not be Apache, but which would definitely be a separate instance from iwwebd. As such you should not muck around too much with the iwwebd configuration files - but instead muck with the customer web server configuration files (note: the customer web server should usually be targeted to listen on port 81 rather than 80 - as 80 is used by iwwebd)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Valentine

hmmm... Not related question, but why not use the "Preview" functionality in TeamSite?

It does preview automatically by using "customer" http server and "iw-mount" to map the files.

ie,

http://<ts server/iw-mount/default/main/ME/WORKAREA/me/htdocs/file.html

wiil preview the file.

Mashuk

So are you saying the default installation does not come with the customer web server installed?

Would the customer web server config files, be part of a separate apache instance then, or are there specific files related to the customer web server within teamsite?

On a separate note, in response to Valentine's message, I am using the Preview functionality within Templating, but what I want to do, is to be able to create a dcr, generate a html page, deploy the content, and then be able to view the content from the end users point of view. i.e Through the webserver, not the teamsite one.

All of which is happening on the same box.

Thanks
Mashuk

Adam Stoller

I suggest you have a good read of the TeamSite Administrator's Guide and/or go through TeamSite Administrator training.

The Customer Web Server is the responsibility of the customer - the Administrator's Guide provides information about the parts of that web server's configuration that need to be done to work with TeamSite on the same box. This is how previewing within TeamSite works - so if that's working for you, I imagine you already have a customer web server configured on your TeamSite box.

If you want to view locally deployed files through yet-another-web server running on the same box - that's an entirely separate web server that needs to be configured (on yet-another-port) - and other than the port, there should be nothing TeamSite-specific about the configurations for it.

What a number of customers do - espcially those using JSPs - is they have a separate "staging" or "qa" server to which they deploy content before deploying it to their production servers - and that server's web-server is configured exactly like the production server - so rather than trying to view the content on the TeamSite box as-if you were going to the production server - you view the content on the "qa" box.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Mashuk

I spoke with a colleague who says a separate apache is already installed on the box.

The httpd.conf is configured to a document root, where I am deploying my files to and it is configured to port 81. I can happily view the HTML files through the webserver now :-)

Thanks for the help

Mashuk