Altova Global Resources

XMLSpy Global Resources

Altova Global Resources:

  • Map an alias to multiple resources via different configurations
  • Define files, database connections, and directory paths for different deployment scenarios
  • Switch between development, test, and production configurations at runtime
  • Manage different configurations for Altova server products
  • Share common files and processes among Altova products
  • Share database connection settings among Altova products
  • Invoke workflows that use various Altova applications to process data

What Are Global Resources?

Altova Global Resources are a collection of aliases for file, folder, and database resources. Each alias (i.e., Global Resource) can have multiple configurations, and each configuration maps to a single resource. There are three general applications for Global Resources:

 

 

Defining and Switching Deployment Scenarios

Deployment Scenarios

One of the most useful applications for Global Resources is defining configurations for different deployment environments. It's common practice for an organization to distinguish between development, testing, and production environments for servers, for instance: while an in-house application is still under development, the development team might use one database server, whereas another server is used for QA and testing, and a third server is used in the production environment with real end-user data.

In addition to database servers, you can specify files and folders to be used in various configurations. For instance, you may wish to specifiy a different XSLT file to be used for transformations in each scenario, and a different directory path for saving each transformation.

It's easy to add, edit, and delete Global Resources using the Manage Global Resources dialog, available in multiple Altova tools. Creating a Global Resource involves mapping one alias name to one or more resources (file, folder, or database). Each mapping is called a configuration. A single alias name can therefore be associated with several resources via different configurations.

Once the Global Resources are defined, it takes but one click to switch between configurations using the Global Resources toolbar.

Configuring Global Resources

 

 

Managing Configurations for Altova Server Products

Server Scenarios

Altova FlowForce Server and RaptorXML Server can also take advantage of Global Resources definitions to specifiy different files to use as inputs for processing, based on the specified configuration.

When Global Resources are defined in an Altova desktop developer tool such as XMLSpy or MapForce, the definitions are saved in a Global Resources XML file. To use a Global Resource as an input for processing, the Altova server job is configured with the name and location of the Global Resources XML file, as well as the alias and configuration to be used.

The advantage of using Global Resources is that resources can be changed quickly and easily by switching the name of the configuration.

Learn more:

Global Resources Diagram

 

 

Exchanging Information Between MissionKit Tools

Desktop Developer Tools

A Global Resource can not only be used to switch resources within an Altova application, but also to generate and use resources from other Altova applications. Since Global Resources are supported in numerous Altova products, you can share designs and output created by each tool seamlessly with the others, according to your project's requirements.

For example, you can take advantage of Global Resources to work with the output produced by another application, such as MapForce, directly inside another MissionKit desktop developer tool. Rather than having to save MapForce output and then open it in another application, you can simply add your MapForce mapping project as a Global Resource and access the output – as it is produced on-the-fly by the MapForce engine – in XMLSpy, StyleVision, or even DatabaseSpy, where you can work with it further as necessary. In fact, you can add such Global Resources to XMLSpy projects. This way, when a source XML file is changed, for instance, you can invoke a StyleVision or MapForce process that utilizes it directly in XMLSpy.

Learn more about working with Global Resources in Altova MissionKit developer tools:

Global Resources in XMLSpy

Next Steps