IP Protection Procedure
The procedure to create and exchange IP protected components contains the following steps.
- Both partners must deactivate external code storage.
- Before transferring an IP protected model to a development partner, a rebuild has to be executed with full access rights for the modules and classes which are to be exchanged.
- After that, the access rights, except Execute, for these components can be disabled.
Export the protected components in the *.exp format.
AMD/AXL export does not include generated code.
Note
Non-protected components must not be included in the export; these would enforce code re-generation after import. Deactivate the Include Referenced Items export option to avoid accidental inclusion of unprotected components.
Old versions of the components in the partner's database must be deleted.
Overwriting write-protected components is not possible.
- The protected model can now be imported in the partner's database with the same project.
The project can be rebuilt.
Note
Rebuilding the project can only work when both partners use the same ASCET version (see Preconditions for IP Protection).
See also
Preconditions for IP Protection
ASAM-MCD-2MC Generation for Protected Components
Changing the Access Rights to a Folder or Item
Exporting a Folder or Database/Workspace Item
Importing from Binary Export Files