[DFC_BOF_CANNOT_FIND_OBJECT] Business object com.documentum.xforms.docbase.IDctmAdaptorService does

Hi,

I logged into Forms Builder with docbase "testdoc" and did File ->Adoptors. I got the following ERROR: (Screenshot attached)

[DFC_BOF_CANNOT_FIND_OBJECT] Business object com.documentum.xforms.docbase.IDctmAdaptorService does not exist in docbase proddocError when retrieving adaptor configuration SBO.

I think it is related to Global registry, which is not properly configured in our environmrnt. Also you can note that the error message is referring to docbase "proddoc" which is supposed to be global repository (but it is not configured properly). Also I did not install "Unique Number Forms Adaptor" in the docbase "proddoc". Am I required to install the same in 'proddoc' too to get it function properly in 'testdoc'? If I do not instll in 'proddoc' at this time, does it effect the functionality in 'testdoc'. I don't think so because I still get the "Adoptor Configuration Manager" Window (atached).

If you have any comments, please let me know.

Please share your knowledge and experiences for figuring this out.

Thanks.

Adoptor_Configuration_Manager.docx

DFC_BOF_CANNOT_FIND_OBJECT.docx

Find more posts tagged with

Documentum

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

DCTM_Guru

My statement assumes that you will have 3 different global registeries for 3 different environments. You could potentially have only 1 global registery and have that be accessible to all 3 environments, but that means that you would have to docbrokers projecting from the source environments to the other environments. Once you do this, then if you are using OOTB app, you will see the other repositories on the login page.

This can confuse users, which is why we dont try to project docbases to other environments than its already in.

All comments

DCTM_Guru

SBOs are deployed from global registery. So, you need to fix this first.

athati

Thanks Johnny.

We have three (3) AIX boxes for three Content Servers (Dev, Test and Prod). On each Content Server we created one docbase as follows:

Docbase Name Content Server Environment

devdoc hqdev25 Dev

testdoc hqtest25 Test

proddoc hqprod25 Prod

We are using the following dfc.properties file:

dfc.data.dir=C:/Documentumdfc.globalregistry.password=6HEYuqBk0/4=dfc.globalregistry.repository=proddocdfc.globalregistry.username=dm_bof_registrydfc.registry.mode=windowsdfc.search.ecis.enable=falsedfc.search.ecis.host=dfc.search.ecis.port=dfc.session.secure_connect_default=try_native_firstdfc.tokenstorage.dir=C:/Documentum/apptokendfc.tokenstorage.enable=falsedfc.docbroker.host[0]=hqprod25dfc.docbroker.port[0]=1489dfc.docbroker.host[1]=hqtest25dfc.docbroker.port[1]=1489dfc.docbroker.host[2]=hqdev25dfc.docbroker.port[2]=1489

Do you think we can setup a docbase on one Content Server to be global to another docbase on another Content Server? I think we cannot. I also think the way our environment is setup, does not have global registry and we cannot have one. Therefore we need to remove the three(3) lines (starting with dfc.globalregistry....) need to be removed. I am not sure I am right. I need your input.

Please advise me.

Thanks.

DCTM_Guru

Global registery can be the same repository as the one you are developing are. We do this all the time in DEV.

athati

Thanks Johnny.

I could not understand clearly. What I understand about the global registry is as follows:

If a Content Server has more than one repository, one of them can be setup as global and any BOF modules like SBOs/TBOs can be accessed from all other repositories even if they are installed in one repository.

Our environment has three(3) repositories on three(3) different Content Servers. Do you think I can setup one repository (say 'proddoc' as mentioned in dfc.properties file above) to be global to other tw (2) repositories ('testdoc' and 'devdoc') which are on two(2) different Content Servers?

Your response:

Global registery can be the same repository as the one you are developing are.  We do this all the time in DEV.

I think if I am not wrong, you are trying to say that:

'proddoc' can be global to itself. This is the only repository on Content Server (hqprod25)

Similarly 'testdodc' can be global to itself and 'devdoc' can be gloabl to itself too.

Right!!

Thanks.

DCTM_Guru

This can confuse users, which is why we dont try to project docbases to other environments than its already in.

yamangoyal

Generally it issue comes when Global repository is not configured.

You can try reinstalling dar files.