How To
Summary
The migration to a new environment single or clustering environment for ISIM 7.0
Objective
ISIM7.0 migration option, "how to make ease migration as much as possible".
Plan to migrate a new single or cluster environment.
Environment
ISIM 7.0.1.3 single, and existing data in the DB2 /SDS
Steps
Case 1
The existing data in DB2/SDS and the existing ISIM 7.0.3 and plan to migrate to a new environment either single or cluster on ISIM 7.0.3 .
Consideration If no downtime is not your concern, since the existing LDAP/database used, the current environment has to be down for while until the new configuration is done.
Possible Solution:
-
Create new ISIM VA env using 7.0.1.3 ISO, then, you configure the primary first with the new db/ldap instances, and the once setup is completed - Then, after clone the existing ldap/db from other machine, and go to dashboard and do the reconfigure db/ldap to connect to the DB/LDAP
-
Optional : for clustering environment, create the new cluster to join the new ISIM VA 7.0.1.3 -
Import the keystore from the older ISIM 7.0.1.3 to the new ISIM VA7.01.3 -
Optional : for any custom jar / custom labels, import those -
SSL certificate has to be imported for the new environment again (previously done with the existing ISIM VA.) so that the ISIM adapter/SDI would not be impacted. -
Email Server configuration manually - Manage custom properties again
Case 2
The existing data in DB2/SDS and the existing ISIM 7.0.3, and plan to migrate to a new environment either single or cluster on ISIM 7.0.3.
Consideration Less downtime for current environment however, if you prefer a new environment for DB/LDAP machine.
Possible Solution:
-
Create new ISIM VA env using 7.0.1.3 ISO with a new db/ldap environment, so it has no data. -
export/import data from db/ldap, and import those to the new db/ldap environment -
run reconfigure option against the new db/ldap again ( prefer all same name of db/ldap host, and credentials and etc, make sure the IP is resolved by the host.) -
Optional : for clustering environment, create the new cluster to join the new ISIM VA 7.0.1.3 -
Import the keystore from the older ISIM 7.0.1.3 to the new ISIM VA7.01.3 -
Optional : for any custom jar / custom labels , import those -
SSL certificate has to be imported for the new environment again (previously done with the existing ISIM VA.) so that the ISIM adapter/SDI would not be impacted. -
Email Server configuration - Manage custom properties again
Additional Information
Requirements
The same fixpack and same hostname/machine name for all of VA and Cluster environment
Before making any changes on ISIM VA or Database or LDAP machine, VM level snapshot is required and Database /LDAP backup
References
Do the migrate export ldap/db option on the new db2/ldap machine
Isimkeystore infor
|
You may run after running reconfigure - If they face some issue with SIB or messaging engine then they can clear SIB tables. Please check systemout.log |
please refer https://www-01.ibm.com/support/docview.wss?uid=swg21380384
Execute commands from both "For a single-server configuration" as well as "For a clustered configuration"
Recommended steps below for cleaing up all SIBs infor.
db2 connect to your itimdb name user yourid using password
db2 "delete from ITIMS000.SIB000"
db2 "delete from ITIMS000.SIB001"
db2 "delete from ITIMS000.SIB002"
db2 "delete from ITIMS000.SIBCLASSMAP"
db2 "delete from ITIMS000.SIBKEYS"
db2 "delete from ITIMS000.SIBLISTING"
db2 "delete from ITIMS000.SIBOWNER"
db2 "delete from ITIMS000.SIBOWNERO"
db2 "delete from ITIMS000.SIBXACTS"
db2 "delete from ITIML000.SIB000"
db2 "delete from ITIML000.SIB001"
db2 "delete from ITIML000.SIB002"
db2 "delete from ITIML000.SIBCLASSMAP"
db2 "delete from ITIML000.SIBKEYS"
db2 "delete from ITIML000.SIBLISTING"
db2 "delete from ITIML000.SIBOWNER"
db2 "delete from ITIML000.SIBOWNERO"
db2 "delete from ITIML000.SIBXACTS"
db2 "delete from ITIML001.SIB000"
db2 "delete from ITIML001.SIB001"
db2 "delete from ITIML001.SIB002"
db2 "delete from ITIML001.SIBCLASSMAP"
db2 "delete from ITIML001.SIBKEYS"
db2 "delete from ITIML001.SIBLISTING"
db2 "delete from ITIML001.SIBOWNER"
db2 "delete from ITIML001.SIBOWNERO"
db2 "delete from ITIML001.SIBXACTS"
db2 "delete from ITIML002.SIB000"
db2 "delete from ITIML002.SIB001"
db2 "delete from ITIML002.SIB002"
db2 "delete from ITIML002.SIBCLASSMAP"
db2 "delete from ITIML002.SIBKEYS"
db2 "delete from ITIML002.SIBLISTING"
db2 "delete from ITIML002.SIBOWNER"
db2 "delete from ITIML002.SIBOWNERO"
db2 "delete from ITIML002.SIBXACTS"
db2 commit
How to reconfigure database
Before you reconfigure, create a snapshot to recover from any configuration failures. See Managing the snapshots.
From the Database Server Configuration table, select a record. For example, Identity data store.
Click Reconfigure.
In the Edit Identity data store details window, edit the details. For more information, see Table 1.
Click Save Configuration. A window opens that displays the certificate information.
Click Yes to confirm.
Database improvement before running reconfigure database
SSL certificate reference
Email setting
Isimkeystore upload
From the top-level menu of the Appliance Dashboard, select Configure > Advanced Configuration > Custom File Management.
From the Custom File Management page, upload the itimKeystore.jceks file under directories\data\keystore.
How to move the data for db2
How to migrate/move data for LDAP
Was this topic helpful?
Document Information
Modified date:
21 September 2018
UID
ibm10728993