Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390 > Siebel Repository Import, Export, and Postinstallation Tasks >
Importing and Exporting the Siebel Repository
Repository import is the final step in the Siebel Schema installation process. When you import the Siebel Repository, you populate all the repository tables in the Siebel Database Server with Siebel eBusiness Applications, Release 7.x application objects. Regardless of how many Siebel eBusiness Applications you are using (for example, Siebel Sales, Siebel Service, Siebel Marketing), you load data into the repository tables only once per installation. The Siebel Repository can also be exported into a platform-independent file that can be sent to Siebel Technical Support for analysis in case of problems that cannot be diagnosed by telephone or email. To import the Siebel Repository under Windows
- Launch the Database Server configuration wizard.
- In the Gateway Name Server Address screen, type the following values as you recorded them in your copy of Deployment Planning Worksheet.
- On the Siebel Server Directory screen, perform either of the following tasks:
- Accept the default value displayed in the Siebel Server Directory field. (This is the
SIEBSRVR_ROOT directory, for example, C:\sea7xx\siebsrvr .)
- Click Browse to select an alternate directory path.
To continue, click Next.
- On the Siebel Database Server Directory screen, perform either of the following tasks:
- Accept the default path displayed in the Siebel Database Server Directory field. (This is the
DBSRVR_ROOT directory, for example, C:\sea7xx\dbsrvr .)
- Click Browse to select an alternate directory path.
To continue, click Next.
- On the Database Platform screen, select the database platform you use, in this case, IBM DB2 UDB for z/OS and OS/390.
To continue, click Next.
- On the Siebel Database Operation screen, select Import/Export Repository, and click Next.
- On the Select Repository Operation screen, you can choose from the following options. Select the Import Repository option.
- On the Import Selection screen, indicate the following:
- On the ODBC Data Source Name screen, enter the name of the ODBC data source, for example,
SiebSrvr_SIEBEL , or enter the database alias you prefer to use for the data source. This alias should have been previously registered within DB2 Connect.
NOTE: If you want to work with information on a different database server than the one you currently point to, you can enter the ODBC name of that database server, as long as you have previously registered this as an ODBC data source within DB2 Connect.
The Siebel Server installation process automatically creates the data source, using the syntax: SiebSrvr_ EnterpriseServerName .
To continue, click Next.
- In the Database User Name screen, indicate the following:
- Database User Name. Type the ID used to log into the Siebel Database Server. This user ID should be part of the security group with authorization to set the current SQLID to the schema name.
- Database Password. Type the password for the ID used to log into the Siebel Database Server.
- Database Password (confirm). Retype the password to confirm it.
To continue, click Next.
- On the Siebel Schema Qualifier screen, indicate the following values for your Siebel Schema:
- On the Import Repository Name screen, indicate the following:
- On the Export Repository Name screen, type the following values:
- Export Repository Name. Accept the default name (Siebel Repository) or type another valid name.
- Repository File Name. Accept the default installation path and file name for this repository or type another valid installation path.
To continue, click Next.
- On the Log Output Directory screen, accept the default name (imprep) or type another valid name.
- On the Configuration Parameter Review screen, review the configuration values that you entered on the previous configuration screens:
To apply the configuration now, press "OK".
To apply the configuration later, press "Cancel".
The command line to apply the configuration later is C:\sea7x\siebsrvr\bin\siebupg.exe /m master_imprep.ucf
NOTE: The last line in the prompt is generated dynamically based on the location of your Siebel Server installation.
If a program or system error occurs and you need to rerun the Siebel Upgrade Wizard, you can do so, starting at the point at which the wizard failed, by navigating to \siebsrvr\bin and entering:
siebupg.exe /m master_imprep.ucf
- When the Database Server configuration wizard displays the items to be executed or imported, click OK to begin.
A window appears, displaying information about the repository import activities. Afterwards, a message appears when the repository import is complete.
To verify that the import was successful, review the log files. See Reviewing the Log Files for Repository Import.
TIP: Locate the file master_imprep.ucf in the binary subdirectory of your Siebel Server installation directory and print it out, so that you have a record of the values you entered.
To import the Siebel Repository under UNIX
- Navigate to
$ SIEBEL_HOME and source environment variables, using one of the following commands, depending on the type of shell you use:
Korn or Bourne shell
. ./siebenv.sh
TIP: Make sure there is a space between the initial period and ./siebenv.sh .
C shell
source siebenv.csh
where:
$ SIEBEL_HOME is the location of the Siebel Server root directory.
- Verify whether the values
$ SIEBEL_ROOT and LANGUAGE are correctly set or are empty by entering:
env
If the variables are incorrect or missing, reset them using one of the following commands, as appropriate to the shell you use:
Korn or Bourne shell
SIEBEL_ROOT=New Value ; export SIEBEL_ROOT
LANGUAGE=New Value ; export LANGUAGE
C shell
setenv SIEBEL_ROOT New Value
setenv LANGUAGE New Value
- Go to
$ SIEBEL_ROOT /bin and enter:
dbsrvr_config.ksh
This launches the Database Server configuration wizard.
- Review the values of the following environment variables and confirm whether the settings are correct by entering either
Y or N.
SIEBEL_ROOT = path of your Siebel installation directory
LANGUAGE = language in which you are installing
NOTE: If either the SIEBEL_ROOT or LANGUAGE value is not set or is incorrect, you must correct them before proceeding.
- Verify and accept the default for the path of your Siebel Server root directory and press ENTER.
- Verify and accept the default for the path of your database server root directory and press ENTER.
- Select your RDBMS platform, in this case, IBM DB2 for z/OS and OS/390.
- From the Siebel Database Operation menu, choose Import/Export Repository.
- Choose one of the following options that corresponds to the procedure you want to complete:
1 - Import Repository. To import the Siebel Repository for the first time with a base language, select this option. Proceed to Step 10.
2 - Add Language to an Existing Repository. If you already imported your Siebel Repository and its base language, select this option to add another language to the repository. See Importing a New Language to Your Repository.
NOTE: You must have already imported your base-language repository before you can add a new language.
3 - Export Repository. Exports the Siebel Repository into a platform-independent file that can be sent to Siebel Technical Support for analysis if needed. Proceed to Step 11.
NOTE: Repository export can also be used to replicate repositories.
If you selected Import Repository, the Import Selection screen appears.
- Specify the applicable import option:
1 - Import Siebel Repository. To import one additional language to your repository, enter 1 . See Importing a New Language to Your Repository.
2 - Import Custom Repository. To import all languages to your repository, enter 2 . Proceed to Step 11.
NOTE: Option 2 is used when you are importing a multilingual repository from a test or development environment.
- Enter the number corresponding with the language in which you want to run your database. (This is known as your base language.)
- Enter the name of the ODBC data source, for example,
SiebSrvr_siebel , or enter the database alias you prefer to use for the data source. This alias should have been previously registered within DB2 Connect.
NOTE: If you want to work with information on a different database server than the one you currently point to, you can enter the ODBC name of that database server, as long as you have previously registered this as an ODBC data source within DB2 Connect.
The Siebel Server installation process automatically creates the data source, using the syntax: SiebSrvr_ EnterpriseServerName .
- Specify the Database User Name.
This is the ID allowed to log into the Siebel Database. This user ID should have authorization to set the CURRENT SQLID, for example, SADMIN.
- Enter the database password.
- Indicate the following values:
- Specify the Siebel Schema Qualifier, for example, SIEBTO.
This is the up to eight-character (all uppercase) identifier that designates the Siebel Schema. This is also an authorization ID. The Schema Qualifier must be in uppercase, must start with a letter, and cannot contain special characters.
- Specify the Security Group ID / Grantee or accept the default (SSEROLE) by pressing
ENTER .
This is the group to whom schema access is being granted.
- Enter the name of your import or export repository, or accept the default,
Siebel Repository .
- Enter the name of your repository file or accept the default,
mstrep.dat.
The utility displays the values entered so far and prompts you as to whether you want to run the Siebel Upgrade Wizard.
- If the values are correct, launch the Siebel Upgrade Wizard (
srvrupgwiz ) by entering Y.
- To change the values you previously entered, rerun the Database Server configuration wizard by entering
dbsrvr_config.ksh . This allows you to reconfigure with different values.
NOTE: If a program or system error occurs and you need to rerun the Siebel Upgrade Wizard, you can do so, starting at the point at which the wizard failed, by navigating to $ SIEBEL_ROOT /bin and entering: srvrupgwiz /m master_imprep.ucf
If the repository import was successful, it displays a message that the repository has been imported. Otherwise, see the log files.
|