AEM Screens Application | Community
Skip to main content
RichardMe4
Level 2
Jun 6, 2018 4:19 PM UTC
Solved

AEM Screens Application

Hello everyone, how can I develop an AEM Screens application that consumes web service or database?

We need to make an application that uses a webservice to send and receive a code

Thanks for the help

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
nchandra
nchandraAccepted solution
Level 2
Jun 8, 2018 2:51 PM UTC

Sorry , I didn't follow your question completely.  "With which tools are the screens applications created and how can I place the htl component? "

As I get it,  you can develop the HTL components based on your design and call the back end Webservices and display the content on the screen.

Thanks,

Chandra

View reply

4 replies

RichardMe4Author
Level 2
Jun 11, 2018 3:58 PM UTC

Chandra thank you very much for your support

Translate
nchandra
nchandraAccepted solution
Level 2
Jun 8, 2018 2:51 PM UTC

Sorry , I didn't follow your question completely.  "With which tools are the screens applications created and how can I place the htl component? "

As I get it,  you can develop the HTL components based on your design and call the back end Webservices and display the content on the screen.

Thanks,

Chandra

Translate
RichardMe4Author
Level 2
Jun 6, 2018 5:25 PM UTC

Thanks Chandra,

Similiar to these steps

https://helpx.adobe.com/experience-manager/using/htl63_soap_aem.html?

With which tools are the screens applications created and how can I place the htl component?

Thank you very much

Translate
nchandra
nchandra
Level 2
Jun 6, 2018 4:27 PM UTC

They are many ways to consume the web services

  1.  You can consume the Web services from UI in JQuery or Javascript by using Ajax.

  2.  Write the HTL component, from the WCMUse class you can invoke the OSGI service.

If you are caching the pages then option 1 if it is dynamic content else any option is good.

Thanks,

Chandra

Translate
    Terms & ConditionsAccessibility statement

    Loading footer...