1 / 10

Prerequisite Scanner Sprint 6 Demo

Prerequisite Scanner Team Sprint Demo. Prerequisite Scanner Sprint 6 Demo. IBM Prerequisite Scanner Team June 28, 2012. Key Accomplishments. PRS 1.2.0.0 published on FixCentral and iRAM (story 28070) - Globalization support for Tpae (story 28068)

adonai
Télécharger la présentation

Prerequisite Scanner Sprint 6 Demo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Prerequisite Scanner Team Sprint Demo Prerequisite Scanner Sprint 6 Demo IBM Prerequisite Scanner Team June 28, 2012

  2. Key Accomplishments • PRS 1.2.0.0 published on FixCentral and iRAM (story 28070) - Globalization support for Tpae (story 28068) - KMQ support: WebSphere MQ Monitoring Agent (story 27849) - KQI support: WebSphere Message Broker Monitoring Agent (story 25392) • Provides health check scenario support eco-system (story 28071) • Environment variable set check (story 27901) • osdp installation prereq check top 3 scenarios support (story 28072) • SeaMonkey browser version check (story 27976) • User passed in single property check requirements and design (story 28214) Demo Demo Demo

  3. Demo 1 - Health check scenario eco-system support • Supported health check scenarios • inactive: product installed, but not started on the system  most cases applies to configuration checking • active: product installed & running on the system  most cases applies to operational checking • Optional command line arguments -health [inactive|active] • Health check results • <PRS_HOME>/result_health_[inactive|active].txt • <PRS_HOME>/result_health_[inactive|active].xml

  4. Demo 1 - Health check scenario eco-system support • Health check logs • <PRS_HOME>/health_[inactive|active].log • Health check configuration files • Location <PRS_HOME>/[UNIX_Linux|Windows]/cfg/health/ • codename.cfg • <prodcode>_<prod_version>.cfg • Sample config file # properties in the following section should only be checked for "-health active" scenario [Health:active] db2.version=v9.7+ # properties in the following section should only be checked for "-health inactive" scenario [Health:inactive] internetExplorer.version=8.0+

  5. Demo 1 - Health check scenario eco-system support • Live demo • Next step • Identify high priority health checks to be implemented • White paper creation on how to extend PRS to add health checks • Call to action – use PRS for your products’ health check

  6. Demo 2 – Environment variable set check • Stage 1 work of Java and JRE version check • What does this check do Identify whether an environment variable is set or not. • Windows supports 4 types of environment variables 1) User -- Applies to the user currently logged on to the computer and is saved between logoffs and restarts 2) System -- Applies to all users of the computer and is saved between logoffs and restarts 3) Volatile -- Applies to current logon session and is not saved between logoffs and restarts 4) Process -- Applies to current process and might be passed to child processes • Unix supports environment variable set check for global variables • Property name, valid value • Property name: env.var.set.<variable name> • Valid value: True|False • On windows [type:<type>] used to specify types. Default is “Process”. For example: env.var.set.JAVA_HOME[type:User]=True

  7. Demo 3 – SeaMonkey browser version check • What does this check do • checks for a specific version of SeaMonkey on the machine • requirement is for Linux platforms only • Property name and value • Property name: os.SeaMonkeyVersion • Valid value: numeric format, for example: 2.10 • special characters can be used to represent types of ranges: • 2.10+ check for version 2.10 or higher • 2.* version can be 2.0, 2.1, 2,2, etc Example: os.SeaMonkeyVersion=2.10+

  8. What is PRS A lightweight and easy-to-usescanning tool to automate prerequisite checks for single or multiple products in a solution • Automated and standardized prerequisite checking solution across products and deployment types • Simplicity of use and lightweight solution • Improve TTV, with ready-to-use out-of-the-box predefined checks • Extensibility to expand coverage easily in the field IBM Prerequisite Scanner Key Benefits & Differentiator

  9. Completed sprint 6 stories Story: As part of OSDP helath checking, investigate the ability to run a single check (28236)Story: as admin services team, I would like PRS to design to support our user scenarios for pre and post installation (28214)Story: osdp installation prereq check support stage2 work (28072)Story: add post-install health check support to PRS as officially supported feature (28071)Story: release PRS 1.2 to FixCentral (28070)Story: remove user's guide from PRS release build (28068)Feature request: SeaMonkey webbrowser version check support (27976)Publish KMQ and KQI agent support to FixCentral (27849)Story: as KMQ agent adopter team, I would like PRS to smoke test KMQ agent support (26419)Story: Add coverage for KMQ and KQI Agent (25392)Feature Request :  Environment variable is set, for example, JAVA_HOME (27901)Add TADDM coverage to support Gulf Breeze Transparent Dev (26442)Story: Evaluate ITM remote deploy training to support GTS engagements (28232)Story: Evaluate existing Oracle prereq scripts for reuse in PRS (28238)Story: For IBM Services engagments, I want to check for Oracle prerequisites as part of the solution (27877)Story: To support GTS PI2 engagement activity, add TADDM, TSAM, ORACLE coverage (28237)

More Related