JSE Orion Project

1
JSE Orion Project

• Technical Workgroup Session
• 27 July 2005

2
Agenda

• Introduction
• Data Conversion
• Overview of JSE API
• Functional overview
• Technical overview
• Specifications
• Testing
• Next Steps
• Questions

3
Introduction

• What will NOT be covered
• Bandwidth
• Connectivity
• Pricing
• Recap on printing / reporting
• Focus will be on the API

4
Printing Process
Print data files will be stored on an FTP Server
Member
Member Printer
MSS
FTP Server
Physical Documents
Electronic Documents
Data Publisher
------------------- ------------------- ----------
--------- -------------------
------------------- ------------------- ----------
--------- -------------------
------------------- ------------------- ----------
--------- -------------------
------------------- ------------------- ----------
--------- -------------------
Vendor
Vendor Printer

• Data will be prepared and packaged on MSS and
  then distributed to a JSE FTP site
• The member can then download his files and do his
  printing locally or alternatively, select a
  vendor to retrieve his files from the FTP site.
• In either case, the member/vendor will need to be
  given access rights to download these report
  files from the relevant folder on the server.
• Advantages
• No printer set-up or printer-driver maintenance
• Responsibility for physical printing rests with
  the Member/Vendor
• Disadvantages
• FTP server administration and maintenance rests
  with the JSE
• Security and password management

5
Market Services Preliminary Timeline
ACCN/JSE
CUSTOMER TEST
REVIEW BUILD
MEMBER TEST WITH JSE
Customer Test Platform
MEMBER TEST ENVIRONMENT AVAILABLE
Test Platform (Design, Development, Test)
Member Review (2 weeks)
MEMBER TEST WITH JSE
Allocation API (Design, Develop, Test)
Allocation API (Develop, Test)
Draft Allocation API Spec
Final Allocation API Spec
Member Review (2 weeks)
Finance API (Design)
MEMBER TEST WITH JSE
Finance API (Develop, Test)
Draft Finance Cash Draft Finance Journal
Finance Cash API Spec Finance Journal API Spec
Member Review (2 weeks)
Account API (Design)
MEMBER TEST WITH JSE
Account API (Develop, Test)
Draft Account API Spec
Account API Spec
API Specs to Market
Member Review (2 weeks)
SLB API (Design)
MEMBER TEST WITH JSE
SLB API (Develop, Test)
Draft SLB API Spec
SLB API Spec
15/11 Ref data Overall, Portfolio Holdings Diss
Specs
31/08 GL Diss Spec
20/10 SLB, Corporate Actions Diss Specs
30/09 Money Market Diss Spec
DISS Specs to Market
12/08 Deal Management Diss
12/09 Finance Diss Spec
5/01/06 Actual Test File
28/02/06 Actual Test File
5/01/06 Actual Test File
28/02/06 Actual Test File
30/11 Dummy Test File
24/10 Setup Diss Spec
FRI/ACCN DEVELOPMENT
CUSTOMER TESTING (ALLOCATION, FINANCE, GL)
CUSTOMER TESTING (SETUP, REFERENCE DATA, SLB, CA)
ACCENTURE TESTING
UAT MDR
UAT
11/12 Tech MDR
18/19 MDR1
1/2 MDR2
TWG Test Approach
06/07 Comms Session
TWG Overview Of API/Diss
6
Dissemination Types
7
Dissemination Types
8
Agenda

• Introduction
• Data Conversion
• Overview of JSE API
• Functional overview
• Technical overview
• Specifications
• Testing
• Next Steps
• Questions

9
Data Conversion Process

• Data Purification
• Data will be cleansed in the source systems,
  development environments and in the target
  systems.
• Data Validation
• Data validation routines will be built to execute
  across the data to ensure that it conforms to the
  determined business rules and will align to the
  Market Service Solution design.
• Data Reconciliation
• Data will be reconciled across the process to
  ensure that the data is accurate and accounted
  for. Reports from existing systems will be
  compared to reports from the new system. The
  reconciliation process will be closely audited
  and signed off.

• Data Extraction Process
• Data is extracted from the source systems and
  uploaded to the data conversion pre staging
  development environment.

• Data Transformation Process
• Data from the source systems is mapped to the MSS
  data model.
• Business rules are defined.
• Data is consolidated and transformed from the
  source system format into a format that can be
  uploaded into the target Market Services Solution.

• Data Upload Process
• Data in the format for the target Market Services
  Solution is uploaded from the data conversion
  environment.

10
Data Conversion

• Data Conversion Document
• Will be delivered in stages
• Members to assist in QA/review process

11
Agenda

• Introduction
• Data Conversion
• Overview of JSE API
• Functional overview
• Technical overview
• Specifications
• Testing
• Next Steps
• Questions

12
API

• The following functional items will be catered
  for using the API
• Deal Allocations
• SLB transactions
• General Ledger and sub ledger financial
  transactions
• Client account setup

13
API Technical Overview

• WSA exposes JSE back office functionality over a
  distributed network
• Communicate with WSA via XML Web Services over
  HTTP / SOAP

XML Schema Validation
XML
Business Rules
XML
14
OASIS WS-Security
Technology Committee Sponsor-Level members

• Actional Corporation
• Adobe Systems
• BEA Systems, Inc.
• BMC Software
• Computer Associates
• EMC
• Fujitsu Limited
• Hewlett-Packard
• Hitachi, Ltd.
• IBM
• Microsoft Corporation
• Neustar, Inc.

• Nokia Corporation
• Oracle Corporation
• Reactivity
• RSA Security
• SAP AG
• Sarvega
• SeeBeyond Technology Corporation
• Sun Microsystems
• Systinet Corp.
• Tibco Software Inc.
• VeriSign

Plus 300 Additional OASIS Members
15
WS-I Organization
16
Web Services Architecture XML Structures and
Interfaces

• Synchronous messaging will be catered for
• This will operate on Request / Response pattern
• XML messages will be used
• XML messages will conform to the standard JSE
  global schema

17
Web Services Architecture Technical Specification
Format

• Field Listing will contain the following
• Description
• Validation
• BDA Field Mapping
• Field Constraints
• Interface Configuration
• Message XML Schema Definition
• Message XML Sample

18
Agenda

• Introduction
• Data Conversion
• Overview of JSE API
• Functional overview
• Technical overview
• Specifications
• Testing
• Next Steps
• Questions

19
Testing

• Similar approach to Project Jarrow
• A TWG session will be scheduled for the end of
  August to provided detailed procedure for testing

20
Agenda

• Introduction
• Data Conversion
• Overview of JSE API
• Functional overview
• Technical overview
• Specifications
• Testing
• Next Steps
• Questions

21
NEXT STEPS

• Next TWG scheduled for end of August 2005
• This session will focus on our test Approach
• Specifications
• Living document
• Specifications will all form part of a Software
  Development Kit (SDK)
• Available on the web www.jse.co.za under Orion
• Account Managers to notify members once draft
  specs are available
• Comments on draft specs can be sent to
• Orion_spec_mssapi_at_jse.co.za
• Orion_spec_mssdis_at_jse.co.za
• All questions/comments with the official
  responses will be appended to the relevant
  specifications

22
Questions