Validate AIF ports if they are running in AX

It may happen that AIF ports are failing due to an error, or they do not activate when the AX AOS instance gets started. There is a way to validate AIF ports if they are running correctly using a combination of X++ code and a PowerShell script that you may find below.

Add the following to the Global class collection and do a Full CIL:

And here is the PowerShell script to validate AIF ports. Please make sure you provide a comma-separated list for the AOS names, and a correct path where the Business Connector DLL could be found. Also you might want to provide credential details for the AX login if the user running the script does not have access.

validate AIF ports

 

DAXRunBase / 2016-08-17 / AX 2012 / 2 Comments

AIF port changes without deactivating

For troubleshooting the Application Integration Framework in AX sometimes we have to enable logging of all XML document messages. However the AIF inbound ports cannot be edited by default without deactivating them first. It is a common misbelief that you need to do this.

If you deactivate and reactivate a port, in the background it just regenerates the server-side WCF settings in table AIFWCFConfiguration, that stores the XML string in a container field. Most of the values in there does not actually relate to a lot of fields that you should be able to change. In our case the LoggingMode field was in the scSC parent table of AIFPort.

What we could do instead of deactivating and reactivating our service in question to switch the logging on and off was to simply edit the record in the table browser, which does in fact take immediate effect and the logging will commence or get suspended once you save the row. Please keep in mind that for other fields such as user restrictions or service operations you should do your own research in a Test environment first to decide if it is safe to go ahead with the modification.

DAXRunBase / 2015-10-15 / AX 2012 / 0 Comments