Author: thomas.heute(a)jboss.com Date: 2007-09-12 06:17:51 -0400 (Wed, 12 Sep 2007) New Revision: 8239 Modified: docs/trunk/referenceGuide/en/modules/configuration.xml Log: Added email server and proxy configurations Modified: docs/trunk/referenceGuide/en/modules/configuration.xml =================================================================== --- docs/trunk/referenceGuide/en/modules/configuration.xml 2007-09-12 08:36:00 UTC (rev 8238) +++ docs/trunk/referenceGuide/en/modules/configuration.xml 2007-09-12 10:17:51 UTC (rev 8239) @@ -203,8 +203,66 @@ </para> </sect2> </sect1> + <sect1 id="emailConfiguration"> + <title>Setting up the email service</title> + <para>To be able to use the email service (for example to verify user emails when someone subscribes or for CMS + workflow notifications) it has to be configured correctly. To configure it, go to + <literal>jboss-portal.sar/portal-core.sar/META-INF/jboss-service.xml</literal>. + In this file, the mail module is configured like this: + <programlisting><![CDATA[<mbean + code="org.jboss.portal.core.impl.mail.MailModuleImpl" + name="portal:service=Module,type=Mail" + xmbean-dd="" + xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> + <xmbean/> + <depends>jboss:service=Mail</depends> + <depends>portal:service=Module,type=IdentityServiceController</depends> + <attribute name="QueueCapacity">-1</attribute> + <attribute name="Gateway">localhost</attribute> + <attribute name="SmtpUser"></attribute> + <attribute name="SmtpPassword"></attribute> + <attribute name="JavaMailDebugEnabled">false</attribute> + <attribute name="SMTPConnectionTimeout">100000</attribute> + <attribute name="SMTPTimeout">10000</attribute> + <attribute name="JNDIName">java:portal/MailModule</attribute> +</mbean>]]></programlisting> + Here you can specify a different SMTP server than localhost, then precise the Smtp username and Smtp passwords to + use to send the mails.</para> + <para>If i wanted to use GMail smtp server, i would write: + <programlisting><![CDATA[<mbean + code="org.jboss.portal.core.impl.mail.MailModuleImpl" + name="portal:service=Module,type=Mail" + xmbean-dd="" + xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> + <xmbean/> + <depends>jboss:service=Mail</depends> + <depends>portal:service=Module,type=IdentityServiceController</depends> + <attribute name="QueueCapacity">-1</attribute> + <attribute name="Gateway">smtp.gmail.com</attribute> + <attribute name=&quot;SmtpUser&quot;&gt;username(a)gmail.com&lt;/attribute&gt; + <attribute name="SmtpPassword">myPassword</attribute> + <attribute name="JavaMailDebugEnabled">false</attribute> + <attribute name="SMTPConnectionTimeout">100000</attribute> + <attribute name="SMTPTimeout">10000</attribute> + <attribute name="JNDIName">java:portal/MailModule</attribute> +</mbean>]]></programlisting> + </para> + <note><para>If you have a 'standard' setup and a mail server installed + (That's the case on most Linux distribution out of the box), it will work out of the box.</para></note> + </sect1> <sect1> - <title>Disabling dynamic proxy unwrapping</title> + <title>Setting up proxy settings</title> + <para>There are a couple of scenarios where you will need your proxy to be correctly defined at the JVM + level so that you can access documents from Internet. It could be to get the thirdparty libraries if you + decided to build JBoss Portal from the sources, to access RSS feeds or weather information in the samples + portlet we provide or for your own needs.</para> + <para>To set up the proxy settings you will need to know the proxy host and the port to use then + add them when starting java.</para> + <para>Usually setting up JAVA_OPTS environment variable to <literal>-Dhttp.proxyHost=YOUR_PROXY_HOST -Dhttp.proxyPort=YOUR_PROXY_PORT</literal> + is enough.</para> + </sect1> + <sect1> + <title>Disabling dynamic proxy unwrapping</title> <para>JBoss Portal use the JBoss Microkernel for the service infrastructure. The JBoss Microkernel provides injection of services into other services, also known as wiring. Unfortunately it is only possible to inject dynamic proxies that talks to the MBeanServer due to the fact the Microkernel is JMX based. The overhead