Move all data from one installation to another installation with the same/ different org-env-port combination

[asurajpai]

Hi, We have two installation 1) 2 node installation for test purposes --Test Landscape – As Standalone installation with analytic component on separate box as per installation guide. 2) 5 node installation for production purposes - Production Landscape – As cluster installation as per installation guide. The application team challenges on transporting changes from Test Landscape to Production Landscape as they have different organisation and environment set ups... which would be challenging to transport changes from Test to Production landscape. Can you please suggest a way to export on one test landscape and import to other production landscape aligned with the org-env-port changes. I have seen the link https://community.apigee.com/articles/2093/how-do-... which is not of help in this case. Please let us know the details and commands on a linux box on how to export and import reflecting to the target environments. BR, Suraj

[gnanasekaran]

Hi @asurajpai, what are you trying to transport? the APIs? - is it part of your sdlc? All the data in the edge is accessible thro APIs, so for eg, even if you have 2 apigee installations and 2 different org/env - you can easily write scripts to promote / transport data b/w the 2 For eg, you could access the APIs in the test env like, http://mytest-host/v1/o/mytestorg/apis for production you could import your APIs http://myprod-host/v1/o/myprodorg/apis You can find the documentation for the APIs here, http://apigee.com/docs/management/apis You could also take advantage of the https://github.com/apigeecs/apigee-migrate-tool, there is a configuration to specify 'from' and 'to' Thanks,

[#3]

What about the ability to "move" keystores from one installation to a replacement installation? As far as I know there's no API way to fully export a keystore (private key in particular). Is there some other method to move keystores?

[gnanasekaran]

No, it has to be managed by the clients. Its not a good practice to be able to export keystores from a security POV