DTFAWA-08-R-00007

ATTACHMENT J-3: SWIM Service Container Requirements Compliance Summary

The table contained in this section must be completed and returned by
all Offerors with their Proposals. The table contains the Government's
requirements for the SWIM SC Software, as identified in Section J-2. It
identifies two categories of requirements: must-have requirements and
desirable requirements. Headings inserted into the table indicate which
requirements are in which category.

The Table below must be completed for each product proposed in response
to the SIR. The completed Table must be attached to the Offeror's
Technical and Business Proposal and submitted with it as Appendix A, per
the instructions provided in Section L of the SIR.

## INSTRUCTIONS FOR COMPLETION OF TABLE

**Req #:** Provides the requirement number.

**Requirement Text**: Provides the technical requirement.

**Must/Desirable:** Indicates whether the requirement or a portion of a
requirement is a "must-have" as indicated by "**M**" or "desirable" as
indicated by "**D**".

**Compliance:** In the appropriate column, indicate if your proposed
product is fully compliant or partially compliant with each requirement
by checking the appropriate box. For any requirement for which the
product is partially compliant, provide a roadmap for full compliance
(if available) including dates in the **Comments** column.

**Supporting Information:** In addition to completing the **Compliance**
column, Offerors should provide supporting information as requested. Use
the **Comments** column to provide the requested information. Additional
pages may be attached if necessary, but should be clearly marked to
identify the requirement that the information supports. Note: Appendix A
is not restricted by the page limit required for the Offeror's Proposal.
The Offeror is encouraged to provide explicit examples of configuration
files and/or to cite examples in the product documentation provided with
the proposal, as appropriate. If the example in the product
documentation or configuration file contains multiple items, the Offeror
must indicate which portions apply to the requirement being addressed.

References to "Core Services" refer to IT infrastructure for
implementing Interface Management, Messaging, Security, and Enterprise
Service Management, as described in Section J-2.

+--------------------------+-----+---+---+-------------+---------------+
| **Requirement Text**     | **  | * |   | *           | **Comments**  |
|                          | M-M | * |   | *Supporting |               |
|                          | ust | C |   | Information |               |
|                          | H   | o |   | Requested** |               |
|                          | ave | m |   |             |               |
|                          | ;** | p |   |             |               |
|                          |     | l |   |             |               |
|                          | **D | i |   |             |               |
|                          | -De | a |   |             |               |
|                          | sir | n |   |             |               |
|                          | abl | c |   |             |               |
|                          | e** | e |   |             |               |
|                          |     | * |   |             |               |
|                          |     | * |   |             |               |
+==========================+=====+===+===+=============+===============+
|                          |     | * | * |             |               |
|                          |     | * | * |             |               |
|                          |     | F | P |             |               |
|                          |     | u | a |             |               |
|                          |     | l | r |             |               |
|                          |     | l | t |             |               |
|                          |     | * | i |             |               |
|                          |     | * | a |             |               |
|                          |     |   | l |             |               |
|                          |     |   | * |             |               |
|                          |     |   | * |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Portability**          |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  The Service          |     |   |   |             |               |
|     Container (SC) shall |     |   |   |             |               |
|     operate on           |     |   |   |             |               |
|     heterogeneous        |     |   |   |             |               |
|     software platforms,  |     |   |   |             |               |
|     including the        |     |   |   |             |               |
|     following:           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  on J2EE: servlet     | M   |   |   |             |               |
|     2.x, EJB 2.x and 3   |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  on JVM: J2SE 1.4,    | M   |   |   |             |               |
|     J2SE 1.5, J2SE 1.6   |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  on .NET              | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  The SC shall support |     |   |   | Please      |               |
|     hosting of           |     |   |   | provide a   |               |
|     applications written |     |   |   | list of all |               |
|     in the following     |     |   |   | supported   |               |
|     languages:           |     |   |   | languages.  |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  Java                 | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  C#                   | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  C++                  | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 4.  Other                | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  The SC shall be      |     |   |   |             |               |
|     capable of the       |     |   |   |             |               |
|     following:           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  being deployed       | M   |   |   |             |               |
|     within application   |     |   |   |             |               |
|     components           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  being deployed       | M   |   |   |             |               |
|     within stand-alone   |     |   |   |             |               |
|     applications         |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  being deployed       | M   |   |   |             |               |
|     within heavyweight   |     |   |   |             |               |
|     application servers  |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 4.  being deployed       | D   |   |   |             |               |
|     within application   |     |   |   |             |               |
|     appliances           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 4.  The SC shall provide | D   |   |   |             |               |
|     a non-invasive       |     |   |   |             |               |
|     Application Program  |     |   |   |             |               |
|     Interface (API).\    |     |   |   |             |               |
|     \                    |     |   |   |             |               |
|     Note: Non-invasive   |     |   |   |             |               |
|     means the ability to |     |   |   |             |               |
|     make configuration   |     |   |   |             |               |
|     modifications or to  |     |   |   |             |               |
|     extend functionality |     |   |   |             |               |
|     with no additional   |     |   |   |             |               |
|     coding required for  |     |   |   |             |               |
|     connectivity to the  |     |   |   |             |               |
|     supporting           |     |   |   |             |               |
|     infrastructure.      |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 5.  The SC shall operate |     |   |   | Please      |               |
|     on the following     |     |   |   | provide     |               |
|     Operating Systems    |     |   |   | alternative |               |
|     (OS):                |     |   |   | strategies  |               |
|                          |     |   |   | for all     |               |
|                          |     |   |   | unsatisfied |               |
|                          |     |   |   | or          |               |
|                          |     |   |   | partially   |               |
|                          |     |   |   | satisfied   |               |
|                          |     |   |   | r           |               |
|                          |     |   |   | equirements |               |
|                          |     |   |   | (e.g.,      |               |
|                          |     |   |   | proxy,      |               |
|                          |     |   |   | gateway,    |               |
|                          |     |   |   | etc.).\     |               |
|                          |     |   |   | \           |               |
|                          |     |   |   | Other:      |               |
|                          |     |   |   | Please      |               |
|                          |     |   |   | provide a   |               |
|                          |     |   |   | list and    |               |
|                          |     |   |   | version     |               |
|                          |     |   |   | number for  |               |
|                          |     |   |   | any         |               |
|                          |     |   |   | additional  |               |
|                          |     |   |   | OS          |               |
|                          |     |   |   | supported.  |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  Red Hat Linux        | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  IBM AIX              | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  Sun Solaris          | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 4.  Windows 2K3 Server   | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 5.  Other                | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 6.  The SC shall not     | D   |   |   |             |               |
|     require proprietary  |     |   |   |             |               |
|     APIs when            |     |   |   |             |               |
|     interacting with     |     |   |   |             |               |
|     internal components  |     |   |   |             |               |
|     for integration or   |     |   |   |             |               |
|     extension of         |     |   |   |             |               |
|     existing             |     |   |   |             |               |
|     capabilities.\       |     |   |   |             |               |
|     \                    |     |   |   |             |               |
|     Note: Partial        |     |   |   |             |               |
|     support of the Java  |     |   |   |             |               |
|     Business Integration |     |   |   |             |               |
|     (JBI) specification  |     |   |   |             |               |
|     for binding          |     |   |   |             |               |
|     components is an     |     |   |   |             |               |
|     example of internal  |     |   |   |             |               |
|     standards based APIs |     |   |   |             |               |
|     for extension. The   |     |   |   |             |               |
|     JBI Normalized       |     |   |   |             |               |
|     Message Router (NMR) |     |   |   |             |               |
|     is not required.     |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 7.  The SC shall support | M   |   |   |             |               |
|     business logic,      |     |   |   |             |               |
|     implemented as a     |     |   |   |             |               |
|     simple class/object  |     |   |   |             |               |
|     (.NET, Java, C++,    |     |   |   |             |               |
|     C#), to assure loose |     |   |   |             |               |
|     coupling of the      |     |   |   |             |               |
|     business service     |     |   |   |             |               |
|     from the IT          |     |   |   |             |               |
|     infrastructure.      |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Flexibility**          |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 8.  The SC shall be      | M   |   |   | Provide     |               |
|     lightweight with     |     |   |   | supporting  |               |
|     respect to CPU, RAM, |     |   |   | benchmarks  |               |
|     and bandwidth        |     |   |   | for SCs     |               |
|     requirements. For    |     |   |   | running on  |               |
|     example, it must run |     |   |   | each        |               |
|     within any of the    |     |   |   | supported   |               |
|     specified deployment |     |   |   | SW platform |               |
|     options in           |     |   |   | specified   |               |
|     Requirement 3,       |     |   |   | in          |               |
|     above, without       |     |   |   | Requirement |               |
|     increasing the       |     |   |   | 1.          |               |
|     endpoint server CPU, |     |   |   |             |               |
|     RAM, and bandwidth   |     |   |   |             |               |
|     requirements by more |     |   |   |             |               |
|     than 10%.            |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Distributed**          |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 9.  The SC shall provide | M   |   |   |             |               |
|     a highly distributed |     |   |   |             |               |
|     service              |     |   |   |             |               |
|     infrastructure       |     |   |   |             |               |
|     across both          |     |   |   |             |               |
|     geography and        |     |   |   |             |               |
|     network topology.    |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 10. The SC shall be      | M   |   |   |             |               |
|     capable of being     |     |   |   |             |               |
|     deployed as a        |     |   |   |             |               |
|     managed proxy on a   |     |   |   |             |               |
|     server separate from |     |   |   |             |               |
|     the endpoint         |     |   |   |             |               |
|     implementation       |     |   |   |             |               |
|     server.              |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Pervasive**            |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 11. The SC shall         | M   |   |   |             |               |
|     directly enable      |     |   |   |             |               |
|     service endpoints at |     |   |   |             |               |
|     the point of         |     |   |   |             |               |
|     implementation by    |     |   |   |             |               |
|     supporting           |     |   |   |             |               |
|     distribution to      |     |   |   |             |               |
|     every node that      |     |   |   |             |               |
|     hosts one or more    |     |   |   |             |               |
|     endpoints throughout |     |   |   |             |               |
|     the enterprise.      |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Policy-centric**       |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 12. The SC shall have    | M   |   |   |             |               |
|     the ability for each |     |   |   |             |               |
|     SC instance to       |     |   |   |             |               |
|     enforce enterprise   |     |   |   |             |               |
|     policies at          |     |   |   |             |               |
|     endpoints.           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Modularity**           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 13. The SC shall be      |     |   |   |             |               |
|     modular in order to  |     |   |   |             |               |
|     allow selective      |     |   |   |             |               |
|     deployment of the    |     |   |   |             |               |
|     following Core       |     |   |   |             |               |
|     Services:            |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  Messaging: JMS v1.x, | M   |   |   |             |               |
|     HTTP, ftp, SOAP      |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  Connectivity: JCA    | M   |   |   |             |               |
|     v1.x,                |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  Enterprise Service   | M   |   |   |             |               |
|     Management (ESM):    |     |   |   |             |               |
|     JMX v1.2             |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 4.  Security: HTTP/S 1 & | D   |   |   |             |               |
|     1.1, TLS 1.0, PKCS   |     |   |   |             |               |
|     #1, #5, #7, #10,     |     |   |   |             |               |
|     #12, PKIX IETF RFC   |     |   |   |             |               |
|     2459, SSL 3.0, SAML  |     |   |   |             |               |
|     1.0 & 1.1, X.509,    |     |   |   |             |               |
|     Kerberos 5.0, LDAP   |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 5.  Registry: UDDI v3    | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 6.  WSDL v1.1            | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Scalability**          |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 14. The SC shall not     | M   |   |   |             |               |
|     prevent server       |     |   |   |             |               |
|     clustering.          |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Security**             |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 15. The SC shall enable  | M   |   |   |             |               |
|     integration with the |     |   |   |             |               |
|     security framework   |     |   |   |             |               |
|     of the software      |     |   |   |             |               |
|     platform (reference  |     |   |   |             |               |
|     Requirement 3,       |     |   |   |             |               |
|     above) on which it   |     |   |   |             |               |
|     is running.          |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 16. The SC shall provide | M   |   |   |             |               |
|     role-based access    |     |   |   |             |               |
|     control (RBAC)       |     |   |   |             |               |
|     enforcement at the   |     |   |   |             |               |
|     endpoint level, at   |     |   |   |             |               |
|     the operational      |     |   |   |             |               |
|     level, and at the    |     |   |   |             |               |
|     message level.       |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 17. The SC shall support |     |   |   |             |               |
|     message level        |     |   |   |             |               |
|     security in          |     |   |   |             |               |
|     accordance with the  |     |   |   |             |               |
|     following standards: |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  OASIS WS-Security    | D   |   |   |             |               |
|     1.1                  |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  W3C XML Signature    | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  W3C XML Encryption   | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 4.  OASIS Security       | D   |   |   |             |               |
|     Assertion Markup     |     |   |   |             |               |
|     Language (SAML)      |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 5.  Secure Sockets Layer | D   |   |   |             |               |
|     v3 (SSLv3)           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 6.  IETF RFC 2246        | D   |   |   |             |               |
|     Transport Layer      |     |   |   |             |               |
|     Security v1 (TLSv1)  |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 7.  WS-I Basic Security  | D   |   |   |             |               |
|     Profile version 1.1  |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 8.  OASIS Extensible     | D   |   |   |             |               |
|     Access control       |     |   |   |             |               |
|     Markup Language      |     |   |   |             |               |
|     (XACML)              |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 18. The SC shall support |     |   |   |             |               |
|     the following        |     |   |   |             |               |
|     transport level      |     |   |   |             |               |
|     security:            |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  RFC 2818: HTTP over  | D   |   |   |             |               |
|     TLS                  |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  RFC 2246: The TLS    | D   |   |   |             |               |
|     protocol Version 1.0 |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  The SSL Protocol     | D   |   |   |             |               |
|     Version 3.0          |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Manageability**        |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 19. The SC shall be      |     |   |   | If "others" |               |
|     capable of           |     |   |   | is          |               |
|     integrating with     |     |   |   | selected,   |               |
|     runtime Enterprise   |     |   |   | identify    |               |
|     Service Management   |     |   |   | them in the |               |
|     tools for monitor    |     |   |   | Comments    |               |
|     and control,         |     |   |   | column.     |               |
|     including the        |     |   |   |             |               |
|     following:           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  Tivoli               | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  HP Openview          | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  Amberpoint,          | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 4.  Actional             | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 5.  SOA Operations       | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 6.  Others               | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 20. The SC shall support | M   |   |   |             |               |
|     JMX 1.2 for java     |     |   |   |             |               |
|     endpoints mechanism  |     |   |   |             |               |
|     for providing        |     |   |   |             |               |
|     Enterprise Service   |     |   |   |             |               |
|     Management (ESM)     |     |   |   |             |               |
|     capabilities.        |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 21. The SC shall support | D   |   |   | Please      |               |
|     the simple network   |     |   |   | provide the |               |
|     management protocol  |     |   |   | version of  |               |
|     (SNMP).              |     |   |   | SNMP        |               |
|                          |     |   |   | supported.  |               |
+--------------------------+-----+---+---+-------------+---------------+
| 22. The SC shall provide | D   |   |   |             |               |
|     the capability to    |     |   |   |             |               |
|     manage multiple      |     |   |   |             |               |
|     Business service     |     |   |   |             |               |
|     versions.            |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 23. The SC shall         | D   |   |   |             |               |
|     distinguish between  |     |   |   |             |               |
|     exception types and  |     |   |   |             |               |
|     provide the means    |     |   |   |             |               |
|     for applying         |     |   |   |             |               |
|     exception handling   |     |   |   |             |               |
|     actions.             |     |   |   |             |               |
|                          |     |   |   |             |               |
| Note: Exception handling |     |   |   |             |               |
| actions include route,   |     |   |   |             |               |
| log, and process.        |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Monitoring**           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 24. The SC shall expose  | M   |   |   |             |               |
|     information          |     |   |   |             |               |
|     necessary for        |     |   |   |             |               |
|     calculating Quality  |     |   |   |             |               |
|     of Service (QoS)     |     |   |   |             |               |
|     metrics for assuring |     |   |   |             |               |
|     Service Level        |     |   |   |             |               |
|     Agreement (SLA)      |     |   |   |             |               |
|     compliance.\         |     |   |   |             |               |
|     \                    |     |   |   |             |               |
|     Note: Exposing       |     |   |   |             |               |
|     information does not |     |   |   |             |               |
|     include aggregation  |     |   |   |             |               |
|     of data or           |     |   |   |             |               |
|     calculations         |     |   |   |             |               |
|     necessary for SLA    |     |   |   |             |               |
|     compliance           |     |   |   |             |               |
|     assessment.          |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 25. The SC shall provide |     |   |   |             |               |
|     information to       |     |   |   |             |               |
|     monitor the load on  |     |   |   |             |               |
|     the service provider |     |   |   |             |               |
|     for SLA reporting    |     |   |   |             |               |
|     purposes.            |     |   |   |             |               |
|     Specifically, the SC |     |   |   |             |               |
|     shall be able to     |     |   |   |             |               |
|     measure the          |     |   |   |             |               |
|     following:           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  number of consumers  | M   |   |   |             |               |
|     on an individual     |     |   |   |             |               |
|     endpoint             |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  number of messages   | M   |   |   |             |               |
|     (inbound/outbound)   |     |   |   |             |               |
|     on an individual     |     |   |   |             |               |
|     endpoint             |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  Response time (not   | M   |   |   |             |               |
|     end-to-end, but      |     |   |   |             |               |
|     service execution    |     |   |   |             |               |
|     time, only).         |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Control**              |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 26. The SC shall         |     |   |   |             |               |
|     accommodate          |     |   |   |             |               |
|     implementation of    |     |   |   |             |               |
|     QoS through control  |     |   |   |             |               |
|     of endpoint policies |     |   |   |             |               |
|     for:                 |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  Security policy      | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  Transport Policy     | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  Business Policy      | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 27. The SC shall provide | D   |   |   |             |               |
|     throttling as a      |     |   |   |             |               |
|     means to control the |     |   |   |             |               |
|     load on services     |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Federation**           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 28. The SC shall         | M   |   |   |             |               |
|     encapsulate IT       |     |   |   |             |               |
|     infrastructure to    |     |   |   |             |               |
|     enable an            |     |   |   |             |               |
|     integrated,          |     |   |   |             |               |
|     federated, and       |     |   |   |             |               |
|     consistent           |     |   |   |             |               |
|     environment for      |     |   |   |             |               |
|     messaging, security  |     |   |   |             |               |
|     and enterprise       |     |   |   |             |               |
|     management.          |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Integration**          |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 29. The SC shall enable  | M   |   |   |             |               |
|     event driven         |     |   |   |             |               |
|     integration in order |     |   |   |             |               |
|     to minimize coupling |     |   |   |             |               |
|     between Systems and  |     |   |   |             |               |
|     Software components. |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 30. Users shall be able  | M   |   |   |             |               |
|     to implement RESTful |     |   |   |             |               |
|     web service          |     |   |   |             |               |
|     architectures with   |     |   |   |             |               |
|     the SC.              |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 31. The SC shall be      | D   |   |   | Please      |               |
|     capable of hosting   |     |   |   | provide a   |               |
|     long running         |     |   |   | sample      |               |
|     business process     |     |   |   | co          |               |
|     orchestration        |     |   |   | nfiguration |               |
|     including batch      |     |   |   | file or     |               |
|     processes.\          |     |   |   | reference   |               |
|     \                    |     |   |   | existing    |               |
|     Note: A long running |     |   |   | do          |               |
|     business process is  |     |   |   | cumentation |               |
|     any process that may |     |   |   | for the     |               |
|     have an indefinite   |     |   |   | co          |               |
|     delay because of     |     |   |   | nfiguration |               |
|     external             |     |   |   | submitted   |               |
|     dependencies.        |     |   |   | with this   |               |
|                          |     |   |   | package     |               |
|                          |     |   |   | which       |               |
|                          |     |   |   | explicitly  |               |
|                          |     |   |   | provides    |               |
|                          |     |   |   | examples    |               |
|                          |     |   |   | i           |               |
|                          |     |   |   | llustrating |               |
|                          |     |   |   | this        |               |
|                          |     |   |   | capability. |               |
+--------------------------+-----+---+---+-------------+---------------+
| 32. The SC shall provide | D   |   |   | Please      |               |
|     enterprise           |     |   |   | provide a   |               |
|     integration patterns |     |   |   | list of the |               |
|     (Hohpe) for building |     |   |   | supported   |               |
|     services from SW     |     |   |   | integration |               |
|     components and other |     |   |   | patterns.   |               |
|     services.            |     |   |   |             |               |
|                          |     |   |   |             |               |
| Refer to                 |     |   |   |             |               |
| <http://w                |     |   |   |             |               |
| ww.enterpriseintegration |     |   |   |             |               |
| patterns.com/index.html> |     |   |   |             |               |
| for additional           |     |   |   |             |               |
| information on the       |     |   |   |             |               |
| integration patterns.    |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 33. Web services         | M   |   |   |             |               |
|     implemented with the |     |   |   |             |               |
|     SC shall be          |     |   |   |             |               |
|     compliant with the   |     |   |   |             |               |
|     WS-I Basic Profile   |     |   |   |             |               |
|     1.2.                 |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **SOA Orchestration**    |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 34. The SC shall support | D   |   |   |             |               |
|     Business Process     |     |   |   |             |               |
|     Execution Language   |     |   |   |             |               |
|     (BPEL) for service   |     |   |   |             |               |
|     level orchestration. |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Invocation**           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 35. The SC shall         | M   |   |   |             |               |
|     encapsulate how a    |     |   |   |             |               |
|     consumer binds to    |     |   |   |             |               |
|     the service endpoint |     |   |   |             |               |
|     to enable location   |     |   |   |             |               |
|     independent service  |     |   |   |             |               |
|     invocation           |     |   |   |             |               |
|     (discovery and       |     |   |   |             |               |
|     binding to other     |     |   |   |             |               |
|     services).           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 36. The SC shall be      | M   |   |   |             |               |
|     compatible with the  |     |   |   |             |               |
|     WS-Addressing        |     |   |   |             |               |
|     Specification.       |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 37. The SC shall perform | M   |   |   |             |               |
|     conversion between   |     |   |   |             |               |
|     synchronous and      |     |   |   |             |               |
|     asynchronous         |     |   |   |             |               |
|     invocations.         |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Decoupling**           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 38. The SC shall         | M   |   |   | Please      |               |
|     encapsulate the      |     |   |   | provide a   |               |
|     supporting           |     |   |   | sample      |               |
|     enterprise IT        |     |   |   | co          |               |
|     infrastructure       |     |   |   | nfiguration |               |
|     making the IT        |     |   |   | file or     |               |
|     infrastructure       |     |   |   | reference   |               |
|     pluggable, to        |     |   |   | existing    |               |
|     support decoupling   |     |   |   | do          |               |
|     of ATM services from |     |   |   | cumentation |               |
|     Core Services.       |     |   |   | for the     |               |
|                          |     |   |   | co          |               |
|                          |     |   |   | nfiguration |               |
|                          |     |   |   | submitted   |               |
|                          |     |   |   | with this   |               |
|                          |     |   |   | package     |               |
|                          |     |   |   | which       |               |
|                          |     |   |   | explicitly  |               |
|                          |     |   |   | provides    |               |
|                          |     |   |   | examples    |               |
|                          |     |   |   | i           |               |
|                          |     |   |   | llustrating |               |
|                          |     |   |   | en          |               |
|                          |     |   |   | capsulation |               |
|                          |     |   |   | with        |               |
|                          |     |   |   | different   |               |
|                          |     |   |   | supporting  |               |
|                          |     |   |   | IT          |               |
|                          |     |   |   | inf         |               |
|                          |     |   |   | rastructure |               |
|                          |     |   |   | components. |               |
+--------------------------+-----+---+---+-------------+---------------+
| 39. The SC shall         | M   |   |   | Please      |               |
|     encapsulate the IT   |     |   |   | provide a   |               |
|     technologies within  |     |   |   | sample      |               |
|     the IT               |     |   |   | co          |               |
|     infrastructure to    |     |   |   | nfiguration |               |
|     support modularity   |     |   |   | file or     |               |
|     of IT infrastructure |     |   |   | reference   |               |
|     technology.          |     |   |   | existing    |               |
|                          |     |   |   | do          |               |
|                          |     |   |   | cumentation |               |
|                          |     |   |   | for the     |               |
|                          |     |   |   | co          |               |
|                          |     |   |   | nfiguration |               |
|                          |     |   |   | submitted   |               |
|                          |     |   |   | with this   |               |
|                          |     |   |   | package     |               |
|                          |     |   |   | which       |               |
|                          |     |   |   | explicitly  |               |
|                          |     |   |   | provides    |               |
|                          |     |   |   | examples    |               |
|                          |     |   |   | i           |               |
|                          |     |   |   | llustrating |               |
|                          |     |   |   | en          |               |
|                          |     |   |   | capsulation |               |
|                          |     |   |   | with        |               |
|                          |     |   |   | different   |               |
|                          |     |   |   | supporting  |               |
|                          |     |   |   | IT          |               |
|                          |     |   |   | inf         |               |
|                          |     |   |   | rastructure |               |
|                          |     |   |   | components  |               |
|                          |     |   |   | (e.g.,      |               |
|                          |     |   |   | different   |               |
|                          |     |   |   | LDAP        |               |
|                          |     |   |   | providers,  |               |
|                          |     |   |   | JMS         |               |
|                          |     |   |   | providers). |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Transformation**       |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 40. The SC shall support | M   |   |   |             |               |
|     transformation of    |     |   |   |             |               |
|     one message format   |     |   |   |             |               |
|     to another message   |     |   |   |             |               |
|     format (e.g., data   |     |   |   |             |               |
|     mapper or            |     |   |   |             |               |
|     transformation) for  |     |   |   |             |               |
|     the purpose of       |     |   |   |             |               |
|     providing data       |     |   |   |             |               |
|     mediation.           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Virtualization**       |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 41. The SC shall         | M   |   |   |             |               |
|     encapsulate concerns |     |   |   |             |               |
|     regarding location,  |     |   |   |             |               |
|     versioning,          |     |   |   |             |               |
|     configuration        |     |   |   |             |               |
|     management,          |     |   |   |             |               |
|     deployment,          |     |   |   |             |               |
|     configuration and    |     |   |   |             |               |
|     availability of      |     |   |   |             |               |
|     services.            |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Availability**         |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 42. The SC shall enable  | D   |   |   | Please      |               |
|     active failover to a |     |   |   | provide a   |               |
|     different service    |     |   |   | sample      |               |
|     endpoint             |     |   |   | co          |               |
|     implementation.\     |     |   |   | nfiguration |               |
|     \                    |     |   |   | file or     |               |
|     Note: This means     |     |   |   | reference   |               |
|     that a failed        |     |   |   | existing    |               |
|     service invocation   |     |   |   | do          |               |
|     can automatically    |     |   |   | cumentation |               |
|     invoke another       |     |   |   | for the     |               |
|     endpoint instance of |     |   |   | co          |               |
|     the same service to  |     |   |   | nfiguration |               |
|     satisfy the request. |     |   |   | submitted   |               |
|                          |     |   |   | with this   |               |
|                          |     |   |   | package     |               |
|                          |     |   |   | that        |               |
|                          |     |   |   | explicitly  |               |
|                          |     |   |   | provides    |               |
|                          |     |   |   | examples    |               |
|                          |     |   |   | i           |               |
|                          |     |   |   | llustrating |               |
|                          |     |   |   | this        |               |
|                          |     |   |   | capability. |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Messaging**            |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 43. Web services         | M   |   |   |             |               |
|     implemented with the |     |   |   |             |               |
|     SC shall be capable  |     |   |   |             |               |
|     of complying with    |     |   |   |             |               |
|     the SOAP 1.1         |     |   |   |             |               |
|     standard.            |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Transport**            |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 44. The SC shall have    | M   |   |   |             |               |
|     the ability to route |     |   |   |             |               |
|     messages between     |     |   |   |             |               |
|     each SC instance.    |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 45. The SC shall support |     |   |   | Please      |               |
|     multiple application |     |   |   | provide a   |               |
|     transport protocols  |     |   |   | sample      |               |
|     declaratively.\      |     |   |   | co          |               |
|     \                    |     |   |   | nfiguration |               |
|     Note: Support means  |     |   |   | file or     |               |
|     that a service       |     |   |   | reference   |               |
|     implemented with the |     |   |   | existing    |               |
|     SC will be able to   |     |   |   | do          |               |
|     accept requests on   |     |   |   | cumentation |               |
|     any supported        |     |   |   | for the     |               |
|     protocol.            |     |   |   | co          |               |
|                          |     |   |   | nfiguration |               |
|                          |     |   |   | submitted   |               |
|                          |     |   |   | with this   |               |
|                          |     |   |   | package     |               |
|                          |     |   |   | that        |               |
|                          |     |   |   | explicitly  |               |
|                          |     |   |   | provides    |               |
|                          |     |   |   | examples    |               |
|                          |     |   |   | i           |               |
|                          |     |   |   | llustrating |               |
|                          |     |   |   | multiple    |               |
|                          |     |   |   | transport   |               |
|                          |     |   |   | support.    |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  PoX/HTTP(S)          | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  PoX/JMS              | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  SOAP/HTTP(S)         | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 4.  SOAP/JMS             | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 5.  ftp                  | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 6.  RMI (for java        | D   |   |   |             |               |
|     endpoints)           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 7.  IIOP                 | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 46. The SC shall support | M   |   |   | Please      |               |
|     application          |     |   |   | provide     |               |
|     transport extension  |     |   |   | extension   |               |
|     and customization.\  |     |   |   | API         |               |
|     \                    |     |   |   | doc         |               |
|     Note: The goal is to |     |   |   | umentation. |               |
|     be able to add new   |     |   |   |             |               |
|     protocols as they    |     |   |   |             |               |
|     emerge, or to add    |     |   |   |             |               |
|     standardized         |     |   |   |             |               |
|     features for how     |     |   |   |             |               |
|     supported protocols  |     |   |   |             |               |
|     are handled.         |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 47. The SC shall provide | M   |   |   | Please      |               |
|     transport conversion |     |   |   | provide a   |               |
|     between supported    |     |   |   | sample      |               |
|     protocols            |     |   |   | co          |               |
|     declaratively; e.g., |     |   |   | nfiguration |               |
|     SOAP/HTTP to         |     |   |   | file or     |               |
|     SOAP/JMS.\           |     |   |   | reference   |               |
|     \                    |     |   |   | existing    |               |
|     Note: WS-Addressing  |     |   |   | do          |               |
|     to be used for       |     |   |   | cumentation |               |
|     different transports |     |   |   | for         |               |
|     for request and      |     |   |   | co          |               |
|     reply.               |     |   |   | nfiguration |               |
|                          |     |   |   | submitted   |               |
|                          |     |   |   | with this   |               |
|                          |     |   |   | package     |               |
|                          |     |   |   | which       |               |
|                          |     |   |   | explicitly  |               |
|                          |     |   |   | provide     |               |
|                          |     |   |   | examples    |               |
|                          |     |   |   | i           |               |
|                          |     |   |   | llustrating |               |
|                          |     |   |   | transport   |               |
|                          |     |   |   | conversion. |               |
+--------------------------+-----+---+---+-------------+---------------+
| 48. The SC shall be able |     |   |   |             |               |
|     to use multiple      |     |   |   |             |               |
|     message-oriented     |     |   |   |             |               |
|     middleware for       |     |   |   |             |               |
|     transport, including |     |   |   |             |               |
|     the following:\      |     |   |   |             |               |
|     \                    |     |   |   |             |               |
|     Note: This is use of |     |   |   |             |               |
|     the middleware by    |     |   |   |             |               |
|     the SC for external  |     |   |   |             |               |
|     transport to another |     |   |   |             |               |
|     endpoint.            |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  IBM MQ               | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  ActiveMQ             | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  JMS                  | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 49. The SC shall support | D   |   |   |             |               |
|     WS-Reliable          |     |   |   |             |               |
|     Messaging over       |     |   |   |             |               |
|     SOAP/HTTP.           |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 50. The SC shall work    | M   |   |   |             |               |
|     with push/pull,      |     |   |   |             |               |
|     pub/sub,             |     |   |   |             |               |
|     request/reply, and   |     |   |   |             |               |
|     synchronous          |     |   |   |             |               |
|     /asynchronous        |     |   |   |             |               |
|     invocation styles.   |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 51. The SC shall provide | D   |   |   | Please      |               |
|     a library of         |     |   |   | provide a   |               |
|     technology adapters, |     |   |   | list of     |               |
|     including the        |     |   |   | supported   |               |
|     following:           |     |   |   | adapters.   |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  CORBA                | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  Other                | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 52. The SC shall support | D   |   |   |             |               |
|     WS-Notification.     |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 53. The SC shall support | M   |   |   |             |               |
|     at least one of the  | for |   |   |             |               |
|     following two SOAP   | the |   |   |             |               |
|     message attachment   | fir |   |   |             |               |
|     protocols:           | st, |   |   |             |               |
|                          | D   |   |   |             |               |
|     1.  either Message   | for |   |   |             |               |
|         Transmission     | the |   |   |             |               |
|         Optimization     | sec |   |   |             |               |
|         Mechanism        | ond |   |   |             |               |
|         (MTOM), or       |     |   |   |             |               |
|                          |     |   |   |             |               |
|     2.  SOAP with        |     |   |   |             |               |
|         Attachments.     |     |   |   |             |               |
|                          |     |   |   |             |               |
| > Note: Either MTOM or   |     |   |   |             |               |
| > SOAP with Attachments  |     |   |   |             |               |
| > is required. If either |     |   |   |             |               |
| > one is supported, then |     |   |   |             |               |
| > the other is only      |     |   |   |             |               |
| > desired.               |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 54. The SC shall provide | M   |   |   |             |               |
|     support for content  |     |   |   |             |               |
|     based routing.       |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| **Integrated Development |     |   |   |             |               |
| Environment (IDE)**      |     |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 55. SC development       |     |   |   | If "others" |               |
|     components shall     |     |   |   | is          |               |
|     integrate with other |     |   |   | selected,   |               |
|     IDEs, including:     |     |   |   | identify    |               |
|                          |     |   |   | them in the |               |
|                          |     |   |   | Comments    |               |
|                          |     |   |   | column.     |               |
+--------------------------+-----+---+---+-------------+---------------+
| 1.  Eclipse              | M   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 2.  JDeveloper           | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+
| 3.  Others               | D   |   |   |             |               |
+--------------------------+-----+---+---+-------------+---------------+