Import of Folders and Database/Workspace Items
Every object in an ASCET database or workspace has a unique identity tag, and is known to the database/workspace only by this identity tag. Database/workspace items reference each other only on the basis of these tags, not on the basis of the names displayed in the Component Manager.
You can import from one or more export files of the following formats into your database.
Binary export file (see Binary Export) | ASCET Export files (*.exp,*.prj) | |
AMD export file (see AMD/AXL Export) | ASCET Model Data files (*.main.amd, *.main.xml) | |
compressed AMD export file | ASCET compressed Model Data files (*.axl,*.zip) | |
AUTOSAR component description files | AUTOSAR XML files (*.arxml) | see also Special Features of the ARXML Import |
ASAM-MCD-2MC project | ASAP2 files (*.a2l) |
Note |
|---|
When you are using a workspace, you cannot use the binary export format for import. |
The folders and items required are created automatically. You are prompted for confirmation when an existing item is overwritten by an imported item.
Besides the components themselves, the export files also store the component paths in the exporting database/workspace. If an imported item is located in a folder existing in the target database/workspace, it is written into that folder. If an item is located in a folder in the source database/workspace that does not exist in the target database/workspace, the folder is automatically created. If necessary, several levels of folders are created. The folder hierarchy is recreated as it exists in the source database/workspace.
When an item is imported that already exists in the target database/workspace, the existing item is overwritten, unless it is protected (see Disallowing Overwriting of Items). Renaming offers no protection against overwriting because items are identified by their object IDs or UUIDs, not their names.
If an imported item overwrites an existing item, the behavior of existing implementations can be specified in the import options. When you activate the Discard Existing Implementations option, all existing implementations are replaced by imported implementations. To keep existing implementations, Discard Existing Implementations must be deactivated.
With ARXML import, the import option Use UUIDs for Identification ensures that, if no OIDs are available, UUIDs are used instead of names to identify components in the database/workspace. The import option Platform Types must be used to specify the package for platform implementation types.
With EXP import, you can specify the target database path for an imported item overwriting an existing item. When you deactivate the Keep Folder Path of Components option, the imported item is stored at the export database path, even in case it is stored in a different folder in the target database. To keep the existing path name, Keep Folder Path of Components has to be activated.
Before you import folders or items, set the import options in the ASCET options.
You can
Import from binary export files
Import from ARXML or A2L files
Use the AUTOSAR to ASCET Converter
See also