This section describes different methods for migrating IBM SmartCloud Entry to a new release.
There are several options for migrating IBM SmartCloud Entry to a new release:
v Manually migrating to a new release v Migrating from one system to another
v Migrating to a version 3.1 IBM SmartCloud Entry for System x virtual appliance v Migrating a Derby database to a DB2 database
Migrating to a new release
You can migrate your IBM SmartCloud Entry configuration when you are installing a new release.
To migrate data and configuration files that are not migrated by the installer or to manually migrate your data and configurations, follow the instructions in these topics. When you migrate data in IBM
SmartCloud Entry you must migrate sequentially; you cannot skip a version. For example, if you want to migrate IBM SmartCloud Entry version 2.3 to version 3.1, you need to migrate from version 2.3 to version 2.4 first. Before you migrate to the latest version, ensure that all available fix packs are applied.
Then, migrate from IBM SmartCloud Entry version 2.4 (with fix packs) to version 3.1.
To migrate IBM SmartCloud Entry to a new release, take the following general steps:
v Migrate your configuration v Migrate your data
v (Optional) Manually migrate any remaining configuration files
Migrating your configuration
When you migrate to a new version of IBM SmartCloud Entry, you can choose to migrate all of your preferences from one set of configuration files to the new set.
To migrate your preferences from one set of configuration files to the new set, use the following OSGi command:
migrateConfig [source directory]
where source directory is the location of the previous IBM SmartCloud Entry release configuration files.
Running this command migrates the following configuration files:
v cfs.keystone v ldap.xml
v deployment.properties
v authentication.properties: admin.username, admin.password, and admin.name should not be updated.
v email.properties v messaging.properties v metering.properties v billing.properties v web.properties v *.jks
v products/*.xml
© Copyright IBM Corp. 2013 35
Example
To migrate configuration files from a previous version, run the following command:
migrateConfig C:\oldSKC\.skc
Migrating your data
When you are migrating to a new version of IBM SmartCloud Entry, you can choose to migrate data from your previous database.
Before you begin
To prepare for the data migration, follow these steps:
1. Ensure that the target database exists.
2. In your browser, log out and close all open IBM SmartCloud Entry windows.
Procedure
To migrate your data, use the following OSGi command:
upgradeDatabase 'DB2_Path' 'DB2_User_Name' 'DB2_password'
where DB2_Path is the path of the DB2 database, DB2_User_Name is the name of the DB2 administrator, and DB2_password is the password for the DB2 administrator.
Note: DB2_User_Name and DB2_password are only needed when migrating data from a DB2 database.
Notes:
v The upgradeDatabase command supports only major versions of databases.
v The source database must be Derby or DB2.
v Only approved requests can be migrated, while others such as pending requests, rejected requests, and withdrawn requests cannot be migrated. If the approved requests related instances have been deleted, they cannot be migrated either.
v If any errors occur during migration, renew the target database and run the upgradeDatabase command again.
Results
You can see migration details in the console.
Example
v To migrate your data from a Derby database, run the following command:
upgradeDatabase 'C:\oldSKC\.skc\'
v To migrate your data from a DB2 database, run the following command:
upgradeDatabase '//localhost:50001/skc''db2admin' 'db2passwd'
What to do next
You must restart IBM SmartCloud Entry after migration.
Migrating configuration manually
Some configuration information must be migrated manually.
This configuration information includes:
v Network configuration v Security relevant files v Logging.properties file v skc.ini file
Note: When migrating configuration information for a Microsoft Windows 2008 installation, you must manually configure the cloud connection.
Migrating from one system to another
You can migrate your IBM SmartCloud Entry configuration from one system to another system.
About this task
Note: Migrating a configuration from one system to another replaces the configuration on the target system.
To migrate IBM SmartCloud Entry from one system to another, follow these steps:
Procedure
1. Shut down IBM SmartCloud Entry on the target system.
2. Copy the .SCE31 directory from the source system to the target system, overwriting the .SCE31 directory on the target system.
3. Update the directory path in the logging.properties file to the following:
java.util.logging.FileHandler.pattern=/home/sysadmin/.SCE31/logs/skc-%g.log 4. Update the directory path in the server.properties file to the following:
org.eclipse.equinox.http.jetty.ssl.keystore=/home/sysadmin/.SCE31/.keystore
5. Use the appropriate option on the sceappmgr menu to generate a new SimpleToken on the target system.
6. Start IBM SmartCloud Entry on the target system.
The configuration from the source system is now available on the target system.
Migrating from version 2.4 to a version 3.1 appliance
You can migrate IBM SmartCloud Entry version 2.4 to a version 3.1 appliance.
About this task
To migrate to a version 3.1 appliance, follow these steps:
Procedure
1. Copy the version 2.4 version on this system to the following directory:
/home/sysadmin/
Use one of the following methods to copy this information:
v scp
For example, from the remote host where the previous version of IBM SmartCloud Entry 2.4 is installed, run a command similar to the following:
scp -r /root/.SCE24 sysadmin@<Appliance IP>:/home/sysadmin/
where Appliance IP is the IP address of the appliance.
v winscp
Chapter 7. Migrating IBM SmartCloud Entry 37
v sftp
For example, you could compress the directory on the remote system, use SFTP to copy the compressed directory to the appliance and then extract it, as follows:
zip -rv SCE24.zip .SCE24 sftp sysadmin@Appliance IP put SCE24.zip
quit and then
ssh sysadmin@Appliance IP unzip SCE24.zip
exit
ssh sysadmin@Appliance IP
where Appliance IP is the IP address of the appliance.
v mount
Note: You can also use FTP to copy files to the appliance, but you cannot use FTP from another host system.
2. Use the appropriate option on the sceappmgr menu to migrate from version 2.4 to a version 3.1 appliance.
This migrates the cloud connections, integrates the properties files, and updates the database.
Migrating a Derby database to DB2 database
Use the migratedatabase command to move the IBM SmartCloud Entry database from an embedded Derby database to an external DB2 database. Migrating to an external DB2 database can improve scaling, performance, and production level data store.
To prepare for the migration process, follow these steps:
1. Ensure that the DB2 database exists and is empty. For instructions about how to create the database, see “Creating a DB2 database for IBM SmartCloud Entry” on page 22.
2. Configure IBM SmartCloud Entry to use DB2. For more information, see “Configuring database” on page 82.
3. In your browser, log out and close all opened IBM SmartCloud Entry windows.
To migrate the current database to the DB2 database, use the following OSGi command:
migrateDatabase source_directory
where source_directory is the property file location. You can see migration details in the console. It is not necessary to restart IBM SmartCloud Entry after migration.
Example: Migrating from a Derby database to a DB2 database
Migrate the Derby database to a DB2 database by running the following command:
migrateDatabase 'C:\oldSCE24\.SCE24\' Notes:
v Only approved requests can be migrated, while others such as pending requests, rejected requests, and withdrawn requests cannot be migrated. Approved requests related instances that have been deleted cannot be migrated.
v If any errors occur during migration, renew DB2 first and try running the migrateDatabase command again.
v To free up the space that is occupied on IBM SmartCloud Entry server, the migrateDatabase command clears the Derby database following the migration. Create a backup of the Derby database before migration.
v During migration, invoice IDs might change.
Chapter 7. Migrating IBM SmartCloud Entry 39