Hi All,

ISAM Version 9.0.6 

We have implemented ISAM for one of our customers where runtime database for federations modules uses In-built database. 

In recent times there were issue regarding the connectivity to the database(HVDB). User base in our environment is close to 20L, but the number of users logging in is close to 500. Should we pull the database out of VA to overcome the connectivity issues ? Please suggest 

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar
------------------------------

HI

it gives you more control over managing the database in terms of performance and capacity and hence will be helpful in production use.

------------------------------
Tushar
Tushar
------------------------------

Original Message:
Sent: Sun February 23, 2020 01:19 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi All,

ISAM Version 9.0.6 

We have implemented ISAM for one of our customers where runtime database for federations modules uses In-built database. 

In recent times there were issue regarding the connectivity to the database(HVDB). User base in our environment is close to 20L, but the number of users logging in is close to 500. Should we pull the database out of VA to overcome the connectivity issues ? Please suggest 

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar
------------------------------

Hi Tushar,

is there a way to export the existing data in VA to a external database ? will there be any impact id we directly point the federation runtime to external database.

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar
------------------------------

Original Message:
Sent: Mon February 24, 2020 03:30 AM
From: Tushar Prasad
Subject: Federation Runtime Database

HI

it gives you more control over managing the database in terms of performance and capacity and hence will be helpful in production use.

------------------------------
Tushar
Tushar

Original Message:
Sent: Sun February 23, 2020 01:19 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi All,

ISAM Version 9.0.6 

We have implemented ISAM for one of our customers where runtime database for federations modules uses In-built database. 

In recent times there were issue regarding the connectivity to the database(HVDB). User base in our environment is close to 20L, but the number of users logging in is close to 500. Should we pull the database out of VA to overcome the connectivity issues ? Please suggest 

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar
------------------------------

HI

you can  follow this link

https://www.ibm.com/support/knowledgecenter/en/SSPREK_9.0.6/com.ibm.isam.doc/admin/task/tsk_deploy_extnl_hvdb.html


and then from Appliance, you can export the database into the format which is desired. For example, if you would like to export to DB2 (hvdb) , then select that.

The extracted zip will have instructions to  how to use that data to import into respective external database.

after tuning and other db activity , you can safely switch the runtime HVDB to external database and your federation flow should work fine.


Obviously, you need to do that in pre prod /lower environment .

To directly point to external database, you need to assess whether you need to continue using data in HVDB (for example, device registration,session data, oauth grants)

if you don't need existing data for your flow then you can directly point(but you need to be careful with your existing assessment)







------------------------------
Tushar
Tushar
------------------------------

Original Message:
Sent: Thu February 27, 2020 03:23 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi Tushar,

is there a way to export the existing data in VA to a external database ? will there be any impact id we directly point the federation runtime to external database.

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar

Original Message:
Sent: Mon February 24, 2020 03:30 AM
From: Tushar Prasad
Subject: Federation Runtime Database

HI

it gives you more control over managing the database in terms of performance and capacity and hence will be helpful in production use.

------------------------------
Tushar
Tushar

Original Message:
Sent: Sun February 23, 2020 01:19 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi All,

ISAM Version 9.0.6 

We have implemented ISAM for one of our customers where runtime database for federations modules uses In-built database. 

In recent times there were issue regarding the connectivity to the database(HVDB). User base in our environment is close to 20L, but the number of users logging in is close to 500. Should we pull the database out of VA to overcome the connectivity issues ? Please suggest 

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar
------------------------------

Hi Tuhsar, Rahil

The inbuilt export functionality doesn't work properly. I tried this option to move all configuration data to external database, however it doesn't export all data. We have around 60 federation mapping rules and 20 authentication mechanisms, none of them exported.



------------------------------
Bipin Dash
------------------------------

Original Message:
Sent: Thu February 27, 2020 03:45 AM
From: Tushar Prasad
Subject: Federation Runtime Database

HI

you can  follow this link

https://www.ibm.com/support/knowledgecenter/en/SSPREK_9.0.6/com.ibm.isam.doc/admin/task/tsk_deploy_extnl_hvdb.html


and then from Appliance, you can export the database into the format which is desired. For example, if you would like to export to DB2 (hvdb) , then select that.

The extracted zip will have instructions to  how to use that data to import into respective external database.

after tuning and other db activity , you can safely switch the runtime HVDB to external database and your federation flow should work fine.


Obviously, you need to do that in pre prod /lower environment .

To directly point to external database, you need to assess whether you need to continue using data in HVDB (for example, device registration,session data, oauth grants)

if you don't need existing data for your flow then you can directly point(but you need to be careful with your existing assessment)







------------------------------
Tushar
Tushar

Original Message:
Sent: Thu February 27, 2020 03:23 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi Tushar,

is there a way to export the existing data in VA to a external database ? will there be any impact id we directly point the federation runtime to external database.

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar

Original Message:
Sent: Mon February 24, 2020 03:30 AM
From: Tushar Prasad
Subject: Federation Runtime Database

HI

it gives you more control over managing the database in terms of performance and capacity and hence will be helpful in production use.

------------------------------
Tushar
Tushar

Original Message:
Sent: Sun February 23, 2020 01:19 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi All,

ISAM Version 9.0.6 

We have implemented ISAM for one of our customers where runtime database for federations modules uses In-built database. 

In recent times there were issue regarding the connectivity to the database(HVDB). User base in our environment is close to 20L, but the number of users logging in is close to 500. Should we pull the database out of VA to overcome the connectivity issues ? Please suggest 

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar
------------------------------

Hi Bipin

You might be referring to 907 version where mapping rules are part of file system , not stored in configdb( which is my xx-migrated-xx only)


------------------------------
Tushar
Tushar
------------------------------

Original Message:
Sent: Sun March 01, 2020 08:28 PM
From: Bipin Dash
Subject: Federation Runtime Database

Hi Tuhsar, Rahil

The inbuilt export functionality doesn't work properly. I tried this option to move all configuration data to external database, however it doesn't export all data. We have around 60 federation mapping rules and 20 authentication mechanisms, none of them exported.

For mapping rules, the exported "fim_mapping_rules.lob" file contains only below data

"XX-Migrated-XX"

For auth mechanicsm, "isam_ami_attr_selector_map.lob" file doesn't contain all data

------------------------------
Bipin Dash

Original Message:
Sent: Thu February 27, 2020 03:45 AM
From: Tushar Prasad
Subject: Federation Runtime Database

HI

you can  follow this link

https://www.ibm.com/support/knowledgecenter/en/SSPREK_9.0.6/com.ibm.isam.doc/admin/task/tsk_deploy_extnl_hvdb.html


and then from Appliance, you can export the database into the format which is desired. For example, if you would like to export to DB2 (hvdb) , then select that.

The extracted zip will have instructions to  how to use that data to import into respective external database.

after tuning and other db activity , you can safely switch the runtime HVDB to external database and your federation flow should work fine.


Obviously, you need to do that in pre prod /lower environment .

To directly point to external database, you need to assess whether you need to continue using data in HVDB (for example, device registration,session data, oauth grants)

if you don't need existing data for your flow then you can directly point(but you need to be careful with your existing assessment)







------------------------------
Tushar
Tushar

Original Message:
Sent: Thu February 27, 2020 03:23 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi Tushar,

is there a way to export the existing data in VA to a external database ? will there be any impact id we directly point the federation runtime to external database.

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar

Original Message:
Sent: Mon February 24, 2020 03:30 AM
From: Tushar Prasad
Subject: Federation Runtime Database

HI

it gives you more control over managing the database in terms of performance and capacity and hence will be helpful in production use.

------------------------------
Tushar
Tushar

Original Message:
Sent: Sun February 23, 2020 01:19 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi All,

ISAM Version 9.0.6 

We have implemented ISAM for one of our customers where runtime database for federations modules uses In-built database. 

In recent times there were issue regarding the connectivity to the database(HVDB). User base in our environment is close to 20L, but the number of users logging in is close to 500. Should we pull the database out of VA to overcome the connectivity issues ? Please suggest 

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar
------------------------------

Thank you Tushar for your prompt response. Yes it's 9.0.7. I think We have to use REST API to export/import.

------------------------------
Bipin Dash
------------------------------

Original Message:
Sent: Sun March 01, 2020 09:22 PM
From: Tushar Prasad
Subject: Federation Runtime Database

Hi Bipin

You might be referring to 907 version where mapping rules are part of file system , not stored in configdb( which is my xx-migrated-xx only)


------------------------------
Tushar
Tushar

Original Message:
Sent: Sun March 01, 2020 08:28 PM
From: Bipin Dash
Subject: Federation Runtime Database

Hi Tuhsar, Rahil

The inbuilt export functionality doesn't work properly. I tried this option to move all configuration data to external database, however it doesn't export all data. We have around 60 federation mapping rules and 20 authentication mechanisms, none of them exported.

For mapping rules, the exported "fim_mapping_rules.lob" file contains only below data

"XX-Migrated-XX"

For auth mechanicsm, "isam_ami_attr_selector_map.lob" file doesn't contain all data

------------------------------
Bipin Dash

Original Message:
Sent: Thu February 27, 2020 03:45 AM
From: Tushar Prasad
Subject: Federation Runtime Database

HI

you can  follow this link

https://www.ibm.com/support/knowledgecenter/en/SSPREK_9.0.6/com.ibm.isam.doc/admin/task/tsk_deploy_extnl_hvdb.html


and then from Appliance, you can export the database into the format which is desired. For example, if you would like to export to DB2 (hvdb) , then select that.

The extracted zip will have instructions to  how to use that data to import into respective external database.

after tuning and other db activity , you can safely switch the runtime HVDB to external database and your federation flow should work fine.


Obviously, you need to do that in pre prod /lower environment .

To directly point to external database, you need to assess whether you need to continue using data in HVDB (for example, device registration,session data, oauth grants)

if you don't need existing data for your flow then you can directly point(but you need to be careful with your existing assessment)







------------------------------
Tushar
Tushar

Original Message:
Sent: Thu February 27, 2020 03:23 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi Tushar,

is there a way to export the existing data in VA to a external database ? will there be any impact id we directly point the federation runtime to external database.

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar

Original Message:
Sent: Mon February 24, 2020 03:30 AM
From: Tushar Prasad
Subject: Federation Runtime Database

HI

it gives you more control over managing the database in terms of performance and capacity and hence will be helpful in production use.

------------------------------
Tushar
Tushar

Original Message:
Sent: Sun February 23, 2020 01:19 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi All,

ISAM Version 9.0.6 

We have implemented ISAM for one of our customers where runtime database for federations modules uses In-built database. 

In recent times there were issue regarding the connectivity to the database(HVDB). User base in our environment is close to 20L, but the number of users logging in is close to 500. Should we pull the database out of VA to overcome the connectivity issues ? Please suggest 

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar
------------------------------

yes, that's right..use Rest API to export and import

------------------------------
Tushar
Tushar
------------------------------

Original Message:
Sent: Sun March 01, 2020 10:00 PM
From: Bipin Dash
Subject: Federation Runtime Database

Thank you Tushar for your prompt response. Yes it's 9.0.7. I think We have to use REST API to export/import.

------------------------------
Bipin Dash

Original Message:
Sent: Sun March 01, 2020 09:22 PM
From: Tushar Prasad
Subject: Federation Runtime Database

Hi Bipin

You might be referring to 907 version where mapping rules are part of file system , not stored in configdb( which is my xx-migrated-xx only)


------------------------------
Tushar
Tushar

Original Message:
Sent: Sun March 01, 2020 08:28 PM
From: Bipin Dash
Subject: Federation Runtime Database

Hi Tuhsar, Rahil

The inbuilt export functionality doesn't work properly. I tried this option to move all configuration data to external database, however it doesn't export all data. We have around 60 federation mapping rules and 20 authentication mechanisms, none of them exported.

For mapping rules, the exported "fim_mapping_rules.lob" file contains only below data

"XX-Migrated-XX"

For auth mechanicsm, "isam_ami_attr_selector_map.lob" file doesn't contain all data

------------------------------
Bipin Dash

Original Message:
Sent: Thu February 27, 2020 03:45 AM
From: Tushar Prasad
Subject: Federation Runtime Database

HI

you can  follow this link

https://www.ibm.com/support/knowledgecenter/en/SSPREK_9.0.6/com.ibm.isam.doc/admin/task/tsk_deploy_extnl_hvdb.html


and then from Appliance, you can export the database into the format which is desired. For example, if you would like to export to DB2 (hvdb) , then select that.

The extracted zip will have instructions to  how to use that data to import into respective external database.

after tuning and other db activity , you can safely switch the runtime HVDB to external database and your federation flow should work fine.


Obviously, you need to do that in pre prod /lower environment .

To directly point to external database, you need to assess whether you need to continue using data in HVDB (for example, device registration,session data, oauth grants)

if you don't need existing data for your flow then you can directly point(but you need to be careful with your existing assessment)







------------------------------
Tushar
Tushar

Original Message:
Sent: Thu February 27, 2020 03:23 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi Tushar,

is there a way to export the existing data in VA to a external database ? will there be any impact id we directly point the federation runtime to external database.

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar

Original Message:
Sent: Mon February 24, 2020 03:30 AM
From: Tushar Prasad
Subject: Federation Runtime Database

HI

it gives you more control over managing the database in terms of performance and capacity and hence will be helpful in production use.

------------------------------
Tushar
Tushar

Original Message:
Sent: Sun February 23, 2020 01:19 AM
From: Rahil Anwar
Subject: Federation Runtime Database

Hi All,

ISAM Version 9.0.6 

We have implemented ISAM for one of our customers where runtime database for federations modules uses In-built database. 

In recent times there were issue regarding the connectivity to the database(HVDB). User base in our environment is close to 20L, but the number of users logging in is close to 500. Should we pull the database out of VA to overcome the connectivity issues ? Please suggest 

Thanks and Regards,
Rahil

------------------------------
Rahil Anwar
------------------------------