1. Requirements & Migration
C:IBM/collateral/ibmtemplate/ce-clientfacing.ppt

2. Agenda
Requirements
Migration 2
© 2016 IBM
© 2016 IBM 2

3. ITX 9.0.0 Requirements Release notes
Detailed System Requirements No
Software Pre-Req’s
© 2016 IBM

4. ITX 9.0.0 New Supported Additions
WMQ 8.x
Informix 12
Sybase 16
Extreme Scale 8.6
Minimum Java version - 1.7
Windows 12 Server
Windows 10
Red Hat Enterprise Linux AS v7 Intel and System Z
SUSE Linux 12
SOAP 2.0
IIB v10.0
SI 5.2.6
Data Power still runs on WTX

5. ITX 9.0.0 Requirements Disk Space Memory
TX Design Studio – 2GB (recommended)
Min requirement 1GB (recommended)
ITX for Application Programming
ITX for Integration Servers
ITX with Command Server
ITX with Launcher
Product installation footprint varies around 400MB - 475MB
Memory
TX Design Studio – 1GB (recommended)
Consult the system requirements for IIB, BPM Advanced or Sterling Integration.

6. Migration Story… Version Year Backward compatibility from v5.0 onwards
1994
V1.1
1995
V1.2
V1.3
1996
V1.4
1997
V2.1
1999
V5.0
2000
V6.0
2001
V6.5
2002
V6.7
2003
V7.5
2004
V8.0
2005
V8.1
2006
V8.2
2007 V
2008
V8.3
2009 V
2010
V8.4
2011
2012
2013
Backward compatibility from v5.0 onwards

7. ITX Migration
Facts
Migration is a tedious process, No Silver bullet
Maps have to be tested on the new release and moved to production
Map updates (if any) have to go over the development, testing life cycle before production
Based on the number of the maps, migration may go from weeks to months.
Product have tools to make migration easier

8. ITX 9.0.0 Migration Artifacts Comments Maps (mmc & …)
Not required. Maps developed from v5.0 are portable. (exceptions are when defects are resolved over the years, map output may change and require attention)
System Files (msl)
Not Required.
Source Files (msd, mtt, mdq, mms)
Not Required
Resource Registry (mrc, mrn)
dtx.ini (configuration file)
Required. Customer has to manually merge any previous changes to the new INI file
Management Console Configurations (mgmtconsole.bin)

9. ITX 9.0.0 Migration Artifacts Comments
Event Server Administration files (LauncherAdmin.bin)
Not required.
SNMP Adminstration (snmpadmin.bin)
Not Required

10. Design Studio is 64-bit now, but no changes in look and feel
Steps in Place for Migration to v9.0 - Design Studio
Install ITX Design Studio on same system as previous versions
Use the Studio to import the projects in to the new workspace (make sure to import the source also
Export the Preferences in Previous Design Studio and Re-import them. For Database Interface Designer and Integration Flow Designer, the preferences have to be manually migrated.
Open and Save the TX related files
Steps in Place for Migration to v9.0 – Runtime
dtx.ini, Management Console configurations, Launcher Administration, Resource Registry files must be replicated for ITX v9.0 version and manually configured

11. Steps in Place for Migration to v9.0 – Runtime
Compiled maps, inputs must be replicated and go over the Testing phase before final deployment
IIB , Sterling B2B Integrator and BPM advanced integration should follow the product specific migration recommendations

12. Tools available for migration – Type Designer
Artifacts
Usage
Comments
tanalyze
analyzes and save the type trees
Recommended for migration of Type Trees to v9.0 format
timport
imports metadata definitions to type trees
Recommended when type tree artifacts are saved in textual format
texport
exports type trees to XML format
Recommended , if customer chooses to use textual format for source control management.

13. Tools available for migration – Map Designer
Artifacts
Usage
Comments
mcompile
compiles maps.
Recommended for migration of Maps to to v9.0 format
mimport
imports metadata definitions to map definitions
Recommended when map artifacts are saved in textual format
mexport
exports maps to XML format
Recommended , if customer chooses to use textual format for source control management.
mreport
generates reports in HTML format
Used as print map specifics

14. Tools available for migration – Integration Flow Designer
Artifacts
Usage
Comments
sdeploy
deploys systems
Recommended for migration of systems to to v9.0 format and deploy the systems to test or product platform
msdimport
imports metadata definitions to system definitions
Recommended when system artifacts are saved in textual format
msdexport
exports systems to XML format
Recommended , if customer chooses to use textual format for source control management.

15. Tools available for migration – Runtime
Artifacts
Usage
Comments
Command server
Invokes maps
Recommended for testing maps are part of migration
dtxPage
calculates suggested settings for memory page size and count for maps
Recommended for performance tuning of maps
ResourceRegistryHelper utilties
Updates MRN and MRC files

16. Migration Life Cycle – Option 1
V9.0 trees
XML
Type Trees
Analyze and Save
V9.0 mms
XML
maps
Analyze and Save
V9.0 trees
V9.0 mmc
V9.0 mms
Compile
Run & Compare 16

17. Migration Life Cycle – Option 1
V9.0 Systems
XML
Systems
Analyze and Save
Deploy 17

18. Migration Life Cycle – Option 2
V8.x trees
V9.0 mmc
V8.x mms
Compile
Run & Compare 18

19. Migration Life Cycle – Option 3
V8.x mmc
Run & Compare 19

20. WTX - Q & A

21. WTX