Import export service for fully scaled environment

Question

We have fully scaled CM environment with 6 CM servers. We are trying to implement utility to export specific schema from source to destination and perform the content synchronization at destination. For moving schema from source to destination, we are trying to use ImportExport service.

The problem that we are having is,

when we perform export using ImportExport service the export package is created on either of 6 CM servers so there is no way to identify where package is created so we can't pass it to import. Same thing is happening for import as we are not aware of the server which will be connected for import and package may not even be available there to the server connected.

How can we resolve this issue? Is there any way we can specify the package location to be available to both source and destination servers.

Approaches that we have tried till now and outcome of the same:

1. Tried to connect to individual CM server on source and destination: Since, CME is running SSL as per client requirement and SSL certificate is for load balanced endpoint, can't connect to individual server as it gives SSL/TLS error.
2. Provided shared location on the server to export the package and use the same shared location for importing the package: With this approach no way to find the location of export package i.e. on which of the 6 server it got created and also during import it is not able to locate workingDirectory and import fails.
3. Generate the export package then manually copy it to all 6 destination servers for import and then run the import process and then clean up destination location: This is not the preferred approach.

Answer 1

Since there is no other approach available to handle the mentioned scenario.

We went ahead with approach 3 "Generate the export package then manually copy it to all 6 destination servers for import and then run the import process and then clean up destination location: This is not the preferred approach."

Answer 2

Hiren. I suggest you to chose second option and use shared folder for exporting/importing packages. Here example of my configuration for ImportExport in the TCM configuration. Probaly on your system workingFolder(in the ImportExport element) is missed or linked to non-shared folder.

<importExport maxProcessCount="1" workingFolder="C:\Program Files\Tridion\ImportExport\Temp" processLogLocation="C:\Program Files\Tridion\log" transactionTimeout="0" userReplyTimeout="3600">
<export threadCount="1" packagesLocation="C:\Program Files\Tridion\ImportExport\Packages" />
<undo undoPackagesLocation="C:\Program Files\Tridion\ImportExport\UndoPackages" />