Sunday, March 13, 2016
The Endeca Assembler is an Oracle Commerce component that performs the following essential roles in any Oracle Commerce application:
- It acts as the runtime component of Experience Manager, a tool that enables the business user to configure the runtime appearance and behavior of the application.
- It accesses values from a variety of sources, including databases, Digital Asset Management systems, social media feeds, and the MDEX engine.
- It creates view-ready application component models known as cartridges. A cartridge is a series of key and value pairs known as a content item. The key and value pairs contain values accessed by the Assembler.
- Your application renders these values visually, in the UI controls or other components that compose the pages in your application.
The following diagram illustrates the role of the Assembler in an Oracle Endeca Commerce implementation:
As shown in the preceding diagram, the following things happen when customers request information through your application page:
1. Application invokes the assemble() method as follows:
ContentItem contentItem = new RedirectAwareContentInclude("/myUrl");
ContentItem responseContentItem = assembler.assemble(contentItem)
where /myUrl is the URL to a page that you are assembling in Experience Manager and responseContentItem is a tree of other content items.
2. The assemble() method sends responseContentItem to the Assembler.
3. The Assembler passes the individual content items in responseContentItem to cartridge handlers, each of which handles a different content type. Each content item specifies a request for information.
4. The cartridge handlers pass the requests on to the appropriate sources of information, such as an MDEX Engine, a relational database system, a content management system, and so on.
5. The cartridge handlers receive and process information from their respective sources.
6. Each cartridge handler returns to the Assembler a content item that contains the requested information.
7. The Assembler combines the content items that it receives from all of the cartridge handlers into a responseContentItem, which is structured as a tree that contains all of the information required by the front end application.
8. The Assembler returns responseContentItem to the front end application.
9. Rendering code in the application converts the information in responseContentItem into a form that can be displayed in the appropriate cartridges on your application page.
No comments
Post a Comment
Note: Only a member of this blog may post a comment.