Missing information on Database migration on Symantec IGA Xpress - Deployment Guide

[William Cheang]

This guide(Symantec IGA Xpress - Deployment Guide) talk about migration from existing vApp implmentation

using the migration tool "mogrify" to export and import ProvisioningData & Userstore data.

But there is no detail info on how to migrate existing DB data to run on R15.

 

Q. Can IGA R15 point direct to DB datasource(IdentityManager iamDB with v14.5) and start up ?

(Existing workflow items(pending approval)- continue to work in R15 ?) 

Q. Can IGA R15 point direct to DB datasource(IdentityPortal sigmadb with v14.5) and start up ?  

Any changes required on IdentityPortal ? 

Note: I have tried directly point IGA R15 to a sigmadb, webapp able to startup, but the "CAIM" connector inside IdentityPortal not able to startup and have error "Can not find sigma.keystore file".

Anyone encounter this error ? on migrating existing data(with role, target permission, approval workflow items), vapp 14.5 to R15 ? 

regards,

William

-------------------------------------------

[Avinash Gupta Boggarapa Venkata]

Hi William
The mogrify tool does not migrate the database. Migration of the actual DB  must be handled separately by your DB administrator.

You can point IGA R15 to an existing Identity Manager (iam) database from v14.5. However, the recommended approach is to take a backup of the existing DB, create a new DB instance using that backup, and point R15 to the new DB. Alternatively, you may perform the DB migration with the help of your DB administrator.

Regarding the sigma.keystore issue, you should not normally encounter this when migrating Identity Portal data. Could you please confirm which version of the mogrify tool you are using?

Thanks
Avinash Gupta

-------------------------------------------

[William Cheang]

Hi Avinash,

I do aware that mogrify does not migrate database.  Do note that my current env is r14.5 vapp(using mssql db), which we plan to migrate to R15.

For the iamDB (identityManager database), as u mentioned we can point R15 to newDB(restored iamdb), which tested working (no issue)

But for IdentityPortal it did not work just by re-point db.

I have found out that my existing sigmadb(which is r14.5), is created with caim_connector_id=222.

and the new sigmadb(r15), is created with caim_connector_id=242

If IdentityPortal(idp) datasource directly point to sigmadb(r14.5), then the caim_connector would not startup & return error. 

So, i exported my new sigmadb(r15)'s caim_connector to json file.

Then on my new IdentityPortal r15, import this caim_connector(r15) and overwrite it and then caim_connector able to startup without error.

At this moment, i still testing functions in IdentityPortal UI whether is it working properly with restored caim_connector. 

(All the above, have nothing todo with DB migration, post configuration changes required after restored DB).

For IG connector part, i have not test yet. So i do not know whether IG datasource can point directly to a restored IG DB.

Appreciate that you can perform end-to-end migration testing which include IM,IP & IG (whether using MSSQL or Oracle DB),

then share with us on any post DB migration steps required to bring up the IM,IP & IG service.

 

regards,

William

-------------------------------------------

[Avinash Gupta Boggarapa Venkata]

Hi William,

You should not be facing the IP connector issue - it is expected to work after migration.

Could you please check whether the sigma.keystore file was included in your export.zip under the path:
export/igx_conf/conf/idp/sigma-keystore-tool/

After migration, the sigma.keystore should be present at:
/opt/brcm/iga/conf/idp/sigma-keystore-tool/sigma.keystore

Can you please confirm whether the sigma.keystore file exists in both of these locations?

Thanks
Avinash Gupta

-------------------------------------------

[William Cheang]

Hi Avinash,

Here's my reply.

export.zip->export/igx_conf/conf/idp/sigma-keystore-tool/

>>> sigma.keystore is present

 

/opt/brcm/iga/conf/idp/sigma-keystore-tool/sigma.keystore

>>> the sigma-keystore-tool folder does not exist, sigma.keystore is not there.

regards,

William

-------------------------------------------

[Avinash Gupta Boggarapa Venkata]

Thanks for the confirmation, William.
Could you please let me know which version of the mogrify tool you are using?

-------------------------------------------

[William Cheang]

i think is this version ->mogrify-15.0.0-136.zip

-------------------------------------------

[Avinash Gupta Boggarapa Venkata]

Hi William,

I tested the migration locally using the same version of the mogrify tool that you mentioned. It is working fine for me. After the migration, the sigma.keystore file is correctly copied to the
/opt/brcm/iga/conf/idp/sigma-keystore-tool
location, and the connector starts successfully in my setup

If this is a test environment, could you please try restoring the conf folder once again and check if the issue persists?

Thanks
Avinash Gupta

-------------------------------------------

[William Cheang]

Hi Avinash,

Thanks for the advice, i think maybe i miss out the step to restore the conf folder, will try again. thank you.

regards,

William

-------------------------------------------

[Rinat Matityahu]

Hi William

We have created a document as database migration seems to be a common query from many of our customers who are evaluating their migration plan.

https://community.broadcom.com/discussion/iga-suite-v15-database-migration-approach

Would love to hear your feedback.

Regards

Rinat

-------------------------------------------