Version 4.0 ReadMe
18
of the story, not in the story body. Any XPath statement that produces an XML element will result
in story save failures if used in the story body. For example:
"<mosExternalMetadata>%/mos/mosObj/MosExternalMetadata/*%</mosExternalMetadata>"
This example will replicate the complete contents of mosExternalMetadata. Only use this
statement in the attachments.
MOS Router Service
• In previous versions of MOS Gateway 3.0, empty MOS messages sent from devices could cause
MOS Router Service to terminate unexpectedly. This is fixed.
• In previous versions of MOS Gateway, MOS Router Service could exit or fail to start if one of the
configured devices was unreachable. This is fixed. MOS Router Service will now start correctly
and report that the device is unreachable.
Hardware and Software Changes for Version 3.0.1
The following changes were made to iNEWS MOS Gateway version 3.0.1.
MOS Router Service
• In previous versions of MOS Gateway, messages over 16KB would result in a MOS Router
Service crash. This is fixed. Message size is now limited to 32764 bytes when used with iNEWS
version 2.8.8 and earlier. Message size in iNEWS v3.0 and later is limited to 65,535 bytes.
Hardware and Software Changes for Version 3.0.0
The following changes were made to iNEWS MOS Gateway version 3.0.0.
roItemStat
• MOS Gateway now supports feeding item channels back to iNEWS. Anytime an <itemChannel>
tag is included in a roItemStat message, the text inside that element will be passed on to iNEWS as
the new item channel.
<mos>
<mosID>MOS</mosID>
<ncsID>NRCS</ncsID>
<roItemStat>
<roID>NRCS/SHOW.6PM.RUNDOWN</roID>
<storyID>64261505</storyID>
<itemID>MOS-Active</itemID>
<objID>12345</objID>
<status>READY</status>
<time>2009-11-16T16:55:08</time>
<itemChannel>A</itemChannel>
</roItemStat>
</mos>
Comentarios a estos manuales