Abrief synopsis of how a DataSource upload file gets from a client machine onto a TIBCO Collaborative Information manager (CIM) Linux Server and then into CIM when ORACLE is the database.

Abrief synopsis of how a DataSource upload file gets from a client machine onto a TIBCO Collaborative Information manager (CIM) Linux Server and then into CIM when ORACLE is the database.

book

Article ID: KB0094268

calendar_today

Updated On:

Products Versions
TIBCO Collaborative Information Manager -
Not Applicable -

Description

Resolution:
Description:
============
Brief synopsis of how a DataSource upload file gets from a client machine onto a CIM Linux Server and then into CIM when ORACLE is the database.

Environment:
============
Oracle, TIBCO Collaborative Information manager (CIM) / TIBCO Master Data Management (MDM), for all versions of CIM / MDM


Resolution:
===========
When issuing a DataSource upload request from a csv file on a client machine, CIM / MDM uses the HTTP protocol to upload the csv file from the client to the Work directory of the CIM server. The Linux tools sed and awk are used to process the file once it has been delivered to the CIM Server to format the uploaded file and generate the sqlldr script: finally, ORACLE's sqlldr tool is used to actually copy the data into the appropriate Data Fragment (DF) tables.

Issue/Introduction

Abrief synopsis of how a DataSource upload file gets from a client machine onto a TIBCO Collaborative Information manager (CIM) Linux Server and then into CIM when ORACLE is the database.