1. Tecniche di integrazione applicativa con Host Integration Server 2004 Alessandro Appiani MCT MCSE (2000 NT 4.0 NT 3.5)

2. Agenda  SNA & Host Integration Server Application Integration Scenari Scenari  Funzionalità di Host Integration Server 2004 per l’integrazione applicativa  Windows Initiated Processing (WIP)  Host Initiated Processing (HIP) - cenni

3. IBM Platform Interoperability  IBM Mainframe and AS/400 Platforms Daily operations (mission-critical apps and data) Daily operations (mission-critical apps and data) “Vital” information to run organization “Vital” information to run organization  Windows Platform Build new LOB apps Build new LOB apps Visual Studio Visual Studio.NET Framework.NET Framework Windows 2000/2003 Datacenter Windows 2000/2003 Datacenter  Co-existence = integration

4. IBM Platform Integration  Extending Host Systems IBM Mainframe IBM Mainframe IBM Midrange (AS/400, AIX) IBM Midrange (AS/400, AIX)  Microsoft Technologies Host Integration Server 2004 (ex SNA Server) Host Integration Server 2004 (ex SNA Server) COM+,.NET Framework, Visual Studio COM+,.NET Framework, Visual Studio SQL Server, MSMQ SQL Server, MSMQ BizTalk Server & Adapters BizTalk Server & Adapters

5. Application Integration scenario

6. Internal Applications (any platform) Process BizTalk Orchestration B2B Trading Partners (any platform) BizTalk Messaging MSMQ.NET or COM Web Service Web Service Mainframe AS/400 HIS Microsoft Integration Platform

7. IMS Terminal IMS Control Region IMS Message Queue IMS DB IMS TP CICS Mirror TP CSMI TCP/IP Listener DB2VSAM COMMAREA Linked to CICS TP Mainframe.NET or COM+ Component TI Proxy Metadata ASP.NET TI Runtime Business Process COMTI Component Builder Windows Server LU6.2 or TCP/IP Network APPC TCP/IP MSDTC COMTI Manager (RE) Application Integration TI Scenario

8. Application Integration Benefits of TI  “Wraps” CICS and IMS apps as Windows objects  Enables Windows developers to: Build n-tier applications that integrate Windows with IBM CICS and IMS transactions Build n-tier applications that integrate Windows with IBM CICS and IMS transactions Access host transactions without learning host programming—Component Builder Access host transactions without learning host programming—Component Builder Extend scope of Windows transactions to include CICS/IMS via 2PC Extend scope of Windows transactions to include CICS/IMS via 2PC Use either LU 6.2 or TCP/IP transports Use either LU 6.2 or TCP/IP transports  Requires no host footprint or host re-writes!

9. Client HIS Server MSMQ Bridge MQ Series Client MSMQ LU6.2 MVS, VSE AS/400 Unix OpenVMS MSMQ HIS 2000/2004 Server MSMQ-to-MQ Series Bridge TCP App

10. MSMQ-MQSeries Bridge  Transactional Bridging  Supports MQSeries v2 and v5  MSMQ Encryption from Client to Bridge InformationServerInformationServer RoutingServerRoutingServer Client Proxy Server Server QueueManagerQueueManager MSMQ Server MSMQConnectorMSMQConnector Microsoft MSMQ- MQSeries Bridge Microsoft MSMQ- MQSeries Bridge IBMMQSeriesIBMMQSeries Windows NT IBM MVS/ESA HP-UX Sun Solaris AIX AS/400 Digital OpenVMS (VAX & AXP)

11. Windows Server Application Integration Sending Messages with Bridge Mainframe, AS/400, RS/6000, UNIX, etc. MQSeries Application MQGET() MQSeries Server Delivers to destination queue MSMQ-MQSeries Bridge Take from connector queue, converts and forwards to MQSeries MSMQ Application MQCreateQueue() MQOpenQueue() MQSendMessage() MSMQ Stores on connector queue

12. Windows Server Application Integration Receiving Messages with Bridge Mainframe, AS/400, RS/6000, UNIX, etc. MQSeries Application MQOPEN() MQPUT() MQSeries Server Delivers to destination queue MQSeries Stores on transmission queue MSMQ-MQSeries Bridge Takes from transmission queue, converts and forwards to MSMQ MSMQ Application MQReceiveMessage() MSMQ Destination Queue

13. Application Integration Messaging Bridge  MSMQ 1.0 and 2.0  MQSeries Client NT 2.1 and 5.1  Integrated Setup and Administration  WMI Provider  Encryption - MSMQ Clients and Bridge  Documentation

14. Integrating Host Apps with.NET Framework Overview

15. IMS Terminal IMS Control Region IMS Message Queue IMS DB IMS TP CICS Mirror TP CSMI TCP/IP Listener DB2VSAM COMMAREA Linked to CICS TP Mainframe.NET or COM+ Component TI Proxy Metadata ASP.NET TI Runtime Business Process COMTI Component Builder Windows Server LU6.2 or TCP/IP Network APPC TCP/IP MSDTC COMTI Manager (RE) Mainframe Applications Transaction Integrator (ex COMTI)

16. Mainframe Applications Transaction Integrator for.NET  Bi-direction Mainframe App Integration WIP: Publish Host Apps as XML Web Services WIP: Publish Host Apps as XML Web Services HIP: Invoke Managed Server Apps from Host TPs HIP: Invoke Managed Server Apps from Host TPs  TI Designer Runs within Visual Studio IDE Runs within Visual Studio IDE Import/Export Managed Assemblies Import/Export Managed Assemblies Build TI Projects as part of VS Solutions Build TI Projects as part of VS Solutions  TI Runtime Supports managed execution of WIP and HIP scenarios Supports managed execution of WIP and HIP scenarios Executes within context of ASP.NET Executes within context of ASP.NET Converts Host Data Types to/from.NET CLS Data Types Converts Host Data Types to/from.NET CLS Data Types

17. AS/400 Applications Transaction Integrator  Publish AS/400 Apps as XML Web Services  Access AS/400 Apps from COM or.NET clients  TI Designer Import/Export RPG o Cobol Import/Export RPG o Cobol Display Relationship between Data Types Display Relationship between Data Types Specify.NET or COM Interfaces Specify.NET or COM Interfaces Simple Programming Model Simple Programming Model  TI Runtime Distributed Program Call Distributed Program Call Converts AS/400 types (as RPG, COBOL) Converts AS/400 types (as RPG, COBOL) Converts Windows types (COM and.NET CLS) Converts Windows types (COM and.NET CLS)

18. Host Initiated Processing Transaction Integrator  Host Clients call Windows Servers Batch process return to sender response Batch process return to sender response Allows Asynchronous (over Synch) Allows Asynchronous (over Synch) Data movement and migration Data movement and migration  Architecture Administration (Apps, LEs, HEs, Object Views) Administration (Apps, LEs, HEs, Object Views) Runtime Services Runtime Services Multiple Listeners Multiple Listeners Data Conversion and Method Resolution (Data, End Point, TRM) Data Conversion and Method Resolution (Data, End Point, TRM) No DTC Transactions No DTC Transactions Security Security Use TRM (Transaction Request Message) for CICS Use TRM (Transaction Request Message) for CICS Use IRM (IMS Request Message) for IMS Connect Use IRM (IMS Request Message) for IMS Connect Designer Designer Host to Windows data type conversions Host to Windows data type conversions Source code Import and Export Wizards Source code Import and Export Wizards

19. Integrating Host Apps with.NET Framework approfondimenti

20. Overview of Application Integration  Transaction Integrator (TI) allows for communication between Windows and mainframe or AS/400 programs using COM or.Net – no need for TCP/IP Sockets or APPC programming  Comprised of three parts – TI Designer – to create a COM typelib or.Net assembly describing the methods and data to be exchanged TI Designer – to create a COM typelib or.Net assembly describing the methods and data to be exchanged TI Manager – to configure the PC and host environments TI Manager – to configure the PC and host environments TI Runtime – installed with TI Manager when installing via HIS 2004 Server Enterprise Edition TI Runtime – installed with TI Manager when installing via HIS 2004 Server Enterprise Edition  Connectivity to mainframe via LU 6.2 or TCP/IP  Connectivity to AS/400 via TCP/IP  Supports two-phase commit over LU 6.2  Comes with a tutorial called CedarBank in the SDK  Tightly integrated with Visual Studio.Net

21. CedarBank Tutorial  Tutorial is installed with the HIS 2004 SDK  Default location: C:\Program Files\Microsoft Host Integration Server \SDK\Samples\AppInt\HostInitiated C:\Program Files\Microsoft Host Integration Server \SDK\Samples\AppInt\HostInitiated C:\Program Files\Microsoft Host Integration Server \SDK\Samples\AppInt\WindowsInitiated C:\Program Files\Microsoft Host Integration Server \SDK\Samples\AppInt\WindowsInitiated  All CICS and IMS information is included for Windows and for the Mainframe  Sample RPG code is included for the AS/400  For WIP - Cedrbank and GetAccounts methods  For HIP – Cedrbank method

22. TI Designer  New TI project type hosted in Visual Studio.NET Seamless integration with Visual Studio.Net Seamless integration with Visual Studio.Net Participates in.Net solutions and projects Participates in.Net solutions and projects  TI object definition COBOL / RPG Import Wizard COBOL / RPG Import Wizard Can build methods and parameters manually Can build methods and parameters manually  Data mapping COBOL to.NET / COM COBOL to.NET / COM RPG to.NET / COM RPG to.NET / COM Elemental Data Types (strings, integers) Elemental Data Types (strings, integers) Aggregates (data tables, structures) Aggregates (data tables, structures)

23. TI Designer Project

24. TI Manager  Includes the following MMC Snap-ins: Transaction Integrator (to manage WIP and HIP objects) Transaction Integrator (to manage WIP and HIP objects) Component Services (for TI COM objects) Component Services (for TI COM objects) IIS (for TI.Net WIP objects) IIS (for TI.Net WIP objects)  Operation Mode (right-click Transaction Integrator) Create/Edit Create/Edit Read-only Read-only  Write mode timeout setting (Transaction Integrator Properties) Default – 10 minutes Default – 10 minutes Maximum Value – 600 minutes Maximum Value – 600 minutes

25. TI Manager

26. Windows Initiated Processing (WIP)  Client program on Windows initiates call to host program  Mainframe – CICS or IMS - LU 6.2 or TCP/IP  AS/400 – RPG programs – TCP/IP only  Use TI Designer within VS.Net to build a COM type library or a.Net assembly that is called from a client program  TI Runtime uses the typelib or assembly to translate the incoming client data, send the data to the host, and translate the returned host data to send back to the client  TI Manager is an MMC Snap-in used for defining host information such as IP address or LU names

27. Host Initiated Processing Overview  Client program on host initiates a call to a Windows program  Mainframe – CICS or IMS - LU 6.2 or TCP/IP  AS/400 – RPG programs – TCP/IP only  Use TI Designer within VS.Net to build a COM type library or a.Net assembly  Program a dll that implements the methods exposed in the typelib or assembly  TI Runtime uses the typelib or assembly to translate the incoming host data, send the data to the Windows server program, and translate the returned data to send back to the host  TI Manager sets up a Windows Service that listens for incoming calls from the host

28. Diagnostics TI Internal TracingTI Internal Tracing Traces specific HIP object(s) or all WIP objectsTraces specific HIP object(s) or all WIP objects Controlled through TI ManagerControlled through TI Manager Right-click specific HIP application – Tracing…Right-click specific HIP application – Tracing… Right-click Windows Initiated Processing – Tracing…Right-click Windows Initiated Processing – Tracing… Dynamic starting and stopping of tracingDynamic starting and stopping of tracing Protocol TracingProtocol Tracing TCP/IP – Netmon or NetcapTCP/IP – Netmon or Netcap SNA – SNA Trace UtilitySNA – SNA Trace Utility SNA Application – LU 6.2 Messages – APPC APISNA Application – LU 6.2 Messages – APPC API SNA Server – LU 6.2 MessagesSNA Server – LU 6.2 Messages Application Event LogApplication Event Log

29. Diagnostics: WIP tracing

30. Diagnostics: HIP tracing

31. SNA tracing

32. In sintesi  Host Integration Server è la piattaforma abilitante per integrare il mondo Windows con le applicazioni presenti in ambiente IBM  Windows Initiated Processing (WIP) consente ad un programma Windows di “chiamare” un programma residente su mainframe o AS/400  Host Initiated Processing (HIP) consente ad un programma mainframe o AS/400 di invocare un programma Windows  I tool e le tecnologie di HIS consentono la piena integrazione applicativa tra l’ambiente di sviluppo.NET, i Windows Server e il mondo IBM

33. Riferimenti e risorse  Information & Evaluation http://www.microsoft.com/hiserver http://www.microsoft.com/hiserver http://www.microsoft.com/hiserver  Product documentation http://www.microsoft.com/hiserver/techinfo/productdoc/ default_2004.asp http://www.microsoft.com/hiserver/techinfo/productdoc/ default_2004.asp http://www.microsoft.com/hiserver/techinfo/productdoc/ default_2004.asp http://www.microsoft.com/hiserver/techinfo/productdoc/ default_2004.asp  MSDN Development Center & HIS SDK http://msdn.microsoft.com/library/library/en- us/his_2004Def/htm/his2004_def_portal_page.asp http://msdn.microsoft.com/library/library/en- us/his_2004Def/htm/his2004_def_portal_page.asp http://msdn.microsoft.com/library/library/en- us/his_2004Def/htm/his2004_def_portal_page.asp http://msdn.microsoft.com/library/library/en- us/his_2004Def/htm/his2004_def_portal_page.asp  Host Integration Server Resource Kit ISBN: 0-7356-1185-8 ISBN: 0-7356-1185-8 http://mspress.microsoft.com http://mspress.microsoft.com http://mspress.microsoft.com

34. © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.