Red Hat, Inc. has announced its next-generation service design, development and integration platform, JBoss Fuse Service Works 6, to help enterprises unlock information dispersed in different applications, integrate disparate business processes, and transition to open hybrid cloud architectures.
Today’s enterprise IT environments are highly distributed, yet the applications, workflows and business processes—many of which are mission-critical to the function and operation of the business—are highly dependent on one another. JBoss Fuse Service Works provides the integration, orchestration, governance and monitoring required to meet the speed and quality needs of the business. JBoss Fuse Service Works sets the stage for faster and easier cloud, mobile and business process development projects by allowing IT to simplify service-enabling of existing and new applications and data.
JBoss Fuse Service Works 6 represents the next version of Red Hat JBoss SOA Platform and includes enterprise service bus (ESB) capabilities based on Apache Camel, an implementation of many of the most commonly used enterprise integration patterns (EIP). It leads to greater accuracy, agility and quality, across enterprise applications and services. Additionally, JBoss Fuse Service Works 6 provides a foundation for running integration in the cloud, setting the stage for integration Platform-as-a-Service (iPaaS).
JBoss Fuse Service Works includes:
· Enterprise Service Bus (ESB) consisting of a modern enterprise integration pattern-based development model through Apache Camel, a high-performance messaging broker through Apache ActiveMQ, and a web services framework through Apache CXF.
· Service delivery – Full life cycle support for developing, deploying and managing service-oriented applications is provided by a lightweight service delivery framework, based on Service Component Architecture (SCA), called SwitchYard. SwitchYard supports distributed and cross-functional teams with code and model-driven tooling, and enables developers to focus on the actual business logic by separating the underlying implementation.
· Service governance – Life cycle management for services, from design and development through deployment, is based on the Overlord project, helping to define, expose and enforce rules or policies.
· Business transaction monitoring – Overlord also provides the infrastructure to capture service activity information and then provides necessary metrics and alerts to help meet business and service level agreements (SLAs) and optimize the integration solutions.