Command-Line Parameters
This topic describes the available command-line parameters for External Data Loader Client.
You can use the help option to see a list of all the commands that are available. For example, the following command lists all the command-line options.
> java -jar oscdataloader.jar help
You can get the options for each command, by using the option -h for that command. For example, the following command lists the options available for the submit command.
> java -jar oscdataloader.jar submit -h
If you're using a proxy server while importing using the EDLC, then you must specify the proxy parameters in the command-line call. The following example shows how:
java -Dhttps.proxyHost=host_name -Dhttps.proxyPort=80 -jar
oscdataloader.jar listobjects -target-url https://<your_pod> -u importuser -w
Here are the command-line parameters.
Command and Options (Preceded by Hyphen) |
Description |
||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The path where the configuration file is located. |
||||||||||||||||||||||||||
- |
The description of the import job submitted. |
||||||||||||||||||||||||||
-delimiter |
The delimiter used in your source file. The default value is COMMA_DELIMITER. Possible values are:
|
||||||||||||||||||||||||||
- |
The date format that's used in your source CSV file. The default value is ORA_ZCA_US_FORMAT. Possible values are:
|
||||||||||||||||||||||||||
- |
The decimal separator is used in your source file. The default value is Period (.). Possible values are:
|
||||||||||||||||||||||||||
- |
Enable or disable custom business logic for the import job. The default value is false. Possible values are:
|
||||||||||||||||||||||||||
-encoding |
The source file encoding. Possible values are:
|
||||||||||||||||||||||||||
-export |
Download the exported attachment files from the content management server to your local directory. For example,
Make sure that the directory you provide as output path already exists with read and write permissions for the user performing the export. |
||||||||||||||||||||||||||
|
Get log files of an import activity. |
||||||||||||||||||||||||||
- |
Display help text containing possible commands. |
||||||||||||||||||||||||||
|
Show the usage message. |
||||||||||||||||||||||||||
- |
Activate high-volume import for supported objects. By default, this option is set to true for all the supported objects. To use low-volume import, set this option to false. For example,
|
||||||||||||||||||||||||||
|
The import activity identifier of the job. This is used to track the status of the import job. |
||||||||||||||||||||||||||
|
The name of the import job. |
||||||||||||||||||||||||||
|
The name of source CSV file. Provide a file name within 40 characters. |
||||||||||||||||||||||||||
-latest |
Indicates that the import jobs should be sorted by
the latest creation date, when used with the
lists the imports sorted by the latest creation date. This parameter can take the value true or false. A value of true indicates that the imports are sorted by the latest creation date. By default, this parameter has the value false. |
||||||||||||||||||||||||||
- |
The number of import jobs to be listed by the
lists the first 100 import jobs. |
||||||||||||||||||||||||||
|
Get the list of import activities. You can get the
list sorted by latest creation date by using the parameter |
||||||||||||||||||||||||||
|
List the objects supported by External Data Loader Client. |
||||||||||||||||||||||||||
- |
Specify the type of log file to generate. Possible values are Exception, Error, Diagnostic, and All. |
||||||||||||||||||||||||||
|
The mapping number. |
||||||||||||||||||||||||||
-mode |
The import mode which is to be used for the import job. The default mode is CREATE_RECORD. Possible values are:
|
||||||||||||||||||||||||||
- |
The email address to which the import job status would be sent. |
||||||||||||||||||||||||||
- |
The object to import. |
||||||||||||||||||||||||||
- |
The import offset. |
||||||||||||||||||||||||||
-s |
The mode of scheduling the import job which determines whether the import job executes immediately or at a future date. The default value is ONE_TIME_IMMEDIATE. Possible values are:
|
||||||||||||||||||||||||||
|
Save credential in credential store wallet. |
||||||||||||||||||||||||||
|
Split the import data file into multiple smaller files. The Split Size parameter is used to configure the split size that's used by EDLC. You can use either a low-volume split size or a high-volume split size. You can use the split records option to use low-volume split. Low-volume split has a default split size value of 50000 records. You can either set the default split size using the profile option ORA_ZCA_IMPORT_LOW_VOLUME_CHUNK_SIZE, or specify the split size using the split records command. Possible values are 10k,20k,30k,40k,and 50k. Example command:
You can use the high volume split option to use high-volume split. High-volume split has a default split size value of 200000 records. You can either set the default split size using the profile option ORA_ZCA_IMPORT_HIGH_VOLUME_CHUNK_SIZE, or specify the split size using the split records command. Possible values are 100k,200k,300k,400k,and 500k. Example command:
Note: You can use this parameter when the default values
slow down the performance or if an optimum size is recommended for
the data pattern being imported. This parameter is provided to reduce
the number of records that need to split for each EDLC job.
|
||||||||||||||||||||||||||
-st |
Scheduled future time stamp for an import activity job. |
||||||||||||||||||||||||||
|
Retrieve the status of the specified import. |
||||||||||||||||||||||||||
|
Submit file import request in Sales and Fusion Service. |
||||||||||||||||||||||||||
- |
The environment against which the command is run. |
||||||||||||||||||||||||||
- |
The time stamp format used in your source file. The default value is ORA_ZCA_US_FORMAT. Possible values are:
|
||||||||||||||||||||||||||
- |
Specify the user name of the user running the command. |
||||||||||||||||||||||||||
- |
The Credential Store that holds one set of user credentials (user name and password pair). |
||||||||||||||||||||||||||
validate-settings-for- performance |
Validate settings to check high-volume import performance. You
can use this parameter when you have performance issues while import importing
data in high volume for Account, Contact, Address, Relationship, Organization,
and Person objects. To validate the settings, you must pass this parameter as
“true”. When the parameter is set to “true”, then import job validates the
value of the following profile options to determine if the profile options have
been set to the recommended values.
|