NORTHPOINTE SUITE WEB SERVICES ARCHITECTURE
|
|
- Cassandra Norton
- 5 years ago
- Views:
Transcription
1 NORTHPOINTE SUITE WEB SERVICES ARCHITECTURE
2 Table of Contents LDAP LOGIN 2 APPLICATION LOGIN 4 LIST REFERENCE CODES 9 STORE REFERENCE CODES 14 LIST AGENCIES 18 GET AGENCY ID 23 LIST SECURITY GROUPS 27 GET SECURITY GROUP ID 32 GET USER ID 37 STORE USER 42 STORE OFFENDER 48 Northpointe Evolving Practice Through Scientific Innovation 1
3 LDAP LOGIN Overview The main purpose of this use case is to create an alternative login process by validating user accounts against LDAP and Northpointe Suite. Measurable Result Actor successfully logs into the application Flow of Events Actor will access COMPAS thru a LDAP specific entry point. Actor s credentials are validated and a list of the actor s group memberships is returned to application. The system will check to see if the actor is a member of a group that matches a security group in COMPAS. If the actor is a member of a COMPAS security group the system will validate the actor s LDAP account information against a COMPAS user account and log them into the application. If the actor does not yet have an account in COMPAS, the system will create a new account using the actor s LDAP properties. If the actor is not a member to a group that matches a security group in COMPAS they will not be allowed access to COMPAS. Northpointe Evolving Practice Through Scientific Innovation 2
4 LDAP LOGIN Northpointe Evolving Practice Through Scientific Innovation 2009 Northpointe Institute for Public Management, Inc. All Rights Reserved. 3
5 SERVICES APPLICTION LOGIN Overview The main purpose of this use case is to expose a web service that logs the user into a specific application and return the url needed for the actor to redirect to the application home page. Measurable Result Actor successfully logs into the application Flow of Events System will expose a web service method requiring specific parameters. Once web service is invoked the system will validate actor s credentials. If credentials are valid the system will create a session inside the application and return a full URL that will be used to redirect the user into the application. If credentials are not valid the web service will return an error code. Web Service Name NPuserServices.asmx Web Service Parameters Table 1: Parameter List Item Type Required Service Key String X Customer_ID String X Application_ID Integer X UserName String X Password String X IsPasswordEncrypted RedirctToPage Boolean String Northpointe Evolving Practice Through Scientific Innovation 4
6 Services Application LOGIN Table 2: Parameter Details Item Description Database/Table/Field Service Key Customer_ID Application_ID Protected key that is required to invoke the web service Identifies the client Identifies the application trying to login to AppInfo Value Customer Rec_ID Sys_Application Rec_ID UserName Password IsPasswordEncrypted RedirectToPage Web Service Return User Name Password Boolean value to state if password being passed into method is encrypted or not. Page name of desired page redirect. Defaults to home.aspx. False See Northpointe for implementation details if other than home page Upon successfully completion of login procedure the web service will return the following string value Type DataSet Description NULL ErrorCode Default is 0 ReturnValue Message url needed to access application Default is an empty string Northpointe Evolving Practice Through Scientific Innovation 5
7 Services Application LOGIN Web Service Error Codes If the system encounters an error the web service will return and error code and description. Format for error code is as follows Error Code Description 100 Invalid Key 101 Invalid Customer_ID 102 Invalid Application_ID 103 Invalid Username or Password 104 Expired or inactive account 105 Account does not have access to application 900 UnExpected Error Northpointe Evolving Practice Through Scientific Innovation 6
8 Services Application LOGIN Soap 1.2 Response and Request Schema The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values. POST /northpointeservices/npuserservices.asmx HTTP/1.1 Host: localhost Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <GetUserID xmlns=" <ServiceKey>string</ServiceKey> <CustomerID>string</CustomerID> < >string</ > </GetUserID> </soap12:body> </soap12:envelope> HTTP/ OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <GetUserIDResponse xmlns=" <GetUserIDResult> <Message>string</Message> <ErrorCode>int</ErrorCode> <ReturnValue>string</ReturnValue> <Dataset> <xsd:schema>schema</xsd:schema>xml</dataset> </GetUserIDResult> </GetUserIDResponse> </soap12:body> </soap12:envelope> Northpointe Evolving Practice Through Scientific Innovation 7
9 Services Application LOGIN Sample of Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message /> <ErrorCode>0</ErrorCode> <ReturnValue>1</ReturnValue> </Response> Sample of Un-Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message>invalid </message> <ErrorCode>102</ErrorCode> <ReturnValue /> </Response> Northpointe Evolving Practice Through Scientific Innovation 8
10 SERVICES LIST REFERENCE CODES Overview The main purpose of this use case is to expose a web service that returns a dataset of all the reference codes by type. Measurable Result Reference code dataset is returned Flow of Events System will expose a web service method requiring specific parameters. Once web service is invoked the system will validate all parameters. System will then take parameters to return a reference code dataset. If parameter validation is not successful, the web service will return an error code. Web Service Name NPConfigurationServices.asmx Web Service Parameters Table 1: Parameter List Item Type Required ServiceKey String X Customer_ID String X Type_ID Integer X Northpointe Evolving Practice Through Scientific Innovation 9
11 Services List Reference Codes Table 2: Parameter Details Item Description Database/Table/Field ServiceKey Customer_ID Protected key that is required to invoke the web service Identifies the client Type_ID Indentifies what reference code type AppInfo Value Customer Rec_ID Web Service Return Upon successfully completion of procedure the web service will return the following string value. Type DataSet Description Dataset of all active agencies. Name and Rec_ID ErrorCode Default is 0 ReturnValue Message Default is an empty string Default is an empty string Web Service Error Codes If the system encounters an error, the web service will return an empty dataset with an error code and description. Format for error code is as follows: Error Code Description 100 Invalid Service Key 101 Invalid Customer_ID 102 Invalid Type_ID 103 No Codes Found for Type_ID 900 UnExpected Error Northpointe Evolving Practice Through Scientific Innovation 10
12 Services List Reference Codes Soap 1.2 Response and Request Schema The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values. POST /northpointeservices/npconfigurationservices.asmx HTTP/1.1 Host: localhost Content-Type: text/xml; charset=utf-8 Content-Length: length SOAPAction: " <?xml version="1.0" encoding="utf-8"?> <soap:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap=" <soap:body> <GetReferenceCodes xmlns=" <ServiceKey>string</ServiceKey> <Customer_ID>string</Customer_ID> <Type_ID>int</Type_ID> </GetReferenceCodes> </soap:body> </soap:envelope> HTTP/ OK Content-Type: text/xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap=" <soap:body> <GetReferenceCodesResponse xmlns=" <GetReferenceCodesResult> <Message>string</Message> <ErrorCode>int</ErrorCode> <ReturnValue>string</ReturnValue> <Dataset> <xsd:schema>schema</xsd:schema>xml</dataset> </GetReferenceCodesResult> </GetReferenceCodesResponse> </soap:body> </soap:envelope> Northpointe Evolving Practice Through Scientific Innovation 11
13 Services List Reference Codes Sample of Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message /> <ErrorCode>0</ErrorCode> <ReturnValue /> - <Dataset> - <xs:schema id="ref_code" xmlns="" xmlns:xs=" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> - <xs:element name="ref_code" msdata:isdataset="true" msdata:usecurrentlocale="true"> - <xs:complextype> - <xs:choice minoccurs="0" maxoccurs="unbounded"> - <xs:element name="ref_codes"> - <xs:complextype> - <xs:sequence> <xs:element name="text" type="xs:string" minoccurs="0" /> <xs:element name="refstring" type="xs:string" minoccurs="0" /> <xs:element name="order" type="xs:int" minoccurs="0" /> <xs:element name="isactive" type="xs:boolean" minoccurs="0" /> <xs:element name="islocked" type="xs:boolean" minoccurs="0" /> </xs:sequence> </xs:complextype> </xs:element> </xs:choice> </xs:complextype> </xs:element> </xs:schema> - <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1"> - <Ref_Code xmlns=""> - <Ref_Codes diffgr:id="ref_codes1" msdata:roworder="0" diffgr:haschanges="inserted"> <Text>General</Text> <RefString /> <Order>1</Order> <IsActive>true</IsActive> <IsLocked>true</IsLocked> </Ref_Codes> </Dataset> </Response> Northpointe Evolving Practice Through Scientific Innovation 12
14 Services List Reference Codes Sample of Un-Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message>no codes found for type_id</message> <ErrorCode>103</ErrorCode> <ReturnValue /> </Response> SERVICES STORE REFERENCE CODES Northpointe Evolving Practice Through Scientific Innovation 13
15 Overview The main purpose of this use case is to expose a web service that creates/update a reference code value. Measurable Result Record is created or updated Flow of Events System will expose a web service method, requiring specific parameters, to create or update a list of reference code. Once web service is invoked the system will validate all parameters. System will then use parameters to create/modify the records. If parameter validation is not successful, the web service will return an error code. Web Service Name NPConfigurationServices.asmx Web Service Parameters Table 1: Parameter List Item Type Required Service Key String X Customer_ID String X Type_ID Integer X RefCodeDataSet Dataset X Services Store Reference Codes Northpointe Evolving Practice Through Scientific Innovation 14
16 Table 2: Parameter Details Item Description Database/Table/Field Service Key Customer_ID Type_ID RefCodeDataSet Protected key that is required to invoke the web service Identifies the client Reference Code Dataset Schema Indentifies the Code Type trying to update codes for. Dataset of reference codes that need to be created or updated AppInfo Value Customer Rec_ID See List below See below Column Type Description Text String Text value of item Order Integer Order of which you want displayed RefString String Internal reference code used to uniquely identify code text IsDeleted Boolean Should this code be deleted? IsActive Boolean Is this code active? IsLocked Boolean <?xml version="1.0" standalone="yes"?> <Ref_Code> <Ref_Code> <Text>Example #1</Text> <RefString>REQ_NOTIF1</RefString > <Order>1</Order> <IsLocked>true</IsLocked> <IsActive>true</IsActive> <IsDeleted>false</IsDeleted> </Ref_Code> <Ref_Code> <Text>Example #2</Text> <RefString>REQ_NOTIF2</RefString > <Order>2</Order> <IsLocked>true</IsLocked> <IsActive>true</IsActive> <IsDeleted>false</IsDeleted> </Ref_Code> </Ref_Code> Services Store Reference Code Is this code locked and cannot be edited thru COMPAS? Northpointe Evolving Practice Through Scientific Innovation 15
17 Reference Code Types Name Type_ID Description Release Date Type Valid ID DAPO Notes Release Date Type Valid ID Veteran Status Highest Level of Education Completed Controlling Offenses Non-Controlling Offenses Static-99 Score Drug of Choice Drug Method of Use Alcohol use Relationship Gang Status Serious RVR Charge Source Documents in File TB Code Mental Health Screening Recommendation for Adaptive Support Indicated MDO Screening Indicated TABE Score TABE Per Hold/Warrants/Detainers Prior Serious Current Work Skills Voc Training Desired Veteran Status Highest level of education completed Controlling Offenses Non-Controlling Offenses Static 99 Score Drug of Choice Drug Method of Use Alcohol Use Relationship to the client Gang Status Serious RVR (CDC 115) Charge Source Documents in File TB Code Mental Health Screening Recommendation for Adaptive Support Indicated MDO Screening Indicated TABE Score TABE Per Holds, Warrants, Detainers Prior serious (PC & PC ) or Violent Current Work Skills Vocation Training Desired Services Store Reference Code Northpointe Evolving Practice Through Scientific Innovation 16
18 Web Service Return Upon successfully completion of procedure the web service will return the following string value. Type DataSet Description NULL ErrorCode Default is 0 ReturnValue Message User ID record of record created or updated Default is an empty string Web Service Error Codes If the system encounters an error the web service will return an error code and description. Format for error code is as follows: Error Code Description 100 Invalid Key 101 Invalid Customer_ID 102 Invalid Type_ID 103 Invalid RefCodeDataSet Schema - Text 104 Invalid RefCodeDataSet Schema - Order 105 Invalid RefCodeDataSet Schema - RefString 106 Invalid RefCodeDataSet Schema - IsDeleted 900 UnExpected Error SERVICES LIST AGENCIES Northpointe Evolving Practice Through Scientific Innovation 17
19 Overview The main purpose of this use case is to expose a web service that returns a dataset of all the active Agencies. Measurable Result Agency dataset is returned Flow of Events System will expose a web service method requiring specific parameters. Once web service is invoked the system will validate all parameters. System will then take parameters to return a agency dataset. If parameter validation is not successful, the web service will return an error code. Web Service Name NPConfigurationServices.asmx Web Service Parameters Table 1: Parameter List Item Type Required ServiceKey String X Customer_ID String X Table 2: Parameter Details Item Description Database/Table/Field ServiceKey Customer_ID Protected key that is required to invoke the web service Identifies the client AppInfo Value Customer Rec_ID Services List Agencies Northpointe Evolving Practice Through Scientific Innovation 18
20 Web Service Return Upon successfully completion of procedure the web service will return the following string value. Type DataSet Description Dataset of all active agencies. Name and Rec_ID ErrorCode Default is 0 ReturnValue Message Default is an empty string Default is an empty string Web Service Error Codes If the system encounters an error, the web service will return an empty dataset with an error code and description. Format for error code is as follows: Error Code Description 100 Invalid Service Key 101 Invalid Customer_ID 102 Invalid Application_ID 103 No Active Agencies 900 UnExpected Error Services List Agencies Northpointe Evolving Practice Through Scientific Innovation 19
21 Soap 1.2 Response and Request Schema The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values. POST /northpointeservices/npconfigurationservices.asmx HTTP/1.1 Host: localhost Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <GetAgencies xmlns=" <ServiceKey>string</ServiceKey> <Customer_ID>string</Customer_ID> </GetAgencies> </soap12:body> </soap12:envelope> HTTP/ OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <GetAgenciesResponse xmlns=" <GetAgenciesResult> <Message>string</Message> <Dataset> <xsd:schema>schema</xsd:schema>xml</dataset> <ErrorCode>int</ErrorCode> <ReturnValue>string</ReturnValue> </GetAgenciesResult> </GetAgenciesResponse> </soap12:body> </soap12:envelope> Northpointe Evolving Practice Through Scientific Innovation 20
22 Services List Agencies Sample of Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message /> <ErrorCode>0</ErrorCode> <ReturnValue /> - <Dataset> - <xs:schema id="agency" xmlns="" xmlns:xs=" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> - <xs:element name="agency" msdata:isdataset="true" msdata:usecurrentlocale="true"> - <xs:complextype> - <xs:choice minoccurs="0" maxoccurs="unbounded"> - <xs:element name="agencies"> - <xs:complextype> - <xs:sequence> <xs:element name="rec_id" type="xs:int" minoccurs="0" /> <xs:element name="customer_id" type="xs:string" minoccurs="0" /> <xs:element name="name" type="xs:string" minoccurs="0" /> <xs:element name="description" type="xs:string" minoccurs="0" /> <xs:element name="isactive" type="xs:boolean" minoccurs="0" /> <xs:element name="isdeleted" type="xs:boolean" minoccurs="0" /> <xs:element name="ishidden" type="xs:boolean" minoccurs="0" /> </xs:sequence> </xs:complextype> </xs:element> </xs:choice> </xs:complextype> </xs:element> </xs:schema> - <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1"> - <Agency xmlns=""> - <Agencies diffgr:id="agencies1" msdata:roworder="0" diffgr:haschanges="inserted"> <Rec_ID>8</Rec_ID> <Customer_ID>e254c4df486e430bb4278c3c9b59d4c0</Customer_ID> <Name>Test Agency</Name> <Description>Test Agency Description</Description> <IsActive>true</IsActive> <IsDeleted>false</IsDeleted> <IsHidden>false</IsHidden> </Agencies> - <Agencies diffgr:id="agencies2" msdata:roworder="1" diffgr:haschanges="inserted"> <Rec_ID>1</Rec_ID> <Customer_ID>e254c4df486e430bb4278c3c9b59d4c0</Customer_ID> <Name>Test Agency 1</Name> <Description>Test Agency 1</Description> Northpointe Evolving Practice Through Scientific Innovation 21
23 Services List Agencies <IsActive>true</IsActive> <IsDeleted>false</IsDeleted> <IsHidden>false</IsHidden> </Agencies> - <Agencies diffgr:id="agencies3" msdata:roworder="2" diffgr:haschanges="inserted"> <Rec_ID>4</Rec_ID> <Customer_ID>e254c4df486e430bb4278c3c9b59d4c0</Customer_ID> <Name>Test Agency 2</Name> <Description>Test Agency 2</Description> <IsActive>true</IsActive> <IsDeleted>false</IsDeleted> <IsHidden>false</IsHidden> </Agencies> </Agency> </diffgr:diffgram> </Dataset> </Response> Sample of Un-Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message>Invalid service key.</message> <ErrorCode>100</ErrorCode> <ReturnValue /> </Response> Northpointe Evolving Practice Through Scientific Innovation 22
24 SERVICES GET AGENCY ID Overview The main purpose of this use case is to expose a web service that returns an ID for a agency record by agency name. Measurable Result Agency ID is returned Flow of Events System will expose a web service method requiring specific parameters. Once web service is invoked the system will validate all parameters. System will then take parameters to return an Agency ID. If parameter validation is not successful, the web service will return an error code. Web Service Name NPConfigurationServices.asmx Web Service Parameters Table 1: Parameter List Item Type Required Service Key String X Customer_ID String X AgencyName String X Table 2: Parameter Details Item Description Database/Table/Field Service Key Customer_ID Protected key that is required to invoke the web service Identifies the client AppInfo Value Customer Rec_ID AgencyName Services Get Agency ID Name of Agency Northpointe Evolving Practice Through Scientific Innovation 23
25 Web Service Return Upon successfully completion of procedure the web service will return the following string value. Type DataSet Description NULL ErrorCode Default is 0 ReturnValue Message Agency ID Default is an empty string Web Service Error Codes If the system encounters an error, the web service will return an error code and description. Format for error code is as follows: Error Code Description 100 Invalid Key 101 Invalid Customer_ID 102 Invalid Application_ID 103 Invalid Agency Name 104 Agency is not active 900 UnExpected Error Northpointe Evolving Practice Through Scientific Innovation 24
26 Services Get Agency ID Soap 1.2 Response and Request Schema The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values. POST /northpointeservices/npconfigurationservices.asmx HTTP/1.1 Host: localhost Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <GetAgencyID xmlns=" <ServiceKey>string</ServiceKey> <Customer_ID>string</Customer_ID> <AgencyName>string</AgencyName> </GetAgencyID> </soap12:body> </soap12:envelope> HTTP/ OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <GetAgencyIDResponse xmlns=" <GetAgencyIDResult> <Message>string</Message> <ErrorCode>int</ErrorCode> <ReturnValue>string</ReturnValue> <Dataset> <xsd:schema>schema</xsd:schema>xml</dataset> </GetAgencyIDResult> </GetAgencyIDResponse> </soap12:body> </soap12:envelope> Northpointe Evolving Practice Through Scientific Innovation 25
27 Services Get Agency ID Sample of Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message /> <ErrorCode>0</ErrorCode> <ReturnValue>23</ReturnValue> </Response> Sample of Un-Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message>invalid agency</message> <ErrorCode>102</ErrorCode> <ReturnValue /> </Response> Northpointe Evolving Practice Through Scientific Innovation 26
28 SERVICES LIST SECURITY GROUPS Overview The main purpose of this use case is to expose a web service that returns a dataset of all the active security groups Measurable Result Security group dataset is returned Flow of Events System will expose a web service method requiring specific parameters. Once web service is invoked the system will validate all parameters. System will then take parameters to return a security group dataset. If parameter validation is not successful, the web service will return an error code. Web Service Name NPConfigurationServices.asmx Web Service Parameters Table 1: Parameter List Item Type Required Service Key String X Customer_ID String X Application_ID Integer X Services List Security Groups Northpointe Evolving Practice Through Scientific Innovation 27
29 Table 2: Parameter Details Item Description Database/Table/Field Service Key Customer_ID Application_ID Web Service Return Protected key that is required to invoke the web service Identifies the client Identifies the application trying to login to AppInfo Value Customer Rec_ID Sys_Application Rec_ID Upon successfully completion of procedure the web service will return the following string value. Type DataSet Description Dataset of all active security groups. Name and Rec_ID ErrorCode Default is 0 ReturnValue Message Default is an empty string Default is an empty string Web Service Error Codes If the system encounters an error, the web service will return an empty dataset with an error code and description. Format for error code is as follows: Error Code Description 100 Invalid Key 101 Invalid Customer_ID 102 Invalid Application_ID 103 No Active Security Groups 900 UnExpected Error Services List Security Groups Northpointe Evolving Practice Through Scientific Innovation 28
30 Soap 1.2 Response and Request Schema POST /northpointeservices/npconfigurationservices.asmx HTTP/1.1 Host: localhost Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <GetGroups xmlns=" <ServiceKey>string</ServiceKey> <Customer_ID>string</Customer_ID> <Application_ID>int</Application_ID> </GetGroups> </soap12:body> </soap12:envelope> HTTP/ OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <GetGroupsResponse xmlns=" <GetGroupsResult> <Message>string</Message> <ErrorCode>int</ErrorCode> <ReturnValue>string</ReturnValue> <Dataset> <xsd:schema>schema</xsd:schema>xml</dataset> </GetGroupsResult> </GetGroupsResponse> </soap12:body> </soap12:envelope> Northpointe Evolving Practice Through Scientific Innovation 29
31 Services List Security Groups Sample of Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message /> <ErrorCode>0</ErrorCode> <ReturnValue /> - <Dataset> - <xs:schema id="group" xmlns="" xmlns:xs=" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> - <xs:element name="group" msdata:isdataset="true" msdata:usecurrentlocale="true"> - <xs:complextype> - <xs:choice minoccurs="0" maxoccurs="unbounded"> - <xs:element name="groups"> - <xs:complextype> - <xs:sequence> <xs:element name="rec_id" type="xs:int" minoccurs="0" /> <xs:element name="name" type="xs:string" minoccurs="0" /> <xs:element name="description" type="xs:string" minoccurs="0" /> <xs:element name="ranking" type="xs:int" minoccurs="0" /> <xs:element name="isglobal" type="xs:boolean" minoccurs="0" /> <xs:element name="isactive" type="xs:boolean" minoccurs="0" /> <xs:element name="isdeleted" type="xs:boolean" minoccurs="0" /> </xs:sequence> </xs:complextype> </xs:element> </xs:choice> </xs:complextype> </xs:element> </xs:schema> - <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1"> - <Group xmlns=""> - <Groups diffgr:id="groups1" msdata:roworder="0" diffgr:haschanges="inserted"> <Rec_ID>1</Rec_ID> <Name>Global Adminstrator</Name> <Description>Global Adminstrator</Description> <Ranking>0</Ranking> <IsGlobal>false</IsGlobal> <IsActive>true</IsActive> <IsDeleted>false</IsDeleted> </Groups> - <Groups diffgr:id="groups2" msdata:roworder="1" diffgr:haschanges="inserted"> <Rec_ID>2</Rec_ID> <Name>Site Administrator</Name> <Description>Site Administrator</Description> Northpointe Evolving Practice Through Scientific Innovation 30
32 Services List Security Groups <Ranking>1</Ranking> <IsGlobal>false</IsGlobal> <IsActive>true</IsActive> <IsDeleted>false</IsDeleted> </Groups> - <Groups diffgr:id="groups3" msdata:roworder="2" diffgr:haschanges="inserted"> <Rec_ID>5</Rec_ID> <Name>Power Users</Name> <Description>Powers Users</Description> <Ranking>2</Ranking> <IsGlobal>false</IsGlobal> <IsActive>true</IsActive> <IsDeleted>false</IsDeleted> </Groups> - <Groups diffgr:id="groups4" msdata:roworder="3" diffgr:haschanges="inserted"> <Rec_ID>19</Rec_ID> <Name>Test Group</Name> <Description>Test Group</Description> <Ranking>1</Ranking> <IsGlobal>false</IsGlobal> <IsActive>true</IsActive> <IsDeleted>false</IsDeleted> </Groups> </Group> </diffgr:diffgram> </Dataset> </Response> Sample of Un-Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message>invalid application id</message> <ErrorCode>102</ErrorCode> <ReturnValue /> </Response> Northpointe Evolving Practice Through Scientific Innovation 31
33 SERVICES GET SECURITY GROUP ID Overview The main purpose of this use case is to expose a web service that returns an ID for a group record by group name. Measurable Result Security group id is returned Flow of Events System will expose a web service method requiring specific parameters. Once web service is invoked the system will validate all parameters. System will then take parameters to return a security group id. If parameter validation is not successful, the web service will return an error code. Web Service Name NPConfigurationServices.asmx Web Service Parameters Table 1: Parameter List Item Type Required Service Key String X Customer_ID String X Application_ID Integer X GroupName String X Services Get Security Group ID Northpointe Evolving Practice Through Scientific Innovation 32
34 Table 2: Parameter Details Item Description Database/Table/Field Service Key Customer_ID Application_ID Protected key that is required to invoke the web service Identifies the client Identifies the application trying to login to AppInfo Value Customer Rec_ID Sys_Application Rec_ID GroupName Name of the security group Web Service Return Upon successfully completion of procedure the web service will return the following string value. Type DataSet Description NULL ErrorCode Default is 0 ReturnValue Message Requested Security Group ID Default is an empty string Services Get Security Group ID Northpointe Evolving Practice Through Scientific Innovation 33
35 Web Service Error Codes If the system encounters an error, the web service will return an error code and description. Format for error code is as follows: Error Code Description 100 Invalid Service Key 101 Invalid Customer_ID 102 Invalid Application_ID 103 Invalid Group Name 104 Group Name is not active 900 UnExpected Error Soap 1.2 Response and Request Schema The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values. POST /northpointeservices/npconfigurationservices.asmx HTTP/1.1 Host: localhost Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <GetGroupID xmlns=" <ServiceKey>string</ServiceKey> <Customer_ID>string</Customer_ID> <Application_ID>int</Application_ID> <GroupName>string</GroupName> </GetGroupID> </soap12:body> </soap12:envelope> Services Get Security Group ID Northpointe Evolving Practice Through Scientific Innovation 34
36 HTTP/ OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <GetGroupIDResponse xmlns=" <GetGroupIDResult> <Message>string</Message> <ErrorCode>int</ErrorCode> <ReturnValue>string</ReturnValue> <Dataset> <xsd:schema>schema</xsd:schema>xml</dataset> </GetGroupIDResult> </GetGroupIDResponse> </soap12:body> </soap12:envelope> Northpointe Evolving Practice Through Scientific Innovation 35
37 Services Get Security Group ID Sample of Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message /> <ErrorCode>0</ErrorCode> <ReturnValue>5</ReturnValue> </Response> Sample of Un-Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message>invalid group name</message> <ErrorCode>103</ErrorCode> <ReturnValue /> </Response> Northpointe Evolving Practice Through Scientific Innovation 36
38 SERVICES GET USER ID Overview The main purpose of this use case is to expose a web service that returns an ID for a user record by a username or address. Measurable Result User id is returned Flow of Events System will expose a web service method requiring specific parameters. Once web service is invoked the system will validate all parameters. System will then take parameters to return a security group id. If parameter validation is not successful, the web service will return an error code. Web Service Name NPuserServices.asmx Web Service Parameters Table 1: Parameter List Item Type Required Key String X Customer_ID String X String X Northpointe Evolving Practice Through Scientific Innovation 37
39 Services Get User ID Table 2: Parameter Details Item Description Database/Table/Field Key Customer_ID Protected key that is required to invoke the web service Identifies the client AppInfo Value Customer Rec_ID Users address Web Service Return Upon successfully completion of procedure the web service will return the following string value. Type DataSet Description NULL ErrorCode Default is 0 ReturnValue Message Requested User ID Default is an empty string Northpointe Evolving Practice Through Scientific Innovation 38
40 Services Get User ID Web Service Error Codes If the system encounters an error, the web service will return an error code and description. Format for error code is as follows: Error Code Description 100 Invalid Key 101 Invalid Customer_ID 102 Invalid Address 103 Account is not active 104 Account has been deleted 900 UnExpected Error Northpointe Evolving Practice Through Scientific Innovation 39
41 Services Get User ID Soap 1.2 Response and Request Schema The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values. POST /northpointeservices/npuserservices.asmx HTTP/1.1 Host: localhost Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <LoginUser xmlns=" <ServiceKey>string</ServiceKey> <Customer_ID>string</Customer_ID> <Application_ID>int</Application_ID> < >string</ > <Password>string</Password> <IsPasswordEncrypted>boolean</IsPasswordEncrypted> <RedirectToPage>string</RedirectToPage> </LoginUser> </soap12:body> </soap12:envelope> HTTP/ OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <LoginUserResponse xmlns=" <LoginUserResult> <Message>string</Message> <ErrorCode>int</ErrorCode> <ReturnValue>string</ReturnValue> <Dataset> <xsd:schema>schema</xsd:schema>xml</dataset> </LoginUserResult> </LoginUserResponse> </soap12:body> </soap12:envelope> Northpointe Evolving Practice Through Scientific Innovation 40
42 Services Get User ID Sample of Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message /> <ErrorCode>0</ErrorCode> <ReturnValue> sqqjmsghe61siye8cgfnbjlfsg1k3l6qbsnagqmwaqbst0tawa%3d&page=home.as px</returnvalue> </Response> Sample of Un-Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message>invalid login credentials</message> <ErrorCode>103</ErrorCode> <ReturnValue /> </Response> Northpointe Evolving Practice Through Scientific Innovation 41
43 SERVICES STORE USER Overview The main purpose of this use case is to expose a web service that stores a user record. Measurable Result User record is saved Flow of Events System will expose a web service method, requiring specific parameters, to create a new user record. Once web service is invoked the system will validate all parameters. System will then use parameters to create a new user. If parameter validation is not successful, the web service will return an error code. If address already exists, the system will update the offender attached to the specific address. If username already exists, the system will update the offender attached to the specific username. Web Service Name NPUserServices.asmx Web Service Parameters Table 1: Parameter List Item Type Required Service Key String X Customer_ID String X Application_ID Integer X CreatedBy_User_ID Integer X Agency String X Services Store User Northpointe Evolving Practice Through Scientific Innovation 42
44 Table 1: Parameter List - continued Item Type Required FirstName String X LastName String X MiddleInitial String String X UserName String X Password String X Group_ID Integer X IsConfAdmin Boolean X IsScreener Boolean X Table 2: Parameter Details Item Description Database/Table/Field Service Key Customer_ID Application_ID CreatedBy_User_ID Agency Services Store User Protected key that is required to invoke the web service Identifies the client Identifies the application the user belongs too ID of user creating the user Agency the user is located at AppInfo Value Customer Rec_ID Sys_Application Rec_ID User Rec_ID Agency Name Northpointe Evolving Practice Through Scientific Innovation 43
45 Table 2: Parameter Details - continued Item Description Database/Table/Field FirstName First name of user LastName MiddleInitial Last Name of user Middle Initial of user address of user UserName Username of User * Password Group_ID IsConfAdmin IsScreener Password for user Security group that user will belong too Is this user a high level system administrator Is this user a screener Group Rec_ID * address replaces username in all suite products Web Service Return Upon successfully completion of procedure the web service will return the following string value. Type DataSet Description NULL ErrorCode Default is 0 ReturnValue Message User ID record of record created or updated Default is an empty string Northpointe Evolving Practice Through Scientific Innovation 44
46 Services Store User Web Service Error Codes If the system encounters an error the web service will return an error code and description. Format for error code is as follows: Error Code Description 100 Invalid Key 101 Invalid Customer_ID 102 Invalid Application_ID 103 Invalid CreatedBy_User_ID 104 Invalid Agency 105 Invalid 106 Invalid Password Length, Minimum of 6 characters 107 Invalid Group ID 900 UnExpected Error Northpointe Evolving Practice Through Scientific Innovation 45
47 Services Store User Soap 1.2 Response and Request Schema The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values. POST /northpointeservices/npuserservices.asmx HTTP/1.1 Host: localhost Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <StoreUser xmlns=" <ServiceKey>string</ServiceKey> <Customer_ID>string</Customer_ID> <Application_ID>int</Application_ID> <CreatedBy_User_ID>int</CreatedBy_User_ID> <Agency_ID>int</Agency_ID> <FirstName>string</FirstName> <LastName>string</LastName> <MiddleInitial>string</MiddleInitial> < >string</ > <Password>string</Password> <Group_ID>int</Group_ID> <IsScreener>boolean</IsScreener> </StoreUser> </soap12:body> </soap12:envelope> HTTP/ OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <StoreUserResponse xmlns=" <StoreUserResult> <Message>string</Message> <ErrorCode>int</ErrorCode> <ReturnValue>string</ReturnValue> <Dataset> <xsd:schema>schema</xsd:schema>xml</dataset> </StoreUserResult> </StoreUserResponse> </soap12:body> </soap12:envelope> Northpointe Evolving Practice Through Scientific Innovation 46
48 Services Store User Sample of Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message /> <ErrorCode>0</ErrorCode> <ReturnValue>4561</ReturnValue> </Response> Sample of Un-Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message>invalid password length</message> <ErrorCode>102</ErrorCode> <ReturnValue /> </Response> Northpointe Evolving Practice Through Scientific Innovation 47
49 Services Store Offender Overview The main purpose of this use case is to expose a web service that stores an offender record. Measurable Result Offender record is stored Flow of Events System will expose a web service method requiring specific parameters. Once web service is invoked the system will validate all parameters. System will then take parameters to create a new offender. If parameter validation is not successful, the web service will return an error code. If offender number already exists, the system will update the offender attached to the specific offender number. Web Service Name NPOffenderServices.asmx Web Service Parameters Table 1: Parameter List Item Type Required Service Key String X Customer_ID String X Application_ID Integer X CreatedBy_User_ID Integer X Agency String X FirstName String X LastName String X MiddleName String OffenderNumber String X AltOffenderNumber String DateOfBirth String X Ethnicity String X Gender String X SSN String Northpointe Evolving Practice Through Scientific Innovation 48
50 Services Store Offender Table 2: Parameter Details Item Description Database/Table/Field Service Key Customer_ID Application_ID CreatedBy_User_ID Agency Protected key that is required to invoke the web service Identifies the client Identifies the application trying to login to ID of user creating the offender Agency offender is located at AppInfo Value Customer Rec_ID Sys_Application Rec_ID User Rec_ID Agency Name FirstName LastName MiddleName OffenderNumber AltOffenderNumber DateOfBirth Ethnicity Gender SSN First Name of Offender Last Name of Offender Middle Name of Offender Offender Number (CDC) Alternate Offender Number Date of Birth of Offender Ethnicity of Offender Gender of Offender Social Security Number of Offender Sys_Code Text Sys_Code Text Northpointe Evolving Practice Through Scientific Innovation 49
51 Services Store Offender Web Service Return Upon successfully completion of procedure the web service will return the following string value. Type DataSet Description NULL ErrorCode Default is 0 ReturnValue Message Offender ID created or edited Default is an empty string Web Service Error Codes If the system encounters an error, the web service will return an error code and description. Format for error code is as follows: Error Code Description 100 Invalid Key 101 Invalid Customer_ID 102 Invalid Application_ID 103 Invalid CreatedBy_User_ID 104 Invalid Agency 105 Offender Number already exists 106 Invalid Date of Birth 107 Invalid Ethnicity 108 Invalid Gender 109 Invalid Social Security Number 110 Social Security Number already exists 900 UnExpected Error Northpointe Evolving Practice Through Scientific Innovation 50
52 Services Store Offender Soap 1.2 Response and Request Schema The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values. POST /northpointeservices/npoffenderservices.asmx HTTP/1.1 Host: localhost Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <StoreReEntrytOffender xmlns=" <ServiceKey>string</ServiceKey> <Customer_ID>string</Customer_ID> <Application_ID>int</Application_ID> <CreatedBy_User_ID>int</CreatedBy_User_ID> <AgencyName>string</AgencyName> <FirstName>string</FirstName> <LastName>string</LastName> <MiddleName>string</MiddleName> <OffenderNumber>string</OffenderNumber> <AltOffenderNumber>string</AltOffenderNumber> <DateOfBirth>string</DateOfBirth> <Ethnicity>string</Ethnicity> <Gender>string</Gender> <SSN>string</SSN> </StoreReEntrytOffender> </soap12:body> </soap12:envelope> HTTP/ OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap12=" <soap12:body> <StoreReEntrytOffenderResponse xmlns=" <StoreReEntrytOffenderResult> <Message>string</Message> <ErrorCode>int</ErrorCode> <ReturnValue>string</ReturnValue> <Dataset> <xsd:schema>schema</xsd:schema>xml</dataset> </StoreReEntrytOffenderResult> </StoreReEntrytOffenderResponse> </soap12:body> </soap12:envelope> Northpointe Evolving Practice Through Scientific Innovation 51
53 Services Store Offender Sample of Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message /> <ErrorCode>0</ErrorCode> <ReturnValue>1009</ReturnValue> </Response> Sample of Un-Successful Invoke <?xml version="1.0" encoding="utf-8"?> - <Response xmlns:xsi=" xmlns:xsd=" xmlns=" <Message>invalid application id</message> <ErrorCode>102</ErrorCode> <ReturnValue /> </Response> Northpointe Evolving Practice Through Scientific Innovation 52
NO: 22/15(1)/ /DCH/DHDS/Machinery Government of India Ministry of Textiles Office of the Development Commissioner for Handlooms **** ADDENDUM
NO: 22/15(1)/2014-15/DCH/DHDS/Machinery Government of India Ministry of Textiles Office of the Development Commissioner for Handlooms **** ADDENDUM Udyog Bhavan, New Delhi Dated: 27.10.2014 Subject: -
More informationTWW UNIMESSAGE. Volume SMS Messaging. Web services Integration Guide ( Version 3.09 )
TWW UNIMESSAGE Volume SMS Messaging Web services Integration Guide ( Version 3.09 ) 1 TWW UNIMESSAGE Volume SMS Messaging WEBSERVICES Integration Guide Information in this document, or in the described
More informationDynmark Messaging Platform XML HTTP Interface Quick Start Guide. Draft Revision September
Dynmark Messaging Platform XML HTTP Interface Quick Start Guide Draft Revision 3.0.5 4 September 2006 E-mail: support@e-txt.co.uk CONTENTS Sending Messages... 3 Sending a Simple Message...3 Text Merge
More information[MS-DSDIFFGRAM]: SharePoint Web Services: DataSet DiffGram Structure
[MS-DSDIFFGRAM]: SharePoint Web Services: DataSet DiffGram Structure Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications
More information[MS-DSDIFFGRAM]: SharePoint Web Services: DataSet DiffGram Structure Specification
[MS-DSDIFFGRAM]: SharePoint Web Services: DataSet DiffGram Structure Specification Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes
More informationIHS Haystack Web Services Quick Start Guide April 2014
IHS Haystack Web Services Quick Start Guide April 2014 Table of Contents: Overview Methods GetFLISBriefResultsByCAGECodeAndPartNumber GetFLISBriefResultsByPartNumber GetFLISSummaryResultsByMultipleNIINs
More informationNotes. Any feedback/suggestions? IS 651: Distributed Systems
Notes Grading statistics Midterm1: average 10.60 out of 15 with stdev 2.22 Total: average 15.46 out of 21 with stdev 2.80 A range: [18.26, 23] B range: [12.66, 18.26) C or worse range: [0, 12.66) The curve
More informationIntroduction BB4 Web Services specifications... 5
Billy Blue s 4 Web Service API Guide rel. 1.1 07-07-2010 Summary Introduction... 4 Monitor, share, inform.... 4 BB4 web services... 4 Web Service data format... 4 How to use Web Service di BB4... 4 Use
More informationKOSTAS MARKELLOS University of Patras, Computer Engineering and Informatics Department, University Campus, 26500, Rio, Greece
USING STANDARDISED WEB SERVICES FOR INTEGRATING PROCESSES OF AUTONOMOUS ACTORS COMMUNICATING WITHIN A PUBLIC INFORMATION SYSTEM - A CASE STUDY FROM GREECE KOSTAS MARKELLOS University of Patras, Computer
More informationSharePoint Web Services: DataSet DiffGram Structure
[MS-DSDIFFGRAM-Diff]: Intellectual Property Rights tice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats,
More informationWMH API Documentation. Contents
WMH API Documentation Contents WMH API Documentation... 1 Terms... 2 Questions... 3 Functions... 4 GetAvailableInventory... 4 GetAvailableInventoryXML... 4 GetPricing... 4 GetPricingXML... 4 GetProductInfo...
More informationOracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On
Oracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On Configuration Guide E84772-01 Last Update: Monday, October 09, 2017 Oracle Utilities Opower Energy Efficiency Web Portal -
More informationTWS Toolkit V2.1 Developer s Manual
2002 Algoria. TWS (Telephony Web Services), and related modules and products, is a registered trademark from Algoria TWS Toolkit V2.1 Developer s Manual Juillet 2007 Contact and Support : Algoria Adress
More informationSPARROW Gateway. Developer API. Version (Build 7373)
SPARROW Gateway Developer API Version 3.2.0 (Build 7373) Released September 2016 Revision History Date Revision Comments Author 2016 02 26 2.0 Initial document created Alexandra Blinova 2 Table of Contents
More informationGoToMyPC Reporting Services API
GoToMyPC Reporting Services API Developer s Guide Version 1.2 Last Updated: March 8, 2013 Contents Overview of GoToMyPC API Offerings... 1 GoToMyPC Reporting API Overview... 1 Benefits... 1 Example Implementations...
More informationOracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1. September 2017
Oracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1 September 2017 Copyright 1987, 2017, Oracle and/or its affiliates. All rights reserved. This software and related
More informationSPARROW Gateway. Custom Payment Redirect. Version (Build 7373)
SPARROW Gateway Custom Payment Redirect Version 3.2.0 (Build 7373) Released September 2016 Revision History Date Revision Comments Author 2015 06 09 1.0 Initial document created Blinova Alexandra 2 Table
More informationFax Broadcast Web Services
Fax Broadcast Web Services Table of Contents WEB SERVICES PRIMER... 1 WEB SERVICES... 1 WEB METHODS... 1 SOAP ENCAPSULATION... 1 DOCUMENT/LITERAL FORMAT... 1 URL ENCODING... 1 SECURE POSTING... 1 FAX BROADCAST
More informationValidation Language. GeoConnections Victoria, BC, Canada
Validation Language Submitted To: Program Manager GeoConnections Victoria, BC, Canada Submitted By: Jody Garnett Brent Owens Refractions Research Inc. Suite 400, 1207 Douglas Street Victoria, BC, V8W-2E7
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWMT]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationIntroduction Syntax and Usage XML Databases Java Tutorial XML. November 5, 2008 XML
Introduction Syntax and Usage Databases Java Tutorial November 5, 2008 Introduction Syntax and Usage Databases Java Tutorial Outline 1 Introduction 2 Syntax and Usage Syntax Well Formed and Valid Displaying
More informationiats Payments AuraLink Web Services
AuraLink Web Services Version 5.1 Last Updated January 18 th, 2016 iats AURALink Web Services This guide provides an explanation of iats AURALink Web services, how they work, and how to set them up. Our
More informationWeb Service Architecture for Computer-Adaptive Testing on e-learning
Web Service Architecture for Computer-Adaptive Testing on e-learning M. Phankokkruad, K. Woraratpanya Abstract This paper proposes a Web service and serviceoriented architecture (SOA) for a computer-adaptive
More informationXML / HTTP(s) NETIO M2M API protocols docs
XML / HTTP(s) NETIO M2M API protocols docs Protocol version: XML Version 2.0 Short summary XML / HTTP(s) protocol is a file-based M2M API protocol, where the NETIO device is a HTTP(s) server and the client
More information[MS-OXWMT]: Mail Tips Web Service Extensions. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWMT]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationNetworks and Services (NETW-903)
Networks and Services (NETW-903) Dr. Mohamed Abdelwahab Saleh IET-Networks, GUC Fall 2018 Table of Contents 1 XML Namespaces 2 XML Schema 3 The SOAP Protocol and RPC 4 SOAP Messages Name Conflicts A name
More informationWhite Paper. Fabasoft Integration for Novell GroupWise. Fabasoft Folio 2017 R1 Update Rollup 1
White Paper Fabasoft Integration for Novell GroupWise Fabasoft Folio 2017 R1 Update Rollup 1 Copyright Fabasoft R&D GmbH, Linz, Austria, 2018. All rights reserved. All hardware and software names used
More informationSOA Suite for healthcare integration Series
Oracle SOA Suite 11g R1 PS5 SOA Suite for healthcare integration Series Exception Handling - Processing Endpoint Errors michael@czapski.id.au January 2013 Table of Contents Introduction... 1 Solution Overview...
More informationXML and Web Services
XML and Web Services Lecture 8 1 XML (Section 17) Outline XML syntax, semistructured data Document Type Definitions (DTDs) XML Schema Introduction to XML based Web Services 2 Additional Readings on XML
More informationOracle Communications Network Charging and Control. Web Services Description Language Reference Guide Release 6.0.1
Oracle Communications Network Charging and Control Web Services Description Language Reference Guide Release 6.0.1 April 2017 Copyright Copyright 2017, Oracle and/or its affiliates. All rights reserved.
More informationPTC Integrity 10.7 Web Services Reference
PTC Integrity 10.7 Web Services Reference PTC Integrity 10.7 Web Services Reference Copyright 2015 PTC Inc. and/or Its Subsidiary Companies. All Rights Reserved. User and training guides and related documentation
More informationMWTM 6.1 NBAPI WSDL and XSD Definitions
APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM 6.1 Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-5 ProvisionAPI.wsdl, page
More informationNetwork Configuration Protocol
The (NETCONF) defines a simple mechanism through which a network device can be managed, configuration data can be retrieved, and new configuration data can be uploaded and manipulated. NETCONF uses Extensible
More informationilinc 10 Web Services
ilinc 10 Web Services Version 1.8 ilinc is a trademark of ilinc Communications, Inc.. All rights reserved. Page 1 of 103 Table of Contents Table of Contents... 2 SOAP Web Service Introduction... 4 Web
More information[MS-EDCSOM]: Intellectual Property Rights Notice for Open Specifications Documentation
[MS-EDCSOM]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-SSDPWP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationMain title goes here EDT Hub API Specification v2.9
Main title goes here EDT Hub API Specification v2.9 Prepared by: Philip Young, PCTI IS2 Folder: Internal\Technical\Products\EDT Date: Monday, 24 September 2007 Revision No: 2.9 (EDT Hub version 800800
More informationOracle B2B 11g Technical Note. Technical Note: 11g_005 Attachments. Table of Contents
Oracle B2B 11g Technical Note Technical Note: 11g_005 Attachments This technical note lists the attachment capabilities available in Oracle B2B Table of Contents Overview... 2 Setup for Fabric... 2 Setup
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSXPROP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationINSURER BATCH UPLOAD GUIDE NORTH CAROLINA SURPLUS LINES ASSOCIATION
INSURER BATCH UPLOAD GUIDE NORTH CAROLINA SURPLUS LINES ASSOCIATION TABLE OF CONTENTS 1 Document Metadata... 4 1.1 Authors... 4 1.2 Intended Audience... 4 1.3 Glossary of Terms and Acronyms... 4 1.4 Document
More informationPreliminary. Database Publishing Wizard Protocol Specification
[MS-SSDPWP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationAlwaysUp Web Service API Version 11.0
AlwaysUp Web Service API Version 11.0 0. Version History... 2 1. Overview... 3 2. Operations... 4 2.1. Common Topics... 4 2.1.1. Authentication... 4 2.1.2. Error Handling... 4 2.2. Get Application Status...
More informationPublications Office. TED Website - Notice Viewer WS Technical Specifications Document - Appendix D - NoticeViewer
Publications Office Subject NoticeViewer WS API Version / Status 1.03 Release Date 17/02/2017 Filename Document Reference TED_WEBSITE-TSP-Technical_Specifications_Document-v1.03 TED-TSP-Appendix D Table
More informationTest Cases - VBS Stack Run In. Web Service Test Cases - VBS Stack Run In
Test Cases - VBS Stack Run In Web Service Test Cases - VBS Stack Run In Contents 1 Introduction... 4 2 Scope... 4 3 Data Requirements... 4 4 Integration Overview... 4 5 Test Environment... 5 5.1 1-Stop
More informationCisco CallManager 4.1(2) AXL Serviceability API Programming Guide
Cisco CallManager 4.1(2) AXL Serviceability API Programming Guide This document describes the implementation of AXL-Serviceability APIs that are based on version 3.3.0.1 or higher. Cisco CallManager Real-Time
More informationMWTM NBAPI WSDL and XSD Definitions
APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM 6.1.4 Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-10 ProvisionAPI.wsdl, page
More informationMailtips Extensions to Web Service Protocol Specification
[MS-OXWMT]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationSuccessMaker Data Services API Guide
SuccessMaker 7.0.1 Data Services API Guide Document last updated August 2014 Copyright 2011 2014 Pearson Education, Inc. or one or more of its direct or indirect affiliates. All rights reserved. Pearson
More informationMessages are securely encrypted using HTTPS. HTTPS is the most commonly used secure method of exchanging data among web browsers.
May 6, 2009 9:39 SIF Specifications SIF Implementation Specification The SIF Implementation Specification is based on the World Wide Web Consortium (W3C) endorsed Extensible Markup Language (XML) which
More informationSMSCenter. SMSCenter API
www.smscenter.co.il SMSCenter Multi Messaging Software Server SMS / MMS / IVR / WAP Push SMSCenter API SMSCenter API The software described in this book is furnished under a license agreement and may be
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSXPROP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More information[MS-OXWSBTRF]: Bulk Transfer Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWSBTRF]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationUser Manual. HIPAA Transactions System Integration for Channel Partner Vendor. Version 15.2 May 2015
User Manual HIPAA Transactions System Integration for Channel Partner Vendor Version 15.2 May 2015 Trademarks and Copyrights Optum HIPAA Transactions System Integration Document Channel Partner Vendor
More information[MS-RDWR]: Remote Desktop Workspace Runtime Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-RDWR]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationHP Service Manager Software
HP Service Manager Software For the Windows and Unix Operating Systems Software version 9.20 Web Services Tailoring Guide Document Release Date: June 2010 Software Release Date: June 2010 Legal Notices
More information[MS-OXWSSYNC]: Mailbox Contents Synchronization Web Service Protocol Specification
[MS-OXWSSYNC]: Mailbox Contents Synchronization Web Service Protocol Specification Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes
More information[MS-SSDPWP-Diff]: Database Publishing Wizard Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SSDPWP-Diff]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More information[MS-OXWSXPROP]: Extended Properties Structure. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWSXPROP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationW3C XML Schemas For Publishing
W3C XML Schemas For Publishing 208 5.8.xml: Getting Started
More informationOracle Hospitality OPERA Web Self- Service Housekeeping Web Service Specifications Version 5.1. September 2017
Oracle Hospitality OPERA Web Self- Service Housekeeping Web Service Specifications Version 5.1 September 2017 Copyright 2015, 2017, Oracle and/or its affiliates. All rights reserved. This software and
More information[MS-OXWSGTZ]: Get Server Time Zone Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWSGTZ]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationWeb Applications. Web Services problems solved. Web services problems solved. Web services - definition. W3C web services standard
Web Applications 31242/32549 Advanced Internet Programming Advanced Java Programming Presentation-oriented: PAGE based App generates Markup pages (HTML, XHTML etc) Human oriented : user interacts with
More informationBatch Submission Manual for Insurers March 1, 2013
New Jersey Department of Banking and Insurance SLAS Implementation Batch Submission Manual for Insurers March 1, 2013 PO Box 325 Trenton, NJ 08625 Phone: 609.292.7272 Fax: 609.777.0508 http://www.state.nj.us/dobi
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-RDWR]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWOOF]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationData Services API Guide SuccessMaker 10
Document last updated July 26, 2017 Copyright 2017 Pearson Education, Inc. or one or more of its direct or indirect affiliates. All rights reserved. Pearson and SuccessMaker are registered trademarks,
More informationData Services API Guide SuccessMaker 9
Document last updated September 22, 2016 Copyright 2016 Pearson Education, Inc. or one or more of its direct or indirect affiliates. All rights reserved. Pearson and SuccessMaker are registered trademarks,
More informationQosPolicyHolder:1 Erratum
Erratum Number: Document and Version: Cross References: Next sequential erratum number Effective Date: July 14, 2006 Document erratum applies to the service document QosPolicyHolder:1 This Erratum has
More informationBEAWebLogic. Event Server. WebLogic Event Server Reference
BEAWebLogic Event Server WebLogic Event Server Reference Version 2.0 July 2007 Contents 1. Introduction and Roadmap Document Scope and Audience............................................. 1-1 WebLogic
More informationOracle Enterprise Data Quality
Oracle Enterprise Data Quality Automated Loading and Running of Projects Version 9.0 January 2012 Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved. Oracle Enterprise Data Quality,
More informationWeb Services in.net (6)
Web Services in.net (6) These slides are meant to be for teaching purposes only and only for the students that are registered in CSE4413 and should not be published as a book or in any form of commercial
More informationWeb Services. The Pervasive Internet
Web Services CPSC 328 Spring 2009 The Pervasive Internet Years ago, computers couldn t talk to each other like they can now Researchers wanted to share information The Internet! Gopher & Veronica (text
More informationFall, 2005 CIS 550. Database and Information Systems Homework 5 Solutions
Fall, 2005 CIS 550 Database and Information Systems Homework 5 Solutions November 15, 2005; Due November 22, 2005 at 1:30 pm For this homework, you should test your answers using Galax., the same XQuery
More informationCMS SOAP CLIENT SOFTWARE REQUIREMENTS SPECIFICATION
CMS SOAP CLIENT SOFTWARE REQUIREMENTS SPECIFICATION CONTENTS 1. Introduction 1.1. Purpose 1.2. Scope Of Project 1.3. Glossary 1.4. References 1.5. Overview Of Document 2. Overall Description 2.1. System
More informationIUID Registry Application Programming Interface (API) Version Software User s Manual (SUM)
IUID Registry Application Programming Interface (API) Version 5.11 Software User s Manual (SUM) Document Version 5.11 January 04, 2016 Prepared by: CACI 50 N Laura Street Jacksonville FL 32202 Prepared
More informationBest Practices for Publishing and Consuming Web Services with Service Manager
Best Practices for Publishing and Consuming Web Services with Service Manager How to use Web Services for integrating applications with Service Manager HP Management Software Service Management Introduction...
More informationHub API Specification
Hub API Specification Version: 2.13 Published: 18.06.15 Docman is the trading name of PCTI Solutions Ltd. Pioneer Court, Pioneer Way Whitwood, Castleford WF10 5QU 2013 PCTI Solutions Ltd. Docman is the
More informationUse the Call Web Service action.
How to Use the Call Web Service action. Background The Call Web Service action is for advanced users and allows the workflow to make a call to a SOAP web service method. This can be used to create/edit/delete
More informationWeb Services in.net (7)
Web Services in.net (7) These slides are meant to be for teaching purposes only and only for the students that are registered in CSE4413 and should not be published as a book or in any form of commercial
More informationBig Data 9. Data Models
Ghislain Fourny Big Data 9. Data Models pinkyone / 123RF Stock Photo 1 Syntax vs. Data Models Physical view Syntax this is text. 2 Syntax vs. Data Models a Logical view
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OTPCE]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationConstructing a Multi-Tier Application in ASP.NET
Bill Pegram 12/16/2011 Constructing a Multi-Tier Application in ASP.NET The references provide different approaches to constructing a multi-tier application in ASP.NET. A connected model where there is
More informationBig Data for Engineers Spring Data Models
Ghislain Fourny Big Data for Engineers Spring 2018 11. Data Models pinkyone / 123RF Stock Photo CSV (Comma separated values) This is syntax ID,Last name,first name,theory, 1,Einstein,Albert,"General, Special
More informationSOAP and Its Extensions. Matt Van Gundy CS 595G
SOAP and Its Extensions Matt Van Gundy CS 595G 2006.02.07 What is SOAP? Formerly Simple Object Access Protocol Abstract Stateless Messaging Protocol Another XML-based Meta-Standard SOAP Processing Model
More information27-Jan Customer Portal API. Quick reference for developers
27-Jan-2015 Customer Portal API Quick reference for developers Content 1. Brief overview and process flow... 2 1.1. Session... 2 1.2. Customer authorization... 2 1.3. Audio upload... 3 1.4. Calculate price...
More informationfile:///c:/users/tomh/appdata/local/microsoft/windows/temporary%20internet%20fil...
Page 1 of 9
More information[MS-OXWOOF]: Out of Office (OOF) Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXWOOF]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationPreliminary. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSPOST]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationIntroduction to the Cisco ANM Web Services API
1 CHAPTER This chapter describes the Cisco ANM Web Services application programming interface (API), which provides a programmable interface for system developers to integrate with customized or third-party
More information[MS-HGRP]: HomeGroup Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-HGRP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationJava EE 7: Back-end Server Application Development 4-2
Java EE 7: Back-end Server Application Development 4-2 XML describes data objects called XML documents that: Are composed of markup language for structuring the document data Support custom tags for data
More informationWeb Services in.net (2)
Web Services in.net (2) These slides are meant to be for teaching purposes only and only for the students that are registered in CSE4413 and should not be published as a book or in any form of commercial
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSMSHR]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationGoProCaseSoap.wsdl <?xml version='1.0' encoding='utf-8'?><wsdl:definitions name="goprocasesoapservice"
More information
:38:00 1 / 14
In this course you will be using XML Editor version 12.3 (oxygen for short from now on) for XML related work. The work includes writing XML Schema files with corresponding XML files, writing
More informationBVN VALIDATION WEB SERVICE SPECIFICATION DOCUMENT FOR OTHER PARTIES
BVN VALIDATION WEB SERVICE SPECIFICATION DOCUMENT FOR OTHER PARTIES Version: 1.0 Date: 28-05-2015 Level: 1 Subject: June 2015, NIBSS PLC, The information contained herein is proprietary and shall not be
More informationPRELIMINARY. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXWSTASK]: Tasks Web Service Protocol Specification Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation
More informationConfiguring Capabilities Manager
Finding Feature Information, page 1 Prerequisites for, page 1 Information About Capabilities Manager, page 1 How to Configure Capabilities Manager, page 5 Additional References, page 10 Feature Information
More informationThe following is a sample XML code from the HCSProductCatalog.wsdl file.
APPENDIXA This appendix contains sample WSDL and XSD files. It includes the following sections: HCSProductCatalog.wsdl File, page A-1 HCSProvision.xsd File, page A-27 HCSProvisionAsyncResponse.wsdl File,
More information