getDocbaseACSConfig exception

paul_wms · 2021-05-26T17:29:41+00:00

There was an error rendering this rich post.

Using the DFC Java API to copy documents from between docbases, we are getting an exception during new document checkin in the target docbase:

exception.txt

The object ID in the exception message is an ACS Config object from the other docbase, i.e., the source docbase. We have sessions open for both docbases at the same time which have the same docbase ID and it appears that the DocbaseAcsConfigFactory.getDocbaseAcsConfig() method is getting confused trying to get the ACS Config for the target docbase.

Has anyone else seen problems in the DFC API with sessions open simultaneously for docbases with the same docbase ID? Is there a work-around we can try?

Find more posts tagged with

Comments

DCTM_Guru

I dont believe this is supported - having source and testing docbase with same docbase ID. If you are trying to copy documents from one environment to another (e.g. PRD to DEV), you will need to export it out to temp storage location and then import them into target docbase.

How many files (and total size of content) and is this one-time reoccurring process?

paul_wms

I'm using streaming to copy content from the source to the target without intermediate files, so I need both sessions open. There are 20mil+ docs and the client wants to be able to use this custom tool again but the future scenarios are not yet clear to me. I think you're right about it not being supported, was just wondering if there was a work-around. I'm asking them to rebuild the target with a unique ID. Thanks Johnny.

Hicham Bahi

What exactly are you trying to do? How many documents are in the source docbase and is the target docbase empty? Perhaps cloning the docbase might be a solution ?

paul_wms

Thanks for the suggestion, but we are doing type conversion, attribute translation, and even some structural modification as well as content migration, so a custom tool was developed and tested successfully. That is until we tried to run it between docbases with the same docbase ID. So, we have decided to rebuild the empty target repository with a unique ID, which will solve the problem.

DCTM_Guru

@paul_wms - that is the supported path forward, since DCTM assumes that docbase ID are unique across customers as well as environments. The whole cloning of environments only came about when virtualization made it possible without too much headaches, but this requires cloning of everything and not "cloning" specific objects from one environment to the other that has identical docbase IDs.

MohamedYousuff

Can you retry after disabling ACS, just to check if that would work