Data Interchange Services client uses three different databases, two of which can have multiple occurrences. The three databases are: Data Interchange Services client database, Document Manager database, and Configuration database.
A Data Interchange Services client database contains build time data and runtime data. This database is used only by Data Interchange Services client. It is used to develop and maintain maps, document definitions, and runtime objects such as control strings, code lists, translation tables, User Exit profiles, and global variables. Runtime data is moved from this database to a corresponding Document Manager database using export and import functions.
Data Interchange Services uses WebSphere Partner Gateway's Document Manager database when it is translating documents. The Document Manager database contains only runtime data. Maps and document definitions are not kept in this database. Runtime data is moved to this database from a Data Interchange Services client database using export and import functions. Data Interchange Services client can view and manipulate the data contained in this database. The translator component of WebSphere Partner Gateway typically accesses only the Document Manager database.
The Configuration database is used only by Data Interchange Services client. It contains information used to access the other databases. The information includes queries, the message log, preference information, and information about the other databases defined to Data Interchange Services client. It can reside on a local system or a remote system. The Configuration database can be a single-user database or it can be a shared database.
Build time data consists of maps, ROD document definitions, EDI document definitions, XML schema document definitions, and XML DTD document definitions. Build time data is data that is not directly used in the translation of a document.
Runtime data consists of control strings, code lists, User Exit profiles, translation tables, and global variables. Runtime data is data that is used during translation of a document. The translator component of WebSphere Partner Gateway uses only runtime data.
If you have multiple Data Interchange Services client users and require concurrent access, then define the database in a multi-user database management system. IBM's DB2 can be used for this. Any multi-user database supporting ODBC Version 2 or later can be used by Data Interchange Services client. The Data Definition Language (DDL) used to create databases, tables, and indexes is not the same for every DBMS. Sample DDL is distributed in the WebSphere Partner Gateway installation.
Data Interchange Services client can access many Data Interchange Services client databases and Document Manager databases simultaneously. This allows you to work with multiple databases at one time. Many users set up more than one database. Typically a Data Interchange Services client database is paired with a Document Manager database. You may even establish several pairs of these databases. For instance, you may have a Data Interchange Services client database and Document Manager database pair established for a development environment and additional pairs for test and production environments. All of these can be accessed from the same Data Interchange Services client application.
Each database to be accessed by Data Interchange Services client must be identified to Data Interchange Services client. A database is defined to Data Interchange Services client using a database definition. The databases defined to Data Interchange Services client can be listed by selecting Databases from the View menu. This displays the Databases list window. The list window is used to list and perform maintenance functions on database definitions. Use the Database Editor to add, view, and change information about a database definition. The editor is accessed through the Databases list window.
Data Interchange Services client is installed with a default single user Data Interchange Services client database. The database is located in the install directory. The database is defined to Data Interchange Services client using a database definition called "Development." This database can be used, deleted, or ignored. The ODBC Data Source Name for this default database is "WDIClientWBIC60win." This database can be copied to create additional local databases if desired. It has the name "wdiclientwbic60dev.mdb" in the install directory. Use "Microsoft Access Driver" when creating an ODBC definition for copies of this database using the Windows Data Source Administrator tool.
A database physically located on a user's machine is commonly referred to as a local database. The "Development" database installed with Data Interchange Services client is a local database. Other databases installed by the user on their local machine are also considered to be local databases. There can be more than one local database.