Sitecore xConnect -Introduction

Sitecore xConnect -Introduction xConnect



    1. Introduction

    2. Problem with the existing System(sitecore 8.x)

    3. Need for xConnect




Architecture



    • Overview

    • Process and dataflow




Introduction to xConnect:
           xConnect is the brand new api or we can say as seperate component through which the communication happens to the xDB.To visualize it


         xConnect is the service layer that sits in between the xDB and any trusted client, device, or interface that wants to read, write, or search xDB data. Communication must happen over HTTPS and clients must have the appropriate certificate thumbprint.

 

Client device can be anything like wordpress,umbarco not only cms even asp.net application can use xConnect to read,write or search xDB.But for our learning we can take sitecore as our client device

xconnect client devices

 

Now we have client device as sitecore and xConnect as our communicator to xDB and xDB as Repository to store user personalized information in order to provide better insight.How to we track the user personalized data? Tracking api

 

The tracker is responsible for tracking a contact’s activity on your website and submitting that data to xConnect at the end of the session. xConnect and the tracker are separate components that work together. The tracker records a contact’s activities in session, converts that data on session end, and submits it to xConnect using the xConnect Client API.

 

Now we can visualize at high level how the communication happens from client device to xConnect

In partical Terms,xConnect exposes a web API end point through which the communication happens to xConnect.



  https://xchangesitecore.com/sitecore-xconnect-part-3/ Vikash Raaj

Comments

Post a Comment

Popular posts from this blog

Handling Disaster Recovery Plan

Image
Handling Disaster Recovery Plan We all are interested in knowing how to make the disaster or backup production environment which can help to reduce the downtime in real world. We need to setup the servers in different regions. mirror the database to each region from live environment load balancer should be configured to route the request to other environment if the server reachable or alive test page doesn't respond or its 404 bad response. Intimate the network and IT team about failures. Once the original environment is up, request can be sent to the original servers and the mirroring regions can be kept alive and as cold stand by. https://xchangesitecore.com/handling-disaster-recovery-plan/ Vikash Raaj
Read more

Sitecore Media Library

Image
Sitecore Media Library Controlling File Upload and Deny Execute Permissions on the Upload Folder You can strengthen the sitecore installation by restricting the access to the files that are begin uploaded by users. If you allow users to modify the content of /upload in website root folder then you also give them permission to place the scripts and executable programs. Executing these scripts and programs can cause an unexpected behavior on the server. You must therefore prevent an uploaded file from being executed on the server side when a user attempts to download it. We recommend that you deny permissions to run scripts and executable files in the /upload folder Note: You only need to perform this step if your configuration allows content authors to place files directly to the /upload folder. For example, if you use a shared directory or FTP server, content authors can quickly place a lot of media in the media library. Denying Execute Permission in IIS yo...
Read more

Sitecore Aliases for Multi Site

Image
Sitecore Aliases for Multi Site Are you having multi site environment and want to make use of Aliases in different for each site and\or share the Aliases for couple of sites? Yes we can do with the help of the custom plugin that was built to extend the feature of the Aliases Aliases for Multi-Site Environment https://xchangesitecore.com/sitecore-aliases-for-multi-site/ Vikash Raaj
Read more