This IBM® RedpaperTM publication provides information about how to build, deploy, and use IBM MQ as a service. The information in this paper includes the key factors that must be considered while planning the use of IBM MQ as a service. Through descriptions and examples, this paper explains how to apply as a service methodologies to an IBM MQ environment, and describes techniques and preferred practices for integrating IBM MQ into a self-service portal. This paper explains how to create and use an IBM MQ as a service self-service menu for a portal. It includes examples that show how to use an IBM MQ as a service catalog. This paper describes options and techniques for deploying IBM MQ as a service that is tailored to the specific enterprise messaging needs of an organization. Although these techniques can be employed in a cloud environment, they are equally applicable in an on-premises enterprise data center. This paper includes information about the various infrastructure options that can be selected when implementing IBM MQ as a service. The information in this paper helps infrastructure administrators to define services so that you can provision IBM MQ resources quickly. The target audiences of this paper are developers, infrastructure administrators, and line-of-business (LOB) professionals who want to provision IBM MQ resources to be accessed as services in small, medium, large, and complex implementations.

In order to remain competitive in today's world, companies need to be able to integrate internally and externally by connecting sensors, customers and partners with the information in their systems of record. In short, they need to integrate with everything. This IBM® Redbooks® publication describes how IBM Application Integration Suite and IBM Messaging portfolio can be used to satisfy the needs of core hybrid integration use cases, accelerating companies in their digital transformation journey. All concepts are explained within the context of these use cases: Joining the API economy Improving productivity Refactoring for innovation The target audience for this book is cloud and integration architects and specialists who are implementing hybrid integration solutions.

This book constitutes the Revised Selected Papers of the Second International Conference, ICAETA 2023, held in Istanbul, Turkey, during March 10–11, 2023. The 37 full papers included in this volume were carefully reviewed and selected from 139 submissions. The topics cover a range of areas related to engineering, technology, and applications. Main themes of the conference include, but are not limited to: Data Analysis, Visualization and Applications; Artificial Intelligence, Machine Learning and Computer Vision; Computer Communication and Networks; Signal Processing and Applications; Electronic Circuits, Devices, and Photonics; Power Electronics and Energy Systems.

This IBM Redbooks publication describes the fundamental concepts and benefits of message queuing technology. This book is an update of a very popular Redpaper (REDP-0021) based on IBM WebSphere MQ Versions 5.0 to 5.2. This publication provides a design-level overview and technical introduction for the established and reliable WebSphere MQ product. A broad technical understanding of the WebSphere MQ product can improve design and implementation decisions for WebSphere MQ infrastructures and applications. To reduce the time required to gain this understanding, this book summarizes relevant information from across the WebSphere MQ product documentation. We also include hands-on security and troubleshooting sections to aid understanding and provide a reference for common administrative actions performed when building and maintaining WebSphere MQ infrastructures. In the appendix, we provide a summary of the new features in WebSphere MQ Version 6.0.

The differences between well-designed security and poorly designed security are not always readily apparent. Poorly designed systems give the appearance of being secure but can over-authorize users or allow access to non-users in subtle ways. The problem is that poorly designed security gives a false sense of confidence. In some ways, it is better to knowingly have no security than to have inadequate security believing it to be stronger than it actually is. But how do you tell the difference? Although it is not rocket science, designing and implementing strong security requires strong foundational skills, some examples to build on, and the capacity to devise new solutions in response to novel challenges. This IBM® Redbooks® publication addresses itself to the first two of these requirements. This book is intended primarily for security specialists and IBM WebSphere® MQ administrators that are responsible for securing WebSphere MQ networks but other stakeholders should find the information useful as well. Chapters 1 through 6 provide a foundational background for WebSphere MQ security. These chapters take a holistic approach positioning WebSphere MQ in the context of a larger system of security controls including those of adjacent platforms' technologies as well as human processes. This approach seeks to eliminate the simplistic model of security as an island, replacing it instead with the model of security as an interconnected and living system. The intended audience for these chapters includes all stakeholders in the messaging system from architects and designers to developers and operations. Chapters 7 and 8 provide technical background to assist in preparing and configuring the scenarios and chapters 9 through 14 are the scenarios themselves. These chapters provide fully realized example configurations. One of the requirements for any scenario to be included was that it must first be successfully implemented in the team's lab environment. In addition, the advice provided is the cumulative result of years of participation in the online community by the authors and reflect real-world practices adapted for the latest security features in WebSphere MQ V7.1 and WebSphere MQ V7.5. Although these chapters are written with WebSphere MQ administrators in mind, developers, project leaders, operations staff, and architects are all stakeholders who will find the configurations and topologies described here useful. The third requirement mentioned in the opening paragraph was the capacity to devise new solutions in response to novel challenges. The only constant in the security field is that the technology is always changing. Although this book provides some configurations in a checklist format, these should be considered a snapshot at a point in time. It will be up to you as the security designer and implementor to stay current with security news for the products you work with and integrate fixes, patches, or new solutions as the state of the art evolves.

Enterprise Architecture A to Z examines cost-saving trends in architecture planning, administration, and management. The text begins by evaluating the role of Enterprise Architecture planning and Service-Oriented Architecture (SOA) modeling. It provides an extensive review of the most widely-deployed architecture framework models, including The Open Group Architecture and Zachman Architectural Frameworks, as well as formal architecture standards. The first part of the text focuses on the upper layers of the architecture framework, while the second part focuses on the technology architecture. Additional coverage discusses Ethernet, WAN, Internet communication technologies, broadband, and chargeback models.

Microservices is an architectural style in which large, complex software applications are composed of one or more smaller services. Each of these microservices focuses on completing one task that represents a small business capability. These microservices can be developed in any programming language. They communicate with each other using language-neutral protocols, such as Representational State Transfer (REST), or messaging applications, such as IBM® MQ Light. This IBM Redbooks® publication gives a broad understanding of this increasingly popular architectural style, and provides some real-life examples of how you can develop applications using the microservices approach with IBM BluemixTM. The source code for all of these sample scenarios can be found on GitHub (https://github.com/). The book also presents some case studies from IBM products. We explain the architectural decisions made, our experiences, and lessons learned when redesigning these products using the microservices approach. Information technology (IT) professionals interested in learning about microservices and how to develop or redesign an application in Bluemix using microservices can benefit from this book.

This IBM® Red paper books® publication is divided into three parts: Part 1, "Introduction" on page1, provides an introduction to message-oriented middleware and the WebSphere® MQ product. We discuss the concept of messaging, explaining what is new in WebSphere MQ V7.0 and how it is implemented. An overview is provided on how it fits within the service-oriented architecture (SOA) framework. Part 2, "WebSphere MQ V7.0 enhancements and changes" on page 41, explains the new WebSphere MQ V7.0 features and enhancements in detail and includes compatibility and the migration considerations from the previous supported versions. Part 3, "Scenario" on page253, contains a scenario that demonstrates how the new features and enhancements work and how to use them. The sample programs and scripts used for this scenario are available for download by following the instructions in Appendix B, "Additional material" on page379.

Packed with international case studies and examples, the book begins with a detailed analysis of the state of CRM and e-business in the financial services globally, and then goes on to provide comprehensive and practical guidance on: making the most of your customer base; systems and data management; risk and compliance; channels and value chain issues; implementation; strategic implications.

This IBM® RedpaperTM publication will help you install, tailor, and configure IBM OMEGAMON® for JVM on IBM z/OS®. You can use OMEGAMON to recognize and resolve problems in monitoring Java resources on z/OS, including within IBM CICS®, IBM IMSTM, and z/OS Connect EE regions. A discussion on the growth of Java on z/OS is provided and explanation on the reasons why monitoring Java resources is critical to any modern z/OS environment.