Optional Intermediate Repository (IR) Database (DB) Configuration

APM Connect allows dynamic configuration for both data extraction from your EAM system and the configuration of APM data pushed back into your EAM system from APM. This configuration is achieved by manipulating table entries in the Intermediate Repository Database (IRDB).

CAUTION: As you will be editing the IRDB table entries, it is recommended to take a backup of the existing database so that it can be restored in the event the changes you make do not have the desired effect. The backup can be of the entire database that you are modifying.

Database Backup Steps

Procedure

From an elevated command line, execute the following command, replacing postgres with a username with full access to the database labeled database_name:
```
pg_dump -U postgres -Fc database_name > database.dump
```
Additionally, database.dump can be renamed to any name with a .dump extension.
In the event you get a “pg_dump” is not recognized as an internal or external command error, execute using the full path of the postgres installation. An example of full path execution is as follows:
C:\Program Files\PostgreSQL\11\bin\pg_dump” U postgres -Fc database_name > database.dump

Database Restoration Steps

Procedure

From an elevated command line, execute the following command, replacing postgres with a username with full access to the database labeled database_name.
```
pg_restore -U postgres -d database_name database.dump
```
Additionally, database.sql can be renamed to any name with a .sql extension.
In the event you get a “pg_dump” is not recognized as an internal or external command error, execute using the full path of the postgres installation. An example of full path execution is as follows:
C:\Program Files\PostgreSQL\11\bin\ pg_restore” -U postgres -d database_name database.dump

Northbound & Southbound Data Extraction SAP Mapping Configuration

To facilitate a dynamic mapping capability for data extracted from SAP and pushed into APM, the below IRDB tables can be configured. The structure of the tables and fields that are modified during configuration is outlined in subsequent sections of the documentation.

autoextractor_control
autoloader_control
autojoin_control
southbound_mapping_control

Within each table are rows that correspond with steps for data extraction to support the following data types:

Asset Strategy Integration
Equipment
Equipment Technical Characteristics
Functional Location
Functional Location Technical Characteristics
Planned Work Interface
Static Data
Work Management Interface
Work History

Northbound Data Integration Data Flows

During the northbound data integration, each interface follows the following logic:

Southbound Data Integration Data Flows

During the southbound data integration, each interface follows the following logic: