Different ways to transport SAC Content
SAC Provides three ways to transport your content from one tenant to another,
File System mode - In this method, using the menu option Transport > Export > File System, you create a package of your SAC content & its dependencies and download it to your local system in a .tgz file format, and import this .tgz file in your destination environment using the menu option Transport > Import > File System. This option is as simple as downloading from one location and uploading to another location.
Second option is using the Content Network method, you can navigate to the Content Network tab using the menu option Transport > Export > Content Network Storage. In this option similar to the earlier option you create a package with SAC contents and all its dependencies. The package created under this option is not-downloadable like in previous option. Once the package is created, you enhance its properties by giving it a name and description and assign required access to it ranging from Read / Write / Full Control, if you want to later on check the contents of the package or edit the contents within it. You can then assign a destination it to the package, the tenant environment to which you want to export the contents. Once exported, the package will be available in the destination environment under location Transport > Content Network Storage, from where you can seamlessly import it in your destination environment.
However, in this blog, we are going to check the third option of exporting SAC content, i.e. using Cloud Transport Management System, abbreviated as CTMS.
Pre-requisite for Transporting content using CTMS
To transport your package using the CTMS, a pre-requisite is that the CTMS needs to be installed in backend and integrated with SAC.
Once integrated, you need to define the transport routes...meaning define how the transport package will flow from the source environment to the destination environment.
On Successful integration of CTMS with SAC, you will see an option to upload package to CTMS will be added within the SAC interface like in below screenshot
This covers the existing options provided by SAC to transport, the Pre-requisites to use CTMS, and options post successful integration of CTMS with SAC.
Let's now look at how to transport using CTMS
Opinion,
In my personal opinion, I feel the current version of CTMS is still very basic.
If you are already using CTMS in your SAC Project, please share your experience with the tool in the below comments section.
Sujit Honrao
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 |