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

1. Install the current version of Java Runtime Environment (JRE).

2. Set JRE_HOME to the installation directory of java jre
   (for example: C:\Program Files\Java\jre1.8.0_161\bin)

3. Import the java-security-policy-fix for the installed Java version. The jce-policy-8.zip is provided with the migration package.

4. Unpack the migration package of delivery in a directory of your choice.

1. Go to the specified migration directory.

2. In the file database.properties specify the attributes HOST_NAME, DB_PORT, DB_NAME, USER_NAME and USER_PASSWORD for SmartACT and Identity Manager. The properties inside database.properties match those, described in PRIME installation.

   SmartACT database

   ### SmartACT Database smartAct.jdbcUrl=jdbc:sqlserver://<HOST_NAME>:<DB_PORT>;databaseName=<DB_NAME>;AUTO_SERVER=TRUE #smartAct.jdbcUrl=jdbc:sqlserver://<HOST_NAME>:<DB_PORT>;databaseName=<DB_NAME>;instance=<INSTANCE_NAME>;AUTO_SERVER=TRUE - verwendet für SQLEXPRESS Datenbank-Server smartAct.user=<USER_NAME> smartAct.password=<USER_PASSWORD>

    

   Identity Manager database

   ### PRIME Database prime.jdbcUrl=jdbc:sqlserver://<HOST_NAME>:<DB_PORT>;databaseName=<DB_NAME>;AUTO_SERVER=TRUE #prime.jdbcUrl=jdbc:sqlserver://<HOST_NAME>:<DB_PORT>;instance=<INSTANCE_NAME>;databaseName=<DB_NAME>;AUTO_SERVER=TRUE - verwendet für SQLEXPRESS Datenbank-Server prime.user=<USER_NAME> prime.password=<USER_PASSWORD> ...

    

1. Make sure that the certificate for encrypting run data in SmartACT (idexpertcert02.p12) is stored in the directory config. The migration tools contains this certificate, if it is not supplied by you.

2. Open the file encryption-config.xml and check if the value of the attribute pin under the key idexpertcert02 is correct, otherwise set the value:

   encryption-config.xml

   ... <keys> <key name="idexpertcert02"> <type name="pkcs12" locationValue="config/idexpertcert02.p12" pin="XXXX"/> </key> </keys> ...

    

These are examples of person statuses:

Example: Person status in SmartACT

Example: Person status in Identity Manager

Every person from SmartACT is assigned the role BaseRoleSelfServiceUser as part of the migration to Identity Manager, so access via USSP is possible. This can be customized in migrate_persons.properties under the parameter prime.person.roles.added.

The mapping of the data fields between Identity Manager and SmartACT is configured in the file spring\migrate-persons-batch_jobs-beans.xml. The assignment must be adjusted according to the use of the data fields in the following area:

The mapping of the persons is preset as follows:

For this, the MigrationId field is used, which is already used in SmartACT as uniqueness criterion.

Example:

Example:

Mapping of card fields between Identity Manager and SmartACT is configured in the spring\migrate-cards-batch_jobs-beans.xml file.

The assignment must be adjusted according to the use of the data fields in the following area:

The mapping of the cards is preset as follows:

The field MigrationId is used, which is already used in SmartACT as uniqueness criterion.

The following relation is defined especially for the card (see also Relation between the objects)