For the Process Data Integration service to work correctly, you must configure the Meridium Notification Service by modifying the file Meridium.Service.Notification.exe.config on the GE Digital APM Server.
Steps
If you have not done so already, complete any necessary basic configuration for the Meridium Notification Service.
Within the <notification> tags, within the <notificationSettings>tags, uncomment the following text string (i.e., delete the <!-- and -->):
<!-- <add key="server3" serverType="external" endPointName="pdiService"/> -->
Within the <system.serviceModel> tags, within the <client> tags, uncomment the following text string (i.e., delete the <!-- and -->):
<!-- <endpoint name="pdiService" address="net.tcp://PDISERVERNAME/Meridium/PDI/NotifyHandler" binding="netTcpBinding" contract="Meridium.Core.Common.Contracts.INotificationService" /> -->
Within the address attribute, replace PDISERVERNAME with the name or IP Address of the Process Data Integration Server.
If you have only one Process Data Integration Server in your system architecture, save and close the file.
-or-
If you have multiple Process Data Integration Servers, complete the following steps for each additional server:
Within the key attribute, specify a unique name for the connection.
If your system architecture has two Process Data Integration Servers, the strings in the <notificationSettings> tags might look like this:
<add key="PDIserver1" serverType="external" endPointName="pdiService"/>
<add key="PDIserver2" serverType="external" endPointName="pdiService2"/>
...and the corresponding strings in the <client> tags might look like this:
<endpoint name="pdiService" address="net.tcp://Matrikon/Meridium/PDI/NotifyHandler" binding="netTcpBinding" contract="Meridium.Core.Common.Contracts.INotificationService" />
<endpoint name="pdiService2" address="net.tcp://OsiPi/Meridium/PDI/NotifyHandler" binding="netTcpBinding" contract="Meridium.Core.Common.Contracts.INotificationService" />
Copyright © 2018 General Electric Company. All rights reserved.