2 Product-Wise Compatibility

This section defines the following release specific compatibilities:

Legend

The following terms are used to define the product compatibilities:

  • FC: Fully Compatible
  • PC: Partially Compatible. Product combinations are functional but have not undergone complete regression testing. Some feature capabilities may not be fully functional or supported. Partial Compatibility is provided to support the short period of time while customers upgrade components of the EAGLE product family.
  • NC: Not Compatible

EAGLE Compatibility

The following table defines compatibility of EAGLE with different products:

Table 2-1 EAGLE Compatibility Matrix

EAGLE ELAP EPAP EMS FTRA PIC
Release Release Compatibility Release Compatibility Release Compatibility Release Compatibility Release Compatibility
48.0 11.0 FC 17.1 FC 47.0 FC 5.1 FCFoot 1 10.5 FCFoot 4
10.2 FC 17.0 FC 46.6 NC 5.0 FC 10.4 FCFoot 4
10.1 PC Foot 6 16.4 PC 46.5 NC     10.3 PCFoot 4
    16.3 PC         10.2 PCFoot 4
47.1 11.0 FC 17.1 PC Foot 2 47.0 FC 5.1 FCFoot 3 10.4 FC Foot 4
10.2 FC 17.0 FC 46.6 FCFoot 5 5.0 FC 10.3 NC
    16.4 FC     4.5 NC    
10.1 PC Foot 6 16.3 PC 46.5 NC <4.5 NC 10.2 NC
47.0 11.0 FC 17.1 PC Foot 7 47.0 FC 5.1 FCFoot 8 10.4 FCFoot 4
10.2 FC 17.0 FC 46.6 PC Foot 9 5.0 FC Foot 10 10.4 FC Foot 4
10.1 PC Foot 6 16.4 FC 46.5 NC 5.0 FC Foot 10 10.3 PC Foot 4
    16.3 PC <4.5 NC 4.5 FCFoot 11 10.2 PC Foot 4
    16.2 PC            
46.9.3 11.0 FC 17.0 FC 47.0 FC 5.0 FC Foot 10 10.4 FC Foot 4
10.2 FC 16.4 FC 46.6 PCFoot 12 5.0 FC Foot 10 10.4 FC Foot 4
10.1 PC 16.3 PC 46.5 NC 4.5 FCFoot 13 10.3 PC Foot 4
    16.2 PC     <4.5 NC 10.2 PC
46.9 11.0 PC Foot 6 17.0 FC 47.0 FC 5.0 FC Foot 10 10.4 FC Foot 14
10.1.x FC 16.4 FC 46.6 Foot 15 FC 5.0 FC Foot 10 10.4 FC Foot 14
10.0.x NC 16.3 PC 46.5 NC 4.5Foot 16 FCFoot 17 Foot 13 10.3 FC Foot 14
    16.2 PC     <4.5 NC 10.2.1 NC
    16.1 NC            
46.8 11.0 PC Foot 6 17.0 NC 47.0 FC 4.5 Foot 16 FCFoot 18 10.4 FC Foot 14
10.1 FC 16.4 NC 46.6 Foot 19 FC 4.5 Foot 16 FC Foot 18 10.4 FC Foot 14
    16.3 FC 46.5 PC     10.3 FC Foot 14
    16.2 PC         10.2.1 FC Foot 14
    16.1 PC         10.1 NC
46.7 10.1 FC 17.0 NC 47.0 FC 4.5 Foot 16 FCFoot 20 10.4 FC Foot 14
10.1 FC 16.4 NC 46.6 Foot 21 FC 4.5 Foot 16 FC Foot 20 10.4 FC Foot 14
    16.3 FC 46.5 PC     10.3 FC Foot 14
    16.2 PC         10.2 FC Foot 14
    16.1 PC         10.1 FC Foot 14
                10.0 NC
46.6 10.1 FC 16.4 NC 47.0 FC 4.5 Foot 16 FC Foot 20 10.4 FC Foot 14
    16.3 PC 46.6 FC     10.3 FC Foot 14
    16.2 FC 46.5 PC     10.2 FC Foot 14
    16.1 PC 46.3 PC     10.1 FC Foot 14
                10.0 NC
46.5 10.1 FC 16.4 NC 47.0 PC 4.5 Foot 16 FC Foot 20 10.4 FC Foot 14
10.0 PC 16.3 PC 46.6 FC     10.3 FC Foot 14
    16.2 FC 46.5 FC     10.2.1 FC Foot 14
    16.1 FC 46.3 PC     10.2 FC Foot 14
    16.0 PC 46.2 PC     10.1 FC Foot 14
                10.0 NC
46.4 10.1 FC 16.2 FC 46.6 NC 4.5 Foot 16 FCFoot 22 10.2.1 FC Foot 14
10.0 NC 16.1 FC 46.5 PC     10.2 FC Foot 14
    16.0 NC 46.3 FC     10.1 FC Foot 14
        46.2 NC     10.0 NC
46.3 10.1 FC 16.2 FC 46.6 FC 4.5 Foot 16 FC Foot 22 10.2.1 FC Foot 14
10.0 PC 16.1 FC 46.5 PC     10.1 FC Foot 14
    16.0 PC 46.3 FC     10.0 FC Foot 14
    15.0 PC 46.2 PC     9.0 FC Foot 14
        46.0 PC        
46.2 10.0 FC 16.0 FC 46.5 PC 4.5 Foot 16 FCFoot 23 10.2.1 FC Foot 14
9.0 NC 15.0 Foot 14 PC 46.3 NC     10.2 FC Foot 14
    14.0 NC 46.2 FC     10.1 FC Foot 14
        46.0 PC     10.0 FC Foot 14
        45.0 PC     9.0 FC Foot 14

Footnote 1 FTRA 5.1 is tested with JAVA JDK Version 13.0.2 for Linux and JRE 1.8.0_321 for Windows.

Footnote 2 EAGLE 47.1 and 47.0 support an MNP database capacity up to 495M entries.

Footnote 3 FTRA 5.1 is tested with JAVA JDK Version 13.0.2 for Linux and JRE 1.8.0_321 for Windows.

Footnote 4 J7 support not available for PIC

Footnote 5 In case of automatic resynchronization failure, there is an option to do the manual resynchronization. Automatic resynchronization can be initiated in following cases:

  1. On EAGLE addition
  2. Change of EAGLE southbound protocol (TL1 to SNMP or SNMP to TL1)
  3. EMSALM connection breaks and a switch to next configured EMSALM terminal
  4. Eagle sends an auto-resync message to EMS

Practically for production system, customers will see automatic resync fail when they do EAGLE addition for the first time.

Footnote 6 Compatible up to LNP database capacity of 504M. ELAP 10.2 is required for LNP database capacity of 756M.

Footnote 7 EAGLE 47.1 and 47.0 support an MNP database capacity up to 495M entries.

Footnote 8 FTRA 5.1 is tested with JAVA JDK Version 13.0.2 for Linux and JRE 1.8.0_321 for Windows.

Footnote 9 EMS 46.6.2 and above are fully compatible with EAGLE

Footnote 10 FTRA 5.0 is tested with JAVA JDK Version 13.0.2 for Linux and JRE 1.8.0_321 for Windows.

Footnote 11 FTRA 4.5 is tested with JAVA JDK Version 13.0.2 for Linux and JRE 1.8.0_321 for Windows.

Footnote 12 EMS 46.6.3 and above are fully compatible with EAGLE

Footnote 13 FTRA 4.5 is tested with JAVA JDK version 13.0.2 for Linux and JRE 1.8.0_261-b12 for Windows server.

Footnote 14 J7 Point Code format is NOT supported on PIC or EPAP 15.0.

Footnote 15 Only EMS 46.6.2 and later are compatible with the indicated EAGLE release.

Footnote 16 The latest build of FTRA 4.5 is build 40.34.0 and can be found on My Oracle Support (MOS). Refer to the FTRA 4.5 Release Notes on Oracle Help Center for the bug fix content in that FTRA build.

Footnote 17 From EAGLE 46.9, FTRA is not supported on Unix servers.

Footnote 18 FTRA 4.5 is tested with JAVA version 12.0.1 for Linux and Windows servers and with JAVA version 1.8.0_211 for Unix servers.

Footnote 19 Only EMS 46.6.2 and later are compatible with the indicated EAGLE release.

Footnote 20 FTRA 4.5 is tested with JAVA version 8 update 121.

Footnote 21 Only EMS 46.6.2 and later are compatible with the indicated EAGLE release.

Footnote 22 FTRA 4.5 is tested with JAVA version 1.8.0_73-b02 installed on Windows 7 & 8, and 1.8.0_73-b02 installed on UNIX..

Footnote 23 FTRA 4.5 is tested with JAVA version 1.8.0_31-b13.

Note:

  • EPAP 17.1 will support 510M MNP DNs, and this capacity will remain unchanged with the introduction of APP-D cards in 2026
  • FTRA 5.1 and FTRA 5.0 are FC, provided the FTRA machine supports the required ciphers.
  • OS Platforms for FTRA 5.1:
    • Oracle Linux: Versions 8 & 9
    • Microsoft Windows: Versions 10

EMS Compatibility with EPAP and LSMS

The following table defines compatibility of EMS with EPAP and LSMS:

Table 2-2 EMS Compatibility with EPAP and LSMS

EMS EPAP LSMS
Release Release Compatibility Release Compatibility
47.0 17.1 FC 14.0 FC
17.0 FC 13.5 FC
16.4 FC 13.4 PC
16.3 PC    
46.6 17.1 PC 14.0 FC
17.0 FC 13.5 FC
16.4 FC 13.4 FC
16.3 FC 13.3 FC
16.2 FC 13.2 FC
16.1 PC 13.1 FC
46.5 17.1 PC 14.0 NC
17.0 NC 13.5 FC
16.4 NC 13.4 FC
16.3 PC 13.3 FC
16.2 FC 13.2 FC
16.1 PC 13.1 PC
46.3 17.0 NC 13.5 NC
16.2 PC 13.4 NC
16.1 FC 13.3 PC
16.0 PC 13.2 FC
    13.1 PC
    13.0 PC
46.2 16.0 FC 13.1 FC
    13.0 FC

LSMS Compatibility with ELAP

The following table defines compatibility of LSMS with ELAP:

Table 2-3 LSMS Compatibility with ELAP

LSMS ELAP
Release Release Compatibility
14.0 11.0 FC
10.2 FC
10.1 NC
13.5 11.0 NC
10.2 FC
10.1 PCFoot 24
13.4 11.0 NC
10.2 PC
10.1 FC
10.0 PCFoot 25
13.3 10.2 PC
10.1 FC
10.0 PC Foot 26
13.2 10.1 FC
10.0 PC Foot 27

Footnote 24 Compatible up to LNP database capacity of 504M. ELAP 10.2 is required for LNP database capacity of 756M.

Footnote 25 Partially Compatible up to 384M database capacity; Not Compatible greater than 384M database capacity.

Footnote 26 Partially Compatible up to 384M database capacity; Not Compatible greater than 384M database capacity.

Footnote 27 Partially Compatible up to 384M database capacity; Not Compatible greater than 384M database capacity.