Scribd
Upload
32 views2 pages

OTIC Script Modifications Prod

The document provides instructions for modifying an OTIC script to run in a production environment. This includes 1) updating the project name and status when importing, 2) verifying and updating connection information, 3) creating tables in the production OTIC database, and 4) verifying and updating SQL statements, variables, modules, and other aspects of the script to point to production environments and data.

Uploaded by

Caseman Laura
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
32 views2 pages

OTIC Script Modifications Prod

The document provides instructions for modifying an OTIC script to run in a production environment. This includes 1) updating the project name and status when importing, 2) verifying and updating connection information, 3) creating tables in the production OTIC database, and 4) verifying and updating SQL statements, variables, modules, and other aspects of the script to point to production environments and data.

Uploaded by

Caseman Laura
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

OTIC Script Modifications (PROD)

1. While Importing, Update the Project Name to be created from import as


'Prod_Mig_Project_MigUnit' and update the status from Development to Production 
 
2. Update Connections 
 CMIS_Connect_Addition - verify the CMIS RepositoryID is 230 and update the password -
OTIC_user\Ry62sW78@@ 
 Target_CS - verify the CMIS RepositoryID is 230 and update the password - OTIC_user\
Ry62sW78@@ 
 Target_MSSQL_SQL_CS_Repo - Update the source name to 'CS_SQL_Target_PROD', update
the username and password for prod db(csReadWrite\ReadWrite1010@@), 
update the database to 'ContentServer' 
 Test all the Connections 
 
3. create the following tables in Prod OTIC Database by clicking the create table option 
 MAIN_TARGET_PROJECT_OTIC_CTL_EXIST_DOCS 
 T_TARGET_POINTS_IDS 
 TARGET_OTIC_CTL_EXIST_DOCS 
 TARGET_PROJECT_OTIC_CTL_EXIST_DOCS 
 LookUp_Folder 
 T_SOURCES_POINTS_IDS 
 Audit_MainFolderTable 
 Batch_Audit_MainFolderTable 
 BatchTable_Folder 
 MAIN_OTIC_CTL_EXIST_DOCS 
 OTIC_CTL_EXIST_DOCS 
 Projects_OTIC_CTL_EXIST_DOCS 
 TMP_NICKNAME 
 URL_SourceTable 
 Audit_MainDocumentVersionTable 
 BatchTable 
 DocCategLookup 
 Final_Audit_MainDocumentVersionTable 
 ErrorScanTARGET_OTIC_CTL_EXIST_DOCS 
 Table_LLAttrData_CatFixes 
 DELTA_Audit_MainDocumentVersionTable 
 DELTA_TD_Audit_MainFolderTable 
 DELTA_MAIN_OTIC_CTL_EXIST_DOCS 
 DELTA_OTIC_CTL_EXIST_DOCS 
 DELTA_PROJECTS_OTIC_CTL_EXIST_DOCS 
 Z_Table 
 
4. Open Z_MIGRATION_MASTER Table from CS_SystemTables folder and change the connection to
CSPROD_DB_ORACLE 
 
5. Update the Migration Category dataid in CMIS Secondary types(253905) (3 places) 
 
6. Lookup Table - Process - OE/OI - Update the CSID in LT_SourceForScan Lookup Table (Right click
Edit data, then change the folder name, CSID and Parent Folder path) 
 
7. Copy mapping files from OTIC test to OTIC Prod DataSource folder 
 
8. Module - M1_Populate_INIT_TargetIDS - Update Target Folder ID in the script 
 
9. Variable - Verify GVar_Target_Root_PATH 
 
10. Module - M1_PopulateInitTable - Verify the Script 
 
11. Dataset - DS_SourcePoints - Verify the ParentId given in SQL 
 
12. Dataset - DS_Search_DtreeCore_Recursive_AllV - Verify the SQL 
 
13. Variable - Verify GVar_Root_Path 
 
14. Dataset - DS_Select_TARGET_OTIC_CTL_EXIST_DOCS - Verify the SQL 
 
15. Process - Pr6_DocPrep - Module - !!!_IndexCreate - Verify the idx table names. 
 
16. Dataset - DS_FindMissingCats - Update the DefID to 253905 in SQL 

17. Dataset – Update tables in Delta


 Delta_DS_N_GetAllFolders
 DS_Folders_ForDelta

18. Dataset – Update table in Audit_KUAF_Mig > DS_NewObjID_GroupBy_2

You might also like