About transport and migration > Transport and migration prerequisites > Logical names for StreamServer applications

Logical names for StreamServer applications
To deploy the correct configuration to StreamServer applications when migrating and importing sites/application domains, you must assign logical names to all StreamServer applications in all application domains. You can, for example, use the names of the corresponding Design Center Projects as logical names.
The logical name is used as identifier when a configuration is deployed to a StreamServer application. All StreamServer applications in an application domain that have the same logical name are treated as the same StreamServer application. For example, if you have several StreamServer applications with identical logical names (e.g. for load balancing), and you deploy to one of these StreamServer applications, the same configuration is by default deployed to all StreamServer applications with the same logical name.
The logical name is also important during migration from one environment to another. For example, if you have a development application domain that only contains one StreamServer application with the logical name Invoice, and want to deploy changes to a test application domain that contains two StreamServer applications with the logical names Invoice and Order, only the Invoice application is affected by the migration.Click to enlarge
Figure 1
If the test application domain in this example has several StreamServer applications with the logical name Invoice, all Invoice applications are affected by the migration.Click to enlarge
Figure 2
To assign a logical name to a StreamServer application
You can assign a logical name to a StreamServer application when you create it. You can also assign a logical name to an existing StreamServer application:
1
2
In the Properties view, double-click the Logical name property. The Edit Logical Name dialog box opens.
3
OpenText StreamServe 5.6 Updated: 2013-03-01