Web Service Integration

1         Overview  

Perfection Software, Inc (Perfection) has created an electronic web service giving Participants the ability to allow their Customers to electronically interact directly and securely with their Perfection Management System.  This add-on component allows Participants’ existing computer systems to connect via the Internet (or any other standard networking means) to their own Web Site Order Entry system of choice.  Participants have the flexibility to create their own Order Entry system!  Moreover, by automating business communications, Participants can achieve cost reductions, productivity enhancements and a competitive advantage.

1.1          Definitions

1.       Participant: Perfection Software, Inc customer running Perfection Management.

2.       Customer: Participant’s customer.

3.       Web Site Order Entry System: Order Entry system chosen by the Participant. Typically the Order Entry System will be a Web based system, but does not have to be.

4.       Web Service: The optional add-on component developed by Perfection Software, Inc. to provide real time integration between the Web Site Order Entry System and Perfection Management.

5.       xPath: XML Path Language

2          Requirements

2.1         Participant requirements

·         Perfection Management (PM) latest version with the latest enhancements related hereto running on a D3/Windows or D3/Linux Server.

·         Perfection Web Service add-on component running on a Windows system with the .NET Framework loaded. The main PM Server can be used if it is running the required version of Windows. Only Windows Server 2003 and Windows XP SP2 include the requisite functionality. Future operating systems should all provide this functionality to run the Perfection Web Service.

·         If the Perfection Web Service is not running on the PM Server then it should at least be on the local area network, and it should be setup as a server to ensure reliability.

·         At least one available Perfection and D3 Database user license must be available at all times. If a user license is not available then one will have to be purchased. Additional user licenses may be required if a high volume of transactions are going to be processed. If only one user license is used then only one transaction can be processed at a time (Example: If one transaction takes 3 seconds to get a response then a maximum of 20 transactions can be processed per minute – response times and transactions per minute are not guaranteed since they are dependent upon many uncontrollable factors).

·         Participant must currently be on a software support contract with Perfection Software, Inc.

·         Participant must have an “always on” Internet connection  to the Perfection Web Service

·         Static IP required to provide real-time transaction responses

·         Any hardware, software, setup, installation or infrastructure changes required to participate

2.2         Communication Requirements

Participants and the Web Site Order Entry system must have the ability to send and receive XML HTTP transactions through standard networking protocols.  Transactions may be secured and encrypted using HTTPS (SSL).

2.3         Outage Notifications

Participants will need to develop outage notification plans in case of extended downtime because of technical difficulties beyond their control.


3          Business Transactions (This is not a comprehensive list of the available transactions)

3.1          Order Request and Order Confirmation Response

A customer will initially create an order in the participants Web Site Order Entry system. The order will be transmitted to the participants system in a pre-determined XML format via the HTTP (HTTPS recommended) communication channel.

The order request will be processed immediately and an order confirmation will be sent back to the Order Entry system. The order may be accepted, partially accepted or rejected.

3.2          Order Status Update Request and Response

Request and return the status of an individual order.

3.3          Inventory Inquiry Request and Response

Request and return the inventory information and price of inventory by customer if the customer is given.

3.4          Customer Account Status Request and Response

Request and return customer account status detail with Accounts Receivable aging.

4          XML Messaging Guidelines

XML messages are loosely designed around cXML document standards found at www.cxml.org . The Order Request and Confirmation use cXML specific constructs but all other transactions are customized messages.

In addition, the document contains XML Messaging Guidelines in xPath style for the XML elements and attributes that will be utilized for each of the PWS transactions.  XML examples can be provided upon request. Please call (800) 766-7530.


Return To Products Page