Composer: Possible to debug docbasic procedure?

Is there something equivalent to the Docbasic Editor in Documentum Composer that allows for testing/degbugging docbasic code?

Find more posts tagged with

Comments

foroor

Composer at this time does not package a debugger. However, we have had this request from some other customers and our Product Manager will review this need for a future release.

johan.philippe

Not quite correct that Composer does not include a debugger. There's a full debugger for Java included in the eclipse platform on which Composer is built. The part that is missing is to be able to attach that debugger easily with the running code.

foroor

I believe the question posted was about "Docbasic Debugger" not other languages such as Java.

Francois Dauberlieu

To add to Ramin's comment:

it makes sense that you can debug Java in Composer since it's one of the main purposes of Eclipse on which Composer is built.

Debugging DocBasic would be another story since it's really a language basic in itself, without the Doc) that Eclipse doesn't know meaning there would need to be a major extension to Composer or an external debugger, allowing connection to a docbase without necessarily installing the whole project.

Personally, I use a lot of logging in my Docbasic procedures tat when developing and debuging it, I see immediately in the logs what's going on (and wrong)

My 2 cents

DBerger

A docbasic debugger in Composer would be ideal. In absence of that, is there something equivalent to the Docbasic Editor in Application Builder that allows for running docbasic code in Composer? That would allow for the use of logging as suggested by Francois while editing the docbasic code in Composer.

Francois Dauberlieu

You could, on the Content server use dmbasic.exe

if really you need, you could copy it as well as the dmcl stuff to your Composer machine.

Chris_Campbell

If you happen to have a spare environment or PC laying around, you can always fire up 5.3 Desktop and use the DocBasic debugger there. No guarantees since you'll probably be hitting a 6.5 CS from a 5.3 client.

That being said, DocBasic (aka BasicScript from Summit Software) is pretty much VBA. Visual Studio might be able to debug it with some work. I know which .dll files need to be used with DocBasic. If I ever get the time, I might futz around with them and see if I can't get some kind of DocBasic debugger going. Howver, if I could get something going, I wouldn't be able to redistribute those .dll files. You would either have to already have them or have the ability to download 5.3 Desktop.

pwarren

Chris,

This is very interesting. Any insights you could share would be great. I probably have some time to investigate this if you can share your knowledge.

Many thanks

_Paul

Francois Dauberlieu

You could probably copy from DTC or DAB the Docbasic editor executable as well as the dmbasic.exe and the dmcl stuff (dll's and ini files) to another machine and get it to run from there. Note though that it's OLD technology using dmcl, not DFC and therefore, there won't be any handling of BOF's and this kinf of stuff

My 2 cents

Kothari

Hello Francois Dauberlieu,

1. Did you got chance / manage to set up docbasic debug enviornment ?

--> Can you share exact steps for the same ? setting docbasic debug environment ,

2. Still 6.5 DAB can connect to 6.7 repository and can use debug option for docbasic methods ?any one tried the same ?