Pretesting

During pretesting you must completethe pre-installation checklist. The tasks on the pre-installationchecklist are:

• Providing contact information to IBM? such as namesaddresses and phone numbers for those who are involved in the testing
• Providing test ID and production ID information
• Providing the following HTTP(S) protocol information:
  • Server IP address
  • Port
  • Path and parameters
  • User ID
  • Password
  • Content-type header (optional)

Testing

Testing involves verifying the connectionsbetween your business and Sterling B2B CollaborationNetwork.To test the connections your system and the HTTP gateway serviceexchange a generic document. The following figure shows an overviewof the HTTP gateway service testing process:

1. IBM sends EDIor proprietary data to your system and the HTTP gateway service performsthe following tasks:

   Forwards the data to you through the Internetusing the appropriate HTTP information.

   Receives the HTTP responsefrom your system. The following table describes valid response codes:

   Response Code

   Description

   200 OK

   Sterling B2B CollaborationNetwork successfullyreceived the document.

   401 Access Denied

   Invalid login information provided. Try to log in again.

   403 Forbidden

   Permission rights have not been set up for access to this inboundHTTP gateway.

   405 Method Not Allowed

   Unsupported HTTP command issued for the inbound HTTP gateway.The Inbound HTTP Gateway supports only the POST method.

   500 Internal Server Error

   An internal error prevented the inbound HTTP gateway from receivinga document. Try to retrieve the document again.

2. Your system returns EDI or proprietary data to Sterling B2B CollaborationNetwork usingthe current connection. The HTTP gateway service sends the HTTP responseto your your system.

Testing completes when Sterling B2B CollaborationNetwork andyour business can send and receive a generic document and a validHTTP response code is returned.