Inactivating Unreferenced Repository Objects

The Repository Crawler (RepCrawler) utility optionally identifies unreferenced Repository objects and inactivates them. The list of objects checked includes:

• Screen

• View

• Applet

• Business Object

• Business Component

• Integration Objects

• Link

• Pick List

• Task Group

• Task

The benefit of running the utility is that having fewer active objects in the Repository will result in a faster Siebel CRM Upgrade and on-going maintenance of your Siebel CRM Enterprise Software.

Note: The process of inactivating Unreferenced Repository Objects can only be run before the upgrade. It cannot be run after the Upgrade.

Running the Inactivating Unreferenced Repository Objects Utility

1. Navigate to the following directory:

   Windows: $DbsrvrRoot\common folder

   UNIX: $DbsrvrRoot\common folder

2. Run the following command:

   java -jar RepCrawler.jar /s [Siebel Tool/Server Path, one folder up BIN directory]
   /c [DSN] /d [Database Type - Oracle, DB2UDB, MSSQL or DB2390 ] /u [Database User]
   /p [Database Password]  /o [Log directory] /t [Table Owner] /r "Prior Customer 
   Repository" /l [logfilename] /j [Custom Script Directory] /a Y /z [DbsrvrRoot\common 
   path]
   

   RepCrawler refers to the following files (present in the dbsrvr/common folder) to determine whether all active objects for active applications are referenced in the code and repository, and subsequently whether to inactivate those objects or not:

   • RepSanitizationRules.xml. This rules file defines the relationship between objects. The use of object references will be determined by the relationships defined in this file.

   • RefReferenceObjects.txt. This blocklist file contains a list of all the default (out-of-the-box) objects used by Siebel. Customers can expand this list by adding objects, which they do not want to inactivate as part of the RepCrawler process, to this list.

   After RepCrawler runs, any objects which are not referenced in the code and repository will be inactivated.

3. Review the RepCrawler log and verify that RepCrawler ran without errors.

   Windows: $SiebelLogDir\RepCrawler.log

   UNIX: $SiebelLogDir/ RepCrawler.log

4. Review the RepCrawler reports to see the inactive objects.

   • RepCrawler.html. A report where you can see the inactive objects.

   • RepcrawlerLog.log. A log folder that contains all SQL logs executed during the Repcrawler process.

   • repcrawler.js. A data file in JSON format of all inactive objects used in the HTML report.