Two approaches to moving objects between AE systems
- Select objects, e.g. via the Transport Case in the User Interface or the TransportObject API class.
- Unload objects using AE DB Unload program, ucybdbun.
- Change objects using AE DB Change program, ucybchng.
- Load objects using AE DB Load program, ucybdbld.
- Select objects, e.g., in the User Interface or using the FolderList API class.
- Export objects to XML file, e.g., via the Export function in the User Interface or the ExportObject API class.
- Change objects in XML file, e.g., using XSLT.
- Import objects from XML file, e.g., via the Import function in the User Interface or the ImportObject API class.
Pros & Cons of each approach
Our current system for promoting batches between staging environments is based on the transport case mechanism. For a while now, we have been looking into the possibility of moving away from this approach, and switching to an approach based on XML. Before we put too much effort into this transition, I thought it wise to ask the broader community for input.
- Has anyone switched from using the transport case to XML for batch deployments? How did it go? What did you learn?
- Has anyone performed benchmarks to compare the relative performance of the two approaches, and to measure the load each places on the AE/DB?
- How might it be possible to mitigate the disadvantages of the XML approach?