This article describes how to migrate from SmartACT to Smart ID Identity Manager.
Prerequisites
| Expand |
|---|
|
This is a summary of what must be in place before the migration starts. More information is found in the article. - Java 8 Runtime is installed
- JRE_HOME is set as environmental variable
- java-security-policy-fix is recorded
- Databases are correctly registered in database.properties
- Run Data Encryption Certificate is provided and configured in encryption-config.xml
- Personalization is done correctly in migrate_persons.properties
- Configuration for cards/tokens is correct in migrate_cards.properties
- Certificates configuration is correct in migrate_certificates.properties (PKI only Card management)
- Smart ID configurations (for example, Base, Physical ID, DIgital ID) in the latest version are available
|
...
| Expand |
|---|
| title | General functions of migration, type conversion |
|---|
|
When mapping the person, type conversion rules can be specified for the fields in Identity Manager (see Type conversion for the person). A conversion rule is defined as follows: | Attribute | Definition | Example |
|---|
| fieldName | Field name in Identity Manager | Meta_CoreObjectState,
Meta_CoreObjectStateChangeReason, etc. | | conversionType | The following conversion types are supported: - NUMBER_TO_STRING
- NUMBER_TO_STRING_CONDITIONAL
- STRING_TO_NUMBER
- STRING_TO_NUMBER_CONDITIONAL
- DATE_TO_STRING
- STRING_TO_DATE
- BIGDECIMAL_TO_LONG
| NUMBER_TO_STRING: 104 → "104"
NUMBER_TO_STRING_CONDITIONAL: 104 → "active"
STRING_TO_NUMBER: "104" → 104
STRING_TO_NUMBER_CONDITIONAL: "one" → "1", "two" → "2", ...
DATE_TO_STRING: (refer to parsePattern)
STRING_TO_DATE: (refer parsePattern)
BIGDECIMAL_TO_LONG: SmartACT specific conversion of numerical values | | selection | A choice for the conditional conversion | 104 → "active" 105 → "inactive" | | parsePattern | Formatting pattern for the conversion type DATE_TO_STRING
or STRING_TO_DATE | yyyy-MM-dd HH: mm: ss.SSS |
|
...
| Expand |
|---|
| title | Relation between the objects |
|---|
|
When saving, the corresponding record (object) can be linked to one or more objects, for example: - Card with person
- Certificate with card and person
The desired relations are set using the attribute dataPoolRelations, which refers to a list consisting of one or more relations of type DataPoolRelation. Person should be related to card and card should be related to certificate. DataPoolRelation is defined as follows:
| Attribute | Defnition |
|---|
sourceDataPool | Source data pool from which a relation to the target data pool shall be established. | | sourceForeignKey | Source data pool field that references a data pool field in the destination data pool. | | targetDataPool | Target data pool from which to relate to the source data pool shall be established. | | targetForeignKey | Target data pool field that references a data pool field in the source data pool |
|
...
