Course : Hybris Training
Mode of Training : Online
Duration : 40 Hours
Timings : Flexible
Hybris Online Training Demo Registration Link :
Hybris Online Training Course Curriculum:
Introduction: - What is Hybris ?
Key Points for Business
eCommerce Domain Hybris Back-Office Hybris Competitors
S/W & H/W Prerequisites
Hybris Architecture: -
Hybris Building Blocks
Hybris Logical Architecture
Final Architecture Diagram
Hybris Products: -
Installing Hybris :-
Inside Hybris Software
Default Tables / Users
Customer Service Cockpit
Console (hMC) vs Cockpit (PCM)
Project & Local Properties Files
Extensions – Accelerators – Add-ons
Hybris Init & Update
Load Balancing Config
Multiple Hybris Instances
Products & CatLog’s :-
End – End Workout
Hybris Vs Java Vs DBMS
Generic Items & Item types
Data Models & Items.xml
Customer Segments - WCMS
Person & Cart Rules E-E Workout Cart & Order :-
Site & Store
Front Store & Base Store
Hybris Mobile Vs Desktop Site
PCM & WCMS Cockpit E-E Workout
cronJobs E-E Workout
Hybris Sales Overview
Understanding Hybris Integration
Demos and Trail Systems
Tenants & Clusters
Cleanup & Deployment
Memory & Threads
End – End Workout
Hybris Import and Export
Programming with Service Layer :-
Arch of Service Layer
Facades, DTO & DAO
Understanding of Ext
Configuration of Ext
New / Custom ext
Implementation of Ext
Type Based Access Rights
Web Services API
Spring IOC, MVC & AOP
Hybris Marketing Overview
Impex changes to custom extension
Pre-Define and Custom Page, Template
Pre-Define and Customize Component
Validation in Hybris
Transactions – CURD
SVN Evn for Hybris
Introduction to Datahub
Hybris Programming with API
Billing – Com.Integration – Demo
Hybris Future & Road Map
Themes & Coloring
Product Image Handling
Site URL Reg expressions
For more information write back to us at [email protected] or contact us at USA : +1-845-915-8712 (Toll Free) Or India : +91-9642373173
A trigger is a named PL/SQL unit that is stored in the database and executed ( fired ) in response to a specified event that occurs in the database.
Overview of Triggers.
A trigger is a named program unit that is stored in the database and fired (executed) in response to a specified event. The specified event is associated with either a table, a view, a schema, or the database, and it is one of the following:
A database manipulation (DML) statement ( DELETE , INSERT , or UPDATE )
A database definition (DDL) statement ( CREATE , ALTER , or DROP )
A database operation ( SERVERERROR , LOGON , LOGOFF , STARTUP , or SHUTDOWN )
The trigger is said to be defined on the table, view, schema, or database.
A DML trigger is fired by a DML statement, a DDL trigger is fired by a DDL statement, a DELETE trigger is fired by a DELETE statement, and so on.
An INSTEAD OF trigger is a DML trigger that is defined on a view (not a table). The database fires the INSTEAD OF trigger instead of executing the triggering DML statement. For more information, see Modifying Complex Views (INSTEAD OF Triggers).
A system trigger is defined on a schema or the database. A trigger defined on a schema fires for each event associated with the owner of the schema (the current user). A trigger defined on a database fires for each event associated with all users.
A simple trigger can fire at exactly one of the following timing points :
Before the triggering statement executes.
After the triggering statement executes.
Before each row that the triggering statement affects.
After each row that the triggering statement affects.
A compound trigger can fire at more than one timing point. Compound triggers make it easier to program an approach where you want the actions you implement for the various timing points to share common data. For more information, see Compound Triggers.