PUR1311/19. Request for Information (RFI) Provision of an Enterprise Service Bus. to the. European Bank for Reconstruction and Development

Transcription

1 PUR1311/19 Request for Information (RFI) Provision of an Enterprise Service Bus to the European Bank for Reconstruction and Development

2 0. Definitions Bank means the European Bank for Reconstruction and Development with its headquarters at One Exchange Square, London, EC2A 2JN. Supplier means a provider of enterprise service bus software that can provide its services in the United Kingdom. RFI means Request for Information. 1. Introduction The European Bank for Reconstruction and Development (the "Bank") is an international financial institution. The Bank was established by treaty in 1990, with its headquarters in London, to foster the transition towards open market oriented economies and to promote private and entrepreneurial initiatives in Central and Eastern Europe, the Baltic States and the Commonwealth of Independent States that are committed to and applying the principles of multiparty democracy, pluralism and market economics. The Bank has 63 members (61 countries, the European Community and the European Investment Bank). Further information about the Bank's roles and activities can be found on the Bank's website: 2. Purpose of this RFI The purpose of this RFI is to gather information from the market to assist the Bank in its preparations to tender for a Supplier to provide enterprise service bus software. 3. Contact details The sole contact for this RFI is as follows: Tom Gale Principal Manager, Corporate Procurement Unit galet@ebrd.com Tel: Timetable Activity Date Launch of RFI on EBRD s web page 14/11/2013 Deadline for receipt of requests for clarification 28/11/2013 EBRD publishes responses to requests for clarification 05/12/2013 Deadline for responses to RFI 19/12/2013

3 5 Clarifications The process for reception and resolution of queries shall be as follows: Suppliers will send queries by to the following address: There will be one round of queries. The deadline for queries is shown in the timetable set out in section 4.2 of this RFP. The EBRD will publish the responses to all queries on the Bank s website in accordance with the timetable set out in section 4 of this RFI. The clarification document will make no reference to which Supplier made any particular query. 6 Responses Suppliers are asked to review the Bank s requirements as defined in Annex 1 of this RFI and to compile a response to the questions detailed in sections Responses can be sent via to the sole contact for this RFI as defined above. 7 Supplier costs EBRD is not responsible for any Supplier costs associated with this RFI, Supplier responses or any contract discussions or negotiations. Nor is EBRD responsible for any indirectly related costs. No statement by EBRD should be viewed as a request by EBRD or justification for Suppliers to increase or change inventory, staff, facilities, business relationships with its Suppliers, or internal business processes. All actions by Suppliers in response to this RFI or subsequent discussions or negotiations should be taken with the clear understanding that neither this RFI nor subsequent actions or omissions by EBRD obligate or commit EBRD to pay or reimburse Suppliers for any costs or expenses they incur. This RFI is not an offer to enter into a contract.

4 Annex 1 RFI Questions 1.0 Functionality Requirements EBRD defines an enterprise service bus as follows: To facilitate service orientation certain fundamental technologies are needed, of which the most basic is the ESB. An ESB is a messaging hub, which sits between all the service-oriented applications, mediating communications between them. It is essential for simplifying and managing the many and varied connections which will be emerge in a mature SOA. 2.0 Essential Features The "must have" requirements for the product include: A registry, to provide a searchable directory of definitions of all services published via the bus. Connectivity support, to allow it to connect to systems using a wide variety of open and proprietary protocols. Transformation capabilities, to allow it to map messages between different protocols and formats. Routing capabilities, to allow messages to be sent to the correct destinations based on their content and other attributes. Monitoring capabilities, to support performance analysis, message audit, exception tracking etc. Sections 4.0 through 11 contain tables asking for detailed information on a variety of features. Please answer all and add relevant information. 3.0 Definitions Notes: The word Product is used throughout and should be understood to mean ESB product, or suite of products as appropriate. Integration is taken to be the collective term for all the elements needed to create a single, executable service or interface including inbound and outbound adapters, mappings and other required context.

5 4.0 General 4.1 Describe your company background, and please include: An overview of the Company History Financial Health Growth / Merger History and Plans Position against Competitors Total Percentage of Market Share Strategic Industry Advantages / Partnerships 4.2 Describe your professional services capabilities. 4.3 Provide a general description of your company s background and experience with regard to enterprise service bus solutions. Please state how many years has your company been in the enterprise service bus business. Is this the primary business of the company? 4.4 State the number of your company s active enterprise service bus customers. How many new customers were acquired, and how many existing customers were lost, during the last financial year? 4.5 Highlight any relevant relationships with other vendors for technology included in your product or recommended solution. Specify the nature of the relationship, such as OEM, co-marketed or co-selling. 4.6 Please specify the various levels of support offered (for example, 24/7), minimum response time, and other support models and details. 4.7 Describe your general R&D approach, current areas and levels of investment. Outline the capabilities planned for the next release or version as well as the timetable for those capabilities 4.8 Describe your proven capability to deliver products and implementation services within the customer's desired time frame. 4.9 Describe your ability to provide a fully developed and proven training program for the product. 5.0 Integration Design 5.1 Does the product have a visual modelling tool for creating message mappings and other integration elements? Include a brief description. 5.2 Does the product support XSLT transformation for complex mappings?

6 5.3 Does the product support code modules for complex mappings? List supported programming languages List supported IDEs for code development 5.4 Does the product have an expression editor for creating rules for use in visual mappings? Can expressions be re-used? 5.5 Can code-based rules also be used within visual mappings? Can these be made reusable? 5.6 Briefly describe the product s support of external plugins to enhance message mappings. List any relevant standards supported Does the product support end-point abstraction? I.e. can the same logical mapping be re-used with multiple service end-points and even different protocol adapters? Briefly describe the process involved in re-using a mapping in this way. 5.9 Routing: does the modelling tool support integrations with multiple endpoints (i.e. single input message mapped to multiple outputs)? How are these configured? 5.10 Routing: does the modelling tool support content-based routing of messages using complex rules? How are these configured? Can they be re-used? 5.11 Can the product import service definitions from other platforms into the modelling tool? WSDL: please specify versions and options supported. List protocols other than SOAP which can be imported into the modelling tool. Describe support for import of RESTful API definitions Type mappings: describe the modelling approach to data types in message mappings. Does the product support the concept of Global (system-independent) data types? Give a brief account of their use Caching: how is message caching supported by the modelling tool? How can cache scope and caching strategies be defined? 6.0 Integration Testing 6.1 Does the product have an interactive debugger or simulator for analysing integrations in action? Briefly describe. 6.2 Describe any tools provided to aid the testing of integrations before and after deployment. 6.3 Does the product support automation of unit or regression tests of integrations? Describe briefly. 7.0 Integration Deployment 7.1 How are completed integrations deployed from the development environment to QA and production environments? Describe the key process steps. 7.2 Does the product store and track versions of deployed integrations? Describe briefly the versioning process. 7.3 What facilities exist for rolling back an unsuccessful deployment?

7 8.0 Management and Monitoring 8.1 Contract management: describe the product s features for defining, monitoring and enforcing contracts (SLAs) between service consumers and providers. 8.2 Policy Management: describe the product s features for defining and enforcing service policies (on Security, Quality of Service, etc) 8.3 Auditing: briefly describe message auditing and logging features. 8.4 Does the product have an API for administrative tasks, to allow integration with other tools such as workflow or schedulers (e.g. Ctrl-M)? What protocol is used? 8.5 What is the architecture and components of your management and monitoring tool? How does your product monitor current Runtime Performance and Activity History? 8.6 How does your product integrate with existing monitoring frameworks (Enterprise Management tools such as HP OpenView or Trend)? How does your product escalate alerts via or other notification protocols? 9.0 Core capabilities Registry 9.1 Is there a UDDI compliant registry? Describe its relationship to the Modelling and Runtime components of the product. 9.2 What standards for Service descriptions does the Registry support? WSDL state which versions and options (WS-Policy, Document, RPC etc.) Other non-wsdl standards. Does the Registry support RESTful API definitions? 9.3 Can definitions of services offered by other systems be imported into the Registry? State any restrictions over support for locally defined services. 9.4 Describe the registry s provision for rich descriptive metadata, over and above formal service definitions (e.g. documentation formats supported). 9.5 Is there an extensible classification scheme for services, using tags or definable metadata? Give a brief description. 9.6 Describe support for flexible registry searches e.g. keyword, classification-based etc. 9.7 Does the registry support workflow for approval of changes and deployments? Describe briefly. Security 9.8 Describe the process for creation and management of internal users and Role based Access controls 9.9 Describe your product s support for single-sign on and integration with external security Authentication/Authorisation providers (e.g. MS Active Directory)

8 9.10 Give a brief overview of the product s security model for integrations Describe the supported authentication patterns and protocols for access to services. Is SAML-based authentication supported? List the versions. Is the SOAP- SAML token profile (Sender Vouches and Holder-of-Key) supported? 9.12 Is there a secure repository for passwords and identifiers used in basic authentication? Describe its use briefly Does the product support propagation of identity from requester to provider, using SAML or other patterns? List the supported protocols. Connectivity 9.14 List the supported standard protocols for integration connections, including Webservice, File, Database etc Files: what file formats are supported as standard? 9.16 Databases: does the product support calls to database Stored Procedures? 9.17 Bulk loading: does the product have any specific facilities for optimising bulk loading of large data volumes? 9.18 Specific platforms: what adapters or other facilities do you provide for connectivity with the following platforms: SAP Netweaver JBOSS (J2EE) MiSYS Summit Sybase PowerBuilder 9.19 List the Web Service (WS) standards supported List supported content-based protocols (e.g. FpML, CMIS) Integrity: briefly describe the product s support for transactional integrity across heterogeneous targets Extensibility: what is the framework for defining custom adapters or connectors for other protocols? Describe briefly Product Platform Give a brief overview of the essential components of the product and their relationships. Include a diagram if possible How can these components be grouped or clustered for high availability? Briefly describe the options How can these components be scaled or clustered for throughput? Briefly describe the options How can these components be scaled or configured to minimise latency? Briefly describe the options Does the product require an Application Server? List supported server platforms and versions Strategic View 11.1 What support do you have now for hybrid on-premise/cloud-based integration? In

9 particular: Is there a cloud-based version of the product? Describe how premise and cloud-located instances of the product can interoperate, with particular reference to sharing/replication of metadata, seamless routing and service deployments between instances. How, if at all, are these features different for a distributed multi-instance, premises-based installation? 11.2 Describe briefly your product s support for Complex Event Processing.