Summary of Changes to the IMS Integration Hub Distribution Manager Service and Server Config Files

• Summary of Changes to the IMS Integration Hub Distribution Manager Service and Server Config Files
• • Optional Endpoints for Logging Subscriber Errors
  • Endpoints for Integration with Production Accounting
  • Error Logging
  • Updates and Upgrades

Hostnames and some ports in these configuration files can be updated using the Application Configuration Editor. For more information, see Configure the IMS Integration Hub Service.)

Optional Endpoints for Logging Subscriber Errors

A Windows Communication Framework (WCF) endpoint can receive error messages from a subscriber. This configuration is recommended for B2MML integration.

If an endpoint is specified, the matching endpoint and binding must be configured and enabled in DistributionManager.Service.exe.config and DistributionManager.Server.exe.config:

• In the client section, uncomment the following endpoint. A different name can be specified if required.
  Copy

  <endpoint name="IntegrationHub.WCF.Contracts.IMSSubscriberError" address="net.msmq://localhost/private/b2mmlerrors" binding="netMsmqBinding" bindingConfiguration="B2MML" contract="IntegrationHub.WCF.Contracts.IMSSubscriberError"/>

• In the bindings section, uncomment the following binding:
  Copy

  <binding name="B2MML" durable="true" exactlyOnce="true">
    <security mode="Transport"/>
  </binding>

Endpoints for Integration with Production Accounting

Production Accounting registers transactions with IMS Integration Hub for both inbound and outbound transactions using WCF.

If message queues are configured for Production Accounting, the matching endpoints and bindings must be configured and enabled in DistributionManager.Service.exe.config and DistributionManager.Server.exe.config:

• In the services section, uncomment the following endpoint for the IntegrationHub.WCF.Transactions.IMSTransactionPublishingService. A different address can be specified if required.
  Copy

  <endpoint binding="netMsmqBinding" contract="IntegrationHub.WCF.Contracts.IMSDataProductionService" address="net.msmq://localhost/private/datamine.ims.ihub_from_ihub" bindingConfiguration="SecuredMSMQ" />

• In the services section, uncomment the following endpoint for the IntegrationHub.WCF.Transactions.IMSTransactionSubscriptionManager. A different address can be specified if required.
  Copy

  <endpoint binding="netMsmqBinding" contract="IntegrationHub.WCF.Transactions.IMSTransactionRegistrationService" address="net.msmq://localhost/private/datamine.ims.ihub_registersubscribers" bindingConfiguration="SecuredMSMQ" behaviorConfiguration="LargeDataTransferBehavior" />

• In the client section, uncomment the following endpoint. A different address can be specified if required.
  Copy

  <endpoint binding="netMsmqBinding" contract="IntegrationHub.WCF.Contracts.IMSDataProductionService" address="net.msmq://localhost/private/datamine.ims.ihub_from_ihub" bindingConfiguration="SecuredMSMQ" name="IMSDataProductionServiceEndPoint" />

Error Logging

This error logging is for IMS Integration Hub application errors rather than the errors that can be viewed via the Error Log Viewer in the IMS Integration Hub Client.

A different network path and file name can be specified in the following code in the log4net section. The logging level may need to be changed to ERROR or DEBUG for less or more information about errors respectively.

<log4net>
  <appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender">
    <file type="log4net.Util.PatternString" value="DistributionManagerService.txt" />
    <immediateFlush value="true" />
    <appendToFile value="true" />
    <rollingStyle value="Size" />
    <maxSizeRollBackups value="9" />
    <maximumFileSize value="1MB" />
    <staticLogFileName value="true" />
    <layout type="log4net.Layout.PatternLayout">
    <param name="ConversionPattern" value="%date %-5level %message%newline" />
    </layout>
  </appender>
  <root>
    <level value="INFO" />
    <appender-ref ref="RollingLogFileAppender" />
  </root>
</log4net>

Updates and Upgrades

Datamine does not recommend trying to update these configuration files. The following information is for reference purposes.

• The following keys were added in IMS Integration Hub 2.11. The value of these settings must match the remoting settings used for MineMarket. These settings can be updated using the Application Configuration Editor.
  Copy

  <add key="UseRemoting" value="False" />
  <add key="gRPCTracers" value="-all" />

• The following binding was added in IMS Integration Hub 2.11.
  Copy

  <dependentAssembly>
    <assemblyIdentity name="Microsoft.Practices.ServiceLocation" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-1.3.0.0" newVersion="1.3.0.0" />
  </dependentAssembly>

• The version number in the following binding was changed in IMS Integration Hub 2.11.
  Copy

  <dependentAssembly>
    <assemblyIdentity name="System.Threading.Tasks.Extensions" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />
  </dependentAssembly>

• The following keys were added in IMS Integration Hub 2.12. The value of these settings must match the SSL settings used for MineMarket. These settings can be updated using the Application Configuration Editor.
  Copy

  <add key="UseSSL" value="True" />
  <add key="Keystore" value="./keystore" />
  <add key="SSLTargetNameOverride" value="" />