This document provides release notes for IBM Tivoli Netcool/System Service Monitors and Netcool/Application Service Monitors version 4.0. Key items include over 40 problem fixes, several new subagents and features added, expanded platform support, and various improvements and changes.
This document provides instructions for installing and configuring IBM WebSphere MQ version 6.0 on Windows. It discusses migrating from previous versions of MQ and covers installing both the MQ server and MQ client. The document also describes verifying the installations, applying maintenance updates, uninstalling MQ, and lists the documentation available.
This document provides a summary of changes and installation instructions for Tivoli Storage Manager Version 5.5 backup-archive clients. It includes details on installing clients for AIX, HP-UX, Linux, Solaris and z/OS, as well as configuring options, registering with servers, and getting started with backups and restores. The document contains over 550 pages covering all aspects of installing and using Tivoli Storage Manager backup-archive clients.
This document provides installation and configuration instructions for Data Protection for Oracle Version 5 Release 4. It allows for the backup of Oracle 9i and Oracle 10g databases to Tivoli Storage Manager storage through integration with the RMAN Media Management API. Instructions are provided for AIX, HP-UX, Linux, and Solaris platforms. The document also provides information on configuring Tivoli Storage Manager options, defining policies, using the RMAN and Data Protection for Oracle utilities, and troubleshooting.
Proposal ONE MEDIC Pendahuluan 1 PPeennddaahhuulluuaann Rumah sakit merupakan sebuah institusi pelayanan kesehatan yang tidak berdiri sendiri. Secara eksternal sebuah rumah sakit senantiasa terkait dengan entitas-entitas luar seperti farmasi, pasien, asuransi dan lain-lain. Sedangkan secara internal rumah sakit memiliki entitas-entitas seperti instalasi rawat inap, poliklinik, apotek, laboratorium, dokter dan lain sebagainya. Sebagai entitas internal bagian-bagian tersebut tidak dapat saling lepas. Setiap output dari satu entitas internal bisa jadi adalah input bagi entitas internal lainnya. Karena proses saling keterkaitan inilah mengapa sebuah sistem yang terpadu dan komprehensif dibutuhkan. Data yang akurat serta penyediaan infomasi yang cepat, merupakan salah satu faktor penunjang kinerja pelayanan rumah sakit. Penyediaan dan pengelolaan data ini dapat dirancang, dibangun dan dikembangkan dalam sebuah sistem informasi rumah sakit. Sistem informasi yang tepat bagi rumah sakit hendaknya dapat mengikuti pola dinamika rumah sakit, menjaga integritas data serta aman. Sebuah studi yang pernah kami lakukan, menemukan beberapa faktor penyebab mengapa sistem informasi dalam sebuah rumah sakit tidak berjalan, yakni: 1. Sistem manual yang tidak memadai. Pada saat ini sistem manual kerap kali kurang mampu menjawab kebutuhan masyarakat akan kinerja pelayanan prima yang menuntut kecepatan dan keakuratan. 2. Sistem dokumentasi yang tidak “traceable”. Dokumentasi yang menumpuk mengakibatkan kesulitan dalam penelusuran dan pencarian data yang dibutuhkan. Lambatnya proses pencarian data dan pengelolaan informasi dapat menurunkan kinerja pelayanan rumah sakit. 3. Pola komunikasi data konvensional; Mengingat rumah sakit merupakan institusi yang terdiri dari banyak sub sistem dan mungkin secara fisik antar sub sistem terletak berjauhan, maka untuk mengumpulkan data-data yang diperlukan akan membutuhkan waktu relatif lebih lama. 4. Penggunaan aplikasi yang tidak terintegrasi; Aplikasi yang tidak terintegrasi dapat mengakibatkan pemeliharaan sistem yang kompleks, menghasilkan pekerjaan tambahan pada saat pelaporan dan belum tentu output dari masing- masing sistem tersebut compatible. 5. Aplikasi dengan teknologi yang sukar dikembangkan; Aplikasi yang tidak scalable akan sulit untuk disesuaikan terhadap kebutuhan dan dinamika organisasi rumah sakit. 6. Layanan teknis yang tidak menunjang; Sulitnya menghubungi technical support akan memberikan kesulitan dalam proses pencarian solusi. Terlebih lagi tidak adanya pustaka yang memadai serta tidak disertai dengan transfer knowledge yang baik, akan menambah kesulitan dalam penanganan masalah yang mungkin muncul.
This document provides an overview of implementing OMEGAMON XE for Messaging V6.0:
- It discusses WebSphere MQ, WebSphere Message Broker, and WebSphere InterChange Server as messaging middleware.
- It describes the architecture and deployment scenarios of OMEGAMON XE.
- It covers installing the OMEGAMON infrastructure including the Tivoli Enterprise Monitoring and Portal Servers.
- It explains how to install and configure WebSphere MQ agents on z/OS, UNIX/Linux, and Windows.
- It demonstrates using OMEGAMON XE to configure WebSphere MQ resources through its WebSphere MQ Configuration feature.
This document provides reference information for administrators about commands and options for IBM Tivoli Storage Manager Version 6.1 for Linux. It contains information about issuing commands from the administrative client and server console, entering administrative commands, controlling command processing, and descriptions of administrative commands.
This document is a deployment guide for IBM Tivoli Monitoring V6.2. It provides best practices for installing and configuring the product's components, including the monitoring server, portal server, monitoring agents, and Tivoli Data Warehouse. It also covers upgrading from previous versions, agent deployment methods, database requirements, and sample deployment scenarios.
This document provides a step-by-step guide for deploying IBM Tivoli Monitoring 6.1 in small to large environments. It discusses planning the installation, defining the architecture, creating deployment plans, installing the various Tivoli Monitoring components, and configuring the system. The guide also covers demonstrations of a single machine proof of concept installation and a small installation using DB2 Workgroup Edition.
This document provides instructions for installing and configuring IBM WebSphere MQ version 6.0 on Windows. It discusses migrating from previous versions of MQ and covers installing both the MQ server and MQ client. The document also describes verifying the installations, applying maintenance updates, uninstalling MQ, and lists the documentation available.
This document provides a summary of changes and installation instructions for Tivoli Storage Manager Version 5.5 backup-archive clients. It includes details on installing clients for AIX, HP-UX, Linux, Solaris and z/OS, as well as configuring options, registering with servers, and getting started with backups and restores. The document contains over 550 pages covering all aspects of installing and using Tivoli Storage Manager backup-archive clients.
This document provides installation and configuration instructions for Data Protection for Oracle Version 5 Release 4. It allows for the backup of Oracle 9i and Oracle 10g databases to Tivoli Storage Manager storage through integration with the RMAN Media Management API. Instructions are provided for AIX, HP-UX, Linux, and Solaris platforms. The document also provides information on configuring Tivoli Storage Manager options, defining policies, using the RMAN and Data Protection for Oracle utilities, and troubleshooting.
Proposal ONE MEDIC Pendahuluan 1 PPeennddaahhuulluuaann Rumah sakit merupakan sebuah institusi pelayanan kesehatan yang tidak berdiri sendiri. Secara eksternal sebuah rumah sakit senantiasa terkait dengan entitas-entitas luar seperti farmasi, pasien, asuransi dan lain-lain. Sedangkan secara internal rumah sakit memiliki entitas-entitas seperti instalasi rawat inap, poliklinik, apotek, laboratorium, dokter dan lain sebagainya. Sebagai entitas internal bagian-bagian tersebut tidak dapat saling lepas. Setiap output dari satu entitas internal bisa jadi adalah input bagi entitas internal lainnya. Karena proses saling keterkaitan inilah mengapa sebuah sistem yang terpadu dan komprehensif dibutuhkan. Data yang akurat serta penyediaan infomasi yang cepat, merupakan salah satu faktor penunjang kinerja pelayanan rumah sakit. Penyediaan dan pengelolaan data ini dapat dirancang, dibangun dan dikembangkan dalam sebuah sistem informasi rumah sakit. Sistem informasi yang tepat bagi rumah sakit hendaknya dapat mengikuti pola dinamika rumah sakit, menjaga integritas data serta aman. Sebuah studi yang pernah kami lakukan, menemukan beberapa faktor penyebab mengapa sistem informasi dalam sebuah rumah sakit tidak berjalan, yakni: 1. Sistem manual yang tidak memadai. Pada saat ini sistem manual kerap kali kurang mampu menjawab kebutuhan masyarakat akan kinerja pelayanan prima yang menuntut kecepatan dan keakuratan. 2. Sistem dokumentasi yang tidak “traceable”. Dokumentasi yang menumpuk mengakibatkan kesulitan dalam penelusuran dan pencarian data yang dibutuhkan. Lambatnya proses pencarian data dan pengelolaan informasi dapat menurunkan kinerja pelayanan rumah sakit. 3. Pola komunikasi data konvensional; Mengingat rumah sakit merupakan institusi yang terdiri dari banyak sub sistem dan mungkin secara fisik antar sub sistem terletak berjauhan, maka untuk mengumpulkan data-data yang diperlukan akan membutuhkan waktu relatif lebih lama. 4. Penggunaan aplikasi yang tidak terintegrasi; Aplikasi yang tidak terintegrasi dapat mengakibatkan pemeliharaan sistem yang kompleks, menghasilkan pekerjaan tambahan pada saat pelaporan dan belum tentu output dari masing- masing sistem tersebut compatible. 5. Aplikasi dengan teknologi yang sukar dikembangkan; Aplikasi yang tidak scalable akan sulit untuk disesuaikan terhadap kebutuhan dan dinamika organisasi rumah sakit. 6. Layanan teknis yang tidak menunjang; Sulitnya menghubungi technical support akan memberikan kesulitan dalam proses pencarian solusi. Terlebih lagi tidak adanya pustaka yang memadai serta tidak disertai dengan transfer knowledge yang baik, akan menambah kesulitan dalam penanganan masalah yang mungkin muncul.
This document provides an overview of implementing OMEGAMON XE for Messaging V6.0:
- It discusses WebSphere MQ, WebSphere Message Broker, and WebSphere InterChange Server as messaging middleware.
- It describes the architecture and deployment scenarios of OMEGAMON XE.
- It covers installing the OMEGAMON infrastructure including the Tivoli Enterprise Monitoring and Portal Servers.
- It explains how to install and configure WebSphere MQ agents on z/OS, UNIX/Linux, and Windows.
- It demonstrates using OMEGAMON XE to configure WebSphere MQ resources through its WebSphere MQ Configuration feature.
This document provides reference information for administrators about commands and options for IBM Tivoli Storage Manager Version 6.1 for Linux. It contains information about issuing commands from the administrative client and server console, entering administrative commands, controlling command processing, and descriptions of administrative commands.
This document is a deployment guide for IBM Tivoli Monitoring V6.2. It provides best practices for installing and configuring the product's components, including the monitoring server, portal server, monitoring agents, and Tivoli Data Warehouse. It also covers upgrading from previous versions, agent deployment methods, database requirements, and sample deployment scenarios.
This document provides a step-by-step guide for deploying IBM Tivoli Monitoring 6.1 in small to large environments. It discusses planning the installation, defining the architecture, creating deployment plans, installing the various Tivoli Monitoring components, and configuring the system. The guide also covers demonstrations of a single machine proof of concept installation and a small installation using DB2 Workgroup Edition.
This document provides installation and user guidance for IBM Tivoli Storage Manager for Databases Version 5.5, which provides data protection for Microsoft SQL Server. The document covers installing and configuring the software, how to perform backups and restores using both the graphical and command line interfaces, and how to schedule backups with the Tivoli Storage Manager scheduler. It also includes appendices with additional information on topics like silent installation, policy examples, restoring the master database, and messages.
The document is about end-to-end automation with IBM Tivoli System Automation for Multiplatforms. It provides an overview of IBM Tivoli System Automation for Multiplatforms V2.1 and IBM Tivoli System Automation for z/OS V3.1. It then presents three case study scenarios implementing end-to-end automation across different platforms using the products.
This document is the user manual for Oracle VM VirtualBox version 4.1.8. It provides instructions on installing VirtualBox on various host operating systems like Windows, Mac OS X, Linux and Solaris. It also provides details on configuring virtual machines in VirtualBox, including supported guest operating systems, emulated hardware, and settings for components like the system, display, storage, audio, network, USB and more. The manual is intended to guide users through using VirtualBox's virtualization functionality.
This document provides an overview and technical details about IBM Tivoli OMEGAMON XE V3.1, a performance monitoring and problem determination tool for z/OS environments. It discusses the product architecture and components, data collection processes, high availability features, installation and configuration procedures, and maintenance tasks. The document is intended for system programmers and administrators responsible for implementing and managing OMEGAMON solutions.
Oracle vm virtual box usermanual v4.1.20avtechpanama
This document is the user manual for Oracle VM VirtualBox version 4.1.20. It provides instructions on installing VirtualBox on various host operating systems like Windows, Mac OS X, Linux and Solaris. It also provides details on configuring virtual machines in VirtualBox, including supported guest operating systems, emulated hardware, and settings for components like the system, display, storage, audio, network, serial ports and USB support. The manual is intended to guide users through using VirtualBox's virtualization functionality.
TechBook: Using EMC VNX Storage with VMware vSphereEMC
This EMC Engineering TechBook describes how VMware vSphere works with the EMC VNX series. The content in this TechBook is intended for storage administrators, system administrators, and VMware vSphere administrators.
This document provides administration guidance for version 5.5.0 of the HSM for Windows client. It covers installation, configuration, defining migration jobs, reconciliation, commands, and troubleshooting. The document contains chapters on installation, the graphical user interface, migration jobs, commands, backup integration, parameters, and problem determination.
This document is the user manual for XORP version 1.8-CT. It describes how to configure and operate a router running the XORP software. The manual contains information on XORP command structure and modes, how to configure network interfaces, firewall rules, routing protocols and other aspects of the XORP router. It is covered by an open source license and the community is encouraged to provide feedback and contributions to improve the manual.
Learn about IBM AIX Version 7.1 Differences Guide. This IBM Redbooks publication focuses on the enhancements to IBM AIX Version 7.1 Standard Edition. It is intended to help system administrators, developers, and users understand these enhancements and evaluate potential benefits in their own environments. For more information on Power Systems, visit http://ibm.co/Lx6hfc.
Visit the official Scribd Channel of IBM India Smarter Computing at http://bit.ly/VwO86R to get access to more documents.
This document provides an administrator's reference for IBM Tivoli Storage Manager Version 6.2 for Windows. It contains information on administering the server from the command-line interface, including issuing commands, entering administrative commands, and descriptions of individual administrative commands. The document contains over 1300 pages of documentation.
The document is a certification guide that describes the certification process and prerequisites for IBM Tivoli Workload Scheduler V8.4. It provides sample test questions to help prepare for the certification exam. The guide includes information about the recommended resources for study such as courses and publications. It aims to enable readers to earn certification for their skills and expertise with Tivoli Workload Scheduler V8.4.
This document is the user manual for Oracle VM VirtualBox version 4.0.2. It provides instructions on installing VirtualBox on various host operating systems like Windows, Mac OS X, Linux and Solaris. It also describes how to configure, install and use guest operating systems within VirtualBox virtual machines. Key features covered include taking snapshots of VMs, changing VM hardware settings, enabling shared folders and USB support.
This document provides an overview and instructions for installing and using IBM TotalStorage Productivity Center for Replication on Windows 2003. It discusses planning the installation, including hardware and software requirements. It then covers installing DB2, TotalStorage Productivity Center for Replication, and the Two Site BC module. Next it discusses post-installation tasks like configuring Ethernet cards and storage subsystems. Finally it provides examples of using TotalStorage Productivity Center for Replication to set up replication sessions between servers and various storage systems, including SAN Volume Controller, ESS 800, and DS8000.
This document provides an overview and introduction to installing and migrating to IBM Tivoli Workload Scheduler V8.3. It covers prerequisites, a new installation process using a wizard, upgrading from previous versions, and new features such as an improved infrastructure using WebSphere and DB2/Oracle databases. The document is intended to help users get started with V8.3 and provide best practices for installation and migration.
This document provides an overview and instructions for installing and configuring IBM Tivoli OMEGAMON XE for monitoring WebSphere Business Integration middleware. It discusses the OMEGAMON distributed architecture and describes how to install the Candle Management Server, OMEGAMON DE agents, and configure WebSphere MQ monitoring. The document also provides examples of using the OMEGAMON configuration tools to define WebSphere MQ resources, schedule actions, and view monitoring data.
The document introduces Honeywell's Zephyr digital airflow sensors. It provides an overview of how airflow sensors work using heat transfer principles. The Zephyr sensors offer high accuracy, customizability, and insensitivity to mounting orientation or altitude. They have applications in medical devices like ventilators and industrial uses like HVAC systems. The sensors communicate digitally using I2C protocol.
The document provides information about the history and development of Linux. It states that in 1991, Linus Torvalds, a Finnish computer science student, released the first version of the Linux kernel. Though intended as a hobby project, Linux gained significant support from other developers over the years. The kernel was expanded to be capable of more than its original capabilities.
This document provides training materials for configuring common applications in a VERITAS Cluster Server (VCS) environment. It includes conceptual overviews, configuration procedures, and lab exercises for clustering applications, databases, and NFS services. The labs allow students to practice setting up Application, Oracle, and NFS resources in a simulated VCS cluster. The document assumes knowledge of VCS fundamentals and includes varying levels of detail to accommodate different experience levels.
Road to Government 2.0: Technological Problems and Solutions for Transparency...Daniel X. O'Neil
See more at: http://www.aspeninstitute.org/publications/road-government-20-technological-problems-solutions-transparency-efficiency
Greg Ferenstein
March 14, 2013
The 2012 FOCAS convened 38 leaders and developers from government, media and communications enterprises, localities, consumer/user groups and academia to define the problems of open and innovative governance and develop solutions. Road to Government 2.0: Technological Problems and Solutions for Transparency, Efficiency and Participation, summarizes the insights, initiatives and recommendations emanating from the Forum. The report, written by Forum rapporteur Greg Ferenstein, describes the origins of the open government movement, provides a discussion of the meaningful open governance efforts around the world and then addresses a number of serious shortcomings and subsequent solutions in open government. The recommendations include measures to enhance public awareness and media engagement, modifications to the government procurement process and an emphasis on useful participatory government to help improve information flow, communication and citizen interactions.
- See more at: http://www.aspeninstitute.org/publications/road-government-20-technological-problems-solutions-transparency-efficiency#sthash.tRU6v1Qu.dpuf
This document provides installation and user guidance for IBM Tivoli Storage Manager for Databases Version 5.5, which provides data protection for Microsoft SQL Server. The document covers installing and configuring the software, how to perform backups and restores using both the graphical and command line interfaces, and how to schedule backups with the Tivoli Storage Manager scheduler. It also includes appendices with additional information on topics like silent installation, policy examples, restoring the master database, and messages.
The document is about end-to-end automation with IBM Tivoli System Automation for Multiplatforms. It provides an overview of IBM Tivoli System Automation for Multiplatforms V2.1 and IBM Tivoli System Automation for z/OS V3.1. It then presents three case study scenarios implementing end-to-end automation across different platforms using the products.
This document is the user manual for Oracle VM VirtualBox version 4.1.8. It provides instructions on installing VirtualBox on various host operating systems like Windows, Mac OS X, Linux and Solaris. It also provides details on configuring virtual machines in VirtualBox, including supported guest operating systems, emulated hardware, and settings for components like the system, display, storage, audio, network, USB and more. The manual is intended to guide users through using VirtualBox's virtualization functionality.
This document provides an overview and technical details about IBM Tivoli OMEGAMON XE V3.1, a performance monitoring and problem determination tool for z/OS environments. It discusses the product architecture and components, data collection processes, high availability features, installation and configuration procedures, and maintenance tasks. The document is intended for system programmers and administrators responsible for implementing and managing OMEGAMON solutions.
Oracle vm virtual box usermanual v4.1.20avtechpanama
This document is the user manual for Oracle VM VirtualBox version 4.1.20. It provides instructions on installing VirtualBox on various host operating systems like Windows, Mac OS X, Linux and Solaris. It also provides details on configuring virtual machines in VirtualBox, including supported guest operating systems, emulated hardware, and settings for components like the system, display, storage, audio, network, serial ports and USB support. The manual is intended to guide users through using VirtualBox's virtualization functionality.
TechBook: Using EMC VNX Storage with VMware vSphereEMC
This EMC Engineering TechBook describes how VMware vSphere works with the EMC VNX series. The content in this TechBook is intended for storage administrators, system administrators, and VMware vSphere administrators.
This document provides administration guidance for version 5.5.0 of the HSM for Windows client. It covers installation, configuration, defining migration jobs, reconciliation, commands, and troubleshooting. The document contains chapters on installation, the graphical user interface, migration jobs, commands, backup integration, parameters, and problem determination.
This document is the user manual for XORP version 1.8-CT. It describes how to configure and operate a router running the XORP software. The manual contains information on XORP command structure and modes, how to configure network interfaces, firewall rules, routing protocols and other aspects of the XORP router. It is covered by an open source license and the community is encouraged to provide feedback and contributions to improve the manual.
Learn about IBM AIX Version 7.1 Differences Guide. This IBM Redbooks publication focuses on the enhancements to IBM AIX Version 7.1 Standard Edition. It is intended to help system administrators, developers, and users understand these enhancements and evaluate potential benefits in their own environments. For more information on Power Systems, visit http://ibm.co/Lx6hfc.
Visit the official Scribd Channel of IBM India Smarter Computing at http://bit.ly/VwO86R to get access to more documents.
This document provides an administrator's reference for IBM Tivoli Storage Manager Version 6.2 for Windows. It contains information on administering the server from the command-line interface, including issuing commands, entering administrative commands, and descriptions of individual administrative commands. The document contains over 1300 pages of documentation.
The document is a certification guide that describes the certification process and prerequisites for IBM Tivoli Workload Scheduler V8.4. It provides sample test questions to help prepare for the certification exam. The guide includes information about the recommended resources for study such as courses and publications. It aims to enable readers to earn certification for their skills and expertise with Tivoli Workload Scheduler V8.4.
This document is the user manual for Oracle VM VirtualBox version 4.0.2. It provides instructions on installing VirtualBox on various host operating systems like Windows, Mac OS X, Linux and Solaris. It also describes how to configure, install and use guest operating systems within VirtualBox virtual machines. Key features covered include taking snapshots of VMs, changing VM hardware settings, enabling shared folders and USB support.
This document provides an overview and instructions for installing and using IBM TotalStorage Productivity Center for Replication on Windows 2003. It discusses planning the installation, including hardware and software requirements. It then covers installing DB2, TotalStorage Productivity Center for Replication, and the Two Site BC module. Next it discusses post-installation tasks like configuring Ethernet cards and storage subsystems. Finally it provides examples of using TotalStorage Productivity Center for Replication to set up replication sessions between servers and various storage systems, including SAN Volume Controller, ESS 800, and DS8000.
This document provides an overview and introduction to installing and migrating to IBM Tivoli Workload Scheduler V8.3. It covers prerequisites, a new installation process using a wizard, upgrading from previous versions, and new features such as an improved infrastructure using WebSphere and DB2/Oracle databases. The document is intended to help users get started with V8.3 and provide best practices for installation and migration.
This document provides an overview and instructions for installing and configuring IBM Tivoli OMEGAMON XE for monitoring WebSphere Business Integration middleware. It discusses the OMEGAMON distributed architecture and describes how to install the Candle Management Server, OMEGAMON DE agents, and configure WebSphere MQ monitoring. The document also provides examples of using the OMEGAMON configuration tools to define WebSphere MQ resources, schedule actions, and view monitoring data.
The document introduces Honeywell's Zephyr digital airflow sensors. It provides an overview of how airflow sensors work using heat transfer principles. The Zephyr sensors offer high accuracy, customizability, and insensitivity to mounting orientation or altitude. They have applications in medical devices like ventilators and industrial uses like HVAC systems. The sensors communicate digitally using I2C protocol.
The document provides information about the history and development of Linux. It states that in 1991, Linus Torvalds, a Finnish computer science student, released the first version of the Linux kernel. Though intended as a hobby project, Linux gained significant support from other developers over the years. The kernel was expanded to be capable of more than its original capabilities.
This document provides training materials for configuring common applications in a VERITAS Cluster Server (VCS) environment. It includes conceptual overviews, configuration procedures, and lab exercises for clustering applications, databases, and NFS services. The labs allow students to practice setting up Application, Oracle, and NFS resources in a simulated VCS cluster. The document assumes knowledge of VCS fundamentals and includes varying levels of detail to accommodate different experience levels.
Road to Government 2.0: Technological Problems and Solutions for Transparency...Daniel X. O'Neil
See more at: http://www.aspeninstitute.org/publications/road-government-20-technological-problems-solutions-transparency-efficiency
Greg Ferenstein
March 14, 2013
The 2012 FOCAS convened 38 leaders and developers from government, media and communications enterprises, localities, consumer/user groups and academia to define the problems of open and innovative governance and develop solutions. Road to Government 2.0: Technological Problems and Solutions for Transparency, Efficiency and Participation, summarizes the insights, initiatives and recommendations emanating from the Forum. The report, written by Forum rapporteur Greg Ferenstein, describes the origins of the open government movement, provides a discussion of the meaningful open governance efforts around the world and then addresses a number of serious shortcomings and subsequent solutions in open government. The recommendations include measures to enhance public awareness and media engagement, modifications to the government procurement process and an emphasis on useful participatory government to help improve information flow, communication and citizen interactions.
- See more at: http://www.aspeninstitute.org/publications/road-government-20-technological-problems-solutions-transparency-efficiency#sthash.tRU6v1Qu.dpuf
SmartView Reporter can be installed in either a standalone or distributed configuration. A standalone installation installs SmartView Reporter on the same machine as the SmartCenter server, while a distributed installation installs SmartView Reporter on a separate dedicated machine. The distributed installation is recommended for better performance. The document provides step-by-step instructions for installing SmartView Reporter in both standalone and distributed configurations on Windows and Solaris platforms.
Running ColdFusion MX 7 on Linux and UnixSteven Erat
ColdFusion has supported Linux since 1999. This document discusses ColdFusion MX 7's support for Unix and Linux systems. It provides an overview of ColdFusion's history on these platforms, system requirements for ColdFusion MX 7, migration paths from previous versions, and new features in ColdFusion MX 7. It also covers general concerns about running ColdFusion on Unix/Linux and steps for a multiserver configuration installation on Linux via the console.
Art and Science of Web Sites Performance: A Front-end ApproachJiang Zhu
People love fast web sites, but up until now developers have been focusing on the wrong area. Network (TCP, buffers, routing) performance and Backend (web server, database, etc.) performance are important for reducing hardware costs and improving efficiency, but for most pages 80% of the load time is spent on the frontend (HTML, CSS, JavaScript, images, iframes, and others). We will talk about the best practices for making web pages faster, provide case study from top web site, and introduce the tools we use for researching performance. In addition to know how to improve web performance, we will also try to gain an understanding of the fundamentals of how the Internet works including DNS, HTTP, and browsers. This talks was given as an Educational Series called Fog Computing Reading Group at Cisco Advanced Architecture and Research. The content is derived from the materials by Steven Sounders (Google/Stanford), Collin Jackson (Stanford/CMU) and Daniel Austin (eBay).
This document is the September-October 2013 issue of TELE-audiovision, a trade magazine for the digital television industry. The main stories include product reviews of signal analyzers, receivers, and headend equipment from companies like Deviser, Horizon, DragonSat, and SPAUN. There are also articles on topics like self-made IPTV, ultra high definition television, and new digital technologies. Company profiles of ÖREIND, CHANGHONG, and SPEEDCAST are featured.
The document discusses common web application attacks and how to mitigate risks. It covers injection attacks like SQL and OS command injection, session management vulnerabilities, cross-site scripting (XSS), cross-site request forgery (CSRF), password storage issues, and other risks like sensitive data exposure. It emphasizes the importance of input validation, output encoding, secure sessions, use of HTTPS, and other best practices to develop securely. Code examples and demos are provided to illustrate some of these vulnerabilities.
A hybrid kernel is a kernel architecture that combines aspects of microkernel and monolithic kernel architectures. It aims to have the modularity of a microkernel but is implemented similarly to a monolithic kernel, with nearly all operating system services running in kernel space rather than user space. The best known example is the Microsoft Windows NT kernel, which is classified as a hybrid kernel due to some subsystems running in user mode processes rather than purely in kernel mode. Another example is the XNU kernel used in macOS and iOS, which combines the Mach microkernel with BSD components.
Embedded Android provides concise summaries of key concepts in 3 sentences or less:
1. Android is an open source operating system used widely in mobile devices. It is based on the Linux kernel and features an application framework for reuse and replacement of components.
2. The Android ecosystem involves many players including Google, hardware manufacturers, mobile operators, and app developers. Over 850,000 apps are available in the Android Market and Google Play store.
3. Android device requirements include compliance with the Compatibility Definition Document for software and hardware compatibility, as well as passing the Compatibility Test Suite for certification. Development tools include the Android SDK, emulator, and debugging tools.
Disk 1 contains installation files and source files for a C++ library. Disk 1 also contains two ZIP files: CLIBSRC containing more source files for the C++ library, and CMDLG31 containing example files for a Windows 3.1 application. The FILELIST file provides a documentation of files, and the INCLUDE ZIP file contains Borland C++ header files.
Este documento presenta información sobre biocombustibles. Explica que los biocombustibles son combustibles producidos a partir de materias primas biológicas como reemplazo para combustibles fósiles en aras de reducir la contaminación y dependencia del petróleo. Describe algunos tipos de biocombustibles como etanol y biodiésel, y analiza ventajas como menores emisiones contaminantes, así como desventajas como mayores costos de producción. El documento también examina factores como la seguridad alimentaria y el impacto econ
모바일 환경이 다가와서 우리의 개발 환경도 우리가 생활 하는 일상을 변화 하고 있습니다.
앞으로 스마트 단말들이 성장하면서 웹앱의 진화도 빠르게 될 것으로 예측 됩니다.
2년내 Pad 기반의 컴퓨팅 환경이 우리의 대중을 사로 잡지 않을까 하는 예측을 해보며
앞으로 필요한 모바일 서비스의 중요한 부분은 Widget이 되지 않을까 합니다.
..
감사합니다.
The document discusses OpenObject, an open-source Rapid Application Development (RAD) framework written in Python. OpenObject features include an Object-Relationship Mapping (ORM) layer, template-based Model-View-Controller (MVC) interfaces, and report generation. The document also provides instructions on installing OpenObject, describes its typical module structure, and explains how to define business objects using the ORM.
The document provides an overview of Scrum, describing its roles like Product Owner and Scrum Master, meetings like the Daily Scrum and Sprint Review, and artifacts like the Product Backlog and Sprint Backlog; it explains that Scrum is a framework for incremental product development using cross-functional, self-organizing teams who work in sprints to develop working software increments; and it notes some challenges with "faking" Scrum by modifying parts that require overcoming organizational impediments.
This document provides installation and configuration instructions for Data Protection for Oracle, which allows backups of Oracle databases to Tivoli Storage Manager. It describes requirements for supported Windows platforms, outlines the installation process, and provides guidance on configuring Tivoli Storage Manager options and policies. It also covers using Recovery Manager (RMAN) and the provided utilities to perform backups and restores. The document contains appendices with a quick start guide, using the Tivoli scheduler, support information, and accessibility details.
This document is the administration manual for AltiGen Communications' MAX Communication Server (MAXCS) 6.5. It provides an overview of the system features of MAXCS, which is an IP PBX system, and covers installation, configuration, and administration using the MaxAdministrator tool. The manual includes details on system requirements, licensing, setting parameters and call routing rules. It also describes the various views and windows in MaxAdministrator for managing extensions, trunks, call logs, and other system components.
This document provides an overview of Citrix XenApp 5 and the XenApp 5 Feature Pack. It discusses the different product editions, new features in XenApp 5, and enhanced capabilities in the Feature Pack. Key areas covered include application delivery, streaming, Receiver, XenServer virtualization, load testing, provisioning, profiles, monitoring, security, optimization, and voice services. It also provides guidance on deploying XenApp 5 farms and getting started with application management.
This document provides an overview and instructions for configuring and using IBM Tivoli System Automation for z/OS V3R1. It discusses new features of V3R1 including integration with IBM Tivoli OMEGAMON and enhanced GDPS support. The document then covers tasks for setting up and customizing System Automation for z/OS such as defining VTAM configurations, the policy database, and automating startup tasks. It also provides guidance on using functions like the OMEGAMON interface, end-to-end automation capabilities, and managing SYSPLEXes with the Processor Operations feature.
The document is a Getting Started Guide for SRC PE Software Release 4.2.x. It provides an overview of SRC components including the Service Activation Engine, Subscriber Information Collector, Juniper Policy Server, Network Information Collector, and Redirect Server. It also describes SRC data repositories like the Juniper Networks Database, directory, and Session State Registrar. The guide covers management tools for SRC like the SRC CLI, C-Web interface, Policy and Management application, and SDX SNMP agent.
This document provides an installation and configuration guide for IBM Tivoli Directory Server version 6.3. It contains information about installing the server, clients, language packs, and other components across various platforms like Windows, Linux, AIX, Solaris, and HP-UX. The guide also describes how to create and administer directory server instances, configure databases, tune performance, back up and restore data, and more.
This document provides an overview and introduction to IBM's Software Defined Network for Virtual Environments (SDN VE) solution. It describes the components of SDN VE including the Distributed Services Appliance, Distributed Connectivity Service, Distributed Gateways, and 5000V Host Module. It also explains key concepts such as the overlay network, network encapsulation techniques, and how SDN VE addresses network segmentation challenges in virtualized environments.
This document provides a step-by-step guide for deploying IBM Tivoli Monitoring 6.1 in small to large environments. It covers installing and configuring the various Tivoli Monitoring components, including the database, Tivoli Enterprise Monitoring Server (TEMS), Tivoli Enterprise Portal Server, agents, and more. The guide also discusses backup strategies, uninstall procedures, and how to work with the Tivoli Enterprise Portal client.
This document provides an overview and instructions for installing and using IBM TotalStorage Productivity Center for Replication on Windows 2003. It discusses planning the installation, including hardware and software requirements. It then covers installing DB2, TotalStorage Productivity Center for Replication, and the Two Site BC module. Next it discusses post-installation tasks like configuring DS8000 Ethernet cards and storage subsystems. Finally it provides instructions for setting up and using TotalStorage Productivity Center for Replication to manage replication between various storage systems.
This document provides an overview and instructions for deploying and using IBM Tivoli Composite Application Manager for WebSphere V6.0. It describes how to plan, install, and configure the managing server and data collectors to monitor WebSphere application servers. It also provides guidance on using the monitoring console to analyze performance issues.
This document provides an overview and instructions for installing and using IBM Tivoli Composite Application Manager for WebSphere V6.0. It discusses planning the installation, installing the managing server and data collectors, configuring the system, and using the tool to monitor applications, troubleshoot performance issues, and determine problems with the tool.
The document provides information about using the Symantec Backup Exec Command Line Applet, including:
- Required command line switches to perform Backup Exec functions like running backup jobs.
- Supported operations like backup, restore, managing media, and getting job status.
- Creating job scripts to automate backup jobs using command line switches.
- Targeting remote Backup Exec servers and logging in with credentials.
This document provides an overview and instructions for installing and using IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1. It discusses monitoring WebSphere MQ, WebSphere Message Broker, and WebSphere Interchange Server. The document covers installing the OMEGAMON infrastructure including the Candle Management Server and agents. It also provides examples of configuring and monitoring WebSphere MQ resources and troubleshooting scenarios.
This document provides a user's guide for using xPC Target software to model, simulate, and implement real-time applications on a target PC. Key features of xPC Target include a real-time kernel for running models on a target PC in real time, support for signal acquisition and analysis, and parameter tuning. The guide describes the hardware environment of a host PC connected to a target PC, and the software environment for host-target communication. It also outlines the rapid prototyping process and various user interaction methods with xPC Target.
This document provides guidance on setting up a high availability SAP NetWeaver environment using SUSE Linux Enterprise Server and the SUSE Linux Enterprise High Availability Extension. It includes installing SAP NetWeaver with the Enqueue Replication Server and integrating the sap_suse_cluster_connector to provide application-level redundancy. The described configuration has passed all SAP certification tests for high availability.
This document provides instructions for configuring a DeviceNet network. It discusses choosing between a single network or subnets, selecting a scanner, and bridging networks. It also covers connecting devices to the network, setting node addresses, and configuring the network both offline and online using RSNetWorx software. A section on automatically configuring the network with AutoScan is also included.
The IBM Flex System p260 and p460 Compute Nodes are IBM Power Systems servers optimized for virtualization, performance, and efficiency. The nodes support IBM AIX, IBM i, or Linux operating environments, and are designed to run various workloads in IBM PureFlex System. This IBM Redbooks publication is a comprehensive guide to IBM PureFlex System and the Power Systems compute nodes. We introduce the offerings and describe the compute nodes in detail. We then describe planning and implementation steps and go through some of the key the management features of the IBM Flex System Manager management node. For more information on Pure Systems, visit http://ibm.co/18vDnp6.
Visit http://bit.ly/KWh5Dx to 'Follow' the official Twitter handle of IBM India Smarter Computing.
This document provides instructions for installing and configuring Insight Tech Console and Report Server. It covers supported operating systems, installation procedures for Windows and Mac computers, updating Tech Console and managed machines, configuring Tech Console preferences, and basic usage instructions. The guide is intended to help IT and technical staff use Tech Console's central management capabilities for tasks like hardware and software inventory, updating systems, monitoring security, and generating utilization reports.
This document is a deployment guide for IBM Tivoli Monitoring V6.2. It provides best practices for installing and configuring the product. It discusses the IT environment requirements and hardware/software prerequisites. It also includes sample deployment scenarios and steps for upgrading from previous versions. The guide is intended to help customers successfully plan and implement IBM Tivoli Monitoring.
Economic Risk Factor Update: June 2024 [SlideShare]Commonwealth
May’s reports showed signs of continued economic growth, said Sam Millette, director, fixed income, in his latest Economic Risk Factor Update.
For more market updates, subscribe to The Independent Market Observer at https://blog.commonwealth.com/independent-market-observer.
BONKMILLON Unleashes Its Bonkers Potential on Solana.pdfcoingabbar
Introducing BONKMILLON - The Most Bonkers Meme Coin Yet
Let's be real for a second – the world of meme coins can feel like a bit of a circus at times. Every other day, there's a new token promising to take you "to the moon" or offering some groundbreaking utility that'll change the game forever. But how many of them actually deliver on that hype?
STREETONOMICS: Exploring the Uncharted Territories of Informal Markets throug...sameer shah
Delve into the world of STREETONOMICS, where a team of 7 enthusiasts embarks on a journey to understand unorganized markets. By engaging with a coffee street vendor and crafting questionnaires, this project uncovers valuable insights into consumer behavior and market dynamics in informal settings."
2. Elemental Economics - Mineral demand.pdfNeal Brewster
After this second you should be able to: Explain the main determinants of demand for any mineral product, and their relative importance; recognise and explain how demand for any product is likely to change with economic activity; recognise and explain the roles of technology and relative prices in influencing demand; be able to explain the differences between the rates of growth of demand for different products.
Lecture slide titled Fraud Risk Mitigation, Webinar Lecture Delivered at the Society for West African Internal Audit Practitioners (SWAIAP) on Wednesday, November 8, 2023.
OJP data from firms like Vicinity Jobs have emerged as a complement to traditional sources of labour demand data, such as the Job Vacancy and Wages Survey (JVWS). Ibrahim Abuallail, PhD Candidate, University of Ottawa, presented research relating to bias in OJPs and a proposed approach to effectively adjust OJP data to complement existing official data (such as from the JVWS) and improve the measurement of labour demand.
5 Tips for Creating Standard Financial ReportsEasyReports
Well-crafted financial reports serve as vital tools for decision-making and transparency within an organization. By following the undermentioned tips, you can create standardized financial reports that effectively communicate your company's financial health and performance to stakeholders.
8. v NBS 039092 — The agent should save its state as a human-readable
configuration file rather than as ″snmp set″ commands.
v NBS 039442 — Provide integration with HP Insight Manager on Red Hat Linux
AS3.0.
v NBS 039679 — Enable the sqlsvr subagent to connect to a database that is
running on a non-default port.
v NBS 040417 — Provide Sybase 15 support to the sybase subagent.
v NBS 040649 — Complete implementation of OraEffPQTable.
v NBS 040935 — Provide support for Solaris on x86 hardware.
v NBS 041214 — Improve efficiency of the FileTransfer (IP Services module) thread
manager.
v NBS 042274 — Add support for Linux running on PowerPC (ppc64) platforms.
v NBS 042874 — Agent should be able to read and execute configuration files on
any platform regardless of the newline format (CRLF/LF).
v NBS 043052 — Add support for Red Hat Linux AS/ES 4.0 on AMD64/EM64T
platforms.
v NBS 044729 — Extend the ″user remote add″ command to allow the engineID to
be specified explicitly so that it does not need to perform discovery.
v NBS 044750 — Add support for loading Net/UCD-SNMP extension agents on
Linux platforms.
v NBS 044755 — Remove base2 library from agent as only srUserLoginTable uses
it.
v NBS 044909 — Remove legacy traptable.cfg support (left over from versions 2.1
and 3.0).
v NBS 044938 — Remove legacy console support (version 2.x RPC console) from
the Windows installer, as upgrades from version 2.x are no longer supported.
v NBS 045001 — The SNMPv3 engine boot count should be stored as an inivar
and not in a separate file.
v NBS 045002 — The console password should be stored as an encrypted inivar
and not in a separate file.
v NBS 045251 — Update the agent to use Installshield 12 on Windows platforms.
v NBS 045351 — Enhance the loServerTable so that it can be managed properly
using configuration files.
v NBS 045455 — Implement srDiskUtilization and srDiskAccessTime on AIX
platforms.
v NBS 045515 — Enhance the configuration library to support management of
string-controlled tables such as loServerTable.
v NBS 046289 — Add official support for x64 Windows platforms.
v NBS 046313 — Make auto-generated owner strings less cryptic and their origin
more obvious.
v NBS 046432 — The agent should disable any LD_PRELOAD environment
variables after startup.
v NBS 046531 — Add a filter type to the process MIB which allows direct
thresholding of the LastFilterCount as if it were an attribute.
v NBS 046534 — Add a command line parameter to disable the root-user check on
startup.
v NBS 046561 — Add official support for Windows 2003 R2.
v NBS 046627 — SNMP settings dialogs in the Windows installer should be
re-organized.
2 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
9. v NBS 046706 — Reimplement the existing monitors.cfg genalarm rules into
arithmetic rules.
v NBS 046963 — Enhance the monitoring solution for MS Exchange to handle
MSCS cluster installs.
v NBS 047153 — Remove the Omnibus-monitors prefix from binary names.
v NBS 047322 — Add Solaris 10 ″smf″ support for service administration to the
UNIX installer.
v NBS 047348 — Make index MIB objects that are not usually accessible readable
when queried internally using either the command console, genalarmvb or
arithmetic MIB.
v NBS 047411 — Remove subagent srnetusage, nuports.cfg, svc-*.cfg and
srnetusage* inivars from the SSM 4.0 installer.
v NBS 047423 — An adConnectControlrow with connectTo set to domainsInSite
cannot be activated.
v NBS 047468 — Add wts.cfg (Windows Terminal Services configuration) to the
Windows installer.
v NBS 047470 — Remove dependency on being root/admin user for running SSM.
v NBS 047471 — Allow the agent to start up with no SNMP ports bound.
v NBS 047472 — Allow multiple instances of the agent to be run at the same time.
v NBS 047525 — The desktop help tool (desktool.exe) should not start on Startup
or automatically when installed.
v NBS 047544 — Add support for multiline commands in the command console
and configuration files.
v NBS 047571 — Quoting is ignored/not yet implemented for old-style
configuration commands.
v NBS 047599 — Comments should be allowed on the end of configuration
commands, similar to UNIX shell scripting conventions.
v NBS 047645 — monitors.cfg to use the new multiline syntax for arithmetic
expressions to make them more readable.
v NBS 047665 — Improve flexibility of SSM lock file behavior.
v NBS 047774 — MIB Explorer should bind to address 0.0.0.0 when listening for
traps - not just on one specific IP address.
v NBS 047789 — Add a new flag (-l) to the console to enable selection of the
console-side listening port.
v NBS 047896 — Windows binaries should be signed before releasing formal
support for Windows Vista in SSM 4.0.
v NBS 047954 — Multiline matches in logmonx subagent are artificially limited to
4096 characters but the regex library can handle arbitrary lengths.
v NBS 047955 — Integrate the logmonx current file position into the MIB design
(logMonXStatsTable) to eliminate the need for file system access
(LogMonXStateFile). Making any modification to the state file should be possible
through MIB.
v NBS 047997 — Add a dropdown menu to the MIB Explorer to provide fast
access for jumping to particular MIB modules.
v NBS 047998 — Add architecture checking to the UNIX setup script.
v NBS 048011 — Installer can’t start second SSM on AIX or Solaris 10.
v NBS 048028 — Extend the SSM console protocol to distinguish between
commands that are complete and those that are incomplete due to unclosed
quotes. When a command is not complete, the console prompt should change to
indicate that.
Chapter 1. About this release 3
10. v NBS 049404 — Agent should run without init.cfg present.
v NBS CR2666 — MIB Explorer should be able to receive traps on ports other than
162.
v NBS CR7774 — Improve consistency of configuration command syntax help
displayed on the command console.
v NBS CR7850 — Upgrade to lastest version of libpcap (currently 0.9).
v NBS CR8599 — Add a new table to the agent MIB containing inivars so that
they can be viewed and set using SNMP.
Product fix history
This release contains fixes to limitations found in previous releases.
v NBS 030333 — genalarm row should not activate when startup=risingOrFalling
and alarmMode!=hysteresis.
v NBS 033753 — lotus data rows remain after the associated server row has been
removed.
v NBS 033754 — loSampleInterval allows very low sample intervals that cause
excessive CPU usage.
v NBS 034528 — SNMPv2-CONF MIB missing from product distribution.
v NBS 034537 — sqlsvr subagent dbstats table has replica data for separate SQL
databases.
v APAR IY90580 NBS 035024 — Agent does not correctly detect interface speed on
AIX.
v NBS 035564 — sybaseMDASysPlainText table entries should not contain trailing
’n’ characters.
v NBS 036863 — Ambiguous reason for ResultTableRowCount=0.
v NBS 036978 — Default sybase.cfg in version 3.2 produces error ’Unknown
command ″password″.’
v NBS 036980 — Include the new websphere6.cfg configuration file.
v NBS 038053 — Physical memory usage is incorrectly reported as 100% used on
Tru64 platforms.
v NBS 039325 — init.nco_m_ssmagent script fails to terminate native snmpd on
Solaris 10.
v NBS 040536 — MIB Explorer can’t display IMPLIED index strings such as those
in the SNMPv3 MIBs.
v APAR IY90640 NBS 041812 — weblogic subagent logs ″weblogic.kernel.Default″
messages when the servlet is down but the service is up.
v NBS 042909 — Default init.cfg in version 3.2 has RestoreState=off.
v NBS 042993 — Console commands for agentconfig can’t handle file names with
spaces.
v NBS 042998 — Incorrect spelling in Win32 installation: ″priveliges″
v NBS 043059 — Config files are not saved when upgrading the product from
version 3.1.
v NBS 043197 — Problem with InstallShield - install log error ″1: Failed to Invoke
__ISWIInit, error is 0x80004004.″
v NBS 043322 — On Windows platforms, the agent fails to report mounts on
directories those that do not have drive letters.
v NBS 043834 — ntperfmon cannot monitor objects that contain parentheses in
their name.
4 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
11. v NBS 043861 — csh leaves core files on Linux when executed from the
programmable subagent.
v NBS 043863 — On Solaris 7, the product’s installer causes errors by using an
invalid parameter to grep.
v NBS 043954 — On UNIX platforms, the installer ignores the INST_CFGPATH
flag.
v NBS 044251 — Typing errors in oracle-mib.mib.
v NBS 044263 — Swap usage on Solaris 8 does not include RAM based swap.
v NBS 044271 — Many MIB files are missing required IMPORTS from
SNMPv2-SMI and SNMPv2-TC.
v NBS 044396 — transaction subagent crashes when logging to file is enabled.
v NBS 044436 — Agent replies repeatedly to SNMP REPORTs with incorrect type
(a GET) when the security level is authNoPriv, causing it to spin.
v NBS 044912 — Changing the config directory on the command line with ″-f″
does not work on UNIX.
v NBS 045049 — In srIfTable, srIfIPAddr and srIfNetMask return the wrong type:
octetstring (0x04) when they should be IP address (0x80).
v NBS 045050 — The ″snmp match″ command fails on objects that are not
octetstrings.
v NBS 045053 — ntPerfMonControlCounters can be modified while a control row
is active. This should not be possible.
v NBS 045139 — Copyright message in nco_m_ssmagent startup script (and some
other scripts) is wrong.
v NBS 045140 — Windows interface blocking is not working as documented.
v NBS 045196 — LogMonStateFile is ignored if it contains NT event log indexes
that are out of the range of what actually exists within the event log.
v NBS 045283 — support@micromuse.com appears in README.TXT & .MIB on
files during and after installation.
v NBS 045304 — Weblogic servlet dumps exceptions to weblogic logfile.
v NBS 045440 — The INST_COEXIST option for Unix installation is ignored.
v NBS 045450 — ControlIndex is limited to 1..65535 in most MIBs when it should
not be. Only rmon1 has an explicit limitation of the control indexes in its MIB
module.
v NBS 045484 — On Windows, the installer reverts to default configuration when
a copy fails during an upgrade.
v NBS 045504 — lotus subagent log messages require improvement.
v NBS 045514 — On UNIX platforms, LogSize value is reset back to 1000000 after
upgrade.
v NBS 045581 — MIB2 shows the same MAC address for different network
interfaces on Solaris platforms.
v NBS 045663 — sap subagent crashes in the SAP libary (librfc) on some versions
of Linux.
v NBS 045689 — SSM installer and docs both refer to INST_ROOTPATH, which is
no longer used.
v NBS 045714 — Race condition in hipe::ThreadPool could lead to crashes on
extremely busy systems.
v NBS 045718 — websphere subagent’s ws_setup script incorrectly describes the
password field.
Chapter 1. About this release 5
12. v NBS 045754 — On Linux, filetransfer successfully transfers a file yet reports
failure.
v NBS 045776 — LogMonXState behavior is not consistent with sysres state file
behavior.
v NBS 045847 — agentConfig rows are removed prematurely when Control is set
to inactive.
v NBS 045848 — The datactrl configuration command fails to parse the ’delay’
keyword and does not create a control row if the ’delay’ keyword is present.
v NBS 045849 — ntscm.oid does not contain definitions for ntServiceTable.
v NBS 045850 — AgentConfigControl is missing from agentconfig.oid
v NBS 045880 — ntscm is missing console support for setting the
ntServiceControlRunControl object via the ″ntscm″ command.
v NBS 046052 — SNMP GET on logMonXStatsAbsPath does not work, even
though it is defined as a read-only object in the MIB.
v NBS 046055 — sap subagent does not load on AIX.
v NBS 046084 — Cannot connect local console to the agent on Windows x64
platforms.
v NBS 046093 — RMON event table does not update lastTimeSent object correctly.
v NBS 046113 — Terminating the agent after a warmboot does not correctly save
the agent state.
v NBS 046134 — Solaris loopback filesystem mounts (lofs) are incorrectly classed
as hrStorageType ″fixed disk″, which results in duplicate traps when monitoring
all fixed disks on a machine.
v NBS 046197 — The ″trapdest add″ command ignores the owner parameter if
executed from within a config script.
v NBS 046281 — Agentconfig leaves orphan control rows if scripts contain the
″config execute″ command rather than ″agentconfig create″.
v NBS 046315 — Creating contiguously indexed rows in agentConfigTable which
themselves create other agentConfig rows fails, due to poor automatic index
allocation.
v NBS 046343 — It is impossible to pass a community (CONF_DEFCOM) on the
command line of the Unix installer because it will be misinterpreted by the
setup script, no matter how well quoted it is.
v NBS 046344 — Executing invalid commands that contain an equals character
sometimes tricks the console into creating a variable incorrectly.
v NBS 046431 — The ″trapdest list″ command displays trapdests in seemingly
random order.
v NBS 046436 — MonitorRemoteFS inivar is ignored by hostres on Windows
platforms.
v NBS 046590 — Agent crashes when programmable vmConsole output is too
large.
v NBS 046728 — The documentation for the agent config table seems to be
incorrect.
v NBS 046748 — Memory leak in configurator when setting string objects.
v NBS 046754 — vacm remove view comand has inconsistent synatx help.
v NBS 046767 — The documentation for the agentconfigvar table in the reference
guide has a section on trap destination addressing in it.
v NBS 047188 — LogMonStateFile fails to save correctly if subagents are unloaded
before sysres.
6 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
13. v NBS 047189 — Fixed length string returned by the sqlsvr subagent when a
variable length is expected.
v NBS 047195 — Date format used by the sqlsvr subagent changed between build
700 and build 714.
v NBS 047196 — The database contact name is returned by the sqlsvr subagent.
v NBS 047285 — The servlet used by the websphere subagent doesn’t work on
WebSphere 6.x with global security enabled.
v NBS 047401 — All tables should implement Get for all objects, including
indexes.
v NBS 047421 — hrDiskStorageTable fails to show any volume groups other than
rootvg on AIX.
v NBS 047437 — adConnectControlTable row returns ″notInService″ when active
commit fails.
v NBS 047449 — psExceptionTable fails to filter out the ″wait″ process as
controlled by psIdleProcess=hidden on AIX.
v NBS 047452 — Virtual interfaces and zone interfaces are not detected by the
agent on Solaris platforms.
v NBS 047465 — Binding the address/port seems to have no effect on outgoing
SNMP responses on machines with multiple interfaces.
v NBS 047466 — hostres subagent may spin if retrieving network interface
information fails.
v NBS 047482 — On AIX platforms, agent configuration commands sometimes fail
to execute without reason and output the command syntax help instead.
v NBS 047499 — Non-printable characters inside string objects cause an
un-restorable hex string to be written to the agent state file.
v NBS 047523 — Agent sometimes gets stuck in a state where it believes that a
console is connected when it is not, and does not permit further console
connections.
v NBS 047526 — agent.state is written containing large blocks of empty lines,
making it quite unreadable.
v NBS 047530 — Cannot add vacm access entry with security model set to ″any″.
v NBS 047531 — Syntax help for ″vacm add entry″ command is incorrect. Says
″all″ rather than ″any″.
v NBS 047539 — process-mib.mib incorrectly states that PGID will be the value of
the PID on Windows platforms.
v NBS 047540 — vacm add group command allows security model any.
v NBS 047545 — genAlarmControlVariable has an invalid default value.
v NBS 047546 — genalarm control rows should not be able to activated if
genAlarmControlVariable is blank.
v NBS 047567 — Setting logMonXControlDisplayLimit to greater than 512 can
cause buffer overrun and crash.
v NBS 047570 — Memory leak of IMutex object in NetifOpen().
v NBS 047598 — agentIdPlatform reports ’other’ on Windows Vista (RC1).
v NBS 047662 — MIB Explorer reports an invalid OID in the traps tab when a
subagent sends a varbind whose OID lies underneath a known MIB but is not
defined in the MIB.
v NBS 047667 — Only allow a security model of ″usm″ in vacm security group.
v NBS 047676 — Get Bulk VACM returns authorizationError(16) when it doesn’t
make sense for it to do so.
Chapter 1. About this release 7
14. v NBS 047735 — MIB Explorer doesn’t display multiline strings such as complex
arithmetic expressions in tooltips correctly.
v NBS 047751 — MIB Explorer fails to format newlines (linefeed - 0xA) properly
when carriage return (0xD) is absent in DisplayString fields.
v NBS 047787 — A square (representing an unprintable character) appears in the
edit box for arControlExpression in MIB Explorer.
v NBS 047788 — The title of ControlIndex columns is not abbreviated as other
columns are, and should be.
v NBS 047809 — srUserLoginTable contains multiple entries for one (console) login
on Windows.
v NBS 047823 — On Windows Vista, the command console prompts for a
password when a password has not been set
v NBS 047824 — On Windows Vista, the service controller fails to start up,
reporting ’The handle is invalid.’
v NBS 047962 — MIB Explorer crashes when loading/reloading a MIB file.
v NBS 048004 — SNMPV3 auth/priv passwords are stored as plain text in
mibexplorer.cfg.
v NBS 048006 — Per servlet metrics not showing data in WebSphere 6.x.
v NBS 048008 — svrSecurityParamTable allows Parameters to have negative
values.
v NBS 048126 — Cannot connect console to agent restarted after a crash.
v NBS 048151 — On Solaris, all disks are reported as ″running″ even when a disk
is physically removed.
v NBS 048166 — Documentation for the Websphere ASM is slightly incorrect.
v NBS 048220 — Only the first Entry in LogMonXStateFile is recognized on UNIX
when agent is started.
v NBS 048263 — The ″$ccmStatus Enabled″ rule in the shipped ccm.cfg is
incorrect.
v NBS 048321 — SSM installation on UNIX creates files with invalid user-ids: such
as 202, 3332.
v NBS 048337 — sqlsvr tables have missing or incorrect values since the change to
ODBC API.
v NBS 048338 — MIB Explorer crashes if you switch tables too quickly.
v NBS 048339 — UNIX selfinstaller does not clean up tmp directories on failure.
v NBS 048359 — sqlsvr subagent returns a fixed length string when a variable
length is expected.
v APAR IY91779 NBS 048492 — Thresholds within genalarm seem to be
interpreted as 16-bit signed values in comparison.
v NBS 048641 — svrsecurity subagent logs errors when monitoring Windows
event logs that have been rotated.
v APAR IY93088 NBS 048673 — Error ″Can’t read from event log (87)″
v APAR IY93237 NBS 048758 — Memory usage calculation in hostres is incorrect
on HP-UX platforms.
v NBS 048772 — Inconsistent behavior: on HP-UX platforms, the installer shows
tar extraction progress, but not on other UNIX variants.
v NBS 048788 — Console command ″snmp set″ does not set $? with the return
status of the command.
v NBS 048825 — SSM hangs for long periods on a Linux machine with 250+
network interfaces.
8 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
15. v NBS 048831 — In the MIB Explorer, strings that contain ampersands display
incorrect tooltips.
v NBS 048845 — appflowConnHistAppName returning a ’n’ at the end of the
output value.
v NBS 048847 — hrPartitionTable and hrStorageTable don’t understand ZFS
filesystems on Solaris 10.
v NBS 048870 — Mib Explorer crashes when copying OID within the WALK view.
v NBS 048938 — Installer reports symlink errors when upgrading existing agent.
v NBS 048940 — MIB Explorer crashes when starting a walk in arEvalTable from
the righthand pane on Windows Vista.
v NBS 048942 — Console help system has an unused (empty) context named
″subagent″
v NBS 048943 — Installer returns exit code 2 when reporting successful install,
should be 0.
v NBS 048970 — MIB Explorer crash when changing the arEvalTableInstance
Column to ObjectID Named.
v NBS 048972 — silent option during installation is not permitted for non root
users.
v NBS 048986 — Typing error in default agent.cfg prevents mscs.cfg from ever
loading.
v NBS 048995 — Interface bind command needs to be executed twice before it
works.
v NBS 048996 — Interface unbind command just returns an error and fails to
unbind.
v NBS 049013 — Unable to start Service Controller due to Windows manifest
issues.
v NBS 049035 — When sending SNMP V3 Informs with authPriv the agent never
timesyncs with the trap receiver.
v APAR IY93327 NBS 049055 — Version 3.2 (fixpack 727) is sending spurious traps
on Solaris, reporting ″Network mount ... not responding″ for network mounts
which are actually responding.
v NBS 049116 — Running the agent on some network mounts causes incorrect file
permissions to be applied to init.cfg so that the agent cannot be subsequently
re-run.
v APAR IY93511 NBS 049125 — The LogMonStateFile and agent.state can contain
stale position pointers, which can cause unnecessary log re-reads after an agent
restart.
v NBS 049135 — hrStorageTable shows incorrect size/used values for some
network mounts on Windows.
v NBS 049137 — srLogmon outputs incorrect file position values to the
LogMonStateFile on some UNIX platforms.
v NBS 049181 — Agents cores when doing a coldboot if there is an active
loControlTable row.
v NBS 049183 — wsCollectionTable and wsCounterTable are missing some
collection/counter entries that exist on the WebSphere server.
v NBS 049186 — wsCollectionTable and wsDataTable contain rows even when the
websphere subagent is pointing at a host address or port with no WebSphere
server installed.
v NBS 049313 — LogMonX uses excessive CPU when the agent has been up for 8+
months.
Chapter 1. About this release 9
16. v APAR IY94877 NBS 049333 — Under some circumstances the agent will send a
retry for an SNMP-Inform for which an ack has already been received.
v APAR IY95094 NBS 049424 — HrDeviceDescr reports ″Unknown CPU″ on some
POWER5 machines.
v NBS 049437 — websphere CounterTable does not seem to be populated for
WebSphere 6.0+.
v APAR IY95167 NBS 049478 — Mirrored disks on Solaris report hrStorageType as
other(1) instead of fixed(4).
v NBS 049554 — Setting an IP Address object via ″snmp set″ causes a crash in
master agent.
v APAR IY95394 NBS 049560 — In version 3.2 on Windows platforms, time
counters drift gradually (slow down) or stand still when under load.
v NBS 049721 — In the sapControlTable, LastErrorMessage remains even after an
event has succeeded.
v APAR IY95755 NBS 049731 — oracle subagent does not support column changes
for Oracle 9IR2.
v NBS 049818 — Hostres prevents some thumbdrive software from letting you
″eject″ the thumbdrive.
v NBS 049834 — Loading MIB Explorer ignores folders in the host tree when an
empty folder is present.
v NBS 050012 — arithmetic exists() function produces incorrect results.
v NBS 050019 — Scalar arithmetic removed() function returns incorrect results.
v NBS CR3643 — If an interface is disabled/re-enabled on Windows, it is
impossible to retrieve statistics in MIB-2.
v NBS CR7595 — Windows installer honors .iss options in a silent install over
command line options.
v NBS CR8006 — MIB Explorer crashes when creating a chart.
v NBS CR8159 — On UNIX platforms, the installer does not check to see if there is
sufficient space for an install before proceeding.
v NBS CR8189 — SSM seems to be returning different values for Insight Manager
compared to MS SNMP.
v NBS CR8190 — When monitoring CIM agents, some OID values are missing.
v NBS CR8373 — NT event monitor opens Application log if the specified event
log does not exist.
v NBS CR8711 — On Windows platforms, the cursor in the command console
becomes invisible when moving left or right.
v NBS CR8892 — srDisk stats are not reported correctly on Windows 2000/XP if
dynamic disks are enabled.
v NBS CR9120 — srIPDefaultGateway value occassionly changes on HP-UX and
Tru64 even though no changes were made on the box.
v NBS CR9253 — Advancing the clock to 2099 causes the agent crash on startup
(under Windows only).
v NBS CR9318 — Non-thread-safe strtok function is used in a few subagents could
potentially cause a crash.
Product compatibility notes
This information details the compatibility of Netcool/SSM with other applications
and relevant standards.
10 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
17. Netcool/ASM application support
IBM has verified the operation of each monitor in the Netcool/ASM suite on
specific combinations of application and platform versions.
For information about combinations not listed here, contact IBM Support.
Netcool/ASM for Active Directory
Table 1 lists the combinations of application version and platform on which
Netcool/ASM for has been verified by IBM.
Table 1. Netcool/ASM for Active Directory verified platforms and versions
Platform Active Directory
Windows 2000 Server SP4 32-bit X
Windows 2003 Server SP1 32-bit X
Windows 2003 Server SP1 64-bit X
Netcool/ASM for Apache
Table 2 lists the combinations of application version and platform on which
Netcool/ASM for Apache has been verified by IBM.
Table 2. Netcool/ASM for Apache verified platforms and versions
Apache version
Platform 1.3 2.0.50+ 2.2.x
Windows 2000 Server SP4 32-bit X
Windows 2003 Server SP1 32-bit X
Windows 2003 Server SP1 64-bit X
Solaris 10 SPARC X X
Solaris 10 x64 X X
RHEL 4.0 ES Update 4 x86 X
RHEL 4.0 AS Update 4 x86 X
RHEL 4.0 ES Update 4 AMD64/Intel EM64T X
RHEL 4.0 AS Update 4 AMD64/Intel EM64T X
RHEL 4.0 AS ppc64 X
SLES 9.0 x86 X
SLES 9.0 ppc64 X
SLES 9.1 x86 X
SLES 9.2 x86 X
SLES 9.3 x86 X
SLES 10.0 x86 X
AIX 5.2 POWER 4/5 64-bit X
AIX 5.3 POWER 4/5 64-bit X
HP-UX 11.2 PA-RISC X
Chapter 1. About this release 11
18. Netcool/ASM for Microsoft Exchange
Table 3 lists the combinations of application version and platform on which
Netcool/ASM for Microsoft Exchange has been verified by IBM.
Table 3. Netcool/ASM for Microsoft Exchange verified platforms and versions
Microsoft Exchange version
Platform 2000 2003
Windows 2000 Server SP4 32-bit X X
Windows 2003 Server SP1 32-bit X
Netcool/ASM for Microsoft IIS
Table 4 lists the combinations of application version and platform on which
Netcool/ASM for Microsoft IIS has been verified by IBM.
Table 4. Netcool/ASM for Microsoft IIS verified platforms and versions
Microsoft IIS version
Platform Windows 2000 Windows 2003
Windows 2000 Server SP4 32-bit X
Windows 2003 Server SP1 32-bit X
Windows 2003 Server SP1 64-bit X
Netcool/ASM for Lotus Notes
Table 5 lists the combinations of application version and platform on which
Netcool/ASM for Lotus Notes has been verified by IBM.
Table 5. Netcool/ASM for Lotus Notes verified platforms and versions
Lotus Notes version
Platform 6.5.2 7.0.1
Windows 2000 Server SP4 32-bit X X
Windows 2003 Server SP1 32-bit X X
Solaris 8 SPARC X
Solaris 9 SPARC X X
Solaris 10 SPARC X X
AIX 5.2 POWER 4/5 64-bit X
AIX 5.3 POWER 4/5 64-bit X
Netcool/ASM for Microsoft SQL Server
Table 6 lists the combinations of application version and platform on which
Netcool/ASM for Microsoft SQL Server has been verified by IBM.
Table 6. Netcool/ASM for Microsoft SQL Server verified platforms and versions
Platform Microsoft SQL Server 2000
Windows 2000 Server SP4 32-bit X
12 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
19. Netcool/ASM for Oracle
Table 7 lists the combinations of application version and platform on which
Netcool/ASM for Oracle has been verified by IBM.
Table 7. Netcool/ASM for Oracle verified platforms and versions
Oracle version
Platform 9.2.0.1 (9i) 9i RAC 10g 10g RAC
Windows 2000 Server SP4 32-bit X
Windows 2003 Server SP1 32-bit X X X
Solaris 8 SPARC X X
Solaris 9 SPARC X X
RHEL 3.0 ES Update 8 x86 X X
RHEL AS 3.0 Update 8 x86 X X
RHEL 3.0 ES Update 8 AMD64/Intel EM64T X
RHEL 3.0 AS Update 8 AMD64/Intel EM64T X X
RHEL 4.0 ES Update 4 x86 X X
RHEL 4.0 AS Update 4 x86 X X
RHEL 4.0 ES Update 4 AMD64/Intel EM64T X X
RHEL 4.0 AS Update 4 AMD64/Intel EM64T X X
RHEL 4.0 AS ppc64 X X
SLES 9.0 x86 X X
SLES 9.0 ppc64 X X
SLES 9.1 x86 X X
SLES 9.2 x86 X X
SLES 9.3 x86 X X
AIX 5.2 POWER 4/5 64-bit X X
AIX 5.3 POWER 4/5 64-bit X X
HP-UX 11.2 PA-RISC X X X X
Netcool/ASM for SAP R/3
Table 8 lists the combinations of application version and platform on which
Netcool/ASM for SAP R/3 has been verified by IBM.
Table 8. Netcool/ASM for SAP R/3 verified platforms and versions
SAP R/3 version
Platform R/3 4.0B R/3 Enterprise 4.7
Windows 2000 Server SP4 32-bit X
Windows 2003 Server SP1 32-bit X X
Windows 2003 Server SP1 64-bit X X
Solaris 8 SPARC X X
Solaris 9 SPARC X X
Solaris 10 SPARC X
Solaris 10 x64 X
Chapter 1. About this release 13
20. Table 8. Netcool/ASM for SAP R/3 verified platforms and versions (continued)
SAP R/3 version
Platform R/3 4.0B R/3 Enterprise 4.7
RHEL 3.0 ES Update 8 x86 X
RHEL 3.0 AS Update 8 x86 X
RHEL 3.0 ES Update 8 AMD64/Intel EM64T X
RHEL 3.0 AS Update 8 AMD64/Intel EM64T X
RHEL 4.0 ES Update 4 x86 X
RHEL 4.0 AS Update 4 x86 X
RHEL 4.0 ES Update 4 AMD64/Intel EM64T X
RHEL 4.0 AS Update 4 AMD64/Intel EM64T X
RHEL 4.0 AS ppc64 X
SLES 9.0 x86 X
SLES 9.0 ppc64 X
SLES 9.3 x86 X
SLES 10.0 x86 X
AIX 5.3 POWER 4/5 64-bit X
HP-UX 11i (11.11) PA-RISC X
HP-UX 11.2 PA-RISC X
Tru64 5.1b X X
Netcool/ASM for Sybase ASE
Table 9 lists the combinations of application version and platform on which
Netcool/ASM for Sybase ASE has been verified by IBM.
Table 9. Netcool/ASM for Sybase ASE verified platforms and versions
Sybase ASE version
Platform 12.5.2 12.5.4 15.0.1
Windows 2000 Server SP4 32-bit X X
Windows 2003 Server SP1 32-bit X X
Solaris 8 SPARC X X
Solaris 9 SPARC X X
Solaris 10 SPARC X X
RHEL 3.0 ES Update 8 x86 X X
RHEL 4.0 ES Update 4 x86 X X
RHEL 4.0 AS Update 4 x86 X X
SLES 9.2 x86 X
SLES 9.3 x86 X
AIX 5.3 POWER 4/5 64-bit X
HP-UX 11i (11.11) PA-RISC X
HP-UX 11.2 PA-RISC X
14 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
21. Netcool/ASM for WebLogic
Table 10 lists the combinations of application version and platform on which
Netcool/ASM for WebLogic has been verified by IBM.
Table 10. Netcool/ASM for WebLogic verified platforms and versions
WebLogic version
Platform 8.1 9.1
Windows 2000 Server SP4 32-bit X X
Windows 2003 Server SP1 32-bit X X
Windows 2003 Server SP1 64-bit X
Solaris 8 SPARC X
Solaris 9 SPARC X X
Solaris 10 SPARC X X
RHEL 4.0 ES Update 4 x86 X X
RHEL 4.0 AS Update 4 x86 X
RHEL 4.0 ES Update 4 AMD 64/Intel EM64T X
RHEL 4.0 AS Update 4 AMD 64/Intel EM64T X
RHEL 4.0 AS ppc64 X X
SLES 9.0 ppc64 X X
SLES 9.1 x86 X
SLES 9.2 x86 X
SLES 9.3 x86 X X
SLES 10.0 x86 X X
HP-UX 11.2 PA-RISC X X
Netcool/ASM for WebSphere
Table 11 lists the combinations of application version and platform on which
Netcool/ASM for WebSphere has been verified by IBM.
Table 11. Netcool/ASM for WebSphere verified platforms and versions
WebSphere version
Platform 5.0.2 5.1 6.0 6.1
Windows 2000 Server SP4 32-bit X
Windows 2003 Server SP1 32-bit X X
Windows 2003 Server SP1 64-bit X X
Solaris 8 SPARC X
Solaris 9 SPARC X
Solaris 10 SPARC X X
RHEL 3.0 ES Update 8 x86 X X
RHEL 3.0 AS Update 8 x86 X X
RHEL 4.0 ES Update 4 x86 X X
RHEL 4.0 AS Update 4 x86 X X
RHEL 4.0 AS ppc64 X X
Chapter 1. About this release 15
22. Table 11. Netcool/ASM for WebSphere verified platforms and versions (continued)
WebSphere version
Platform 5.0.2 5.1 6.0 6.1
SLES 9.0 ppc64 X
SLES 9.1 x86 X X
SLES 9.2 x86 X X
SLES 9.3 x86 X X
SLES 10.0 x86 X X
AIX5.2 POWER 4/5 64 bit X
AIX5.3 POWER 4/5 64 bit X X X
SNMPv1 compatibility
Some Netcool/SSM MIB modules use the Counter64 data type, so they are not
compatible with SNMPv1. You should only use them with SNMPv2 and later.
This limitation applies to the following subagents:
v appflow
v genalarm
v ntperfmon
v sla
v transaction
v Netcool/ASM for Active Directory
v Netcool/ASM for WebLogic
16 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
24. Software
Netcool/SSM is available for the following versions of HP-UX:
v HP-UX 11.11 (11i) on PA-RISC
v HP-UX 11.2 on PA-RISC or Intel Itanium
Latest Library Patches
Patches to the HP-UX Operating Environment libraries are available. HP-UX 11.11
(11i) requires the libc cumulative patch version PHCO_29495 or later.
The host machine may be running patches that have been recalled. The
Netcool/SSM installer checks to see what operating system patches have been
installed on the machine. If it detects a problem it provides a warning similar to
the following:
# ./netcool-ssm-4.0-xxxx-platform-arch.installer
Netcool/SSM Installer
Patch PHCO_23919 (patch for printf) detected.
*** WARNING: THIS PATCH MAY CAUSE SETUP TO CRASH ***
Consult your Netcool/SSM documentation for details.
Do you want to continue? [n]
Note: Visit the Hewlett-Packard (HP) IT Resource Center online at
http://www.itrc.hp.com for information on updating or removing this patch. The
Netcool/SSM installer will not do this for you.
AIX
The following system requirements apply to AIX host machines.
Hardware
The minimum hardware requirements for running Netcool/SSM on AIX platforms
are:
v IBM POWER4/5 64-bit processor
v 64 MB RAM or greater recommended
v Approximately 35 MB free disk space
v 50 MB minimum swap space recommended
v Ethernet 10/100 network interface card capable of supporting promiscuous
packet reception
Software
Netcool/SSM is available on the following versions of AIX:
v AIX 5.2 (64-bit only)
v AIX 5.3 (64-bit only)
Red Hat Linux
The following system requirements apply to Red Hat Linux host machines.
18 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
25. Hardware
The minimum hardware requirements for running Netcool/SSM on Red Hat Linux
platforms are:
v Intel Pentium II processor 400 MHz or greater
v 128 MB RAM or greater recommended
v Approximately 30 MB free disk space
v 50 MB minimum swap space recommended
v Ethernet 10/100 or Token Ring network interface card capable of supporting
promiscuous packet reception
Software
Netcool/SSM is available for the following versions of Red Hat Linux:
v Red Hat Enterprise Linux AS 2.1 - x86
v Red Hat Enterprise Linux AS/ES 3.0 - x86, AMD64/IntelEM64T
v Red Hat Enterprise Linux AS/ES 3.0 Update 8 - x86, AMD64/Intel EM64T
v Red Hat Enterprise Linux AS/ES 4.0 - x86, AMD64/IntelEM64T
v Red Hat Enterprise Linux AS/ES 4.0 Update 4 - x86, AMD64/Intel EM64T
v Red Hat Enterprise Linux AS 4.0 - ppc64
v Red Hat Enterprise Linux 5 - x86, x64
SuSE Linux Enterprise Server
The following system requirements apply to SuSE Linux Enterprise Server (SLES)
host machines.
Hardware
The minimum hardware requirements for running Netcool/SSM on SLES
platforms are:
v Intel Pentium II processor 400 MHz or greater
v 128 MB RAM or greater recommended
v Approximately 30 MB free disk space
v 50 MB minimum swap space recommended
v Ethernet 10/100 or Token Ring network interface card capable of supporting
promiscuous packet reception
Software
Netcool/SSM is available for the following versions of SLES:
v 9 - x86, ppc64
v 9SP1, 9SP2, 9SP3 - x86
v 10 - x86, AMD64/Intel EM64T
Solaris
The following system requirements apply to Solaris host machines.
Chapter 2. Hardware and software requirements 19
26. Hardware
The minimum hardware requirements for running Netcool/SSM on Solaris
platforms are:
v UltraSPARC IIi 400 MHz processor or AMD/Intel x64 processor
v 128 MB RAM or greater recommended
v Approximately 25 MB free disk space
v 50 MB minimum swap space recommended
v Ethernet 10/100 network interface card capable of supporting promiscuous
packet reception
Software
Netcool/SSM is available on the following versions of Solaris:
v Solaris 8 (SunOS 5.8) SPARC
v Solaris 9 (SunOS 5.9) SPARC
v Solaris 10 (SunOS 5.10) SPARC or x64
Latest library patches
Patches to the Solaris Operating Environment libraries are available. Ensure that
the latest patch for the Solaris Operating Environment is installed and running on
the host machine before you install Netcool/SSM.
Table 12 lists the current patch IDs available at the time of writing. Before installing
a patch, check that it is the latest version as patches are cumulative and always
backward compatible.
Table 12. Patch IDs for Solaris Operating System Versions
Solaris Patch ID
8 (32-bit) 108434
8 (64-bit) 108435
9 (32-bit) 111711
9 (64-bit) 111712
10 119963
For further information about patches to the Solaris Operating Environment, see
http://developers.sun.com/sunstudio/downloads/patches/ss11_patches.html.
Tru64
The following system requirements apply to Tru64 host machines.
Hardware
The minimum hardware requirements for running Netcool/SSM on Tru64
platforms are:
v AXP Processor (500MHz or greater)
v 128MB RAM or greater
v 35MB free disk space
20 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
27. v 50MB minimum swap space
Software
Netcool/SSM is available for the following versions of Tru64:
v Tru64 5.1a, 5.1b
If there is no compiler/development environment on the host machine, then apply
the Compaq supplied redistribution kit, CXXREDIST650.
To verify that this kit has been applied, enter the following command:
setld -v CXXREDIST650
The machine should respond with:
Compaq C++ Run-Time Library Redistribution kit (CXXREDIST650)
If it does not respond in this way, apply the kit using the following commands:
root
cd /tmp
tar -xvf CXXREDIST650.tar
setld -l /tmp/CXXREDIST650.kit
To obtain this kit, visit the Compaq C++ site online at ftp://ftp.compaq.com/pub/
products/C-CXX/Tru64/cxx/cxxredist.htm.
Chapter 2. Hardware and software requirements 21
28. 22 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
30. Netcool/ASM for WebLogic
This release includes an updated version of the WebLogic performance monitoring
servlet, PerfMonitor.ear. When upgrading an existing Netcool/SSM installation that
uses Netcool/ASM for WebLogic to monitor WebLogic servers, you must redeploy
PerfMonitor.ear on each monitored server.
Using the WebLogic Administration Console, undeploy PerfMonitor on each
WebLogic server, then run the wl_setup script (located in the Netcool/SSM bin
directory) to redeploy PerfMonitor on those servers.
Netcool/ASM for WebSphere
This release includes an updated version of the WebSphere performance
monitoring servlet, PerfServlet.ear. When upgrading an existing Netcool/SSM
installation that uses Netcool/ASM for WebSphere to monitor WebSphere servers,
you must redeploy PerfServlet.ear on each monitored server.
Use the WebSphere administrative console to uninstall PerfServlet from each
server, then run the ws_setup script (located in the Netcool/SSM bin directory) to
redeploy PerfServlet on those servers.
programmable subagent
CR9048: The agent hangs when aborting a programmable control row that is
configured to execute a program which has created child processes (Windows
only).
svrsecurity subagent
There are several issues concerning the operation of the Server Security
(svrsecurity) subagent.
Login files
To monitor logins using svrsecurity, the following files must exist or be
symbolically linked to the real files for the subagent to work correctly:
v Linux: /var/log/lastlog
v Solaris: /var/adm/loginlog
v HPUX: /var/adm/acct/sum/loginlog
Login failure threshold on Solaris platforms
On Solaris platforms, the operation of the svrsecurity login failure detection is
different to that on other platforms. Normally the subagent generates a trap when
three failed logins are detected. However, on Solaris platforms the number of failed
logins that must be observed before a trap is generated depends on the value of
the retries parameter defined in the file /etc/default/login. If the value of this
parameter is greater than 3, a trap is not generated until this value is exceeded
(this occurs because the operating system does not write the number of login
failures to the disk until a breach has occurred). If the value of this parameter is 3
or lower, then the subagent behaves as it does on other platforms.
24 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
31. FIN, NULL, and Xmas port scans on Solaris 9 and 10
The Server Security subagent does not detect FIN, NULL, and Xmas port scans on
Solaris 9 and 10 because these operating systems provide automatic protection
against such attacks.
Installing Netcool/SSM
If the installation option string passed to the installer using the /z switch contains
an equal character (=), it must also contain a space character at some point,
otherwise the parameter string is not passed to install script correctly. This is a
known issue in InstallShield version 8.
Operating system limitations
Operating system limitations relate to the interaction between Netcool/SSM and
the operating system that is running on the machine on which Netcool/SSM is
installed.
UNIX
These limitations apply to Netcool/SSM on all UNIX platforms.
UNIX system date/time
On UNIX platforms, changing the system date/time can cause unexpected
behavior in the agent. This is because many events within the agent are scheduled
to perform actions at certain times. Changing the date/time effectively corrupts the
application runtime environment. Symptoms include hanging or spinning the
agent, data not being periodically updated. Agents running on Solaris platforms
are particularly sensitive to system date/time changes.
Note: This does not include changes made by NTP because these date/time
changes are gradual.
Linux
These limitations apply to Netcool/SSM on Linux platforms.
This section describes the known issues on Linux operating systems.
Core files
On Linux distributions that do not use the Native POSIX Threads Library (NPTL),
core files often do not contain any useful information about the application thread
that has crashed. If Netcool/SSM crashes, inspect the host system’s process status
list. The offending thread may still be resident in memory. In this case, rename the
existing core file and enter the command kill -ABRT <pid>. This produces a core
file for the offending thread, providing information useful for debugging.
On Red Hat Enterprise Linux 2.1, more informative core files are generated if you
change the following kernel variable using the command:
echo 1 > /proc/sys/kernel/core_uses_pid
This causes all processes to write core files with filenames core.pid, ensuring that
one thread does not accidentally overwrite the core file of another process.
Applying this change immediately and insert it into the file /etc/rc.d/rc.local.
Chapter 3. Known problems, limitations, and workarounds 25
32. Bonding driver virtual interface
The agent cannot detect the virtual interface formed by the bonding driver (for
example, bond0). The agent only reports interfaces with an assigned IP address.
Assign the interface a dummy IP address (for example, ifconfig bond0 1.1.1.1).
Ensure that the IP address you assign does not interfere with the routing table.
AIX
These limitations apply to Netcool/SSM on AIX platforms.
Low-level packet capture
It is not possible for the low-level packet capture code to capture the outbound
packets. There is no workaround to this issue at present. This affects all monitoring
activities running on AIX that are configured to monitor that same host’s outbound
network activity.
Terminate configuration command
The terminate configuration command terminates the agent; however, when you
issue this command, the AIX service controller is not informed that the agent has
terminated. Similarly, if you terminate the agent using the AIX command kill -9
on the agent process, the AIX service controller is not informed of this. In both
cases, the AIX service controller is not aware that the service has terminated;
however any attempt to stop it using the AIX command stopsrc -
s <service name> will fail.
If this situation arises, restart the host. To prevent this situation occurring, always
invoke the service controller when terminating the agent by using either of the
following commands:
stopsrc -c -s service name (kill -2 plus kill -9 on the named service)
stopsrc -f -s service name (kill -9 on the named service)
Core files
If the agent attempts to dump core and there is not enough disk space in the
partition in which the core file is being created then it will probably be lost or
useless for debug purposes. To prevent this, ensure that there is sufficient disk
space in the partition to hold a core file.
Windows
These limitations apply to Netcool/SSM on Windows platforms.
Registering the Netcool/SSM service on Windows
Under Windows 2000/XP/2003, registering service mode users that already exist
may cause inconsistencies to appear with the Service Controller, and manual
intervention may be required. This seems to be especially true for Domain users. It
is recommended that you use the default service user (that is, Local System).
26 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
33. Windows fault reports
Windows XP platforms provide a feature Report Faults to Microsoft, which is
enabled by default. If the agent crashes and the operating system creates a Dr
Watson dump, the dump file is often corrupted or truncated when Report Faults to
Microsoft is enabled.
To disable Report Faults to Microsoft:
1. In the Start menu select Settings → Control Panel → System.
2. Select the Advanced tab.
3. Click Error Reporting.
4. Select the Disable Error Reporting option.
Interaction with other applications
These limitations relate to the interaction between Netcool/SSM and other
applications that are running on the machine on which Netcool/SSM is installed.
Microsoft SNMP Service
Under Windows 2000/XP/2003, the Microsoft SNMP service which uses UDP port
161 will prevent the agent from running if it is active. You can instruct the
installation program to disable this service if it is detected at installation time.
Kaspersky® Anti-Virus software
On Windows platforms that are running Kaspersky Anti-Virus software there have
been issues when uninstalling the agent. This seems to happen because as
InstallShield performs the uninstallation operation it touches the executable images
installed, which in turn alerts the anti-virus software, which in turn is detected by
InstallShield. The latter complains that the image being uninstalled is in use but
allows the end user to complete the uninstall successfully. The message is benign
and can be ignored.
Microsoft® Exchange™
When you use the Netcool/ASM for Microsoft Exchange on Windows 2000/XP
platforms to monitor a Microsoft Exchange 5.5 SP3 server, the MTA may log an
event 1016 when it is writing an extensible counter to the Windows 2000 Server
Performance Monitor log. This in turn can fill the NT Event Log causing issues for
the serving host.
The cause of this behavior is not the Netcool/ASM for Microsoft Exchange. The
root cause is addressed by applying Microsoft Exchange Service Pack 4. This issue
is described further in the Microsoft knowledge base article 263112.
Veritas® NetBackup™
Some versions of Veritas NetBackup may hang if the agent is running when a
backup is performed. The agent creates a lock file under /var/spool/locks
containing the PID of the agent; this is normal behavior. It sets the permissions of
this file to enforce mandatory locking. Any attempt to open the file will hang until
the lock is released. To avoid this problem, configure Veritas NetBackup to exclude
this directory from the backup cycle.
Chapter 3. Known problems, limitations, and workarounds 27
34. Windows diskperf utility
On Windows 2000/XP/2003 platforms, the diskperf utility is configured by default
to never start. Post installation, it will be configured to start at boot. Although
Netcool/SSM does not require the host to be rebooted after installation, some disk
metrics, such as disk IO since the last host boot, will not have accurate data. This
can only be addressed by rebooting the host machine.
Configuration issues
These limitations relate to the configuration of Netcool/SSM and its components.
System resource usage
It is possible to configure the agent and its subagents in such a way that its
resource usage severely reduces the performance of the host system. For example,
monitoring system activity at too high a rate, or specifying resources to be
monitored at too coarse a level of granularity can consume excessive amounts of
system resources. Try to strike a balance between the number of objects monitored,
the polling interval, and the resource usage on the host on which the agent is
running.
28 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes
36. trying to collect metrics on transactions that will never end. The
transactionControlRequestTimeout object controls that timeout period.
What is the sap.csv file in the config directory for?
The transaction subagent uses this file to map SAP transaction codes to
descriptions of those transactions. If a deployment is intended to monitor more
SAP transactions than are included in this .csv file, you can extend the file with the
appropriate types and descriptions.
Why does my Windows server seem to have several sessions open from
machines running the agent?
This occurs because the hostres subagent is attempting to query network drive
information. You can reduce the number of sessions created on the server by doing
any of the following:
v On the server, reduce the auto-disconnect timeout with the command:
net config server /autodisconnect:<minutes>
v Change the service user account under which the agent executes to be a domain
member.
v Run the agent in application mode.
Why can’t I see any information about network drives in hostres?
This occurs because the agent is running as a service user which does not have
domain privileges and hence can’t query the network drive. To correct this, run the
agent service as a user who is a domain member, or run the agent in application
mode.
Why does transaction subagent stop monitoring some transaction types?
When a control row is created to monitor particular transaction types, the subagent
can fail to capture and display the expected transaction type. The principal reason
for this is that the value of the control row’s transactionControlRequestTimeout
object is too small for the transaction type being monitored or the way the
transaction is configured to operate on the host under test.
For example, if a default transaction row is created to monitor POP & SMTP traffic
between two hosts and there is no such traffic before the request timeout expires
then the connection will timeout. When this occurs, an entry with the following
format is created in the agent.log file (if the agent is configured to operate at log
level 3 or higher):
<DateTime Stamp>: Timed out connection: <Connection endpoints>;
<Application Type> will be created in the agent.log file if it is configured
to operate at log level 3 or higher.
Why does the loopback interface in the MIB-2 interfaces ifTable have a speed of
0?
The agent uses low level system functions to determine the speed of the loopback
interface. The values returned on the different platforms and the semantics
associated with those values vary from platform to platform. By convention, if the
ifSpeed object has the value 0, this indicates ″as fast as possible″ for the platform
being monitored.
30 IBM Tivoli Netcool/System Service Monitors Version 4.0: Release Notes