When you use the ISM Configuration GUI to create and edit ISM profiles, those profiles are written to the TEPS database. Then, when you open the ISM Configuration GUI, the GUI pulls the existing profiles from the database.
In comparison, when you use the ismbatch utility to create and edit profiles, the profiles are not written to the TEPS database. Consequently, the profiles that you create by using the ismbatch utility are not visible in the ISM Configuration GUI.
A resync operation replaces the active profile XML files with the active profiles on the TEPS database. The existing ismbatch profiles are deleted.
ISM 7.3 has added the ISM Configuration CLI that overcomes these problems. When upgrading from an earlier version to ISM 7.3, it is important to migrate any profiles that weren't in the database (for example, previous ismbatch profiles) into the TEPS database.
The following guide shows how you can run the xml2cli command to convert the existing profile XML files into the ismbatch -add commands, and then use ismconfig to process those commands to add the profiles to the TEPS database. Or, you can explicitly add the ismbatch -add commands to a command file, and then use ismconfig to process those commands to add the profiles to the TEPS database.