Messaging solutions in a Linux environment

Messaging solutions in a Linux environment

Recently, the adoption of Linux as a platform for business-critical applications has increased significantly. This evolution has also introduced requirements and technologies that were previously not seen in a Linux environment. Messaging and integration products, such as WebSphere MQ and WebSphere...

Descripción completa

Detalles Bibliográficos
Autor principal: Putte, Geert van de (Autor)
Autor Corporativo: Books24x7, Inc (-)
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:
Linux.
WebSphere.
Telecommunication > Message processing.
Electronic mail systems.
Electronic data interchange.
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009626960606719
Tabla de Contenidos:
  • Front cover
  • Contents
  • Notices
  • Trademarks
  • Preface
  • The team that wrote this redbook
  • Become a published author
  • Comments welcome
  • Chapter 1. Introduction to Linux and messaging
  • 1.1 Introduction to the world of Linux
  • 1.1.1 Linux
  • 1.1.2 Linux kernel
  • 1.1.3 Linux operating system
  • 1.1.4 Linux distributions
  • 1.2 Concepts of Message Oriented Middleware
  • 1.2.1 Point-to-point messaging
  • 1.2.2 Publish/subscribe
  • 1.2.3 A conceptual paradigm view
  • 1.3 Introducing WebSphere MQ
  • 1.3.1 WebSphere MQ support for Linux
  • 1.3.2 WebSphere MQ objects and security
  • 1.3.3 WebSphere MQ administration and management
  • 1.3.4 WebSphere MQ intercommunication and remote queuing
  • 1.3.5 WebSphere MQ transport types
  • 1.3.6 WebSphere MQ application programming interfaces
  • 1.4 Message broker concepts
  • 1.5 Introducing WebSphere BI Message Broker family
  • 1.5.1 Architecture overview
  • 1.5.2 Runtime environment
  • 1.6 Introducing WebSphere Application Server
  • Chapter 2. Linux systems and advanced technologies
  • 2.1 Scalability versus high availability
  • 2.1.1 Scalability
  • 2.1.2 High availability
  • 2.2 Linux technologies for scalability
  • 2.2.1 Storage area network
  • 2.2.2 IBM hardware offerings for Linux scalability
  • 2.2.3 IBM software offerings for Linux scalability
  • 2.2.4 Open source offerings for Linux scalability
  • 2.3 Linux technologies for high availability
  • 2.3.1 Journaled file systems
  • 2.3.2 IBM software offerings for Linux high availability
  • 2.3.3 Open source offerings for Linux high availability
  • 2.4 Creating a highly available and scalable solution
  • Chapter 3. Implementing HA queue managers: Part 1
  • 3.1 Scenario one overview
  • 3.1.1 Using WebSphere MQ in bindings mode
  • 3.1.2 Using WebSphere MQ in client mode
  • 3.2 Using Linux-HA
  • 3.2.1 Features of Linux-HA.
  • 3.2.2 Planning an implementation
  • 3.2.3 Perform an implementation
  • 3.2.4 Heartbeat configuration
  • 3.2.5 Heartbeat authentication
  • 3.2.6 High availability resource configuration
  • 3.2.7 Network mirror configuration
  • 3.2.8 Validating heartbeat failover and failback
  • 3.2.9 HA configuration summary
  • 3.3 Installing and configuring WebSphere MQ
  • 3.3.1 Preinstallation steps
  • 3.3.2 Installation steps
  • 3.3.3 Postinstallation steps and install verification
  • 3.4 Message generation application
  • 3.4.1 Design of the message generation application
  • 3.4.2 Developing the message generation application
  • 3.4.3 Compiling and running the message generation application
  • 3.5 Message retrieval application
  • 3.5.1 Design of the message retrieval application
  • 3.5.2 Developing the message retrieval application
  • 3.6 WebSphere MQ HA configuration and scripts
  • 3.6.1 Normal scenario
  • 3.6.2 Configuring wmq1 and wmq2 for WebSphere MQ HA
  • 3.6.3 Failover
  • 3.6.4 Failback
  • 3.7 Persistent messages on WebSphere MQ queues
  • 3.8 Bindings versus client tests
  • 3.9 Running the Bindings mode test
  • 3.9.1 Queue Manager configuration
  • 3.9.2 Configuration verification
  • 3.9.3 WebSphere Application Server configuration
  • 3.9.4 Queue Manager in action
  • 3.9.5 Summary of results
  • 3.10 Running the Client mode test
  • 3.10.1 Queue manager configuration
  • 3.10.2 Configuration of WebSphere Application Server
  • 3.10.3 WebSphere Application Server in action
  • 3.10.4 Summary of results
  • 3.11 Summary
  • Chapter 4. Implementing HA queue managers: Part 2
  • 4.1 Scenario two overview
  • 4.2 Implementing Linux-HA on SUSE
  • 4.2.1 Planning an implementation
  • 4.2.2 Installing Linux High-Availability
  • 4.2.3 Configuring Linux-HA
  • 4.2.4 Configuring and testing the shared SCSI drives
  • 4.2.5 Validating heartbeat failover and failback.
  • 4.2.6 HA configuration summary
  • 4.3 Installing and configuring WebSphere MQ
  • 4.4 Message generation application
  • 4.4.1 Compiling and running the message generation application
  • 4.5 Messaging retrieval application
  • 4.6 WebSphere MQ HA scripts and configuration
  • 4.6.1 Normal scenario
  • 4.6.2 Configuring brk1 and brk2 for WebSphere MQ HA
  • 4.7 Running the shared-disk test
  • 4.7.1 Queue manager configuration
  • 4.7.2 Configuration verification
  • 4.7.3 WebSphere Application Server configuration
  • 4.7.4 Application in action
  • 4.8 Summary
  • Chapter 5. Implementing HA queue managers: Part 3
  • 5.1 Scenario three overview
  • 5.2 Planning an implementation
  • 5.2.1 Hardware setup
  • 5.2.2 Cluster components
  • 5.2.3 GPFS file systems
  • 5.3 Performing an implementation
  • 5.3.1 Time synchronization
  • 5.3.2 Secure communications
  • 5.3.3 Support programs for the FAStT device
  • 5.3.4 RSCT and GPFS
  • 5.3.5 Configuring WebSphere MQ
  • 5.3.6 Message generating application
  • 5.3.7 Compiling and running the message generation application
  • 5.3.8 Messaging retrieval application
  • 5.3.9 Adding Linux high availability
  • 5.3.10 HA configuration summary
  • 5.4 Running the shared-disk test
  • Chapter 6. Using WebSphere MQ clustering
  • 6.1 Scenario four overview
  • 6.1.1 Using WebSphere MQ clustering for high-availability
  • 6.2 Introduction to WebSphere MQ Cluster
  • 6.2.1 WebSphere MQ clusters benefits
  • 6.2.2 WebSphere MQ cluster terminology
  • 6.3 Installing and configuring WebSphere MQ
  • 6.4 Message generation application
  • 6.5 Messaging retrieval application
  • 6.6 WebSphere MQ cluster setup
  • 6.6.1 Defining the full repository queue managers
  • 6.6.2 Defining the cluster partial repository queue managers
  • 6.6.3 Configuration verification
  • 6.7 Configuration of WebSphere Application Server
  • 6.8 Application in action
  • 6.9 Summary.
  • Chapter 7. Implementing highly available brokers
  • 7.1 Scenario overview
  • 7.1.1 Using brokers with WebSphere MQ clustering for high availability
  • 7.1.2 Using hardware failover for high-availability in brokers
  • 7.2 Introduction to WebSphere BI Message Broker
  • 7.2.1 WebSphere BI Message Broker architecture
  • 7.2.2 The broker
  • 7.2.3 Introducing message flows
  • 7.2.4 Introduction to message modeling and message sets
  • 7.2.5 Message Brokers Toolkit for WebSphere Studio
  • 7.2.6 WebSphere BI Message Broker configuration manager
  • 7.2.7 User name server
  • 7.3 Installing and configuring the broker
  • 7.3.1 Installing and configuring WebSphere MQ
  • 7.3.2 Installing and configuring DB2
  • 7.3.3 Installing and configuring WebSphere BI Message Broker
  • 7.4 Implementation steps
  • 7.5 Creating databases and tables
  • 7.5.1 Creating databases on the WebSphere Application Server
  • 7.5.2 Database setup on Windows win6336
  • 7.5.3 DB2 client setup on hosts brk1 and brk2
  • 7.6 Design and development of the message set
  • 7.6.1 Designing the message set
  • 7.6.2 Developing the message set
  • 7.6.3 Creating the message definition file
  • 7.6.4 Creating the logical structure of the message
  • 7.7 Design and development of message flow
  • 7.7.1 Message flow design
  • 7.7.2 Message flow development
  • 7.8 Configuring the broker domain
  • 7.8.1 Queue manager configuration
  • 7.8.2 Creation and configuration of configuration manager
  • 7.8.3 Broker creation
  • 7.8.4 Connecting brokers to the configuration manager
  • 7.9 Deploying the message flow and message set
  • 7.9.1 Creating a message broker archive
  • 7.9.2 Deploying a bar file
  • 7.10 WebSphere Application Server configuration
  • 7.11 Message generation application
  • 7.12 Message retrieval application
  • 7.12.1 The servlet MonitorStatusServlet.java
  • 7.12.2 The class
  • 7.13 Application in action.
  • 7.13.1 Normal scenario
  • 7.13.2 Failover scenario
  • 7.13.3 Failback scenario
  • 7.14 Summary
  • Chapter 8. Managing a distributed Linux messaging infrastructure
  • 8.1 Planning monitoring
  • 8.2 Implementing WebSphere MQ event monitoring
  • 8.2.1 Queue manager events
  • 8.2.2 Performance events
  • 8.2.3 Channel events
  • 8.2.4 Monitoring program
  • 8.3 Implementing monitoring tool Monit
  • 8.3.1 Installing Monit
  • 8.3.2 Configuring Monit
  • Appendix A. Hardware and software configuration
  • Hardware and software used for first scenario
  • Hardware and software used for the second scenario
  • Hardware and software used for the third scenario
  • Appendix B. Using external SCSI storage enclosure with Linux
  • Configuring ServeRAID controllers for clustering
  • Appendix C. Configuring a FAStT200 disk system for Linux
  • Configuring SANbox2 to use static IP address
  • Configuring the FAStT200 disk enclosure to use a static IP-address
  • Installing the Fiber Host Adapter FC2/133
  • Updating the host adapter BIOS
  • Install the host adapter drivers
  • Install the FAStT_MSJ
  • Appendix D. Additional material
  • Locating the Web material
  • Using the Web material
  • System requirements for downloading the Web material
  • How to use the Web material
  • Abbreviations and acronyms
  • Related publications
  • IBM Redbooks
  • Other publications
  • Online resources
  • How to get IBM Redbooks
  • Help from IBM
  • Index
  • Back cover.

Ejemplares similares