Release NG Update/Migration Information

This document contains relevant information required to upgrade your installation from 5.06 (SP 00) to DOKA-NG SP1 once the release has been installed. Please do a backup of your database and existing files of your doka directory before you proceed.

These instructions represent migration steps but do not represents the whole runbook. Please evaluate carefully your additionally required checks.
Old SPTs and transactions cannot be processed in the new version.
Therefore, ensure that all pending entries and transactions have been fully processed before starting the migration: No pending transactions, no messages in incoming/outgoing queue, no transactions on pause.
For that please check entries in SPTSEL for incoming, paused, SPTs in correction.
Please make sure that in MGRTSK / MQITSK / SWITSK are no transactions anymore to be processed.

The user who is proceeding with the migration/installation needs Security Admin rights (check DBIUSR, select User and check if the checkbox “Security Administrator” is set for the used user. Please check if this user has the right to start R506S1, if not give him the right to start the transaction in the Doka 5 installation before doing the upgrade.

Please consider following activities:

• Stop manager
• Lock the system

Please ensure that following Helptext will be reduced into a field size of 1952:
inr nam (Kein Spaltenname)
00007568 Freigabestatus 2125

DOKA-NG requires at least TradeDesign components with the following version numbers

• TD Server >= 02.00.0158
• Windows Client >= 2.1.0.241
• TRADE2.EXE >= 3.2.0.5158

Please note, that with DOKA-NG the older versions of TradeDesign are no longer supported.
After unpacking and installation of the technical components please check version numbers via SYSINF, Doka should work as before.

Adjust tdpara.ini as follows:
If line OldDispFrmVersion=48 exists ? delete it

Section [Compatibility] needs following settings: SaveDataUTF8=1
LoadDataLegacyEncoding=CP1252
ShowDisplayLegacyEncoding=CP1252
DBUseUnicode=1

The prerequisite for starting the DNG installation and migration: Have a working Doka 5 installation.

Delete all TTO files from ttolib. Make sure that no old ttos from previous installations are contained in that ttolib folder.
Install the upgrade patch. Please copy all files from the patch into your DOKA-NG installation.

! IMPORTANT !!!!
Please install carefully the TDPARA.INI-file which we distributed separately. Tdpara.ini, tdodbc.ini change datasource!!!

Please check if you have following:

• DNG ttolib
• Folder frame with png/ico files
• atp.xmu
• ct.xxxxxx.xmu – make sure you don’t use files with file extension *.cte
• swm mappings
• ini Folder (no. sysmnu-Files)
• smartform-binaries (pdftk.exe and libiconv.dll)

Tdpara.ini + tdodbc.ini need new database name.
Please change “ProfActive=1” to “=0” in tdpara.ini while doing the migration procedure.

Please start Doka with the known Sysadmin user.

You get a dump because the USR-table is not updated yet. Please click ”OK” and you will led to the SYSADM transaction. After the migration script runs for table USR this dump won’t occur anymore.

General:
The SQL script to be executed will be shown and can either be executed directly or first stored and then passed to the database administration group for execution. Please check logs carefully after each step you have done.

Please start transaction R506S1 via SYSADM transaction.
Press the buttons on the right-hand side in the following order (from top to bottom):

Generates and executes conversion script (Click on Execute button).
In case the error about dropping the index LTD_LEDINR is occuring please execute the rest of the script via SYSSQL.

Adds all new columns to the tables shown in the grid (Click on Execute button). Close DOKA completely, restart it and start the R506S1 transaction again.

Continue with:

Creates and, where required, executes the conversion scripts (Click on Execute button).

Converts Stickerbank in Import Documents and Import Collections

Creates and executes the standard database migration script in a similar way to SYSDBA, but only for the tables shown in the grid (Click on Execute button).

The standard SYSDBA is started.
If you were asked to delete / add module(s) in lists in sysdba.ini please sign them with “OK”.

• Drop table LCK in SYSSQL transaction: “drop table LCK” (Click on Execute button+Commit).
• Drop table CCI in SYSSQL transaction: “drop table CCI” (Click on Execute button+Commit).
• Go back to SYSDBA and when you are asked again to delete/add module(s) in lists in sysdba.ini please sign them with “OK”. Please then convert the database by creating and executing the migration script as usual. Execute it until DNG tells you the database is correct. (Background: the database lists <dyn>, <all>, <sta> etc. needs to be updated to the current state of DNG)
• Run migration script in SYSDBA. After the migration script is completely executed and your log still lists: Information about columns in database tables which are longer as the definition of the datafields log file from 12.04.2019: ( ACK, ACT, BET, GLE, HLP, LED, LID, SMH, TXM ) then proceed as follows:
• Please export the mentioned database tables
• Drop the mentioned database tables
• Create the mentioned database tables
• Import the mentioned database tables
• Run the Migration script again and check the log has no Information anymore about the ACK, ACT, BET, GLE, HLP, LED, LID, SMH, TXM database tables.

Close DOKA completely, restart it.

Continue with:

Start the R506S1 transaction again:

Creates Header Records for Mappings SWM.

Check carefully if the conversion has been completed correctly and that there are no errors nor information.

• Select “all” and click on 'Reorg NRM fields' - this will fill all new search fields in the static data tables. Check the log files.
• Run “Repair INR Counter” Check the log files.

Check the log files.

and run Button “Convert to NCHAR”

Importing code tables and ATP-Records:

Start SYSUPD.
Choose as „Mode of Operation“ – “Import Updates into Current Environment”. Create “Current Update Path” – in case no folder is mentioned, By default the option “Import” will be provided, please use as suggested.

Please make sure that the codetables - xmu files are stored in the selected directory.
Please make sure that atp.xmu is stored in the selected directory.

Switch to the panel “Import”
Check the 3 Checkboxes “InsertNew”, “Insert Overwrites Existing”, “Update existing”. So that only “Delete Existing” checkbox is unchecked. Mark all files and press import.

Then run the sql scripts from the patch from the “update” directory (apf-update.sql). This will add the missing settings to the APF configuration.
After you have imported the ATP-Records for the new transactions we have to setup new ETP entries for them. Start REOETP: Fills Table ETP for new Transactions

• Please Check “Reorganize all Entity Groups” if more than one ETG is defined in your system
• Don't check “Update existing ETP Records with ATP Data”.

Start SYSDBA and run “Reorg NRM fields' for the database tables ATP and ETP.

Import Swift Mappings:
Start DBISWH and click Icon for “Import”.

Enter correct directory where the dbe files are saved.
Select the files and import them.

The cbsconf.ini has to be activated. Please check in REOCBS and activate cbsconf.ini.

With DOKA-NG the whole user interface has been redesigned.
Thus during the release upgrade project i.e. all screens in your overlay have to be updated (Retrofitting) by Surecomp.

The user profiles are now stored in ini\sysmnu*.* (former *.DOB/*.DOM files).
We provide with the first delivery those files. Please check them carefully after the first installation is done for missing transactions. The dob and dom files are not necessary anymore. You can delete them from the ini-folder. To adjust the profiles you can use DBIMNU.

Please undo your previous change to ProfActive=1” in tdpara.ini.

Please check if in the ini folder: seckey.ini with the correct Serial-Number is saved.