What Option we have in MT to make MEC as Webserver

Legacy Contributor

We have a requirement to integrate an external application and M3 using SOAP webservice.

The Initiator of the request is the external portal, the request should be received by MEC and a Response should be generated and send out for that request. We have successfully implemented the solution in the on-prem version of M3, using the WebsericeSyncIn and WebserviceSyncOut option, need to know what option we have in the MT version.

Legacy Contributor

Depending on the complexity of the SOAP message you should be able to solve it with API Flows in ION.

We took a brief look into how various on prem MEC http/Webservice use cases can be implemented in cloud and came up with this:

Use Cases

Inbound
All 4 Use Cases below regarding REST and SOAP will be implemented via API Flows and Policies
- Complex REST (POST service) service
- Simple REST (GET service) service
- Complex SOAP (POST service) requirement (wsdl) - loop required
	- loop not yet supported
- Simple SOAP (POST service) requirement (wsdl) - no loops required

- One M3 API call
	- call M3 APIs via ION API
- http receive file
	- supported via IMS
- security
- availability (up time)

Outbound
Rest API is Preferred
- Call one REST API to send message
	- by using API connection point in a Data Flow
- Call one REST API to enrich the message
	- by using API connection point in a Data Flow
But, there's a way to support SOAP
- Call one SOAP API to send message
	- by using API connection point in a Data Flow?
- Call one SOAP API to enrich the message
	- by using API connection point in a Data Flow?