Datastores

A datastore is a structure that allows data to be stored. It can be a table, a file, a message queue or any other data structure accessible by middleware used by Oracle Data Integrator (JDBC/ODBC, JMS or JNDI).

Definition

Property	Definition
Name	Name of the Datastore. This is the name that appears in the trees and that is used to reference the datastore from a project (interface, etc). This name should be different from the resource name, if the latter is unknown or not very clear. For example, if the model contains tables named C3556F or C5677D, you can give them more explicit names, such as CUSTOMER or ORDER, leaving C3556F and C5677D as resource names.
Datastore Type	The type of object the datastore represents.
OLAP Type	Table type in a multidimensional model for Online Analytic Processing (OLAP): Fact table Dimension Slowly Changing Dimension
Resource Name	Name of the object in the form recognized by the data server which stores it. This may be a table name or a file name.
Alias	This is a short name used in check and filter expressions. This name must be used systematically before each column name to allow cross-references to be compiled. For example, for the table CUSTOMER, the alias CUS can be given. In this case, the expression of the condition CLIENT_TYPE could be CUS.TYPE in ('A', 'S', 'D'). The alias name is not necessarily unique for all tables in a certain model, its only purpose is to make writing expressions easier and to make managing cross-references possible.
Description	Detailed description of the datastore.
Number of rows	Number of datastore rows obtained by clicking on refresh.

Files

This tab appears only for datastores attached to a file technology.

Property	Definition
File Format	Format of the file datastore: Delimited : The fields of a line are separated by a record separator. Fixed : The fields of a line are not separated, but their length is fixed.
Header (number of lines)	Number of lines at the beginning of the file that are not data. This lines are ignored.
Record separator	One or several characters separating lines (or records) in the file: MS-DOS : DOS carriage return Unix : UNIX carriage return Other : Free text you can input as characters or hexadecimal codes.
Field Separator	One ore several characters separating the fields in a record. Tabulation Space Other : Free text you can input as characters or hexadecimal codes.
Text delimiter	Pair of characters delimiting a STRING field.
Decimal separator	Character separating the integer and decimal part of a NUMERIC.

Column

This tab enables an overall view of the datastore columns to be displayed, and to be added and deleted. The buttons Reverse and Reverse COBOL Copybook allow you to reverse-engineer the columns of a file in the following conditions:

Reverse: This reverse-engineering launches a standard reverse for the current datastore.
Reverse: This reverse-engineering is also possible for a delimited file. The column names are retrieved on the header line of the file, or are automatically generated. The length of the columns are set with default values, and must be redefined manually. If the file is a fixed file, this button opens a Wizard for defining the columns.
Reverse COBOL Copybook: This reverse-engineering is possible for a Fixed file when you have its description file as a COBOL Copybook format. For more information, see Reverse a COBOL Copybook.

Automatic adjustment: With this option selected for a fixed file only, starting positions are automatically adjusted as a function of column widths, to avoid gaps and overlaps. For example, if you increase the width of the first column from 5 to 16, then the starting position of every other column will be increased by 11 characters. It is not possible to manually specify the starting position of a column when Automatic adjustment is enabled.

Control

This procedure allows you to execute a static control of the data stored in the Datastore. This procedure is executed on a context specified when the control is launched. This check uses the knowledge module shown on the model level.

Journalizing

This tab displays the status of journalizing for the datastore and list of subscribers tracking changes on this datastore, with their subscription creation date.

Services

This tab contains the configuration for generating and deploying data services for this datastore. See Setting Up Data Services for more information.

Property	Description
Deploy as a Data Service	Check this box if you want this datastore to be deployed as a data service.
Data Service Name	Name of the web service generated for this datastore.
Published entity	Name that is used to generate all operations names for the Data Service. For example, if you specify customer as the published entity, the generated operations will be named addcustomer, getcustomer, etc.