Preparing for migration in InfoSphere Information Server (Windows)

Before you export any data from InfoSphere Information Server on Windows to Cloud Pak for Data, complete a set of setup tasks.

Before you begin

Confirm that the prerequisites listed in Prerequisites to migrating data are met.

The migration scripts must be run on a Red Hat® Enterprise Linux® server (minimum version 8.9) without any InfoSphere Information Server components installed. The minimum required resources for this server are 8 CPU, 16 GB RAM, 250 GB of disk space.

Tasks to complete on the InfoSphere Information Server Windows system before migrating

Complete the following tasks in InfoSphere Information Server before you export your data and processes for migration.

You must run all commands as Administrator.
  1. Setting environment variables on the InfoSphere Information Server Windows system
  2. Increasing the expiry time for the CSRF token
  3. Removing invalid users
  4. Assigning the Suite User role to users with inherited roles
  5. Granting access to all data quality projects
  6. Improving export performance
  7. Checking data integrity
  8. Increasing the timeout value for the LTPA token
  9. Creating a db2dsdriver.cfg configuration file

Tasks to complete on the Red Hat Enterprise Linux system before migrating

Complete the following tasks on the system where you want to run the migration scripts before you export your data and processes for migration.

To complete these tasks, you must be logged in to the system as root.
  1. Setting environment variables on the Red Hat Enterprise Linux system
  2. Installing required tools
  3. Installing the migration toolkit
  4. Running the initialization script
  5. Preparing configuration information
  6. Installing required software packages

Setting environment variables on the InfoSphere Information Server Windows system

Complete the following steps:

  1. Open a command prompt.
  2. Set the following environment variables. 
    set IIS_INSTALL_PATH=<IIS installation path>
set IIS_HOST=<IIS host>
set IIS_PORT=<IIS port>
set IIS_USERNAME=<IIS user name>
set IIS_PASSWORD=<IIS password>
set TOOLKIT_PATH=<directory for storing the toolkit content>

Increasing the expiry time for the CSRF token

Increase the expiry time for the CSRF token.

  1. Set the expiry time to 600 seconds by running the following command:
    %IIS_INSTALL_PATH%\ASBServer\bin\iisAdmin.bat -set -key com.ibm.iis.isf.security.CsrfTokenExpiryTime -value 600
  2. Confirm the setting by running the following command:
    %IIS_INSTALL_PATH%\ASBServer\bin\iisAdmin.bat -d | FINDSTR com.ibm.iis.isf.security.CsrfTokenExpiryTime

Removing invalid users

Remove all invalid users from the user registry. Run the commands that apply to your environment.

  1. Get the list of invalid users.
    %IIS_INSTALL_PATH%\ASBServer\bin\DirectorySync.bat -url https://%IIS_HOST%:%IIS_PORT% -user %IIS_USERNAME% -password %IIS_PASSWORD% -giu
  2. Delete all users that were returned in the previous step. Pass the usernames as a tilde-delimited list to the DirectorySync.bat script. If the entries to be deleted are long full DN names, enclose each username in double quotation marks (").
    %IIS_INSTALL_PATH%\ASBServer\bin\DirectorySync.bat -url https://%IIS_HOST%:%IIS_PORT% -user %IIS_USERNAME% -password %IIS_PASSWORD% -delete_user_ids user1~user2~…userN

Assigning the Suite User role to users with inherited roles

Assign the Suite User role to all users that do not have any security roles assigned directly but inherit the roles from the groups that they are part of.

Run the commands that apply to your environment.

  1. Get the list of users without direct role assignments:
    %IIS_INSTALL_PATH%\ASBServer\bin\UsersSync.bat -url https://%IIS_HOST%:%IIS_PORT% -user %IIS_USERNAME% -password %IIS_PASSWORD% -list USERS
  2. Assign the Suite User role to the users returned in the previous step:
    %IIS_INSTALL_PATH%\ASBServer\bin\UsersSync.bat -url https://%IIS_HOST%:%IIS_PORT% -user %IIS_USERNAME% -password %IIS_PASSWORD% -list USERS -sync

Granting access to all data quality projects

Grant access to all data quality projects:

%IIS_INSTALL_PATH%\ASBServer\bin\iisAdmin.bat -set -key com.ibm.iis.ia.server.accessAllProjects -value true
%IIS_INSTALL_PATH%\ASBServer\bin\iisAdmin.bat -set -key com.ibm.iis.ismigration -value true

Improving export performance

To improve the performance of the migration during the export, complete these steps as root:

  1. Create additional indexes in the metadata repository. Complete the following steps depending on where your metadata repository is hosted. These steps must be completed on the InfoSphere Information Server services tier:
    Metadata repository on Db2
    Run these xmetaAdmin commands:
    cd ${IIS_INSTALL_PATH}\ASBServer\bin
.\xmetaAdmin.bat addIndex -model ASCLModel -class DataFileFolder importedVia_DataConnection ASC -dbfile ..\conf\database.properties
.\xmetaAdmin.bat addIndex -model ASCLModel -class DataConnection accesses_DataStore ASC -dbfile ..\conf\database.properties
.\xmetaAdmin.bat addIndex -model DataStageX -class DSDataConnection accesses_DataStore ASC -dbfile ..\conf\database.properties
.\xmetaAdmin.bat addIndex -model ASCLModel -class DataCollection of_PhysicalModel ASC -dbfile ..\conf\database.properties
.\xmetaAdmin.bat addIndex -model ASCLLogicalModel -class Relationship of_LogicalModel ASC -dbfile ..\conf\database.properties
.\xmetaAdmin.bat addIndex -model ASCLModel -class HostSystem name ASC -dbfile ..\conf\database.properties
.\xmetaAdmin.bat addIndex -model ASCLModel -class Connector hostedBy_HostSystem ASC -dbfile ..\conf\database.properties
.\xmetaAdmin.bat addIndex -model ASCLModel -class Connector connectionType ASC -dbfile ..\conf\database.properties
.\xmetaAdmin.bat addIndex -model ASCLModel -class DataConnection usedBy_Connector ASC -dbfile ..\conf\database.properties
.\xmetaAdmin.bat addIndex -model DataStageX -class DSDataConnection usedBy_Connector ASC -dbfile ..\conf\database.properties
    Metadata repository on Oracle
    Run the following commands:
    CREATE INDEX IDX2102100719410 ON investigateDtQltyDmnsn (OFDATAQUALITYCONFIGURATIONXMET ASC, XMETA_REPOS_OBJECT_ID_XMETA ASC, HAS_BENCHMARK_XMETA ASC, IGNORED_XMETA ASC, WEIGHT_XMETA ASC);
CREATE INDEX IDX2102100926320 ON issMstrDtFldrfFrmDtFld (DATAFIELD_XMETA ASC);
CREATE INDEX IDX2102100927200 ON investigateDatQltyRslt (FROM_EXECUTIONHISTORY_XMETA ASC, NBRECORDSTESTED_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA ASC);
CREATE INDEX IDX2102100927180 ON ASCLAnalysisQultyPrblm (FROM_DATAQUALITYRESULT_XMETA ASC, NBOCCURRENCES_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA ASC);
CREATE INDEX IDX2102100927560 ON investigateExectnHstry (OF_QUALITYCOMPONENT_XMETA ASC, STATUS_XMETA ASC, STARTTIME_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA ASC, HAS_EXECUTIONRESULT_XMETA ASC);
CREATE INDEX IDX2102100928040 ON investigatQltyPrblmTyp (CODE_XMETA ASC, DESCRIPTION_XMETA ASC, NAME_XMETA ASC);
CREATE INDEX IDX2102100925570 ON investigateRuleCompnnt (OF_ANALYSISPROJECT_XMETA ASC, SHORTDESCRIPTION_XMETA ASC, NAME_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA ASC);
CREATE INDEX IDX2102100734290 ON ASCLAnalysisClassifctn (METHOD_XMETA ASC, STATE_XMETA DESC);
CREATE INDEX IDX2102100734240 ON ASCLAnalysisClassifctn (STATE_XMETA ASC, METHOD_XMETA DESC);
CREATE INDEX IDX2102100734490 ON investigtClmnnlyssMstr (PROJECTRID_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA ASC, TABLEANALYSISMASTER_XMETA ASC);
CREATE INDEX IDX2102100735000 ON ArfFrmrgntdFrmClssfctn (ORIGINATEDFROMCLASSIFICATINXMT ASC);
CREATE INDEX IDX2102100735420 ON ASCLAnalysis_DataClass (NAME_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA ASC);
CREATE INDEX IDX2102100736020 ON ASCLAnalysisClassifctn (STATE_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA ASC, VALUEFREQUENCY_XMETA ASC);
CREATE INDEX IDX2102100735470 ON investigtClmnnlyssMstr (PROJECTRID_XMETA ASC, TABLEANALYSISMASTER_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA ASC);
CREATE INDEX IDX2102100738180 ON investigateExectnHstry ("OF_QUALITYCOMPONENT_XMETA" ASC, "STARTTIME_XMETA" DESC);
CREATE INDEX IDX2102100736090 ON investigateRuleCompnnt ("OF_ANALYSISPROJECT_XMETA" ASC, "NAME_XMETA" ASC, "XMETA_REPOS_OBJECT_ID_XMETA" ASC);
CREATE INDEX IDX2102100741130 ON investigateDatQltyRslt ("FROM_EXECUTIONHISTORY_XMETA" ASC, "XMETA_REPOS_OBJECT_ID_XMETA" ASC);
CREATE INDEX IDX2102100744410 ON investgtClmnDtTypSmmry (COLUMNANALYSISRESULTS_XMETA ASC, RECORDPERCENT_XMETA ASC, RECORDCOUNT_XMETA ASC, DATATYPE_XMETA ASC);
CREATE INDEX "IDX2102100653330" ON investgtClmnnlyssRslts("COLUMNANALYSISMASTER_XMETA" ASC, "RECORDCOUNT_XMETA" DESC);
CREATE INDEX "IDX2102100653560" ON ASCLModel_DataFile("HOSTEDBY_HOSTSYSTEM_XMETA" ASC, "PATH_XMETA" ASC, "NAME_XMETA" ASC, "XMETA_REPOS_OBJECT_ID_XMETA" ASC);
CREATE INDEX IDX2102100659300 ON investigtClmnnlyssMstr (TABLEANALYSISMASTER_XMETA ASC, COLUMNPROPERTIES_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA ASC);
CREATE INDEX "IDX2102100657460" ON investigateTblPKCnddts ("OF_TABLEANALYSISMASTER_XMETA" ASC, "XMETA_REPOS_OBJECT_ID_XMETA" ASC, "CANDIDATEFLAG_XMETA" ASC,"SELECTED_XMETA" ASC, "INFERRED_XMETA" ASC);
CREATE INDEX "IDX2102100704290" ON investigatTblnlyssMstr ("ANALYSISMASTER_XMETA" ASC, "TABLEANALYSISSTATUS_XMETA" ASC, "XMETA_REPOS_OBJECT_ID_XMETA" ASC);
CREATE INDEX "IDX2102100704280" ON iDtCllctnrfFrmDtCllctn("DATACOLLECTION_XMETA" ASC);
CREATE INDEX "IDX2102100706510" ON investigateTblPKCnddts("OF_TABLEANALYSISMASTER_XMETA" ASC, "SELECTED_XMETA" ASC, "REJECTED_XMETA" ASC);
CREATE INDEX "IDX2102100709420" ON ASCLModel_Annotation("NOTELABEL_XMETA" ASC, "OF_COMMONOBJECT_XMETA" DESC);
CREATE INDEX "IDX2102100708160" ON ASCLRules_RuleVariable("FROM_RULE_XMETA" ASC, "XMETA_REPOS_OBJECT_ID_XMETA" ASC, "DEFAULT_RULEBINDING_XMETA" ASC);
CREATE INDEX "IDX2102100708310" ON investigateRuleCompnnt ("OF_ANALYSISPROJECT_XMETA" ASC, "XMETA_REPOS_OBJECT_ID_XMETA" DESC);
CREATE INDEX "IDX2102100713390" ON investigateAnalyssptns ("OF_ANALYSISSUITE_XMETA" ASC, "USEAUTOMATICDATAQLTYCNFGRTNXMT" DESC);
CREATE INDEX "IDX2102100715420" ON investigateTblPKCnddts("SELECTED_XMETA" ASC, "COLUMNANALYSISMASTER_XMETA" ASC, "XMETA_REPOS_OBJECT_ID_XMETA" ASC);
CREATE INDEX "IDX2102100716030" ON investigateKeyComponnt ("OF_TABLEPKCANDIDATE_XMETA" ASC, "USESCOLUMNANALYSISMASTERXMETA" DESC);
CREATE INDEX "IDX2102100717450" ON investigateAnalyssptns ("UNIQUENESSTHRESHOLD_XMETA" ASC, "OF_ANALYSISSUITE_XMETA" DESC);
CREATE INDEX "IDX2102100717410" ON investigateAnalyssptns("UNIQUENESSTHRESHOLD_XMETA" ASC, "OF_ANALYSISPROJECT_XMETA" DESC);
CREATE INDEX "IDX2102100717390" ON investigateAnalyssptns("UNIQUENESSTHRESHOLD_XMETA" ASC, "OF_TABLEANALYSISMASTER_XMETA" DESC);
CREATE INDEX "IDX2102100716190" ON investigateAnalyssptns("OF_COLUMNANALYSISMASTER_XMETA" ASC, "OF_TABLEANALYSISMASTER_XMETA" ASC, "OF_ANALYSISPROJECT_XMETA" ASC, "OF_ANALYSISMASTER_XMETA" ASC, "OF_ANALYSISSUITE_XMETA" ASC);
CREATE INDEX "IDX2102100733120" ON ASCLRules_RuleBinding ("FROM_RULEEXECUTABLE_XMETA" ASC, "XMETA_REPOS_OBJECT_ID_XMETA" ASC, "BINDS_RULEVARIABLE_XMETA" ASC);
CREATE INDEX "IDX2102100730040" ON investigatentgrDstrbtn ("VALUE_XMETA" ASC, "OFRULESETEXECUTIONRESULTXMETA" ASC, "ABSOLUTEFREQUENCY_XMETA" ASC, "FREQUENCY_XMETA" ASC) ;
CREATE INDEX IDX2312060847540 ON investigatTblQltynlyss (OF_TABLEANALYSISMASTER_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA DESC);
CREATE INDEX IDX2312060848270 ON investigateExectnHstry (OF_QUALITYCOMPONENT_XMETA ASC, ENDTIME_XMETA ASC, STARTTIME_XMETA ASC, HAS_EXECUTIONRESULT_XMETA ASC);
  2. Complete the following steps depending on where your metadata repository is hosted. These steps must be completed on the InfoSphere Information Server metadata repository tier.
    Metadata repository on Db2

    1. Set the following environment variable:

      set DB2_INSTANCE_NAME=<db2-instance-name>
    2. Change to the Db2 instance user, set an environment variables, and connect to the metadata repository:
      su %DB2_INSTANCE_NAME%
. ~\sqllib\db2profile
DB2_INSTANCE_NAME=<db2-instance-name>
XMETA_SCHEMA_NAME=<xmeta-schema-name>
db2 connect to xmeta
    3. Create the indexes:
      db2 "CREATE INDEX %DB2_INSTANCE_NAME%.IDX2312060847540 ON %XMETA_SCHEMA_NAME%.INVESTIGATE_TABLEQUALITYANALYSIS ( OF_TABLEANALYSISMASTER_XMETA ASC, XMETA_REPOS_OBJECT_ID_XMETA DESC) ALLOW REVERSE SCANS COLLECT SAMPLED DETAILED STATISTICS"
db2 "CREATE INDEX %DB2_INSTANCE_NAME%.IDX2312060848270 ON %XMETA_SCHEMA_NAME%.INVESTIGATE_EXECUTIONHISTORY ( OF_QUALITYCOMPONENT_XMETA ASC, ENDTIME_XMETA ASC, STARTTIME_XMETA ASC, HAS_EXECUTIONRESULT_XMETA ASC) ALLOW REVERSE SCANS COLLECT SAMPLED DETAILED STATISTICS"
db2 "CREATE UNIQUE INDEX %DB2_INSTANCE_NAME%.IDX2312060848320 ON %XMETA_SCHEMA_NAME%.INVESTIGATE_TABLEANALYSISMASTER ( XMETA_REPOS_OBJECT_ID_XMETA ASC ) INCLUDE ( TABLEANALYSISSTATUS_XMETA , ANALYSISMASTER_XMETA ) ALLOW REVERSE SCANS COLLECT SAMPLED DETAILED STATISTICS"
db2 "CREATE INDEX %DB2_INSTANCE_NAME%.IDX2312060848360 ON %XMETA_SCHEMA_NAME%.INVESTIGATE_TABLEANALYSISMASTER_DATACOLLECTION_REFFROM_DATACOLLECTION (DATACOLLECTION_XMETA ASC) ALLOW REVERSE SCANS COLLECT SAMPLED DETAILED STATISTICS"
db2 "CREATE UNIQUE INDEX %DB2_INSTANCE_NAME%.IDX2312060848530 ON %XMETA_SCHEMA_NAME%.INVESTIGATE_TABLEANALYSISSTATUS (XMETA_REPOS_OBJECT_ID_XMETA ASC) INCLUDE (DATAQUALITYANALYSISDATE_XMETA, DATAQUALITYANALYSISSTATUS_XMETA) ALLOW REVERSE SCANS COLLECT SAMPLED DETAILED STATISTICS"
db2 "COMMIT"
    4. Update the DBMS statistics for all the tables in the metadata repository before you start the migration. 
      db2 -x "SELECT 'runstats on table',substr(rtrim(tabschema)||'.'||rtrim(tabname),1,50),' and indexes all;' FROM SYSCAT.TABLES WHERE (type = 'T') AND (tabschema = '%XMETA_SCHEMA_NAME%')" > C:\tmp\runstats_xmeta.out
db2 -tvf C:\tmp\runstats_xmeta.out
    5. Exit the Db2 instance owner account:
      exit
    6. Create extra indexes for data assets in data quality projects. Follow the instructions in the support document Indices for performance improvement in legacy migration from InfoSphere Information Server to IBM Knowledge Catalog.
    Metadata repository on Oracle
    Update the DBMS statistics for your metadata repository after the indexes are created with the assistance of a DBA.
    1. Set the following environment variable:
      set XMETA_SCHEMA_NAME=<xmeta-schema-name>
    2. Run the following commands:
      EXEC DBMS_STATS.gather_table_stats('%XMETA_SCHEMA_NAME%','ASCLMODELDATAFILEFOLDR',cascade=>TRUE)
EXEC DBMS_STATS.gather_table_stats('%XMETA_SCHEMA_NAME%','ASCLMODELDATACONNECTIN',cascade=>TRUE)
EXEC DBMS_STATS.gather_table_stats('%XMETA_SCHEMA_NAME%','DATASTAGEXDSDATACNNCTN',cascade=>TRUE)
EXEC DBMS_STATS.gather_table_stats('%XMETA_SCHEMA_NAME%','ASCLMODELDATACOLLECTIN',cascade=>TRUE)
EXEC DBMS_STATS.gather_table_stats('%XMETA_SCHEMA_NAME%','ASCLLOGICALMODLRLTNSHP',cascade=>TRUE)
EXEC DBMS_STATS.gather_table_stats('%XMETA_SCHEMA_NAME%','ASCLModel_HostSystem',cascade=>TRUE)
EXEC DBMS_STATS.gather_table_stats('%XMETA_SCHEMA_NAME%','ASCLModel_Connector',cascade=>TRUE)
    Note: It is recommended to update the DBMS statistics for all the tables in the metadata repository before you start the migration.
    Metadata repository on Microsoft SQL Server
    Update the DBMS statistics for your metadata repository after the indexes are created with the assistance of a DBA.
    Run the following command in Microsoft SQL Server Management Studio on the SQL Server machine. Replace <xmeta-schema-name> with the schema name of the metadata repository in your environment:
    EXEC sp_MSforeachtable 'UPDATE STATISTICS <xmeta-schema-name>.? WITH FULLSCAN'
    Note: It is recommended to update the DBMS statistics for all the tables in the metadata repository before you start the migration.

Checking data integrity

To check the integrity of the data in InfoSphere Information Server, complete the following steps:
  1. Open a command prompt and set the following environment variables:
    set TOOLKIT_PATH=<directory to which the toolkit content is extracted>
set IIS_INSTALL_PATH=<IIS installation path>
  2. Install the migration toolkit.
    1. Download the migration toolkit for InfoSphere Information Server to the %TOOLKIT_PATH% directory. Follow the instructions on this support page:

      Migration from IBM InfoSphere Server to IBM Knowledge Catalog: Applying patches and toolkit to the IBM InfoSphere Server 11.7.1.x installation (Part 1 of 2)

      This document is updated when a new version of the migration toolkit is released and also contains information about any prerequisite patches that you might need to install.

    2. Set the toolkit version and change to the %TOOLKIT_PATH% directory.
      set TOOLKIT_VERSION=<toolkit version>
cd %TOOLKIT_PATH%
    3. Extract the downloaded file to the %TOOLKIT_PATH% directory. Run the following command:
      tar -zxvf iis-migration-toolkit-%TOOLKIT_VERSION%.tar.gz
  3. Update the following response file:
    • For InfoSphere Information Server 11.7.1.4:

      %TOOLKIT_PATH%\migration\iis_scripts\isalite_adt_mr_response_11714.txt

    • For InfoSphere Information Server 11.7.1.5:

      %TOOLKIT_PATH%\migration\iis_scripts\isalite_adt_mr_response.txt

    Set the fieldTask.IS.root property to the InfoSphere Information Server installation path, for example: fieldTask.IS.root=C:\IBM\InformationServer

  4. Run the following command:
    %TOOLKIT_PATH%\migration\iis_scripts\run_IIS_ISALite.bat %IIS_INSTALL_PATH%

    The tool will take some time to process the data and generate a report. This report is stored in the ISA_XMetHC_XXX_%timestamp% subdirectory of the current directory.

    Open the XMETAHealthChecker.html report file in a browser, and review the results and instructions that it contains. Verify that no errors occurred and that all the probes show the status SUCCESS.

Increasing the timeout value for the LTPA token

To ensure that the session can refresh without any issues, increase the timeout value for the LTPA token.

For WebSphere Application Server Liberty
Complete these steps:
  1. Edit the %IIS_INSTALL_PATH%\wlp\usr\servers\iis\server.xml file.
  2. Find the <ltpa expiration="795m"/> entry and update this expiration value with a larger number. Either change it to 1440m, which corresponds to 24 hours, or 2880m, which is 48 hours.
  3. Restart the application server.
    1. Click Start. Then, search for cmd.
    2. Right-click Command Prompt. Then, click Run as administrator.
    3. Run the following commands. Replace ServerName with the name of the server to be stopped or started.
      cd %IIS_INSTALL_PATH%\wlp\bin
server stop <ServerName>
server start <ServerName>
For WebSphere Application Server Network Deployment
Complete these steps:
  1. Log in to the administrative console of the WebSphere application server.
  2. Go to Security > Global Security > LTPA > LTPA timeout.
  3. Increase the timeout value. Either change it to 1440m, which corresponds to 24 hours, or 2880m, which is 48 hours.
  4. Click Apply and OK.
  5. Restart the application server.
    Stand-alone installation
    1. Click Start. Then, search for cmd.
    2. Right-click Command Prompt. Then, click Run as administrator.
    3. Run the following commands. Replace <ServerName> with the name of the server to be stopped or started.
      cd <WebSphere_Install_Path>\profiles\InfoSphere\bin
stopServer.bat <ServerName>
startServer.bat <ServerName>

      If you are prompted for a user ID and password, use the credentials of the WebSphere admin account. The default account is the wasadmin service account.

    Clustered installation
    • On Windows:
      1. Click Start. Then, search for services.
      2. Right-click IBM WebSphere Application Server.
      3. Select Stop the service.
      4. Select Start the service.
    • On Linux:
      Run the following commands. Replace <ServerName> with the name of the server to be stopped or started.
      cd <WebSphere_Install_Path>/AppServer/bin
./stopServer.sh <ServerName>
./startServer.sh <ServerName>

      If you are prompted for a user ID and password, use the credentials of the WebSphere admin account. The default account is the wasadmin service account.

Creating a db2dsdriver.cfg configuration file

  1. On the InfoSphere Information Server services tier, run the following command to list the Db2 connections:
    %IIS_INSTALL_PATH%\ASBServer\bin\xmetaAdmin.bat query -expr "select dc.name as connection_name, dc.username as user_name, dc.connectionString as database_name from connector in Connector, dc in connector->uses_DataConnection where connector.name='DB2Connector'" -dbfile %IIS_INSTALL_PATH%\ASBServer\conf\database.properties http:///5.3/ASCLModel.ecore
    1. Verify the output and check if the Db2 connections are valid and required for migration.
    2. Proceed to step 2, and the following steps, only if Db2 connections are to be migrated.
  2. Log in to the engine tier as the Db2 instance user.
  3. Check if the Db2 client is on the engine tier.
  4. Create a db2dsdriver.cfg configuration file for the Db2 database on the InfoSphere Information Server engine tier host and make the configuration file available to the ASBNode agent and the Connector Access Service (CAS).
    1. Set the following environment variables:
      set DB2_INSTANCE_NAME=<db2-instance-name>
set OUTPUT_FOLDER=<output folder>
    2. Create and populate db2dsdriver.cfg configuration file by running the following command:
      db2dsdcfgfill.exe -i %DB2_INSTANCE_NAME% -o %OUTPUT_FOLDER%
    3. Make sure that read permission to the generated db2dsdriver.cfg file is granted to the group Other users. Run the following command:
      chmod 644 %OUTPUT_FOLDER%\db2dsdriver.cfg

    4. Check the content of the generated db2dsdriver.cfg file. If you find any local database entries with the setting host="LOCALHOST" and port="0", replace LOCALHOST with the correct hostname and update the port entry with the correct Db2 port number. Save your changes.

      For some Db2 versions, running the db2dsdcfgfill.exe command might not create the db2dsdriver.cfg configuration file in the specified folder.

      If this error occurs when you run the db2dsdcfgfill.exe command, check your Db2 client version and upgrade to version 11.5.7.0 if necessary.

    5. Make the db2dsdriver.cfg configuration file available to the ASBNode agent and to CAS. As root user, complete these steps:
      1. Set the following environment variables. 
        set IIS_INSTALL_PATH=<IIS installation path>
set DB2_INSTANCE_NAME=<db2-instance-name>
set OUTPUT_FOLDER=<output folder>
      2. Add the following environment variable to the %IIS_INSTALL_PATH%\ASBNode\bin\NodeAgents_env_DS.bat:
        set CC_DB2_CONNECTION_MIGRATION_DB2DSDRIVER_CFG_%DB2_INSTANCE_NAME%=%OUTPUT_FOLDER%\db2dsdriver.cfg
      3. Restart the ASBNode agent by running the following commands. You must have read permission on the db2dsdriver.cfg configuration file.
        cd %IIS_INSTALL_PATH%\ASBNode\bin
net stop asbagent
        cd %IIS_INSTALL_PATH%\ASBNode\bin
net start asbagent
        You can check the status of ASBNode agent by running the following command:
        sc query asbagent

If you have multiple Db2 instances, complete these steps for each instance.

Setting environment variables on the Red Hat Enterprise Linux system

Complete the following steps:

  1. Log in to the system as root.
  2. Open a bash shell:
    bash
  3. Set the following environment variables. 
    IIS_INSTALL_PATH=/opt/IBM/InformationServer
IIS_HOST=<IIS host>
IIS_PORT=<IIS port>
IIS_USERNAME=<IIS username>
IIS_PASSWORD=<IIS password>
TOOLKIT_PATH=<directory for storing the toolkit content; the directory must not be under the /root path>

    The IIS_INSTALL_PATH variable must always be set to the value /opt/IBM/InformationServer to create the appropriate folder structures for the migration scripts.

Installing required tools

Download and install the jq utility as root user.

  1. Change to the ${TOOLKIT_PATH} directory.
    cd ${TOOLKIT_PATH}
  2. To install the utility, run the following commands:
    curl -LO https://github.com/jqlang/jq/releases/download/jq-1.7.1/jq-linux-i386
chmod +x ./jq-linux-i386
cp jq-linux-i386 jq

Installing the migration toolkit

Install the migration toolkit.

  1. Download the migration toolkit for InfoSphere Information Server to the ${TOOLKIT_PATH} directory. Follow the instructions on this support page:

    Migration from IBM InfoSphere Server to IBM Knowledge Catalog: Applying patches and toolkit to the IBM InfoSphere Server 11.7.1.x installation (Part 1 of 2)

    This document is updated when a new version of the migration toolkit is released and also contains information about any prerequisite patches that you might need to install.

  2. Set the toolkit version and change to the ${TOOLKIT_PATH} directory.
    TOOLKIT_VERSION=<toolkit version>
cd $TOOLKIT_PATH
  3. Extract the downloaded file to the ${TOOLKIT_PATH} directory. Run the following command:
    tar -zxvf iis-migration-toolkit-${TOOLKIT_VERSION}.tar.gz -C ${TOOLKIT_PATH}

Running the initialization script

Run the init_migration_iis.sh script. The script is downloaded as part of the migration toolkit and can be found in the TOOLKIT_PATH directory.

  1. Run the script as root user:
    ${TOOLKIT_PATH}/migration/iis/init_migration_iis.sh "$IIS_INSTALL_PATH"
  2. Give the wkc user write and execute permission to the ${TOOLKIT_PATH} directory. Run the following command:
    setfacl -m u:wkc:rwx ${TOOLKIT_PATH}
  3. Set the path to the export data directory and grant the wkc user write permission to that directory:
    1. Set the EXPORT_DATA_DIR environment variable:
      EXPORT_DATA_DIR=<path to the export data directory>
    2. Give the wkc user write and execute permission to the ${EXPORT_DATA_DIR} directory:
      setfacl -m u:wkc:rwx ${EXPORT_DATA_DIR}

Preparing configuration information

To be able to migrate from a Windows system, some configuration information must be available on the Linux server from which you will run the migration.

Complete the following steps:
  1. Copy the database.properties file from the %IIS_INSTALL_PATH%\ASBServer\conf folder on the InfoSphere Information Server Windows computer (for example C:\IBM\InformationServer\ASBServer\conf) to the ${IIS_INSTALL_PATH}/ASBServer/conf folder on the Linux server.
  2. Run the following commands on the ${IIS_INSTALL_PATH}/ASBServer/conf/database.properties file:
    dos2unix ${IIS_INSTALL_PATH}/ASBServer/conf/database.properties
chmod g+r ${IIS_INSTALL_PATH}ASBServer/conf/database.properties
  3. Copy the isf-server.keystore file from the InfoSphere Information Server Windows computer to the Linux server.
    For WebSphere Application Server Network Deployment
    Source folder on the InfoSphere Information Server Windows computer: %IIS_INSTALL_PATH%\ASBServer\apps\lib\iis\classes (for example C:\IBM\InformationServer\ASBServer\apps\lib\iis\classes)

    Target folder on the Linux server: ${IIS_INSTALL_PATH}/wlp/usr/servers/iis/lib/iis/15properties

    For WebSphere Application Server Liberty
    Source folder on the InfoSphere Information Server Windows computer: %IIS_INSTALL_PATH%\ASBServer\apps\lib\iis\15properties (for example C:\IBM\InformationServer\ASBServer\apps\lib\iis\15properties)

    Target folder on the Linux server: ${IIS_INSTALL_PATH}/wlp/usr/servers/iis/lib/iis/15properties

Installing required software packages

Download and install the IBM Java SDK and the IBM Semeru Runtimes package.

Complete these steps:

  1. Go to the folder where InfoSphere Information Server is installed.
    cd ${IIS_INSTALL_PATH}
  2. Download the latest IBM SDK, Java Technology Edition, Version 8 package from the Java SDK downloads site.

    Go to https://www.ibm.com/support/pages/java-sdk-downloads-version-80 and download the latest version of the Linux on x86 systems 64-bit JRE archive package ibm-java-jre-8.0-8.<xx>-linux-x86_64.tgz, where <xx> represents the version number.

  3. Extract the downloaded file. Replace <xx> in the command with the appropriate version number.
    tar -zxvf ibm-java-jre-8.0-8.<xx>-linux-x86_64.tgz
  4. Rename the resulting folder to ibm-java-x86_64-80 jdk:
    mv ibm-java-x86_64-80 jdk
  5. Change to the wkc user and open a bash shell:
    su wkc
bash
  6. Change to the directory where the toolkit content is stored:
    TOOLKIT_PATH=<toolkit_path>
cd $TOOLKIT_PATH
  7. Download and install the IBM Semeru Runtimes OpenJDK 17 (jdk-17.0.9):
    curl -LO https://github.com/ibmruntimes/semeru17-binaries/releases/download/jdk-17.0.9%2B9_openj9-0.41.0/ibm-semeru-open-jdk_x64_linux_17.0.9_9_openj9-0.41.0.tar.gz
    tar -zxvf ibm-semeru-open-jdk_x64_linux_17.0.9_9_openj9-0.41.0.tar.gz
  8. Set the path to point to the IBM JDK 17 java installed in the previous steps.
    export PATH=${TOOLKIT_PATH}/jdk-17.0.9+9/bin:${TOOLKIT_PATH}:$PATH

What to do next

  1. Determine the scope of export. Evaluate which data you want to migrate and remove all unnecessary data to avoid cluttering the new deployment.
  2. Complete the setup tasks for Cloud Pak for Data in Preparing for migration in IBM Cloud Pak for Data.