Running the User Database Conversion Application Example

The steps listed in this section are examples for the conversion of an ANSI user database to a Unicode user database.

To convert a database

At the JADE developer site, perform the following actions.
1. Install the ANSI or Unicode binaries in the target system at the same patch level as the source platform.
2. Start a database server on the source platform. Run the JADE Remote Node Access utility, as shown in the following example.
```
jadrap.exe ini=c:\jade\jade.ini path=c:\jade\system
```
3. Start a jadclient application on the target (destination) platform, which is where the converted database is to be located, executing the JadeConvertDb application in a user‑defined schema with the appropriate arguments; for example:
```
jadclient path='c:\jade\system'
          ini=/jade/jade.ini
          schema=user-defined-schema
          app=JadeConvertDb
          startAppParameters
          command-line-arguments
```
  The command‑line‑arguments value, which is specified after the startAppParameters argument, represents the arguments described under "Database Conversion Arguments" that control the JadeConvertDb application.
  
  For details about running jadclient to execute a non‑GUI application within your JADE code, see "Running a Non-GUI Client Application using jadclient".
4. There may be untranslatable characters in the ANSI database, caused by characters having been entered in a different code page. If this occurs, the copyfile.log file, created in the logs directory, indicates which objects had string conversion problems.
  
  It is your responsibility to check this file, investigate which strings in the object were not translatable, and fix them to meet your requirements.
5. Re-run the JadeConvertDb application to rebuild the key ordering of collections for collections that have key values that are non‑ASCII (that is, greater than 127 decimal). This guarantees that referential integrity is maintained for such collections.
  
  To rebuild the key ordering of collections in the Unicode database following the conversion of an ANSI database to a Unicode database, specify the rebuildDicts argument with a value of true after the startAppParameters argument when running the jadclient executable in single user mode, as shown in the following example.
```
unicode/bin/jadclient path=unicode/system
                      ini=unicode/jade.ini
                      schema=user‑defined‑schema
                      server=singleUser
                      app=JadeConvertDb
                      startAppParameters
                      rebuildDicts=true
```
6. In the Unicode system, recompile everything, by extracting all schemas and then reloading them.
7. Run the certify database operation in the JADE Database utility (for details, see "Database Certification", in Chapter 1 of the JADE Database Administration Guide), the JADE Logical Certify utility (for details, see Chapter 5, "JADE Logical Certifier Diagnostic Utility", of the JADE Object Manager Guide), and then extensively test your JADE system.
At your customer site or sites, have the customer perform the following actions.
1. Take a copy of their production database for conversion testing (referred to as verification database).
2. Run the certify database operation in the JADE Database utility (for details, see "Database Certification", in Chapter 1 of the JADE Database Administration Guide) and the JADE Logical Certify utility (for details, see Chapter 5, "JADE Logical Certifier Diagnostic Utility", of the JADE Object Manager Guide) on their ANSI verification database, to ensure a good source database.
3. Test the conversion on the verification database and send all certifydb.log, logical certify log, and copyfile.log files back to you at your JADE developer site.
At the JADE developer site, perform the following actions.
1. Review the customer log files, paying special attention to translation problems of user objects in the copyfile.log file.
2. Produce the fix-up scripts (which could be part of the application schemas) that are appropriate for that customer.
3. Extract all schemas from the Unicode system.
4. Send all schemas and fix-up scripts to the customer.
At your customer site or sites, have the customer perform the following actions.
1. Re-run the conversion of the ANSI verification database.
2. Review the copyfile.log file.
3. Load all Unicode schemas and scripts into the customer Unicode verification database.
4. Run any fix-up scripts, to deal with user objects that had translations problems.
5. Perform solid testing and verification of the customer Unicode verification database.
6. Repeat steps 3.a through 4.e of this instruction until you are happy with newly converted Unicode database.
7. Stop the production ANSI system.
8. Backup the customer binaries and database.
9. Convert the customer production ANSI database.
10. Review the copyfile.log file for any differences from prior test conversions.
11. Load all Unicode schemas and fix-up scripts into new customer Unicode production database.
12. Run any fix-up scripts, to deal with user objects that had translations problems.
13. Perform sanity testing of the converted customer Unicode database.
14. Restart the new Unicode production system.