Share via

3.1.1.4 Alternate Launch Configurations

  • Article

A server that supports the IAlternateLaunch (section 3.1.4.16) interface enables clients to create alternate launch configurations for conglomerations. The meaning of such a configuration is implementation-specific.<272>

An alternate launch configuration consists of the following properties, which are associated with the conglomeration for which the alternate launch configuration was created.

 Property name

 Type

 Notes

AlternateLaunchName

string

A unique identifier for alternate launch configurations.

StartType

32-bit unsigned integer

An implementation-specific<273> value that indicates how the ORB is to create instance containers for the conglomeration.

ErrorControl

32-bit unsigned integer

An implementation-specific<274> value that indicates how the ORB is to handle serious errors for components in the conglomeration.

Dependencies

string

An implementation-specific<275> value that represents dependencies that the ORB is to ensure are met before creating an instance container for the conglomeration.

AlternateLaunchRunAs

string

The security principal to be used by the ORB when performing an alternate launch.<276> Clients that configure alternate launch configurations SHOULD set the RunAsUser property of the conglomeration to the same value as AlternateLaunchRunAs.

AlternateLaunchPassword

string

The password for the security principal specified by the AlternateLaunchRunAs property.<277> Clients that configure alternate launch configurations SHOULD set the Password property of the conglomeration to the same value as AlternateLaunchPassword.

DesktopOk

boolean

Indicates whether or not the ORB is to perform an alternate launch in such a way that the components in the conglomeration are able to interact with users interactively.<278>

Except for the AlternateLaunchName property, this configuration is not exposed in any of the tables in the catalog. However, if the server also supports exporting and importing conglomerations, the additional properties StartType, Dependencies, and DesktopOk SHOULD be represented in installer package files that the server creates for conglomerations with alternate launch configurations, so that a round trip of export and import results in an equivalent alternate launch configuration. For more details on round-trip consistency, see IImport::ImportFromFile (section 3.1.4.12.1).

Alternate launch configurations are persistent; that is, they retain their state between sessions.