Running the export in inspect mode

You can run the export in inspect mode to understand what types of data exist in InfoSphere Information Server, what the sizes are, and who owns the data. This step is optional.

You can choose between generating a quick, high-level summary and generating a detailed inspection report in addition to the summary. Depending on the data that is evaluated, generating the detailed report might take more time than generating only a high-level summary.

For a summary, specify the -inspect_mode express option together with the -inspect true option. This mode also is the default setting if you don't specify the -inspect_mode option.
For a detailed inspection report in addition to the summary, specify the -inspect_mode complete option together with the -inspect true option.

To run the export in inspect mode, complete these steps:

Log in to the InfoSphere Information Server node as root.
Note: If InfoSphere Information Server is on Windows, log in to the standalone Red Hat® Enterprise Linux® machine as root.
Then, open a bash shell and change to the wkc user:
```
bash
su wkc
```

Set environment variables for the following required parameters:

TOOLKIT_PATH=<path to the directory where the toolkit was extracted (see Preparing for migration in InfoSphere Information Server)>
IIS_HOST=<IIS host>
IIS_PORT=<IIS port>
IIS_USERNAME=<IIS username>
IIS_PASSWORD=<IIS password>
IIS_INSTALL_PATH=<IIS installation path>
EXPORT_INSTANCE_NAME=<name of the export instance>
EXPORT_DATA_DIR=<path to the export data directory; the wkc user must have write permission to this directory>

IIS_INSTALL_PATH example: If InfoSphere Information Server is installed in the default location, set the IIS_INSTALL_PATH variable to the value /opt/IBM/InformationServer. For InfoSphere Information Server on Windows, the IIS_INSTALL_PATH variable must always be set to /opt/IBM/InformationServer.

Set the path to the toolkit directory.

export PATH=${TOOLKIT_PATH}/jdk-17.0.9+9/bin:${TOOLKIT_PATH}:$PATH

Change to the directory where the toolkit content is stored.
```
cd ${TOOLKIT_PATH}
```

Run the following script to trigger the export in inspect mode. Before running the script, remove any optional parameters that are not needed.

${TOOLKIT_PATH}/migration/iis_scripts/trigger_export_iis.sh -host ${IIS_HOST} -port ${IIS_PORT} -user ${IIS_USERNAME} -password ${IIS_PASSWORD} -export_instance_name ${EXPORT_INSTANCE_NAME} -dir ${EXPORT_DATA_DIR} -inspect true -iis_install_path ${IIS_INSTALL_PATH}

You can periodically check the progress of the inspection run by looking at the status file in the ${EXPORTED_DATA_DIR} target directory in the following path:
```
cat ${EXPORT_DATA_DIR}/${EXPORT_INSTANCE_NAME}/2*/legacy-migration/export-status.json
```
After the inspection run is complete, the export-status.json file contains a status: succeeded message. An example of the status message:
```
{"status":"succeeded","startTime":1711803460,"completionTime":1711803492,"message":"Inspect Completed","percentageCompleted":100}
```
Copy the archive that contains the inspect summary to the ${TOOLKIT_PATH} directory. Then, extract the archive:
```
cp ${EXPORT_DATA_DIR}/${EXPORT_INSTANCE_NAME}/2*/legacy-migration/inspect_summary_20*.zip ${TOOLKIT_PATH}
```
When you extract the archive file, the following file structure is created:
legacy-migration-summary/summary/
- export-inspect-report.txt
- export-status.json
- inspect-summary.json
legacy-migration-summary/details/
- data-quality_projects-inspect-details.csv
- imam_connections_inspect_details.csv
- imam_ldm_inspect-details.csv
- imam_pdm_inspect-details.csv
The export-inspect-report.txt file contains the summary for glossary assets, OpenIGC assets, Business Intelligence assets, custom attributes, and relationships. The inspect-summary.json file contains summary for all other types of assets.

The .csv files in the details folder provide details for data quality projects, and logical and physical models.