Version 3.0.2 ReadMe
4
MosReplicationService.exe - Optional. Only required if you want to use MOS item
replication.
LicenseManager.exe - Optional. Only required if you want to access MOS Gateway license
information remotely over the network.
LicenseServerService.exe - Optional. Only required if you want to access MOS
Gateway license information remotely over the network.
MosAdmin.exe - Optional. Only required if you wish to configure MOS item replication
remotely over the network.
MosAdminService.exe - Optional. Only required if you wish to configure MOS item
replication remotely over the network.
MosConfigService.exe - Exception not required.
RegRGS.exe - Exception not required.
regtlb.exe - Exception not required.
TraceLogService.exe - Exception not required.
Hardware and Software Changes for Version 3.0.2
This following changes were made to iNEWS MOS Gateway version 3.0.2.
Installation
In previous versions of MOS Gateway 3, uninstalling the Gateway from a machine that had been
virtualized with VMware or imaged with Ghost could result in corruption of needed registry keys.
When this occurred the PC or server would fail to boot after uninstall. This issue is fixed. The
uninstaller no longer corrupts the registry keys.
If MOS Gateway 3.0.0 or 3.0.1 is installed, the 3.0.2 installer should be used to upgrade the
previous install. The 3.0.0 and 3.0.1 uninstallers should not be used.
Stories
In previous versions of MOS Gateway, some normal text would be replaced by presenter text as
part of roStorySend. This is fixed.
In previous versions of MOS Gateway, tabs in the story body could be mishandled when NSMLX
was not enabled. This is fixed.
Replication
In previous versions of MOS Gateway, MOS replication would only replicate tags that were
present in a pre-defined list of tags. This is fixed. MOS replication can now replicate all tags
contained in the incoming message.
An asterisk XPath statement can be used to replicate tags that contain multiple levels of children,
like mosExternalMetadata or objPaths. This statement can only be used in the attachment sections
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.
Kommentare zu diesen Handbüchern