RSSDaemon

The effects RSSDaemon has on the host machine

Once the spawndaemon installs RSSDaemon as a Windows Service, it should start automatically and should not be disabled or removed from Windows Services. The RSSDaemon has a very small footprint and there is no measurable performance degradation as a result of the install. The RSSDaemon will be listening on the IP port 6502 and waiting for the RC Nexus server calls to come in. The RSSDaemon only enhances the remote connectivity and it does not take away our ability to dial in via traditional means.

Sometimes you see errors in the Windows System Event log that indicate that the RSSDaemon has ended unexpectedly. That is a normal occurrence and is a consequence of the way RSSDaemon deals with Windows networking.

Network Security Implications

In situations when you are installing the RSSDaemon on a site with the developed sense of IT and Network security, the presence of the RSSDaemon may raise some questions. An alert IT or Network Manager should note that there is a new IP port open on Creo machines. They will surely ask you about the security implications.

You can tell them that the port is a new Creo Service Port and that it pretty harmless. It uses telnet type communication channel to connect to RSS Server in RC. It is passive, meaning it will not initiate any connections on it’s own. The port is not secured at this point, but we are working on the new version of Creo Service Port application that will come this summer, and which will be fully secured and all communication channels to it will be encrypted.