Please enable JavaScript to view this site.

Altova SchemaAgent 2020

» No topics above this level «

SchemaAgent Server

Scroll Home Prev Top Next More

SchemaAgent Server reads information about the supported files in a folder you identify (and optionally in that folder's sub/folders)—the search path. SchemaAgent Server determines the relationships between, and creates an internal map of these files and their components. You can define multiple search paths.

 

You can administer the relationships between one or more files in the defined search paths from within the SchemaAgent Client GUI. The relationships between files can be modified using SchemaAgent clients, and the modified relationships are propagated through the affected file via SchemaAgent Server. Information about the files in the search path(s) and the relationships between these files is then served to SchemaAgent clients that connect to SchemaAgent Server.

 

SchemaAgent Server processes client requests to create, update, or delete schema IIRs (Includes, Imports, and Redefines) and references between schemas and supported files, and manages the communication between SchemaAgent Server and its clients. IIR (Include, Import, and Redefine) relationships between files can be modified and files can be deleted in SchemaAgent clients. These modifications and deletions are implemented in the actual files via SchemaAgent Server. SchemaAgent Server processes client requests to create, update, or delete schema IIRs (Includes, Imports, and Redefines) and to manipulate files, and it manages the communication between SchemaAgent Server and its clients.

 

SchemaAgent clients use the internal map that is created in SchemaAgent Server. This map is created or updated when: (i) a new search path is created, or (ii) an existing search path is modified within SchemaAgent Server; or (iii) SchemaAgent Server is started with search paths already defined. If the contents of a folder are physically modified (for example, if a file is physically deleted from the repository—and not from within a SchemaAgent client) after SchemaAgent Server has been started, then SchemaAgent Server's internal schema map is not automatically updated, and SchemaAgent clients will continue to use the original map.

 

Note: SchemaAgent Server and its clients transfer data using UDP and TCP over port 2799.

© 2019 Altova GmbH