On Mon, Mar 7, 2011 at 6:43 PM, Afkham Azeez <[email protected]> wrote:

> Folks,
> When we first defined the carbon.xml file, we envisioned that multiple
> ports may be needed for different purposes in the future, and to make it
> easier for the users to see and change ports in a single place, we added the
> Ports element.
>
> e.g.
> <!--
>        Ports used by this server
>     -->
>     <Ports>
>         <!-- The JMX Ports -->
>         <JMX>
>             <!--The port RMI registry is exposed-->
>             <!--<RMIRegistryPort>9999</RMIRegistryPort>-->
>             <!--The port RMI server should be exposed-->
>             <!--<RMIServerPort>11111</RMIServerPort>-->
>         </JMX>
>     </Ports>
>
>
>
> Nuwan, you have added the following lines;
>
> <!-- HTTP and HTTPS ports when apache is fronted to a carbon server-->
>     <!--ApacheHttpPort>80</ApacheHttpPort>
>     <ApacheHttpsPort>443</ApacheHttpsPort-->
>
> why can't you use the proxyPorts parameter in the mgt-transports.xml file
> for this? Nuwan, you have also added the following:
> <!-- In-order to  get the registry http Port from the back-end when the
> default http transport is not the same-->
>     <!--RegistryHttpPort>9763</RegistryHttpPort-->
>

> Why not use the Ports section? Isn't there a better way to do this; for
> example, query the BE and get this port?
>

+1.


> Get it from the BE registry.xml?
>

No, the above is a hack and should not make it to the registry.xml. And, the
registry has no concept of I run on this HTTP port. Its the server that
hosts the servlet on this port.

Thanks,
Senaka.

>
>
>
> AmilaJ you have added the following:
>
> <!--
>        Uncomment following piece of code if you need to use in-built LDAP
> server when running carbon.
>        Following piece of code states which port to be used when running
> in-built LDAP server.
>        If the installed product is not IS, you may need to install in-built
> LDAP as a feature.
>     -->
>     <!--LdapServer>
>         <Transports>
>             <TcpTransport>
>                 <Port>10389</Port>
>             </TcpTransport>
>         </Transports>
>     </LdapServer-->
>
> Why can't this be defined in the Ports section? I think now there is a
> separate LDAP config file right?
>
>
>
>
>
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; 
> **http://www.apache.org/*<http://www.apache.org/>
> *
> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2, Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://www.linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to