Middleware News

What's new in IBM Integration Bus V9 IBM Integration Bus is IBM's strategic integration product for Java, Microsoft .NET, and heterogeneous integration scenarios. It represents a significant evolution of the WebSphere Message Broker technology base, and includes new features such as policy-based workload management, business rules, and integration with Business Process Management (BPM) and Microsoft .NET. It also incorporates WebSphere Enterprise Service Bus (ESB) use cases, and WebSphere ESB capabilities will be folded into IBM Integration Bus over time, with conversion tools for initial use cases built-in from day one. This article describes the highlights of IBM Integration Bus V9 for both existing WebSphere Message Broker and WebSphere ESB customers, and for those new to integration. IBM® Integration Bus is designed to solve all integration require

IBM® Integration Bus Advanced formerly known as WebSphere® Message Broker is an enterprise service bus (ESB) providing connectivity and universal data transformation for service-oriented architecture (SOA) and non-SOA environments. Now businesses of any size can eliminate point-to-point connections and batch processing regardless of platform, protocol or data format. With IBM Integration Bus Advanced: Utilize robust capabilities to address diverse integration requirements to meet the needs of any size project. Help your entire organization make smarter business decisions by providing rapid access, visibility and control over data as it flows through your business applications and systems. Connect throughout an array of heterogeneous applications and web services, removing the need for complex point-to-point connectivity. Provide extensive support for Microsoft applications and services to make the most of your existing Microsoft .NET skills and software investment. D

Software AG's webMethods Integration Platform is a proven, pre-integrated software suite that enables enterprises to rapidly integrate systems, services, devices, processes, business partners and data to provide new business value and improve business performance. Overview Capabilities Business Needs Resources Customers Analysts Products Summary Quickly connect all systems and applications—no matter where they are using the webMethods Integration Platform. Leverage IT investments and adopt new technologies quickly and with less risk and redundancy. Capabilities are extensive. Along with application, B2B and cloud integration, the platform covers API management, managed file transfer, master data management, SOA and a complete suite for mobile applications. What You Can Do with the Platform INTEGRATE ANYTHING WITH EVERYTHING Connect any system or application silo with plug-and-play ease Share data across systems Link mobile and SaaS apps secur

The Service Component Architecture (SCA) framework provides three different types of bindings to choose from for SCA import: MQ Binding MQ JMS Binding JMS Binding WebSphere ESB, by virtue of its underlying WebSphere Application Server components, supports publish/subscribe messaging implemented using the default messaging provider. While this article does not use that scenario, it explains the steps needed when you already have WebSphere MQ as the underlying messaging provider. WebSphere MQ V7 or later provides out-of-the-box support for publish/subscribe messaging. This article shows you how to use the WebSphere MQ JMS binding to implement publish/subscribe messaging for seamless integration of events and data. The steps in this article will work on WebSphere MQ V7 or later and WebSphere ESB V6.2 or later. The example below uses a sim

How to Install MQ on Redhat Linux 1.1 User creation Login as  root  to install mq Create following user with group name of “mqm” which will be used to run MQ groupadd mqm # add group mqm (purpose of gropuadd is to create a new group account) useradd -g mqm mqm # add user mqm to group mqm (gpn)(usrn) # gpn – groupname # usrn -- username (useradd or usermod command is used to add a user to a group.useradd command creates a new user or update default new user information.usermod command modifies a user account i.e. it is useful to add user to existing group.User account related info is stored in /etc/passwd, /etc/shadow and /etc/group.) 1.2 Create mount points to install MQ create mqm folder under /opt and /var where the Websphere MQ gets installed. create /opt/mqm root@li-dev01/> cd /opt/ root@li-dev01/opt> mkdir mqm # make it RW to mqm group and 600MB in space capacity create /var/mqm as above # make it RW to mqm group and 300MB in space capacity

IBM WebSphere MQ V7 can help you increase messaging availability without requiring specialist skills or additional hardware. It provides automatic failover via multi-instance queue managers in the event of an unplanned outage, or controlled switchover for planned outages such as applying software maintenance. With this new availability option, the messages and data for a multi-instance queue manager are held on networked storage accessed via a network file system (NFS) protocol, such as NFS V4. You can then define and start multiple instances of this queue manager on different machines, with one active instance and one standby instance. The active queue manager instance processes messages and accepts connections from applications and other queue managers. It holds a lock on the queue manager data to ensure tha

Introduction Part 1 in this article series covered the basics of multi-instance queue managers and multi-instance brokers, and described the active-passive technique of high availability and horizontal clustering. This article describes the new multi-instance broker feature in IBM® WebSphere® Message Broker, and shows you how to use it used to configure an active-active load-balanced environment. To implement this environment, you need to cluster the WebSphere Message Broker and WebSphere MQ components both horizontally and vertically, as shown in Figure 1: Vertical clustering Vertical clustering is achieved by clustering the queue managers using WebSphere MQ clustering, which optimizes processing and provides the following advantages: Increased availability of queues, since multiple instances are exposed as cluster queues Faster throughput of messages, since messages can be delivered on multiple queues Better distribution of workload based on non-functional r