This is a totally new setup program, that ONLY does patching, i.e. one program for all versions and all options, etc.
It will update the running code of the system from ANY version to ANY version on any server without any user intervention (as long as you provide it with everything required).
It is compatible and will patch any single tier, app server, web server and file server automatically.
Note:
It will not update entire releases, as new releases usually include new parameters and settings which may not exist in your version of the INpPatcher.
The INpPatcher can be configured to for the following sources:
- PTF Zip files can automatically be downloaded directly from the Vendor (or otherwise specified) website.
- Zip files can be manually downloaded and placed in a specific local folder.
- Zip files could be extracted and single files could manually be placed in a replicated folder structure.
The latter is the preferred option for production environments as clients can release their patches into production as part of their own schedule.
A configuration option allows you to configure all required parameters.
The INpPatcher is clever enough to evaluate your current server and the available patches, and to thus know exactly what it has to do.
It can read and evaluate your current settings and configurations and use those settings for the patch.
The INpPatcher will do a dynamic backup of each and every file that you are replacing. Thus no full backup is required.
Backups are placed in a user specifiable folder and are versioned according to the current date/time stamp, e.g. INpensions_Backup_200811151305.zip, etc.
Note:
Currently, the INpPatcher does NOT do housekeeping, thus you will have to remove older backups manually (this could be changed in the future releases.)
The INpPatcher will allow you the option to specify the location of where you want to place the file server files. This will usually be a folder on the application server itself.
Note:
Currently, the INpPatcher can only update a single file server instance. You will have to update branch or remote file servers manually (future enhancements may include this).
The INpPatcher is clever enough to first back up the current file (it makes a copy of the current file and then adds the date/time-stamp to it, e.g. AEENV_800807081305.BAK).
It then reads the current AEENV file and gets the following from it:
- Database User Name
- Database User Password
It then looks at what you have given it to patch and will patch the AEENV accordingly.
One of two options (full or additional)
Full (AEENV will be replaced):
- Place a full AEENV (no extension) file under \Application Server\CA\AllFusion Gen\Gen\ (AEENV) and the complete AEENV file will be replaced by your new one
- All entries must contain the following string: “DBUser DBPassword INpensions” and this will be automatically updated to the details from the previous AEENV.
Additional Entries (lines will be added to the current AEENV):
- Place only an AEENV.TXT under \Application Server\CA\AllFusion Gen\Gen\ and it will append the contents of the .TXT file to the current AEENV file.
- All new entries must contain the following string:
xxxx yyyyyyyy zzzzzzzz DBUser DBPassword INpensions
This will be automatically updated to the details from the previous AEENV.
The INpPatcher can and will always update all COM+/MTSPackage(s).
The INpPatcher will always replace all available MTSPackages, as it needs to export the proxies for successful application to any existing web servers.
The web servers will automatically un-install all their remote proxies and will fetch the new application proxies from a share on the application server. It will then automatically install all required proxies.
The INpPatcher can update the registry from a standard .REG format text file automatically.
Requirement:
A standard registry file, i.e. \Application Server\AppServer.Reg or \Web Server\WebServer.Reg (only use these names!)
Typical Layout: (Regedit Version 4 or 5)
AppServer.Reg:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Bytes Software]
"Version"="5.0"
You have the option to configure the INpPatcher to automatically apply the database patches. You would be required to give the database scripts to your DBA, should you decide not to choose this option.
Requirement:
A folder in the zipped patch called \Database Server\.
Any .TXT file in this folder will be renamed to .SQL and then all .SQL scripts will be applied to the default system database in a numerical, then alphabetical order (standard MSDOS behaviour).
Note:
This means that script 02_data.sql or 14_structure.sql will be applied before AAA.sql, etc.
- The INpPatcher executable file (\Program Files\Bytes Software\Tools\AutoPatch\)
- The INpPatchEnabler executable file (\Program Files\Bytes Software\Tools\AutoPatch\)
- A small free utility called GSAR.EXE (text search and replace facility)
- A Java Class called “GetDataFromUrl.class” (Java web page – “screen-scrape” class)
- A SQL command line application called OSQL.EXE
- A standard .ZIP file(s) containing the new patch.
The .ZIP file(s) may have any name and there may be more than one, i.e. 5.0.7_20080130.zip, PTFor5.0_200807081305.zip, ApplicationServer.zip and WebServer.zip, etc.
Note:
The name of the ZIP and Database scripts may NOT contain any spaces.
Folder structure format of the .ZIP file is standard as per installation. View the standard folder structure in the file “Standard_Patch.ZIP” in the following folder:
\Program Files\Bytes Software\Tools\AutoPatch