Project Import/Export Tasks

In a Service Oriented Architecture (SOA) environment, Service Contracts can interact with each other, sharing information models and utilizing the various capabilities of other information models. To avoid duplicate and unnecessary complexity, Tigerstripe allows you to share entire Tigerstripe projects, information within Tigerstripe projects, and provides a way to build dependencies between your projects.

In order to facilitate collaboration between users working on a SOA design, Tigerstripe Workbench allows you to share projects through the following mechanisms:

• Project Copies: this option is easiest way of sharing Service Contract models between Tigerstripe users however it provides very limited support for collaboration. This method relies on a copy of the content in your project. Since projects are self-contained, they can be either copied or exported to .zip archives and imported to another project.
• Source Control Systems: this option leverages the use of a versioning control system to maintain versions of your Tigerstripe models. This mode of collaboration and model sharing allows you to share the actual Tigerstripe model, and designs them in a controlled environment. This method is most ideal when multiple architects need to work on a single Tigerstripe model.
• Tigerstripe Modules: Tigerstripe modules are compiled versions of Tigerstripe models. Their content can be referenced by other Tigerstripe projects. However, they cannot be modified. This is the preferred method of establishing dependencies between Tigerstripe projects that share a common information model.
• Published Web Sites: Tigerstripe can publish Service Contract definitions, that is, Tigerstripe projects, to a web-based document. Users can either uploaded the projects to a web site or access them locally from a hard drive. This method provides a convenient way to share a Service Contract design to a large number of users.

Importing Tigerstripe Projects

• To learn more about how to import Tigerstripe Projects from a directory or a zipped archive, refer to Importing a Tigerstripe Project.
• To learn more about how to import Tigerstripe Projects from a versioning control system, refer to Tigerstripe Source Control Integration.

Exporting Tigerstripe Projects

• To export a Tigerstripe Project as a zipped archive, refer to Exporting a Tigerstripe Project.
• To export a Tigerstripe Project to a module, refer to Working with Tigerstripe Modules.

Working with Tigerstripe Modules

Tigerstripe Modules are binary-like versions of a Tigerstripe Project. You can reference their content to be shared between multiple projects, however they cannot be modified. This provides an ideal mechanism to share information models between Service Contract designs. For more information on how to create and use Tigerstripe modules, refer to Working with Tigerstripe Modules.

Publishing Tigerstripe Projects

To facilitate collaboration between team members, Tigerstripe allows you to publish a Tigerstripe Project to a web site, where the content of the corresponding Service Contract can be browsed and the target integration profiles can be downloaded.

For more information on how to publish a Tigerstripe project, refer to Publishing Service Contracts.