This manual assumes you are using a CAS-based deployment template for your EAC applications, as mentioned above. If you are creating new EAC applications, it is highly recommended that you use this type of deployment template.

If you have EAC applications created in an earlier release, they may be using an older Forge-based deployment template such as the one described in the Oracle Commerce Deployment Template Module for Product Catalog Integration Usage Guide. This type of deployment template uses CAS for its record and schema storage, and Forge to generate configuration and transform records on import. (CAS-style deployment templates also use CAS for record storage, but store schema configuration in the Endeca Configuration Repository, and do not use Forge at all.) Forge-based applications are still supported, but require some differences in the configuration of Oracle Commerce Platform components, as they require record output in a somewhat different format from applications that use a CAS-based template.

If you do have existing EAC applications that use a Forge-based deployment template, you can recreate your EAC applications with a CAS-based deployment template. If you instead continue to use applications based on the older-style template, you will need to reconfigure several Oracle Commerce Platform components, as described in Appendix A: Support for Older Deployment Templates. In addition, you will need to follow the Oracle Commerce Guided Search migration procedure described in the Oracle Commerce Guided Search Tools and Frameworks Migration Guide.