1.2.7 Limitations

This topic explains the limitations of Individual Fix Installer.

This is the start of your topic.

• Every Individual Fix is qualified with some rolled up version. Site should be in the same (neither previous nor later) rolledup version. Sites should not be in any intermediate patchsets.
• If a given Individual Fix is not matching with the connected FCIS environment’s rolledupversion then that Individual fix will not be listed in installer for installation.
• Once the Individual Fix is applied successfully then this will not be listed out from the nextsession of Individual fix installer.
• All Java sources are always consolidated, for example INFRA, TOOLS, ADAPTER, Gateway, etc., This means that the site cannot apply fix selectively instead all Individual fixes till date from the rolled up will be included.
• If there are any dependent bugs for selected bug then all dependent bugs should be applied before applying the selected bug.
• Fix can be applied only once for back end related bugs whereas ear build (APP) can be built as many times as needed.
• Multiple sessions of Individual fix installer is not supported for single FCIS environment.
• JS/UIXML/Help files will be copied into destination path, user has to copy the files manually to the deployment area or External Path.
• For APP bug, Individual fix installer will consolidate the source and Build the Ear in specified location. This will not get deployed in the server.
• The applied fixes will not be rolled back automatically by the installer in case of failures.
• Individual Fix Installer will only rebuild the EAR for APP bugs, user needs to take care of the deployment.