cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Documentum WDK integration - Impossible to import trough Epic

Newbie

Documentum WDK integration - Impossible to import trough Epic

Hi everyone,

I have a document that is located in a folder on my file system. In that
same folder I have the DTD. If I open the XML file in Internet Explorer
it does validate.

If I import the XML Document trough Webtop it works!!!

If I open the XML document in Epic and connect to the WDK Adapter. Once
connected I browse to the location I want to import and select
Documentum-> Create New Object menu.

Then the "Epic Repository for Documentum/WDK Browser" window get the
focus and shows the import process but the browser hang at the label
"Determining XML App category list...

Which makes it impossible to import trough Epic.

I have Webtop 5.2.5 SP2 with IE 6 and JVM 1.4.2_06

I have configured the JVM to show the console Icon but the icon never
appears while using the Epic WDK Integration.

Is the WDK integration use the WebBrowser VB control. If it is how do
you manage to use the Java VM since the control is Hard coded to use the
Microsoft VM (no longer available) ?

Thanks

Best Regards,

Patrick Lemieux
InterDoc


Tags (2)
1 REPLY 1
Highlighted

Re: Documentum WDK integration - Impossible to import trough Epic

The WDK integration is pretty new so I doubt that many people on
Adepters have experience here. Sounds like you will need to go to our
support site pretty fast.

Regarding the Java console, you can get to that using the Tools menu
when full menus are enabled.

I think you are asking if the WDK using the Web Browser control also
known as shdocvw.dll. I am not sure if we are using this directly or if
we are using something that wraps it, but yes we are using it. I believe
that this control uses exactly the same Java Virtual Machine as the
version of IE running will use. I believe that this control and Internet
Explorer share a common foundation for persistent properties so things
like the JVM as well as proxy settings, certificates, and much else is
automatically shared between them.

John Dreystadt
Director of Product Management
Arbortext

Announcements