Altova Global Resources are portable references to files, folders, or databases. When stored as Global Resources, paths and database connection details become reusable and available across multiple Altova applications. For example, if you frequently need to open the same file in multiple Altova desktop applications, you may find it convenient to define it as a Global Resource. This way, you don't even need to remember the file path because you can select the respective Global Resource from the "Open File" dialog box instead. This also has the advantage that, if the file path ever changes, you will change it in one place only.
A typical usage of Global Resources is to define a database connection once and reuse it across all Altova applications that support Global Resources. For example, you can create a database connection on the machine where a MapForce mapping was designed and then reuse the same connection on the machine where MapForce Server runs the mapping (this may require, in some cases, that both machines have the same database client software installed).
Optionally, you can create multiple variations of the same Global Resource (known as "configurations"). This lets you easily switch file or folder paths (or even databases) depending on your needs. For example, you could create a "database" resource with two configurations: "development" and "production". Taking MapForce as example, you could then easily retrieve data from either the development or production database, by choosing the desired configuration from a list before previewing the mapping.
You can create Global Resources from the following Altova desktop applications: Altova Authentic, DatabaseSpy, MobileTogether Designer, MapForce, StyleVision, and XMLSpy. On the server side, Global Resources can be consumed by the following Altova server applications: FlowForce Server, MapForce Server, RaptorXML Server, RaptorXML+XBRL Server.
In MapForce, you can use Global Resources (be they file, folder, or database references) for various scenarios, for example:
•To supply a configurable file path as mapping input, see Example: Run Mappings with Variable Input Files.
•To redirect the mapping output to a configurable path. For more information, see Example: Generate Mapping Output to Variable Folders.
•To supply a configurable path to a StyleVision Power Stylesheet (.sps) file, if one is used by the mapping. For example, instead of referencing a plain StyleVision .sps file from the MapForce component settings, you could refer to an .sps file previously defined as a Global Resource, which has two possible configurations (let's say, "Website.sps" and "Print.sps"). See also Styling Mapping Output with StyleVision.
•To reuse a database connection. If a database has already been defined as a Global Resource (in any Altova application), you can connect to it without going through all the set-up steps again, see Using a Connection from Global Resources.
•To easily switch the database from which the mapping reads data, or the one to which the mapping writes data (provided that two or more databases have the same structure but different data, see Example: Switch Databases).
MapForce Basic Edition does not support consuming database connections defined as Global Resources.