Author: sebawagner
Date: Sat May 12 10:56:29 2012
New Revision: 1337509
URL: http://svn.apache.org/viewvc?rev=1337509&view=rev
Log:
Add some not for Axis2 config needed changes for Port settings
Modified:
incubator/openmeetings/trunk/singlewebapp/docs/PortSettings.html
incubator/openmeetings/trunk/singlewebapp/xdocs/PortSettings.xml
Modified: incubator/openmeetings/trunk/singlewebapp/docs/PortSettings.html
URL:
http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/docs/PortSettings.html?rev=1337509&r1=1337508&r2=1337509&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/docs/PortSettings.html (original)
+++ incubator/openmeetings/trunk/singlewebapp/docs/PortSettings.html Sat May 12
10:56:29 2012
@@ -1040,6 +1040,16 @@ limitations under the License.
</td>
</tr>
</table>
+ <p>
+ If you change the HTTP Port (or HTTPS port) and
need the REST/SOAP
+ Gateway you also should modify the file:
+ <br />
+ <tt>/webapps/openmeetings/WEB-INF/conf/axis.xml
</tt>
+ (Around Line 197)
+ <br />
+ You need to restart Red5 Service so that
changes to the Axis2 conf
+ are online.
+ </p>
</blockquote>
</p>
</td></tr>
@@ -1055,14 +1065,17 @@ limitations under the License.
<tr><td>
<blockquote>
<p>A common way of bypassing the firewall
is to change HTTP port to
- 80 and rtmpT to 443. </p>
+ 80 and rtmpT to 443.
+ </p>
<p>A short description about
the connection mechanism: The
application first tries connecting to rtmp 3
times, because rtmp is
the protocol that is less performance hungry.
If that fails the
- application will fallback to rtmpT. </p>
+ application will fallback to rtmpT.
+ </p>
<p>Most firewalls do allow
traffic on port 443 and they normally do
not analyse the packets, because 443 is
normally SSL encrypted, so
- the firewall should not be able to read the
packets at all. </p>
+ the firewall should not be able to read the
packets at all.
+ </p>
</blockquote>
</p>
</td></tr>
@@ -1077,7 +1090,11 @@ limitations under the License.
</td></tr>
<tr><td>
<blockquote>
- <p>You can run OpenMeetings completely
over SSL. See <a href="RTMPSAndHTTPS.html">RTMPSAndHTTPS</a>. </p>
+ <p>
+ You can run OpenMeetings completely over SSL.
See
+ <a href="RTMPSAndHTTPS.html">RTMPSAndHTTPS</a>
+ .
+ </p>
</blockquote>
</p>
</td></tr>
Modified: incubator/openmeetings/trunk/singlewebapp/xdocs/PortSettings.xml
URL:
http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/PortSettings.xml?rev=1337509&r1=1337508&r2=1337509&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/PortSettings.xml (original)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/PortSettings.xml Sat May 12
10:56:29 2012
@@ -73,26 +73,44 @@
</tr>
</table>
+ <p>
+ If you change the HTTP Port (or HTTPS port) and
need the REST/SOAP
+ Gateway you also should modify the file:
+ <br />
+ <tt>/webapps/openmeetings/WEB-INF/conf/axis.xml
</tt>
+ (Around Line 197)
+ <br />
+ You need to restart Red5 Service so that
changes to the Axis2 conf
+ are online.
+ </p>
+
</section>
<section name="Preventing Firewall issues">
<p>A common way of bypassing the firewall is to change
HTTP port to
- 80 and rtmpT to 443. </p>
+ 80 and rtmpT to 443.
+ </p>
<p>A short description about the connection mechanism:
The
application first tries connecting to rtmp 3
times, because rtmp is
the protocol that is less performance hungry.
If that fails the
- application will fallback to rtmpT. </p>
+ application will fallback to rtmpT.
+ </p>
<p>Most firewalls do allow traffic on port 443 and they
normally do
not analyse the packets, because 443 is
normally SSL encrypted, so
- the firewall should not be able to read the
packets at all. </p>
+ the firewall should not be able to read the
packets at all.
+ </p>
</section>
-
+
<section name="OpenMeetings over SSL">
-
- <p>You can run OpenMeetings completely over SSL. See <a
href="RTMPSAndHTTPS.html">RTMPSAndHTTPS</a>. </p>
-
+
+ <p>
+ You can run OpenMeetings completely over SSL.
See
+ <a href="RTMPSAndHTTPS.html">RTMPSAndHTTPS</a>
+ .
+ </p>
+
</section>
</body>
