Securities Lending Reporting Web Service

Similar documents
Artix ESB. Bindings and Transports, Java Runtime. Version 5.5 December 2008

WSDL. Stop a while to read about me!

El fichero de descripción del servicio se puede obtener a partir de la siguiente URL:

Securities Lending Reporting

Fuse ESB Enterprise Using the Web Services Bindings and Transports

Web Service Provider Example - Enabling Visible Business

Artix Bindings and Transports, C++

<xsd:element name="name" maxoccurs="1" minoccurs="0" <xsd:element name="parentaccountid" maxoccurs="1" minoccurs="0" <xsd:element name="parentaccounti

Java CAPS 6 Update 1 Exposing MTOM-capable Java CAPS Classic Web Service Contents Introduction

Exercise sheet 4 Web services

Oracle Communications Network Charging and Control. Web Services Description Language Reference Guide Release 6.0.1

ISM Configuration Step by Step Guide SOAP Monitor. Overview. Version 1.1

Preliminary. Database Publishing Wizard Protocol Specification

Web Services in.net (7)

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

The contents of this publication the specifications of this application are subject to change without notice.

ID2208 Programming Web Services

Technical Specifications for TAXI (Web Services using tml) Version template-3.0

Web Services in.net (6)

SOA & Web services. PV207 Business Process Management

This tutorial is going to help all those readers who want to learn the basics of WSDL and use its features to interface with XML-based services.

City/Zip Lookup Web Service Implementation Guide Version 1.00

dciphering Computing Amazon Seller Central Soap/XML Services as of Jan/2009

Lab 3: Simple Integration Use Case

Introduction to the Prime Fulfillment API

ETSI TS V9.0.0 ( ) Technical Specification

[MS-SSDPWP-Diff]: Database Publishing Wizard Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

02267: Software Development of Web Services

Interface Control Document

ITIL as a Testbed for SOA. Michael Rulf. VP Advanced Engineering

Real-Time Claim Adjudication and Estimation Connectivity Specifications

PART VII Building Web Services With JAX-RPC. 7.5 JAX Web Service Architecture. Development of a Web Service with JAX. Runtime View of a Web Service

Using BMC SRM OOB Web Services

Defending Web Services using Mod Security (Apache)

Web Services. Grid Computing (M) Lecture 6. Olufemi Komolafe 19 January 2007

ISM Configuration Step by Step Guide SOAP Monitor. Overview. Version 1.0

ECE450H1S Software Engineering II Tutorial I Web Services

Lecture Notes course Software Development of Web Services

Descriptions. Robert Grimm New York University

This presentation is a primer on WSDL Bindings. It s part of our series to help prepare you for creating BPEL projects. We recommend you review this

Web services. In plain words, they provide a good mechanism to connect heterogeneous systems with WSDL, XML, SOAP etc.

Best Practices for Publishing and Consuming Web Services with Service Manager

Introduction to Web Services

Objective: Review how to use access the Bulkvs.com Origination and 911 SOAP API using SOAP UI

-iport-type-name Specifies the porttype element for which a binding should be generated. Specifies the name of the generated SOAP binding.

Calendar Data API. Version gradleaders.com

SOAP Primer for INSPIRE Discovery and View Services

Developing JAX-RPC Web services

Support For assistance, please contact Grapevine: or

Guide: SOAP and WSDL WSDL. A guide to the elements of the SOAP and WSDL specifications and how SOAP and WSDL interact.

Descriptions. Robert Grimm New York University

Articulation Transfer Clearinghouse Implementation Guide

A namespace prefix is defined with a xmlns attribute using the syntax xmlns:prefix="uri".

What is Web Service. An example web service. What is a Web Service?

Software Developer s Guide for Cisco Secure Access Control System 5.3

Oracle Communications Network Charging and Control. Open Services Development User's & Technical Guide Release: NCC4.4.1

GoToMyPC Reporting Services API

Sriram Krishnan, Ph.D. NBCR Summer Institute, August 2010

Fax Broadcast Web Services

Dr. Cesare Pautasso Computer Science Department Swiss Federal Institute of Technology (ETHZ)

DAFTAR REFERENSI. [GRE07] diakses tanggal 7 Desember 2007.

European Publication Server - Web Service Access 1.1 -

1.264 Lecture 14. SOAP, WSDL, UDDI Web services

ETSI TS V9.0.0 ( ) Technical Specification

Data Pump User Guide

Web Applications. Web Services problems solved. Web services problems solved. Web services - definition. W3C web services standard

Usage of Evaluate IPAddress Action with wm Mediator

Publications Office. TED Website - Notice Viewer WS Technical Specifications Document - Appendix D - NoticeViewer

PTC Integrity 10.7 Web Services Reference

IndySoap Architectural Overview Presentation Resources

Web Services and WSDL

SOAP. Gustavo Alonso Computer Science Department Swiss Federal Institute of Technology (ETHZ)

Web Services Overview

Category: Standards Track December Using NETCONF over the Simple Object Access Protocol (SOAP)

Developing Applications for the Java EE 7 Platform 6-2

Dyalog APL SAWS Reference Guide

WEB SERVICES PXC. (v 0.2) Manel Guerrero Albert Cabellos UNIVERSITAT POLITÈCN NICA DE CATALUNYA

Web Services Invocation Framework (WSIF)

Candidate Resume Data API

@WebService OUT params via javax.xml.ws.holder

Introduction to Web Services

Case study group setup at catme.org Please respond before Tuesday next week to have better group setup

Web Services. GC: Web Services Part 2: Rajeev Wankar

DAVE. SOAP Web Services

ETSI TS V9.1.0 ( ) Technical Specification

SOAP Web Services Objektumorientált szoftvertervezés Object-oriented software design. Web services 11/23/2016. Outline. Remote call.

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

DAP Web Services Specification DRAFT

ETSI TS V8.3.0 ( )

Modulo II WebServices

Industry Training Register. Guide to integration for ITOs

CSE 210: Service-Oriented Software and Systems Engineering & Model-Driven Development

Power IQ WS-API Programming Guide Release 2.0

27-Jan Customer Portal API. Quick reference for developers

»

Annex I Messaging Service Specifications

Broadband Connectivity Service (BBCS),Full Access Services (FA) and Cooperation Partner Services (COPA) General Functions Interface Specification

Developing a Service. Developing a Service using JAX-WS. WSDL First Development. Generating the Starting Point Code

Cisco CallManager 4.1(2) AXL Serviceability API Programming Guide

Web. Web. Java. Java. web. WebService. Apache Axis. Java web service. Applet Servlet JSP SOAP WebService XML J2EE. Web (browser)

Transcription:

Securities Lending Reporting Web Service External Interface Specification Broker Trades Message Specification November 2009 (November 2007) ASX Market Information 2009 ASX Limited ABN 98 008 624 691

Table of Contents Introduction...3 About this Guide...3 Securities Lending Submission Service Overview...4 SOAP Request example...5 Daily Submission...7 CSV file format for Daily Submissions...7 On Success...8 Quarterly Submission...9 CSV file format...9 On Success...10 Error Handling...11 13/11/2009 Securities Lending Reporting Web Service (External Interface Specification) Page 2 of 12

Introduction About this Guide This specification has been designed as to provide external parties with the information required in order to write interfaces to the Web Service ASX is developing for the ASX Securities Lending direct reporting facility 1. The Securities Lending Submission Service is provided to the Participants who may be interested in automating the data submission process. The Submission Service itself is described by way of a Web Services Description Language (WSDL). The Submission Service exposes two operations as per WSDL below: - Daily Submission (submitdaily) - Quarterly Submission (submitquarterly) Both Daily and Quarterly submission operations require four arguments, being: ASXOnline User Name, ASXOnline Password, ASXOnline Company PIN, and The CSV file being uploaded. If you do not have an ASX Online User Name, Password or Company PIN, please contact the ASX Online administrator in your firm. They will provide you with these details. If you do not know who your ASX Online administrator is, or are not a Participant of ASX, please contact the ASX Online Help Desk on 1800 682 484 or via email at ASX.Online@asx.com.au. As well as providing the above functions via the Web Service described in this document, these functions can be performed essentially manually via the internet by logging into the ASXOnline Securities Lending Reporting Facility through your internet browser. The steps required to access the ASXOnline facility are described in a separate User Guide which can be found here: https://www.asxonline.com/participants/services/securitylending/usernotes.pdf. Aside from error response upon unsuccessful submission, no reports will be available directly through the Web Service. If you have any questions or require clarification on the use of the web service, please contact ASX Customer Service (Hours are 8:30am-6:00pm Sydney) on: - 131 ASX (131 279) from within Australia (cost of a local call) or - +61 2 9338 0000 from Overseas 1 ASTC Bulletin references P2009/583 Technical Capability & Effective Date For Securities Lending Activity Reporting - Daily Reporting And Quarterly Reporting ( Direct Reporting ): https://www.asxonline.com/intradoccgi/groups/clearing_and_settlement/documents/communications/asx_024864.pdf 13/11/2009 Securities Lending Reporting Web Service (External Interface Specification) Page 3 of 12

Securities Lending Submission Service Overview The following WSDL defines the Submission service. <?xml version="1.0" encoding="utf-8"?> <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetnamespace="http://webservice.participants.asx.com.au" xmlns:tns="http://webservice.participants.asx.com.au" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"> <message name="uploadreturn"> <part name="uploadreturn" type="xsd:boolean"></part> </message> <message name="uploadrequest"> <part name="username" type="xsd:string"></part> <part name="password" type="xsd:string"></part> <part name="pin" type="xsd:string"></part> <part name="csv" type="xsd:hexbinary"></part> </message> <porttype name="securitylendingsubmission"> <operation name="submitdaily"> <input message="tns:uploadrequest"/> <output message="tns:uploadreturn"/> </operation> <operation name="submitquarterly"> <input message="tns:uploadrequest"/> <output message="tns:uploadreturn"/> </operation> </porttype> <binding name="securitylendingsubmissionbinding" type="tns:securitylendingsubmission"> <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="submitdaily"> <soap:operation soapaction=""/> <input> <mime:multipartrelated> <mime:part> <soap:body use="literal"/> </mime:part> <mime:part> <mime:content part="csv" type="application/octet-stream"/> </mime:part> </mime:multipartrelated> </input> <output> <soap:body use="literal"/> </output> 13/11/2009 Securities Lending Reporting Web Service (External Interface Specification) Page 4 of 12

</operation> <operation name="submitquarterly"> <soap:operation soapaction=""/> <input> <mime:multipartrelated> <mime:part> <soap:body use="literal"/> </mime:part> <mime:part> <mime:content part="csv" type="application/octet-stream"/> </mime:part> </mime:multipartrelated> </input> <output> <soap:body use="literal"/> </output> </operation> </binding> <service name="securitylendingservice"> <port name="securitylendingsubmission" binding="tns:securitylendingsubmissionbinding"> <soap:address location="https://www.asxonline.com/participants/services/securitylendingsubmission"/> </port> </service> </definitions> SOAP Request example Here is an example of daily submission SOAP request. ------=_Part_0_10159276.1255406309890 Content-Type: text/xml; charset=utf-8 Content-Transfer-Encoding: 8bit Content-ID: test1234 <soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:web="http://webservice.participants.asx.com.au"> <soapenv:header/> <soapenv:body> <web:submitdaily> <username>smith_j</username> <password>password</password> <pin>123456</pin> <csv href="file1234"/> </web:submitdaily> </soapenv:body> </soapenv:envelope> ------=_Part_0_10159276.1255406309890 Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-ID: <file1234> 14/09/2009 ASX_CODE BHP,222,111 13/11/2009 Securities Lending Reporting Web Service (External Interface Specification) Page 5 of 12

------=_Part_0_10159276.1255406309890-- 13/11/2009 Securities Lending Reporting Web Service (External Interface Specification) Page 6 of 12

Daily Submission The submitdaily operation requires four mandatory arguments: ASXOnline User Name, ASXOnline Password, ASXOnline Company PIN, and CSV file containing the daily data (as attachment) If you do not have an ASX Online User Name, Password or Company PIN, please contact the ASX Online administrator in your firm. They will provide you with these details. If you do not know who your ASX Online administrator is, or are not a Participant of ASX, please contact the ASX Online Help Desk on 1800 682 484 or via email at ASX.Online@asx.com.au. CSV file format for Daily Submissions A comma separated file format has been chosen, identical to the format required for manual submissions. This format is as follows: Example of the file containing ISINs Example of file containing ASX codes File name should not be longer than 30 characters including.csv extension which is mandatory. 13/11/2009 Securities Lending Reporting Web Service (External Interface Specification) Page 7 of 12

On Success On successful submission, the data specified in the CSV file are committed to the database and the service returns a status code of 1 in the response as shown below. <soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance"> <soapenv:header/> <soapenv:body> <tns:submitdailyresponse xmlns:tns="http://webservice.participants.asx.com.au"> <uploadreturn>1</uploadreturn> </tns:submitdailyresponse> </soapenv:body> </soapenv:envelope> 13/11/2009 Securities Lending Reporting Web Service (External Interface Specification) Page 8 of 12

Quarterly Submission The submitdaily operation requires four mandatory arguments: ASXOnline User Name, ASXOnline Password, ASXOnline Company PIN, and CSV file containing the quarterly data (as attachment) If you do not have an ASX Online User Name, Password or Company PIN, please contact the ASX Online administrator in your firm. They will provide you with these details. If you do not know who your ASX Online administrator is, or are not a Participant of ASX, please contact the ASX Online Help Desk on 1800 682 484 or via email at ASX.Online@asx.com.au. CSV file format A comma separated file format has been chosen, identical to the format required for manual submissions. This format is as follows: Example of the file containing ISINs Example of file containing ASX codes File name should not be longer than 30 characters including.csv extension which is mandatory. 13/11/2009 Securities Lending Reporting Web Service (External Interface Specification) Page 9 of 12

On Success On successful submission, the data specified in the CSV file are committed to the database and the service returns a status code of 1 in the response SOAP message. <soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance"> <soapenv:header/> <soapenv:body> <tns: submitquarterly Response xmlns:tns="http://webservice.participants.asx.com.au"> <uploadreturn>1</uploadreturn> </tns: submitquarterly Response> </soapenv:body> </soapenv:envelope> 13/11/2009 Securities Lending Reporting Web Service (External Interface Specification) Page 10 of 12

Error Handling The service invocation may fail due to various conditions, such as incorrect password or PIN supplied in the service request. On these conditions, the web service responds with SOAP Fault element in the response. As per standard, the SOAP Fault element contains the fault code and the fault string that contains the detailed message indicating the nature of the error. ASX recommends that when Participants encounter error during web service calls they are to submit the data manually via the website to obtain the source of the error. Hence the fault string will not contain fine-grained error information. The error response will be of the following structure: <soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance"> <soapenv:header/> <soapenv:body> <soapenv:fault> <faultcode>soap-env:client</faultcode> <faultstring>some error description</faultstring> </soapenv:fault> </soapenv:body> </soapenv:envelope> If you continue to experience problems using the web service, please contact ASX Customer Service (Hours are 8:30am-6:00pm Sydney) on: - 131 ASX (131 279) from within Australia (cost of a local call) or - +61 2 9338 0000 from Overseas 13/11/2009 Securities Lending Reporting Web Service (External Interface Specification) Page 11 of 12