SOURCES SOUGHT
70 -- Enterprise Service Bus
- Notice Date
- 12/4/2009
- Notice Type
- Sources Sought
- NAICS
- 511210
— Software Publishers
- Contracting Office
- Social Security Administration, Office of Budget, Finance, and Management, Office of Acquisition and Grants, 1st Floor, Rear Entrance, 7111 Security Blvd., Baltimore, Maryland, 21244
- ZIP Code
- 21244
- Solicitation Number
- SSA-RFI-10-1004
- Archive Date
- 12/26/2009
- Point of Contact
- Aminta Freeman,
- E-Mail Address
-
aminta.freeman@ssa.gov
(aminta.freeman@ssa.gov)
- Small Business Set-Aside
- N/A
- Description
- Business Rules Engine General Information Document Type: Sources Sought Notice Solicitation Number: Reference-Number-SSA-RFI-10-1004 Posted Date: Original Response Date: Original Archive Date: Current Archive Date: Classification Code: 7030 ADP SOFTWARE Contracting Office Address Social Security Administration, Deputy Commissioner, Budget, Finance and Maintenance, Office of Acquisition and Grants, 7111 Security Boulevard, Baltimore, MD, 21244. Description This is a REQUEST FOR INFORMATION. Reference Reference-Number-SSA-RFI-10-1004 when responding to this announcement. The Social Security Administration (SSA) is attempting to identify responsible vendors that are capable of providing an Enterprise Service Bus. Background information: •Ø The target platform the ESB will be installed on has yet to be determined. Potential platforms are; Sun Solaris (UNIX) or mainframe operating system z/OS 1.9 or higher. •Ø The Social Security Administration is utilizing t hree IBM z990 2084 and three IBM z9 2094 mainframe systems at the National Computer Center in Baltimore, Maryland. The mainframe operating system will be z/OS 1.9 or higher. The ESB must be able to interact with this processing environment. •Ø The majority of the agency's Web Applications are running on IBM's WebSphere Application server 6.1 for z/OS. There are also Web Applications running under IBM's WebSphere Application server 6.1 for SOLARIS. •Ø The agency has a large amount of legacy application running using CICS on the z/OS platform. General requirements: •Ø The product must be full featured and easy to use. Describe the main features of the product and ease of use. •Ø Support for role based activities. •Ø Describe the different user roles. •Ø Outline the development versus operations roles. •Ø Support for service creation and deployment. •Ø Supports multiple ESBs (federation). •Ø Must integrate with IBM DataPower and similar SOA appliances. •Ø ESB Administration; easy to use graphical user interfaces and support for scripting to automate configuration and administration. Mainframe Connectivity requirements: •Ø Must be able to connect to IBM DB2, CICS native, VSAM, 3270, IDMS. •Ø Must integrate with Computer Associates Top Secret and IBM Tivoli. •Ø SSA runs a cluster of IBM mainframes (Sysplex), describe support for or how your product integrates into this environment. •Ø Define additional mainframe connectivity support. Database Connectivity requirements: •Ø Must support at a minimum IBM DB2, Oracle and JDBC. •Ø List additional database supported. •Ø Describe the Java Database Connectivity (JDBC) APIs supported. Communications requirements: •Ø Synchronous and asynchronous interaction communication. •Ø Reliable messaging, once only delivery of messages. •Ø Support for various message sizes, including individual transactions, large files (greater than 1BG) and multiple transactions. •Ø Message tracking end to end. Tracking the message from origin to end point, provide status of the message, address exceptions and message resending. •Ø Message and error logging. Messaging requirements: •Ø Message-oriented middleware connectivity: must support IBM Websphere MQ, JMS, SOAP/ HTTP, SOAP/JMS and SOAP/MQ. •Ø Describe the included messaging infrastructure. •Ø Support for the Java EE Connector Architecture (JCA) resource adapter. •Ø Outline additional Message-oriented middleware connectivity support. For example support of Microsoft Message Queuing (MSMQ), Microsoft BizTalk, TIBCO Rendezvous, and Oracle Advanced Queuing? Life-cycle Support requirements: •Ø Life-cycle support. What level of life-cycle support is provided? •Ø Policy management; Describe how enable policy management is enable. For example using Metadata, UDDI integration and third party repositories. •Ø Ability to customize life-cycles. •Ø Must be able to integrate with external life-cycle management tools. •Ø Describe the life-cycle management tools supported. •Ø List supported third party vendor support of registry / repository. Tools requirements: •Ø Must integrate with Eclipse based tools. •Ø Support for services testing tools. •Ø Support for service orchestration tools. •Ø Integration with a service registry. •Ø Describe service registries supported. •Ø Support for performance monitoring tools. •Ø Describe performance monitoring supported. •Ø Describe the tools supported. Protocols requirements: •Ø Support of standard web services protocols. •Ø Ability to define custom protocols. •Ø List and describe the web services specifications and APIs supported. For example: Java Architecture for XML Binding (JAXB) specification, Java API for XML Processing (JAXP) specification, Web Services Definition Language (WSDL), etc. •Ø List support the non-web services protocols for example: XML/HTTP(s) REST, generic XML/HTTP, JCA, etc. •Ø Is it possible to extend the protocols supported by the ESB? Adapter requirements: •Ø Describe support for the following adapters: •o Package Applications such as SAP, Oracle, Siebel, etc. •o Legacy, CICS, green screens, etc. •o Technology, databases, transaction processing (TP) monitors, and gateways to third-party messaged-oriented middleware, etc. File Operations requirements: •Ø Support for the File Operations such as FTP,.tar files,.zip files. Etc. •Ø List File Operations supported. Email connectivity requirements: •Ø Must support the standard email connectivity protocols for example; Internet Message Access Protocol (IMAP), Multipurpose Internet Mail Extensions (MIME)/attachments, Post Office Protocol (POP) and Simple Mail Transport Protocol (SMTP). •Ø List connectivity protocols supported. Mediation: •Ø Support for intelligent routing for example; store and forward, publish/subscribe, request/reply and content based. •Ø List intelligent routing capabilities. •Ø Support for standard Transformation for example; XSLT, XPath, XML to XML, etc. •Ø List transformations features. •Ø Support for dynamic service virtualization. •Ø Describe dynamic service virtualization capabilities. Orchestration requirements: •Ø Support for standard specification languages. List languages supported such as BPMN. •Ø Support for standard representations such as; BPEL, XPDL, BMLP, WSFL etc. List representations supported. •Ø Describe workflow integration support. Security •Ø Authentication. •Ø Authorization. •Ø Encryption / Decryption. •Ø Digital signatures. •Ø List the Supported specifications and APIs for security. For example; Java 2 Security Manager, Java Authentication and Authorization Service (JAAS), Java Authorization Contract for Containers (JACC), etc. •Ø Support for Web services security. List the supported specifications and APIs for Web services security. For example; Canonical XML, Decryption Transform for XML Signature, OASIS Web Services Security: SOAP Message Security (WS-Security), etc. •Ø Describe Directory support, such as Generic LDAP, Microsoft Active Directory, Sun LDAP,, IBM Tivoli Access Manager, etc. •Ø Describe support roles based Authorization. •Ø Support WS-Security and SAML (security assertion markup language). •Ø Describe Audit capabilities: •o Audit logging of administrative activities is required. •o Can the logs with integrated from multiple sources? Monitoring and management requirements: •Ø Support monitoring and management capabilities. Provide details for the level of support for the features listed below: •o Service level agreement monitoring. •o Enforcement of Service Level Agreements. •o Service management loggings. For example describe how the ESB supports endpoint status, errors, invocations, response time, elapsed time, throughput, and SLA violations. •o Support for vendor of third party service management tools. •o Support for the creation of a single management domain that spans multiple local area network (LAN) and wide-area network (WAN) segments and multiple security domains. •o Support for vendor or third party monitoring tools. Detail third party vendors supported that handle end-to-end service monitoring and management capabilities. •o Supports end to end technical monitoring of all ESB activities, mediations and processes. •o Business activity monitoring (BAM) including vendor or third party support. Describe BAM capabilities that are provided? Do those capabilities support monitoring of systems outside of the ESB itself? •o Ability to provide alerts on error conditions. •o Must be able to drill down to error level details to aide in problem resolution. •o Support for performance monitoring activities for all associated ESB activities. •o Support for alerts. Describe how alerts are supported. For example; drill down to problem resolution, filtering and tracing and email alerts. Quality of Service requirements: •Ø Describe quality service features such as Load Balancing, Fault tolerance, Failover, Transaction Support, Prioritization, etc. Architecture requirements: •Ø Describe support for Federation. •o Homogeneous Federation. Describe how it's the ESB would federate with other instances of itself. Describe specific federation capabilities. •o Heterogeneous Federation. Detail third party ESB products supported as existing federation targets. •Ø Describe support for scalability and availability. •o Describe how the ESB is scalable and highly available. •o Detail throughput scalability. Support for large workloads in a single location. •o Describe geographic scalability. •o Outline features of endpoint quality of service. For example service throttling, temporary traffic shaping, service prioritization, service retry, dynamic routing, and event sequencing of interdependent events. •o Can a registry/repository be used to store operational information to enable dynamic endpoint lookup based on service-level policies? •o Describe the ESB Topology. For example; a distributed or broker topology? Outline the advantages offered by the ESB's particular topology? •Ø Runtime environment. •o Describe operating systems supported by the ESB. •o Describe application servers supported. •o Detail DBMS support. •o Are there specific application servers or DBMS that must in place to run the ESB? •o Outline dynamic provisioning capabilities. •o What is the initial installation memory required by the ESB per server? •o What are typical runtime memory footprints that customers utilize? •o What is the typical disk footprint? •o Describe support for alternative implementations. For example can routing or transformation provided by the vendor be replaced with alternate implementations by SSA? •o Detail reliable messaging features. •o How does the ESB support reliable messaging across firewalls? •Ø Costs •o Detail how the product is priced (by server, by client, by service, enterprise, etc.)? •o What about licenses for development and test environments? •o Are there alternatives for subscription pricing in addition to software licenses? •o Provide details of how subscription pricing compares with license pricing. The solution shall be compliant with Section 508 Electronic and Information Technology (EIT) Accessibility Standards. Interested vendors must provide verifiable proof in sufficient detail to demonstrate their ability to meet the SSA's requirement, see URL site http://www.ssa.gov/oag/acq/oagacq_508.htm. V endors having the capability to meet the above requirements are invited to submit complete details. The responses must clearly state how their product provides the ability to meet the above requirements. Interested parties shall respond to this notice within 7 calendar days from date of this publication. Vendors responding shall indicate whether their services are available on the GSA Federal Supply Schedules. Pricing data may be submitted. This is not a request for proposal and the Government does not intend to pay for information submitted. Respondents will not be notified of the results of the evaluation of the data received. No contract award will be made on the basis of responses received; however, this information will be used in SSA's assessment of capable sources. No Faxed responses. Requests for copies of a solicitation will not be honored or acknowledged. No formal solicitation is being issued at this time. Please submit electronic responses only to the contract specialist identified herein. NOTE: There is a size limit for e-mail: No submission shall be greater than 5 MB. Original Point of Contact Aminta Freeman, Contract Specialist, Email aminta.freeman@ssa.gov
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/SSA/DCFIAM/OAG/SSA-RFI-10-1004/listing.html)
- Place of Performance
- Address: TBD, United States
- Record
- SN02017045-W 20091206/091204235405-dcfc275b037d4b75a493efc5e4db3f97 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |