Hi @SuTe, IFS Applications’ extensive integration supports everything from third-party products to other IFS Products such as IFS Planning and Scheduling Optimization (PSO). You can read more about IFS Integration here

https://docs.ifs.com/techdocs/Foundation1/010_overview/240_integration/default.htm

If the 3rd party system MitreFinch has API’s for exporting their data, then it is just a matter of customizing/using IFS Connect to integrate MitreFinch to IFS

*Admin Edit: Updated wit.ifs link with link to docs.ifs.com

Hi, where do I obtain a logon to enable me to follow this link please?

Hi @SuTe - Apologies for our delay here. The wit.ifsworld link is actually from our internal documentation, so it isn’t accessible to non-employees. I have pulled the info below about IFS Connect. Please let me know if that helps. 

IFS Connect

IFS Connect is an integration broker, designed for XML and web services. It can be used to facilitate integration of business logic with external business processes, applications, and devices.

The openness and flexibility of IFS Connect is achieved through the concept of transport connectors. Transport Connectors provide the connectivity between external devices/applications and IFS Connect. They provide protocol and data format conversion between IFS Applications internal XML format and external formats. For example, the Mail connector translates to MIME format and SMTP protocol. The connectors are hosted by a framework that provides services such as SOAP enveloping and XML transformation.

IFS Connect includes a number of ready-to-use connectors as well as a development framework to build your own. IFS Connect is based on Internet communication standards and include connectors such as Mail (POP3/IMAP/SMTP), HTTP/HTTPS, FTP/FTPS/SFTP and JMS.

Using transformers, IFS Connect can transform both outbound and inbound messages between XML and some other file format, for example HTML or plain text.

IFS Connect enables everything to talk to everyone. The Business API (BizApi) doesn't need to be aware of which connector is receiving the message. It's just a matter of configuring the routing rules. It is also possible to define a PL/SQL method instead of BizAPI.

• Any transport connector can execute any Business API or PL/SQL method with an inbound xml message.
• Any Business API can use any transport connector for the transport of an outbound xml message.
• Every new Business API that is created can use any of the supported protocols.
• Every new transport connector that is added can be used by existing Business APIs.

*Admin Update (April 2020): Our wit links often reference the same content you should see in your in-product documentation. I’m going to try to update all the wit links with docs links.