Changing Xmx and other memory settings for External Purge on Windows

By default, the maximum Java heap size Xmx = 512 MB on a Windows installation. You must increase the heap size to greater than 512 MB, for systems with very large databases.

Follow these steps:
  1. Run <B2Bi_install>/bin>stopExternalPurgeWindowsService.cmd.
  2. Edit InstallExternalPurgeWindowsService.cmd.in in the <B2Bi_install>/bin> directory.
  3. Add the following lines in the InstallExternalPurgeWindowsService.cmd.in file and save the changes.
    
echo -Xms4096m >> %PARAM_FILE%
echo -Xmx4096m >> %PARAM_FILE%
echo -Xmn1365m >> %PARAM_FILE%
echo -Xss256k >> %PARAM_FILE%
The Xmn should be 1/3 the size of the Xmx. The Xss of 256k is the preferred out of the box setting for Sterling B2B Integrator.
    Note: Search the following lines and add the above lines below these lines.
    
echo -DvendorFile=&PROP_DIR;
servers.properties >> %PARAM_FILE%
  4. Run <B2Bi_install>/bin>setupfiles.cmd.
  5. Run <B2Bi_install>/bin>uninstallExternalPurgeWindowsService.cmd.
  6. Run <B2Bi_install>/bin>InstallExternalPurgeWindowsService.cmd.
  7. Run <B2Bi_install>/bin>startExternalPurgeWindowsService.cmd.
  8. Verify the changes in the Windows Registry. 
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\
IBMSterlingB2BIntegratorExternalPurgeatport\Parameters\Java\options

    The system displays the new memory values under \options.