Скачать презентацию THE SCO GROUP 2007 Jonathan Schilling Chief Скачать презентацию THE SCO GROUP 2007 Jonathan Schilling Chief

5c484d2bfffd47959369bde778286652.ppt

  • Количество слайдов: 25

THE SCO GROUP 2007 Jonathan Schilling – Chief Mobile Architect Rick Powell – System THE SCO GROUP 2007 Jonathan Schilling – Chief Mobile Architect Rick Powell – System Engineer Albert Fu – Advanced Technology Group Alex Sack – Mobile Architect 1 © The SCO Group, Inc. All Rights Reserved

Agenda SCO Mobile Server with Hip. Check SCO Mobility Server – Jonathan Schilling Hipcheck Agenda SCO Mobile Server with Hip. Check SCO Mobility Server – Jonathan Schilling Hipcheck Server Setup – Rick Powell Web 2. 0 Albert Fu Alex Sack 2

SCO Mobile Server overview § A platform for deploying mobile applications § SCO Open. SCO Mobile Server overview § A platform for deploying mobile applications § SCO Open. Server 6 M and SCO Unix. Ware 7 M provide the basis § Natural extension of the heritage of SCO’s traditional product line § Can provide services for any kind of mobile application § Hip. Check – one particular SCO Mobile application, of particular interest to SCO UNIX users 3

SCO Mobile Architecture Components § Client part of service § Smartphones, PDAs, some feature SCO Mobile Architecture Components § Client part of service § Smartphones, PDAs, some feature phones, some SMS-only § Web browsers, i. Phone browser § Native PC desktops § Mobile Server part of service § Service processor § Web admin pages (if necessary) § Local database § Back-end integration part of service (if necessary) § Connectors § Agents 4

An Example - Hip. Check Architecture 5 An Example - Hip. Check Architecture 5

Types of Edge. Click Mobile Digital Services § § § Self-Contained Service Business Integration Types of Edge. Click Mobile Digital Services § § § Self-Contained Service Business Integration Service Monitoring Service Mobile Database Service Two-way SMS Service 6

Self-Contained Service § A new application § Does not connect to existing application § Self-Contained Service § A new application § Does not connect to existing application § No agents necessary § Subscriber-centric § Also groups, contacts, etc. § § § Most logic on SCO Mobile Server Stores application data in MS database Will often not need web admin pages Optionally can be tied to “landing pages” Examples: Daytimer Mobile, Shout, Vote 7

Business Integration Service § Connects to existing application § Therefore, has connectors or agents Business Integration Service § Connects to existing application § Therefore, has connectors or agents § Purpose is data collection, data reporting, transaction processing § SCO Mobile Server becomes mostly a “switch” § MS database mostly just used for routing § Application is client- and agent-centric § Has web admin pages to manage agents § Examples: Musco Foods, Carlamobile, DTP 8

Monitoring Service § Specialized variant of business integration service § Tracks vital business and Monitoring Service § Specialized variant of business integration service § Tracks vital business and system metrics § View health indicators of business or system § Receive alerts based on user-set triggers § Take actions to correct problems § Combines SOA with EDA § Examples: Hip. Check (for Operating Systems) § Hip. Check Source Code Product available for others to customize it to particular environments 9

Mobile Database Service § § Keep full application database on mobile device Periodically synch Mobile Database Service § § Keep full application database on mobile device Periodically synch with back-end server All sorts of data capture are possible Biometric input devices with generic interfaces § e. g. fingerprint scan § Examples: Mobile local census info 10

Two-way SMS Service § Existing application sends SMS to phone, phone user replies by Two-way SMS Service § Existing application sends SMS to phone, phone user replies by SMS, gets routed to application § No client program on phone needed § Any phone can be used § Appropriate for well-defined, limited user interactions § Must supply SCO Mobile Server plug-in for two-way SMS provider chosen § Examples: SCO Mobile “Team. Link” § For a coach coordinating responses from team members § For confirming doctor/dental appointments 11

Hip. Check Product Overview § Hip. Check is an SCO Mobile application § Allows Hip. Check Product Overview § Hip. Check is an SCO Mobile application § Allows you to monitor the health of your UNIX and Windows systems from your mobile devices § View current state § processes, users, disks, CPU, memory, printers, services, etc. § Set triggers to get alerts about critical system conditions § Service stops running, disk gets low on space, etc. § Take corrective actions § Kill runaway process, restart crashed service, reset password, etc. § Hosting and business model choices § Hip. Check service may be hosted by SCO – subscription model § Or deployed by reseller or end customer – conventional model § The bridge between SCO’s UNIX and mobile product worlds 12

What all gets monitored/managed? § Views § System info (OS name, OS version, FQDN, What all gets monitored/managed? § Views § System info (OS name, OS version, FQDN, IP addr, nbr of cpus, last boot time, up time, current users, current pagefile usage), processes, services, filesystems, cpu usage, memory usage, network usage, user info, printers, print jobs, error events, hardware info, system and application logfiles § Alerts § Machine unreachable, logfile has specified regexp in it, process stops running, service starts or stops, filesystem space below specified threshold, printer status change, print jobs § Actions § Reboot system, kill process, restart/stop service, cancel print job, cancel all print jobs, enable/disable printer, lock/unlock/reset user, execute arbitrary command 13

The four components of Hip. Check § Hip. Check agent § Runs on a The four components of Hip. Check § Hip. Check agent § Runs on a monitored system in background § Responds to view and action requests § Periodically checks for triggers, generates alert if detected § Hip. Check client § Mobile user interface for views, triggers/alerts, actions § Hip. Check web admin pages § Browser administrator user interface for defining monitored systems and who can do what on them § Hip. Check service § What runs on the SCO Mobile Server and ties all this together 14

Hip. Check supported systems § Hip. Check systems to be monitored § § § Hip. Check supported systems § Hip. Check systems to be monitored § § § § § Hip. Check UI phone client § § § Windows Vista (coming) Windows XP Professional Windows Server 2003 Windows 2000 SCO Open. Server 5. 0. 7 SCO Open. Server 6. 0. 0 SCO Unix. Ware 7. 1. 1 and up Sun Solaris 2. 8 and up, SPARC and Intel Windows Mobile 5. 0 for Pocket PC Windows Mobile for Pocket PC 2003 Treo Palm. OS Blackberry (soon), Nokia (soon), Sony Ericsson (soon) Hip. Check UI desktop client § Windows Vista (coming), XP Home or Pro, 2003 Server, 2000 Server § Hip. Check alerts § Any phone that can receive SMS messages § Also e-mail 15

Configuring via Admin pages § Hip. Check subscribers and groups § Same as Me Configuring via Admin pages § Hip. Check subscribers and groups § Same as Me Inc subscribers and groups § Use https: //. . . /meinc/app to administer § Hip. Check specific administration § Use https: //. . . /hipcheck/app § Task-oriented § Create/modify monitored system definition § Easy to fill out due to drop-down lists § Set/modify privileges of subscribers for a system § Must do, otherwise subscribers won’t see any systems! § Status check on monitored systems § Green or red – useful for agent installation check too 16

Hip. Check’s privilege model § Hip. Check subscribers can be of three levels § Hip. Check’s privilege model § Hip. Check subscribers can be of three levels § View privilege – can see monitored system, do views, get alerts § Admin privilege – can set triggers for alerts, take actions § Owner privilege – can grant privileges to others, see monitored system’s root/admin password, delete a monitored system § Groups (defined via Me Inc) can be used as well as subscribers 17

Hip. Check Security § Client to SCO Mobile Server § Me Inc subscriber must Hip. Check Security § Client to SCO Mobile Server § Me Inc subscriber must login and be authenticated § Me Inc account must be eligible for Hip. Check § Communication is over https § On SCO Mobile Server § Administrator must grant access to specific monitored systems § Administrator must grant additional access to set alerts or take actions or add other subscribers § Administrator must supply root/admin account, password of monitored system § SCO Mobile Server to Agent § Communication is over https with certificates § Monitored system is typically protected by firewall 18

Firewall issues § The Hip. Check Edge. Click Processor runs outside an enterprise’s firewall Firewall issues § The Hip. Check Edge. Click Processor runs outside an enterprise’s firewall § True when hosted by SCO § True when deployed by reseller for an end customer § The monitored systems and Hip. Check agent run inside an enterprise’s firewall § True for almost all production situations § Cannot access systems’ ports 80/8080/etc. directly § SCO Mobile’s Proxy Relay Agent Service is the solution § Runs on system just inside the enterprise firewall § Accepts server-to-agent calls via one dedicated firewall opening § Forwards them to all the monitored systems 19

Scenario 1 20 Scenario 1 20

Scenario 2 21 Scenario 2 21

Scenario 3 22 Scenario 3 22

Scenario 4 23 Scenario 4 23

Availability § Hip. Check 1. 0. 3, SCO hosted § was deployed May 8 Availability § Hip. Check 1. 0. 3, SCO hosted § was deployed May 8 § https: //hipcheck. meinc. com § Open a trial account – step by step guide to follow § Hip. Check 1. 0. 3 Reseller/Customer deployed § went GA July 31 § http: //www. sco. com/suppor t/download. html § Package HCms for OSR 6 and UW 7 § HCms exe for Windows 2003 § Multiple locales § English, Chinese now 24

Work in progress § Software inventory view/management § See early stages in demos in Work in progress § Software inventory view/management § See early stages in demos in lab § Hardware monitoring – power mgmt, temperature probe § Windows monitored systems only § SNMP integration § A big task! § MS SCOM (formerly MOM) integration § Work is far along, see demos in lab § Active Directory integration § Parts done already § Multiple locales § Product is fully I 18 N’d, L 10 N’s provided as market demands § Audit trails and reports, “Dashboard” big picture viewing § Always adding functionality, suggestions welcome 25