Summary of Changes to DistributionManager.Service.exe.config and DistributionManager.Server.exe.config
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" />
Updates and Upgrades
Datamine does not recommend trying to update these configuration files. The following information is for reference purposes.
- The following appSettings key has been added.Copy
<add key="DynamicMsmqBindingName" value="SecuredMSMQ"/>
- The following msmq binding has been updated.Copy
<binding name="msmq" maxReceivedMessageSize="8388608">
<readerQuotas maxStringContentLength="8388608" />
<security mode="Transport" />
</binding> - The following SecuredMSMQ binding has been added.Copy
<binding name="SecuredMSMQ" durable="true" exactlyOnce="true" useActiveDirectory="true" maxReceivedMessageSize="8388608" closeTimeout="00:10:00" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00">
<readerQuotas maxStringContentLength="8388608" />
<security mode="Transport">
<message algorithmSuite="TripleDesSha256Rsa15" />
<transport msmqAuthenticationMode="WindowsDomain" msmqEncryptionAlgorithm="Aes" msmqSecureHashAlgorithm="Sha512" msmqProtectionLevel="EncryptAndSign" />
</security>
</binding> - The following section of code must be included in the behaviors section if using Production Accounting.
Copy
<endpointBehaviors>
<behavior name="LargeDataTransferBehavior">
<dataContractSerializer maxItemsInObjectGraph="2147483647" />
</behavior>
</endpointBehaviors>