33.3 Prerequisites for Importing Data

Before importing data, ensure that you have exported the data sources, policies, or configurations that you want to move to another system, and have downloaded the exported files to your local computer. For those areas that you cannot export, take screenshots and record the details in a planning worksheet. Also, be aware of the importance of the order in which you import data.

After exporting, prepare your environment for import, using the following steps, then start importing in the recommended order.

To prepare your system for imports:

  1. Stop all Tomcat instances.

  2. Delete localhost from the following locations:

    • Linux: /opt/netiq/idm/apps/tomcat/work/Catalina/localhost

    • Windows: C:\netiq\idm\apps\tomcat\work\Catalina\localhost

  3. Delete all files and folders from the temp directory in the following locations:

    • Linux: /opt/netiq/idm/apps/tomcat/temp

    • Windows: C:\netiq\idm\apps\tomcat\temp

  4. Delete or move out all the log files from the following locations:

    • Linux: /opt/netiq/idm/apps/tomcat/logs

    • Windows: C:\netiq\idm\apps\tomcat\logs

  5. Have the DBA delete all the ID Gov schemas.

    NOTE:You do not have to delete the IGRPT schema.

  6. Have the DBA create the ID Gov schemas either:

  7. On the primary node, navigate to the /opt/netiq/idm/apps/idgov/bin or C:\netiq\idm\apps\idgov\bin directory and run the following command. Make sure that you are using the same password that you have used for all the ID Gov schemas.

    /db-init.sh -password password 2>&1 | tee -a recreate-schema.log

    Once you run the command, you will be able to see the output in your Linux terminal or Windows and it will also be captured in the file.

  8. On the primary node, navigate to the /opt/netiq/idm/apps/idgov/logs or C\netiq\idm\apps\idgov\logs directory perform the following steps:

    1. Copy the actual command (after Command:) from the dbtool-rptuser-log.txt.

      1. Replace xxx for the real password and execute the command

        This will create the necessary igrptuser and grant the correct view rights on the views in the IGOPS schema.

    2. Copy the actual command (after Command:) from the config-init-log.txt.

      1. Replace xxx for the real password and execute the command.

        This will import the default global properties back into the IGOPS schema.

  9. Start the primary tomcat.

    During the start-up of this node, the base data load will occur and default data will be added into the necessary tables.

  10. Once Tomcat has fully started login as the Bootstrap user.

  11. Extract the Identity and Application Source zip files that were previously exported and start importing based on the recommended order of import.