SOA ESB on MuleSource and ActiveMQ

This module covers the detailed design for the Service Processing Platform (SPP) and the Enterprise Service Bus (ESB) (full specification to be supplied after winning supplier chosen) [login to view URL];view=article&id=57&Itemid=43 The Enterprise Service Bus (ESB) will be deployed for the SOAmods project and provide the default data routing for the systems integration between the back-office (CRM, ERP, CMS) and the front-office applications (Website, marketing, e-commerce). The main features supplied by the ESB will be: [login to view URL] routing between asynchronous queues [login to view URL] endpoints to process messages [login to view URL] a message infrastructure for a SaaS (Software as a Service) hosted environment. Winning Bids will be based on [login to view URL] experience with Mule ESB and ActiveMQ [login to view URL] of approach to deliver this module [login to view URL] of company and size of team to implement this module [login to view URL] of production deployment or reference letters [login to view URL] of Java and knowledge of SOA The service within this design will concentrate on the following functionality deliverables: Deliverable 1 XXXXXXXXXXXXXXX Default configuration script to be run in each environment Default configuration script to be run in each environment to ensure that the sane base installation is consistent. We will be running many environments and will therefore need a default configuration to be migrated from dev, test, and production. Deliverable 2 XXXXXXXXXXXXXXX MuleSource ESB deployment on redundant servers and LDAP security The ESB is a redundant set of applications that provide the messaging infrastructure for the SOAmods project. They are as follows: [login to view URL] – used for all message routing and queue management [login to view URL] [login to view URL] MQ – provides all queues [login to view URL] [login to view URL] connector for security [login to view URL] Fuji – for all automated syndication and adapters [login to view URL] Deliverable 3 XXXXXXXXXXXXXXX SaaS Message Routing and Queuing strategy There are 3 ecosystems that will require data as follows: [login to view URL] – Public users (fos) [login to view URL] – Company (bos) [login to view URL] - Partners There should be default queues for each company. As we register a new company we need to supply a new set of queues to support the system. Queues should be based on domain such as the following: [login to view URL] – Organizational, contacts, and users [login to view URL] - Catalogs, Products, and Warehouses [login to view URL] – leads, opportunities, quotes, and orders [login to view URL] – accounting Deliverable 4 XXXXXXXXXXXXXXX Sample Test Harness and minimal Operations tools to maintain and monitor our active and dead letter queues Sample Test Harness and minimal Operations tools to maintain and monitor our active and dead letter queues Test Harness – Active MQ web based sample Need to add login to the test harness consider running on Jboss Portal with LDAP Active MQ – Queue Inspector Need to add login to the test harness consider running on Jboss Portal with LDAP Deliverable 5 XXXXXXXXXXXXXXX Message Routing and Syndication Server (one sample transformation based on Fuji) Ensure that we are able to supply a message routing of messages based on WS Addressing (To and Action) to properly route the messages to the correct Segment (Company) We need to Support a Publish/Subscribe Model for similar messages. Such as new inventory published and sent to all subscribers of that data segment. We need to support an automated syndication server to send messages from our standard model to partner proprietary formats via an adapter