To make application objects accessible outside of the Developer tool, deploy an application that contains the objects. You can create a new application, or create the application as you deploy an object. When you deploy an application, you isolate the application objects from changes in data structures.

You can deploy application objects in the following ways:

Deploy to a Data Integration Service.

When you deploy an application to a Data Integration Service, the application runs and end users can connect to the application.

Depending on the types of objects in the application, end users with appropriate permissions can query the objects, access web services, or run mappings or workflows from the command line. You can also deploy objects to allow users to query the objects through a third-party client tool.

Deploy to a network file system.

When you deploy an object to a network file system, the Developer tool creates an application archive file. Deploy an object to an archive file if you want to archive the object in a version control system.

If your organization requires that administrators deploy objects to a Data Integration Service, an administrator can deploy the application archive file to a Data Integration Service using the Administrator tool.

You can also import objects from an application archive file into projects or folders in the Model repository.

After you deploy application objects or an application archive file to a Data Integration Service, you can use the Developer tool to connect to the run-time application and view read-only copies of the run-time objects.