COBOL アプリケーションにおける意思決定ロジックの保守容易性と可視性の向上
IBM WebSphere ILOG Rule for COBOL により、WebSphere ILOG JRules BRMS ルール・セットを COBOL アプリケーション内部で使用するために COBOL コピーブック・コードに生成することができます。
自動的な意思決定を改善するために、既存の COBOL ベース・アプリケーションに強力なビジネス・ルール管理システム (BRMS) 機能を追加します。WebSphere ILOG JRules BRMS で管理できるように、意思決定ロジックを外部化します。
- 実行可能フォーマットにコンパイルするために、COBOL ソース・コードを WebSphere ILOG JRules BRMS ルール・セットから生成します。
- ルール・フロー、自然言語ルール、デシジョン・テーブル、およびデシジョン・ツリーを取り込む COBOL コピーブックを生成します。
- 技術者ユーザーとビジネス・ユーザーの両方が意思決定ロジックを理解できる、柔軟かつ安全な管理されたシステムでルールを管理します。
- ビジネス・ルールを複数のアプリケーション、システム、およびプロセスで再使用します。
- COBOL アプリケーションを徐々に最新化して総合的な SOA 戦略への移行を迅速化するための方法として、Rules for COBOL および WebSphere ILOG JRules BRMS を活用します。
- サポートされるオペレーティング・システム: Linux、System z
製品について
ご購入 WebSphere ILOG Rules for COBOL
初年度の IBM ソフトウェア・サブスクリプション & サポートは製品価格に含まれています。
ご購入には諸手続きが必要になりますので、弊社窓口までお問い合わせください。
Overview
The WebSphere ILOG business rule management system (BRMS) product line provides a comprehensive set of capabilities that enable Business and IT functions within the organization to work together collaboratively for authoring, maintaining and deploying decision logic that is critical to business systems.
Rules for COBOL is ideal for companies that deploy business rules in COBOL, but want to benefit from the latest BRMS technology. The rules in a COBOL application can be incrementally migrated to a central business rule repository for external management, even directly by business users, and still be executed in COBOL code.
Benefits of Rules for COBOL:
- Makes decision logic easily accessible and re-useable across the organization.
- Rules are stored and managed in a centralized repository, with comprehensive capabilities for querying and reporting on rules and associated metadata.
- Rules can be defined in a customizable business vocabulary using a variety of rule metaphors, including decision tables, text-based rules and rule flows (combining multiple rulesets in a defined execution sequence).
- Tools and environments are designed specifically for the unique needs of different stakeholders involved in rule management—Line of Business personnel, Business Analysts, Systems Developers, and IT Operations.
- Reduces the amount of time, effort and cost required to develop and maintain applications by separating business decision logic from core application code. By managing rules outside of COBOL apps, the code base becomes more stable and less likely to be affected by change.
- Rules can be easily shared across business applications, ensuring consistency in the implementation of business policies across the organization’s applications and systems.
- Provides an initial step in legacy modernization efforts. With Rules for COBOL, rules managed in the BRMS can be generated as COBOL code and inserted directly within the application. Later, the inserted decision logic code can be replaced with a call to the BRMS rule engine, utilizing the exact same rules managed in the BRMS repository and providing a straight-forward transition path.
New Features in Rules for COBOL
The v7.0x releases of Rules for COBOL provide a number of new and improved features:
New optimized code generation for rule flows and decision tables, along with additional methods for handling numeric computations in COBOL copybooks.
Rules for COBOL now supports business object model (BOM) generation and COBOL code to BOM mapping for Level 88 data items. It also supports Java executable object model (XOM) method generation for Level 88 data items, with some limitations.
Rules for COBOL now supports all data types for local variables: primitive, String , Date, Class and Collector type. And references to external files can also be included in the generated COBOL code.
There is a new CICS Usage option which generates a wrapper program to facilitate integration with existing CICS applications.
WebSphere ILOG Rules for COBOL V7.1 improves the ability to define, maintain, and govern decision logic used in COBOL-based applications.
Rules for COBOL generates Enterprise COBOL.
Rules for COBOL now provides reporting of errors incurred during rule authoring and suggestions for resolution of the errors.