• Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,615
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
153
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ILOG BRMS Mainframe Options ILOG, Inc. – Internal Use Only The Rule Solution for the Mainframe
  • 2. Mainframe Integration Options
    • JRules components run in multiple environments on the mainframe
    • Development, execution, and rule management are quasi-independent
    • Execution and management may require RDBMS access, which can be either on or off the mainframe
    • So, any mainframe configuration is to some degree “mix and match.”
    ILOG, Inc . Internal Use Only
  • 3. Mainframe Integration Options
    • Rule Execution Options
      • RES on WebSphere for z/OS
      • RES on WebSphere on z/Linux
      • Rules for COBOL
      • Rule Engine within CICS JVM pool
    • Rule Management Options
      • RTS on WebSphere on z/Linux
      • RTS on WebSphere on Unix or Linux
      • Rule Studio on Linux or Windows
  • 4. ILOG BRMS Mainframe Configuration Examples ILOG, Inc. – Internal Use Only
  • 5. Option: JRules on zOS
    • Description
      • Rule Execution Server (RES) is certified by IBM to execute on the mainframe platform running on WebSphere for zOS.
      • Fully leverages the ILOG BRMS, while running your Java applications with the ILOG JRules rule engine and rule execution server on the mainframe.
      • The RTS Repository has also been tested and certified to run on the mainframe.
      • Communication with the CICS application through MQ Series.
    • Benefits
      • Organizations can continue to harness the power and value of their mainframes for the execution of business applications.
      • Java environment allows more easily scalable architectures (multithreading, multiple concurrent application instances), at a lower cost in system resources
      • High performance, since MQ Series allows direct memory transfer based communication within the same physical machine
      • The Java runtime environment is easy to configure, Java byte code is portable to any Unix system
    ILOG, Inc . Internal Use Only
  • 6. z/OS Execution / Unix management Unix, Linux, Windows Unix ILOG, Inc . Internal Use Only Mainframe zOS / LPAR DB2 for z/Series Rule Repository & Run-time Store CICS Customer Application COBOL, PL/1 or C++ Program WebSphere Rule Team Server WebSphere for z/OS Rule Execution Server JMS/MQ MQ series Deploy Rule Studio Source Code Control JRules Project Synchro
  • 7. Option: JRules on zOS - SOA Strategy ILOG, Inc . Internal Use Only ILOG RES
  • 8. Option: JRules with Rules for COBOL
    • Description
      • Adopted by customers that want to manage the rules separate from COBOL code but want to:
        • Leverage their investment in their COBOL applications and mainframe technology or
        • Phase out their mainframe applications (by subsystem, functionality, state, etc.) Java based rules service resides on an UNIX platform.
    • Benefits
      • Begin externalizing and managing business rules from COBOL code in a short timeframe – does not require entire application program rewrite
      • Use of Company’s COBOL copybooks for generation of BOM
      • Generates COBOL code Sub-Program for execution on mainframe
      • Execute natively using existing program flow (can change flow later, if desired)
      • Use of your companies change management and quality control process
    ILOG, Inc . Internal Use Only
  • 9. Option: JRules and Rules for COBOL Unix, Linux, Windows Unix WebSphere Rule Team Server Upload Rule Studio Source Code Control JRules Project Synchro Mainframe zOS Customer Application Cobol Programs CICS Services Batch Proc. COBOL sub COBOL sub Upload OR