This form assists in deploying the artifact.

The way in which software in the archive is deployed is variable. It is based on what available resources exist and what the target machine is, then, capable of doing. If the target machine has a different architecture than the software expects, there may, for instance, need to be some intermediary that allows the software to run. An emulator or some kind of interpreter might be used to bridge the gap from old to new. These artifacts are each called a provider and essentially map one environment and architecture to another. It is possible that an artifact might need a chain of these.

Other artifacts might be data. Such an artifact would require software or some intermediary to interpret that data and visualize it or otherwise allow some interactivity. This would be a viewer for that object and is often based on associations with that artifact's type or subtype which you see near the artifact's name in the header above.

This panel illustrates that path from the artifact to modern resources. It further allows control and consideration to how that path is constructed. It allows for alternative viewers or providers and further allows extra constraints or services to be used. At the end of the path, you can select where to deploy the object.

It may be possible to deploy to your own machine. Typically, for web-based artifacts, your modern browser can adequately display them. In these situations, your browser would simply load the content itself. The system encourages local resources, but you can also override that behavior in the panel by selecting a different target machine than your own.

It is possible to add input and to configure the running artifact or any of its viewers or providers by expanding the item to show its options. If there are any inputs, those will be listed with a button available to select another object to attach as input. If that input is a configuration, there will be another button to write in the configuration options specifically.