Installing WebSphere Studio Application Monitor V3.1
This IBM Redbooks publication is for installers of IBM WebSphere Studio Application Monitor for Multiplatforms, including performance analysts, WebSphere administrators, and technical managers. Our goal is to provide a useful overview about installing WebSphere Studio Application Monitor and, more i...
| Autores principales: | , , |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Research Triangle Park, N.C. :
IBM, International Technical Support Organization
2005.
|
| Edición: | 1st ed |
| Colección: | IBM redbooks.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009626914406719 |
Tabla de Contenidos:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Executive summary
- Chapter 1. Executive summary
- Part 2 WebSphere Studio Application Monitor description
- Chapter 2. What is WebSphere Studio Application Monitor?
- 2.1 What is new in WebSphere Studio Application Monitor V3.1
- 2.2 Composite request monitoring
- 2.3 Architecture and design
- 2.3.1 The Managing Server
- 2.3.2 The Data Collectors
- 2.4 The three monitoring levels
- 2.5 Monitoring methodologies
- 2.5.1 In-flight request monitoring
- 2.5.2 Historical workload reporting
- 2.6 Composite request monitoring
- 2.6.1 Composite monitoring scope
- 2.6.2 Enterprise application integration
- 2.6.3 CICS and IMS transactions in composite requests
- 2.6.4 Multiple hops
- 2.7 The installation process summary
- 2.7.1 Install and start the Managing Server
- 2.7.2 Install and start the Data Collectors
- 2.7.3 Start the monitored servers
- 2.7.4 Configure the Data Collectors
- 2.7.5 Verify the installation
- 2.7.6 Activate composite request monitoring
- 2.7.7 Post-installation
- Chapter 3. Preinstallation planning
- 3.1 Hardware and software prerequisites
- 3.1.1 Managing Server hardware
- 3.1.2 Managing Server software
- 3.1.3 Data Collector hardware
- 3.1.4 Data Collector software
- 3.2 Managing Server configuration options
- 3.2.1 How many?
- 3.2.2 Managing Server topologies
- 3.3 Data Collector considerations
- 3.4 Network and protocol considerations
- 3.5 Firewalls
- 3.6 Repository database sizing
- 3.7 DB2 drivers
- 3.8 Established systems for composite request monitoring
- 3.8.1 CICS
- 3.8.2 IMS
- 3.9 Middleware for composite request monitoring
- 3.9.1 CICS Transaction Gateway
- 3.9.2 IMS Connect
- 3.9.3 WebSphere MQ.
- 3.10 Composite request monitoring requirements tables
- Chapter 4. WebSphere Studio Application Monitor installation rollout planning
- 4.1 Strategic or tactical
- 4.2 Planning the rollout
- 4.2.1 Identify an enterprise business sponsor and the stakeholders
- 4.2.2 Define ownership
- 4.2.3 Choose the project manager
- 4.2.4 Educate the user community and gain stakeholder support
- 4.2.5 Identify and document business needs for monitoring
- 4.2.6 Identify applications and JVMs to monitor
- 4.2.7 Define appropriate levels of access to the user groups
- 4.2.8 Define appropriate views to the user groups
- 4.2.9 Plan time frame to implement
- 4.3 Rollout
- 4.4 Establish a training plan
- 4.5 Identify reporting requirements
- 4.6 Identify implementation team
- 4.7 Identify initial deployment benefits
- 4.8 Installation
- 4.8.1 Before you start
- 4.8.2 Plan the installation
- 4.8.3 Install Application Monitor
- 4.8.4 Major tasks performed by the installer
- 4.8.5 Installation scripts
- 4.8.6 Common mistakes
- 4.8.7 Resolving installation issues
- 4.8.8 Installation log files
- 4.9 Platform-specific issues
- 4.9.1 Customized startup and shutdown instructions
- 4.9.2 Common error messages and solutions
- 4.10 Maintenance
- 4.10.1 Assign responsibilities
- 4.10.2 Training
- 4.11 Database maintenance
- 4.12 Monitoring
- 4.13 Upgrade maintenance strategy
- 4.13.1 Preproduction testing
- 4.13.2 Software upgrades
- 4.13.3 Updating a large number of servers (Data Collectors)
- Part 3 Managing Server installation
- Chapter 5. WebSphere Studio Application Monitor Managing Server installation
- 5.1 Managing Server installation overview
- 5.2 Prepare to install
- 5.3 Software level requirements
- 5.4 Hardware configuration requirements
- 5.5 Network considerations
- 5.6 Database software installation.
- 5.7 J2EE application server installation
- 5.8 Optional: HTTP Web server installation
- 5.9 Virtual Frame Buffer installation
- 5.10 Create users
- 5.10.1 Linux (Intel), Linux for zSeries, and Sun Solaris: User and directory structure creation
- 5.10.2 AIX 5L: User and directory structure creation
- 5.11 Set up the environment
- 5.11.1 Linux (Intel), Linux for zSeries, and Solaris: WebSphere Application Server variables and DB2 source setup
- 5.11.2 AIX 5L: WebSphere Application Server variables and DB2 source setup
- 5.12 Validate that the environment variables are set
- 5.12.1 Linux (Intel), Linux for zSeries, or Solaris: Environmental command
- 5.12.2 AIX 5L: Environmental command for session
- 5.13 Start the J2EE server
- 5.13.1 Linux (Intel), Linux for zSeries, or Sun Solaris: WebSphere Application Server validation
- 5.13.2 AIX 5L: WebSphere Application Server validation
- 5.14 Run the non-interactive silent MS installation for all UNIX platforms
- 5.15 Run the graphical user interface MS installation
- 5.16 Set file permissions and directory ownership
- 5.17 Start the Managing Server
- Part 4 Distributed Data Collector installation
- Chapter 6. WebSphere Studio Application Monitor distributed Data Collector installation
- 6.1 Installation of the Distributed Data Collectors
- 6.1.1 Software requirements
- 6.1.2 Prepare to run the installer
- 6.2 Install Application Monitor V3.1 Data Collector on Windows 2000 Server SP4
- 6.2.1 Start the J2EE server to be monitored
- 6.2.2 Set up environment variables for the Application Monitor DC installer
- 6.2.3 Unpackage the installation code
- 6.2.4 Microsoft Windows graphical user interface installation
- 6.2.5 Microsoft Windows non-interactive (silent) installation
- 6.2.6 Configure the Data Collector
- 6.3 Linux (Intel), Linux for zSeries, and AIX 5L Data Collector.
- 6.3.1 Start the J2EE server to be monitored
- 6.3.2 Set up environment variables for the Application Monitor DC installer
- 6.3.3 Unpackage installation code
- 6.3.4 UNIX graphical user interface DC installation
- 6.3.5 Non-interactive (silent) DC installation
- Part 5 z/OS subsystem and Data Collector installations
- Chapter 7. CYN1 z/OS subsystem
- 7.1 What the CYN1 subsystem does and how
- 7.2 Install CYN1
- 7.2.1 Preallocate data sets on z/OS
- 7.2.2 Extract the TAR file with CYN data sets
- 7.2.3 Transfer files from the PC to z/OS
- 7.2.4 Receive the files on z/OS
- 7.2.5 Define the subsystem CYN1
- 7.2.6 Provide RACF authorization
- 7.2.7 Update PROC00
- 7.2.8 Authorize data sets and update LNKLST
- 7.2.9 Install the IEFU83 exit
- 7.2.10 Start CYN1PROC
- 7.2.11 Optional customization for large WebSphere environments
- 7.3 Verify the CYN1 installation
- 7.3.1 Display commands to verify your installation
- 7.3.2 SCYNAUTH listing
- 7.3.3 SCYNPROC listing
- Chapter 8. Data Collector for z/OS
- 8.1 About the z/OS Data Collector for WebSphere Application Server for z/OS
- 8.2 Plan your installation
- 8.2.1 Check prerequisites
- 8.2.2 Plan your Managing Server
- 8.2.3 Plan which servers you want to monitor
- 8.2.4 Plan your Application Monitor naming convention
- 8.2.5 Plan for SMF or Workload Manager reporting
- 8.2.6 Plan for configuration change
- 8.2.7 Plan for periodic log cleanup
- 8.2.8 Plan for network considerations
- 8.2.9 Firewalls
- 8.2.10 Plan for application testing
- 8.3 Overview of installation steps
- 8.4 Install the UNIX System Services components
- 8.4.1 Overview of the UNIX System Services installation steps
- 8.4.2 Binary FTP the TAR file to a temporary directory on z/OS
- 8.4.3 Untar the file
- 8.4.4 Change permissions
- 8.4.5 Change ownership.
- 8.4.6 Copy the files to a new directory structure
- 8.4.7 Update configuration parameters
- 8.5 Customize WebSphere Application Server for z/OS
- 8.5.1 Update the WebSphere Application Server for z/OS servant region procedure
- 8.5.2 Configure the probe services
- 8.5.3 Configure the z/OS Data Collector Home Runtime
- 8.5.4 Configure the protocol timeout properties
- 8.5.5 Configure the administrative services
- 8.5.6 Configure the servant region libpath
- 8.5.7 Supporting global and Java security
- 8.5.8 Next steps
- 8.6 Start the Data Collector
- 8.7 Optional support for WebSphere Application Server for z/OS Version 5 functions
- 8.7.1 Add SMF support
- 8.7.2 Add PMI support
- 8.7.3 Add JDBC support
- 8.7.4 Add JNDI support
- 8.7.5 Add JMS support
- 8.7.6 Add Message Queue Interface (MQI) capturing support
- 8.7.7 Add multiple host support (multiple IP stacks)
- 8.7.8 Add support for composite requests using CICS Transaction Gateway
- 8.7.9 Add support for composite requests using IMS Connect
- 8.7.10 Add support for J2EE-to-J2EE monitoring
- 8.8 Install into multiple J2EE servers on the same z/OS system
- 8.9 Uninstall the WebSphere Application Server for z/OS Data Collector
- Chapter 9. CICS Transaction Server for z/OS Data Collector
- 9.1 Installation steps
- 9.1.1 z/OS
- 9.1.2 MVS/UNIX System Services
- 9.1.3 CICS TS configuration changes
- 9.2 Start CICS TS with Application Monitor for CICS
- 9.2.1 Start CICS TS
- 9.2.2 Configure the DC in the Application Monitor Managing Server console
- 9.3 WebSphere Application Server-CICS Transaction Gateway-CICS composite request monitoring
- 9.3.1 Application Monitor WebSphere J2EE Data Collector
- 9.3.2 CICS Transaction Gateway
- 9.4 WebSphere Application Server-MQ-CICS composite request monitoring
- 9.4.1 Application Monitor WebSphere J2EE Data Collector.
- 9.4.2 WebSphere MQ.
