OD 6.0 Datadeploy module, DAS and DB2

Hi everybody,

I've now been trying to get DAS working for quite some time, but for some reason this seems to be impossible. The part where the Datadeploy should collaborate with the Eventserver always fails. I am able to initialize the DAS deployment using the iwsyncdb script. This creates the tables and deploys the initial content. But if I then change a DCR entry -> nothing happens (no database update)!
The only error message provided by OD when starting the service is:
---------------
EventServer might not be running, please restart EventServer
SetContextClassLaoader
Could not create JNDI Context: javax.naming.NamingException: JndiServer [Root exception is java.rmi.NotBoundException: JndiServer]
EventServer might not be running, please restart EventServer
-------------
But as you can imagine, restarting the Eventserver effects NOTHING :-((

Sometimes submitting the dcr helps, but this is NOT what I want to do (if I would have to write data to the database only on submit I think it would be easier to write my own script instead of dealing with Datadeploy!).

Is there ANYBODY out there who has a running installation of DAS on a similar environment?
My environment is Win2000 SP4, TS6.1 SP1, OD6.0, DB2 8.2

Thanks,
Stephan

Find more posts tagged with

Comments

coschtl

Perhaps ANYBODY running the OD 6.0 Datadeploy connector with DAS and Oracle?

Migrateduser

I'm sorry this isn't a very helpful answer, but perhaps Tech Support can help you work through this?

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

coschtl

I already have a case on this.

I just thought that perhaps any other Interwoven customer got this configuration working and has some hints for me...

Regards,
Stephan

Migrateduser

Hi,
My guess is that the sequence of events is off in your case.

start TS server ( have the iw.cfg file configured for event subsystem)

start Event subsystem (Assuming all the event subsystem configuration are already done)
now you might need a iwreset -ui

now bring up OD 6.0..

IMPORTANT : check the log files to see if DD listner was able to register to event sub system.
the message you indicated in your previous posts indicates that the event subsystem was not up when DD listner was started.

thanks
srini

coschtl

Hi Srini,

thanks for the tips.
The error message I had posted was caused by a config error (I had activated the event reporting inside the DAS configuration but not inside the OD config file). Nevertheless DAS doesn't work as it should. The real problem in fact seems to be the event subsystem. In the meantime I noticed that DAS reacts on events like "rename" and "submit" but not on "Save DCR..."

At the moment I am in contact with senior support. Perhaps they can solve this...

Stephan

Ottawa_IWOV

Any update on this, I see them same error message in my od.log, however, I am not sure if it causing a problem either.

coschtl

The problem is a "slash-problem" on Windows.

Here is what I found out:
- using backslashes works for "submit", "rename"
- using forward slashes works for "save"

The only workaround for the problem is to use both, forward- and backslashes for all areas and combine them within an OR expression.

I had opened a support case on this and finally got the following result:
...Our Engineers have investigated this bug. Unfortunately we don't have consistency on vpath notation in events published by templating verses iwserver. iwserver uses forward slashes and backward slashes depending on the platform. Templating, which publishes the save DCR events, always uses forward slashes (regardless of the platform). This causes DAS to miss the rename and submit DCR events. Such is the symptom of this problem. The root cause is iwserver and templating need to standardize on the format of the vpath they use to publish DCR events.
This looks like a long-standing problem, which will involve some major restructuring of code to fix. Therefore it is being considered for TeamSite 6.7, or 6.5 Service Pack 2 at the earliest...

Nevertheless, I am not using DAS anymore because it has some other very serious bugs.

Regards,
Stephan

ruler

Hi Stephan
Can you pls post more details of how you resolved this issue.
Are you talking about the configuration files?
If you could post the piece of code that you corrected that will be of great help...Thanks!

coschtl

Inside the <od-home>/etc/daemon.cfg you have to configure the Events-Filter using forward AND backslashes, and combine them using an OR-expression, i.e.:

<filter name="EventsFilter">
<keep>
<and>
<or>
<like>
<field name="area" match="%default/main/branch_1%" />
</like>
<like>
<field name="area" match="%default\main\branch_1%" />
</like>
</or>
<or>
<like>
<field name="area" match="%default/main/branch_2%" />
</like>
<like>
<field name="area" match="%default\main\branch_2%" />
</like>
</or>
</and>
</keep>
</filter>

Adam Stoller

Hmm - according to the 6.0.2 DD Admin Manual - page 129:

Also note the use of forward slashes (â€œ/â€�). Since the area is a TeamSite area, forward slashes should be used even if TeamSite is installed on Windows. If you're sure you need to provide both types of slashes (for vpaths) - then you should contact Support and file a bug against the documentation (or the product if the docs are right and the product is behaving wrong)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

coschtl

My original post refers to OD 6.0 without service pack! And for this release the Support Team's statement is:

Our Engineers have investigated this bug. Unfortunately we don't have consistency on vpath notation in events published by templating verses iwserver. iwserver uses forward slashes and backward slashes depending on the platform. Templating, which publishes the save DCR events, always uses forward slashes (regardless of the platform). This causes DAS to miss the rename and submit DCR events. Such is the symptom of this problem. The root cause is iwserver and templating need to standardize on the format of the vpath they use to publish DCR events.

This looks like a long-standing problem, which will involve some major restructuring of code to fix. Therefore it is being considered for TeamSite 6.7, or 6.5 Service Pack 2 at the earliest

as you can see above...

I don't know if the problem still exists, because I am NOT using DAS (and the Eventserver) anymore because in OD 6.0 it still had a lot of "show stopping" bugs.

regards,
Stephan