Update information
IBM® Safer Payments 6.3.1.04 includes changes that might require you to take action.
Read relevant update information
Compare the current operational version to the version that you want to install. Read update information topics that are relevant to your situation.
| If you install a... | Read update information topics for ... | For example, if the version changes from ... | Read update information topics for... |
|---|---|---|---|
| Fix pack | All fix packs between the two versions | 6.3.0.01 to 6.3.1.09 | 6.3.0.01 and up to 6.3.1.09 |
| Major release | The target version up to the fix pack that you are installing | 6.2.x to 6.3.1.09 | 6.3.0.00 and 6.3.x up to 6.3.1.09 |
| Major release and skip one major release | The major release for the skipped version and all topics in the target version up to the fix pack that you are installing | 6.1.x to 6.3.1.09 | 6.2.0.00, 6.3.0.00, and 6.3.x up to 6.3.1.09 |
| Major release and skip multiple major releases | The major release for the skipped versions and all topics in the target version up to the fix pack that you are installing | 6.0.x to 6.3.1.09 | 6.1.0.00, 6.2.0.00, 6.3.0.00, and 6.3.x up to 6.3.1.09 |
If needed, see:
6.3.1.04 Update information
- Pmml files that are larger than 500 MB can now be uploaded. Parsing pmml files can temporarily but significantly increase memory consumption on the server side. The increase is larger for larger files.
- Previously, if retention by time was used, empty DDC files were created for attributes that are not stored. The problem is now fixed but it is best to remove the DDC files from the file system. Use the file name to identify the DDC files for attributes. The files contain the attribute UID in their file name.
- If you encountered problems with attribute purging before the update (log message 520), force a full purge of all affected attributes after the update. First, create a challenger revision and deactivate purging for each affected attribute. Then, activate purging again and perform a golive. A full purge is performed during the next end of day job. All the old transaction records are securely delete from memory and disk.
- During the upgrade, it is not possible to create a new mandator while different instances are on different versions. If you need to create a new mandator, wait until all instances are upgraded.
- To improve defense against a Slowloris DOS attack, set the following new
fields:
- Click and click an instance.
- On the tab, select Enable incoming connection limit. Enter a connection threshold in Incoming connection limit.
- Repeat on the tab.
- Repeat for other instances.
- Set the new option to control whether white spaces are included in JSON responses. In the 6.5.0.01, 6.4.2.02, and 6.3.1.03 releases, a change was introduced that omitted white spaces in the JSON responses over MCI. Now you can control it.