Author: chris.laprun(a)jboss.com Date: 2007-12-07 18:14:23 -0500 (Fri, 07 Dec 2007) New Revision: 9320 Modified: docs/tags/JBoss_Portal_2_6_3/referenceGuide/en/modules/wsrp.xml Log: - Slight update to add mention of host name impact on configuration. - Minor reformat. Modified: docs/tags/JBoss_Portal_2_6_3/referenceGuide/en/modules/wsrp.xml =================================================================== --- docs/tags/JBoss_Portal_2_6_3/referenceGuide/en/modules/wsrp.xml 2007-12-07 23:12:47 UTC (rev 9319) +++ docs/tags/JBoss_Portal_2_6_3/referenceGuide/en/modules/wsrp.xml 2007-12-07 23:14:23 UTC (rev 9320) @@ -84,25 +84,19 @@ <para>If you've obtained the source distribution of JBoss Portal, you need to build and deploy the WSRP service separately. Please follow the instructions on how to install <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/ins... - Portal - from the sources</ulink>. Once this is done, navigate to - <filename>JBOSS_PORTAL_HOME_DIRECTORY/wsrp</filename> - and type: - <command>build deploy</command> - At the end of the build process, - <filename>portal-wsrp.sar</filename> - is copied to + Portal from the sources</ulink>. Once this is done, navigate to + <filename>JBOSS_PORTAL_HOME_DIRECTORY/wsrp</filename> and type: <command>build deploy</command> + At the end of the build process, <filename>portal-wsrp.sar</filename> is copied to <filename>JBOSS_HOME/server/default/deploy</filename>. </para> <sect2 id="wsrp-ports"> - <title>Considerations to use WSRP when running Portal on a non-default port</title> - <para>If you have modified the port number on which Portal runs, you will also need - <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=WSRPChangePorts"&... the port information for - WSRP - </ulink> - as found on<ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossPortal">J... Portal's - wiki</ulink>. + <title>Considerations to use WSRP when running Portal on a non-default port or hostname</title> + <para>If you have modified the port number on which Portal runs or bound your Application Server to a specific + host name, you will also need + <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=WSRPChangePorts"&... the port and/or hostname + information for WSRP</ulink> as found on + <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossPortal">J... Portal's wiki</ulink>. </para> </sect2> @@ -110,8 +104,7 @@ <title>Considerations to use WSRP with SSL</title> <para>It is possible to use WSRP over SSL for secure exchange of data. Please refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=WSRPUseSSL">in... - on - how to do so from + on how to do so from <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossPortal">J... Portal's wiki</ulink>. </para> </sect2> @@ -120,21 +113,13 @@ <sect1> <title>Making a portlet remotable</title> <para>JBoss Portal does <emphasis role="bold">NOT</emphasis>, by default, expose local portlets for consumption by - remote WSRP - consumers. In order to make a portlet remotely available, it must be made "remotable" by adding a - <literal>remotable</literal> - element to the - <filename>jboss-portlet.xml</filename> - deployment descriptor for - that portlet. If a - <filename>jboss-portlet.xml</filename> - file does not exist, one must be added to the - <filename>WEB-INF</filename> - folder of the web application containing the portlet. + remote WSRP consumers. In order to make a portlet remotely available, it must be made "remotable" by adding a + <literal>remotable</literal> element to the <filename>jboss-portlet.xml</filename> deployment descriptor for + that portlet. If a <filename>jboss-portlet.xml</filename> file does not exist, one must be added to the + <filename>WEB-INF</filename> folder of the web application containing the portlet. </para> <para>In the following example, the "BasicPortlet" portlet is specified as being remotable. The - <literal>remotable</literal> - element is optional. + <literal>remotable</literal> element is optional. </para> <example> <programlisting><![CDATA[ @@ -149,13 +134,9 @@ </portlet-app>]]></programlisting> </example> <para> - It is also possible to specify that all the portlets declared within a given - <filename>jboss-portlet.xml</filename> - file have a specific "remotable" status by default. This is done by adding a single - <literal>remotable</literal> - element to the root - <literal>portlet-app</literal> - element. Usually, this feature will be used to remotely expose + It is also possible to specify that all the portlets declared within a given <filename>jboss-portlet.xml</filename> + file have a specific "remotable" status by default. This is done by adding a single <literal>remotable</literal> + element to the root <literal>portlet-app</literal> element. Usually, this feature will be used to remotely expose several portlets without having to specify the status for all the declared portlets. Let's look at an example: </para> <example>