Smart Reference Data can be used to serve multiple Smart 3D catalog databases. To keep track of what was transferred to which Smart 3D instance, and to enable incremental (delta) transfers, each transfer job is assigned to a particular destination. These destinations represent the Smart 3D catalog databases with their specific connection information, like the catalog server, catalog schema server, catalog database, and the catalog schema database.
The destinations are defined on the Destinations screen.
The fields in the Destinations block are listed below.
|
Field |
Description |
|---|---|
|
Destination |
The name of the export destination, which will be assigned to the export job on Integration > Smart 3D > Smart 3D Transfer Jobs > Transfer Jobs. |
|
Host Name |
The Smart 3D computer name where the Smart Reference Data Listener is running. This computer can be a middleware node; it does not necessarily need to be on the same computer as the Oracle or SQL Server Smart 3D database. |
|
Site Server |
Oracle database: The TNS alias of the database instance. SQL Server database: The name of the server instance. |
|
Site DB |
Oracle database: The database schema. SQL Server database: The database name within the server instance (for example, TEST_V2011R1_SDB).
|
|
DB Provider |
Select Oracle for an Oracle Smart 3D database; select MSSQL for a Microsoft SQL Server Smart 3D database. |
|
Catalog DB |
The container for the reference data that is supplied by Smart Reference Data.
|
|
Catalog Server |
The node/computer where the catalog database is running |
|
Catalog Schema Server |
The node/computer where the catalog schema database is running. |
|
Catalog Schema DB |
The container for the schema data that is supplied by Smart Reference Data, like custom attributes and codelists. |
|
Run CIP |
Default for the Run CIP is No for all transfer jobs created for this destination. |
|
Production |
If this check box is selected, it indicates that the destination is a production destination. |
|
Prod. Dest. |
Specifies the production destination for the destination. A list of values is available. Only destinations with the Production check box selected are shown in the LOV. A production destination can only be assigned to one destination. |
|
Comment |
Enter a comment or description for the destination. |
|
Symbol Share Path |
Specifies the shared content folder in Smart 3D where exported Smart 3D symbol DLLs are stored. |
Pay close attention to the case-sensitivity of the site database entry.
The structure that is assigned to the destination must be defined on the Catalog Structure field. For more information, see Catalog Structures.
Each end node element in a catalog structure can have one or more sheets attached.
This structure is used on Destination Data to display the inventory data per destination. The inventory reflects the status of the reference data transferred to the Smart 3D destination. Based on the inventory data, the transfer jobs indicate data as added, modified, or deleted compared to previous jobs.
The destination appears in the Destination field. If the Production Destination indicator is set to Yes, the destination is a production destination. In the Production Destination field, the production destination for the destination is shown.
Here you can manually change values or add missing values. After saving the changes, re-query the data. All changed or added values are highlighted with a red background color for the Sort Order values.
When a new export job run for this destination is started, all these manual modifications are applied in the Fill interface tables stage. For more information, see Job Results.