Overall Steps for Cloning BIOVIA Applications. 

1. STOP All BIOVIA application services on Target  environment.
2. STOP All BIOVIA application services except HUB in Source environment.  Export a CloneConfig.xml file and then stop foundation Hub service.
3. Export Source database schemas ( Hub,CISPRo,Compose/Capture and all VAULT schemas( except DIRECT)).

(when importing direct indexes they need to run the below two commands before exporting SYMYXDB schema)

Log in As symyxdb;

select mdlaux.prepareindexexport ('allchemstrucs') from dual;

select mdlaux.prepareindexexport ('allchemrxns') from dual;

1. Import database schemas to sandbox environment. Verify no error and the database sequences are good ( we had recently issue at PPD with DB sequences where we had to perform the whole cloning activity again).
2. Confirm Direct is working ( check direct version, synonyms, index status from DIRECT, SYMYXDB,SYMYXDBUSER and CISPRo schema).
3. Log in as vaultsite:

• Update G_REPOSITORY Table:-

• Update g_repository set databaseconnection=replace(databaseconnection,'HOST=sourcedatabase','HOST=destinationdatabase');
• Update G_REPOSITORY set

Databaseconnection=replace(databaseconnection,'SERVICE_NAME=SRC','SERVICE_NAME=DEST’);

• Commit;

• Update VAULTCONFIG Table:-

• Update VAULTCONFIG set entry=replace(entry,'Source Hub End Point', 'Destination Hub End Point') where NAME='Hub.Endpoint';
• Update VAULTCONFIG set entry=replace(entry, 'Source Vault End Point', 'Destination Vault End Point') where NAME='Hub.AppReg.Vault.VaultEndpoint';
• Commit;

1. Update the CloneConfig.xml file as per instruction and place it in the Hub folder for example C:\\Program Files\\BIOVIA\\Foundaiton\\. (node can be removed if you are configuring a non-load balanced system with load balanced source data).
2. Update the app-config.groovy file at Hub installation folder appropriately . ( changes needed to hub schema password if target environment hub schema password  is different than source hub schema and remove the encryption property completely . Please refer to hub documentation).
3. Restart Hub service in Target Environment .
4. Confirm HUB is running .
5. Start PLP services and see if you still can authenticate using HUB . If not most likely you need to reset the registration, you can delete the PPS\\xmldb\\Objects\\HubConfig.2.xml and reconnect PLP authentication to HUB  and update applications.
6. Change PLP data sources if necessary.
   
7. If BOIVIA Compose is used then please use the steps below  to modify the BIOVIA Compose/Capture Target server installation.  Customers that are not using BIOVIA Compose/Capture may skip this section.​​​​​​​
8. Log into the Target environment Oracle Database as the BIOVIA Foundation schema user.
9. Execute the following SQL commands to delete the BIOVIA Foundation registration entry row for Compose/Capture:

                    delete from COR_HUB_INT_APP_REG;

                     commit;

           Start the Compose/Capture service(s) in the Target environment, which will automatically rebuild the required         

            registration information. Confirm users can access the Compose/Capture features.

For CISPRo:-

1. Start CISPRO and see if its running. If not, remove the CISPro from foundation hub application list and reregister using CISPRO config tool.
2. Run Vault Config tool and update all the database password as needed and click apply( you will also need to put hub user name and password before saving it). This will update all the vault config files and restart all vault services.
3. Confirm all vault pages are loading. If so , log into the vault admin console and update the end points for different application permission to point correct sandbox endpoints ( for example RunProtocol App permission etc).
4. Confirm login to Workbook client .