| |
|
| |
|
SOA Business Catalog entry process: Technical criteria
To meet the technical requirements of the IBM SOA Business Catalog, your solution must meet at least one of these technical criteria scenarios.
Product versions listed are the minimum required; you may also use later versions of these products. The options serve as a small set of examples for connecting to the IBM SOA Foundation products.
Scenario 1
The asset provides connectivity to the IBM SOA Foundation products. Possible scenario options include:
-
The services are callable from IBM SOA Foundation products using the connectivity asset. For example, the asset could be:
-
Adapter developed using one of the following:
-
WebSphere Adapter Toolkit
-
ISV JCA 1.5 Adapter
-
ISV JMS connectivity
-
Web services using one of the following transport protocols:
-
SOAP / HTTP
-
SOAP / JMS
-
REST
-
WebSphere MQ connectivity using one of the following protocols or servers:
-
JSR 168 portlets that aggregate or consume services
-
Test cases that are created using Rational Tester for SOA Quality, which validates the reliability of composite business services using the following protocols:
-
SOAP/HTTP
-
REST
-
SOAP/MQ
-
HTTPS
Scenario 2
The assets provide value-add capabilities, features, and functions to enhance the IBM SOA Foundation products and can be leveraged in building composite applications. Possible scenario options include:
-
WebSphere Business Modeler content or extensions, such as:
-
Industry-specific process or data models
-
WebSphere Process Server extensions, such as:
-
Rules engines or rule sets which extend WebSphere Process Server
-
Process component libraries
-
Enterprise Service Bus (ESB) extensions, such as:
-
ESB primitives which extend WebSphere ESB
-
WebSphere Message Broker nodes or message flows which extend WebSphere Message Broker
-
Tools that extend or improve on the SOA development cycle through Eclipse version 3.0 or higher
-
Monitoring or dashboard assets which consume Common Base Events (CBEs) from WebSphere Process Server / Common Event Infrastructure (CEI)
-
Tivoli extensions, such as:
-
Adapters extending Tivoli Access Manager to provide security management for business processes or services
-
Process managers extending Tivoli Change and Configuration Management Database to manage business processes or services infrastructure
-
Discovery library adapters extending Tivoli Change and Configuration Management Database to discover business processes or services infrastructure
-
Configurations extending process managers to provide management of business processes or services infrastructure
-
Rational extensions to enhance SOA development, such as:
-
JSF plug-in to Rational Application Developer for GUI components
-
J2EE tool or Web services plug-ins/extensions for Rational Application Developer
-
SOA processes for Rational Unified Process, packaged as Rational Method Composer plug-ins
-
SOA plug-ins to Rational Software Architect modeling platform for modeling extensions
-
SOA transformations (both model-model and model-code) implemented in the Rational Software Architect transformation framework
-
Pattern or profile for Rational Software Architect plug-ins to enhance SOA development
-
Portal extensions to enhance SOA development, such as:
-
JSF components produced for portal development
-
WebSphere Portlet Factory Designer Builders extension
Scenario 3
Delivers SOA solutions through composite applications, leveraging the exclusive use of core runtime IBM SOA Foundation products and other assets. Possible scenario options include:
-
Composite application that assembles business services for multiple areas of the IBM SOA reference architecture to meet specific business needs of the solution. Composite applications have some combinations of the following basic criteria:
-
Extensive use of the IBM SOA Foundation products
-
Composite business services developed using WebSphere Business Services Fabric and Lotus Domino Designer deployed on Lotus Domino
-
Separate user interface, process, services, and data into distinct encapsulated layers to provide improved flexibility and agility
-
Use services calls to connectivity ESB layer using the protocols and products defined in the criteria for scenarios one or two.
-
Process services and orchestration using WebSphere Process Server and WebSphere Integration Developer
-
Interaction services using WebSphere Portal Server and WebSphere Portlet Factory
-
Information services using IBM Information Server
-
Exclusive use of core runtime IBM SOA Foundation products. A business service must provide either a process service or business application service as defined in the SOA reference architecture with extensive use of at least one of the IBM SOA Foundation products:
-
WebSphere Application Server
-
WebSphere Process Server
-
WebSphere Portal Server
-
WebSphere Message Broker
-
WebSphere Enterprise Service Bus
-
IBM Information Server
-
FileNet P8
-
Lotus Expeditor
-
Assets that provide services other than process and business services as defined in the SOA reference architecture with extensive use of at least one of the IBM SOA Foundation products:
-
Rational Asset Manager
-
Tivoli Provisioning Manager
-
Engage in other assets. Business Partners may submit their asset and describe how their asset may meet these criteria.
|
|
|
|
