Driver Parameters for the Siebel - Unity Data Export Engine

The following table provides the definitions and default values for several driver parameters for the Siebel Unity Data Export engine.

Parameter Name Default Value Required Purpose or Definition

Batch Split Size

1000

Y

The number of records representing the batch size threshold for each batch during initial data export. If the batch size exceeds this number of records, then this batch is split into multiple batches, with a separate job for each batch.

Batch Submit Size

100

Y

The value must be lower than the value of Batch Split Size. Each job fetches this many records and invokes the adapter service to write the data into a CSV file. A new job repeats this process until all records in all batches have been processed.

Charset

UTF-8

Y

The character set of the data. Supported values are UTF-8 or UTF-16.

Delete File After Upload

Y

N

Deletes the CSV file after import if the value is Y or the parameter does not exist. Otherwise, the file is not deleted.

ExportOnly

N

Y

If the value is N, then CSV files are uploaded in OOS. Otherwise, the CSV files are generated in the path specified in the filepath parameter.

bucketname

Not applicable

N

The name of the OOS bucket where the CSV file is to be uploaded. This parameter is required only where ExportOnly is set to N.

directory

Not applicable

N

The name of the directory under the OOS bucket. If this parameter is left empty, the file is uploaded into the OOS bucket at the top level.

filepath

Not applicable

Y

The file path where the CSV files are created. This path must be accessible to the Siebel Server where the Search component group is enabled. Also, it must be accessible to the Configuration Agent that runs the JBS.

namespace

Not applicable

N

The name space of the OOS.

Note: For security hardening, the following parameters are deprecated in the Data Export Administration:
  • fingerprint
  • key_file
  • region
  • tenancy
  • UserId
This improves the security by moving sensitive authentication data (especially private key metadata) out of UI-maintained driver parameters and into a server-side configuration file.

For more details, see OCI Authentication Parameters.