Is there an advantages converting SBO to DFS Pojo service

Abhay

Hello All,

We are currently on 5.3 and are migrating to 6.5 now. We are planning to migrate the exisitng Web services and SBOs (not exposed as Web services) to DFS.

We have a recycle bin functionality, which uses an SBO. I would like to know whether there is any advantage in converting the SBO to a DFS POJO service. To my knowledge,  when ever there is a code change, if its an SBO, the deployment is only on Content Server and all the client applications will get the updated code by means of BOF refresh, which if taken care by DFC. In case of DFS service, we need to deploy the re-built remote jar on all the client applications accessing the service.

We have two types of interfaces to Documentum - WDK applications (Webtop & DA) and J2EE applications which invoke Web services (DFS in future).

I understand that WSF, DFS are a level above the SBOs and are used to implement Service Oriented Archicture, and a comparision with them might not be conclusive and effective. I just want to know from experts whether there would be any advantage by converting SBO to DFS in future with the developments happening in Documentum.

Appreciate valuable suggestions

Kumar

Francois Dauberlieu

I'd say it's the other way around.

If you convert your SBO's/TBO's to DFS specific stuff, that means you will only be able to use them with DFS.  So in the future, if you also want to support some other consumer, you'll have to redevelop it.

The other way around, the SBO's/TBO's are available without too much effort to any consumer, including DFS app's

My 2 cents