[Mashup-user] Deploying the mashup server a a J2EE webapp ?

Sebastien Mosser mosser at polytech.unice.fr
Wed Jul 16 03:11:10 PDT 2008


hi.

thanks for your answer.

> The mashup server actually is running on it's own Tomcat instance, so 
> you can just setup mod_jk or mod_proxy in front of it as you generally 
> do without any problem. Our own community site at http://mooshup.com is 
> running with mod_proxy in front, so it's a scenario that we use ourselves.

I've got on my server a tomcat running the following conectors :
> mosser at anubis:/opt/tomcat55/conf$ cat server.xml
> ...
> <Connector port="8180"
>            redirectPort="8443"
>            minSpareThreads="25"
>            connectionTimeout="20000"
>            maxSpareThreads="75"
>            maxThreads="150">
> </Connector>
> <Connector port="8009"
>            redirectPort="8443"
>            protocol="AJP/1.3">
> </Connector>
>  ...


And I declare on apache mod_jk configuration the following binding :
> mosser at anubis:/etc/apache2$ cat workers.properties 
> worker.list=geronimo_ajp13
> worker.geronimo_ajp13.port=8009
> worker.geronimo_ajp13.host=localhost
> worker.geronimo_ajp13.type=ajp13
> mosser at anubis:/etc/apache2$ cat conf.d/jk.conf
> <IfModule mod_jk.c>
>     JkWorkersFile /etc/apache2/workers.properties
>     JkLogFile /var/log/apache2/mod_jk.log
>     JkLogLevel error
>     JkMount /compound/* geronimo_ajp13
> </IfModule>

I'm wondering how I can add a new apache connector inside the Mashup 
Server, as the server.xml doesn't looks familiar for me :

> mosser at asmodeus:~/Desktop/wso2/wso2-mashup-server-1.0.2/conf$ cat server.xml 
>  ...
> <Ports>
>         <!--
>         Uncomment this section and provide the correct HTTP port
>         in the case of a generic server installation
>          -->
>         <!--
>         <HTTP>9762</HTTP>
>         -->
>         <!--
>        Uncomment this section and provide the correct HTTPS port
>        in the case of a generic server installation
>          -->
>         <!--
>         <HTTPS>9443</HTTPS>
>         -->
>         <!--
>            The JMX Port
>         -->
>         <JMX>7999</JMX>
>         <!--
>            Port for listening to external commands such as START, STOP, RESTART
>         -->
>         <CommandListener>7666</CommandListener>
>     </Ports>
>  ...

And it mostly looks like WSAS config instead of WSO2 mashup server's one 
:'(.

apparently, ports definition is declared a transportReceiver directly in 
axis2.xml config file ...

> We do not distribute the mashup server as a war file right now, so I'm 
> afraid you will not be able to deploy it in your existing tomcat. Hope 
> this will not be a problem.

Well ... using a mapping through apache to wso2 server is not a problem. 
I'm juste wondering how :). did you publish any tutorials or 
documentation on that topic ?

cheers,


-- 
  Sebastien Mosser
  EPU Polytech'Nice - Sophia Antipolis, Bureau 314
  CNRS / I3S / Rainbow - http://rainbow.i3s.unice.fr/~mosser



More information about the Mashup-user mailing list