Using Siebel Tools > Archiving Objects > Importing Objects from an Archive >

Using the Command Line to Import an Archive

You can use the command line to import objects from an archive. You can also use the command line to do other work.

To use the command line to import an archive

1. In Siebel Tools, make sure the projects that the import affects are checked out or locked.

   You cannot use the command line to check out or lock these projects. For more information, see Open a command line, and then navigate to the SIEBEL_TOOLS_ROOT\BIN folder.

2. Use the following command to run siebdev.exe:

   siebdev.exe /c tools.cfg /d ServerDataSrc /u SADMIN /p MSSQL /ws dev_sadmin_m9 /batchimport "Siebel Repository" merge "C:\Tools75\import.sif" import.log

   Here /ws refers the workspace name and this workspace needs to be in the editable state for import to be successful. You can use the full path or the relative path to the current folder to specify the SIF file and the log file.

To import, also note the following options:

• import_mode determines how to handle a conflict. You can use one of the following values with it:
  • overwrite.
  • merge.
  • skip. If you use skip, and if a corresponding object does not exist in the repository, then there is no conflict and the utility imports the record.

    For information, see Options You Can Choose to Resolve a Conflict.

• sif_files specifies the name of one or more sif files that contains the objects that batchimport imports, such as sif_file1, sif_file2, sif_file_n, or the path to a folder that includes .sif files.
• log_file specifies the name of the file that siebdev uses to log information.

Example of Using the Command Line to Import an Archive

The following example imports an archive:

siebdev.exe /c tools.cfg /d ServerDataSrc /u SADMIN /p MSSQL /ws dev_sadmin_m6 /batchimport "Siebel Repository" overwrite import1.sif, import2.sif" import.log

It uses the overwrite option for conflict resolution. It logs the results to the import.log file. For more information, see Options You Can Choose to Resolve a Conflict.

Example of Importing All Files

The following example imports all files:

siebdev.exe /c tools.cfg /d ServerDataSrc /u SADMIN /p MSSQL /ws dev_sadmin_m4 /batchimport "Siebel Repository" merge C:\23075\Tools\importfiledir import.log

This command imports all files in the following folder:

C:\23075\Tools\importfiledir

It uses the merge option for conflict resolution. It logs the results to the import.log file.