Initialization VS Update in SAP Commerce [Hybris]

By Ramesh V

In this article, I will explain the detailed differences between System Initialization and Update process.

SAP Commerce includes a built-in initialization process that first removes all existing database content, performs several required steps in the background, and then leaves the system in a predefined state. In addition, an Update only applies the requested changes and deploys the most recent changes to the database.

In the following discussion, I will explain the detailed differences between System Initialization and System Update.


Initialization:

When you perform system initialization, the following actions are carried out:

  • It removes all the existing data in the DB.
  • It drops all the existing schemas and tables [i.e. existing type definitions defined in items.xml file] from the DB.
  • It will recreate the schemas and tables in DB.
  • It reloads the data into the database.
  • All the data available in DB will be lost after initialization.

We can Initialize SAP Commerce either from command line using ant initialize command, or using SAP Commerce Administration console [HAC] as shown below:

    Initialize system using Command line:


    Initialize system from SAP Commerce Administration console [HAC]:



Update:

When you perform system update, the system does the following:

  • It reads all the type definitions defined in item.xml file. 
  • It will just modify the changes requested and will not clear any existing schemas or tables.

We can Update SAP Commerce either from command line using ant updatesystem command, or using SAP Commerce Administration console [HAC] as shown below:

    Update system using Command line:

    Update system from SAP Commerce Administration console [HAC]:


Note: In generally we do system Update frequently as it takes less time and faster than Initialization. And System initialization can be performed only once at the time of Hybris setup or in some specifical cases for example when database is corrupted.


Happy Learning🙂🙂🙂





Location:Hyderabad Hyderabad, Telangana, India
SAP CX Senior Consultant[Hybris]

Comments

Post a Comment

Popular posts from this blog

Type System in SAP Commerce [Hybris]

By Ramesh V
In this article, I have explained in details about what is a Type System in SAP Commerce [Hybris] and how the data can be organized in the Hybris system. Type System in SAP Commerce is a data modeling framework . It defines the structure and organization of data within the platform. In SAP Commerce data can be organized in the form of types , for example product information, customer information, address information, cart information and order information etc. A type is a template for objects and every object stored in a platform is a type instance. Types can be defined in an items.xml file using following aspects: the deployment : It defines the database table where objects stored. attributes : Manage and store data for the object. the java class of the object. In SAP Commerce, Type is a blueprint of an Item and Item is an instance of a Type . Types can inherit from other types, allowing for a hierarchical organization of data. Attributes define the properties of a type. They can ...
Read more

Differences between Extension and AddOn in SAP Hybris

By Ramesh V
In this article, I have explained differences between Extension and AddOn in details in SAP Commerce [Hybris] and also described when to use Extensions and when to use AddOn's. An Extension is a self-contained module that adds or modifies functionality in SAP Commerce.   An Extension generally represents a larger functionality and it contains business logic, type definitions, back-office configurations and other configuration files like xml, properties and etc, whereas AddOns are used to extend the functionality of SAP Commerce Accelerator[storefront] without modifying the core code base. AddOns are plugin kind of extension, you can easily remove your AddOns without refactoring the code of your Accelerator extension. Extension can work independently or extend the another extension whereas AddOn always depends on an existing extension (e.g. acceleratorstorefront). Extensions are used for business logic whereas AddOns are mostly used for Frontend/UI customization.     ...
Read more

items.xml in SAP Commerce [Hybris]

By Ramesh V
The items.xml file specifies types of an extension for defining the data model . By editing the items.xml file, you can define new types or extend existing types. In addition, you can define, override, and extend attributes of the types. Location of the items.xml file: The items.xml is located in the resources directory of an extension. The items.xml files are prefixed with the name of their respective extension in the form of extension name-items.xml. For example: For the core extension, the file will be core-items.xml . For the catalog extension, the file will be catalog-items.xml . Basic structure of the items.xml file: The items.xml defines the types for an extension in XML format and the basic structure is as follows: <items   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"               xsi:noNamespaceSchemaLocation="items.xsd">           ...
Read more