I am working on a use case scenario for Adobe Launch. While integrating Adobe Launch with AEM using Adobe IMS configuration through Adobe I/O I realised that Adobe Launch can also be integrated with AEM by making configurations in AEM, and Adobe I/O will not be required.
I would like to know why Adobe is suggesting to use Adobe I/O to connect Launch console with AEM, while the same can be achieved without using Adobe I/O.
Is it having some advantages which can't be achieved using normal integration.
Please let me know the advantages of using I/O method over config method and vice versa.
What I meant by that is its easier to manage the integrations and know what integrations are present when you set that up in the Adobe I/O because what that's going to do is flag it as an integration with the Admin Console under "Integrations" Adobe I/O creates a technical user account for the integration when you set up an integration. That's what I said its easier to set it up that way through Adobe I/O.
Good morning! Mostly what that one comes down to is its easier to manage the connection in Adobe I/O. Yes in theory you could do that without it but simply we found that it works better when you do that with Adobe I/O its just easier to work with.