WebSphere Commerce provides the capability to integrate with procurement systems. This capability enables WebSphere Commerce customers to participate as suppliers in the procurement system's marketplace, increase sales, and enhance their business-to-business presence on the Web. WebSphere Commerce provides an extensible and customizable functionality in such a way that one can extend either the messages or the business logic.
WebSphere Commerce supports two modes of integration to procurement systems:
- Local catalog mode
- In Local catalog mode, suppliers have their catalog replicated on the procurement system. The buyers can browse the catalog and construct a shopping cart without connecting to the supplier's WebSphere Commerce site.
- Punch-out catalog mode
- In Punch-out catalog mode, suppliers maintain a single catalog within WebSphere Commerce, and use it to enable Web presence and participation in the procurement system's network.
Types of communication in procurement systems
Customers can choose to operate in either local or punch-out catalog mode using the communication of choice with their procurement system. There are two different types of communication protocols used in procurement systems:
- Two-step mode
- This protocol is used by procurement systems that use XML/HTTP or some other XML messages. The XML messages are used for initial setup, authentication, and registration of requisitioning users that belong to the buyer organization. Once the initial tasks are completed, a browser window is launched where the buyer can complete their shopping cycle. An example of this protocol is Ariba's XML protocol.
- One-step mode
- This protocol is used by procurement systems that use browser URL requests
for initial setup and authentication, as well as for buyers to complete their
shopping cycle. An example of this protocol is mySAP.com's OCI
protocol.
Note: WebSphere Commerce provides the infrastructure (commands, database schema) to support both types of protocols.