Problem with connecting to two different docbrokers same docbase name

I wrote a stand alone DFC program to connect to two docbases with the same name, ID but projected to two different docbrokers. Here is how I am connecting to the docbases.

// *******************************// get session for Source Docbase// *******************************srcSession= connectToDocbase(srcDocbase, srcUser, srcPass, srcDocbroker);// *******************************// get session for Target Docbase// *******************************trgSession = connectToDocbase(trgDocbase, trgUser, trgPass, trgDocbroker);privateIDfSession connectToDocbase(String docbase, String user, String pass, String docbroker) throws DfException, Exception {try { clientX = new DfClientX(); client = clientX.getLocalClient(); if (docbroker != null && docbroker.length() > 0) { client.getClientConfig().setString("primary_host", docbroker); client.getClientConfig().setString("primary_port", "1489"); }IDfTypedObject serverMap =client.getServerMapEx(docbase, null, docbroker, "1489"); "i_host_name"); out.println("Host Name :" + hostName); IDfLoginInfo loginInfo =clientX.getLoginInfo(); loginInfo.setUser(user);loginInfo.setPassword(pass);this.sessionManager = client.newSessionManager(); if (sessionManager.hasIdentity(docbase)) { sessionManager.clearIdentity(docbase); }sessionManager.setIdentity(docbase, loginInfo); sessionManager.authenticate(docbase + "@" + hostName); catch (DfException dfEx) { out.println("Error connecting to the " + docbase " docbase. Swallowing this exception..." + dfEx + "\n Stack trace : "+dfEx.getStackTraceAsString()); }return sessionManager.newSession(docbase); }

The problem is that although it seems like it is successfully connecting to both docbases, it is really creating two sessions in the source docbase. It is not connecting to the target docbase at all.Can someone tell me why ?Here is the dfc.properties filedfc.docbroker.host[0]=aixxx1dfc.docbroker.port[0]=1489dfc.docbroker.host[1]=aix112dfc.docbroker.port[1]=1489dfc.bof.registry.repository=gfgfgfdfc.bof.registry.username=dmadmindfc.bof.registry.password=ghddf=dfc.session.max_collection_count=1000dfc.session.max_count=1000dfc.session.pool.enable=truedfc.session.reuse_limit=1000dfc.data.dir=C\:\\Documentumdfc.search.ecis.enable=falsedfc.search.ecis.host=dfc.search.ecis.port=dfc.tracing.enabled=truedfc.diagnostics.resources.enable = falsedfc.checkout.dir=C\:\\Documentum\\Checkout

Find more posts tagged with

Comments

DCTM_Guru

I dont think this is supported, since the docbase list would not be able to differentiate the two.

Begin T

Johnny,

Well, thats what I thought first too. But I had some hope after reading this thread. He had the same problem and got it resolved.

https://community.emc.com/message/97291

I am doing the same thing in my code except my code is D6, his might be 5.2.5 or 5.3

Begin T

Just to update everyone....I gave up on this !

Francois Dauberlieu

Fair enough.

Note that even if indeed somebody solved the same issue, at least for the Docbase name, he didn;t mention the Docbase ID, this is not supported, which is why EMC gives multiple Docbase IDs when you purchase Documentum.

I suspect the reason being that the docbase ID is used in the algorithm that generate the object IDs, for all objects.

In any cases, my personal point of view, and I emphasize on personal, is that it doesn't seem to me to be a good practice but hey, who am I to judge

Begin T

In my case, the two docbases have same name and ID.

As a work around, I am thinking of exporting to another docbase from the clone docbase, and then to the target docbase. Not the ideal solution, but seems like there is no way around it.

Begin T

Some more observations on this topic:

1) I have Samson on my computer. In the dmcl.ini file, I specified both source and target docbrokers (not sure if this is a good idea though). When I launch Samson, I see both docbases in the login screen. They are listed as docbase@docbroker1, docbase@docbroker2.I believe this Samson uses 5.3 libraries.

2) I also have a local DA 6.5. I tried the same test in DA, specified both docbrokers in the dfc.properties. But I see only one docbase in the login screen.

This raises the question whether the DFC version makes a difference. It (might?) work with DFC 5.3, but not D6 ?.

Any thoughts ?

Francois Dauberlieu

Actually, Samsom uses the olg DMCL libraries (even before EDMS98) which are not used anymore since version 5.* by Documentum as it has been replaced by the DFC.

So I guess you hit one of the big changes (and limitation in DFC) between DFC and DMCL but still as said before, same docbase Name and ID would most likely not be a supported configuration (if any EMC employee want to jump in to confirm or not....)

Begin T

I tested in Desktop client 5.3 SP3. I see only one docbase.

Francois Dauberlieu

Of course it does, DTC is using the DFC. As I said before, DFC is not DMCL (like the good old Workspace client for EDMS98 used) and it seems that DFC doesn't support this configuration