...
This guide assumes basic familiarity with USPS. It also assumes the reader is familiar with SOAP, XML and other related technologies.
| Info |
|---|
This documentation applies to both the Classic and Redesign versions of USPS. Except as noted in the document the Redesign and Classic API's of the SOAP services are compatible. |
Glossary
ITC, Information Technology Centers are regional data processing centers that provide computer services to member school districts. Among the services ITCs provide is hosting of the USPS application for school districts.
...
This document is updated routinely to reflect the current version of the USPS SOAP service.
Links to the latest version of this document can be obtained from the SSDT Public Wiki site at: https://wikimcoecn.ssdt-ohio.orgatlassian.net/wiki/x/EBMO_AYm
Resources
This document does not represent the complete documentation for the USPS SOAP service. The actual API documentation is contained in the WSDL, the USPS XML Schema and the OECN RPC XML schema. These documents are available from the the actual installation of the USPS SOAP service. Developers can find the current development version of the documents at: http://devel.ssdt.nwoca.org/uspssoap/
...
To view a list of changes made to the USPS XML Schema for version 1.6 onward of the USPS SOAP service, view the Updates to USPS XML Schema page.
usps-42.xsd
UspsWebService.wsdl
Status of the USPS SOAP Service
...
District Database Identification
Each database is identified by a “district code” For Classic USPS a single SOAP service endpoint is used to access all district databases at an ITC. Each unique database is identified by a "district code" or IRN. Some ITCs ITC's also support the use of NCES codes to identify district databases. After a SOAP client authenticates with the SOAP service, it must declare the district database on which it intends to operate. Alternatively, the SOAP client may query the service for the databases the user has access to and allow the user to select the district code.
For Redesign USAS, a separate endpoint is used for each district. In Redesign implementations of the SOAP service, the setDistrictAccess operation is a NOOP and is not necessary.
SOAP Service Endpoints
Each ITC that supports the USPS Classic USAS SOAP service will provide one or more “SOAP endpoint” URLs URL's for accessing the service for their districts. In most cases, a single endpoint will be used for all districts hosted by a given ITC Site. However, in some cases, an ITC may provide a different endpoint for specific districts.
Most ITCs For Redesign USAS SOAP, a separate endpoint will be provided for each school district.
ITC's will provide an HTTPS (SSL) end-point can be used to encrypt SOAP messages on the wire. Developers are encouraged required to use HTTPS when available. Each ITC decides whether HTTPS is available or required and may have other local security policies regarding from what networks SOAP connections are availablefor production instances.
Authentication and Authorization
...
- Invoke _login _operation with credentials for an account on the USPS server
- Optional: Invoke _getDistrictList _to return a list of districts the user can access
- Optional for Redesign: Invoke _setDistrictAccess _to bind the session to a given district database
...
It is important that the client invoke setDistrictAccess code to establish the district database to which the session is bound. This must be done exactly once after login and prior to any other USPS operation.{{
...
|
|---|
A client must not invoke _setDistrictAccess _more than once for a session. A fault will be returned if such an attempt is made and the session will be left in an indeterminate state. Client applications that need to access more than one district, must establish at least one session for each district. |
...
Session Timeout
Sessions consume resources on both the SOAP server and the back-end USPS server. Therefore, inactivity timeouts apply to the SOAP sessions. The timeout interval is configurable by each ITC and defaults to approximately 45 minutes. If there is no activity for a session during the timeout interval, the session will be deleted from the SOAP service. Any subsequent invocations using an expired sessionId will result in a fault being returned. Client applications that attempt to maintain long running connections, must be prepared to handle such faults.
...
| HTML Table |
|---|
|
| Table Row (tr) |
|---|
| Table Head (th) |
|---|
| Looks like |
|
| Table Row (tr) |
|---|
| Table Cell (td) |
|---|
| UWC_TOKEN_START~1292862896731~UWC_TOKEN_END |
|
| Table Row (tr) |
|---|
| Table Cell (td) |
|---|
| Or with line numbering:
UWC_TOKEN_START~1292862896732~UWC_TOKEN_END |
|
| Table Cell (td) |
|---|
| /resource/W2?employee.id=EMP0001&tax.year=2008 |
| Table Cell (td) |
|---|
| Content-type: application/pdf |
| Table Cell (td) |
|---|
| /resource/W2?employee.id=EMP0001&tax.year=4008 |
| Table Cell (td) |
|---|
| HTTP 404 Response (not found) |
| Table Cell (td) |
|---|
| | /resource/W2?employee.id=EMP0001&tax.year=* |
| Table Cell (td) |
|---|
Returns all URL's found for the specified employee
|
| Table Cell (td) |
|---|
| | /resource/W2?employee.id=*&tax.year=2008 |
| Table Cell (td) |
|---|
Returns all URL's for all documents for the specified year
|
|
| HTML Table |
|---|
|
| Table Row (tr) |
|---|
| Table Cell (td) |
|---|
| WS-I is a trademark of the Web Services-Interoperability Organization in the United States and other countries. |
|
|
...