nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Documentum 4i migration (yes I said 4i)

richard2010

Old system is 4.2.6 on Solaris 8 with Oracle 7/8? for DB

New system is 6.7 on Server 2k8 R2 with Sql 2008R2

I have purchased Buldoser and have successfully connected it to the old repository using DFC 5.3 and I have connected it to the new repository using DFC 6.7

Problem is I can't get both to work at the same time.

If I have 6.7 installed, it won't connect to the 4.2.6 repository

If I have 5.3 installed, it won't connect to the 6.7 repository.......

Yes, this is all way above my expertise level (Only been working in Documentum about a month now, but I have been to both the Technical Fundamentals and Administration courses from EMC).

Any tips or suggestions to point me in the right direction?

Find more posts tagged with

Comments

MohdWasil

go through Documentum System Migration Guide 5.3.x may be helpful...get it through powerlink..

Through Buldozer you can connect to one docbase at a time .Once content has been extracted batch folder you need to connect to target docbase and then loading from buldozer will take care ....also just have a look at Bulldozer User Guide....

lastnitescurry

Best of luck Richard, I have not used Buldozer there are other options that may connection to 2 repositories at same time

http://www.google.co.uk/search?q=documentum+repository+migration+tools

http://www.tsgrp.com/Open_Source/OpenMigrate/open-migrate.jsp

https://community.emc.com/thread/104809

msroth

Here are some other things you that might be helpful: https://community.emc.com/docs/DOC-1713. Other migration topics can be found here: http://msroth.wordpress.com/research/.

I have not used Bulldozer but have used a competing product. We had a similar situation and had to have both the DFC for 6.6 and the DFC/DMCL for 4i loaded on the same machine but isolated from one another.

richard2010

I may be new at this, but I can google like a mad man…..

I figured out how to get it connected to the 4.2.6 repository. Only problem is that once I get the system configured to connect to the old repository, it will no longer connected to the new repository.

It comes down to DFC versions. DFC 5.3 will connect to CS 4.2.6 but not 6.7. DFC 6.7 will connect to CS 6.7 but not 4.2.6.

Apparently Buldoser support thinks I should be able to do this with one version of DFC.

From what I've been reading, DFC 5.3 should connect to at least a CS 6.5 (latest as of the article I was reading), so I wonder if it should be able to connect to 6.7?

What I've been doing for now is testing how to pull down parts of a cabinet from the 4.2.6 then install dfc 6.7 and start the mapping process in the new repository. Not extremely efficient, but it is working so far.

DCTM_Guru

Ver 4i and through 5.2.5, Documentum uses dmcl dll and not DFC

Ver 5.3 and uses DFC

So what you are saying about not being able to connect to 4 and 6.7 simultaneous sounds about right.

richard2010

That's what somebody else told me. But my app will not connect to the 4.2.6 until I install DFC 5.3.

If 4.2.6 doesn't use DFC then does the 5.3 DFC install add something else beside just DFC?

richard2010

Just found this old DFC 4.2.16 documentation....

http://www.scribd.com/doc/12405977/DFC-4216-Patch-Release-Notes

Down in the document it states that DMCL gets installed with the DFC 4.2.16 setup. I'm left to assume something similar is hapening with the 5.3 install that must not be happening with the 6.7.

Francois Dauberlieu

Yeap, you're right

lastnitescurry

DFC 6.7 should be backwards compatible and work with a 4i repository. I say should, if it is not then it is an EMC bug and you need to raise a case with Tech Support, you are on your own as EMC have made no claims for it to be supported. For sure you can not do fancy new stuff like aspects or tbos in the 4i repository.

Personally I would do the following.

a) Project the 4.2.6 docbase to the docbroker on the 6.7 host.

You can do it administrator but I perfer the hardcoded way of modifing the server.ini file, that will be in folder

$DOCUMENTUM\dba\config\<repository name>

and you will need to add something like

[DOCBROKER_PROJECTION_TARGET_1]
host = dctm4ivm
port = 1489

After editing server.ini you will need to stop and restart the repository. Use DA, to change docbroker projections, if you can not stop & restart

b) Verify the 4.2.6 repository can be accessed via the 6.7 host applications, i.e. the Administrator client DA

You should have access to basic administration facilities, which rarely change, for example Jobs, viewing reports, editing properties and running.

If you can not connect then get onto your network people.

Assuming a & b are working then you can connected to either repository with the tool of your choice.

If you want to get very fancy or are not allowed to project the 4i repository to 67 content server docbroker, then take the docbroker program and run it on a seperate 3rd server which has network access to both content servers. Then project both repositories to this new docbroker. Suggest you would install Tomcat and DA on this 3rd party server, so you can test your setup.

Message was edited by: Brian Dinneen

DCTM_Guru

"DFC 6.7 should be backwards compatible and work with a 4i repository"

Brian, why do you think this, since all the documentation says it is only supported against 5.3 servers and above? EMC is going to tell you the same thing since 4.2 is not officially supported.

lastnitescurry

Why? It was guess, based on 4i & 5x dmcl being pretty much the same.

Yes 5x does have new features but at is core it still uses the dmcl dll.

5.3.sp6 is a different beast as it is based on the 6x DFC technology which removed the dmcl dll and went to pure java.

Odds are EMC testers have not tested a 6x DFC against 4i repository for practical time consdieration reason. Not for any lack of support.

As the documentation does not same 4i interaction is supported, then it is a waste of time to raise a tech support case if it does not work.

If it was me, I would still do as I proposed.