Managed File Transfer

 View Only

Tips for making the B2Bi and SFG patch install process faster

By Tanvi Kakodkar posted Wed January 22, 2020 11:35 AM

  
Originally updated on August 28, 2014 by VinceTkac

Tips for making the B2Bi and SFG patch install process faster

There are a number of things that can cause the application of a patch or fixpack to take a long time (size of the patch or DB changes for example) but a common slowdown (and one that is easy to address) is that either setupfiles or deployer are scanning large directories which they don't need to.


More recent patches of B2Bi/SFG have updates to make those processes skip specific directories that are known to be large and which do not contain files needed at patch time.  If you are on a version prior to those fixes, you can clean out or move the following directories.  In a production system, these directories can become very large.

arc_data
documents
logs
backups
properties/backups
tmp
uninstall

The logs, tmp, uninstall and backups directories are generally safe to cleanup if the system is running well and you don't need to revert files or debug.

The arc_data and documents directories can't just be cleaned out but can be temporarily moved outside of the install directory.  This can be done with the node and adapter containers shutdown, just before running InstallService and moved back just after running InstallService.

Additionally, if there are custom directories under the install directory that hold a large number of files (perhaps a file system adapter directory), consider temporarily moving these outside of the install when applying a patch or fixpack just like above for documents.


#DataExchange
#IBMSterlingB2BIntegratorandIBMSterlingFileGatewayDevelopers
0 comments
18 views

Permalink