I'm using the mod_jk2 approach together with Rewrite, and that works just great for all virtualhosts, and other tomcat-apps etc, very easy to add new stuff. I have had problems with mod_proxy earlier, but I never had any problems with mod_jk2

Cheers,
Tomas

This is my virtualhost setting for www.primekey.se.

<VirtualHost www.primekey.se:80>
  # We must disable default charset or everything will be ISO-8859-1,
  # but Magnolia sends everything on UFT-8 so...
  AddDefaultCharset off
  ServerAdmin [EMAIL PROTECTED]
  #DocumentRoot /var/www/primekey.se
  ServerName www.primekey.se
  ServerAlias primekey.se
  RewriteEngine on
  RewriteLogLevel 5
  RewriteLog "/var/log/apache2/rewrite.log"
  RewriteRule ^/$ /primekey/en.html [R]
  <Location "/primekey">
    JkUriSet worker ajp13:localhost:8010
  </Location>
  <Location "/docroot">
    JkUriSet worker ajp13:localhost:8010
  </Location>
</VirtualHost>


Claudio Greuter wrote:
Hi there.

I have set up magnolia to run on tomcat port 81 of my server.
As there are other web sites hosted by an Apache server on the same site, I 
wanted to set it up using named virtual hosts.

I followed the instructions here to set up tomcat to have useful URLs
http://www.magnolia.info/wiki/Wiki.jsp?page=RunningMagnoliaInTheRootOfAHost


After that I tried:
http://www.magnolia.info/wiki/Wiki.jsp?page=UseMagnoliaWithApache2.0

It did not work as expected and I stripped the XML a bit, until it worked to 
redirect it to other sites.  The virtual host now looks as follows:

<VirtualHost *:80>
Servername 192.168.26.128

Proxypass / http://192.168.26.128:81/

</VirtualHost>

This does not work when I direct to the Tomcat address and port. The error I receive in 
the browser is "Bad Gateway   The proxy server received an invalid response from an 
upstream server."

In the Log file of apache it tells me that the permission was denied on 
192.168.26.128:81

However when I change the proxypass top redirect to www.sbb.ch/ it redirects 
fine.


My first quess was that tomcat is not listening, so I opened 
http://192.168.26.128:81 in a browser and voila the site appears (however it 
does not work when I type the address without http:// ).


Does anyone know what is wrong here? I do not have enough experience with 
apache.

Thanks and regards

Claudio


***********************************************
IPH Informatik AG
Herr Claudio Greuter
Lagerhausstrasse 9
8400 Winterthur
Tel: +41 (052) 233 94 72
Fax: +41 (052) 233 94 71
[EMAIL PROTECTED]
***********************************************

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 24. Mai 2006 16:37
To: [email protected]
Subject: Re: [magnolia-user] Content Migration V2 -> V3

Hi,

thanks all for your answers! As far as I understood the problem, the solution is: a) convert with xsl (is there a schema?, which nodes change?), writing a converter b) only new projects with 3.x (the situation I have with the one I am working with)
c) buy the migration license.


Dear Ralf,

where is the shop? And will it be opened? I need the € - Price and a I will need a invoice with tax declaration for the german tax.

Hartmut


Am 24.05.2006 um 15:33 schrieb Ralf Hirning:

As was discussed here, there will be changes in the content structure when
going from Magnolia 2.x to Magnolia 3.x.

If you have the Enterprise Edition of Magnolia you will have a tool
"Packaging for Magnolia" which supports typical tasks in a productive
environment:

* Create and download a package of any resources used in a Magnolia
environment. This can be any repository content or files of the web
application
* Upload the package to a Magnolia instance
* Install the package
* Uninstall a package
* Backup any resources in your Magnolia environment

Typical use-cases are:
* Deploy templates (including configuration) to test / productive
environment
* Deploy template changes (change requests)
* Deploy content changes
* Backup content and configuration of production environment
* Share results within a development team

We will provide a special migration license (cost: $50) with which you can create a package on Magnolia 2.x and install the package in Magnolia 3.x.
The content will be migrated on the fly.

Ralf


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------



----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
 ----------------------------------------------------------------for list 
details 
seehttp://www.magnolia.info/en/magnolia/developer.html----------------------------------------------------------------

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to