EBCC syncronisation fail with new application

Question

Hello.
My team has problems using the Portal 4.0 with WLS 6.1 SP1.
We copied the p13n Domain and rename the Domain and the Server.
When we then syncronise one of the sample webflows with the new server, all
works fine.
Then we add our very simple application with 2 jsps (one with a webflow form
that fires an event that is configured to switch to the second one) on the
same Domain/Server.
When we then want to syncronise the EBCC could not connect (errormsg:
Authorisation denied. Check User/pass and ensure server running)
Can someone help us?
Must we add some tables inside the cloudspace database or is this done
automatically?
Where is the relationship between the database and the application
configured?
Is there a simple tutorial from A to Z how to set up a new Domain and Server
ready for webflow / Code and deploy a simplest application / configure
webflow with ebcc.
I need a all steps included tutorial to give this to my developers. The
e-docs are great but it is dificult to collect all pices together.
If someone has a finished configured simple webflow application please send
it to me together with the domain config xml.
Thanks a lot!
Markus Lutum
[email protected]

Answer 1

Frank,
You only need to do this config steps if you are setting up a cluster (or
would like to synchronize several machines with a single EBCC instance
automatically). For the default single user dev. box you should not need to
do this, just deploying the DataSync WebApp (our apps have it) is all that
is required. If you don't have any EJBs deployed on the machine (which is
the case with the typical admin server) you also have to put p13n_util.jar
under WEB-INF/lib of the DataSync WebApp.
Please note that config is significantly improved with the upcoming 7.0
release.
(Param Name) = (Param Value)
notifiedName = notifiedNameDataRepository
notifiedPassword = password
notifiedLogin = system
notifiedUrl = http://localhost:7501/scddDataSync/DataSyncServlet
notifiedRealm = weblogicYou need to append "-1" to all of these (ie. the paramter for the first URL
would be "notifiedUrl-1", "notifiedUrl-2" for the second etc.
This does not explain your NoClassDefFoundError however. Try cleaning up the
temp server directories, double checking you put p13n_util.jar under the
correct WEB-INF/lib and restarting the server.
Sincerely,
Daniel Selman
"Frank Wang" <[email protected]> wrote in message
news:[email protected]...
>
Hi again, Michael,
I tried what you suggested, and still got the same NoClassDefFoundErrorexception
for com/bea/p13n/management/data/message/MessageExecutor. This is what Idid:
>
1) I moved the p13n_util.jar file intoconfig\petflowDomain\applications\scdd\datasync\WEB-INF\lib.
>
2) I added the following parameters to the deployment descriptor for thedatasync
webapp. Within the console's deployment descriptor screen for thedatasync webapp,
I went to "Data Synchronization Web Application > Web App Descriptor >Parameters",
and added the following parameters:
(Param Name) = (Param Value)
notifiedName = notifiedNameDataRepository
notifiedPassword = password
notifiedLogin = system
notifiedUrl = http://localhost:7501/scddDataSync/DataSyncServlet
notifiedRealm = weblogic
3) Within the startup script (config\petflowDomain\startPetflow.bat), Iadded the
argument "-Ddata.sync.jdbc.master.dr=true" to the end of the "java"command, immediately
before "weblogic.Server".
4) There is only one server configured for the petflowDomain, and it isnamed "petflowServer".
Since this domain is a part of BEA's sample apps, I did not think I wouldneed to
configure a separate "sync" server. The JDBC dataSyncPool (Services >JDBC > Connection
Pools) starts up correctly, and is targeted at petflowServer. The Tx DataSource
is also configured at Services > JDBC > Tx Data Sources. I really don'tthink that
there's anything wrong with these configs since I copied this overstraight from
PetFlow.
Do you have any other suggestions? I do have a proposal: How about if youguys set
up a working, blank domain with the correct servers, jar files, xmldescriptors,
datasync app(s), and then e-mail it to me? Or, conversely, I can zip upmy current,
non-working domain and send it to you for debugging? This would be fasterthan trying
to exchange messages on the newsgroup.
-Frank
"Frank Wang" <[email protected]> wrote:
Hi Michael,
Thank you very much for your research and reply.
Can you elaborate on Item 2 you mentioned? Which "parameters for
synchronization
w/managed servers" are you speaking of? Can you list which file(s) and
which parameter(s)
and values to configure? This will save me a lot of time trying tofigure
that out.
In Item 4, I'm not sure which servers are the "sync" server and "managed"
server.
I only have one server for my "ddDomain" domain. Can you explain this
as well?
I'm currently evaluating Portal on my local workstation, so there is no
other physical
server involved at the moment.
Thanks again,
Frank
"Michael Goldverg" <[email protected]> wrote:
Good news, issue is RESOLVED.
Several things need to be done:
1. Copy p13n_util.jar to the WEB-INF/lib directory under the datasync
webapp,
which
is used as a proxy. This needed to be done because of the problems with
the class
loader.
2. The BEA Deployment guide has several discrepancies, so the parameters
fo synchronization
with managed servers should be defined for the webapp itself, not forthe
servlet.
This could be done using the deployment descriptor edit from theconsole.
Also, the
document states the name for URL parameter as "notifiedURL" (incorrect),
should be
"notifiedUrl".
3. In the startup parameters for the WLPortal server, running the proxy
datasync
application the following parameter should be added:"-Ddata.sync.jdbc.master.dr=true".
4. Finaly, the datasync connection pool and TX datasource should bedeployed
on all
servers (sync server and managed servers).
It took us 2 days to figure this out, but it works well now.
Regards,
Michael Goldverg
"Frank Wang" <[email protected]> wrote:
I have the same exact problem as the previous poster. I created a
brand
new domain
called "ddDomain", and made a new enterprise app
called "scdd". Within it, I created a simple webapp also called"scdd".
Here's
my folder structure:
ddDomain\applications\scdd\
pipeline.jar
p13n_util.jar
scdd\
index.jsp
welcome.jsp
WEB-INF\
web.xml
weblogic.xml
lib\
webflow_servlet.jar
webflow_taglib.jar
datasync\
(datasync files copied from\bea\wlportal4.0\applications\p13nApp\datasync)
META-INF\
application.xml
The following are my settings:
ddDomain\applications\scdd\META-INF\application.xml:
<module>
<web>
<web-uri>datasync</web-uri>
<context-root>scddDataSync</context-root>
</web>
</module>
ebcc > Connection Settings > Connection Details > Data Synchronization:
/scddDataSync/DataSyncServlet
WLS starts up fine, and I know that I am hitting my "scdd" applicationfrom
the browser
(http://localhost:7501/scdd) since the
index.jsp file was compiled.
When I use the ebcc to synchronize (ebcc > Tools > Syncrhonize...), I
get
the following
exception in WLS:
<Jun 5, 2002 6:01:05 PM PDT> <Info> <Management> <Configuration changes
for domain
saved to the repository.>
<Jun 5, 2002 6:02:56 PM PDT> <Info> <NT Performance Pack> <Allocating:'2'
NT reader
threads>
<Jun 5, 2002 6:02:58 PM PDT> <Error> <HTTP>
<[WebAppServletContext(14774279,datasync,/datasync)]
Error loading servlet:
'DataSyncServlet'
java.lang.NoClassDefFoundError:com/bea/p13n/management/data/message/MessageExecutor
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
atweblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
:665)
atweblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.ja
va:643)
(stack trace left out...)
After a bit of looking, I discovered that the MessageExecutor classresides
in p13n_util.jar.
I tried adding this file to the
scdd\WEB-INF\lib directory, but that didn't work. I also trieddeploying
it as an
EJB, that didn't work either, and gave me the
following error:
<Jun 7, 2002 11:25:39 AM PDT> <Error> <J2EE> <Error deployingapplication
pipeline:
Caught IOException for path=:
C:\bea\wlportal4.0\.\config\petflowDomain\applications\.wlnotdelete\wlap1
5174\pipeline.jar>
Per tip of Mr. Daniel Selman in a previous posting, I tried deployinga
number of
other jar files found in
\bea\wlportal4.0\applications\p13nApp, but they all gave me WLS
exceptions.
>>>>
I am evaluating Portal/Webflow for my company, and would like thisresolved
asap.
The documentation is very poor and lacking a
beginner's step-by-step guide.
-Frank
=============================================
"David Anderson" <[email protected]> wrote:
Synchronization is accomplished using the DataSyncServlet that needs
to
be
deployed as part of you enterprise application in the datasync web
application. If you have more than one enterprise application
deployed
to
the same instance of Weblogic Server, you need to make sure that thecontext
URI for the datasync web application is different for each of the
enterprise
applications.
In your application.xml file there should be an entry as follows:
<module>
<web>
<web-uri>datasync.war</web-uri>
<context-root>portalDataSync</context-root>
</web>
</module>
Make sure that the <context-root> element is different for each of the
instances of the datasync application. Additionally, you should checkyour
synchronization connection settings to make sure that the Data
Synchronization setting is pointing to your context root. You can
check
this from the EBCC using Tools->Connection Settings selecting the
connections tab on the resulting dialog box, selecting one of your
connections, hitting the edit button and then the advanced button.
You may need to clean out the database in order for thesynchronization
to
work.
Dave
"Markus Lutum" <[email protected]> wrote in message
news:[email protected]...
Hello.
My team has problems using the Portal 4.0 with WLS 6.1 SP1.
We copied the p13n Domain and rename the Domain and the Server.
When we then syncronise one of the sample webflows with the new
server,
all
works fine.
Then we add our very simple application with 2 jsps (one with a
webflow
form
that fires an event that is configured to switch to the second one)
on
the
same Domain/Server.
When we then want to syncronise the EBCC could not connect
(errormsg:
Authorisation denied. Check User/pass and ensure server running)
Can someone help us?
Must we add some tables inside the cloudspace database or is thisdone
automatically?
Where is the relationship between the database and the application
configured?
Is there a simple tutorial from A to Z how to set up a new Domainand
Server
ready for webflow / Code and deploy a simplest application /
configure
webflow with ebcc.
I need a all steps included tutorial to give this to my developers.The
e-docs are great but it is dificult to collect all pices together.
If someone has a finished configured simple webflow application
please
send
it to me together with the domain config xml.
Thanks a lot!
Markus Lutum
[email protected]