IBM® WebSphere® Everyplace® Deployment for Windows and Linux Version 6Platform Management
IBM® WebSphere® Everyplace® Deployment for Windows and Linux Version 6 Platform Management
This presentation introduces the platform management capabilities of IBM WebSphere Everyplace Deployment for Windows and Linux Version 6.
Goals
Goals Understand how to mange the client platform
The goal of this presentation is to understand how to manage the IBM WebSphere Everyplace Deployment for Windows and Linux Version 6 client platform.
Agenda
Agenda Overview Standalone deployment Enterprise deployment and management
The agenda of this presentation is to provide an overview of platform management, explain the standalone deployment of software, and describe the enterprise deployment of software and management for the client platform
Section
Section Overview
Let’s start with an overview of platform management.
Platform Management
Managed Client Services Eclipse Update Manager Platform Management Value Enable “On Demand” management of applications Deployment options Standalone Enterprise Standards Eclipse OSGi Open Mobile Alliance Install UI Client Access Services Platform Management Managed Client Services Interaction Services Mgmt UI Enterprise Management Agent Preferences Page Configuration Servlet Platform Management
Platform Management installs, maintains, and configures applications and services on the client. There are two platform management services. The Update Manager enables end-users to directly install applications and components from standard Eclipse update sites onto the Workbench. The Enterprise Management Agent enables an administrator to manage the client platform remotely by using a Device Management Server, which is provided by the server platform. IBM WebSphere Everyplace Deployment Version 6 supports two options to deploy software to the client. Standalone deployment allows an end-user to install software onto their device through the Eclipse Update Manager. Enterprise deployment enables a System Administrator to install software onto multiple devices by using the Enterprise Management Agent and a Device Management Server.
Section
Section Standalone Deployment
Next, let’s cover standalone deployment of software to the client platform.
Eclipse Update Manager
Eclipse Update Manager Developers package components as plug-ins Deployers package components into Features Features published to Update Sites Features installed from Update Sites using the Update Manager End-user can manage software for their client via Install or Application Management UI Install software from local file system or remote site Install, disable, uninstall features Update Site Feature Plug-in Plug-in Plug-in Eclipse Update Manager Install UI Mgmt UI
In IBM WebSphere Everyplace Deployment Version 6, developers package software components as Eclipse plug-ins. Solution Deployers then package these plug-ins into installable Eclipse Features consisting of one or more plug-ins and optionally other Features. They then publish these Features to an Eclipse Update Site. End-users can use the installation user interface with the Update Manager to install these Features from an Update Site onto their client. Furthermore, end-users can use the management user interface to disable and uninstall Features that are installed on their client.
Application Install User Interface
Application Install User Interface Install UI Select Application > Install
This slide shows the application install user interface. Launch the client workbench, select Application, and then select Install.
Application Management User Interface
Application Management User Interface Mgmt UI Select Application > Application Management
This slide shows the application management user interface. Launch the client workbench, select Application, and then select Application Management.
Standalone Deployment
Standalone Deployment Plug-in Plug-in Plug-in produces Developer Application Integrator produces Plug-in Plug-in Plug-in Feature produces Deployer Using RSDP Using RSDP Using RSDP Update Site Plug-in Plug-in Plug-in Feature creates creates or
Let’s now walk through the process of standalone deployment. The Developer uses the Rational Software Development Platform (RSDP) to create one or more plug-ins for their software components. They may either use the Plug-in Project wizard in the Plug-in Development Environment (PDE) or the Client Services Project wizard in the Bundle Tools to create the plug-ins. Next, the Application Integrator uses the Feature Project wizard in the PDE to integrate plug-ins into a Feature. The Deployer then produces an Update Site that contains one or more Features. They can then create Update Sites on CD’s or on the Web. End-users can then subsequently access these Update Sites from their client workbench to install Features onto their client platform.
Section
Section Enterprise Deployment and Management
Finally, let’s explore enterprise deployment of software and management for the client platform.
Enterprise Management
Enterprise Management Device Management Server (DMS) WebSphere Application Server Server Client HTTP Plugins Web Services Interfaces Admin Console DMS Notification NativeApp Bundle SyncML/DM Protocol Enterprise Mgmt Agent Managed Client Services Eclipse Update Manager Enterprise Management Agent SyncML /DM HTTP(S) App App
The Enterprise Management Agent works cooperatively with the Device Management Server provided by the IBM WebSphere Everyplace Deployment Version 6 server to perform management operations. The agent and server use the SyncML/DM protocol defined by the Open Mobile Alliance to communicate management requests. A System Administrator uses the Device Management (Admin) Console to schedule management jobs for devices that include software installation, update, and configuration. When installing and updating software components, the management system determines which components are already on the device and then installs only the missing components based on information about the dependencies among all the requested components (i.e. bundles). The Device Management Server can also notify the Agent about management jobs. When the Agent receives a management job to install components, the Agent uses HTTP/HTTP(S) to pull the necessary components from the Device Management Server. Next, let’s discuss Enterprise Management in more detail.
Enterprise Management Agent
Update Manager Enterprise Management Agent Java agent running on the client SyncML/DM protocol used between agent and DM Server Agent can be configured for periodic polling of the DM Server DM Server can notify the agent to connect HTTP Service must be configured Listen on address other than localhost (e.g. ALL) Use a static port (e.g. 8777) Provides OSGi specific capabilities such as bundle control Provides platform inventory capabilities, enabling management of platform configuration Supports Win32/Linux native extensions for native software inventory, configuration, install, uninstall Supports secure connections with DM Server via SSL Uses Update Manager to install features from distributed update sites Enterprise Management Agent
The Enterprise Management Agent is written in Java and runs on the Managed Client Services provided by the client platform. The agent uses the SyncML/DM protocol to communicate with the Device Management Server to perform management jobs. The agent can be configured to periodically poll the Device Management Server for jobs. However, the Device Management Server can also notify the agent to connect and then perform a management job (i.e. install software). The agent provides OSGi-specific specific capabilities supported by Managed Client Services, such as bundle control, and provides inventory capabilities so a System Administrator can manage the configuration of the client platform. The agent supports native extensions to manage native software on Windows and Linux clients. These extensions support Install, Uninstall, Status, Start, Stop, and gathering information from STDOUT/STDERR. SSL is also enabled to secure the connection between the Enterprise Management Agent and the Device Management Server. The Device Management Server only deploys bundles – not Update Sites. Therefore, an Update Site must be packaged and deployed in a NativeAppBundle (we will explain this topic in more detail later in this presentation). When the agent receives a NativeAppBundle, the agent extracts the Update Site from the bundle and uses Update Manager to install the Features in the Update Site onto the client platform.
Enterprise Management Agent(continued)
Enterprise Management Agent (continued) Configuration During install After install using one of these options Locally by using Preference Page Remotely by using DM Console to communicate with Enterprise Management Agent via DMS Locally or remotely by using Web browser to open configuration servlet hosted in the Web Container running the service When configuring using Preference Page, user will receive warning When Enterprise Management Agent enabled, Install and Application Management UI for Update Manager disabled Update Manager Enterprise Management Agent Preferences Page Configuration Servlet
You can configure the Enterprise Management Agent either during or after installation of the client. You are prompted to configure the agent while installing the client platform and, if you choose to do so, you can use a Preferences Page to provide the information necessary to connect the agent to a Device Management Server. You may also configure the agent after installing the client by using one of the following options. An end-user can configure the agent locally from the client workbench by selecting File -> Preferences -> Enterprise Management Agent and then use the Preferences Page to configure the agent. A System Administrator can remotely configure the agent by using the Device Management Console to configure the agent via the Device Management Server. A System Administrator can locally or remotely configure the agent by using a Web browser to open a configuration servlet that is hosted by the Web container running the client service. When the IBM WebSphere Everyplace Deployment for Windows and Linux Version 6 client is installed as a system management service, the Enterprise Management Agent Servlet is the only way to configure and control the Enterprise Management Agent. If you choose to enable the Enterprise Management Agent, the end-user will no longer have control over installing, updating, or uninstalling features so please check with your Systems Administrator before you enable the agent.
Enterprise Management AgentInstall Configuration Page
Enterprise Management Agent Install Configuration Page
This slide shows the Enterprise Management Agent Configuration page which is displayed during installation of the client.
Enterprise Management AgentRuntime Preference Page
Enterprise Management Agent Runtime Preference Page Preferences Page
This slide shows the Enterprise Management Agent Configuration page which is displayed in the client workbench after you have installed the client. To display this page, launch the client workbench and select File -> Preferences -> Enterprise Management Agent. If you choose to enable the Enterprise Management Agent, you will be prompted with the warning shown on this slide. If you enable the Enterprise Management Agent, the end-user will no longer have control over installing, updating, or uninstalling features so please check with your Systems Administrator before you enable the agent.
Enterprise Management Agent System Management Installation
Enterprise Management Agent System Management Installation Configuration during installation using same configuration page as runtime Configuration pages hosted on Web Container running in the service Entries added to Start menu (on Windows) to launch browser to view servlet
You can install the client platform to run as a system management service. This configuration enables a system administrator to manage the entire system with the platform’s management agent that communicates with the Device Management Server. In this configuration, there is no user interface to interact with the platform. Configuration of the management agent settings is accomplished either during the installation process or afterwards by using an agent configuration servlet that you access from a browser.
Enterprise Management AgentConfiguration Servlet
Enterprise Management Agent Configuration Servlet Configuration Servlet
This slide shows how the initial web page provided by the configuration servlet.
Enterprise Deployment
Enterprise Deployment Plug-in Plug-in Plug-in produces Developer Application Integrator produces Plug-in Plug-in Plug-in Feature produces NativeApp Bundle App Deployer registers Using RSDP Using RSDP Using RSDP Using DM Console Update Site Plug-in Plug-in Plug-in Feature produces Using NativeAppBundle Device Management Server NativeApp Bundle App
Let’s now walk through the process of Enterprise deployment. The Developer and Application Integrator perform the same steps as in Standalone Deployment. The Deployer then produces an Update Site that contains one or more Features. However, now the Deployer uses the NativeAppBundle tool to produce a NativeAppBundle that contains an Update Site. Next, the Deployer uses the Device Management Console to register the NativeAppBundle with the Device Management Server. The System Administrator can subsequently use the console to schedule deployment of this NativeAppBundle to one or more clients. The Enterprise Management Agent on a receiving client extracts the Update Site from the NativeAppBundle and invokes the local Update Manager to install the Update Site, and its Features and plug-ins, onto the client platform.
Slide 20
Trademarks, Copyrights, and Disclaimers The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM CICS IMS MQSeries Tivoli IBM(logo) Cloudscape Informix OS/390 WebSphere e(logo)business DB2 iSeries OS/400 xSeries AIX DB2 Universal Database Lotus pSeries zSeries Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Other company, product and service names may be trademarks or service marks of others. Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This document could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or program(s) described herein at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's intellectual property rights, may be used instead. Information is provided "AS IS" without warranty of any kind. THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted, if at all, according to the terms and conditions of the agreements (e.g., IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. IBM makes no representations or warranties, express or implied, regarding non-IBM products and services. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. © Copyright International Business Machines Corporation 2005. All rights reserved. Note to U.S. Government Users - Documentation related to restricted rights-Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract and IBM Corp. Template Revision: 9/28/2005 5:50 PM