Operation void launchGCT (Name objectName = NA, CIS CharacterString context = NA, CIS SequenceOf Structs::AVP userInfo = NA, CIS CharacterString gctDisplayAddress = NA, CIS SequenceOf Structs::AVP additionalInfoInputList = empty list, CIS Boolean. closingEnabled, CIS SequenceOf Structs::AVP additionalInfoOutputList), in Class EMS

Documentation
This operation of the EMS invokes the launch of the GCT if requested to do so under a server-launched configuration.
Operation Exceptions:
1. NOT_IMPLEMENTED - Raised in case when EMS does not support this operation.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure
3. UNABLE_TO_COMPLY - Raised in case the EMS is unable to complete the launch.
4. CAPACITY_EXCEEDED - Raised in case the maximum number of active GCTs supported by the EMS has been reached.
5. ENTITY_NOT_FOUND - Raised when the object referenced does not exist.
6. INVALID_INPUT - Raised when one of the input parameter is invalid.

Protocol |  | Qualification |
Exceptions |  | Size |
Time |  | Concurrency | Sequential
Export Control | PublicAccess |  |

Preconditions
1. The EMS supports the server launch window system protocol (i.e., is capable of server launching in addition to client
launching).
2. The NMS has retrieved the GCT profile of the EMS that contains the window/widget data the EMS supports for
GCT, and has selected an object to be displayed upon GCT launch.
3. The managed object to be displayed upon GCT launch exists and is in a valid state.
4. The EMS has access to the NMS display address.
5. The NMS has access to any other required servers (e.g., ICA server for Citrix Metaframe).
Postconditions
The GCT application opens the display successfully at the NMS host address.
Semantics

Arguments

objectName
/* in */ The applicable reference object. The EMS displays the GCT to the extent supported by the EMS. The EMS should invoke the GCTwhich is available for the closest object in the object name hierarchy. (e.g. if the card internal view is not available for the equipment object indicated then the EMS will invoke the GCT of its ME instead). Only the top-level of the EMS is mandatory to be supported by the EMS.
context
/* in */ Top Level, Fault, Configuration (software management/connection management), Accounting, Performance, Security, Systems Management. Context is of secondary priority with the ObjectName as serving as the highest priority in determining which GCT window to open.
Suggested names are:
- TOP_LEVEL,
- FAULT,
- CONFIGURATION_SOFTWARE,
- CONFIGURATION_CONNECTION,
- ACCOUNTING,
- PERFORMANCE,
- SECURITY,
- SYSTEMS_MANAGEMENT.
userInfo
/* in */ The capability / user information that applies to the operations that are made available through the GCT application, depending on the EMS ability to enforce capability / user limitations on the GCT.
Suggested names are:
- userId,
- password,
- capability .
Capability suggested values are:
- READ_ONLY,
- READ_WRITE.
Values and meaning for these attributes are left to bilateral agreement EMS and NMS.
gctDisplayAddress
/* in */ The IP address or hostname including any display port information.
additionalInfoInputList
/* in */ A suggested value isGCTParentWindow -Allows the association of the GCT to the desired parent window when the window meachanism supports this (e.g. when using a pure X-protocol).
closingEnabled
/* out */ An output flag indicating the ability of the EMS to manage the open GCT window: specifically whether the EMS is able to close it upon request (i.e. using a subsequent destroyGCT operation). Default value is true.
additionalInfoOutputList
/* out */ An output parameter. Suggested Value: GCTWindowHandle - this is an optional return value that allows the NMS to manage the GCT, within its own window manager, when possible (e.g. when using a pure X-protocol).