Point def LSF9 env to prod LSF9 ADAM ldap?

I would definitely not recommend this at all. If you repointed it, anyone working in your dev environment could screw up your production ldap. Think about it all the conflicts with your production ldap and dev environment, do you really want that?

 

Why not make a copy of your production ldap and point the copy to the dev environment.

Totally understood, however resources are in short supply and I'm being assured that this would only be a temporary situation with only a few select people with access to do this.

Both ideas would not work, due to the internals of what is stored. Cloning is one thing, and I have done it....What is being attempted would never work, as is.

The bigger issue, is why?
A fully populated ADAM instance, with 300,000 users, and a large LS deployment is about a 1 gig on disk. I'm sure there is only one client in this position. Since that couldn't be your position, ADAM wouldn't take any resources, any serious memory, any serious disk space. Just setup another instance. Even if on a PC.


Kwane

Thanks very much for the feedback. The "resources" I spoke of are "human". Because of separation of duties, I've got to convince another group to execute it, but it is not a long process. I have been able to locate an ADAM install document for LSF9 which describes installing an ADAM instance for Multiple Environments. Looks as if some pre-planning and additional tasks needed to be executed on the initial ADAM install. If I was able to get the additional tasks executed now, after the initial install, would this work, or should I safely request a brand new instance?

I see what you are intendnig to do...you want to resue the INSTANCE, and not the DATA from the PROD environment. Due to the simplicity of installing ADAM, and the potential need to restart the DEV environment, independent of PROD, I would use a seperate INSTANCE. If we were talking sharing with TEST, it'd be a slightly different story.

I *JUST* installed ADAM for an installation, and it took 11 minutes total. That includes install, user account creation, DR preparation, schema preparation, and hardening. I didn't use any LDIF or scripts. All by hand.

Kwane