Cross-Platform Considerations

Overview

When migrating or promoting SAS Federation Server to a different platform (for example, migrating from Windows to Linux), you must prepare the SYSCAT database for the destination platform. If applicable, you can also prepare the SQL_LOG database for the destination platform. The preparation must be done before performing the migration or promotion tasks that are presented in this chapter. If you are not changing platforms, you can skip this topic.

Prepare the Database for the Destination Platform

To prepare the SYSCAT database for the destination platform:

Perform a backup of the 2.x or 3.x SYSCAT.TDB file as outlined in Database Backup and Restore. Perform the backup from the 2.x or 3.x installation path. This is an example of the backup command for UNIX:
```
install-path/bin/dfsutil backup -db syscat /tmp/syscat.tbk
```
Move the SYSCAT backup file to the destination machine, where SAS Federation Server 4.1 is installed.
Working in the installation area for 4.1, perform a restore on the backup file. See Database Backup and Restorefor additional details. This is an example of the restore command for UNIX:
```
install-path/bin/dfsutil restore -db syscat /tmp/syscat.tbk
```
Note: The restored file is placed in the /var directory of the 4.1 installation path, and is named SYSCAT.TDB in Windows, and syscat.tdb in UNIX. The location of the restored file is where the cfg.TRANPATH entity is pointing in dfs_entities.dtd. The default directory is usually /var but might be configured for a different path.
To perform a migration, use the 4.1 installation location when prompted for the old 2.x installation location. If you are performing a promotion, you are finished because the database file has been copied to the new location.
(Optional) Repeat the preceding steps for the SQL_LOG transactional database, if needed. However, the SQL_LOG database file does not require migration. The restore places the database in the correct directory of the 4.1 installation area.