You can use personalization to control who has access to specific content. When customizing your pages, you work with personalization assets such as rules, targeters and segments. If you are working in a multisite environment, personalization assets can be used between multiple sites. For example, you could use a Rules tab to display and manage multiple Site Override Rules and Site Filters. Site filters can be applied to Content Groups and targeters, allowing site-filtered searches. Scenarios are aware on which site the scenario event has occurred.
For detailed information on personalization and using Oracle Commerce Personalization, refer to the Personalization Programming Guide.
There are two general options for customizing page content.
Simple Customization – This customization requires the configuration of an alternate URL in a component property. Depending upon requirements, this customization may be all that is required for most customization needs
Targeting Customization – Targeting customization is useful when one of a number of JSPs could be rendered in a particular situation. In this situation, the decision of which JSP to render depends on complex rules, rules that are expected to change often, or in instances where it is necessary to modify these rules without restarting the application.
Targeting Customizations require writing targeting XML rules that contain information such as request attributes, product and/or order information, the current customer and the current agent, or other information relevant to the functional area in question. Targeting rules normally target repository items; however, in this case targeting rules target Nucleus components that identify which JSPs to render
