A package must be made available by the designer for delivery to a runtime instance. If a package exists on a runtime instance, it can be replaced by an updated package. Verify that the instance is stopped before delivering the updated package.
If a package does not currently exist on the instance, see Delivering a New Package.
Note: Only one package can reside on a runtime instance.
WARNING! Before stopping the instance to use the new package, verify that there are no active business process instances being analyzed. All business process should be complete. Substitution of a new package instance can result in runtime errors if the configuration and metadata for any active business process instances have changed.
To update a package:
In the Server Explorer, connect to the runtime instance where you are deploying your package.
Click the expand symbol next to the instance name to expand the contents.
Right-click the package and select Update Package.
Enter the full path and file name, or Browse for the .bpi file of the updated package.
Click OK to place the package on the instance.
Warning! There is no confirmation to overwrite the previous package.
The status information for the package changes to Need to Deploy.
If the instance is still running, it is using the old package to analyze processes.
When the project package is delivered to a runtime instance, the agent copies pertinent information to the runtime instance.
The next step is to define the physical bindings for the logical endpoints in the business process. See Binding Service Endpoints.