Note | |
---|---|
Only required when you want to use the e-Commerce Blueprint |
This section describes how you have to adapt your IBM Rational Application Developer (RAD) environment in order to integrate with CoreMedia Digital Experience Platform 8.
In general, certain configuration files need to be adapted in the IBM WebSphere Commerce workspace. Depending on your degree of already applied customization, you might need to merge the provided configuration snippets with your custom code.
This chapter also contains small configurations in the CoreMedia system. These tasks are highlighted in the margin.
Note | |
---|---|
Deployment to IBM WebSphere Commerce servers, including Staging, Production and Development, is not part of this manual. Please refer to appropriate IBM documentation in the info center at http://pic.dhe.ibm.com/infocenter/wchelp/v7r0m0/index.jsp The configuration should be performed by an experienced RAD developer. |
Scope of delivery
In order to connect CoreMedia DXP 8 with your IBM WebSphere Commerce server you will get the following artifacts from CoreMedia:
The CoreMedia LiveContext 2.0 WebSphere Commerce Project Workspace archive (Workspace archive, for short). It contains the required resources to customize the IBM WebSphere Commerce Server and JAR files with extensions for CoreMedia DXP 8 to be added to the classpath of your IBM WebSphere Commerce workspace and deployment packages. These files include the configuration described in the following chapters.
The CoreMedia LiveContext 2.0 WebSphere Commerce Project Sample Data archive (Sample Data archive, for short). The archive contains sample data for the WCS system, which corresponds with the test data for the CoreMedia system in CoreMedia Blueprint.
You will find both files on the CoreMedia releases download page at http://releases.coremedia.com/dxp8
The customization involves the following aspects:
Section 3.4.1, “Preparing the RAD Workspace” describes how to apply the required customization to your IBM WebSphere Commerce workspace
Section 3.4.2, “Copy Libraries” describes how to copy required libraries into the WCS.
Section 3.4.3, “Configuring the Search” describes how you have to extend the IBM search profile and the Solr index. This enables the CoreMedia system to get additional information necessary for the integration.
Section 3.4.4, “Extending REST Resources to BOD Mapping” describes how you have to configure the mapping of REST resources to the Business Object Document nouns.
Section 3.4.5, “Configuring the Cookie Domain” describes how you enable session synchronization between the CoreMedia and IBM system for content-led scenario.
Section 3.4.6, “Multiple Logon for the Same User” describes how you configure the IBM WCS system to accept multiple logins with the same user.
Section 3.4.7, “Configuring REST Handlers” describes which REST handlers you have to add and configure.
Section 3.4.8, “Applying Changes to the Management Center” describes the deployment of the Management Center customization.
Section 3.4.9, “Deploying the CoreMedia Fragment Connector” describes the deployment of the fragment connector, which renders content from CoreMedia DXP 8 as fragments to IBM WebSphere Commerce pages.
Section 3.4.10, “Customizing IBM WebSphere Commerce JSPs” describes how to apply customizations to IBM WebSphere Commerce JSPs.
Section 3.4.11, “Deploying the CoreMedia Widgets” describes the deployment of the CoreMedia widgets, which can be used to add content or assets from CoreMedia DXP 8 to IBM WebSphere Commerce pages using the fragment connector.
Section 3.4.12, “Setting up SEO URLs for CoreMedia Pages” describes how to set up SEO URLs for CoreMedia Pages.
Section 3.4.13, “Event-based Commerce Cache Invalidation” describes how to enable event based commerce cache invalidation.
Section 3.4.14, “Deploying the CoreMedia Catalog Data” describes how to import the CoreMedia catalog content from the Sample archive into the WCS.
Note | |
---|---|
In the following sections |