-
Module 1: E-COMMERCE TECHNICAL OVERVIEW
-
Module 2: DEVELOPMENT ENVIRONMENT
-
Module 3: BRANDING THE E-COMMERCE SITE
-
Module 4: ECOMMERCE WEB PARTS
-
Module 5: SEARCH CONFIGURATION AND CUSTOMIZATION
-
Module 6: COMMERCE RUNTIME SERVICES
-
Module 7: TESTING, DEPLOYMENT AND VERSIONING OF ECOMMERCE SITE
Lesson 1: Commerce Runtime Extensibility
Commerce Runtime Extensibility
Commerce Runtime Extensibility : Microsoft Dynamics AX offers many services in the commerce runtime that support the basic functionality of an online store. You can add your own services or extend the services that are included in Microsoft Dynamics AX.
Lesson Objectives
Microsoft Dynamics AX offers many services in the commerce runtime that support the basic functionality of an online store. You can add your own services or extend the services that are included in Microsoft Dynamics AX.
How to Integrate a Service into CRT
This topic describes how to create a new service and add it to the commerce runtime configuration.
To create a new service, you have to create 3 different objects, which are Request object, Response object and Service object. After creating the service, you have to modify the Commerce Runtime configuration file. The below steps highlight this process
Creating a Service
A service handles any number of service messages. A service message is the combination of a service request and response. To create a service, implement a request, a response, and a service.
Modifying the Commerce Runtime configuration file
Services are enumerated as types in the commerce runtime config file. The commerce runtime config file controls which types to load. Services are loaded in the order in which they are listed in the configuration file. All of the default services are loaded automatically, but if you add a new service above one of the default services, the new service will replace the default service.
Commerce Runtime Configuration (CommerceRuntime.config)
Services are enumerated as types in the commerce runtime configuration file. You can add types in the commerce runtime configuration file to control which services are loaded in the commerce runtime.
Services are loaded in the order in which they are listed in the configuration file. All of the default services are loaded automatically, but if you add a new service above one of the default services, the new service will replace the default service.
To replace a service in the CRT, remove the type that represents that service from the file and add the type that represents the service you want to use.
You can either use fully qualified assembly names to load assemblies from the Global Assembly Cache or you can use specific types from a directory source: