The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Integrating a WebSphere Commerce procurement system

Setting up multiple communication types for multiple procurement systems

Michael D.J. Shields (mshields@ca.ibm.com), Solution Architect, IBM

Michael Shields is a Solution Architect on the IBM Software Services for WebSphere team at IBM Toronto, Canada. He has over a decade of strong customer facing skills, including helping clients customize IBM software to exceed their business goals.

Michael has published over 12 tutorials on the WebSphere Commerce Information Center and over 8 tutorials on the developerWorks WebSphere Commerce zone. He holds over 12 technical certifications and a designation as a project manager (PMP). Michael also has a creative side that resulted in 5 patents, with more currently under review.

Summary: This tutorial describes how to integrate multiple procurement systems into a PunchOut session. You will learn what procurement systems to develop based on communication types. Finally, you will configure WebSphere® Commerce to work with two procurement communication types and a simple validation process using reusable test methods.

Date: 30 Jul 2008
Level: Intermediate
PDF: A4 and Letter (808 KB | 67 pages)Get Adobe® Reader®

Activity: 16127 views
Comments:

Before you start

This tutorial will look at the PunchOut aspect of procurement integrations. PunchOut is an easy to implement protocol for interactive sessions managed across the Internet. This is achieved through a dialog of real-time, synchronous cXML messages, which support user interaction at a remote site.

The following section from ghe WebSphere Commerce Information Center describes the available to market flow provided by the product: Purchasing flow using the punch-out catalog mode.

This tutorial shows how to integrate an Ariba® procurement system using cXML synchronous messages and using XML/HTTP configuration in WebSphere Commerce. It will then show how to integrate an SAP® procurement system via an OCI flow in WebSphere Commerce.

What is cXML?

cXML is different from most other electronic business protocols. cXML is a streamlined protocol intended for consistent communication of business documents between procurement applications, e-Commerce hubs, and suppliers.

For more information about cXML, see the cXML Web site.

What is OCI?

The Open Catalog Interface (OCI) incorporates external product catalogs into systems like SAP. This way, data that is required to create shopping cart items in the SAP system can be transferred directly from the external catalog to the SAP. The interface uses the transfer mechanisms of Hyper Text Transfer Protocol (HTTP).

What is in this tutorial?

The tutorial will cover the following sequence:

Types of communication protocols in procurement systems: Two types of communication protocols are reviewed in this tutorial. The tutorial provides a mechanism to ensure that you have a complete picture of PunchOut integrations using different communication types.
Saving and configuring the cXML DTD: For the first part of this tutorial, cXML is the main focus to establish a strong working integration. The configuration of the cXML DTD into the ariba_user_template.xml is important for understanding how XML/HTTP is translated into a working software system.
Instance and database configuration for the two-step communication protocol: You will be required to make some instance and database updates to configure WebSphere Commerce to work with PunchOut integrations. Only the two-step communication protocol will be handled at this level. One-step communication protocol will be handled later in this tutorial.
Setting up the frontend for cXML: There are some JSP files and Struts configurations required to enable JSP to output pages and cXML messages.
Test scenario options: The different ways to test a two-step communication protocol PunchOut integration will be reviewed and analyzed in this section.
Initial setup test Scenario for cXML: Strap yourself in for a ride because this is going to be a huge learning curve. You will construct a test URL based on the cXML DTD mapping and name-value pairs handled by the WebSphere Commerce code.
Test scenario for Ariba: You will go through a useful test scenario for a two-step communication protocol PunchOut integration.
Database configuration for the one-step communication protocol: After validating the successful PunchOut integration, now you will set up a configuration for the one-step communication protocol.
Setting up the front end for OCI: For this section, you will review the JSP code and then save into your workspace. Thus, allowing the PunchOut process to complete the frontend flow through the JSP output as well as redirecting to the AdvancedB2BDirect shopping pages.
Test scenario for OCI: By following what you have already done for the cXML testing section, the OCI flow has a similar process. You will use an HTML form to initiate the request to WebSphere Commerce to perform a PunchOut experience.