LCON TALX Briefing

1
LCON / TALX Briefing

• 12 MARCH 2002

2
Countdown
Jarrow Count Down To Go Live as at 12th March
2002 Just 62 Total Days 40 JSE Business Days
Remaining
3
LCON Briefing
Agenda

• Recap from last LCON brief
• Lessons learnt
• Schedule and processes
• Relevant documentation
• TALX Front End specifics
• Questions

4
LCON Briefing
Agenda

• Recap from last LCON brief
• Lessons learnt
• Schedule and processes
• Relevant documentation
• TALX Front End specifics
• Questions

5
Timeline
2001
2002
June
Aug
Oct
Sept
Feb
Jan
Dec
Nov
July
Mar
April
May
4/6/01
3/8/01
JSE Design
19/10/01
6/8/01
JSE Development
4/6/01
19/10/01
JSE Build and Test of
Technical
Infrastructure
22/10/01
JSE/LSE Prepare and Execute
Integration Test

18/01/02
4/6/01
3/8/01
9/11/01
Prepare and Execute Business Operations Proving
12/4/02
21/1/02
Design of JSE Front End Solution
Build and Test of JSE

Front End Solution
2/03/02
LCON
16/03/02
Design, Build and Test of Data Vendor / Member


Front End Solution
LCON
27/6/01
18/01/02
30/03/02
LCON
13/4/02
1st DR
31/03/02
18/7/01
27/6/01
4/6/01
27/04//02
JSE / LSE Draft Spec
JSE / LSE Final Spec
Prepare and Execute Customer Test
26/11/01
2nd DR
Go-live
We are here!
6
Deployment Timeline
April
May
March
LCON 1
Dress Rehearsal 3 (CONT)
JSE LSE Internal Dress Rehearsal
Sat Sun4-5 May
Sat2 Mar
Sat6 Apr
Go-live
Sat Sun13-14 Apr
LCON 2
Dress Rehearsal 1
13 May
Sat16 Mar
JSE LSE ASR Test
Sat Sun27-28 Apr
Dress Rehearsal 2
LEGEND LCON Live Connectivity Testing DR Dress
Rehearsal CONT Contingency ASR Alternate Site
Recovery (LSE) Internal External
Sat23 Mar
LCON 3
Sat30 Mar
7

General Overview

• Who has to participate in LCON? (Live
  Connectivity Test)
• All systems that will connect directly to JSE
  SETS and/or receive information from InfoWiz for
  production
• ALL JSE users (members and data vendors)
• Minimum one ASP terminal per user
• All instances of active servers and at
  least one terminal-
• Host-to-Host Primary server
• Alternate Back-up server
• Failover / DRP site

Reminder Conformance is a prerequisite to LCON
8
JCON LCON Support

• Users Responsibility
• Own IT technical team on site for resolution of
  connectivity queries
• Notify JSE Customer Services once on site and
  ready to start testing
• User staff to test the login and related testing
• Software provider support
• Ensure the JSE User Readiness team has correct
  contact names and numbers
• JSE and LSE Teams
• Support through JSE Customer Services only
• Customer Test analysts
• All queries must be logged and a reference
  numbers allocated
• Problems will be handled First in first addressed
  as there are limited resources
• Contact Number during test
• JSE Customer Services Help Desk [phone]

9
Enablement Process
The high level process for LCON is the same as
that for conformance tests. The key difference is
that the Live environment is used, both at the
customer and the Exchange sites.
LCON Dates Left Saturday 16 March and 30 March
JCON LCON Test Preparation
Production Application Infrastructure Freeze
JCON Test Execution
Sign Live Contract
Enablement Process
LCON Test Execution
Schedule

• Minimum requirements
• Signed contracts including order form with
  ACCURATE details per enablement
• Conformed software (passed Conformance on final
  version of software for go-live)
• User Enabled and customer ready for production
  rollout
• Production infrastructure in place
• Scheduled LCON slot

10
JCON / LCON Preparation

• An LCON is a connectivity test to confirm the
  communications connectivity and customer
  enablement comprising two parts
• The first part tests the JSE users connectivity
  to the JSE Hub (JCON). JCON only applies to TALX
  ASP users
• The second part tests the users connectivity
  through to the JSE SETS and InfoWiz systems (LCON)

2 LCON Tests
JCON Connectivity from a member to the JSE Hub
LCON Connectivity from a member to JSE SETS
InfoWiz
You need to undergo a JCON test before an LCON
test if you are a TALX ASP user
11
JCON LCON Preparation
Production Application Infrastructure Freeze
JCON LCON Test Preparation
JCON Test Execution
Sign Contracts
Enablement Process
LCON Test Execution
Schedule

• A Customer Support representative will contact
  customers the Thursday before the test to confirm
  readiness
• Host to Host Customers must ensure
• You have activated your production KEK(s)
  (provided valid Key Check Value to the JSE)
• Production routing is in place for production /
  back-up line
• You have tested your back-up line prior to LCON
  weekend
• You have conformed before your JCON LCON
• ALL Customers must ensure
• They have the correct test scripts
• They are contactable by telephone through-out the
  day on the telephone numbers provided to their
  JSE User Readiness representative
• On the morning of the test the customer will be
  contacted by a CTA

12
LCON Scenarios
13
Test Procedures
LCONs allow customers to confirm the
communications connectivity and customer
enablement

• InfoWiz Installation
• Connect to broadcast groups
• Log-on to Interactive Request Interface
• Re-request missed messages
• Recover from line failure (backup)
• Log-off Interactive Request Interface

• JSE SETS Installation
• Log-on to Secure Interactive Interface
• Enter Trade Report
• Request own order book download
• Recover from line failure (backup)
• Log-off Secure Interactive Interface

14
Test Procedures

• A JCON (for ASP) and LCON is a MANDATORY test
• 3 working days notice for cancellation of
  bookings
• LCON is required per software installation going
  live, i.e. primary, secondary DRP
• Have to pass LCON to continue
• Each member will be provided with a Customer
  Support representative who must be contacted
  directly if faced with any problems. If a member
  calls and the representative is not available,
  please leave a message and the representative
  will get back to you
• Customer support representatives will contact
  members on the Thursday prior to the LCON test
• Test execution is between 12h00 and 18h00 on LCON
  Saturday

15
Production Infrastructure Freeze
JCON LCON Test Preparation
Production Application Infrastructure Freeze
JCON Test Execution
Sign Live Contract
Enablement Process
LCON Test Execution
Schedule

• The user production application and
  infrastructure freeze is required
• to ensure connectivity and communications are
  working on Dress Rehearsals and Go live
• Minimise risk on the Go live week ends
• If members reconfigure their systems after LCON
  testing, e.g. change IP address, they need to
  repeat the LCON test, provided that slots are
  available
• If slots are not available, they cannot Go Live
• No LCONS will be allowed on Dress Rehearsal test
  days time is limited and all market period
  schedules need to be tested on these days

16
JSE Application Infrastructure Freeze
JSE Soft Freeze
JSE Hard Freeze
4 Feb 2002
15 Mar 2002
24 June 2002
13 May 2002
JSE Jarrow Testing
Dress Rehearsals
LCONs
Jarrow Release 1
Jarrow Release 1.1
Next Customer Take On
2 Mar 2002
27 July 2002
JSE User Freeze
17
LCON Briefing
Agenda

• Recap from last LCON brief
• Lessons learnt
• Schedule and processes
• Relevant documentation
• TALX Front End specifics
• Questions

18
Lessons Learnt

• User Technical Infrastructure Audit Reports were
  due on the 18th Feb
• many are still outstanding!!!! These
  must be submitted by no later than close of
• business today else LCON will not be
  allowed
• Not all contracts (JSA / JIDA) have been received
  contracts are required 7 days before LCON
  date.
• User Router Configurations are complex. Verify
  these against the sample configurations
• supplied in the JSE Guide to Production
  Connectivity Testing document.
• Kindly source JSE assistance before close of
  business on Friday to avoid delays on Saturday
• Production BIC codes as loaded and used for
  current BDA STRATE Swift interfaces should
• be used to configure user systems (use BIC
  code on your CEIF)
• Verify all BDG IP address configurations as
  provided on the CEIF forms with special
• attention to B10 and B11 (these are common
  to JSE LSE).
• Insufficient time was allocated for the JSE and
  LSE to ensure production connectivity
• this resulted in a delay and should not
  re-occur.
• Users must test their back up lines in production
  prior to the LCON test.

19
Lessons Learnt

• Until the reference data download is
  started, only idle polls will be received on all
  BDGs.
• Users must verify receipt of idle polls on
  all subscribed BDGs. Kindly complete the
  related
• test template and submit these to the JSE
  after the test via email or fax.
• Previous LCON test included fail over
  testing from primary to backup line then back to
• the primary line. Fail over back to the
  user primary line is not required. This was to
• ensure connectivity for Monday trading.
  This will be tested and proved on Sunday as part
  of
• the JET test.
• Reference data will be released at the
  defined time. Users not ready to receive this
  will be
• enabled to re-request this.
• Members are urged to follow the LCON
  process, e.g. customers should use
• Customer Support as point of contact on day
  of testing.
• Any network infrastructure queries or
  questions prior to LCON testing should be made
• via JSESPEC or User Readiness Helpdesk
  [phone] / 7280.
• No direct communication to technical
  infrastructure team during LCON, unless
• initiated by the JSE.

20
Lessons Learnt

• Kindly ensure that you note the name of the
  CTA executing your test.
• LCON test report results will be available
  from Wednesday afternoon post the LCON test.
• JSE customer test documentation will be
  re-published tomorrow kindly ensure you
• download the latest versions from the JSE
  website.
• The test schedule timings are approximate
  and will be adhered to where possible. Users
• must be available until the end of the
  test. Only general problems will result in a
  delay.
• LCON is to resolve connectivity and
  application communication between users, the JSE
  and
• the LSE.
• If you are testing more than one solution,
  test each solution separately, not in parallel,
  i.e.
• start and end one solution before going on
  to next.
• Users must ensure that all new lines (if
  any) terminate at the correct JSE address.
  Primary
• and back up lines should not terminate at
  the same place. If you are unsure, please
  contact
• JSE Spec or the JSE User Readiness
  Helpdesk as soon as possible.
• We have 47 potential users on Saturday
  patience is required.

21
LCON Briefing
Agenda

• Recap from last LCON brief
• Lessons learnt
• Schedule and processes
• Relevant documentation
• TALX Front End specifics
• Questions

22
LCON Schedule Process
Primary Line
Secondary Line
Connect to SII, IRI, BI confirm reception of
subscribed BDG idle polls
Connect to SII, IRI, BI confirm reception of
subscribed BDG idle polls
Enter Trade Report
Primary to Secondary line fail-over
Enter Trade Report
Receive Reference Data Download
JSE confirm users to connect
Conduct JCON
END
0800
1230
1330
1800
1430
1200
JSE CSS willl confirm systems ready
LSE CTA will call to ask customer to start test
LSE CTA to call to confirm start of download
JSE to perform failover. LSE CTA will call
customer to start next step
Customer to confirm progress with LSE CTA
Customer to confirm progress with LSE CTA
CustomerComms

• Connect to SII, IRI BI only after call received
  from Customer Support
• LSE CTA will guide customer through test
  execution
• JSE Customer Services Help desk should be
  contacted by customers if any problems arise
  during testing 520-7777

23
Sunday JET Testing
User notification to JSE of results
JET startup
JET User Login
JET shutdown
8h15
9h00
10h15
10h00

• JET will be available on Sunday between
  09h00 and 10h00 to verify user
  connectivity for Mondays trading
• The system will be in a start-up mode
  allowing users to LOGIN only
• Users should verify their JET Link Monitor
  screen to ensure
• - that both CTCI and Broadcast show
  connected
• - if resolving there is a
  connectivity problem, please contact support
• All JET API adapters will be started to
  allow users to verify their TIBCO connectivity
• Once you have successfully logged in to MW
  and TIBCO, your test is complete.
  PLEASE NOTIFY SUPPORT ONCE YOU HAVE
  SUCCESSFULLY TESTED
• JSE JET Support can be contacted on 520-7477
  throughout the test on Sunday only

24
LCON Briefing
Agenda

• Recap from last LCON brief
• Lessons learnt
• Schedule and processes
• Relevant documentation
• TALX Front End specifics
• Questions

25
Relevant Documentation

• JSE Guide to Production Connectivity
  Testing
• JSE ASP (MAW) Connectivity Test Schedule
• JSE Live Connectivity Test Schedule
  Checklist
• JSE Production Connectivity FAQs
• Documentation downloadable from the JSE website
• http//www.jse.co.za
• jse_initiatives
• jsetrad_info_sys
• customer_testing_services
• customer_testing.htm

26
Questions
TALX users to remain behind for TALX specific
testing requirements to follow
27
LCON Briefing
Agenda

• Recap from last LCON brief
• Lessons learnt
• Requirements for ASP
• Schedule and processes
• Relevant documentation
• TALX Front End specifics
• Questions

28
Test Procedures
LCONs allow customers to confirm the
communications connectivity and customer
enablement

• InfoWiz Installation
• Connect to broadcast groups
• Log-on to Interactive Request Interface
• Re-request missed messages
• Recover from line failure (backup)
• Log-off Interactive Request Interface

• JSE SETS Installation
• Log-on to Secure Interactive Interface
• Enter Trade Report
• Request own order book download
• Recover from line failure (backup)
• Log-off Secure Interactive Interface

• TALX ASP Installation
• Log-on to Secure Interactive Interface
• Enter Trade Report
• Log-off Secure Interactive Interface

29
JCON / LCON Preparation

• An LCON is a connectivity test to confirm the
  communications connectivity and customer
  enablement comprising two parts
• The first part tests the JSE users connectivity
  to the JSE Hub (JCON). JCON only applies to TALX
  ASP users
• The second part tests the users connectivity
  through to the JSE SETS and InfoWiz systems (LCON)

2 LCON Tests
JCON Connectivity from a member to the JSE Hub
LCON Connectivity from a member to JSE SETS
InfoWiz
You need to undergo a JCON test before an LCON
test if you are a TALX ASP user
30
JCON Schedule and Process
JSE to fail-over customer line
JCON END LCON to follow
Verify connectivity via Globe ICON on toolbar
Log-on to TALX Server
JSE Confirm system up
Log-on to TALX Server
Verify connectivity via Globe ICON on toolbar
Log-off TALX Server
0800
1200
0830
-1000
JSE CSS willl confirm systems ready
Users test ALL TALX sign ons
JSE fail user to backup lines
Users test ALL TALX sign ons
Users logoff
Users verify connectivity per sign on
Users verify connectivity per sign on
JCON is applicable to Talx ASP users only TALX
users must execute LCON in the afternoon
31
TALX Front End Specifics

• Requirements for TALX Front End
• TALX contract signed
• TALX order form returned
• ALL TALX terminal installation(s) completed
• TALX ASP Front End (JCON)
• Member Security Contact representative to
  provide the JSE with a list of traders and
• email address to receive related sign ons
  and passwords. Send Trader Name,
• existing JET trader ID and contact number
  per trader to Rekha at rekhar_at_jse.co.za
• by Wednesday before test)
• Connectivity established by launching
  application from 08h00 to 12h00
• - Log on with your password
• - Users Logins and passwords will be
  sent to brokers before JCON test via email only
  
• if the above steps have been completed.

32
TALX Front End Specifics - JCON

• Requirements for JCONs continued
• Verify connectivity, by checking that the
  little globe icon on the toolbar changes colour,
  
• i.e. from red/yellow to blue/green
• Double click on the globe icon to get the
  server information window. This should show
• up as green. If not green in colour,
  please contact JSE Customer Support [phone]
  
• During fail-over test, connectivity will be
  lost for a short period (1-2 minutes) and
• connection will be re-established
  automatically. If this reconnection is
  unsuccessful,
• please contact JSE Customer Support (011)
  520 7777

33
TALX Front End Specifics Host to Host

• Requirements for TALX Server Front End (LCON)
• No JCON with JSE required
• ALL TALX servers installed and configured
• ALL TALX terminals and users configured
• TALX server passed conformance test
• Establish connectivity from each workstation
  to server before 12h00 (recommended)
• Confirmed JSE TALX support (only applicable
  for Host to Host) with Rekha
• Rowjee (011) 520 7572
• Continue with LCON test

34
LCON Briefing
Agenda

• Recap from last LCON brief
• Lessons learnt
• Requirements for ASP
• Schedule and processes
• Relevant documentation
• TALX Front End specifics
• Questions

35
Questions