<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_Discovering_the_WalkMe_Solution_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2025-05-02T11:26:04.000Z

Deploying Solution: A High-Level View of Data Architecture

<div id="content"><p tabindex="0">Uncover the inner workings of WalkMe’s data architecture and gain the expertise to optimize deployment and enhance user experience.</p><p tabindex="0">This course takes a deep dive into the data flow from the WalkMe Editor to end users, detailing the roles of AWS for secure storage and Akamai CDN for fast, reliable content delivery. Learn how WalkMe ensures top-tier performance and security, and discover how to leverage these insights for seamless deployment solutions.</p><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_rvwbghwl"></div></div></div>

A High-Level View of Data Architecture

Discovering WalkMe

Deploying WalkMe - A High Level View of Data Architecture

Welcome to today's session on deploying the WalkMe Digital Adoption Platform. This module of Deploying WalkMe focuses on helping you understand how WalkMe's components are deployed to end users, content creators, and WalkMe administrators. Throughout this learning journey, you will understand various deployment types for the main WalkMe components, and explore the flow of data architecture in a high-level overview. WalkMe is a digital adoption platform, but what does this mean? A digital adoption platform, often referred to as DAP or simply DAP, drives technology's ability to seamlessly engage with end users to execute a business process that impacts revenue, risk, and or cost. The WalkMe Digital Adoption Platform is comprised of three main components. First is data and visibility. WalkMe Analytics helps customers make data-driven decisions by providing a clear view of user adoption. It simplifies complex data into insights, showing user engagement and behavior. This analysis allows organizations to track adoption, spot trends, and improve strategic planning in order to enhance usability, optimize user experience, and achieve business goals effectively. Then there is content creation, delivered in the WalkMe Console and the WalkMe Editor. The state-of-the-art editor for creating and publishing content on top of other applications is a desktop client used by content creators and admins only. The editors and admins can install the WalkMe editor and the editor browser extension to create, test and deploy WalkMe content. finally there is the UX layer an overlay that sits on top of underlying applications giving organizations the ability to seamlessly engage with end users to execute a business process even if the process spans multiple applications walkme's digital adoption platform provides the capabilities across browser desktop and mobile however this learning journey will be focused on walkme for web within the browser. Let's talk about the UX layer in WalkMe for web in a bit more detail. How can customers make WalkMe accessible to their users? Setting up walkme is simple and done once after setup WalkMe admins can create and manage content for users on their own. It all begins with the WalkMe snippet visible here on the screen. If the customer has access to the app's code, just add the WalkMe snippet to the HTML in the master header. Once added, users will see WalkMe content over the application without needing to download anything. Some applications already have the WalkMe snippet available. Check with your WalkMe account team for the latest information on this. If you can't add the snippet to the app's code, WalkMe provides a browser extension for users. This injects the snippet when they visit the relevant page, allowing users to see WalkMe content. The extension can be enabled via mass deployment by IT teams. The extension has a list of URLs to show WalkMe on. When users visit a page, it checks if the URL matches the list. If it does, WalkMe content shows. For data privacy, the list is checked locally. This means the current URL isn't sent back to the server. The browser extension lets WalkMe work, even where the snippet can't be installed manually. This makes it simple to support workflows across different applications. Plus, it's easy to expand Walkme's use to other apps since it's already set up and ready. Now let's dive into a high-level view of the architecture behind WalkMe, following the data from the editor to the end user. Your users browse to the application as they normally would, they don't need to log into anything else, and they can use any browser. The underlying application and user interaction are separate from the WalkMe system, ensuring segregation from the application's functionality. WalkMe loads resources to the browser asynchronously. This ensures WalkMe doesn't affect user experience or site performance. Let's explore this process further. Let's start by looking at creating content. Your WalkMe content creator uses the editor to either build WalkMe content or edit pre-built content from solution accelerators. You can have multiple admins with varied roles. Once the content is built and tested, it's time for deployment. Let's explore this now. We store deployed content as static JavaScript files in the cloud using AWS servers. WalkMe content is stored securely in an Amazon S3 bucket. Each customer's content is logically separated, meaning it's like each client having their own locked room in a shared, secure facility. This ensures privacy and security. For those needing extra assurance, there's an option to upgrade to a dedicated S3 bucket, offering complete isolation and added control. WalkMe provides flexibility and security tailored to your needs. The content is then cached by Akamai CDN for fast and reliable delivery to end users. The snippet will instruct the end-user browser to download the WalkMe JavaScript files from the CDN and stores them in the browser cache. The files hold the data needed to use WalkMe content and is typically one or two megabytes in size. Users can view all the content created for them without downloading or any other actions. To enhance performance, there is no need to constantly communicate with the server. The WalkMe content data will only be downloaded again if changes were made to any content. And remember, WalkMe content is displayed only after the web page has completely loaded, so there's no lag or negative effect to the performance of the underlying application. Finally, analytics data is sent back to our GCP servers for access and monitoring on WalkMe Insights. Thank you for completing this learning path on Deploying WalkMe. You've gained a solid understanding of WalkMe's core technology, deployment, and data flow. With this knowledge, you can confidently engage clients, plan tailored solutions, and present WalkMe as the ultimate tool for digital adoption. You're equipped to make a real difference. Go make it happen. Good luck and happy selling.