Recently new customer requirements, in the form of Excel data, the contents of the data table, through the AS2 protocol transfer to the client side, originally intended to use stored procedures directly output Excel, but a think, ODI such a powerful tool should be able to directly convert, so reference the official standard document, test success, OK, No more verbose, follow the steps to explain:
- Building a model
The ODI is exported, first of all to have the source and the destination model, simply say from the---to
Here we export from view to file, then we need to establish the model and file model of the view.
Create a file model first.
Create Model folder, name casually, here's my name files:
After creating the Model folder, right click on the Model folder files, pop-up menu, select New Model, New model
New model such as: Define tab page, fill in the name, because it is the file model, so the technology to choose the file logic scheme to choose FLAT_FILES_SRC, Other tab can also default.
After setting up the model, right click, Pop up the following menu, select New datastore:
Create a new data store, such as: In the Define tab page, enter a name, the resource name here to select your own defined CSV file.
In the File Tabl page, select the file format, enter the field delimiter
In the Column tab page, select Reverse engineering, the system automatically put the CSV file column, read out, such as
The CSV format is as follows: note here that all fields are in one column, separated by commas.
So far, the file data store has been established.
The following establishes the data store for the view:
Views are stored in a file store similar to:
Build the Model:
Reverse engineering: I'm here to view, if it's a table or something, you can choose as you want, the mask is like a filter, my view starts with XXCUS_A01, so I just filter out the view at the beginning.
Select Reverse engineering: When clicked, the view name appears and the new Datastore is selected
The other tab can default to this view data model is complete.
- Build a project
The model is all set up, now we build the project, enter the name and code in the Define tab page
New interface: Expand the new project, find the interface, right-click, create a new interface, in the Definition tab page, enter a name, note that the "staging area is different from the target area" This is now gray, it is not available now, it must be saved before it can be checked.
Click on the interface, the mapping below: In the map, you can see the left and right two boxes, to help just create the view data store dragged to the left, the file data store to the right, and then the left column, drag to the right column, the corresponding mapping settings.
Set flow options: In the Flow tab, select the target area, ikm and options in the property Inspector, and refer to Settings.
The Save interface is set up.
- Perform tests
Select the interface and click the Execute button to test
View execution results in action: for example, to see the execution succeed, insert book 799
Until this test is complete.
Oracle ODI data table export to file