Servers >> Shared Servers

	Where did all the processes go?
	Why are my coordinate system names getting changed?
	Is there a limit to how long the Shared Services can be left to run?

Where did all the Shared Server processes go?

There used to be one process per type of data store you were licensed to access. We have folded the Data Store Descriptors into a single Shared Services process. In doing this fewer machine resources are needed and response time is greatly improves when your programs request a list of available projects or try to start data servers.

Back to Top ...

Why are my coordinate system names getting changed?

When you start a data server and check a project's coordinate systems, sometimes you will notice that the coordinate system's name isn't what you expect. When the data server requests a coordinate system, it provides as many parameters as it can to the Coordinate Service (one of the Shared Services). The Coordinate Service recognizes that the name isn't important -- the parameters are. If it finds a system with the same parameters, it simply uses it, regardless of the name. If that system uses different units for the surface or depth axes, it simply does the necessary unit conversions while using the existing system. In this way, we save a lot of resources in the Shared Services.

Back to Top ...

Is there a limit to how long the Shared Services can be left to run?

While it is true that certain objects, once created in the Shared Services, never go away until it is restarted, these objects are reused and should not take up significant resources under normal usage. The best examples here are the custom Coordinate Systems created by the Coordinate Service. These are only created if the parameters of a requested coordinate system aren't matched by a predefined system or by a custom system created since the SharedServices were last started. Hence, this should not be a problem and you should not have to restart the SharedServices to reduce resource usage.