You can import Adabas files and thus convert them to a Tamino schema or schema sub-tree. The Adabas Wizard helps you in mapping Adabas data to a Tamino schema.
The imported Adabas file meta-data is embedded in the schema which is currently shown in the Tamino Schema Editor. This may be an existing schema or an empty schema that you have just created using the
command.Important:
The Adabas database needs to be active, and the Entire Network
server must be started. For detailed information about Tamino configuration to
access Adabas, see the document
X-Node Access to
Adabas in X-Node: Mapping to External
Databases of the Tamino Server documentation.
To import Adabas meta-data using the Adabas Wizard
Make sure that the required schema (either an empty schema or an existing schema) is shown in the Tamino Schema Editor.
If you want to import Adabas data into an existing schema, select the element below which the Adabas data is to be inserted.
From the
menu, choose .This command is only available, if the current selection in the tree allows the insertion of Adabas meta-data.
The dialog for the Adabas Wizard is displayed.
To import data directly from an Adabas database, enter the database identification and the number of the file in the appropriate text box. If you want to import from a corresponding Natural DDM File, additionally enter the file name in the Natural DDM File text box. The Natural file must reside on your computer. You can also select the Natural DDM File from the file chooser dialog box.
Choose the
button.The next dialog of the Adabas Wizard appears, providing the Adabas columns for generating the tree in the Schema Editor. If you have not entered a Natural DDM file name, only the short names of the Adabas fields are displayed as column names.
If you have entered a Natural DDM file name, the full column names appear.
Select the check box for each column that you want to use for generating the sub-tree.
You can also use the
or button.Choose the
button.The schema is generated.
You can now view the properties of the schema and of each node. In the Physical Properties pane, for example, you can see that the storage type is XML and that a pure X-Node mapping has been performed. For a description of all available properties, see Properties Explained.