Unlike middleware running on traditional application environments, there is no one specific role that one can affix to DataPower. DataPower defies generic labeling. The reasons for this are:
Hardened security: It can act purely as a security gateway.
Appliance versatility: It is easy to add to the the network at various points to perform different functions.
XML lingua franca: The promise of XML-speak is uniformity, simplicity, and transparency of handling data. Being XML-centric from
core upwards gives DataPower the ability to adapt to different roles.
Any-to-any transformation: The ability to transform any data format allows it to be an integration device.
Multi-protocol support: This allows it to be a integration device or bridge for heritage applications.
All the above are bolstered by the ease-of-use factor. Consumability is a core competence of DataPower. DataPower is consumable at different levels:
Installation: As a network appliance it can be up and running in literally a few minutes.
Development cycle: On-board Web GUI based approach to creating and managing applications gets rid of the develop-deploy
round trip development methodology.
Development model: The modeling uses the building-block approach where the application is built using a collection of objects one on top of another. The granularity of these objects maps comfortably to architectural components of typical applications.
All the above enable WebSphere DataPower SOA Appliances to be used in a variety of ways, depending on the task at hand.
For Online Training on Websphere Datapower mail us at [email protected]
Hardened security: It can act purely as a security gateway.
Appliance versatility: It is easy to add to the the network at various points to perform different functions.
XML lingua franca: The promise of XML-speak is uniformity, simplicity, and transparency of handling data. Being XML-centric from
core upwards gives DataPower the ability to adapt to different roles.
Any-to-any transformation: The ability to transform any data format allows it to be an integration device.
Multi-protocol support: This allows it to be a integration device or bridge for heritage applications.
All the above are bolstered by the ease-of-use factor. Consumability is a core competence of DataPower. DataPower is consumable at different levels:
Installation: As a network appliance it can be up and running in literally a few minutes.
Development cycle: On-board Web GUI based approach to creating and managing applications gets rid of the develop-deploy
round trip development methodology.
Development model: The modeling uses the building-block approach where the application is built using a collection of objects one on top of another. The granularity of these objects maps comfortably to architectural components of typical applications.
All the above enable WebSphere DataPower SOA Appliances to be used in a variety of ways, depending on the task at hand.
For Online Training on Websphere Datapower mail us at [email protected]
RSS Feed
