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
2.1 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 |
47.0 | 10.2 | FC | 17.0 | FC | 46.6 | PCFoot 1 | 5.0 | FCFoot 2 | 10.4 | FCFoot 3 |
10.2 | FC | 16.4 | FC | 46.6 | PCFoot 1 | 5.0 | FC Foot 2 | 10.4 | FC Foot 3 | |
10.1 | PCFoot 4 | 16.3 | PC | 46.5 | NC | 4.5 | FCFoot 5 | 10.3 | PCFoot 3 | |
16.2 | PC | <4.5 | NC | 10.2 | PCFoot 3 | |||||
46.9.3 | 10.2 | FC | 17.0 | FC | 46.6 | PCFoot 6 | 5.0 | FCFoot 2 | 10.4 | FCFoot 3 |
10.2 | FC | 16.4 | FC | 46.6 | PCFoot 6 | 5.0 | FCFoot 2 | 10.4 | FCFoot 3 | |
10.1 | PCFoot 4 | 16.3 | PC | 46.5 | NC | 4.5 | FCFoot 7 | 10.3 | PCFoot 3 | |
16.2 | PC | <4.5 | NC | 10.2 | PCFoot 3 | |||||
46.9 | 10.1.x | FC | 17.0 | FC | 46.6Foot 8 | FC | 5.0 | FCFoot 2 | 10.4 | FCFoot 9 |
10.1.x | FC | 16.4 | FC | 46.6Foot 8 | FC | 5.0 | FCFoot 2 | 10.4 | FCFoot 9 | |
10.0.x | NC | 16.3 | PC | 46.5 | NC | 4.5Foot 10 | FCFoot 11Foot 7 | 10.3 | FCFoot 9 | |
16.2 | PC | <4.5 | NC | 10.2.1 | NC | |||||
16.1 | NC | |||||||||
46.8 | 10.1 | FC | 17.0 | NC | 46.6Foot 8 | FC | 4.5Foot 10 | FCFoot 12 | 10.4 | FCFoot 9 |
10.1 | FC | 16.4 | NC | 46.6Foot 8 | FC | 4.5Foot 10 | FCFoot 12 | 10.4 | FCFoot 9 | |
16.3 | FC | 46.5 | PC | 10.3 | FCFoot 9 | |||||
16.2 | PC | 10.2.1 | FCFoot 9 | |||||||
16.1 | PC | 10.1 | NC | |||||||
46.7 | 10.1 | FC | 17.0 | NC | 46.6Foot 8 | FC | 4.5Foot 10 | FCFoot 13 | 10.4 | FCFoot 9 |
10.1 | FC | 16.4 | NC | 46.6Foot 8 | FC | 4.5Foot 10 | FCFoot 13 | 10.4 | FCFoot 9 | |
16.3 | FC | 46.5 | PC | 10.3 | FCFoot 9 | |||||
16.2 | PC | 10.2 | FCFoot 9 | |||||||
16.1 | PC | 10.1 | FCFoot 9 | |||||||
10.0 | NC | |||||||||
46.6 | 10.1 | FC | 16.4 | NC | 46.6 | FC | 4.5Foot 10 | FCFoot 13 | 10.4 | FCFoot 9 |
16.3 | PC | 46.5 | PC | 10.3 | FCFoot 9 | |||||
16.2 | FC | 46.3 | PC | 10.2 | FCFoot 9 | |||||
16.1 | PC | 10.1 | FCFoot 9 | |||||||
10.0 | NC | |||||||||
46.5 | 10.1 | FC | 16.4 | NC | 46.6 | FC | 4.5Foot 10 | FCFoot 13 | 10.4 | FCFoot 9 |
10.0 | PC | 16.3 | PC | 46.5 | FC | 10.3 | FCFoot 9 | |||
16.2 | FC | 46.3 | PC | 10.2.1 | FCFoot 9 | |||||
16.1 | FC | 46.2 | PC | 10.2 | FCFoot 9 | |||||
16.0 | PC | 10.1 | FCFoot 9 | |||||||
10.0 | NC | |||||||||
46.4 | 10.1 | FC | 16.2 | FC | 46.6 | NC | 4.5Foot 10 | FCFoot 14 | 10.2.1 | FCFoot 9 |
10.0 | NC | 16.1 | FC | 46.5 | PC | 10.2 | FCFoot 9 | |||
16.0 | NC | 46.3 | FC | 10.1 | FCFoot 9 | |||||
46.2 | NC | 10.0 | NC | |||||||
46.3 | 10.1 | FC | 16.2 | FC | 46.6 | FC | 4.5Foot 10 | FCFoot 14 | 10.2.1 | FCFoot 9 |
10.0 | PC | 16.1 | FC | 46.5 | PC | 10.1 | FCFoot 9 | |||
16.0 | PC | 46.3 | FC | 10.0 | FCFoot 9 | |||||
15.0 | PC | 46.2 | PC | 9.0 | FCFoot 9 | |||||
46.0 | PC | |||||||||
46.2 | 10.0 | FC | 16.0 | FC | 46.5 | PC | 4.5Foot 10 | FCFoot 15 | 10.2.1 | FCFoot 9 |
9.0 | NC | 15.0Foot 9 | PC | 46.3 | NC | 10.2 | FCFoot 9 | |||
14.0 | NC | 46.2 | FC | 10.1 | FCFoot 9 | |||||
46.0 | PC | 10.0 | FCFoot 9 | |||||||
45.0 | PC | 9.0 | FCFoot 9 |
Footnote 1 EMS 46.6.2 and above are fully compatible with EAGLE. In case of automatic resynchronization failure, there is an option to do the manual resynchronization. Automatic resynchronization can be initiated in following cases:
- On EAGLE addition
- Change of EAGLE southbound protocol (TL1 to SNMP or SNMP to TL1)
- EMSALM connection breaks and a switch to next configured EMSALM terminal
- 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 2 FTRA 5.0 is tested with JAVA JDK Version 13.0.2 for Linux and JRE 1.8.0_321 for Windows.
Footnote 3 J7 support not available for PIC
Footnote 4 Compatible up to LNP database capacity of 504M. ELAP 10.2 is required for LNP database capacity of 756M.
Footnote 5 FTRA 4.5 is tested with JAVA JDK Version 13.0.2 for Linux and JRE 1.8.0_321 for Windows.
Footnote 6 EMS 46.6.3 and above are fully compatible with EAGLE
Footnote 7 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 8 Only EMS 46.6.2 and later are compatible with the indicated EAGLE release.
Footnote 9 J7 Point Code format is NOT supported on PIC or EPAP 15.0.
Footnote 10
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 11 From EAGLE 46.9, FTRA is not supported on Unix servers.
Footnote 12 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 13 FTRA 4.5 is tested with JAVA version 8 update 121.
Footnote 14 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 15 FTRA 4.5 is tested with JAVA version 1.8.0_31-b13.
2.2 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 |
46.6 | 17.0 | FC | 13.5 | FC |
16.4 | FC | 13.5 | FC | |
16.3 | FC | 13.4 | FC | |
16.2 | FC | 13.3 | FC | |
16.1 | PC | 13.2 | FC | |
13.1 | PC | |||
46.5 | 17.0 | PC | 13.5 | FC |
16.4 | NC | 13.5 | FC | |
16.3 | PC | 13.4 | FC | |
16.2 | FC | 13.3 | FC | |
16.1 | PC | 13.2 | FC | |
13.1 | PC | |||
46.3 | 17.0 | NC | 13.3 | PC |
16.2 | PC | 13.3 | PC | |
16.1 | FC | 13.2 | FC | |
16.0 | PC | 13.1 | PC | |
13.0 | PC | |||
46.2 | 16.0 | FC | 13.1 | FC |
13.0 | FC |
2.3 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 |
13.5 | 10.2 | FC |
10.1 | PCFoot 16 | |
13.4 | 10.2 | PC |
10.1 | FC | |
10.0 | PCFoot 17 | |
13.3 | 10.2 | PC |
10.1 | FC | |
10.0 | PCFoot 17 | |
13.2 | 10.1 | FC |
10.0 | PCFoot 17 |
Footnote 16 Compatible up to LNP database capacity of 504M. ELAP 10.2 is required for LNP database capacity of 756M.
Footnote 17 Partially Compatible up to 384M database capacity; Not Compatible greater than 384M database capacity.