Configuring EXPRESS Data Manager (EDM) requires an EDM database (EDM_DB), provided by EPM Jotne is encapsulated in the solution, to facilitate the STEP-based data exchange.

Once the EDM_DB has been created, source and target schemas, STEP-specific schemas, exchange-specific exchange specific EXPRESS-X mappings, and certain query schemas are loaded along with some models. Once all the configuration has been completed, the EDM_DB is stored as a master copy and a single working copy of the database is created to be used by STEP data exchange for staging process.

Only a single instance of an EDM Database can be accessed from a Method Server. But in multiple Method Server environments, the limitation becomes an overhead. To overcome this, you can configure multiple EDM database-based data exchange.

This configuration requires manually copying the master copy of EDM_DB into the working EDM_DBs. The number of copies of EDM_DB to be made is equivalent to the number of MS.

For instance, if you have configured n number of Method Servers for a Windchill, then “n” working copies of EDM_DB have to be created at the same EDM location. Once this is done, then only requests related to EDM-based data exchange can be served by any of these “n” configured working copies of EDM_DB.

For example, if Windchill has three for ground method servers then make copies of <WT_HOME>/edm-home/edm_database/user as user_2 and user_3 in the same location.

For more information, see the “Supported Types” section in Business Field Mapping.