Functional Components and Interfaces in SCOMO

1    SCOMO Server
The SCOMO Server is a logical entity which is dedicated to issue SCOMO Operations to the device or consume the SCOMO Alerts from the device.
2    SCOMO Client
The SCOMO Client is responsible for executing SCOMO Operations.  It consumes the Software Component delivered to the device and is expected to relay SCOMO Alerts conveying a success or failure result back to the SCOMO Server .
3    The Device Management Client
The DM Client component makes it possible to initiate software component management in the device from a DM server. The DM Enabler provides support for device discovery and parameter setup by the DM Client component.  The SCOMO enabler provides a management object for software components that the DM Client component provides access to, such that the DM server can manipulate it.  The DM client interacts with a Software Component Agent in the device that is responsible for conducting the management activities using a delivered software component management object.  The DM client employs the Generic Alert [DMPRO] mechanism to communicate the final notification comprising the status of the management activity. ScoMo does not define or specify the Device Management Client
4    Alternate Download Client
The alternate download client is an optional feature that may exist on the device and used for downloading software components to the device when the DMPRO is not being used for such downloads. The alternate download client may support DLOTA or something else. SCOMO does not define or specify the alternate download client
5    The Device Management Server
The SCOMO architecture requires the DM server component to support device discovery, determination of an appropriate software component and delivery of a software component management object to the device over Large Object downloads if the device can support that. It also facilitates receipt of a final notification from the device employing the Generic Alert mechanism. SCOMO does not define or specify the Device Management Server.
6    The Alternate Download Server
The Alternate Download Server is an optional feature of the device management system that makes it possible to download software management objects using the alternate download mechanism, such as DLOTA.  The Download Server is not defined or specified within the scope of SCOMO
7    External Management Infrastructure
The Device Management System comprises of a set of external management components over and above the device management server that participate in the overall process of managing devices. The external management infrastructure is used but not defined or specified within the scope of the SCOMO.

Understanding Important Windows PowerShell Concepts

The Windows PowerShell design integrates concepts from many different environments. Several of them are familiar to people with experience in specific shells or programming environments, but very few people will know about all of them. Looking at some of these concepts provides a useful overview of the shell.

Commands are not Text-based

Unlike traditional command-line interface commands, Windows PowerShell cmdlets are designed to deal with objects - structured information that is more than just a string of characters appearing on the screen. Command output always carries along extra information that you can use if you need it. We will discuss this topic in depth in this document.

If you have used text-processing tools to process command-line data in the past, you will find that they behave differently if you try to use them in Windows PowerShell. In most cases, you do not need text-processing tools to extract specific information. You can access portions of the data directly by using standard Windows PowerShell object manipulation commands.

The Command Family is Extensible

Interfaces such as Cmd.exe do not provide a way for you to directly extend the built-in command set. You can create external command-line tools that run in Cmd.exe, but these external tools do not have services, such as help integration, and Cmd.exe does not automatically know that they are valid commands.

The native binary commands in Windows PowerShell, known as cmdlets (pronounced command-lets), can be augmented by cmdlets that you create and that you add to Windows PowerShell by using snap-ins. Windows PowerShell snap-ins are compiled, just like binary tools in any other interface. You can use them to add Windows PowerShell providers to the shell, as well as new cmdlets.

Because of the special nature of the Windows PowerShell internal commands, we will refer to them as cmdlets.

Windows PowerShell Basics

Graphical interfaces use some basic concepts that are well known to most computer users. Users rely on the familiarity of those interfaces to to accomplish tasks. Operating systems present users with a graphical representation of items that can be browsed, usually with drop-down menus for accessing specific functionality and context menus for accessing context-specific functionality.

A command-line interface (CLI), such as Windows PowerShell, must use a different approach to expose information, because it does not have menus or graphical systems to help the user. You need to know command names before you can use them. Although you can type complex commands that are equivalent to the features in a GUI environment, you must become familiar with commonly-used commands and command parameters.

Most CLIs do not have patterns that can help the user to learn the interface. Because CLIs were the first operating system shells, many command names and parameter names were selected arbitrarily. Terse command names were generally chosen over clear ones. Although help systems and command design standards are integrated into most CLIs, they have been generally designed for compatibility with the earliest commands, so the command set is still shaped by decisions made decades ago.

Windows PowerShell was designed to take advantage of a user's historic knowledge of CLIs. In this chapter, we will talk about some basic tools and concepts that you can use to learn Windows PowerShell quickly. They include:

· Using Get-Command

· Using Cmd.exe and UNIX commands

· Using External Commands

· Using Tab-Completion

· Using Get-Help