0 0 Mainframe Legacy Access Migration (MLAM) Version 5 Municipality Meeting 3/5/2015 & 3/10/2015.

14
1 1 Mainframe Legacy Access Migration (MLAM) Version 5 Municipality Meeting 3/5/2015 & 3/10/2015

Transcript of 0 0 Mainframe Legacy Access Migration (MLAM) Version 5 Municipality Meeting 3/5/2015 & 3/10/2015.

11

Mainframe Legacy Access Migration

(MLAM)

Version 5

Municipality Meeting3/5/2015 & 3/10/2015

MLAM Introduction Topics

• Introduction of VITA/NG Personnel

•Project Overview

•Necessary Actions

•Project Timeline

•Questions/Contacts

2

Introduction of VITA/NG Personnel

3

•Hal Hughey (VITA) – Customer Account Manager

•Mike Shaffer (VITA) – Service Delivery Manager

•Jonathan Botts (NG) – Project Manager

•Other(s)

Project Overview

4

•VITA/NG project to retire end-of-life devices

–Channel interface Processor (CIP) router

–Data Link Switching (DLSw) router

•Objectives:

–Move all users off of CIP/DLSw

–Utilize secure communications for all mainframe access

Project Overview

5

CIP Router

DIT DLSw Router

To U

ser

Org

aniz

atio

ns

Open Systems Adapter

To U

ser Org

anizatio

ns

Legacy Connections Transformed Connection

IBMMainframe

Applications

Compensation Board/RESQ users are not part of this project

Project Overview

•Which device am I using?

–DLSw router:

• User report included names of users

–From a list of dedicated connections

–CIP router:

• User report included names of users AND transactions counts per month

•The migration solution is the same…

6

Action Plan

1. Define single point of contact (POC) for entire municipality to:

– Coordinate flow of information between municipal departments (if applicable)

– Communicate to end users

– Submit request for FW rules

– Reporting status to VITA/NG team

7

With more than 150 municipalities, state agencies, and non-state agencies involved, a SINGLE POC for each is essential

Action Plan

2. Review list of identified users

• Report any discrepancies to VITA/NG team

3. Procure/obtain TN3270 emulator that can support TLS encryption

• If current emulator cannot

4. Complete firewall rule request form and send to [email protected]

8

Action Plan

5. Test connectivity

• Reply to completion notice with any issues

If 2+ weeks after completion, contact VCCC

6. Notify VITA/NG of successful connection

7. Implement changes for all

9

VITA/NG executes request and provides new address/port information

Proven Migration Procedures

•Several municipalities have finished migrations

•Numerous FW rule requests processed using form

10

Clean-Up Activities

•Municipality:

–Submit TSR Form

•Only if local circuit can be eliminated

•VITA/NG:

–Block legacy access route

•To prevent users from reverting

11

End User Impact

•Emulator software may alter look and feel of connection (display changes)

•Application accessed and data presented should not change

–Several municipalities have finished migrations

–Numerous FW rule requests processed

•Encryption process is transparent to user

12

Project Timeline

•Target for migration – 90 days (6/8/15)

• Requested feedback from POC:

– Milestone updates:

• Selected TN3270 emulator

• Submitted FW rule request ticket

– Status update every two weeks

– Notification of any schedule constraints

13

Questions/Contacts/Resources

•Please direct all questions and updates to:

[email protected]

–Shared mailbox for MLAM project

•FAQs and other information

– Includes links to TSR & firewall rule request

•Submit firewall rule request form to:

[email protected]

14