bbs

Document Sample
bbs Powered By Docstoc
					                                                                                   Vendor Interface Specification




Arkansas Title XIX File Delivery and Retrieval System



                                     Vendor Interface
                                        Specification

                                                            HP Enterprise Services
                                                500 President Clinton Ave, Suite 400
                                                              Little Rock, AR 72201
                                                                                USA




                                                                                                          7/15/10




      HP is a registered trademark and the HP logo is a trademark of Hewlett-Packard Corporation
                                                                                                                          Vendor Interface Specification




Contents
WebBBS documentation ............................................................................................................................ 1
Interface standards ..................................................................................................................................... 2
  Web interface ........................................................................................................................................... 2
  FTP interface ............................................................................................................................................ 2
  Client software ......................................................................................................................................... 3
Web service interface specifications ........................................................................................................ 4
  Connecting to the server ........................................................................................................................ 4
  HTTPS messages .................................................................................................................................... 4
  Ping request and response messages .................................................................................................. 4
  UpLoad request and response messages ............................................................................................ 5
  DownLoad request and response messages ....................................................................................... 7
  Directory request and response messages .......................................................................................... 9
  DeleteFile request and response messages ...................................................................................... 12
  SuggestedPassWord request and response messages ................................................................... 13
  PassWordChange request and response messages ......................................................................... 15
  Error response message ...................................................................................................................... 16
  Status codes and status descriptions................................................................................................. 17
FTPS (FTP over SSL) specification ......................................................................................................... 18
  Uploading files ....................................................................................................................................... 18
  Downloading files .................................................................................................................................. 18
  Directory listing ..................................................................................................................................... 18
  Change user password ......................................................................................................................... 18
SFTP (FTP over SSH) specification ......................................................................................................... 19
  Uploading files ....................................................................................................................................... 19
  Downloading files .................................................................................................................................. 19
  Directory listing ..................................................................................................................................... 19
  Change user password ......................................................................................................................... 19
Security standards and practices ........................................................................................................... 20
  Password creation requirements ......................................................................................................... 20
  New WebBBS client passwords ........................................................................................................... 20
  Password aging ..................................................................................................................................... 20
  Website password change procedures ............................................................................................... 20
  Web service password change procedures ....................................................................................... 21
  FTPS (FTP over SSL) password change procedures ........................................................................ 21
  SFTP (FTP over SSH) password change procedures ........................................................................ 21
Appendix A: Sample file upload program .............................................................................................. 22
Appendix B: Sample file DownLoad program ........................................................................................ 23
Appendix C: Sample directory listing program ..................................................................................... 24
Appendix D: Sample DeleteFile program ............................................................................................... 25
Appendix E: Supported FTP commands. ............................................................................................... 26
Appendix F: SOAP 1.1 envelopes ........................................................................................................... 28
Appendix G: SOAP1.2 Envelopes ........................................................................................................... 37
Appendix H: Base64 encoding character set ......................................................................................... 47




7/15/10                                                                                                                                                     iii
Modification log

Rev #   Date           Author        Section             Nature of Change
1.3     5 April 2010   Mike Morgan   All web service     Added new section for DeleteFile Soap
                                     section, 1.3, add   message, added XML nodes to all response
                                     appendix E          layouts for days since last password change,
                                                         and documentation for FTP over SSL
                                                         supported commands.
1.4     3 May 2010     Mike Morgan   1.3, 1.4,           Sect 1.3 split into two sections; 1.3(FTP over
                                     Appendix E and      SSL) and 1.4 (FTP over SSH); prev. 1.4
                                     F                   Security Standards and Practices sec. is now
                                                         sec. 1.5; added appendix E and F; added
                                                         documentation of Base64encoding to
                                                         uploading and downloading sections for NCPD
                                                         files.
1.5     25 May 2010    Mike Morgan   All                 Grammatical corrections for final review.




iv                                                                                          7/15/10
                                                                                 Vendor Interface Specification




WebBBS documentation
This document is intended for Software Vendors who wish to develop applications to interact with
Arkansas State Medicaid‟s file delivery and retrieval system (WebBBS). It is created and maintained by
HP Enterprise Services for the purpose of uploading and downloading HIPAA compliant transactions.




7/15/10
Interface standards

Web interface
WebBBS is designed to support batch file uploads and downloads. It supports two web interface
methods. The first method is to logon to the secure web site using a trading partner user ID and
password. The web site is integrated with file transfer wizards that allow users to upload and download
files. The second method is to use a commercially or locally developed client application that runs on the
end-user‟s PC or the server that connects to the secure trading partner web services. The client
application must send service requests using HTTPS protocol and including the trading partner user ID,
password, and a service request message when applicable. The service request data can include a listing
of files available for download, a specific file ID to download, or a file name and data to upload. The files
should be transferred in standard ASCII text format. All data is transferred using the Secure Socket Layer
(SSL), which encrypts the data over the network.


FTP interface
The FTP interface is designed to support batch file uploads and downloads. This interface supports SFTP
and FTPS file transfers. Users may either logon to the FTP server interactively or develop software that
will logon to the FTP server programmatically.




2                                                                                                     7/15/10
                                                                                 Vendor Interface Specification




Client software
The client software can be written in any language that supports HTTPS. The request transactions are
formatted in XML, but the data files transferred to and from the web services are in the HIPAA standard
formats. The XML data is used to support the security and general interaction with the web services.




7/15/10                                                                                                      3
Web service interface specifications

Connecting to the server
To connect to WebBBS web services use a network connection that provides access to the public
internet. In the application, use the URL https://secure.medicaid.state.ar.us:8443/webbbs.asmx to
establish a connection with the web service interface. It is recommended that this URL not be hard coded
as part of the application but be configurable instead. Sample C# source code is provided in Appendix A,
B, C and D that demonstrates how to establish a connection and send service requests. All transactions
require a connection that is made using SSL protocol. Please note that different programming languages,
such as Visual Basic, have different ways of connecting using SSL. To access the specific web
application‟s functionality, invoke the Web Method identified in Table 1.

Note: For a complete description with sample SOAP Envelope and transaction request messages with
      responses, see Appendix F & G.

Table 1. Web methods.
Web Method                                 Accepted Input Data Type           Message Format
WebBBSPing                                 String                             XML
WebBBSPing                                 XML                                XML
WebUploadFromClient                        String                             XML
WebUploadFromClient                        XML                                XML
WebDownloadFromClient                      String                             XML
WebDownloadFromClient                      XML                                XML
WebDeleteFileFromClient                    String                             XML
WebDeleteFileFromClient                    XML                                XML
WebDirectoryDownloadFromClient             String                             XML
WebDirectoryDownloadFromClient             XML                                XML
WebGetSuggestedPassWordFromClient          String                             XML
WebGetSuggestedPassWordFromClient          XML                                XML
WebPassWordChangeFromClient                String                             XML
WebPassWordChangeFromClient                XML                                XML


HTTPS messages
Once a connection is established, standard SOAP messaging protocol is used to interact with the web
application. The web methods accept simple XML formatted messages of two different data types: “XML”
and “String”. These simple XML formatted messages are described in detail in the following sections.


Ping request and response messages
The Ping message requires no formal layout to interact with the Ping service. Its intent is to focus on a
connection without being bound to message layout protocol. Any message that is sent as one of the
acceptable types results the success response message: <Success>You Have Successfully Interfaced
WebBBS</Success>




4                                                                                                    7/15/10
                                                                                     Vendor Interface Specification




UpLoad request and response messages
The file UpLoad message is an XML formatted message for uploading files from the client to the HP
Enterprise Services server. No more than one file can be uploaded at a time, and the total length of the
entire message may not exceed four (4) megabytes. If the message size exceeds the four (4) megabyte
maximum, the entire transaction will be rejected. UpLoad request/response message descriptions with
sample XML and XML schemas are shown in Tables 2 and 3. See Appendix A for a sample UpLoad
program.

Note: FileData for batch NCPDP contains low order ASCII characters in the file format that are not W3
      XML compliant. Thus, in order for this file data to be submitted via WebBBS web service, it must be
      base64 encoded. This can be done by marking the „base64encoded‟ attribute true in the FileData
      element of the request. All other methods of submission, such as FTPS, do not require the file data
      to be encoded. See Appendix H for base64 encoding specifications.

 Table 2. UpLoad XML request message description.
Element     Description                                                                                  Require
UserName The username is used to authenticate the user submitting the request.                           Y
            Sample Data: MC123456
            Format: Alphanumeric
PassWord The password is used in conjunction with the UserName to ensure the validity of                 Y
            the user making the request.
            Sample Data: pass1234
            Format: Alphanumeric
FileName    The name of the file being uploaded.                                                         Y
            Sample Data: myfile.dat
            Format: Alphanumeric
FileData    This is the actual character data that comprises the file being uploaded.                    Y
            Sample Data: These are the contents of my file.
            Format: Alphanumeric
            Element Attribute
            base64encoded: This attribute tells the system that the file data has been
            base64encoded and requires decoding. This is a required attribute for NCPDP
            batch submission and is to true. This attribute can be omitted or set to false for all
            other file data submissions.

Sample UpLoad XML request message (base64encoded attribute omitted)
<UpLoad>
 <UserName>MYTESTUSER</UserName>
 <PassWord>MyTestPassword</PassWord>
 <FileName>0.FIL</FileName>
 <FileData>this is not base64 encoded data</FileData>
</UpLoad>


Sample UpLoad XML request message (base64encoded=“false”)
<UpLoad>
 <UserName>MYTESTUSER</UserName>
 <PassWord>MyTestPassword</PassWord>
 <FileName>0.FIL</FileName>
 <FileData base64Encoded="false">this is not base64 data</FileData>
</UpLoad>




7/15/10                                                                                                          5
Sample UpLoad XML request message (base64encoded=“true”)
<UpLoad>
 <UserName>MYTESTUSER</UserName>
 <PassWord>MyTestPassword</PassWord>
 <FileName>0.FIL</FileName>
 <FileData base64Encoded="true">AjAwUk1DMDAwMDAxICAgICAgICAgICAgICAgIDAwMDA</FileData>
</UpLoad>


UpLoad request XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="UpLoad">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="UserName" type="xsd:string"/>
 <xsd:element name="PassWord" type="xsd:string"/>
 <xsd:element name="FileName" type="xsd:string"/>
 <xsd:element name="FileData" type="xsd:string">
 <xsd:attribute name="base64encoded" type="xs:Boolean" default="false"/>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>


Table 3. UpLoad XML response message description.
Element                Description
DateTime               The date and time the response was generated.
                       Sample: 10/10/2009 3:22:42 PM
DaysSincePassChange     The number of days that has elapsed since the user last changed their
                        password.
                        Sample: 23
                        Format: Numeric
StatusCode              A string that identifies the resulting status of the performed operation.
                        Sample: 0
                        Format: Numeric
StatusDescription       A string that describes the status code returned in the response.
                        Sample: UpLoad Success (respective to status code: 0)
                        Format: Alpha-numeric
FileID                  A string that identifies the ID of the file that was uploaded.
                        Sample: 123925469
                        Format: Numeric
FileName                A string that identifies the name of the file that was uploaded.
                        Sample: foo.txt
                        Format: Alpha-numeric-special

Sample UpLoad response XML message
<Response>
 <DateTime>10/10/2009 3:22:42 PM </DateTime>
 <DaysSincePassChange>23</DaysSincePassChange>
 <StatusCode>0</StatusCode>
 <StatusDescription>UpLoad Success</StatusDescription>
 <FileID>123925469</FileID>
 <FileName>foo.txt</FileName>
</Response>




6                                                                                                   7/15/10
                                                                                   Vendor Interface Specification



UpLoad response XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="Response">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="DateTime" type="xsd:string"/>
 <xsd:element name=”DaysSincePassChange” type=”xsd:string”/>
 <xsd:element name="StatusCode" type="xsd:string"/>
 <xsd:element name="StatusDescription" type="xsd:string"/>
 <xsd:element name="FileID" type="xsd:string"/>
 <xsd:element name="FileName" type="xsd:string"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>



DownLoad request and response messages
The DownLoad request is an XML formatted message sent over HTTPS to download a file. A file ID or file
name is required to download files and is available through the directory listing response. DownLoad
request/response message descriptions with sample XML and XML schemas are shown below. See
Appendix B for a sample DownLoad program.

Note: FileData for NCPDP response files contain low order ASCII characters in the file format that is not
      W3 XML compliant. In order for this file data to be downloaded via WebBBS web service, it must be
      base64 encoded. This will be done by marking the „base64encoded‟ attribute true for the FileData
      element of the response. Then the client application would need to decode the data. See Appendix
      H for base64 encoding specifications.

Table 4. DownLoad XML request message description.
Element                Description                                                            Require
UserName               The username is used to authenticate the user submitting               Y
                       the request.
                       Sample Data: MC123456
                       Format: Alphanumeric
PassWord               The password is used in conjunction with the UserName to               Y
                       ensure the validity of the user making the request.
                       Sample Data: pass1234
                       Format: Alphanumeric
FileID                     Specifies the ID of the file to download.                          N
                           Sample Data: 000000123                                             If a file name
                           Format: Alphanumeric                                               is specified

FileName                   A string that identifies the name of the file to download          N
                           Sample: foo.txt                                                    If a file ID is
                           Format: Alpha-numeric-special                                      specified


Sample DownLoad XML request message (with a FileID)
<DownLoad>
 <UserName>MyTestUser</UserName>
 <PassWord>MyTestPassword</PassWord>
 <FileID>502940839</FileID>
</DownLoad>




7/15/10                                                                                                         7
Sample DownLoad XML request message (with a FileName and FilePath)
<DownLoad>
 <UserName>MyTestUser</UserName>
 <PassWord>MyTestPassword</PassWord>
 <FileName>foo.txt</FileName>
</DownLoad>


DownLoad request XML schema
<?xml version="1.0" encoding="utf-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="Download"/>
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="UserName" type="xsd:string"/>
 <xsd:element name="PassWord" type="xsd:string"/>
 <xsd:element name="FileID" type="xsd:string" minOccurs="0"/>
 <xsd:element name="FileName" type="xsd:string" minOccurs="0"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>


Table 5. DownLoad XML response message description.
Element                Description
DateTime               The date and time the response was generated.
                       Sample: 10/10/2009 3:22:42 PM
DaysSincePassChange      The number of days that has elapsed since the user last changed their
                         password.
                         Sample: 23
                         Format: Numeric
StatusCode               A string that identifies the resulting status of the performed operation.
                         Sample: 0
                         Format: Numeric
StatusDescription        A string that describes the status code returned in the response.
                         Sample: UpLoad Success (respective to status code: 0)
                         Format: Alpha-numeric
FileID                   Specifies the ID of the file to download.
                         Sample Data: 000000123
                         Format: Alphanumeric
FileName                 A string that identifies the name of the file to download.
                         Sample: foo.txt
                         Format: Alpha-numeric
FileData                 The actual file data contained in the file (1 Byte - 2 Million Bytes, not 2MB).
                         Sample: “this is some file text in ASCII character text format”
                         Format: Alpha-numeric
                         Element Attribute
                         base64encoded: This attribute tells the client that the file data has been
                         base64encoded and requires decoding. This attribute will be set to true for
                         NCPDP response files, which will have a file extension of NCP. It will be false
                         for all other response files.




8                                                                                                    7/15/10
                                                                                       Vendor Interface Specification



Sample DownLoad XML response message (base64encoded=“false”)
<Response>
 <DateTime>10/10/2009 3:22:42 PM</DateTime>
 <DaysSincePassChange>23</DaysSincePassChange>
 <StatusCode>0</StatusCode>
 <StatusDescription>DownLoad Success</StatusDescription>
 <FileID>1234567</FileID>
 <FileName>foo.txt</FileName>
 <FileData base64encoded="false">Not NCP file data and will not be base64 encoded.</FileData>
</Response>


Sample DownLoad XML response message (base64encoded=“true”)
<Response>
 <DateTime>10/10/2009 3:22:42 PM</DateTime>
 <DaysSincePassChange>23</DaysSincePassChange>
 <StatusCode>0</StatusCode>
 <StatusDescription>DownLoad Success</StatusDescription>
 <FileID>1234567</FileID>
 <FileName>foo.txt</FileName>
 <FileData base64encoded="true">AjAwUk1DMDAwMDAxICAgICAgICAgICAgICAgIDAwMDA</FileData>
</Response>


DownLoad response XML schema
<?xml version="1.0" encoding="utf-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="Response"/>
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="DateTime" type="xsd:string"/>
 <xsd:element name=”DaysSincePassChange” type=”xsd:string”/>
 <xsd:element name="StatusCode" type="xsd:string"/>
 <xsd:element name="StatusDescription" type="xsd:string"/>
 <xsd:element name="FileID" type="xsd:string"/>
 <xsd:element name="FileName" type="xsd:string"/>
 <xsd:element name="FileData" type="xsd:string">
 <xsd:attribute name="base64encoded" type="xsd:Boolean" default="false"/>
 </xsd:element>
 </xsd:sequence>
 </xsd:sequence>
</xsd:schema>



Directory request and response messages
The Directory message is an XML formatted message that gathers information such as the file ID, file
name, and file path for files available for download. The file information can be applied to a DownLoad
message to retrieve file data. The FileTypes tag is optional; it allows filtering by file type, and multiple file
types may be specified by separating each by a semicolon. This tag also has an attribute, “onlynewfiles”,
which instructs the system to only return new files. Directory request/response message descriptions with
sample XML and XML schemas are followed. See Appendix C for a Directory sample program.

Table 6. Directory XML request message description.
Element       Description                                                                                  Require
UserName      The username is used to authenticate the user submitting the request.                        Y
              Sample Data: MC123456
              Format: Alphanumeric
PassWord      The password is used in conjunction with the UserName to ensure the validity of              Y
              the user making the request.
              Sample Data: pass1234
              Format: Alphanumeric



7/15/10                                                                                                            9
Element         Description                                                                              Require
FileTypes       This is a file mask allowing you to limit the files returned. For example, if you only   N
                want the 997 functional acknowledgments, you would use *.997 here. The default
                behavior is *.* for every file available.
                Sample: *.997
                Format: Alphanumeric
                Element Attribute
                onlynewfiles: If set to a value of “true”, the system will only retrieve new files. If
                omitted or set to a value of “false”, the system will retrieve both old and new files.

Sample directory XML request message (for only new 997s)
<Directory>
       <UserName>MyTestUser</UserName>
       <PassWord>MyTestPassword</PassWord>
       <FileTypes onlynewfiles="true">*.997</FileTypes>
</Directory>


Directory request XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" xml:lang="EN">
 <xsd:element name="Directory">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="UserName type="xsd:string"/>
 <xsd:element name="PassWord" type="xsd:string"/>
                <xsd:element name="FileTypes" type="xsd:string" minOccurs="0">
 <xsd:attribute name="onlynewfiles" type="xs:Boolean" default="false"/>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>


Table 7. Directory XML response message description.
Element                 Description
DateTime                The date and time the response was generated.
                        Sample: 10/10/2009 3:22:42 PM
DaysSincePassChange           The number of days that has elapsed since the user last changed their
                              password.
                              Sample: 23
                              Format: Numeric
StatusCode                    A string that identifies the resulting status of the performed operation.
                              Sample: 0
                              Format: Numeric
StatusDescription             A string that describes the status code returned in the response.
                              Sample: Directory Success (respective to status code: 0)
                              Format: Alpha-numeric
FileCount                     An integer value of data type string that identifies the number of files returned
                              in the directory listing.
                              Sample Data: 50
                              Format: Numeric
DirectoryList                 This will be a list of 0 or more occurrences of a FileInfo XML structure.
                              Sample: see FileInfo Table 8
                              Format: XML




10                                                                                                           7/15/10
                                                                                     Vendor Interface Specification



Table 8. FileInfo Xml structure description.
Element            Description
FileId             An unsigned long value of data type string that identifies the ID of the file.
                   Sample: 555925469
                   Format: Numeric
FileName           A string that identifies the name of the file available for downloading.
                   Sample: foo.txt
                   Format: Alpha-numeric
FilePath           A string that identifies the relative file path where stored on the server.
                   Sample: /Home/MC123456/download/
                   Format: Alpha-numeric
FileSize           An unsigned long value of data type string that indentifies the file size in bytes.
                   Sample: 30606
                   Format: Numeric
DateCreated        A string that represents the date and time the file was uploaded/created on the
                   server.
                   Sample: 10/27/2009 12:44:25 PM
                   Format: Alpha-numeric-special

Sample directory XML response message
<Response>
 <DateTime>6/16/2009 3:53:51 PM</DateTime>
 <DaysSincePassChange>23</DaysSincePassChange>
 <StatusCode>0</StatusCode>
 <StatusDescription>Directory Success</StatusDescription>
 <FileCount>1</FileCount>
 <DirectoryList>
 <FileInfo>
 <FileID>123456</FileID>
 <FileName>foo.997</FileName>
 <FilePath>/Home/test1234/download/</FilePath>
 <FileSize>2345</FileSize>
 <DateCreated> 10/5/2009 9:38:26 AM</DateCreated>
 </FileInfo>
 </DirectoryList>
</Response>


Directory response XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" xml:lang="EN">
 <xsd:element name="Response">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="DateTime" type="xsd:string"/>
 <xsd:element name=”DaysSincePassChange” type=”xsd:string”/>
 <xsd:element name="StatusCode" type="xsd:string"/>
 <xsd:element name="StatusDescription" type="xsd:string"/>
 <xsd:element name="FileCount" type="xsd:string"/>
 <xsd:element name="DirectoryList">
 <xsd:element name="FileInfo" minOccurs="0" maxOccurs="unbounded">
 <xsd:sequence>
 <xsd:element name="FileID" type="xsd:string"/>
 <xsd:element name="FileName" type="xsd:string"/>
 <xsd:element name="FilePath" type="xsd:string"/>
 <xsd:element name=”FileSize” type=”xsd:string”/>
 <xsd:element name="DateCreated" type="xsd:string"/>
 </xsd:sequence>
 </xsd:element>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>




7/15/10                                                                                                         11
DeleteFile request and response messages
The DeleteFile message is an XML formatted message used to delete files in a user‟s download folder
once a file has been downloaded. This facilitates clean up of old files in a timely manner. If a user opts to
not delete files immediately after download, all files still present after 24 hours will be deleted to conserve
space. See Appendix D for a sample DeleteFile program.

Table 9. DeleteFile XML request message description.
Element    Description                                                                          Require
UserName The username is used to authenticate the user submitting the request.                  Y
           Sample Data: MC123456
           Format: Alphanumeric
PassWord      The password is used in conjunction with the UserName to ensure the               Y
              validity of the user making the request.
              Sample Data: pass1234
              Format: Alphanumeric
FileID        The ID of the file that is to be deleted. This can be obtained from a previous    N
              DownLoad request or, if deleting occurs at a later time, it can be obtained       If a file name
              from the Directory request.                                                       is provided
              Sample: 555925469
              Format: Numeric
FileName      The name of the file that is to be deleted. This can be obtained from a           N
              previous DownLoad request or, if deleting occurs at a later time, it can be       If a file ID is
              obtained from the Directory request.                                              provided
              Sample: foo.txt
              Format: alpha-numeric-special

Sample DeleteFile XML request message (using FileID)
<DeleteFile>
       <UserName>MyTestUser</UserName>
       <PassWord>MyTestPassword</PassWord>
       <FileID>555925469</FileID>
</DeleteFile>


Sample DeleteFile XML request message (using FileName)
<DeleteFile>
       <UserName>MyTestUser</UserName>
       <PassWord>MyTestPassword</PassWord>
       <FileName>foo.txt</FileName>
</DeleteFile>


DeleteFile request XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" xml:lang="EN">
 <xsd:element name="DeleteFile">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="UserName type="xsd:string"/>
 <xsd:element name="PassWord" type="xsd:string"/>
                <xsd:element name="FileID" type="xsd:string" minOccurs="0"/>
                <xsd:element name="FileName" type="xsd:string" minOccurs="0"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>




12                                                                                                        7/15/10
                                                                                  Vendor Interface Specification



Table 10. DeleteFile XML response message description.
Element                  Description
DateTime                 The date and time the response was generated.
                         Sample: 10/10/2009 3:22:42 PM

DaysSincePassChange      The number of days that has elapsed since the user last changed their
                         password.
                         Sample: 23
                         Format: Numeric
StatusCode               A string that identifies the resulting status of the performed operation.
                         Sample: 0
                         Format: Numeric
StatusDescription        A string that describes the status code returned in the response.
                         Sample: Directory Success (respective to status code: 0)
                         Format: Alpha-numeric
FileID                   A numeric value of data type string that identifies the file deleted.
                         Sample: 555925469
                         Format: Numeric
FileName                 The name of the file that was deleted.
                         Sample: foo.txt
                         Format: alpha- numeric-special

Sample DeleteFile XML response message
<Response>
 <DateTime>6/16/2009 3:53:51 PM</DateTime>
 <DaysSincePassChange>23</DaysSincePassChange>
 <StatusCode>0</StatusCode>
 <StatusDescription>File Delete Success</StatusDescription>
 <FileID>555925469</FileID>
<FileName>foo.txt<FileID>
</Response>


DeleteFile response XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" xml:lang="EN">
 <xsd:element name="Response">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="DateTime" type="xsd:string"/>
 <xsd:element name=”DaysSincePassChange” type=”xsd:string”/>
 <xsd:element name="StatusCode" type="xsd:string"/>
 <xsd:element name="StatusDescription" type="xsd:string"/>
 <xsd:element name="FileID" type="xsd:string"/>
 <xsd:element name="FileName" type="xsd:string"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>



SuggestedPassWord request and response messages
The SuggestedPassWord message can be used to receive a randomly generated password that meets
all password requirements listed in this document under Section 1.5: Security Standards and Practices.




7/15/10                                                                                                      13
Table 11. SuggestedPassWord XML request message description.
Element     Description                                                                              Require
UserName     The username is used to authenticate the user submitting the request.                   Y
             Sample Data: MC123456
             Format: Alphanumeric
PassWord     The password is used in conjunction with the UserName to ensure the validity of         Y
             the user making the request.
             Sample Data: pass1234
             Format: Alpha-numeric-special

Sample SuggestedPassWord XML request message
<SuggestedPassWord>
 <UserName>MYTESTUSER</UserName>
 <PassWord>MyTestPassword</PassWord>
</SuggestedPassWord>


SuggestedPassWord request XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="SuggestedPassWord">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="UserName" type="xsd:string"/>
 <xsd:element name="PassWord" type="xsd:string"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>


Table 12. SuggestedPassWord XML response message description.
Element                Description
DateTime               The date and time the response was generated.
                       Sample: 10/10/2009 3:22:42 PM
DaysSincePassChange      The number of days that has elapsed since the user last changed their
                         password.
                         Sample: 23
                         Format: Numeric
StatusCode               A string that identifies the resulting status of the performed operation.
                         Sample: 0
                         Format: Numeric
StatusDescription        A string that describes the status code returned in the response.
                         Sample: UpLoad Success (respective to status code: 0)
                         Format: Alpha-numeric
PassWord                 A password that is guaranteed to meet all required password standards.
                         Sample: 4rfv%TGB
                         Format: alpha-numeric-special


Sample SuggestedPassWord XML response message
<Response>
 <DateTime>10/10/2009 3:22:42 PM </DateTime>
 <DaysSincePassChange>23</DaysSincePassChange>
 <StatusCode>0</StatusCode>
 <StatusDescription>Get Suggested Password Success</StatusDescription>
 <PassWord>7ujm*IK$</PassWord>
</Response>




14                                                                                                       7/15/10
                                                                             Vendor Interface Specification



SuggestedPassWord response XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="Response">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="DateTime" type="xsd:string"/>
 <xsd:element name="DaysSincePassChange" type="xsd:string"/>
 <xsd:element name="StatusCode" type="xsd:string"/>
 <xsd:element name="StatusDescription" type="xsd:string"/>
 <xsd:element name="PassWord" type="xsd:string"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>



PassWordChange request and response messages
The PassWordChange message is used to change a user‟s password when an aged password prevents
the use of the standard UpLoad, DownLoad, and Directory request transactions. Password protocol may
be reviewed in this document under Section 1.5: Security Standards and Practices.

Table 13. PassWordChange XML request message descriptions.
Element        Description                                              Length                   Require
UserName       The username is used to authenticate the user            6-15                     Y
               submitting the request.
               Sample Data: MC123456
               Format: Alphanumeric
PassWord       The password is used in conjunction with the             Min: 8                   Y
               UserName to ensure the validity of the user making the   Alpha-Numeric
               request.                                                 Can include
               Sample Data: pass1234                                    special characters
               Format: Alphanumeric
NewPassWord A password that meets all required password                 Minimum 8                Y
               standards.
               Sample Data: 5tgb^YHN7ujm
               Format: Alpha-Special-numeric

Sample PassWordChange XML request message
<PassWordChange>
 <UserName>MYTESTUSER</UserName>
 <PassWord>MyTestPassword</PassWord>
 <NewPassWord>1qaz@WSX3edc</NewPassWord>
</PassWordChange>


PassWordChange request XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="PassWordChange">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="UserName" type="xsd:string"/>
 <xsd:element name="PassWord" type="xsd:string"/>
                <xsd:element name="NewPassWord" type="xsd:string"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>




7/15/10                                                                                                 15
Table 14. PassWordChange XML response message description.
Element               Description
DateTime              The date and time the response was generated.
                      Sample: 10/10/2009 3:22:42 PM
DaysSincePassChange      The number of days that has elapsed since the user last changed their
                         password.
                         Sample: 23
                         Format: Numeric
StatusCode               A string that identifies the resulting status of the performed operation.
                         Sample: 0
                         Format: Numeric
StatusDescription        A string that describes the status code returned in the response.
                         Sample: Password Changed Successfully (respective to status code: 0)
                         Format: Alpha-numeric

Sample PassWordChange XML response message
<Response>
 <DateTime>10/10/2009 3:22:42 PM </DateTime>
 <DaysSincePassChange>0</DaysSincePassChange>
 <StatusCode>0</StatusCode>
 <StatusDescription> Password Changed Successfully </StatusDescription>
</Response>


PassWordChange response XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="Response">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="DateTime" type="xsd:string"/>
 <xsd:element name=”DaysSincePassChange” type=”xsd:string”/>
 <xsd:element name="StatusCode" type type="xsd:string"/>
 <xsd:element name="StatusDescription" type="xsd:string"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>



Error response message
Any error messages will be sent back and accessed in the StatusCode and StatusDescription elements of
the appropriate response.

Sample UpLoad XML response message (containing error message):
<Response>
 <DateTime>10/10/2009 3:22:42 PM </DateTime>
 <DaysSincePassChange>23</DaysSincePassChange>
 <StatusCode>200</StatusCode>
 <StatusDescription>
        A file with the name 'foo.txt' already exists in this folder.
 </StatusDescription>
 <FileID>0</FileID>
 <FileName>foo.txt</FileName>
 <FilePath></FilePath>
</Response>




16                                                                                                   7/15/10
                                                                                 Vendor Interface Specification




Status codes and status descriptions
Status codes and descriptions can be used to supply the end-user‟s application with the status of a
performed transaction, along with a brief description of the accompanied status code.


Table 15. Example status codes and status descriptions.
Status      Status Description
Code
-2          Your password expires today! A password change is required.
-1          Invalid Request Format
0           “Requested Operation” Success
200         A file with the name “File name” already exists in this folder.
2025        Invalid username/password or not allowed to sign on from this location.
2976        Invalid username/password or not allowed to sign on from this location.
2850        Unable to locate file 'File Path and Name'
2410        New password is not strong enough. "password criteria here"
2020        Not allowed to delete file id # „id‟




7/15/10                                                                                                     17
FTPS (FTP over SSL) specification
This section covers the basic FTP commands that are most frequently used. A complete list of supported
FTP commands can be found in Appendix E. FTPS connections can be established using
“secure.medicaid.state.ar.us” port 990 (Explicit) and port 21 (Implicit).

Note: Users are required to change passwords on first login; you must log in either to
      https://secure.medicaid.state.ar.us or via an interactive FTPS session to change your password.


Uploading files
When uploading files via FTPS, a connection should be made to “secure.medicaid.state.ar.us” using a
trading partner user ID (also known as MCID) and password. The user should then “CWD” to
/home/<your MCID>/upload and upload the file by issuing the “STOR” command along with the name of
the file that is to be uploaded.

Example: STOR foo.txt


Downloading files
When downloading files via FTPS, a connection should be made to “secure.medicaid.state.ar.us” using
an MCID and password. The user should then “CWD” to /home/<your MCID>/download and retrieve the
file from that location with the “RETR” command along with either the file name or the file ID.

Example: RETR foo.txt


Directory listing
When attempting to ascertain what response files have been created and are available to download via
FTPS, a connection should be made to “secure.medicaid.state.ar.us” using the MCID and password. The
user should then “CWD” to /home/<your MCID>/download and execute a “LIST” command for a list of
downloadable files.

Example: LIST


Change user password
When a user needs to change their password via FTPS, a connection should be made to
“secure.medicaid.state.ar.us” using an MCID and password. Use the change password command
“CHGPW” along with the current password and the new password twice. The old password is rechecked.
The new passwords must match and meet all password requirements listed under Section 1.5: Security
Standards and Practices.

Example: CHGPW oldpassword newpassword newpassword




18                                                                                               7/15/10
                                                                                  Vendor Interface Specification




SFTP (FTP over SSH) specification
This section covers the basic SFTP commands that are most frequently used. An SFTP connection can
be established using “secure.medicaid.state.ar.us” port 22.

Note: Users are required to change passwords on first login; you must log in to
      https://secure.medicaid.state.ar.us to change your password.


Uploading files
When uploading files via SFTP, a connection should be made to “secure.medicaid.state.ar.us” using an
MCID and password. To upload a file, “cd” to /home/<your MCID>/upload and issue the “put” command
along with the name of the file to be uploaded.

Example: put foo.txt


Downloading files
When downloading files via SFTP, a connection should be made to “secure.medicaid.state.ar.us” using
your MCID and password. To download a file, “cd” to /home/<your MCID>/download and retrieve the file
from that location with the “get” command along with file name or file id.

Example: get foo.txt


Directory listing
When attempting to ascertain what response files have been created and are available to download via
SFTP, a connection should be made to “secure.medicaid.state.ar.us” using an MCID and password.
Then, “cd” to /home/<your MCID>/download and execute a “dir” command for a list of downloadable files.

Example: dir


Change user password
Not supported for SFTP.




7/15/10                                                                                                      19
Security standards and practices
Since interaction with the WebBBS is accomplished over the World Wide Web, security is a concern in
ensuring that services are and will be available for use in a secure and stable environment. In order for
HP Enterprise Services to guarantee a safe and stable working environment, security standards and
practices have been established and put in place. These measures protect both users and HP Enterprise
Services from threats that exist in World Wide Web traffic.


Password creation requirements
     1. Password must contain a minimum of 8 alpha-numeric-special characters.

     2. Password must contain at least 1 upper and 1 lower case alpha character.

     3. Password must contain at least 1 number.

     4. Password must contain at least 1 special character.

     5. Cannot be similar to username (MCID).

     6. Cannot use any common 'dictionary' word.

     7. Cannot use previous six (6) passwords.


New WebBBS client passwords
     1. Any new client to the WebBBS system will be given a temporary password that meets the
        required criteria as listed above.

     2. This password will be a one-time-use only password that must be changed upon first login. The
        newpassword should be of the client‟s choosing and adhere to the required password criteria
        listed above.


Password aging
     1. Passwords will expire after a 90 day period.

     2. Each method of interaction with WebBBS, excluding SSH protocol, has its own procedures for
        changing passwords when a change is deemed necessary by the system. Each of these
        procedures can be reviewed below in the following subsections.


Website password change procedures
The WebBBS website is set up with a 10 day “warning period” to notify users prior to password expiration.
When a user logs in during this period, they will be prompted to change their password. If the user fails to
login during or prior to the “warning period” to change their password, allowing it to exceed its 90 day life
span, the account will be locked, and the user will need to contact the EDI Help Desk for further
assistance.



20                                                                                                    7/15/10
                                                                                   Vendor Interface Specification



Note: Passwords may be changed at any time by logging into the secure website
      https://secure.medicaid.state.ar.us


Web service password change procedures
WebBBS clients using the web service interface will not be given a 10 day “warning period” prior to their
                                                                                      th
password expiring. They will only be notified that their password has aged on the 90 day, and, at this
time, the user will not be allowed to perform any upload, download, directory, or delete transactions until
the password has been changed. A client application can ascertain when a password needs to be
changed by checking the “DaysSinceLastPassChange” field in each response sent back from the server.
If the user fails to change their password and the account password is allowed to exceed a 90 day life
span, the account will be locked out, and the userwill need to contact the EDI Help Desk for further
assistance.


FTPS (FTP over SSL) password change procedures
WebBBS supports the following FTP command to change a user‟s password:

CHGPW oldpass new pass newpass

This command sends a password request to WebBBS for the logged on user. The old password is
rechecked and the passwords must match and meet the strength requirements for the site.


SFTP (FTP over SSH) password change procedures
Not supported.




7/15/10                                                                                                       21
Appendix A: Sample file upload program
Connection buffers should be set no larger than 4,096,000 bytes and connection timeouts should be set
at 2 minutes (120 seconds) for file upload applications. This sample application accepts the username
and password as command line parameters.

using   System;
using   System.Collections.Generic;
using   System.Linq;
using   System.Text;
using   System.Xml;

namespace Local_Web_Service_Test
{
 class Program
 {
 static void Main(string[] args)
 {
 //created and named a reference to the WebBBS web service using web service wizard
 // with url set to https://secure.medicaid.state.ar.us:8443/WebBBS.asmx
 API_FileHandler_Numeric.API_FileHandlerSoapClient myWebBBSService =
 new API_FileHandler_Numeric.API_FileHandlerSoapClient();

 String temp = "<UpLoad>" +
 "<UserName>" + args[0] + "</UserName>" +
 "<PassWord>" + args[1] + "</PassWord>" +
 "<FileName>foo.txt</FileName>" +
 "<FileData>1234567890</FileData>" +
 "</UpLoad>";
 XmlDoument request = new XmlDocument();
 XmlElement response = null;
 request.LoadXml(temp);

 //sending a request as a string type
 response = myWebBBSService.WebDownloadFromClient(request.InnerXml);

 System.Console.WriteLine(response);


 //sending a request as xml type
 response = myWebBBSService.WebDownloadFromClient1((XmlElement)request.FirstChild);
 System.Console.WriteLine(response);

 }
 }
}




22                                                                                               7/15/10
                                                                                Vendor Interface Specification




Appendix B: Sample file DownLoad program
Connection buffers should be set no larger than 4,096,000 bytes and connection timeouts should be set
at 2 minutes (120 seconds) for file download applications. This sample application accepts the username
and password as command line parameters.

using     System;
using     System.Collections.Generic;
using     System.Linq;
using     System.Text;
using     System.Xml;

namespace Local_Web_Service_Test
{
 class Program
 {
 static void Main(string[] args)
 {
 //created and named a reference to the WebBBS webservice using webservice wizard
 // with url set to https://secure.medicaid.state.ar.us:8443/WebBBS.asmx
 API_FileHandler_Numeric.API_FileHandlerSoapClient myWebBBSService =
 new API_FileHandler_Numeric.API_FileHandlerSoapClient();

 String temp = "<DownLoad>" +
 "<UserName>" + args[0] + "</UserName>" +
 "<PassWord>" + args[1] + "</PassWord>" +
 "<FileID>502940839</FileID>"
 "</DownLoad>";
 XmlDoument request = new XmlDocument();
 XmlElement response = null;
 request.LoadXml(temp);

 //sending a request as a string type
 response = myWebBBSService.WebDownloadFromClient(request.InnerXml);
 System.Console.WriteLine(response);

 //sending a request as xml type
 response = myWebBBSService.WebDownloadFromClient1((XmlElement)request.FirstChild);
 System.Console.WriteLine(response);
 }
 }
}




7/15/10                                                                                                    23
Appendix C: Sample directory listing program
Connection buffers should be set no larger than 4,096,000 bytes and connection timeouts should be set
at 2 minutes (120 seconds) for directory listing applications. This sample application accepts the
username and password as command line parameters.

using   System;
using   System.Collections.Generic;
using   System.Linq;
using   System.Text;
using   System.Xml;

namespace Local_Web_Service_Test
{
 class Program
 {
 static void Main(string[] args)
 {
 //created and named a reference to the WebBBS webservice using webservice wizard
 // with url set to https://secure.medicaid.state.ar.us:8443/WebBBS.asmx
 API_FileHandler_Numeric.API_FileHandlerSoapClient myWebBBSService =
 new API_FileHandler_Numeric.API_FileHandlerSoapClient();

 String temp = "<Directory>" +
 "<UserName>" + args[0] + "</UserName>" +
 "<PassWord>" + args[1] + "</PassWord>" +
 "<FileTypes>*.*</FileTypes>" +
 "</Directory>";
 XmlDoument request = new XmlDocument();
 XmlElement response = null;
 request.LoadXml(temp);

 //sending a request as a string type; InnerXml property returns a string
 response = myWebBBSService.WebDirectoryDownloadFromClient(request.InnerXml);
 System.Console.WriteLine(response);

 //sending a request as xml type;
 response = myWebBBSService.WebDownloadFromClient1((XmlElement)request.FirstChild);
 System.Console.WriteLine(response);
 }
 }
}




24                                                                                               7/15/10
                                                                               Vendor Interface Specification




Appendix D: Sample DeleteFile program
Connection buffers should be set no larger than 4,096,000 bytes and connection timeouts should be set
at 2 minutes (120 seconds) for DeleteFile applications. This sample application accepts the username
and password as command line parameters.

using     System;
using     System.Collections.Generic;
using     System.Linq;
using     System.Text;
using     System.Xml;

namespace Local_Web_Service_Test
{
 class Program
 {
 static void Main(string[] args)
 {
 //created and named a reference to the WebBBS webservice using webservice wizard
 // with url set to https://secure.medicaid.state.ar.us:8443/WebBBS.asmx
 API_FileHandler_Numeric.API_FileHandlerSoapClient myWebBBSService =
 new API_FileHandler_Numeric.API_FileHandlerSoapClient();

 String temp1 = "<DownLoad>" +
 "<UserName>" + args[0] + "</UserName>" +
 "<PassWord>" + args[1] + "</PassWord>" +
 "<FileID>502940839</FileID>"
 "</DownLoad>";
 String temp2 = "<DeleteFile>" +
 "<UserName>" + args[0] + "</UserName>" +
 "<PassWord>" + args[1] + "</PassWord>" +
 "<FileID>502940839</FileID>"
 "</DeleteFile>"
 XmlDoument request1 = new XmlDocument();
 XmlElement response1 = null;
 XmlDoument request2 = new XmlDocument();
 XmlElement response2 = null;
 request1.LoadXml(temp1);
 request2.LoadXml(temp2);

 //sending a request as a string type
 response1 = myWebBBSService.WebDownloadFromClient(request1.InnerXml);
         if( response.GetElemtentsByTagName[“StatusCode”].Item(0).InnerText == "0" )
 {
         // successful download delete file from source download folder
 myWebBBSService.WebDeleteFileFromClient(request2.InnerXml);
 }

 //sending a request as xml type
 response1 = myWebBBSService.WebDownloadFromClient1((XmlElement)request1.FirstChild);
 if( response1.GetElemtentsByTagName[“StatusCode”].Item(0).InnerText == "0" )
 {
         // successful download delete file from source download folder
 myWebBBSService.WebDeleteFileFromClient1((XmlElement)request2.FirstChild);
 }
 System.Console.WriteLine(response1);
 System.Console.WriteLine(response2);
 }
 }
}




7/15/10                                                                                                   25
Appendix E: Supported FTP commands.
Command             Description
USER username       Indicates the WebBBS username to use for login.

PASS password       Indicates the WebBBS password to use for login.

AUTH type           Starts secure communication for the specified security type: TLS-C or
                    TLS-P.
FEAT                Returns the feature set supported, specifically AUTH, PROT and
                    PBSZ.
PROT type           Sets the data connection protection type. For TLS-C security, the
                    PROT P command is required to enable security on the data channel.
PBSZ size           Sets the protection buffer size for encryption. Included for
                    compatibility; the size is never checked.
CLNT name version   Sets the FTP client name and version for logging purposes.

LIST                Obtains a directory listing, with date, size, and filename in a format
                    compatible with Microsoft's FTP server. Any command arguments
                    beginning with "-" are ignored.
NLST                Obtains a bare directory listing.

RETR fileID         Downloads a file, first checking that the current user has read access
                    to the file. The fileID of the file to retrieve, the filename can be used in
                    place of the ID.
STOR filename       Uploads a file. WebBBS will create a new fileID and return it in the 226
                    response.
APPE filename       Appends a file. This is only supported for resuming file transfers.
                    WebBBS will create a new fileID, copy the old partial file and append
                    new data, and return it in the 226 response.
CWD directory       Changes current directory. See below.

MKD directory       Creates a directory, if the user has permission.

RMD directory       Deletes a directory, if the user has permission.

DELE fileID         Deletes the file, if the user has permission.

RNFR fileID         Changes the original file name associated with a file ID, if the user has
RNTO filename       permission.
REST skipcount      Sets the byte skip count for a subsequent RETR or STOR command.
                    For RETR, WebBBS will skip the first "skipcount" number of bytes in
                    the downloaded file. For STOR, WebBBS will copy the first "skipcount"
                    number of bytes from the destination file to a new file then append the
                    transmitted bytes.




26                                                                                        7/15/10
                                                                                 Vendor Interface Specification



Command                          Description
SIZE filename                    Reports the size in bytes of the named file, the same number returned
                                 in a directory list.
MODE type                        Sets the mode in which data is to be transferred via the data
                                 connection, S for Stream Mode, and Z for Zip compression mode.
SYST                             Reports the system type. The returned string indicates compatibility
                                 with the Microsoft Windows FTP server.
HELP                             Displays a list of commands.

PORT                             Initiates an active data connection. If configured to allow only passive
                                 connections, this is refused.
PASV                             Initiates a passive connection. This is used by some FTP clients to
                                 accommodate firewalls that do not allow an FTP server to initiate TCP
                                 data connections.
QUIT                             Quits the session.

CCC                              If enabled, the Cleartext Command Channel command switches the
                                 command channel from encrypted to cleartext.
STAT                             Returns brief information to properly authorized users about the FTP
                                 server including name, version and local time.
CLNT name version                Sets the FTP client name and version for logging purposes.


WebBBS supports the following FTP commands for the purposes of integrity checking.
Command                         Description
INTEGRITY type                  Enables integrity checking on STOR and RETR. For type L, use "lump
                                mode" data stream which compresses data on the fly and include a
                                SHA1 hash of the file for integrity verification. For type H, "hash
                                mode", the data stream is standard, and the client is responsible for
                                checking the SHA1 hash for integrity verification. Type N turns
                                integrity checking off.
XSHA1 filename                  Returns the SHA1 hash of the file named, usually the most recently
                                transferred file.
HASH OK/BAD                     Notifies WebBBS FTP, after a STOR or RETR, that the client has
                                verified the file SHA1 hash and that it has matched (or not matched)
                                the one passed in the data stream in lump mode, or returned by the
                                XSHA1 command.

WebBBS supports the following FTP command for the purpose of changing a password.
Command                                     Description
CHGPW oldpassword newpassword               Sends a password change request to WebBBS for the
newpassword                                 logged-on user. The old password is rechecked and the
                                            new passwords must match and meet strength
                                            requirements for the site.

WebBBS unsupported commands: ACCT, SMNT, REIN, STOU, ALLO, ABOR, SITE




7/15/10                                                                                                     27
Appendix F: SOAP 1.1 envelopes
The following are sample SOAP 1.1 requests and responses. The placeholders shown should be
replaced with actual values.

WebBBSPingWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebbbsPingWithXml"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebbbsPingWithXml xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebbbsPingWithXml>
 </soap:Body>
</soap:Envelope>


WebBBSPingWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebbbsPingWithXmlResponse xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebbbsPingWithXmlResult>XML Response</WebbbsPingWithXmlResult>
 </WebbbsPingWithXmlResponse>
 </soap:Body>
</soap:Envelope>


WebBBSPingWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebbbsPingWithString"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebbbsPingWithString xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebbbsPingWithString>
 </soap:Body>
</soap:Envelope>


WebBBSPingWithString response envelope
POST /webbbs.asmx HTTP/1.1




28                                                                                           7/15/10
                                                                           Vendor Interface Specification



Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebbbsPingWithStringResponse xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebbbsPingWithStringResult>XML Response</WebbbsPingWithStringResult>
 </WebbbsPingWithStringResponse>
 </soap:Body>
</soap:Envelope>


WebUploadFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebUploadFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebUploadFromClientWithXml xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebUploadFromClientWithXml>
 </soap:Body>
</soap:Envelope>


WebUploadFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebUploadFromClientWithXmlResponse xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebUploadFromClientWithXmlResult>XML Response</WebUploadFromClientWithXmlResult>
 </WebUploadFromClientWithXmlResponse>
 </soap:Body>
</soap:Envelope>


WebUploadFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebUploadFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebUploadFromClientWithString xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>



7/15/10                                                                                               29
 </WebUploadFromClientWithString>
 </soap:Body>
</soap:Envelope>


WebUploadFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebUploadFromClientWithStringResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebUploadFromClientWithStringResult>XML Response</WebUploadFromClientWithStringResult>
 </WebUploadFromClientWithStringResponse>
 </soap:Body>
</soap:Envelope>


WebDownloadFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebDownloadFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDownloadFromClientWithXml xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebDownloadFromClientWithXml>
 </soap:Body>
</soap:Envelope>


WebDownloadFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDownloadFromClientWithXmlResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDownloadFromClientWithXmlResult>XML Response</WebDownloadFromClientWithXmlResult>
 </WebDownloadFromClientWithXmlResponse>
 </soap:Body>
</soap:Envelope>


WebDownloadFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebDownloadFromClientWithString"



30                                                                                           7/15/10
                                                                           Vendor Interface Specification




<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDownloadFromClientWithString xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebDownloadFromClientWithString>
 </soap:Body>
</soap:Envelope>


WebDownloadFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDownloadFromClientWithStringResponse
xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDownloadFromClientWithStringResult>XML Response</WebDownloadFromClientWithStringResult>
 </WebDownloadFromClientWithStringResponse>
 </soap:Body>
</soap:Envelope>


WebDirectoryDownloadFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction:
"https://secure.medicaid.state.ar.us/webbbs.asmx/WebDirectoryDownloadFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDirectoryDownloadFromClientWithXml
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebDirectoryDownloadFromClientWithXml>
 </soap:Body>
</soap:Envelope>


WebDirectoryDownloadFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDirectoryDownloadFromClientWithXmlResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDirectoryDownloadFromClientWithXmlResult>



7/15/10                                                                                               31
 Xml Response
 </WebDirectoryDownloadFromClientWithXmlResult>
 </WebDirectoryDownloadFromClientWithXmlResponse>
 </soap:Body>
</soap:Envelope>


WebDirectoryDownloadFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction:
"https://secure.medicaid.state.ar.us/webbbs.asmx/WebDirectoryDownloadFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDirectoryDownloadFromClientWithString
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebDirectoryDownloadFromClientWithString>
 </soap:Body>
</soap:Envelope>


WebDirectoryDownloadFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDirectoryDownloadFromClientWithStringResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDirectoryDownloadFromClientWithStringResult>
 Xml Response
 </WebDirectoryDownloadFromClientWithStringResult>
 </WebDirectoryDownloadFromClientWithStringResponse>
 </soap:Body>
</soap:Envelope>


WebDeleteFileFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebDeleteFileFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDeleteFileFromClientWithXml xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebDeleteFileFromClientWithXml>
 </soap:Body>
</soap:Envelope>




32                                                                                           7/15/10
                                                                           Vendor Interface Specification



WebDeleteFileFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDeleteFileFromClientWithXmlResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDeleteFileFromClientWithXmlResult>Xml Response</WebDeleteFileFromClientWithXmlResult>
 </WebDeleteFileFromClientWithXmlResponse>
 </soap:Body>
</soap:Envelope>


WebDeleteFileFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebDeleteFileFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDeleteFileFromClientWithString xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebDeleteFileFromClientWithString>
 </soap:Body>
</soap:Envelope>


WebDeleteFileFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebDeleteFileFromClientWithStringResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDeleteFileFromClientWithStringResult>
 Xml Response
 </WebDeleteFileFromClientWithStringResult>
 </WebDeleteFileFromClientWithStringResponse>
 </soap:Body>
</soap:Envelope>


WebGetSuggestedPassWordFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction:
"https://secure.medicaid.state.ar.us/webbbs.asmx/WebGetSuggestedPassWordFromClientWithXml"

<?xml version="1.0" encoding="utf-8">



7/15/10                                                                                               33
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebGetSuggestedPassWordFromClientWithXml
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebGetSuggestedPassWordFromClientWithXml>
 </soap:Body>
</soap:Envelope>


WebGetSuggestedPassWordFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebGetSuggestedPassWordFromClientWithXmlResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebGetSuggestedPassWordFromClientWithXmlResult>
 Xml Response
 </WebGetSuggestedPassWordFromClientWithXmlResult>
 </WebGetSuggestedPassWordFromClientWithXmlResponse>
 </soap:Body>
</soap:Envelope>


WebGetSuggestedPassWordFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction:
"https://secure.medicaid.state.ar.us/webbbs.asmx/WebGetSuggestedPassWordFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebGetSuggestedPassWordFromClientWithString
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebGetSuggestedPassWordFromClientWithString>
 </soap:Body>
</soap:Envelope>


WebGetSuggestedPassWordFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebGetSuggestedPassWordFromClientWithStringResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">



34                                                                                         7/15/10
                                                                           Vendor Interface Specification



 <WebGetSuggestedPassWordFromClientWithStringResult>
 Xml Response
 </WebGetSuggestedPassWordFromClientWithStringResult>
 </WebGetSuggestedPassWordFromClientWithStringResponse>
 </soap:Body>
</soap:Envelope>


WebPassWordChangeFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebPassWordChangeFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebPassWordChangeFromClientWithXml xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebPassWordChangeFromClientWithXml>
 </soap:Body>
</soap:Envelope>


WebPassWordChangeFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebPassWordChangeFromClientWithXmlResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebPassWordChangeFromClientWithXmlResult>
 Xml Response
 </WebPassWordChangeFromClientWithXmlResult>
 </WebPassWordChangeFromClientWithXmlResponse>
 </soap:Body>
</soap:Envelope>




7/15/10                                                                                               35
WebPassWordChangeFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length
SOAPAction:
"https://secure.medicaid.state.ar.us/webbbs.asmx/WebPassWordChangeFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebPassWordChangeFromClientWithString
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebPassWordChangeFromClientWithString>
 </soap:Body>
</soap:Envelope>


WebPassWordChangeFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: text/xml;charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <WebPassWordChangeFromClientWithStringResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebPassWordChangeFromClientWithStringResult>
 XML Response
 </WebPassWordChangeFromClientWithStringResult>
 </WebPassWordChangeFromClientWithStringResponse>
 </soap:Body>
</soap:Envelope>




36                                                                                        7/15/10
                                                                           Vendor Interface Specification




Appendix G: SOAP1.2 Envelopes
The following are sample SOAP 1.2 requests and responses. The placeholders shown should be with
actual values.

WebBBSPingWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebbbsPingWithXml"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap12:Body>
 <WebbbsPingWithXml xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebbbsPingWithXml>
 </soap12:Body>
</soap12:Envelope>


WebBBSPingWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap12:Body>
 <WebbbsPingWithXmlResponse xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebbbsPingWithXmlResult>XML Response</WebbbsPingWithXmlResult>
 </WebbbsPingWithXmlResponse>
 </soap12:Body>
</soap12:Envelope>


WebBBSPingWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebbbsPingWithString"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap12:Body>
 <WebbbsPingWithString xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebbbsPingWithString>
 </soap12:Body>
</soap12:Envelope>




7/15/10                                                                                               37
WebBBSPingWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap12:Body>
 <WebbbsPingWithStringResponse xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebbbsPingWithStringResult>XML Response</WebbbsPingWithStringResult>
 </WebbbsPingWithStringResponse>
 </soap12:Body>
</soap12:Envelope>


WebUploadFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebUploadFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebUploadFromClientWithXml xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebUploadFromClientWithXml>
 </soap12:Body>
</soap12:Envelope>


WebUploadFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebUploadFromClientWithXmlResponse xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebUploadFromClientWithXmlResult>XML Response</WebUploadFromClientWithXmlResult>
 </WebUploadFromClientWithXmlResponse>
 </soap12:Body>
</soap12:Envelope>




38                                                                                         7/15/10
                                                                           Vendor Interface Specification



WebUploadFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebUploadFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebUploadFromClientWithString xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebUploadFromClientWithString>
 </soap12:Body>
</soap12:Envelope>


WebUploadFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebUploadFromClientWithStringResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebUploadFromClientWithStringResult>XMl Response</WebUploadFromClientWithStringResult>
 </WebUploadFromClientWithStringResponse>
 </soap12:Body>
</soap12:Envelope>


WebDownloadFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebDownloadFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDownloadFromClientWithXml xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebDownloadFromClientWithXml>
 </soap12:Body>
</soap12:Envelope>




7/15/10                                                                                               39
WebDownloadFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDownloadFromClientWithXmlResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDownloadFromClientWithXmlResult>XML Response</WebDownloadFromClientWithXmlResult>
 </WebDownloadFromClientWithXmlResponse>
 </soap12:Body>
</soap12:Envelope>


WebDownloadFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebDownloadFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDownloadFromClientWithString xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebDownloadFromClientWithString>
 </soap12:Body>
</soap12:Envelope>


WebDownloadFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDownloadFromClientWithStringResponse
xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDownloadFromClientWithStringResult>XML Response</WebDownloadFromClientWithStringResult>
 </WebDownloadFromClientWithStringResponse>
 </soap12:Body>
</soap12:Envelope>




40                                                                                           7/15/10
                                                                           Vendor Interface Specification



WebDirectoryDownloadFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction:
"https://secure.medicaid.state.ar.us/webbbs.asmx/WebDirectoryDownloadFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDirectoryDownloadFromClientWithXml
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebDirectoryDownloadFromClientWithXml>
 </soap12:Body>
</soap12:Envelope>


WebDirectoryDownloadFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDirectoryDownloadFromClientWithXmlResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDirectoryDownloadFromClientWithXmlResult>
 XML Response
 </WebDirectoryDownloadFromClientWithXmlResult>
 </WebDirectoryDownloadFromClientWithXmlResponse>
 </soap12:Body>
</soap12:Envelope>


WebDirectoryDownloadFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction:
"https://secure.medicaid.state.ar.us/webbbs.asmx/WebDirectoryDownloadFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDirectoryDownloadFromClientWithString
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebDirectoryDownloadFromClientWithString>
 </soap12:Body>
</soap12:Envelope>




7/15/10                                                                                               41
WebDirectoryDownloadFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDirectoryDownloadFromClientWithStringResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDirectoryDownloadFromClientWithStringResult>
 XML Response
 </WebDirectoryDownloadFromClientWithStringResult>
 </WebDirectoryDownloadFromClientWithStringResponse>
 </soap12:Body>
</soap12:Envelope>


WebDeleteFileFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebDeleteFileFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDeleteFileFromClientWithXml xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebDeleteFileFromClientWithXml>
 </soap12:Body>
</soap12:Envelope>


WebDeleteFileFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDeleteFileFromClientWithXmlResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDeleteFileFromClientWithXmlResult>
 XML Response
 </WebDeleteFileFromClientWithXmlResult>
 </WebDeleteFileFromClientWithXmlResponse>
 </soap12:Body>
</soap12:Envelope>




42                                                                                          7/15/10
                                                                           Vendor Interface Specification



WebDeleteFileFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebDeleteFileFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDeleteFileFromClientWithString xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebDeleteFileFromClientWithString>
 </soap12:Body>
</soap12:Envelope>


WebDeleteFileFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebDeleteFileFromClientWithStringResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebDeleteFileFromClientWithStringResult>
 XML Response
 </WebDeleteFileFromClientWithStringResult>
 </WebDeleteFileFromClientWithStringResponse>
 </soap12:Body>
</soap12:Envelope>


WebGetSuggestedPassWordFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction:
"https://secure.medicaid.state.ar.us/webbbs.asmx/WebGetSuggestedPassWordFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebGetSuggestedPassWordFromClientWithXml
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebGetSuggestedPassWordFromClientWithXml>
 </soap12:Body>
</soap12:Envelope>




7/15/10                                                                                               43
WebGetSuggestedPassWordFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebGetSuggestedPassWordFromClientWithXmlResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebGetSuggestedPassWordFromClientWithXmlResult>
 XML Response
 </WebGetSuggestedPassWordFromClientWithXmlResult>
 </WebGetSuggestedPassWordFromClientWithXmlResponse>
 </soap12:Body>
</soap12:Envelope>


WebGetSuggestedPassWordFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction:
"https://secure.medicaid.state.ar.us/webbbs.asmx/WebGetSuggestedPassWordFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebGetSuggestedPassWordFromClientWithString
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebGetSuggestedPassWordFromClientWithString>
 </soap12:Body>
</soap12:Envelope>


WebGetSuggestedPassWordFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebGetSuggestedPassWordFromClientWithStringResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebGetSuggestedPassWordFromClientWithStringResult>
 XML Response
 </WebGetSuggestedPassWordFromClientWithStringResult>
 </WebGetSuggestedPassWordFromClientWithStringResponse>
 </soap12:Body>
</soap12:Envelope>




44                                                                                         7/15/10
                                                                           Vendor Interface Specification



WebPassWordChangeFromClientWithXml request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction: "https://secure.medicaid.state.ar.us/webbbs.asmx/WebPassWordChangeFromClientWithXml"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebPassWordChangeFromClientWithXml xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>XML Request</Request>
 </WebPassWordChangeFromClientWithXml>
 </soap12:Body>
</soap12:Envelope>


WebPassWordChangeFromClientWithXml response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebPassWordChangeFromClientWithXmlResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebPassWordChangeFromClientWithXmlResult>
 XML Response
 </WebPassWordChangeFromClientWithXmlResult>
 </WebPassWordChangeFromClientWithXmlResponse>
 </soap12:Body>
</soap12:Envelope>


WebPassWordChangeFromClientWithString request envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length
SOAPAction:
"https://secure.medicaid.state.ar.us/webbbs.asmx/WebPassWordChangeFromClientWithString"

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebPassWordChangeFromClientWithString
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <Request>String Request</Request>
 </WebPassWordChangeFromClientWithString>
 </soap12:Body>
</soap12:Envelope>




7/15/10                                                                                               45
WebPassWordChangeFromClientWithString response envelope
POST /webbbs.asmx HTTP/1.1
Host: secure.medicaid.state.ar.us
Content-Type: application/soap+xml; charset=utf-8
ContentLength:length

<?xml version="1.0" encoding="utf-8">
<soap12:Envelope
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xsd="http:www.w3.org/2001/XMLSchema"
 xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
 <soap:Body>
 <WebPassWordChangeFromClientWithStringResponse
 xmlns="https://secure.medicaid.state.ar.us/webbbs.asmx">
 <WebPassWordChangeFromClientWithStringResult>
 XML Response
 </WebPassWordChangeFromClientWithStringResult>
 </WebPassWordChangeFromClientWithStringResponse>
 </soap12:Body>
</soap12:Envelope>




46                                                          7/15/10
                                                                                 Vendor Interface Specification




Appendix H: Base64 encoding character set
The base64 encoding/decoding character set used by WebBBS is a widely accepted standard; in
ascending order from zero are the uppercase characters "A" to "Z", the lowercase characters "a" to "z",
the numerals "0" to "9", and the symbols "+" and "/". The valueless character "=" is used for trailing
padding.




7/15/10                                                                                                     47

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:229
posted:8/27/2011
language:English
pages:51