Skip to main content
pdf?stylesheet=default
Blackboard Help

(Optional) Performing a 32-bit to 64-bit Cross-Platform Migration

The information in this topic applies when upgrading from any legacy Blackboard system.

Blackboard Learn Release 9.1 is the first release to offer an entire application and database footprint using 64-bit addressable memory. To take advantage of more addressable memory, Blackboard strongly encourages clients to deploy using 64-bit operating systems (OSs) and sub components (Java and SQL Server or Oracle).

Upgrading Blackboard Academic Suite 8.0 or Blackboard Learn 9.0 on existing hardware to Blackboard Learn 9.1 must occur before migration. Database restore to a 64-bit machine must be completed before running the application server upgrade.

Blackboard Learn 9.1 Service Pack 8 (SP8) requires a 64-bit operating system. Clients upgrading to SP8 must upgrade their operating system before upgrading the application.

Windows

To learn about migrating a Blackboard Learn 9.1 instance operating on a Windows 32-bit platform to Blackboard Learn 9.1 operating on a Windows 64-bit platform, see 32-bit to 64-bit Cross Platform Migration for Windows.

UNIX

To learn about migrating a Blackboard Learn 9.1 instance operating on a UNIX 32-bit platform to Blackboard Learn 9.1 operating on a UNIX 64-bit platform, see 32-bit to 64-bit Cross Platform Migration for UNIX.

 

Errata and Additions

Errata and additions to the above Platform Migration PDFs

Resetting Learn Configuration Parameters

After migration of the database the Blackboard Learn configuration parameters must be reset within the restored database:

  • $DST_APP_HOSTNAME should be replaced with the unqualified hostname of the destination application server,
  • $DST_DB_HOSTNAME should be replaced with the unqualified hostname of the destination database server,
  • $DB_INSTANCE should be replaced with your database instance name and $DOMAIN should be replaced with your DNS domain name. 

Unix

su - oracle 
sqlplus "/ as sysdba"

  • For single-app server environments, the BB_CONFIG_REGISTRY can be updated directly, like so:

update bbadmin.BB_CONFIG_REGISTRY set HOSTNAME = '$DST_APP_HOSTNAME.$DOMAIN';

  • For load-balanced environments, the records in bbadmin.BB_CONFIG_REGISTRY table must be manually deleted. Then, after updating the properties files for each app server (as instructed below in this document) a PushConfigUpdates from each appserver will insert the record for that server’s hostname information.

update bbadmin.BB_INSTANCE set DB_HOST = '%DST_DB_HOSTNAME%'; 
update bbadmin.BB_INSTANCE set DB_INSTANCE = '%DB_INSTANCE%'; 
update bbadmin.BB_INSTANCE set STAT_DB_HOST = '%DST_DB_HOSTNAME%'; 
update bbadmin.BB_INSTANCE_HOST set HOSTNAME = '%DST_APP_HOSTNAME%.%DOMAIN%'; 
update cms.XY_FILE_SYSTEMS set JDBC_CONNECTION_URL = 'jdbc:inetdae7:%DST_DB_HOSTNAME%.%DOMAIN%%DB_INSTANCE%:1433?database=cms_files_users&secureLevel=0' where DISPLAY_NAME = 'cms_files_users'; 
update cms.XY_FILE_SYSTEMS set JDBC_CONNECTION_URL = 'jdbc:inetdae7:%DST_DB_HOSTNAME%.%DOMAIN%%DB_INSTANCE%:1433?database=cms_files_courses&secureLevel=0' where DISPLAY_NAME = 'cms_files_courses'; 
update cms.XY_FILE_SYSTEMS set JDBC_CONNECTION_URL = 'jdbc:inetdae7:%DST_DB_HOSTNAME%.%DOMAIN%%DB_INSTANCE%:1433?database=cms_files_orgs&secureLevel=0' where DISPLAY_NAME = 'cms_files_orgs'; 
update cms.XY_FILE_SYSTEMS set JDBC_CONNECTION_URL = 'jdbc:inetdae7:%DST_DB_HOSTNAME%.%DOMAIN%%DB_INSTANCE%:1433?database=cms_files_inst&secureLevel=0' where DISPLAY_NAME = 'cms_files_inst'; 
update cms.XY_FILE_SYSTEMS set JDBC_CONNECTION_URL = 'jdbc:inetdae7:%DST_DB_HOSTNAME%.%DOMAIN%%DB_INSTANCE%:1433?database=cms_files_library&secureLevel=0' where DISPLAY_NAME = 'cms_files_library'; 
update cms.XY_FILE_SYSTEMS set JDBC_CONNECTION_URL = 'jdbc:inetdae7:%DST_DB_HOSTNAME%.%DOMAIN%%DB_INSTANCE%:1433?database=cms_doc&secureLevel=0' where DISPLAY_NAME = 'cms_doc'; 
exit