Tuesday, 30 May 2017

Understanding the difference between Soap and Restful Web Services

A web service is the ability of a client application to invoke a service on a remote computer and get back data.  There are two types of web services:

  • Soap web service
  • Rest web service

Soap web service

A soap web service exposes a web service definition language (WSDL) document. Using a programming language like Java, you can create proxy objects that consume operations exposed by the web service’s SOAP stack. By creating a Java proxy object, your Java application can exchange the following messages with a soap web service:


  • Soap request: sent to the web service by a client application requesting an action.
  • Soap response: Sent to a client application by the web service after a SOAP request is processed.

A benefit of using web services is that you can create a client application in a development environment that supports SOAP. A client application is not bound to a specific development environment or programming language. For example, you can create a client application using Microsoft Visual Studio .NET and C# as the programming language. Likewise, you can create a client application using Java.

To read an article on AEM and SOAP - see http://scottsdigitalcommunity.blogspot.ca/2014/02/creating-adobe-cq-bundles-using-apache.html.

To read an article about creating an AEM HTL component that invokes a 3rd party SOAP web service and displays the result set, see http://scottsdigitalcommunity.blogspot.ca/2016/08/creating-aem-html-template-language.html.

Restful web services

A restful web service is the explicit use of HTTP methods. A restful web service is more lightweight as opposed to a soap web service. As a result, invoking a restful web service operation is normally faster than invoking a soap web service operation. You do not need to create Java proxy classes to invoke a restful web service. You can invoke a restful web service using almost any tool, leading to lower bandwidth and shorter learning curve. For example, you can invoke a restful web service using Java classes located in the org.apache.http package.

To read an article on AEM and Rest - see http://scottsdigitalcommunity.blogspot.ca/2013/11/creating-adobe-experience-manager.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel





Friday, 19 May 2017

Adding a Custom Carousel Component to the Experience Manager Toy Site

The ability to add custom components to an Adobe Experience Manager site is important as it offers you flexibility to address your business requirements. When developing custom components, you can use third-party libraries of which there are many. For example, you can use JQuery plug-ins to create custom components that can improve the look and feel of your site. For information about some existing JQuery plug-ins, see 50 Amazing jQuery Plugins That You Should Start Using Right Now.

As an example, this article is going to modify the Experience Manager Toy Site. This site contains a static image, as shown here.



To improve the look and feel of this site, the static image is replaced with a carousel component that displays different images located in the Experience Manager DAM. 


This article discusses how to create a custom carousel component then add it to the Experience Manager Toy Site. To read this article, click https://helpx.adobe.com/experience-manager/using/toystore_carousel.html.
.

NOTE: To build the Experience Manager Toy Site, see Creating your First Adobe Experience Manager 6.3 website.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel



Monday, 15 May 2017

Developing your first Experience Manager 6.3 Components

When working with Adobe Experience Manager projects, you often need to develop custom components. This article discusses how to on board new developers to Experience Manager and build custom components. This article starts by creating a properly structured Experience Manager project that follows best practices. That is, it discusses specific tooling for both Java developers and front-end developers, as well as how to edit the rendered markup with HTL and Sling models.

In addition, this article covers working with Experience Manager Core Components. For information, see Core Components.


To read this Experience Manager 6.3 developer article, click https://helpx.adobe.com/experience-manager/using/aem63_components.html.



Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel


Tuesday, 9 May 2017

Ask the AEM Community Experts for May 2017


Title: Using Lazybones and Editable template in AEM projects

Date: Tues May 30, 2017 11 AM EST

Description: Join Ankur Ahlawat and Scott Macdonald for a discussion about using Lazybones and Editable template in AEM Projects. By joining this session, you will gain a better understanding of how to build AEM projects that take advantage of Lazybones and the new Editable Templates in your projects.


To watch this session - click: https://communities.adobeconnect.com/pkou4185bxyh/?proto=true .

Promote this blog in your own AEM Community Channels - take advantage of this free AEM webinar!!


Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.


YouTube: Subscribe to the AEM Community Channel

Monday, 8 May 2017

Creating Editable Templates for an Experience Manager Website

When developing enterprise scale Adobe Experience Manager web sites, you can use editable templates. An editable template lets you specify the layout of a page, You can for example, determine the look and feel of the template, specify which components are allowed in the template, and so on. An editable template is built using the Experience Manager template editor.

This article adds editable templates to the Experience Manager Toy Site. This editable template uses a policy which determines what AEM components are allowed in it, as shown in the following illustration.


The following illustration shows the editable template in Initial Content mode.


Using an editable template, you can create pages for your site. The Experience Manager pages have the same look and feel, but have different content. To read this development article, check back later in June 2017. 

NOTE: This Experience Manager developer article builds off of the Sample Toy Site built for Experience Manager 6.3. For information about developing this site, see Creating your First Adobe Experience Manager 6.3 website.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel


Monday, 1 May 2017

Creating Multimedia Experiences using Assets and Dynamic Media

Building interactive and responsive multimedia experiences can be difficult given the vast number of platforms and screens. The Adobe Experience Manager Assets and Dynamic Media capabilities offer a framework and suite of components that allow creators and marketers to effortlessly customize and deliver interactive multimedia viewers across all devices. These easy-to-use tools give marketers the power to build rich and scalable multimedia experiences with little to no technical knowledge.


By reading this article, you will learn the following:


  • Use Dynamic Media to take a single set of assets and serve unlimited customized variations, including size, color, format, and zoom.
  • Author and deploy interactive experiences using out-of-the-box viewers and graphical authoring tools
  • Develop custom viewers using the HTML5 Dynamic Media SDK for complete control
To read this article, click https://helpx.adobe.com/experience-manager/using/aem_dynamic_media.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel