/usr/share/doc/red5/html/tomcat-deployment.html is in red5-doc 1.0~svn4374-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 | <html><head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 11. Deploying Red5 To Tomcat</title><link rel="stylesheet" type="text/css" href="html.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Red5 - Reference Documentation"><link rel="up" href="core-components.html" title="Part II. Red5 Core Components"><link rel="prev" href="logging-setup.html" title="Chapter 10. Logging Setup"><link rel="next" href="stream-paths.html" title="Chapter 12. Customize Stream Paths"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div xmlns="http://www.w3.org/TR/xhtml1/transitional" style="background-color:white;border:none;height:73px;border:1px solid black;"><a style="border:none;" href="http://osflash.org/red5" title="Red5 Open Source Flash Server"><img style="border:none;" src="images/red5-banner.png"></img></a><a style="border:none;" href="http://osflash.org/red5" title="Red5 Open Source Flash Server"><img style="border:none;position:absolute;padding-top:5px;right:42px;" src="images/red5-banner-logo.png"></img></a></div><div class="chapter"><div class="titlepage"><div><div><h2 class="title"><a name="tomcat-deployment"></a>Chapter 11. Deploying Red5 To Tomcat</h2></div></div></div>
<div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d5e1640"></a>11.1. Preface</h2></div></div></div>
<p>This document describes how to deploy Red5 to Tomcat as web application
archive (WAR). The standard Red5 deployment consists of a standalone Java
application with an embedded J2EE container (Jetty or Tomcat) running as a
system service, whereas the WAR version runs inside of a J2EE container.</p>
</div>
<div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d5e1643"></a>11.2. Deployment</h2></div></div></div>
<p>The Tomcat war deployer scans the webapps directory for wars periodically.
When a war is found that has not yet been deployed, the deployer will expand
the war file into a directory based on the filename of the war. A war named
myapp.war would be expanded into a directory named myapp; depending upon
your installation the full path would look similar to this C:\Tomcat-
6.0.14\webapps\myapp. </p>
<p>Red5 server is packaged into a file named ROOT.war, this filename has a
special connotation on most J2EE application servers and is normally the default
or root web context. The root web context is responsible for servicing requests
which do not contain a path component. A url with a path component looks like
<a class="ulink" href="http://www.example.com/myapp" target="_top">http://www.example.com/myapp</a> wheres root web application url would resemble
this
<a class="ulink" href="http://www.example.com/" target="_top">http://www.example.com/</a>. An additional configuration file the context
descriptor, is located in the META-INF directory for each web context.
Applications that are not accessed via HTTP, do not require a web / servlet
context. The root war file contains nearly everything that is in a standalone server
build except for embedded server classes and select configuration files.
</p>
</div>
<div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d5e1649"></a>11.3. Context descriptors</h2></div></div></div>
<p>A Context XML descriptor is a fragment of XML data which contains a valid
Context element which would normally be found in the main Tomcat server
configuration file (conf/server.xml). For a given host, the Context descriptors are
located in $CATALINA_HOME/conf/[enginename]/[hostname]/. Note that while
the name of the file is not tied to the webapp name, when the deployer creates
descriptors from the context.xml files contained in the war; their names will match
the web application name. </p>
<p>Context descriptors allow defining all aspects and configuration parameters of a
context, such as naming resources and session manager configuration. It should
be noted that the docBase specified in the Context element can refer to either the
.WAR or the directory which will be created when the .WAR is expanded or the
.WAR itself. </p>
</div>
<div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d5e1653"></a>11.4. Red5 Configuration</h2></div></div></div>
<p>Configuration of the Red5 server consists of a few context parameters in the
web.xml, a default context file, a bean ref file, and a Spring web context file for
each application that will utilize Red5 features. Web applications that use only
AMF to communicate with Red5 do not require a configuration entry in the servers application context. The application context which is managed via Spring
is only available to applications that are contained within the root war; due to the
way that the web application classloaders work. In addition, Red5 uses a context
counterpart called a Scope which serves as a container for the context, handler,
server core instance, and a few other objects. A scope is similar to the
application model in FMS.
The initial entry point or startup servlet for Red5 is the WarLoaderServlet and it is
configured as a servlet listener in the web.xml as shown below. Functionally this
servlet takes the place of the Standalone class in a standard Red5 server</p>
<pre class="programlisting">
<listener>
<listener-class>org.red5.server.war.WarLoaderServlet</listener-class>
</listener>
</pre>
<p>This listener is responsible for starting and stopping Red5 upon receipt of context
initialized and context destroyed container events. The war loader is similar in
function to the Spring ContextLoaderListener servlet but is specialized for Red5.</p>
<div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="d5e1658"></a>11.4.1. Spring contexts</h3></div></div></div>
<p>There are two types of contexts used by Red5, "default" and "web"; there may be
only one default context but any number of web contexts. </p>
</div>
<div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="d5e1661"></a>11.4.2. Default context</h3></div></div></div>
<p>The default context is synonymous with the global application context and is
responsible for providing objects and resources at the top or global level. Spring
beans in this level are configured via the defaultContext.xml and
beanRefContext.xml which are located in the ROOT classes directory (ex.
C:\Tomcat-6.0.14\webapps\ROOT\WEB-INF\classes). The bean ref file defines
the default.context bean which as an instance of
org.springframework.context.support.ClassPathXmlApplicationContext. Two
other configuration files red5-common.xml and red5-core.xml are used to
construct the default context; these files are derived from the standalone
configuration files of the same names, the primary difference is that the server
embedding sections have been removed. </p>
<p>The default context is referenced in the web.xml via the parentContextKey
parameter: </p>
<pre class="programlisting">
<context-param>
<param-name>parentContextKey</param-name>
<param-value>default.context</param-value>
</context-param>
</pre>
<p>This parameter is used by the ContextLoader to locate the parent context, which
in turn allows the global resources to be located. The context loader is used by
the WarLoaderServlet to initialize the web contexts. </p>
<p>The scope counterpart to the global context is the global scope and it is
referenced in the web.xml via the globalScope parameter: </p>
<pre class="programlisting">
<context-param>
<param-name>globalScope</param-name>
<param-value>default</param-value>
</context-param>
</pre>
</div>
<div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="d5e1669"></a>11.4.3. Web context</h3></div></div></div>
<p>Web context definitions are specified in Spring configuration files suffixed with
-web.xml; If your application is named oflaDemo then its configuration file would
be named oflaDemo-web.xml. The Spring web context files should not be
confused with J2EE context descriptors as they are only used for red5 web
contexts and the later are used by Tomcat. Each web context must have a
corresponding configuration file, the configuration files are specified using an ant-
style parameter in the web.xml as shown below. </p>
<pre class="programlisting">
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>WEB-INF/classes/*-web.xml</param-value>
</context-param>
</pre>
<p>Context configuration files specify the resources that are used to notify the
application about joining / leaving clients and provide the methods that
a client can call. Additionally, the configuration files specify the scope hierarchy
for these classes. </p>
<p>Every context configuration must contain a minimum of three entries - a context,
scope, and handler. The only exception to this rule is the root web application
since it does not have a handler application, in this case the global handler is
used. </p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>
<span class="bold"><strong>Context</strong></span> - Each context must have a unique name assigned since all the
</p>
</li></ul></div>
<p>contexts exist within a single Spring application context. The root web
context is named web.context, additional contexts suffix this base name
with their web application name; for example oflaDemo would be named
web.context.oflaDemo. A context is specified in the web context file as
shown below. </p>
<pre class="programlisting">
<bean id="web.context" class="org.red5.server.Context">
<property name="scopeResolver" ref="red5.scopeResolver" />
<property name="clientRegistry" ref="global.clientRegistry" />
<property name="serviceInvoker" ref="global.serviceInvoker" />
<property name="mappingStrategy" ref="global.mappingStrategy" />
</bean>
</pre>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>
<span class="bold"><strong>Scope</strong></span> - Every application needs at least one scope that links the handler
</p>
</li></ul></div>
<p>to the context and the server. The scopes can be used to build a tree
where clients can connect to every node and share objects inside this
scope (like shared objects or live streams). You can consider the scopes
as rooms or instances.
The root scope has the name web.scope, additional scope names should
follow the naming convention specified for contexts. A scope for oflaDemo
would be named web.scope.oflaDemo so that it will not conflict with other
contexts. </p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>A scope bean has the following properties: </p>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>server - This references the server red5.server </p>
</li><li class="listitem">
<p>parent - The parent for this scope is normally global.scope </p>
</li><li class="listitem">
<p>context - Context for this scope, use the web.context for root and </p>
</li></ol></div>
</li></ul></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>web.context.oflaDemo for oflaDemo </p>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>handler - Handler for this scope, which is similar to a main.asc in </p>
</li></ol></div>
</li></ul></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>FMS. </p>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>contextPath - The path to use when connecting to this scope. </p>
</li><li class="listitem">
<p>virtualHosts - A comma separated list of host names or IP addresses this scope listens on. In the war version we do not control the host names, this is accomplished by Tomcat.</p>
</li></ol></div>
</li></ul></div>
<p>The root scope definition looks like this: </p>
<pre class="programlisting">
<bean id="web.scope" class="org.red5.server.WebScope" init-method="register">
<property name="server" ref="red5.server" />
<property name="parent" ref="global.scope" />
<property name="context" ref="web.context" />
<property name="handler" ref="global.handler" />
<property name="contextPath" value="/" />
<property name="virtualHosts" value="*,localhost, localhost:8080" />
</bean>
</pre>
<p>The contextPath is similar to the docBase in the J2EE context file for each
web application. Where the docBase is used to locate resources by HTTP,
the contextPath is use to find resources via RTMP. Your applications may
add additional elements after the configured path to dynamically create
extra scopes. The dynamically created scopes all use the same handler
but have their own properties, shared objects and live streams. </p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>
<span class="bold"><strong>Handler</strong></span> - Every context needs a handler to provide the methods called by
</p>
</li></ul></div>
<p>connecting clients. All handlers are required to implement
org.red5.server.api.IScopeHandler, however you may implement
additional interfaces for controlling access to shared objects or streams. A
sample implementation is provided with Red5 that may be used as your
base class: org.red5.server.adapter.ApplicationAdapter. Please refer to
the javadoc for this class for additional details.
As an example the scope handler for the oflaDemo is shown: </p>
<pre class="programlisting">
<bean id="web.handler.oflaDemo"
class="org.red5.server.webapp.oflaDemo.Application"/>
</pre>
<p>The id attribute is referenced by the oflaDemo scope definition: </p>
<pre class="programlisting">
<bean id="web.scope.oflaDemo" class="org.red5.server.WebScope" init-
method="register">
<property name="server" ref="red5.server" />
<property name="parent" ref="global.scope" />
<property name="context" ref="web.context.oflaDemo" />
<property name="handler" ref="web.handler.oflaDemo" />
<property name="contextPath" value="/oflaDemo" />
<property name="virtualHosts" value="*,localhost, localhost:8080" />
</bean>
</pre>
<p>If you don't need any special server-side logic, you can use the default
application handler provided by Red5: </p>
<pre class="programlisting">
<bean id="web.handler" class="org.red5.server.adapter.ApplicationAdapter" />
</pre>
</div>
<div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="DeployingRed5ToTomcatExternalapplications"></a>11.4.4. External applications</h3></div></div></div>
<p>An external application refers to a web application that accesses Red5 outside of
the ROOT web application. Whether these applications exist within the same
JVM instance or not, they may only access Red5 via RTMP or the AMF tunnel
servlet. The tunnel servlet is configured in the web.xml for each application that
requires AMF communication with Red5, an example is shown below: </p>
<pre class="programlisting">
<servlet>
<servlet-name>gateway</servlet-name>
<servlet-class>org.red5.server.net.servlet.AMFTunnelServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>gateway</servlet-name>
<url-pattern></servlet-mapping>
</servlet-mapping>
</pre>
<p>The tunnel servlet class must be on the classpath of the application under which
it is executed. In addition to the tunnel servlet the
org.red5.server.net.servlet.ServletUtils class is required along with the following
library jars: </p>
<div class="literallayout"><p><br>
commons-codec-1.3.jar <br>
commons-httpclient-3.0.1.jar <br>
commons-logging-1.1.jar <br>
log4j-1.2.14.jar <br>
mina-core-1.1.2.jar <br>
</p></div>
<p>These jars should be placed in the WEB-INF/lib directory of your application. ex. </p>
<div class="literallayout"><p><br>
C:\Tomcat-6.0.14\webapps\myapp\WEB-INF\lib<br>
</p></div>
</div>
</div>
<div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d5e1731"></a>11.5. Creating and deploying your application</h2></div></div></div>
<p>In the following section, two applications will be covered. The first will be a web
application that communicates with Red5 via AMF or RTMP and has its own
handler, referred to as "RemoteApp". The second will consist an SWF that
communicates with Red5 via RTMP, this application will be called "LocalApp".
Any IDE may be used to create these applications as long as it supports Java;
the Eclipse IDE is suggested. SWF files outlined in the examples were created
using AS3 in Flex. </p>
<div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="d5e1734"></a>11.5.1. Remote application</h3></div></div></div>
<p>This example will provide you with the minimum amount of configuration needed
for a remote Red5 application. The following resources will be created: </p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>J2EE web application </p>
</li><li class="listitem">
<p>Client SWF </p>
</li><li class="listitem">
<p>Red5 handler class </p>
</li><li class="listitem">
<p>Spring web context </p>
</li></ul></div>
<p>
<span class="bold"><strong>Steps</strong></span>
</p>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>Create a web application named RemoteApp in your IDE. </p>
</li><li class="listitem">
<p>Obtain a red5.jar, which may be downloaded from
<a class="ulink" href="http://red5.googlecode.com/files/red5.jar" target="_top">http://red5.googlecode.com/files/red5.jar</a> or built from source with the command "ant jar". This library is needed if you extend the ApplicationAdapter for your scope handler.
</p>
</li><li class="listitem">
<p>Obtain the red5-remoting.jar, this may be accomplished by building yourself from the command line with "ant remotejar" or by downloading it from
<a class="ulink" href="http://red5.googlecode.com/files/red5-remoting.jar" target="_top">http://red5.googlecode.com/files/red5-remoting.jar</a>. This library provides the AMF tunnel servlet.
</p>
</li><li class="listitem">
<p>Place the library jars in your project library directory and add them to your build classpath. </p>
</li><li class="listitem">
<p>Compile the Java and Flex source. </p>
</li><li class="listitem">
<p>Create a directory named RemoteApp in the Tomcat webapps directory. ex. C:\Tomcat-6.0.14\webapps\RemoteApp </p>
</li><li class="listitem">
<p>Copy the contents of the web directory to the RemoteApp directory. </p>
</li><li class="listitem">
<p>From the bin directory copy the RemoteApp.swf to the webapps\RemoteApp directory. </p>
</li><li class="listitem">
<p>Copy the lib directory and its contents to the WEB-INF, excluding the red5.jar file. </p>
</li><li class="listitem">
<p>Copy the whole example directory and the RemoteApp-web.xml file from the bin directory to the classes directory under ROOT. ex. C:\Tomcat- 6.0.14\webapps\ROOT\WEB-INF\classes </p>
</li><li class="listitem">
<p>Restart tomcat </p>
</li><li class="listitem">
<p>Open your browser and go to:
<a class="ulink" href="http://localhost:8080/RemoteApp/RemoteApp.html" target="_top">http://localhost:8080/RemoteApp/RemoteApp.html</a>
</p>
</li><li class="listitem">
<p>Click on the RTMP or HTTP connect buttons. For a successful test you should see a server response of "Hello World". </p>
</li></ol></div>
</div>
<div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="d5e1778"></a>11.5.2. Local application</h3></div></div></div>
<p>A simple application that resides entirely within the ROOT web application. This
example consists of a Spring web context, handler class, and a client SWF. </p>
<p>
<span class="italic">'Steps '</span>
</p>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>Create a web application named LocalApp in your IDE. </p>
</li><li class="listitem">
<p>Obtain a red5.jar, which may be downloaded from
<a class="ulink" href="http://red5.googlecode.com/files/red5.jar" target="_top">http://red5.googlecode.com/files/red5.jar</a> or built from source with the command "ant jar". This library is needed if you extend the ApplicationAdapter for your scope handler.
</p>
</li><li class="listitem">
<p>Place the library jar in your project library directory and add it to your build classpath. </p>
</li><li class="listitem">
<p>Compile the Java and Flex source. </p>
</li><li class="listitem">
<p>Copy the LocalApp.html and LocalApp.swf from the bin directory to the ROOT directory. ex. C:\Tomcat-6.0.14\webapps\ROOT </p>
</li><li class="listitem">
<p>Copy the whole example directory and the LocalApp-web.xml file from the bin directory to the classes directory under ROOT. ex. C:\Tomcat- 6.0.14\webapps\ROOT\WEB-INF\classes </p>
</li><li class="listitem">
<p>Restart tomcat </p>
</li><li class="listitem">
<p>Open your browser and go to:
<a class="ulink" href="http://localhost:8080/LocalApp.html" target="_top">http://localhost:8080/LocalApp.html</a>
</p>
</li><li class="listitem">
<p>Click on the connect button. For a successful test you should see a server response of "Hello World". </p>
</li></ol></div>
</div>
<div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="d5e1804"></a>11.5.3. Example Source</h3></div></div></div>
<p>The example application source is available in Subversion at
<a class="ulink" href="https://red5.googlecode.com/svn/java/example/trunk/" target="_top">https://red5.googlecode.com/svn/java/example/trunk/</a>
</p>
</div>
</div>
<div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d5e1808"></a>11.6. Additional web configuration</h2></div></div></div>
<p>
<span class="bold"><strong>Log4j</strong></span> - The path to the logging configuration file and the Spring logging startup
servlet are shown below. These entries should precede the war loader servlet
entry so that logging is initialized prior to Red5 startup.
</p>
<pre class="programlisting">
<context-param>
<param-name>log4jConfigLocation</param-name>
<param-value>/WEB-INF/log4j.properties</param-value>
</context-param>
<listener>
<listener-class>org.springframework.web.util.Log4jConfigListener</listener-class>
</listener>
</pre>
<p>
<span class="bold"><strong>AMF gateway</strong></span> - This servlet provides communication with server applications
using AMF.
</p>
<pre class="programlisting">
<servlet>
<servlet-name>gateway</servlet-name>
<servlet-class>org.red5.server.net.servlet.AMFGatewayServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>gateway</servlet-name>
<url-pattern>/gateway</url-pattern>
</servlet-mapping>
</pre>
<p>
<span class="bold"><strong>RTMPT</strong></span> - This servlet implements an RTMP tunnel via HTTP, this is normally
used to bypass firewall issues.
</p>
<pre class="programlisting">
<servlet>
<servlet-name>rtmpt</servlet-name>
<servlet-class>org.red5.server.net.rtmpt.RTMPTServlet</servlet-class>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>rtmpt</servlet-name>
<url-pattern>/open/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>rtmpt</servlet-name>
<url-pattern>/idle/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>rtmpt</servlet-name>
<url-pattern>/send/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>rtmpt</servlet-name>
<url-pattern>/close/*</url-pattern>
</servlet-mapping>
</pre>
<p>
<span class="bold"><strong>Security</strong></span> - The following entries are used to prevent retrieval of sensitive
information.
</p>
<pre class="programlisting">
<security-constraint>
<web-resource-collection>
<web-resource-name>Forbidden</web-resource-name>
<url-pattern>/WEB-INF/*</url-pattern>
</web-resource-collection>
<auth-constraint />
</security-constraint>
<security-constraint>
<web-resource-collection>
<web-resource-name>Forbidden</web-resource-name>
<url-pattern>/persistence/*</url-pattern>
</web-resource-collection>
<auth-constraint />
</security-constraint>
<security-constraint>
<web-resource-collection>
<web-resource-name>Forbidden</web-resource-name>
<url-pattern>/streams/*</url-pattern>
</web-resource-collection>
<auth-constraint />
</security-constraint>
</pre>
</div>
<div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d5e1822"></a>11.7. Troubleshooting</h2></div></div></div>
<p>If you have problems with deployment or if your application does not start, follow
these steps prior to posting a bug. Directory examples use a typical windows
based path structure. </p>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>Stop the Tomcat server </p>
</li><li class="listitem">
<p>Locate your Tomcat installation directory </p>
</li></ol></div>
<div class="literallayout"><p><br>
C:\Program Files\Apache\Tomcat <br>
</p></div>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>Delete the "work" directory </p>
</li></ol></div>
<div class="literallayout"><p><br>
C:\Program Files\Apache\Tomcat\work <br>
</p></div>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>Delete the "Catalina" directory from the "conf" directory </p>
</li></ol></div>
<div class="literallayout"><p><br>
C:\Program Files\Apache\Tomcat\conf\Catalina <br>
</p></div>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>Delete the expanded war directories, if they exist </p>
</li></ol></div>
<div class="literallayout"><p><br>
C:\Program Files\Apache\Tomcat\webapps\ROOT <br>
C:\Program Files\Apache\Tomcat\webapps\echo <br>
C:\Program Files\Apache\Tomcat\webapps\SOSample <br>
</p></div>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>Ensure your WAR files are in the webapps directory </p>
</li></ol></div>
<div class="literallayout"><p><br>
C:\Program Files\Apache\Tomcat\webapps\ROOT.war <br>
C:\Program Files\Apache\Tomcat\webapps\echo.war <br>
C:\Program Files\Apache\Tomcat\webapps\SOSample.war <br>
</p></div>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>Restart Tomcat </p>
</li></ol></div>
<p>If you still experience problems, gather the following information and post an
issue on Trac after you do a quick search to see if others have experienced the
same problem. </p>
<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<p>Java version </p>
</li><li class="listitem">
<p>Tomcat version </p>
</li><li class="listitem">
<p>Operating system </p>
</li><li class="listitem">
<p>Red5 version (0.8, Trunk, Revision 2283, etc...)</p>
</li></ol></div>
</div>
<div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d5e1860"></a>11.8. Definitions</h2></div></div></div>
<p> AMF:: </p>
<div class="blockquote"><blockquote class="blockquote">
<p> A binary format based loosely on the Simple Object Access Protocol (SOAP). It is used primarily to exchange data between an Adobe Flash application and a database, using a Remote Procedure Call. Each AMF message contains a body which holds the error or response, which will be expressed as an ActionScript Object. </p>
</blockquote></div>
<p> Ant:: </p>
<div class="blockquote"><blockquote class="blockquote">
<p> Software tool for automating software build processes. It is similar to make but is written in the Java language, requires the Java platform, and is best suited to building Java projects. </p>
</blockquote></div>
<p> AS3:: </p>
<div class="blockquote"><blockquote class="blockquote">
<p> A scripting language based on ECMAScript, used primarily for the development of websites and software using the Adobe Flash Player platform. </p>
</blockquote></div>
<p> Flex::</p>
<div class="blockquote"><blockquote class="blockquote">
<p> Software development kit and an IDE for a group of technologies initially released in March of 2004 by Macromedia to support the development and deployment of cross platform, rich Internet applications based on their proprietary Macromedia Flash platform. </p>
</blockquote></div>
<p> RTMP:: </p>
<div class="blockquote"><blockquote class="blockquote">
<p> Real Time Messaging Protocol (RTMP) is a proprietary protocol developed by Adobe Systems that is primarily used with Adobe Flash Media Server to stream audio, video, and data over the internet to the Adobe Flash Player client. RTMP can be used for Remote Procedure Calls. RTMP maintains a persistent connection with an endpoint and allows real-time communication. Other RPC services are made asynchronously with a single client/server request/response model, so real-time communication is not necessary. </p>
</blockquote></div>
<p> RTMPT:: </p>
<div class="blockquote"><blockquote class="blockquote">
<p> RTMP using HTTP tunneling. </p>
</blockquote></div>
<p> SWF::</p>
<div class="blockquote"><blockquote class="blockquote">
<p> Proprietary vector graphics file format produced by the Flash software from Adobe. Intended to be small enough for publication on the web, SWF files can contain animations or applets of varying degrees of interactivity and function. SWF is also sometimes used for creating animated display graphics and menus for DVD movies, and television commercials. </p>
</blockquote></div>
<p> Tomcat::</p>
<div class="blockquote"><blockquote class="blockquote">
<p> A web container, or application server developed at the Apache Software Foundation (ASF). Tomcat implements the servlet and the JavaServer Pages (JSP) specifications from Sun Microsystems, providing an environment for Java code to run in cooperation with a web server. It adds tools for configuration and management but can also be configured by editing configuration files that are normally XML-formatted. Tomcat includes its own internal HTTP server.</p>
</blockquote></div>
</div>
<div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d5e1886"></a>11.9. Bibliography</h2></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>Red5 -
<a class="ulink" href="http://red5.org" target="_top">http://red5.org</a>
</p>
</li><li class="listitem">
<p>Apache Tomcat -
<a class="ulink" href="http://tomcat.apache.org" target="_top">http://tomcat.apache.org</a>
</p>
</li><li class="listitem">
<p>Wikipedia -
<a class="ulink" href="http://en.wikipedia.org" target="_top">http://en.wikipedia.org</a>
</p>
</li></ul></div>
</div>
</div><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navfooter"><hr></hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="logging-setup.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="stream-paths.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 10. Logging Setup </td><td width="20%" align="center"><span style="color:white;font-size:90%;"><a href="http://osflash.org/red5" title="Red5">Red5 Open Source Flash Server</a></span></td><td width="40%" align="right" valign="top"> Chapter 12. Customize Stream Paths</td></tr></table></div></body></html>
|