Administer > Manage WebSphere Commerce features > Marketing
Configure WebSphere Commerce to communicate with KickApps for remote widgets
To use KickApps as a widget service provider for remote widgets, configure a transport method in the WebSphere Commerce Administration Console using the KickApps affiliate account information. WebSphere Commerce requires this account information to support KickApps integration in the Madisons starter store and Management Center.
Before you begin
Your site must have an affiliate account with KickApps. When the account is set up, KickApps provides the site with a user name and password that gives you access to the account information required for this procedure.For more information about KickApps integration and affiliate accounts, see KickApps integration for remote widgets.
You must complete this configuration procedure on each server that:
- Displays KickApps widgets for customers to share on the Madisons starter store. This requirement applies to remote widgets for e-Marketing Spots, wish lists, and gift registries. If you do not complete this configuration procedure, the Share links on the Madisons store pages are not visible.
- Requires a Management Center connection to the KickApps App Studio. The Management Center Marketing tool uses the KickApps App Studio widget editor on the Internet to create e-Marketing Spot remote widgets. As a result of this configuration procedure, when business users log on to Management Center, they are automatically signed on to the KickApps App Studio. Then, when business users click the Get Widget button in the e-Marketing Spot properties view, they connect directly to the KickApps App Studio. This is referred to as single sign-on.
Procedure
- Retrieve the affiliate account information from the KickApps Web site:
- Log on to the KickApps affiliate center at this link:
http://affiliate.kickapps.com/user/displayAffiliateLoginPage.kickAction
- Click Configure > Advanced.
- In the left pane, click Single Sign-On.
- From the right pane, copy the values for the following fields so that you can enter them into the Administration Console later in this procedure:
- Affiliate E-mail
- Username
- Site Name
- Affiliate Site (AS) ID
- Unique Site ID
- If the site has the CNAME field configured, copy the CNAME value as well. Your site might have a CNAME record set up to implement DNS masking for the KickApps widgets the site creates. DNS masking is an optional configuration that makes URLs to KickApps widgets look like they are located on the domain.
- Under Configure the Single Sign-on settings below, ensure that the following two options are selected:
- Activate SSO
- SSO Key to authenticate SOAP requests
- Save the settings.
- Open the Administration Console and select Site on the Administration Console Site/Store Selection page.
Alternatively, you can specify this configuration at the store level. The store-level configuration overrides the site-level configuration.
- Click Configuration > Transports. The Transport Configuration page displays.
- Click Add.
- From the list of transports, select KickApps; then click Add.
- Select KickApps again; then click Configure.
- Use the values you copied from the KickApps affiliate site, enter values for the following the Transport Configuration Parameters:
- Affiliate Site (AS) ID
- Affiliate E-mail
- Unique Site ID
- Site Name
- User Name
- Optional: You can enter the CNAME value if the site has set up DNS masking.
- For the Production Server Host Name parameter, enter the host name of the production server containing the e-Marketing Spot. The KickApps Web service uses the URL on the production server to make requests to get feed content for the widget during editing.
- Click OK to save the configuration.
Related concepts
Remote widgets for e-Marketing Spots
Related tasks
Create an e-Marketing Spot remote widget
Related reference
Remote widget setup and implementation checklists