Integration of Package Types - Intergraph Smart Materials - 10.1 - Administration & Configuration - Hexagon

HxGN SMAT Connector for Jovix

Language
English
Product
Intergraph Smart Materials
Subproduct
Jovix
Search by Category
Administration & Configuration
Smart Materials/Smart Reference Data Version
10.1

This section discusses the integration of package types from Smart Materials to Jovix.

  • Package Types are integrated from Smart Materials to Jovix as Container Type in Jovix.

  • Package Types are used during Containers creation in Jovix

  • New and existing Package Types can also be integrated.

Package Type name must not be changed either in Smart Materials or in Jovix.

Prerequisite

Before you begin Jovix to Smart Materials integration of Release Note Packages, you must execute the following script on the database server:

  • execute MI_JVX_PCK_RN_CONTAINERS.integrate_existing_pck_types

Triggering point for integration

Creation of a new package type in Smart Materials triggers integration of package type to Jovix.

Package type in Smart Materials is not project specific. Hence, package type is integrated to all the Jovix projects that are defined in the project default ZI_JX_PROJ.

Log files

You can check the Package Type integration status in the log files that are saved in the path defined in the DBA setting LOG_FILE_DEST or from Jovix Integration Report in Smart Materials Web. The naming format of package type log files is as follows:

JOVIX_ADD_PCK_TYPE_SMAT_<PCK TYPE NAME>_<Date in dd-mm-yyyy_Time in hhmmss>.log

Integration of existing package types

To start integration of existing package types from Smart Materials to Jovix, you must execute the following script on the database server:

execute MI_JVX_PCK_RN_CONTAINERS.integrate_existing_pck_types

Log files

You can check the integration status in the log files that are saved in the path defined in the DBA setting LOG_FILE_DEST. The naming format of warehouse log files is as follows:

JOVIX_ALL_PCKTYPES_EXISTING_<Date in dd-mm-yyyy_Time in hhmmss>.log