Tomcat vs turnkey

From what I can tell, there is little difference between a turnkey install and a tomcat install + placing the .war file/s into that tomcat instance (aside from the port number). Before I got really involved with one or the other, any insights or concerns re: both would be very much appreciated. Security / administration / things like changing the port number / etc...
Thank you very much for your time.

Jeremy,
You are correct that the turnkey install does not have any significant
differences from just deploying the .war file on to Tomcat. This is on
purpose. We just wanted to provide a preconfigured server that you could
try the samples with right away.
I wouldn't lose any sleep over it.
If you are deploying a 'fresh' application however, I would suggest using
the .war file as it is doesn't contain any extra destinations or samples
that would not be needed in a production application.
Tom Jordahl
Adobe

Similar Messages

Is LC Foundation bundled with LiveCycle Data Services

I recently got this question - Do I get LC Workbench and LC Foundation when I buy LiveCycle Data Services?
The answer is "No".
With LiveCycle Data Services you get:
1. LiveCycle Data Services server - It works with most application server, but ship with a tomcat based turnkey option
2. Adobe Application Modeling Plugin - This is a plugin to Flash Builder 4 that enables to do Model Driven Development of Flex applications. This is "New in 3.0"
Anil Channappa | Sr. Product Manager LiveCycle Data Services and Blaze DS
Adobe Systems Inc | 21-61 Hickory Dr, Waltham, MA 02451-1011
[email protected]<mailto:[email protected]>| 781.839.1331 | myBlog<http://anilchannappa.org/

Hi Guillaume,
there is no limitation. Dynamic PDF files can be generated with Livecycle Data Services.
You should have a look at the XML file generated by your Flex code. Try to save it and see how the XML file behaves when you generate a PDF preview with Designer. You can go to the menu: File > Properties > Preview > Use XML test data...
With the XFAHelper class, you can either load a PDF or a XDP file. Have you tried with a XDP ?
I've attached a dynamic PDF file that I've created for a customer. I generate a dynamic PDF file using LiveCycle Data Services. Maybe you'll find some clues within the file.
Michael

Tomcat Manager Portal in BlazeDS Turnkey Server

Hi all,
Im pretty new to blazeds, and liking what i have experienced thus far. Could anyone please tell me how to access the Tomcat Manager Portal within the BlazeDS Turnkey Server Installation.
Like in know it runs on port 8400 by default. So running it then opening http://localhost:8400 gets me the blazeds turnkey home page with links to the sample apps.
However I want to get to the Tomcat Portal to change file access permissions etc. And if i wanted to deploy apps from there etc.
Is this possible?
Please advise!
Kind Regards
Willem

Follow the instructions here:
http://blog.techstacks.com/2009/05/tomcat-management-setting-up-tomcat.html
Basically just add a user and role to the $CATALINA_HOME/conf/tomcat-users.xml:
<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
<role rolename="manager"/>
<user username="tomcat" password="tomcat" roles="manager"/>
</tomcat-users>
Then use the URL: http://localhost:8400/manager/html to access the manager.

Install and run blazeds-turnkey-3.2.0-3978 in Tomcat in Linux

I Installed and ran the blazeds-turnkey-3.2.0-3978 distrubution in Tomcat 5.0.27 with JVM 1.5.0_22 in Window Vista successfully.
Blazeds, ds-consolo, and samples applications are working fine. I'm not using the Tomcat with Flex Builder. The ds-consolo and samples are
accessed through http://localhost:8080/ds-consolo and http://localhost:8080/samples. I did not change any of the configuration files
(service-config.xml, ...) in the distribution package.
Now I try to Install and run the same blazeds-turnkey-3.2.0-3978 distrubution in the same Tomcat 5.0.27 with JVM 1.5.0_22 in a remote Linux server.
I changed the configuration files as following:
For blazeds application, I changed the parameters in all the configuration files under WEB-INF/flex in following way:
{server.name}:{server:port} to xyz.com   (xyz.com is the domain name, and we use default port 80)
{context-root} to blazeds
For ds-consolo application, I changed the parameters in all the configuration files under WEB-INF/flex in following way:
{server.name}:{server:port} to xyz.com   (xyz.com is the domain name, and we use default port 80)
{context-root} to ds-consolo
For samples application, I changed the parameters in all the configuration files under WEB-INF/flex in following way:
{server.name}:{server:port} to xyz.com   (xyz.com is the domain name, and we use default port 80)
{context-root} to samples
It seems they were all deployed to the Tomcat OK, but when I tried to run the ds-consolo and samples apps, I got
errors. Did I set the parameters, especially {context-root}, correctly? Am I missing anything?

I Installed and ran the blazeds-turnkey-3.2.0-3978 distrubution in Tomcat 5.0.27 with JVM 1.5.0_22 in Window Vista successfully.
Blazeds, ds-consolo, and samples applications are working fine. I'm not using the Tomcat with Flex Builder. The ds-consolo and samples are
accessed through http://localhost:8080/ds-consolo and http://localhost:8080/samples. I did not change any of the configuration files
(service-config.xml, ...) in the distribution package.
Now I try to Install and run the same blazeds-turnkey-3.2.0-3978 distrubution in the same Tomcat 5.0.27 with JVM 1.5.0_22 in a remote Linux server.
I changed the configuration files as following:
For blazeds application, I changed the parameters in all the configuration files under WEB-INF/flex in following way:
{server.name}:{server:port} to xyz.com   (xyz.com is the domain name, and we use default port 80)
{context-root} to blazeds
For ds-consolo application, I changed the parameters in all the configuration files under WEB-INF/flex in following way:
{server.name}:{server:port} to xyz.com   (xyz.com is the domain name, and we use default port 80)
{context-root} to ds-consolo
For samples application, I changed the parameters in all the configuration files under WEB-INF/flex in following way:
{server.name}:{server:port} to xyz.com   (xyz.com is the domain name, and we use default port 80)
{context-root} to samples
It seems they were all deployed to the Tomcat OK, but when I tried to run the ds-consolo and samples apps, I got
errors. Did I set the parameters, especially {context-root}, correctly? Am I missing anything?

Install and run blazeds-turnkey-3.2.0-3978 in Tomcat on Linux

I Installed and ran the blazeds-turnkey-3.2.0-3978 distrubution in Tomcat 5.0.27 with JVM 1.5.0_22 in my laptop (Window Vista Pro) successfully.
Blazeds, ds-consolo, and samples applications are working fine. I'm not using Flex Builder for this. The ds-consolo and samples are
accessed through http://localhost:8080/ds-consolo and http://localhost:8080/samples. I did not change any of the configuration files
(service-config.xml, ...) in the distribution package.
Now I try to Install and run the same blazeds-turnkey-3.2.0-3978 distrubution with the same Tomcat 5.0.27 with JVM 1.5.0_22 in a remote Linux server.
I changed the configuration files as following:
For blazeds application, I changed the parameters in all the configuration files under WEB-INF/flex in following way:
{server.name}:{server:port} to xyz.com   (xyz.com is the domain name, and we use default port 80).
{context-root} to blazeds
For ds-consolo application, I changed the parameters in all the configuration files under WEB-INF/flex in following way:
{server.name}:{server:port} to xyz.com   (xyz.com is the domain name, and we use default port 80).
{context-root} to ds-consolo
For samples application, I changed the parameters in all the configuration files under WEB-INF/flex in following way:
{server.name}:{server:port} to xyz.com   (xyz.com is the domain name, and we use default port 80).
{context-root} to samples
It seems they were all deployed to the Tomcat OK, but when I tried to run the ds-consolo and samples apps, I got
errors. Did I set the parameters in the configuration files, especially {context-root}, correctly? Am I missing anything?

If it is caused by a wrong port, I should get an error message or timeout.
This is the services-config.xml file I'm using for Blazeds app
<?xml version="1.0" encoding="UTF-8"?>
<services-config>
    <services>
        <service-include file-path="remoting-config.xml" />
        <service-include file-path="proxy-config.xml" />
        <service-include file-path="messaging-config.xml" />
    </services>
    <security>
        <login-command class="flex.messaging.security.TomcatLoginCommand" server="Tomcat"/>
    </security>
    <channels>
        <channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint url="http://infody.com/blazeds/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
        </channel-definition>
        <channel-definition id="my-secure-amf" class="mx.messaging.channels.SecureAMFChannel">
            <endpoint url="https://xyz.com/blazeds/messagebroker/amfsecure" class="flex.messaging.endpoints.SecureAMFEndpoint"/>
            <properties>
                <add-no-cache-headers>false</add-no-cache-headers>
            </properties>
        </channel-definition>
        <channel-definition id="my-polling-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint url="http://xyz.com/blazeds/messagebroker/amfpolling" class="flex.messaging.endpoints.AMFEndpoint"/>
            <properties>
                <polling-enabled>true</polling-enabled>
                <polling-interval-seconds>4</polling-interval-seconds>
            </properties>
        </channel-definition>
    </channels>
    <logging>
        <target class="flex.messaging.log.ConsoleTarget" level="Error">
            <properties>
                <prefix>[BlazeDS] </prefix>
                <includeDate>false</includeDate>
                <includeTime>false</includeTime>
                <includeLevel>false</includeLevel>
                <includeCategory>false</includeCategory>
            </properties>
            <filters>
                <pattern>Endpoint.*</pattern>
                <pattern>Service.*</pattern>
                <pattern>Configuration</pattern>
            </filters>
        </target>
    </logging>
    <system>
        <redeploy>
            <enabled>false</enabled>
        </redeploy>
    </system>
</services-config>
There is no url or port settings in the other three Blazeds configuration xml file: remoting-config.xml, proxy-config.xml, messaging-config.xml
Here is the services-config.xml file for ds-console app:
<?xml version="1.0" encoding="UTF-8"?>
<services-config>
    <services>
        
        <service id="remoting-service" class="flex.messaging.services.RemotingService">
            <adapters>
                <adapter-definition id="java-object" class="flex.messaging.services.remoting.adapters.JavaAdapter" default="true"/>
            </adapters>
            
            <destination id="RuntimeManagement" channels="amf">
                <properties>
                    <source>flex.management.jmx.MBeanServerGateway</source>
                </properties>
            </destination>
        </service>
    </services>
        <security>
            <login-command class="flex.messaging.security.TomcatLoginCommand" server="Tomcat"/>
        </security>
    <channels>
        <channel-definition id="amf" class="mx.messaging.channels.AMFChannel">
            <endpoint url="http://xyz.com/ds-console/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
            <properties>
                <polling-enabled>false</polling-enabled>
            </properties>
        </channel-definition>
    </channels>
    <logging>
        
        <target class="flex.messaging.log.ConsoleTarget" level="Error">
            <properties>
                <prefix>[BlazeDS] </prefix>
                <includeDate>false</includeDate>
                <includeTime>false</includeTime>
                <includeLevel>true</includeLevel>
                <includeCategory>true</includeCategory>
            </properties>
            <filters>
                <pattern>Endpoint.*</pattern>
            </filters>
        </target>
    </logging>
    <system>
        <redeploy>
            <enabled>true</enabled>
            <watch-interval>20</watch-interval>
            <watch-file>ds-console/WEB-INF/flex/services-config.xml</watch-file>
            <touch-file>ds-console/WEB-INF/web.xml</touch-file>
        </redeploy>
    </system>
</services-config>

[svn] 4619: Bug: BLZ-313 - HTTPProxyService throws null pointer when non-turnkey BlazeDS app is deployed to Tomcat 6 .0.16

Revision: 4619
Author: [email protected]
Date: 2009-01-22 10:47:12 -0800 (Thu, 22 Jan 2009)
Log Message:
Bug: BLZ-313 - HTTPProxyService throws null pointer when non-turnkey BlazeDS app is deployed to Tomcat 6.0.16
QA: Yes
Doc: No
Checkintests: Pass
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-313
Modified Paths:
blazeds/trunk/modules/proxy/src/flex/messaging/services/HTTPProxyService.java

I submitted a bug, and this was fixed in the latest trunk
version.

Non-turnkey BlazeDS with Tomcat / ActiveMQ / Spring

the turnkey blazeds supplies tomcat 6.0.14, spring 2.0, activemq 4.1.1.
if i go non-turnkey, i would like to go tomcat 6.0.18, spring 2.5, activemq 5.2.0.
activemq seems to have changed quite a bit from turnkey solution's version. are there any pointers to integrating this stack properly, because else, i may have to go down the turnkey route, and miss out on the latest improvement from each component.

HI Sujit,
Thanks......
I got it working now..... The problem is with spring.jar. I
was using spring framework version 2.0.8.
I have replaced it with Spring Framework 2.5.5. Now it is
working fine.....
I have no clue why the sample is not working with spring
framework version 2.0.8.
Regards
Sunil.P

Question about blazeds turnkey, tomcat and directory structure

hi. this question is pretty basic...been reading sujit reddy g's blog on installing/setting up blazeds.
in one article he creates a samplewebapps directory in C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\samplewebapps and copies the blazeds WEB-INF/lib into that directory and the configuration files in the flex folder across as well...http://sujitreddyg.wordpress.com/2009/04/07/setting-up-blazeds/
in another article on invoking java methods from flex he configures the remote-config.xml file directly in the blazeds\WEB-INF\flex folder....http://sujitreddyg.wordpress.com/2008/01/14/invoking-java-methods-from-adobe-fle x/
wasn't sure why in the first example he copied the files and folders to the samplewebapps directory while in the second example he just configured the files within the blazeds directory...thanx...(i'm a newbie at server side development)

I'll take a stab at it. The key thing to realize is the BlazeDS code is ADDED on
to the appserver. E.g. for Tomcat/WebLogic/et al one adds the reference in the web.xml file in WEB-INF.
So, what is that add-on?
1. Executable files. These are jar files and typically stuck into WEB-INF/lib
2. Configuration files. flex/services-config.xml is specified in web.xml. It refers to the other config files in WEB-INF/flex
So, the config in web.xml tells Tomcat (and its forked commercial products) to load up the Flex jars and run some classes. By standard, the "run some classes" follows the servlet lifecycle and runs specific methods in the class when the servlet is loaded, called, destroyed. So, Flex jars have a class which implements the servlet interface.
Incidentally, you may also see references to log4j, Spring, and other frameworks in the web.xml as well. They do the same sort of stuff. So, Tomcat does the passing of the HTTP packets and stages them into Java classes and the hooked in frameworks do add their own behaviours to the setup.
HTH,
TimJowers
P.S> Also note in Flex when you setup the project properties for a Flex Project then you need to match up your URL and "context" to what you have on your server. In his exampe, the "samples" context may have already been setup so easier to use. What is a "context"? The idea is to have more than one webapp running on an appserver. In Tomcat, its basically just the subdirectory under "webapps". That directory name becomes part of the URL. E.g. webapps/samples -> http://localhost:8080/samples or webapps/mytest -> http://localhost:8080/mytest

Question re: Blaze DS Directory Structure Following Turnkey Installation

Hello. I've been building client-side apps with flex for a while and have started getting into backend development.
I have read up a fair bit on blaze ds and have downloaded the turnkey installation and successfully ran a few of the samples...but i have a couple of questions re: the directory structure if someone could help...i unzipped the turnkey into Blaze_ds folder on the desktop...
a) .........\Blaze_ds\tomcat\webapps\blazeds\WEB-INF - could u please explain the concept of the WEB-INF directory and the folders inside it (flex, src, classes, lib, etc.)
b) ......... \Blaze_ds\tomcat\webapps\samples - there are all the samples in here (eg. testdrive-chat, testdrive-101, dashboard, etc.)...and there is also a WEB-INF and META-INF folders...just wondering why there isn't WEB-INF/META-INF inside each sample folder
Finally, can someone also let me know the concept of localhost and the port number 8400 and are there any good books on blaze ds?
thx!

There's really not much difference. In some cases, you might already have a web application you are using so you could just copy the contents of the blazeds web app into your existing web application.
Application servers can host more than one web application and a Flex application that uses BlazeDS can be deployed on a different web app than the one where BlazeDS is running or a different server entirely so it really just depends how you want to set things up.
Hope I'm not just making things more confusing for you. . .
-Alex

No data loaded when running publish/subscribe sample on Tomcat

I have Tomcat 6.0 running as a .jsp handler with Apache 2.2 using the mod_jk connector. I've configured the samples/ context to be handled via Tomcat. Everything seems to be working fine -- I can access the files and launch .jsp files via my web browser.
But when I try to fire up the DataPush example, I get no results from BlazeDS. Here's the procedure I am using:
1. Start the feed by running http://localhost:8080/samples/testdrive-datapush/startfeed.jsp
2. Run the Flex side: http://localhost:8080/samples/testdrive-datapush/index.html.
3. Press the "Subscribe to 'feed' destination."
Using Firebug within Firefox, I can tell that it's attempting to access a streaming channel. There are two requests:
1) http://localhost:8080/samples/messagebroker/streamingamf
2) http://localhost:8080/samples/messagebroker/streamingamf?command=open&version=1
Request #1 comes back with a plain-text "Loading..." response.
Request #2 returns an error message: The request sent by the client was syntactically incorrect ().
Incase it matters, I have been playing around with the config files in previous tests. For this test, I deleted the samples.war, and samples/ directory from Tomcat. Then I copied the original samples.war back in and restarted Tomcat to redeploy. I would think that this erases all of my configuration settings -- but it does not seem to be doing that (The Data Push/Pull does NOT default to streaming from the Turnkey package, yet when I hit the service again, it always tries to perform streaming first -- as I had told it to do in a previous configuration).
So I have two questions:
1. Why doesn't the example work using streaming?
2. Why aren't my configuration files being reloaded when I restart Tomcat?
TIA
Jonathon

Hi,Alex
Thanks for your advies, But it do not works.
with a Apache Fronting Tomcat, the following config is work:
channel 1 : Hi. Here are answers to your questions.
>
>>>1. Why doesn't the example work using streaming?
>Some proxies buffer the response that is sent back to the client. This causes streaming connections to not work. This is a known issue with the mod_jk connector. Take a look at the following bug for more info.
>http://bugs.adobe.com/jira/browse/BLZ-84
>
>>>2. Why aren't my configuration files being reloaded when I restart Tomcat?
>Did you recompile the sample application after changing the configuration? The configuration information is used by both the server and the client and is compiled into the client. You will need to recompile the client application using the new configuration files if you want your changes to be picked up. Note that is is possible to load the configuration information into the client application at runtime but that's not how the sample applications were built. If you are interested in loading the configuration information at runtime here is a blog posting that gives an example.
>http://coenraets.org/blog/2009/03/externalizing-service-configuration-using-blazeds-and-lc ds/
>Hope that helps.
>-Alex
>

Tomcat: prefix in services-config.xml must be unique?

Hi all, I've been trying to get my flex application communicating with Tomcat and now have it working
Just trying to confirm something that took me many hours to get right and may help others along the way..
Originally I modified the BlazeDS webapp by updating the remoting xml and putting in my own classes and it worked without any problems
I then removed the BlazeDS webapp directory out the tree and created a new one carefully checking each step.. but there was nothing written to catalina log file at any time when running the app or any sign of communication even in debug mode
I then moved the sample BlazeDS webapp back and when starting Tomcat it complained of duplicate ID's (here is the message: Exception: flex.messaging.config.ConfigurationException: Can not add destination with id 'insert your remoting destination id' to service with id 'proxy-service' because another service with id 'remoting-service' already has a destination with the same id)
Eventually I noticed in services-config.xml logging section for my new webapp that the <prefix> was still set to BlazeDS - changed this to the new webapp directory name and not only did the exceptions disappear but everything now worked
So I'm thinking that the prefix is much more important than just a logging descriptor as the XML tag suggests
Can anyone confirm this behaviour or shed some light?
PS I should make clear the above problems were not when running the turnkey but on a fresh install of tomcat 6.0.29 on Centos linux using apache proxypass/reverseproxypass to redirect port 80 to 8080
PS2 - I realise this is not a pure Flex question but it's related due to Adobe crafting a turnkey Flex/Tomcat install with Blaze and it's in the flex configuration files)
I hope I've covered all bases in the question and look forward to knowing more... CHEERS!

Hi all, I've been trying to get my flex application communicating with Tomcat and now have it working
Just trying to confirm something that took me many hours to get right and may help others along the way..
Originally I modified the BlazeDS webapp by updating the remoting xml and putting in my own classes and it worked without any problems
I then removed the BlazeDS webapp directory out the tree and created a new one carefully checking each step.. but there was nothing written to catalina log file at any time when running the app or any sign of communication even in debug mode
I then moved the sample BlazeDS webapp back and when starting Tomcat it complained of duplicate ID's (here is the message: Exception: flex.messaging.config.ConfigurationException: Can not add destination with id 'insert your remoting destination id' to service with id 'proxy-service' because another service with id 'remoting-service' already has a destination with the same id)
Eventually I noticed in services-config.xml logging section for my new webapp that the <prefix> was still set to BlazeDS - changed this to the new webapp directory name and not only did the exceptions disappear but everything now worked
So I'm thinking that the prefix is much more important than just a logging descriptor as the XML tag suggests
Can anyone confirm this behaviour or shed some light?
PS I should make clear the above problems were not when running the turnkey but on a fresh install of tomcat 6.0.29 on Centos linux using apache proxypass/reverseproxypass to redirect port 80 to 8080
PS2 - I realise this is not a pure Flex question but it's related due to Adobe crafting a turnkey Flex/Tomcat install with Blaze and it's in the flex configuration files)
I hope I've covered all bases in the question and look forward to knowing more... CHEERS!

Error: "Cannot access the web server" with BlazeDS Turnkey

Help! I'm new to Flex and BlazeDS and Eclipse. I was trying to setup a Flex Project using a BlazeDS/Tomcat server running from Eclipse on Windows XP per the example in flexbandit.com/archives/55#comment-269 and in (www.infoq.com/articles/blazeds-intro).   I am NOT using the Eclipse Flex plug-in. I'm using Flex Builder for the Flex code.
Here's what I've done:
I installed BlazeDS and tested http://localhost:8400 - That worked.
I setup Tomcat in Eclipse. - That seemed to work.
I created a Dynamic Web Project in Eclipse - That seemed to work.
I created the bare-bones BlazeDS Configuration under the Eclipse project and then created a basic HelloWorld java class.
I added the destination in the “remoting-config.xml” file found in the c:/projects/workspace/ReportGenTool/WebContent/WEB-INF/flex” directory:
<destination id="HelloWorld">   <properties> <source>HelloWorld</source> </properties> </destination>
When I started the application server by clicking on the server's green play button in Eclipse and then tried to open localhost:8400/ReportGenTool, I got the 404 error : The requested source (/ReportGenTool/) is not available which according to the instructions is fine.
Next I created a Flex Project, but when I try to validate the new Flex project configuration, it gives me an error "Cannot access the web server. The server may not be running, or the web root folder or root URL may be invalid."
When I validated the server was running after setting up the BlazeDs Turnkey, I saw the BlazeDS page.
Now when I bring up http://localhost:8400 I get:
      Directory Listing for /
      Apache Tomcat/6.0.14
My eclipse project is named ReportGenTool and I've overwritten the WebContent directory with the META-INF and WEB-INF directories from the BlazeDS installation (C:\blazeds\tomcat\webapps\blazeds). According to Eclipse the server is running.
My Flex project is named ReportGenTool and is located in another directory away from the Eclipse project directory.
     My root folder is: C:\Projects\workspace\ReportGenTool\WebContent
     Root URL: is http://localhost:8400/ReportGenTool/
     Context root is: /ReportGenTool/
Any idea what might be wrong? What didn't I configure that needs to be configured?
Thanks in advance.

This is not working because your router has a direct to your web server that is not through the outside interface which is needed for nat to occur, for this to work you need to setup a loopback interface as nat outside and policy route traffic to there for your server traffic
Bu if your server is internal why do you need nat at all? Can you not use bind with views that might be simpler
M
Sent from Cisco Technical Support iPad App

ECM Connector + Turnkey Installation - Error with MySQL (NoClassDefFoundError)

Twice I have installed LiveCycle ES for JBoss Using Turnkey (following the documentation)... W2K3 Server, 2GB RAM, 32GB Hard Drive, Java 1.5.0.15.
The core services work good, but it's ECM Connector for Documentum that throws up an error. (Snippets of the server.log below)
I searched for aspectj.org namespace and it belongs to MySql. Am I supposed to copy a jar file somewhere? I searched the docs but couldn't find any mention.
Odd enough, the sample ECM Documentum Connector Services work, it's the standard ones that don't (Authentication, Connector, etc)
EMCDocumentumContentRepositoryConnector: 1.0 Stopped com.adobe.livecycle.ConnectorforEMCDocumentum 8.0.3188.1.83522.8
When I click start, I get internal error and server.log fills up with the class not found errors.
Any insight you could provide would great helpful.
Thanks in advance,
Vikram
2008-07-11 11:08:54,984 ERROR [org.jboss.ejb.plugins.LogInterceptor] Unexpected Error in method: public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterLocal.doRequiresNe w(com.adobe.idp.dsc.transaction.TransactionDefinition,com.adobe.idp.dsc.transaction.Transa ctionCallback) throws com.adobe.idp.dsc.DSCException
java.lang.NoClassDefFoundError: org/aspectj/lang/Signature
at com.adobe.livecycle.documentumservice.impl.util.DocumentumUtils.configureClient(Documentu mUtils.java:88)
at com.adobe.livecycle.documentumservice.impl.DocumentumProviderServiceLifeCycleImpl.configu reDocbroker(DocumentumProviderServiceLifeCycleImpl.java:261)
at com.adobe.livecycle.documentumservice.impl.DocumentumProviderServiceLifeCycleImpl.execute Once(DocumentumProviderServiceLifeCycleImpl.java:92)
at com.adobe.livecycle.documentumservice.impl.DocumentumProviderServiceLifeCycleImpl.onStart (DocumentumProviderServiceLifeCycleImpl.java:53)
at ...
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
2008-07-11 11:08:55,000 INFO [STDOUT] Jul 11, 2008 11:08:55 AM com.adobe.idp.dsc.registry.service.impl.ServiceRegistryImpl start
SEVERE: ServiceRegistryImpl:start(EMCDocumentumAuthProviderService, 1.0):com.adobe.idp.dsc.DSCRuntimeException(Internal error.)
ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:207)
at com.adobe.idp.dsc.transaction.impl.DefaultTransactionTemplate.execute(DefaultTransactionT emplate.java:79)
at

Using j2se 1.4.2_04, turnkey installation works perfectly.
Bye,
Dr.Channard

Flex-tomcat-server.jar

Hello, everyone.
I'm trying to install the security jars for JBoss. I previously had
them installed, but recently reformatted my machine and seem to have
lost track of the jars needed.
I've downloaded both the
blazeds-src-3-0-0-544
and
blazeds-src-3-0-1-1755
(haven't gone to any daily builds)
both have the file
{blazeds_install}/resources/security/jboss/readme.txt
which states
1. Copy flex-tomcat-common.jar and flex-tomcat-server.jar from
{blazeds_install}/resources/security/tomcat folder to {jboss_root}/
server/default/lib folder.
Neither of those files exist.
I think I only had the second one and I had pulled it from an example
somewhere.
But I want both to be sure there's no dependencies.
If anyone
1) has a copy
2) knows where i can get one,
3) know how to build them,
or
4) knows the expected contents,
could you PLEASE let me know.
google has failed me,
tia,
-bill shirley

I looked in the Turnkey for 3.0.1.1755 and both those jars are in there in the expected location so the easiest thing to do would be to download the Turnkey and grab them from there.
http://opensource.adobe.com/wiki/display/blazeds/download+blazeds+3
Hope that helps.
-Alex

[svn:bz-trunk] 18081: Move BlazeDS to Tomcat 6.0.29

Revision: 18081
Revision: 18081
Author:   [email protected]
Date:     2010-10-08 01:10:36 -0700 (Fri, 08 Oct 2010)
Log Message:
Move BlazeDS to Tomcat 6.0.29
Check-in Tests: PASS
QA: Yes
Modified Paths:
    blazeds/trunk/build.properties
    blazeds/trunk/build.xml
    blazeds/trunk/collateral/blazeds-src-readme.htm
    blazeds/trunk/collateral/blazeds-turnkey-readme.htm
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/build.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/flexunit/build.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/build.xml
    blazeds/trunk/qa/build.properties

If you're still using Buckminster 3.6, I strongly suggest switching to 3.7 - it has a number of bug fixes and improvements. This applies to both headless, and the IDE (assuming Eclipse 3.7 Indigo).
Matthew

Tomcat vs turnkey

Similar Messages

Maybe you are looking for