What are the steps to recreate a remote Aveksa DB?
We would like use the same application configuration, (workflows, connectors, collectors should be kept), but get a new and fresh DB(remove all the content of it)
This really relies on what you have configured in the product because there some dependencies. If you use roles and want to transfer them you need to collect the data (identities / entitlements) before importing the roles.
Exporting the configuration is easy, importing the configuration you need to slice into different steps where you import part of the config first, then run that config before importing the next part of the config.
I would suggest to contact PS to help with the steps that are suitable for your situation
I am basically trying to figure out if I can do something like that-
1. Backup the configuration using one of RSA scripts
2. drop the DB schema
3. Recreate the DB
4. Restore the configuration using RSA script
is there an option?
I would say do it using the below steps.
Let me know if you still face any issues at the above steps.
It is more than just looking for errors. Some dependencies don't give you errors it makes the system do things you didn't want it to do yet. If you import your rules and activate them before you've collected your identities you could have a lot of change requests that start to provision access because you have a joiner rule setup. At step 8 is where it gets tricky
This document might help https://community.rsa.com/docs/DOC-86711
Thanks a lot. This is the kind of answer i was looking for. i will try it.
Retrieving data ...