Service Management includes basic web services for creating and managing objects and attributes, and common web services used by various ENOVIA applications, such as notifications.
In Service Management, ENOVIA products can be viewed as service components that can be used to create a loosely-coupled, plug-and-play architecture. The Service Administrator defines deployment definitions (the URL used to connect to an application hosting server) to configure which services are deployed on which application servers.
A web service defines an ENOVIA service, such as a Business Object, Policy, Notification, and so on. It is defined by service content and shared content. Service content is a logic folder that holds related service definition files that define the web interface or XML schema (widl/wsdl, xsd) or implementation files (.java, c#) for a specific web service. Shared content is the same, but can be used by multiple web services.
A service folder bundles related services together, or additional service folders. You can then assign the service folder to a specific service key instead of applying the individual services.