Create new Documentum environment using current data - urgent

All -

I have a rather urgent issue that has come out of the recent government hacking incidents.

We have a directive to change all service account owners to conform to a naming and password change standard. This is supposed to be accomplished by the end of this week (July 31).

I started down the path of changing the Documentum install owner in our Development environment, only to run into a number of issues. I opened a ticket with Documentum and was told that changing the install owner is no longer supported (after 6.6) and that the steps I was following would only work in a "plain" content server install. We have ADTS, RPS, RM, PRS, xPlore 1.4. We're on 7.1 (Windows Server 64-bit).

Is there any way to create a new instance of Documentum with a new user and then move the data over? I've done the clone thing before, but that requires that you use the same install owner.

Any help would be much appreciated. There have to be other Government installations out there running into the same problem.

- Jane

Find more posts tagged with

Comments

rouset

Jane,

Since the "Change Installation Owner" procedure is no longer supported I believe that an "ETL" or "Extract-Transform-Load" approach may be necessary. That is, I believe that you will need to create a new standards compliant repository and then use a tool to extract the objects and reload them into the new compliant repository.

A few questions:

(1) Do the target usernames meet the standards for a repository? I remember those are in the Installation Guide and/or the Administration Guide.

(2) What size are the repositories?

(3) Does the xPlore Administration credentials also need changing?

(4) Are you using LockBox?

This partner product is quite adept at this type of transformation.

The migration-center content migration platform: | migration-center.com

If you seek more counsel, please contact me privately via the email link.

Tom

PanfilovAB

If we are talking about security, the changing name of installation owner does not make sense (anyway I do believe that performing direct updates in database is more straightforward way rather than using any migration tools or dump/load) because, being the only one person who understand security in Documentum, I can say without any doubts that figuring out the name of installation owner takes a couple of minutes . More than 3 years ago we requested EMC to create a special status for dm_user's which must allow certain users to authenticate only by login tickets, but nothing has been changed . However, if you want to disable password-based authentication for installation owner it's enough to set user_source to "inline password" and leave user_password blank (you also may create database trigger to prevent further modifications)

Mudgal

Jane

You can easily change password for ADTS (Search Admin guide "change installation account password") We have inbuild utility to do this task .

Xplore will not be impacted by change in password as far i believe .

Regards

Mridul

Alvaro_de_Andres


jklawrence wrote:

All -

I have a rather urgent issue that has come out of the recent government hacking incidents.
We have a directive to change all service account owners to conform to a naming and password change standard.  This is supposed to be accomplished by the end of this week (July 31).


- Jane

This process is not trivial and it won't be done in a week no matter what a directive say. You can change the owner account by following the old procedure and then change every reference in DB/.xml/.properties/.bat files/windows registry/services to the new account. I've seen this done in a 6.7sp2 but it was something planned with months in advance and thoroughly tested in dev.

I think reinstalling everything will be harder/more time consuming unless you don't have many objects in the repository (let's say a couple of GB that a dump could take "easily")