Adding an MSO to Transport
Intended audience: DEVELOPERS ADMINISTRATORS
AO Platform: 4.3
Overview
The purpose of adding an MSO to Transport is to allow the MSO to be easily transferred to another server environment. Click the Transport icon :transport-tool: either on the MSO card view of all MSOs in the Ontology Composer or from the header during the configuration of a specific MSO.
By default, the MSO and all dependencies are included in the structure enabled for Transport. Using checkboxes, it is possible, but not recommended, to not include some or all of the dependencies, including:
Include all dependencies - this checkbox allows users to include all MSO dependencies.
Include property value synonyms - this checkbox allows users to include property value synonyms. Property value synonyms are typically implementation/domain-specific, so they may not be required to be transferred to another implementation.
Include statistics - this checkbox allows users to include statistics generated from the data sources connected to the MSO. This checkbox should only be selected if the target server environment has the same data. If the target server environment has different data, eg, a production environment, then Statistics should be re-generated on the target system.
Include suggestions - this checkbox allows users to include suggestions generated for the MSO based on the Discovery processes (Relationships, Words, Traits). Like with Statistics, the checkbox should only be selected if the target server environment has the same data. If the target server environment has different data, eg. a production environment, then the Discovery processes will most likely need to be re-run.
Include insights - this checkbox allows users to include the Insights created for the MSO.
Finally, it’s possible to add Common MSOs by clicking the Add Common MSOs button.
See Transport Tool for details on next steps.