Chapter 11. Deployment
About Deployment
When an application modeler has designed or updated an application in StarPound Studio, the modeler builds (compiles) a version of the application that can be deployed to StarPound Runtime using Management Console or StarPound Studio.
This "deployable" version of the application, also called a package, is loaded to a deployment target, a collection of servers set up to run applications. Once deployed, the application can be executed by end users.
For more information on creating application models, see the StarPound Studio User Guide.
Updated Applications
When you deploy an updated version of an application, the system immediately begins using the new version for any new requests for that application. Any instances of the application that are already running will complete using the old version of the application.
About System Profiles
You also use the Deployment area to export System Profiles, which contain the configuration data associated with an organization.
When an application modeler imports your System Profile into StarPound Studio, the modeler can then reference elements of the organization (queues, teams, users, work item types) while creating application models. The modeler can also use the configuration data in the System Profile to validate the application model.
Deployment Operations
The Deployment Area of the Management Console allows administrators to:
- Deploy applications to deployment targets
- Import and export deployment targets
- Export System Profiles, the configuration data associated with an organization that is used to develop applications in StarPound Studio
Sections of the Deployment Page
The Deployment page consists of three sections:
- Deployment
- Deployment Target
- System Profile
The following is an example of the Deployment page:
About System Profiles
You also use the Deployment area to export System Profiles, which contain the configuration data associated with an organization.
When an application modeler imports your System Profile into StarPound Studio, the modeler can then reference elements of the organization (queues, teams, users, work item types) while creating application models.
Procedures: Deployment
You can perform the following tasks using the Deployment area.
Deploying Packages to a Pre-Defined Target
To deploy a package (a compiled application) to a pre-defined deployment target:
- In the Deployment section of the page, use the Browse button to select a deployment package.
- Select a target from the Deployment Target drop-down list.
- Click the Deploy button to deploy the package.
Importing a Deployment Target
To import a deployment target definition file, which defines the collection of servers that make up the deployment target:
- In the Deployment Target section of the page, enter a target name in the Name field.
- Use the Browse button next to the Target field to select a deployment target definition.
- Click the Go button to save the target.
The newly saved target is then available in the two Target drop-down lists on the screen.
Exporting a Deployment Target
To export a deployment target definition file for use on another system:
- In the Deployment Target section, use the Export Deployment Target drop-down list to select a target.
- Click the Go button. The system displays a Save As dialog.
- Save the XML file locally.
Exporting a System Profile
To export a System Profile file:
- In the System Profile section, click the Export System Profile button. The system displays a Save As dialog.
- Save the System Profile XML document locally.
Deployment Page
The following section provides definitions for fields on the Deployment page.
Fields
Deployment Package
Deployment Target
Deployment Target Name (Import)
Import Deployment Target
Export Deployment Target
Operations
Export System Profile

