________________________________
From: André Warnier <a...@ice-sa.com>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Saturday, 17 December 2011 6:03 PM
Subject: Re: Tomcat 6.0 configuration with Adobe LiveCycle DS ES 3.0 Server
I have written a simple web application to accept Name using Flex SDK 3.2
HttpService and send it to my web application running on Tomcat 6.0 WebServer.
We are Using Flex with LiveCycle DS ES 3.0 to communicate Web Server(Tomcat
6.0). Am able to accept input in flex code but the problem is when trying to
send data from Flex client to Tomcat WebServer application, it does not work.
Both LifeCycle DS ES 3.0 and WebServer Tomcat 6.0 are running on same machine.
LiveCycle DS ES 3.0 uses port no - 8400
WebServer Tomcat 6.0 uses port no - 8000
LiveCycle DS ES 3.0 uses two configuration files :-
a. services-config.xml
b. proxy-config.xml
WebServer Tommcat 6.0 uses one configuration files :-
a. web.xml
I have worked with Adobe and they have helped me configure LiveCycle DS ES 3.0.
I have Installed Flex Debugger and it gives follwoing error message when trying
to communicate with Tomcat 6.0 WebServer:-
[RPC Fault faultString="Send failed" faultCode="Client.Error.MessageSend"
faultDetail="Channel.Connect.Failed error NetConnection.Call.Failed: HTTP:
Status 404: url: 'http://localhost:8400/JLCAPP/messagebroker/amf'"]
at
mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:220]
at
mx.rpc::Responder/fault()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\rpc\Responder.as:53]
at
mx.rpc::AsyncRequest/fault()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\rpc\AsyncRequest.as:103]
at
mx.messaging::ChannelSet/faultPendingSends()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\messaging\ChannelSet.as:1482]
at
mx.messaging::ChannelSet/channelFaultHandler()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\messaging\ChannelSet.as:975]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at
mx.messaging::Channel/connectFailed()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\messaging\Channel.as:997]
at
mx.messaging.channels::PollingChannel/connectFailed()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\messaging\channels\PollingChannel.as:354]
at
mx.messaging.channels::AMFChannel/statusHandler()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\messaging\channels\AMFChannel.as:390]
Am providing you with the configuration file that am using at Tomcat Webserver
namely web.xml.
web.xml
-----------
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; version="2.5"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd";>
<!-- MessageBroker Servlet -->
<!-- Http Flex Session attribute and binding listener support -->
<listener>
<listener-class>flex.messaging.HttpFlexSession</listener-class>
</listener>
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
</init-param>
<init-param>
<param-name>debug</param-name>
<param-value>3</param-value>
</init-param>
<init-param>
<param-name>detail</param-name>
<param-value>3</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>MessageBrokerServlet</servlet-name>
<servlet-class>flex.messaging.MessageBrokerServlet</servlet-class>
<init-param>
<param-name>services.configuration.file</param-name>
<param-value>/WEB-INF/flex/services-config.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>MessageBrokerServlet</servlet-name>
<url-pattern>/messagebroker/*</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>hello.html</welcome-file>
</welcome-file-list>
</web-app>
The problem is that connection is not getting established between LiveCycle DS
ES 3.0 and Tomcat 6.0 WebServer. Am not able to figure out what configuration
settings are wrong at my Tomcat 6.0 WebServer that is denying the connection
between the two servers.
Hope this explains the problem am facing. In case you need any more information
please let me know.
Regards,
Anshul.
Anshul Asthana wrote:
...
> Subject: Re: Tomcat 6.0 configuration with Adobe LiveCycle DS ES 3.0 Server
>
> I want to configure Tomcat 6.0 with Adobe LiveCycle DS ES 3.0 Server so that
> both can communicate with each other. What are the steps and settings I need
> to configure and How to configure them in Tomcat 6.0.
>
> Tomcat 6.0 uses port no - 8000.
> Adobe LiveCycle DS ES 3.0 Server uses port no - 8400.
>
> Regards,
> Anshul
Anshul,
1) on this list, it is preferred if you write your answers directly below the
question, and not on top. That makes the flow of the conversation easier to
follow (rather than having to jump up and down trying to figure out what is
answering what).
2) your question/statement, as phrased above, does not mean anything.
You have two pieces of software, Tomcat and the Adobe thing (which on this list
we don't know much about).
Both are running, apparently.
And each one of them opens a listening port, apparently.
But these two servers will not "communicate" unless some application in one of
them decides to establish some communication with the other one, in order to
"do something".
Or do you just expect them to start saying "Hello" to eachother and start
talking about the weather on the WWW ?
So what exactly are you trying to achieve, what have you tried, and what does
not work as you expect ?
Hi André,
