Import Converted Windows Data

After you convert your trading partner data, you can import the data into Sterling B2B Integrator.

1. Import the final.xml file (or the renamed .xml output file) into Sterling B2B Integrator.
2. Review the import report to determine whether any errors occurred in the import process. Any object having an error associated with it (see the STATUS column) is not successfully imported. Therefore, you must correct the error and import the object again.
3. Review the imported document envelopes, control numbers, and code lists. If necessary, modify them as needed.
   Note: If you converted using the winconvert.sh utility, all control number values (both local and global) from the outbound partner relationships are lost and reset to a value of “1.” You must now open the outbound envelope definition in Sterling B2B Integrator and set the control number to the appropriate value.
4. Change related map details:
   1. Change Application Integration map types to Sterling B2B Integrator (the map function must be set to Sterling Integrator).
   2. Remove all standard or extended rules specific to Sterling Gentran:Server for Windows.
   Note: For more information about maps related to your converted trading partner data, see Map-Related Considerations When Converting Trading Partner Data.