Bookshelf v7.7: Modifying the Repository

Modifying the Repository

SSSE requires certain repository characteristics that were not included in earlier versions of Siebel 7.7 software. You must modify the repository, then compile and deploy a new Siebel Repository File (SRF).

In order to modify the repository correctly, you must check out certain projects in Siebel Tools, and then import certain SIF files. Table 12 lists these projects and files for your reference as you carry out the procedure that follows.

Table 12. SIF Files to Import and Associated Projects to Check Out
SIF File Name	Projects to Check Out Before Importing SIF	Comments
7722-SSSE-HOR-Base.sif	Table Activity Table Employee Table Opty Table Organization Table Party Table Person Table Project Table Service Request	Adds the DB_LAST_UPD column to tables and adds or updates some indexes in the Siebel Business Applications database.
7722-SSSE-SIA-Base.sif	Table Activity Table Employee Table Opty Table Organization Table Party Table Person Table Project Table Service Request	Adds the DB_LAST_UPD column to tables and adds or updates some indexes in the Siebel Industry Applications database.
7722-SSSE-ServerDomain.sif	Table ServerDomain	Makes data model changes to SSSE objects.
7722-SSSE-Objects.sif	PIM Server Integration PIM Server Integration (UI) PIM Server Integration Engine PIM Server Integration Workflows PIM Server Integration Workflows Level2	Updates existing and creates new SSSE repository objects for the Siebel Business Applications database.
7722-SSSE-SIA-Objects.sif	PIM Server Integration PIM Server Integration (UI) PIM Server Integration Engine PIM Server Integration Workflows PIM Server Integration Workflows Level2	Updates existing and creates new SSSE repository objects for the Siebel Industry Applications database.

Importing these SIF files causes changes in certain database tables. For information about which tables are changed by which SIF files, see Table 13. You will need this information during the procedure that follows.

Table 13. Tables That SIF Files Change
SIF File Name	Changed Tables
7722-SSSE-HOR-Base.sif and 7722-SSSE-SIA-Base.sif	S_ACT_CONTACT S_ACT_EMP S_ADDR_ORG S_ADDR_PER S_CONTACT S_CONTACT_BU S_CONTACT_INFO S_EVT_ACT S_OPTY S_ORG_EXT S_PARTY S_POSTN S_POSTN_CON S_PROJ S_SRV_REQ S_USER
7722-SSSE-ServerDomain.sif	S_SD_EXCH_STATE S_SD_PIM_ROW S_SD_SRCKEY S_SD_STATE_DATA S_SD_SV_PROFILE S_SD_SYNC_INFO S_SD_USERMAP_TS S_SD_USER_MAP S_SD_USR_ACCESS S_SVRDOMAIN_EXT

The following procedure briefly describes how to modify your Siebel repository to make it compatible with SSSE.

NOTE: Several steps in the following procedure require you to overwrite object definitions in the repository. This is necessary because SSSE requires that you remove some parameters from the SRF.

To modify your Siebel repository for use with SSSE

In Siebel Tools, check out the appropriate projects, and then import one of the following SIF files:

For Siebel Business Applications, import the file 7722-SSSE-HOR-Base.sif
For Siebel Industry Applications, import the file 7722-SSSE-SIA-Base.sif
For conflict resolution, select Merge. This will preserve any customizations you have made to your tables. If you have not customized your tables, you can select Overwrite the object definition in the repository, instead. For the list of projects that must be checked out for the SIF import to succeed, see Table 12.

Check out the appropriate projects, and then import the SIF file 7722-SSSE-ServerDomain.sif.

For conflict resolution, select Overwrite the object definition in the repository. For the list of projects that must be checked out for the SIF import to succeed, see Table 12.

Make sure there are no Siebel Servers running against the database.

If servers are running, there will be errors in the next step because the tables that need to be changed will still be in use.

Apply the database table changes by using the Siebel Tools Apply feature.

To use the feature, query for all changed tables, and then apply the changes to the entire query (select Current for the tables in the dialog). Make sure that all tables listed in Table 13 are listed in the query results or other steps in the configuration may fail.

If not all of the tables appear in your query, manually apply the database changes for each of the tables listed in Table 13 by selecting each table and clicking Apply.

For more information about applying changes in Siebel Tools, see Configuring Siebel eBusiness Applications.

Check out the appropriate projects, and then import one of the following SIF files:

For Siebel Business Applications, import the file 7722-SSSE-Objects.sif
For Siebel Industry Applications, import the file 7722-SSSE-SIA-Objects.sif
For conflict resolution, select Overwrite the object definition in the repository. For the list of projects that must be checked out for the SIF import to succeed, see Table 12.

Compile the SRF.

Be sure to check out the new PIM Server Integration Extract Only project and include it among the projects you select before compiling.

Deploy the new SRF to your Siebel Servers.

NOTE: If you are applying 7722-SSSE-HOR-Base.sif in a Microsoft SQL database, certain errors are common—Microsoft SQL servers have an 8K page size and they report errors if any rows that have all columns populated will not be stored. You can ignore the following errors unless you intend to populate all columns in these tables:

01000 (1708): [Microsoft][ODBC SQL Server Driver][SQL Server]Warning: The table 'S_ORG_EXT' has been created but its maximum row size (12201) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

01000 (1708): [Microsoft][ODBC SQL Server Driver][SQL Server]Warning: The table 'S_EVT_ACT' has been created but its maximum row size (9513) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.