Releasing secondary data

In this step, the T24.UPGRADE service releases all the remaining (non-critical) data items as a regular process during the online upgrade of Temenos Transact system. During this stage, the T24.UPGRADE service runs in all the servers (production and upgrade) as the system is in online stage.

Installing Temenos Transact products

Read these configurations to install any Temenos Transact products as part of the secondary upgrade process.

Procedure

1. Login to Temenos Transact.
2. Open the T24.UPGRADE record.
3. Specify Attribute Type as MODULES and Attribute Value as the corresponding Temenos Transact Product that you want to install (here TAXGST).

   To include more than one Temenos Transact products, click the icon to expand the Attribute Type multi-value field.

4. Add these Temenos Transact products in SPF and COMPANY records.
5. Commit T24.UPGRADE to release the secondary data items of these Temenos Transact products.

Installing Temenos Transact updates

Read these configurations to install any Temenos Transact updates as part of the secondary upgrade process.

Procedure

1. Login to Temenos Transact.
2. Open the T24.UPGRADE record.
3. Specify Attribute Type as UPDATES and Attribute Value as YES.

   This step will help to release all required Temenos Transact secondary updates.

   In T24.UPDATE.RELEASE, the DATA.RELEASED field gets updated to C (complete).

   In SPF, T24.UPDATES field gets updated with the list of Temenos Transact updates installed as part of this upgrade process.

Run the T24.UPGRADE service

The T24.UPGRADE service performs the following:

• It releases all the remaining (secondary) data items for the secondary upgrade process and updates the SPF SYSTEM record.

  

• The T24.AUTHORISE service authorizes all the secondary data released during the Temenos Transact.UPGRADE service.

  After authorizing the released secondary data, T24.AUTHORISE updates the Online Upgrade and Last Cache Reset Period fields of SPF system record. So that already running sessions will reset cache once per session (not every day) and refresh with latest data released during this upgrade. For more information, see Cache Reset Mechanism.

  

  

  The already running sessions performs the cache reset on its next request and gets refreshed with released data items in upgrade process without disturbing the production system.

  

  You can check the log message in "Logger servlet".