SAP Customer Data Cloud

 

SAP Customer Data Cloud

Gigya’s customer IAM helps building digital relationships between companies and their customers. It allows to manage customer’s profile, opt-in, consent and preference. Consumer trust is the key to succeed for customer driven organizations.

SAP acquired Gigya back in 2017. After acquisition it is known as SAP Customer Data Cloud.

 

Its Features are:

1.     Registration as a Service: Registration-as-a-Service (RaaS) provides the capabilities for customer identity and access management.

2.     Profile Management: SAP Customer Data Cloud provides a centralized location to manage your user profiles and user consent.

3.     Consent Replication: Consent replication allows customers to review their signed consent statements on the SAP Commerce Cloud Platform.

4.     Data Privacy Management: Data Privacy Management for SAP Customer Data Cloud integration ensures that customer’s personal data is handled properly.

 

Registration as a Service:

Provides the Capability for customer identity and access management.

We can configure the login screen sets available in SAP CDC to be used in SAP Commerce to allow you to engage with customers.

Can also customize these screen sets as per the requirement.

Helps to gather crucial information about the storefront users and stores is securely and use it for phenomenal user experience.

Customer registers on Storefront, then the profile is created in SAP Customer Data Cloud (CDC) and then in SAP Commerce Cloud (hybris).

 

Profile Management:

Provides a centralized location to manage your user profiles and user consent.

User can update his/her profile from SAP Commerce Cloud Storefront or any CS agent can do it from Backoffice.

Updates are reflected in SAP Customer Data Cloud.

User consent are initially done in SAP Customer Data Cloud (CDC) and later can be handled by SAP Commerce Cloud storefront.

 

Consent Replication:

Allows Customer to review their signed consent statement on the SAP Commerce Cloud storefront.

Only Administrator account in SAP Customer Data Cloud (CDC) can create and manage consent statement.

Once Settings are done and applied to respective screens, upon agreement customers can easily review their consent on the Profile details page in SAP Commerce Cloud Storefront.

Changes are reflected in SAP Customer Data Cloud and then stored in SAP Commerce Cloud.

 

Data Privacy Management:

It ensures that customer’s personal data is handled properly.

It consists of

1.     Audit Reporting: gives the power to generate reports containing personal data of user.

2.     Personal Data Erasure: user can ask to delete their personal data. Moreover system can also erase data over a certain retention period.

GigyaUserCleanupHook ensures that whenever users are deleted in SAP Commerce Cloud using the cleanup job, their account is deleted from SAP Customer Data Cloud as well.

 

SEO Tips And Tricks

 SEO

Search engine optimization

Search engines can reward you with higher rankings but only if you provide valuable information. It creates more traffic, more user to a site. SEO is a great tool for targeting the desired audience.
Things matter even it is a size of needle. Here are some healthy tips and tricks by which you can boost your site's rankings!!

Checkout this link for the healthy tips and tricks

Tips and Tricks to boost your site's ranking

News Letter Subscription

News Letter Subscription in Hybris

This task is done by using Mailchimp as a campaign manager.

Requirements:

1.      Active account on mailchimp. If you do not have then create a free account.

2.      Running hybris suite of any latest version.

Acceptance criteria:

User subscribe to your list from storefront. Email should be stored in mailchimp audience.

All otb files, content catalog, and products catalog is used.

Step1:

Create a CMSParagraph component

To create use this impex

$contentCatalog=apparel-ukContentCatalog

$contentCV=catalogVersion(CatalogVersion.catalog(Catalog.id[default=$contentCatalog]),CatalogVersion.version[default=Staged])[default=$contentCatalog:Staged]

INSERT_UPDATE

ContentSlot;$contentCV[unique=true];uid[unique=true];active;cmsComponents(&componentRef)[mode=append]

;;FooterSlot;true;CookieNotificationComponent,AnonymousConsentManagementComponent

Step2:

Call this component in your footer.tag file

Location of this file is :

/<storefront>/web/webroot/WEB-INF/tags/responsive/common/footer/footer.tag

Use component id to call it.

<cms:component uid="MailchimpFooterComponent"></cms:component>

Step3:

Add data to this component by either using impex or through backoffice

Impex for data is

UPDATE CMSParagraphComponent;$contentCV[unique=true];uid[unique=true];content[lang = en]

;;MailchimpFooterComponent;"<div id=""mc_embed_signup"">

<form action=""hide for privacy reasons this you will get from mailchimp acocunt "" method=""post"" id=""mc-embedded-subscribe-form"" name=""mc-embedded-subscribe-form"" class=""validate"" novalidate>

    <div id=""mc_embed_signup_scroll"">

              <h2>Get on the list.</h2>

              <p>Apparently we had reached a great height in the atmosphere, for the sky was a dead black and there a stars.</p>

<div class=""mc-field-group"">

              <input type=""email"" value="""" name=""EMAIL"" class=""required email emailtype"" id=""mce-EMAIL"" placeholder=""Your email"">

</div>

              <div id=""mce-responses"" class=""clear"">

                             <div class=""response"" id=""mce-error-response"" style=""display:none""></div>

                             <div class=""response"" id=""mce-success-response"" style=""display:none""></div>

              </div>    <!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups-->

    <div style=""position: absolute; left: -5000px;"" aria-hidden=""true""><input type=""text"" name=""b_7d9a62fe5c9ca5b12961bd498_bdd7dcc143"" tabindex=""-1"" value=""""></div>

    <div class=""clear""><input type=""submit"" value=""Subscribe"" name=""subscribe"" id=""mc-embedded-subscribe"" class=""button_subscribe""></div>

    </div>

</form>

</div>"

 

You need to add some extra script lines for that you have to modify footer.tag file

<script type="text/javascript" src='//s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js'>

</script>

<cms:component uid="MailchimpFooterComponent">

             

              <script type='text/javascript'>

                             (function($) {

                                           window.fnames = new Array();

                                           window.ftypes = new Array();

                                           fnames[0] = 'EMAIL';

                             }(jQuery));

                             var $mcj = jQuery.noConflict(true);

              </script>

</cms:component>

 

To add data via backoffice

Steps:

1.      Login in to backoffice

2.      Go to Component under WCMS

3.      Select your Component

4.      Add data in Content field

5.      Click on save

 

Outcome:

 

 

I have used Internal Custom CSS for the styling. Let me know you need this file.

If you need more help in this regarding mailchimp let me know in comments.  

How to run two hybris instances in one machine

Run Multiple Hybris Instances in One Machine

Acceptance Criteria : Run two hybris instances in one machine at the same time.

Requirements: Any version of hybris setups which is initialized.

Steps to perform:

Step 1: Open local.properties file of config extention for first instance

Step 2: Add the following properties in it. 

• tomcat.http.port=7001
• tomcat.ssl.port=7002
• tomcat.ajp.port=7109
• tomcat.jmx.port=7003
• tomcat.jmx.server.port=7004
• solrserver.instances.default.hostname=localhost
• solrserver.instances.default.port=8983
• solrserver.instances.default.memory=512m

Step 3: Open local.properties of second instance and change the solr port. This port number should be different from the first instance.

Save both the files and do ant all.

Once Build is successful Start the server with command "hybrisserver.bat" for both the instances.

Once Servers are up for both the instances change endpoints of one instance for which we changed the solr port number.

Note: 8983 is the default port number for solr 

Step4: Run the below impex to change the endpoints of solr

# Updates the endpoints for the Solr server configurations

INSERT_UPDATE SolrEndpointUrl ; solrServerConfig(name)[unique=true] ; url[unique=true]            ; master

                              ; Default                             ; http://localhost:8984/solr  ; false 

                              ; Default                             ; https://localhost:8984/solr ; true  

                              ; Local Standalone                    ; http://localhost:8984/solr  ; false 

                              ; Local Standalone                    ; https://localhost:8984/solr ; true  

                              ; Local Cloud                         ; localhost:9983              ;       

                              

# Removes old http endpoints

REMOVE SolrEndpointUrl ; solrServerConfig(name)[unique=true] ; url[unique=true]          

                       ; Default                             ; http://localhost:8983/solr

                       ; Local Standalone                    ; http://localhost:8983/solr

Results:

Extensions

Extension Structure

Extension Modules

Extension Modules are structural elements of an extension. Each of them offers a certain set of functionality.

Extension Module	Functionality
Core	Declarations of types, items, classes
Web	Web application

Core Extension Module:

The core extension module of an extension covers several basic components.

Type System Definition: Defined in item.xml in xml format file name pattern is always defined as <$extension> -items.xml

Java Source Code Files: Java source files of an extension.

Extension Version: Resource directory contains a file called <$extension>.<build.number>

Localization Files: Contains the localization files for the extension’s type and type’s attribute.

Web Extension Module:

The web extension module is the part of an extension that is accessible via browser.

Extensions can be added through localextensions.xml file located in config directory.

Extensions can have a core module or web module or it can be both.

Extension is configured by extensioninfo.xml file. It defines list of extensions required for current extension. If required extension does not exist in installation then build will get fail.

We can change the webroot path of an Extension for this we need to modify local.properties file we need to add a line 

hac.webroot=/admin

storefoundation.webroot=/storefoundation

The default web application of SAP commerce that is launched is hac console. It is not recommended to set this as a default web application in live environment. To set HAC no longer be the default web application we need to modify local.properties file

Hac.webroot=/admin

Creating a New Extension

SAP commerce comes with an extension generator system called extgen. Using extgen we can create new extensions based on extension templates there are number of extension templates available.

To make any of your extension serves as template extension add following line to the extensioninfo.xml file

<meta key="extgen-template-extension" value="true"/>

An extension template is a predefined basic extension to be duplicated. The copy serves as a starting point for creating a new extension, typically used for a customer specific implementations.

1.       Open a command prompt.

2.       Navigate to the <HYBRIS_BIN_DIR> /platform directory.

3.       Run the <HYBRIS_BIN_DIR> /platform/setantenv.bat file. Don't close the command prompt as the settings are transient and are lost if the command prompt is closed.

4.       Run ant extgen in <HYBRIS_BIN_DIR>/platform directory. This internally runs ant in the extgen directory.

 Extgen prompts you to specify values for the technical aspects of an extension. Extgen comes with default values for all these technical aspects. These default values are defined in the project.properties file in the extgen directory. The default value is displayed in brackets ([ and ]), such as:

Press [Enter] to use the default value [training]

Extgen prompts you to specify:

·       The extension's name.

·       The extension's Java package.

·       The extension template to use.

After these steps give custom extension reference in localextensions.xml file

<extension name=”customExtension”>

Rebuild the SAP commerce

1.       Open a command prompt.

2.       Navigate to the <HYBRIS_BIN_DIR>/platform directory.

3.       Make sure that a compliant version is used:

o   On the Windows operating system, call the <HYBRIS_BIN_DIR>/platform/setantenv.bat file. Do not close the command prompt after this call as the settings are transient and would get lost if the command prompt is closed.

o   On the Unix operating system, call the <HYBRIS_BIN_DIR>/platform/setantenv.sh file, such as: . ./setantenv.sh.

4.       Call ant clean all to build the entire SAP Commerce.

There are 21 Templates Available to select from while creating extension