Configuring for the Bulk Load for PostgreSQL Database
The bulk load service provides a way to mass provision the inventory database with existing parties and items. A configuration file has been provided which needs to be configured with appropriate values before the bulk load is initiated.
- Procedure
- If you have not already, create CSV files containing items, item characteristics, orders, item relationships, parties, and party characteristics, and put these files in a directory on the TIBCO Product and Service Inventory server machine.
- Create a bulk load JSON configuration file (bulkConfig.json) on the TIBCO Product and Service Inventory server machine. For details, see
CSV File and JSON Config File Samples for an example of how the JSON configuration file must be constructed. This file can be saved in the
$PSI_HOME/config/
file. - Configure the following parameters in the bulk load JSON configuration file:
Parameter Description oracleDirectoryName
This is the absolute directory path where the csv files containing the data are to be loaded.
timeStampFormat
This is the timestamp format for the date/time columns that are used in the CSV exported data. Timestamps here follow the PostgreSQL notation. It is possible to customize the date/time format per entity for the date/time type of columns in the source data. One possible timestamp format is: "DD-MON-YYYY HH12.MI.SS PM". An example value of this format is: "01-JAN-2014 05.40.12 PM".
commitSize
Unlike the Oracle database, the bulk load does not use this parameter. Keep the default.
entities
This is the list of entities to load. Each entity to load is a configuration object containing the following parameters:
type
- This parameter defines the type of entity to load. It can be any one of the following types: PARTY, PARTY_CHARACTERISTIC,ITEM, ITEM_CHARACTERISTIC, ITEM_RELATOINSHIP, ITEM_ORDER, ITEM_ORDER_COMMENTdataSourceName
- This is the name of the CSV file.dataSourceColumnList
- This parameter is for the names of the columns in the CSV file. The possible values depend on the type of entity to load. Some columns are mandatory and some are optional. For details, see Mandatory and Optional Columns.
- Configure the path to the bulk load JSON config file in the
ConfigValues_PSIService.json
file. The value to configure isbulk.configuration
.