Sitecore Commerce 8.2.1 DevOps and Solution Overview.

Sitecore has recently launched a new version Sitecore Commerce 8.2.1, I have done the Sitecore Commerce 8.2.1 setup and  here is the high-level solution view and DevOps details.
Important URLs

Intallation - Download Link
DevOps - Guidelines

Here is the solution high-level view - 

Solution components
The storefront is built using state-of-the-art technologies such as:

1. Castle Windsor – a best-of-breed, mature Inversion of Control container available for .NET. For more information, see the Castle website.
2. Bootstrap 3.2 – a free collection of tools for creating websites and web applications. It contains HTML and CSS-based design templates for typography, forms, buttons, navigation, and other interface components, as well as optional JavaScript extensions. In the Storefront, Bootstrap HTML and CSS design templates are the output of the Sitecore renderings. For more information, see the getBootstrap website.
3. Knockout – a JavaScript library that helps you create rich, responsive display and editor user interfaces with a clean underlying data model. For more information, see the knockoutjs.com website.
4. Sitecore and ASP.NET MVC.
5. HTML5 and Responsive Web Design (RWD)
6. Newtonsoft JSON
7. WebActivator
8. JQuery

Sitecore XP provides a next-generation Content Foundation that includes:

1. Pipelines - A flexible pipeline-oriented processing framework.
2. Rules - A flexible rules framework.
3. Events framework.
4. Logging framework.
5. Configuration - Done through Bootstrapping.

Business Tools - The web-based Sitecore tools that are used by merchandisers, marketers, procurement, and customer support personnel to manage commerce content. These tools include:

1. Customer and Order Manager (COM) - This tool is new in release 8.2.1, and is integrated with the Commerce Engine via its CommerceAuthoring API.
2. Pricing and Promotions Manager (PPM) - This tool is new in release 8.2.1, and integrated with the Commerce Engine via its CommerceAuthoring API.
3. Merchandising Manager (MM) - An existing tool for managing the catalog. It integrates with Commerce Server, where catalog management is currently hosted. MM will be rebuilt in a future release when Commerce Server is phased out, and will integrate with the Commerce Engine in the same way as the other tools.

 I will share more details about the custom module and workflow for the Cart, Order, and Pricing & Promotion. Feel free to ask if you have any question.

Schedule Publish/UnPublish Best practices

Publishing best practices

Schedule Publishing/UnPublishing

Architecture and customization

-Jitendara Soni

1       Introduction. 4

2       Schedule publishing and unpublishing – Best Practices. 5

2.1         Items should have workflow assigned, else it will be automatically published to CD(WEB) 5

2.2         User publishing version option, instead of using publishing option on the template. 5

2.2.1      Template level publishing will be applicable for all version. 5

2.2.2      If you create first item and publish for future then it’s fine but if you edit and publish for the future the current whole item will be removed from the CD(WEB) instance. 5

2.2.3      Before publishing new version – default it will take current time for publishing, verify and reschedule this before workflow goes in final stats. 5

3       Schedule publishing and unpublishing scenarios. 5

3.1         Scenario 1 –    Create an item without any worklow. 6

3.2         Scenario 1.1 – Create second version of that item without any workflow.. 6

3.3         Scenario 1.1 – never publish setup without any workflow. 6

3.4         Scenario 2.1 – Create item with workflow.. 6

3.5         Scenario 2.2 – Create new version of workflow items. 6

3.1         Scenario 2.3 – Schdule multiple item through publish menu-change options

1 Introduction

For scheduling and unpublished content based on the upcoming dates is a key area for the Architecture to take the right decision, even to agree for the initial discussion,

Here, it’s an attempt to cover – What is default is Sitecore and what all are the must required changes/customization.

Example – Scheduling.

2 Schedule publishing and unpublishing – Best Practices.

2.1  Items should have workflow assigned, else it will be automatically published to CD(WEB)

2.2  User publishing version option, instead of using publishing option on the template.

        2.2.1 Template level publishing will be applicable for all version.

        2.2.2 If you create first item and publish for future then it’s fine but if you edit and publish for the future the current whole item will be removed from the CD(WEB) instance

        2.2.3 Before publishing new version – default it will take current time for publishing, verify and reschedule this before workflow goes in final stats. 

3 Schedule publishing and unpublishing scenarios.

Scneaion after enabling the future publishing job, as example below

3.1 Scenario 1 – Create an item without any worklow.

Item will be published.

3.2 Scenario 1.1 – Create second version of that item without any workflow

Second item will automatically published.

3.3 Scenario 1.1 – never publish setup without any workflow.

Set never publish to this items – let see if this item automatically disappear or not

It would be quickly deleted.

3.4 Scenario 2.1 – Create item with workflow

It will be published after approval

3.5 Scenario 2.2 – Create new version of workflow items

After approval for next 5 minutes, previous content will be moved.

3.6 Scenario 2.3 – Schdule multiple item through publish menu-change options

Here multiple item can be defined, below are the details

Pipeline Execution:-

Note :-  For any execution and logic for the pipeline execution below information will be usefull.

We wanted to process some date modification on pipeline and used itemCompleted pipeline but that will only triggered once for all language versions, then have to move our code to itemProcessing pipelines.

Details:-

ItemProcessing - this will be executed for all language versions. Let's say if you have one content for five languages then it will be executed for five time, You code should handle to be executed for one or multiple time based on your field type Shared or not.

Pipeline processing End :- This will be executetd only one time, let's say if you have content published for five languages it will be executed once.

Piple line end: this will also be executed once as Pipeline process End

Sitecore:- How to exclude particualr .DLL from the TDS package.

From my previous blog
http://jitendrasoni.blogspot.co.uk/2015/01/sitecore-how-to-exclude-particualr-dll.html

Hi folks,

Today, We got different scenario where our client was expecting the TDS package but that should not have some common.dll.

Problem :- If we create the solution without that dll then it will not be build.

Solutions :-

TDS has a feature to exclude the respective dll's