Design and Build LTM

We are in the midst of our implementation of LTM and we ask the same question of managed services.  We were told that there can not be a copy of TEST to production. 

We have been able to copy production down to Test (done some preliminary setup in PROD).  Also, we have been able to migrate configurations across test database areas.

 

Thanks

Karen

Hi KW,

I'm not sure what value there is to copy the build from TEST to PROD because of the way the deployment works in Landmark where everything is deployed from svn every time. If your TEST and PROD environment and apps are on the same version level, then the deployed builds should be identical. If they aren't the same, then you need to match them up in svn first (or have AMS do it) and then deploy.

However, you can use Spreadsheet Designer to dump configuration from TEST and upload to PROD. You could also use the command line tools, but they are pretty clunky. You also have to be VERY CAREFUL what you dump and load since many business classes have unique ID relationships, so you have to be sure to copy everything that is related.

We've found that our environment configurations between our environments are never exactly the same - particularly our services and endpoints. There really isn't any way to "copy" those - they have to be configured correctly for each environment.

What exactly are you trying to accomplish through the copy?

I believe the purpose behind doing the copy is to save the time with rebuilding the entire Production system again and building time in the Project plan to accomplish this task. Did you build your LTM Productline separate or at the same time in a test and production servers? The plan is to keep both the test and production system equal with Landmark and GHR versioning.

We set up out PROD box later than our TEST box, but it was still well before our go-live date, so we had plenty of time to upload and validate configuration, services, and endpoints. Of course this only works for an initial Landmark implementation.

If you are upgrading, then you really don't have any option but to upgrade the PROD server and then upload or enter the new configuration data after the upgrade. Since the Environment, Application, and DB are all closely tied to the svn repository and build, there isn't any way to just do everything in TEST and then copy it over to PROD. It just doesn't work that way.