IBM Services Assets for WebSphere Software are extensions to the IBM product portfolio, built by IBM Software Services for WebSphere. Based on real-world client engagements and requirements, these assets enhance the user experience working with WebSphere products by providing patterns, utilities, best practices, automation, and integration artifacts to improve the quality and delivery of your projects
IBM Services Assets are continually developed and enhanced through an agile process based on feedback from clients and consultants. Some IBM Services Assets are available via direct download, others are available in conjunction with services engagements. Either way, IBM Software Services for WebSphere can help you quickly optimize each asset with services that are tailored to your requirements.
Typical services provided with IBM Services Assets include:
- Services Asset Workshop
We help you determine how the pattern can improve your solution and estimate the scope and complexity of the implementation.
- Services Asset Implementation
An IBM Specialist/Architect performs on-site implementation of the asset and mentors the client team.
- Services Asset Strategy and Planning
For large implementations across the organization, we help determine the strategy and planning for implementing the asset, taking into account project life cycles, environments, migration, integration, and so on.
- Services Asset Extensibility
We can help evaluate and implement features and extensions to the asset that will further enhance your solution.
IBM Services Assets for WebSphere Software available now:
The Dynamic Forms (DYNF) services asset uses IBM Operational Decision Manager to define forms and change their status with rules. It also provides a default web application to render forms and interacts with IBM Operational Decision Manager. Dynamic Forms enables business users to manage forms on their own with minimal IT support, brings agility to forms, and enables a system to adapt quickly to changing business needs.
Enterprise Exception Handler
The Enterprise Exception Handling (EEH) pattern provides a standardized method of reporting exceptions in the organization through the Enterprise Service Bus (ESB) that may be analyzed in the future. Most application and system exceptions are reported in an inconsistent manner and often reported in logs that are distributed across every node in the subsystem. The pattern addresses this concern by standardization and centralization of system-wide exceptions in a heterogeneous environment.