RELEASE NOTES RELEASE NOTES. Version ID Delivery Date 23/04/2014. Product Technical Manager: Rodolfo Martín García

Transcription

1 Client Simware Version ID Delivery Date 23/04/2014 Product Technical Manager: Rodolfo Martín García Date Signature Project Manager: Jose Alberto R.A. Project QA Manager: Walid Kabbani Rihawi QA Manager: Walid Kabbani Rihawi Operations and projects manager: Jose María López Rodríguez 1

2 1 Release Content The content of the release is detailed next: - Simware RTI over DDS using OpenSplice o rtiexec1516 v2.1.1 o librti1516 v2.1.1 o libfedtime1516 v2.1.1 o krtishapes example v2.1.1 These elements contain: - Runtime Kit o o lib: Libraries necessary for running rtiexec1516 and applications (federates) bin: Executables binaries and configuration files necessary for running rtiexec1516, federates and examples. - Developer Kit o include: Headers required for building federates o doc: Documentation. - This release support all the features and services described at the standard IEEE1516 for an RTI, taking into account the limitations described at chapter 6 of this document. 2

3 2 Release Baseline All items tagged with SimwareRTI_

4 3 Release Highlights New feature: Inherited Publication/Subscription. Improved Save/Restore process. Now, it can be executed successfully in distributed systems. Changes in product license: It is supported a limited license included in Simware Platform for up to 4 federates and a SimwareRTI Pro license that handles unlimited federates. Backwards incompatibility with previous versions Improved Federation Data Management. Improved other RTI detection. Backwards incompatibility with previous versions VPN and Wan remote federates can join the federation FDD is now sent compressed, in order to avoid timeouts in joinfederationexecution service invocations over VPN & WAN. Backwards incompatibility with previous versions New deployment tree New Windows build supporting VS2008 Presagis integration. New Windows build with flags NON_SECURE_SCL=0 and HAS_ITERATOR_DEBUGGING=0 New Linux build g

5 4 Fixed Bugs and Changes ID Description Detecte d Test Scripts update Backwards Incompatibility krtishapes' Subscription, Save/Restore and Resigning ID Description Detecte d Backwards Incompatibility SimwareRTI: Save/Restore bugs fixing SimwareRTI: New feature: Inherited Publication/Subscription SimwareRTI: Installer shows boost package whereas installing SimwareRTI: Change License Mode Run 4 federates per rtiexec X 761 SimwareRTI: 'TurnUpdatesOn' callback not working ID Description Detecte d Backwards Incompatibility 438 SimwareRTI: Other SimwareRTI detection errors X 551 SimwareRTI: SubscribeObjectClassAttributes ReflectAttributeValues discordance 664 SimwareRTI: ReflectAttributeValues not always received after DiscoverObjectInstance 665 SimwareRTI: Fixing state machine OwnershipState SimwareRTI - Can only use default domain SimwareRTI: Federates receive data updates from all Federations X in the RTI 674 SimwareRTI: Sometimes some Object instances are discovered but not updated 688 SimwareRTI: Problem with xerces initialization in windows ID Description Detecte d 642 KRTISHAPES: Defectos menores identificados en SimwareRTI SimwareRTI: Don t send callback response when no response is expected Backwards Incompatibility 5

6 649 SimwareRTI: add void send method to invoker for one way X callbacks 651 SimwareRTI: Use named partitions for control & data X 660 SimwareRTI: Send FDD Compressed X 661 Preparacion de release de desarrollo SimwareRTI y Simware

7 5 Version limitations If a federate dies without completing the resign, the rtiexec may still shows the federate as federation member. There is a feature partially implemented to solve this issue, so the liveliness of the federates in the federation is checked with a configurable periodicity. Synchronization points management presents the next limitation: o To register synchronization points specifying an optional set of joined federates it is needed to know their handles in the federation execution, and these handles are provided at runtime; so it is necessary to implement a mechanism that allows to choose, from among the federates in the federation, the ones that are wanted to be synchronized. Save / Restore services implemented with the next limitations: o Restore federation state works only once, since the state files saved are removed in the restoring process. If a federate is subscribed to an interaction which also publishes, then this federate will receive the interactions sent by itself. Management Object Model (MOM) services partially implemented. Transportation data field for attributes and interactions specified in the FOM document is ignored: it is always set up as 'BestEffort', although it has been defined as 'Reliable'. Since version 2.1.0, with the inclusion of new feature of inherited publication/subscription, there is a bug related to instances discovery, such that sometimes an instance is discovered when it shall not be discovered. 7

8 6 Known Issues ID Description Detected 321 SimwareRTI: Registro de puntos de sincronizacion SimwareRTI: Remove inactive federates from federation (dead, network disconnected ) 760 SimwareRTI: Object Instance Discovery in forbidden case SimwareRTI: Problems with callback outputs in testkrti::mifederateambassador