Introducing SMART Plug-Ins (SPIs)
Upcoming SlideShare
Loading in...5
×
 

Introducing SMART Plug-Ins (SPIs)

on

  • 1,810 views

Prezentacija "Introducing SMART Plug-Ins (SPIs)" održana na ComTrade Fabrici Znanja.

Prezentacija "Introducing SMART Plug-Ins (SPIs)" održana na ComTrade Fabrici Znanja.

Statistics

Views

Total Views
1,810
Views on SlideShare
1,721
Embed Views
89

Actions

Likes
0
Downloads
23
Comments
0

2 Embeds 89

http://www.itdogadjaji.com 87
http://www.slideshare.net 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Introducing SMART Plug-Ins (SPIs) Introducing SMART Plug-Ins (SPIs) Presentation Transcript

  • Introducing SMART Plug-Ins (SPIs)
  • What are SPIs? • Pre-configured software modules that “plug into” HP Operations Manager or HP SiteScope to help you maintain the availability and performance of your distributed IT infrastructure • Efficient and productive link between applications that run on a server and other server components.
  • SPI Development • We are –HP partner since 1993 –SPI vendor since 2001 • SPI for Siebel since Q2 2002 • SPI for Citrix since Q4 2002 • SPI for Documentum in Q3 2005 • SPI for Terminal Server Q3 2006
  • LEARN ABOUT SPI FOR SIEBEL
  • SPI for Siebel Customer Selection Anadarko Petroleum 5
  • Certification and Implementation • SPI for Siebel is certified by Oracle, Siebel, and by HP • SPI for Siebel can be fully implemented in few weeks 6
  • What is wrong? You need a SPI! Why am I not able to connect to the Siebel Everything looks ok, but application ? why didn’t I get an email notification from my Siebel application? Siebel Enterprise Why is the application so slow today ? 7
  • Top Business Challenges Siebel is used for sales or marketing automation: •Improve end-user adoption of Siebel Sales applications • Improve end-user satisfaction by: • Finding and removing performance bottlenecks Siebel is used for • Efficient data collection ordering or for call center • Excellent (technical) support automation: • Non-stop availability of services • Provide Web service • Non-stop availability of services • Find and remove issues before they affect end users Siebel Enterprise 8
  • Top Technical Challenges Component stability and Issues with tasks: everything performance looks up and running, but tasks are not done, for • Object managers go example: offline, no session can be started • Email messages are not sent • Once the maximum • Databases (EIM) are not number of tasks for Siebel synchronized component is reached, no • Workflows are not processed task can be started • Transactions are not processed • Siebel component • Records are not updated process hangs or crashes •… Siebel Enterprise Complexity, Slowly perceived heterogeneous platforms performance by end and distributed users architecture 9
  • Effects of “Technical Issues” • Excuses for not having the job done – Technology is the best scapegoat • Direct cause of poor end-user experience – Service support centers, web portals, etc., are very sensitive to performance problem Managing Siebel reduces risks •Know it before the user or customer does •Shorter time to discover root causes •Manage expectations – preserve and increase satisfaction 10
  • Monitoring Siebel End-user Experience Automatically monitor availability and response times of Siebel applications from different locations: - HP OVIS (OpenView Internet Service) + Smart Probe - Load Runner OVIS and Siebel Smart Probe Load Runner and VUGen Siebel Enterprise Availability or performance issue is detected, but what is causing the issue is still not clear! 11
  • Monitoring Siebel Environment with SPI for Siebel • With SPI for Siebel you can automate diligent monitoring of your environment, define application management policies, which enable automated corrective actions, identify the root cause for multiple failures, even if they are seemingly non-related. SPI for Siebel empowers you to proactively manage your environment. Your Siebel environment is no longer “Black box”. HP Operations + SPI for Siebel Database Server Siebel Web Siebel Client Server Web Server Siebel Web Client Siebel Resonate Siebel Gateway Central Server Server Dispatch Siebel Web Client Web Server Siebel Server Siebel File Siebel System Dedicated Client Siebel Enterprise 12
  • SPI for Siebel Architecture 13
  • SPI for Siebel Components • Use SPI for Siebel templates or policies to monitor what is happening in your Siebel environment • Use SPI for Siebel tools or applications to check the systems, react on the issues found, or to administrate your Siebel environment • Use SPI for Siebel OVPM Graphs and HP Reporter Web based reports to check performance trends, availability history, Siebel usage history, or some other trends and history. 14
  • Monitoring Availability Database Server Siebel Web Siebel Client Server Web Server Siebel Web Client Siebel Resonate Siebel Gateway Central Server Server Dispatch Siebel Web Client Web Server Siebel Server Siebel File Siebel System Dedicated Client 15
  • Monitoring Availability • Know when there are: – Siebel Gateway, Siebel Server, Siebel WEB Server Extension, or Resonate Central Dispatch availability issues – Database or Siebel shared file system connectivity issues • Monitor availability because: – If any important part of Siebel is not available, the Siebel user will not be able to work with Siebel. GUI will freeze or the user will not be able to login to Siebel application. 16
  • Monitoring Siebel Related Log Files Database Server Siebel Web Siebel Client Server Web Server Siebel Web Client Siebel Resonate Siebel Gateway Central Server Server Dispatch Siebel Web Client Web Server Siebel Server Siebel File Siebel System Dedicated Client 17
  • Monitoring Siebel Related Log Files • Know when there are: – Any serious issues reported to Siebel Gateway, Siebel Server, Siebel WEB Server Extension, Resonate Central Dispatch or Siebel Component log files. • Monitor Siebel related log files because: – Usually small issues first appear in your Siebel environment and are reported to different log files. If initial issues are not managed and handled, they grow and become critical issues. AND MANY MORE MONITORING OPTIONS AVAILABLE! Read more at www.spi.hermes-softlab.com 18
  • INTRODUCING SPI FOR DOCUMENTUM
  • Documentum SPI Story • HERMES SoftLab, member of ComTrade Group is world leader for Citrix and Siebel operations management – Working closely with HP to provide application management solutions for HP customers – Richest and deepest functionality for app management modules • Through Citrix management we bumped into Documentum – Documentum often deployed with Citrix – Documentum can be enterprise class and business critical – Challenges with business transaction performance – complex delivery chain – No enterprise application management solution available • Did deeper investigation – Partnered with leading local Documentum implementer and pharmaceutical app. developer – Several other challenges discovered/discussed (transaction performance, rendering services, system job failures etc) • Decided to develop the SPI – Established partnership with Documentum – Full support from Documentum and HP – Close cooperation with customers – Marketing and promotion partnerships – Feature leader 20
  • Customer selection 21
  • Business Challenges • Ensuring positive customer experience – Documentum directly used for delivery of customer services Documentum is in direct (legal, insurance, banking…) contact with the customer. Direct impact on customer service and experience. • Ensuring the efficiency of the business system – Documentum is enterprise and business critical Documentum a critical value (pharmacy, airline, energy…) delivery chain element. Direct influence on execution capability, performance of the business system, productivity. • Ensuring successful deployment and adoption – Documentum blamed for non-performance when in-fact other elements cause problems • Operational effectiveness – Documentum experts get dragged into resolving non-Documentum calls/problems – Holistic view and root cause analysis 22
  • Technical Challenges • Complexity, heterogeneous platforms, distributed architecture – Service instability – Application performance in rich data models – Jobs not running per schedule – Threshold limits for DB and Filestore space • Integration and interoperability with external systems – Transaction response times and end-user experience – EAI challenges • Other 23
  • Functionality overview Alarms, Status Performance Service (Graphs & Reports) management User End user Documentum FT Query experience response availability response Server User Log Jobs DB tables and Sessions Files Services Layer Content Search/Query Workflows statistics Repository and Infrastructure Layer Database Full-text Index File system 24
  • Managing Documentum Infrastructure • Content server/repository monitoring – Reveals if Documentum users are not able to connect to repository • Important processes/components not running • DB not available • Server status – Monitors Documentum system health and performance • Session activity and resource consumption (identifies problematic sessions) • Process resource consumption • DB login time too long • Available space on disks where the file stores reside • Detects failed jobs , jobs that are executing too long (hung jobs) or jobs scheduled but failed to start. • Notifies administrators about internal errors/warnings • Monitors DB table size and growth • Event monitoring (unprocessed renditions, logon failures, custom events) 25
  • Managing Documentum Infrastructure • Index server monitoring – Know if is it possible to add new documents to full-text index and search for documents? • Is Index Server available • Status of Index Server modules (Node Controller, QRServer, RTS Top Dispatcher, Document Processor, etc.) • Index Agent status (running, stopped, responding) – Monitors Indexing system health and performance • Notifies if the indexing queue is growing and if there is a backlog of failed indexing items • Index server/agent resource consumption • Alerts if there are internal errors in index server/agent • Periodically checks FT index disk usage 26
  • Monitor user experience and performance • Repository availability from the client perspective • Monitors end-user response time with executing some standard operations against repository – Connect time – Check-out time – Check-in time – Delete time – Disconnect time • Index server latency – The time needed to add a new document into the index and make it searchable – Save-to-search latency (divided into 3 stages) • Time spent in indexing queue before Index Agent acquires the document • Time needed to preprocess a document • Indexing time • Full-text index search response time – Monitors if FT queries come back in a timely fashion 27
  • Monitor user experience and performance 28
  • Policies (1/2) • Instructions that run on the OpenView agents deployed on the Documentum Content Servers – Trigger events usually associated with faults – Advice on a corrective action that should be taken (instructions) – Collect data for graphs and reports (policies with “Perf” extension) • Logically grouped – Content Server policies should be deployed on the Documentum Content servers … 29
  • Policies (2/2) • Manual configuration possible – Polling interval – Automatic/operator initiated actions – Thresholds – Severities  SPI for Documentum provides Threshold assistant reports  Help determine suitable monitoring policy thresholds for the customer environment  Calculate min/max/avg values  Can greatly reduce the number of false alarms 30
  • Tools • Enable operators perform actions on remote managed nodes without the need to physically log on • Can be configured to run on many nodes simultaneously. • With SPI for Documentum tools you can get different current information about your Documentum environment: – Client response time – Top user sessions – Filestore info – Job info 31
  • Service maps • Model service hierarchy in IT environment – Mostly auto discovered – Higher-levels modeled on top of auto discovered – Further connect them to company organizational units (business impact) • Documentum auto discovered service map focuses on modeling dependencies between Documentum components 32
  • Service maps – index server 33
  • Graphs • Data collected with the performance policies are used as input for instant graphs • Used for monitoring, analyzing, and comparing 34
  • Reports (1/4) • Present long-term trends about your Documentum environment – Can be used to project future resources • Generated reports are in html format • SPI for Documentum provides more than 50 out of the box report templates • Most reports available – On Docbase/Server level – For last 28 days/yesterday 35
  • Reports (2/4) • Jobs – Job execution time – Top jobs by job duration – Number of running jobs – Number of failed jobs – Number of jobs failed to start • User sessions – Session activity - number of active/inactive sessions – Load of user sessions (CPU and memory consumption) • Documentum availability – From user perspective • Client response time – Get insight into how fast the documents are accessed or stored to the Docbase 36 Confidential
  • Reports (3/4) • Process statistics – Availability, CPU & memory consumption – Focus administrative effort on servers that need it most • Filestore info – Top filestores with largest content or least available space – Space prediction • Database availability – Determine average, minimum, and maximum l ogin time for Documentum database • Database statistics – Table size growth (dmi_queue_item, dm_audittrail) – Number of events (Unprocessed renditions, Log- on failures) 37
  • Reports (4/4) • Threshold Assistant reports – Help determine suitable policy thresholds for the customer environment – Calculate min/max/average values – Can greatly reduce the number of false alarms 38
  • More at www. spi.hermes-softlab.com