IBM Cúram 7.X Certification Important Notes

DHARMEDRA SAHU

Introduction

This tutorial contains important points which will help to understand the basic Cúram knowledge. These points are very significant and help to prepare for the certification exam.
Please find the points in below section –

This diagram (given in ppt) provides a holistic narrative of the IBM Cúram approach to SPM. The narrative begins with the following questions:
1. Who is in need?
2. What are their needs?
3. Who can help?
4. How to achieve sustainable outcomes?

 

The two “tiers” of IBM Cúram Social Program Management (SPM) are as follows

  • IBM Cúram Application Modules
  • IBM Cúram Social Program Management Platform (SPMP).

The SPM platform houses the foundational infrastructure and functionality that reside at the heart of IBM Cúram SPM products.

Domain-Specific Processes: This process is related to SPM fundamental processes like Intake, Evidence Management, Case Management, Participant Management (like Person, Prospect Person, Employer, information provider etc.), Multi-Disciplinary Teams, Financial Management, Eligibility and Entitlement, Decision Assist and Supervisor Workspace.

Business Services:  The business services can be done through configuration or develop using the admin or system portal. The Business Services are Rules, Task Management, Code Tables, Search, Word Integration, Calendaring Scheduling, Rate Tables IEG & Correspondence.

Technical Services: The Technical services include development that needs build and deployment. The Technical Services are Web Services, Editors Security, Workflows, Exception handling, Logging, Queuing, Cognitive Manager, Transaction Management, REST API & EAI.

Data Dictionary: The Data Dictionary is an HTML representation of Database table, code table, properties & Domain Definition.

Knowledge Center: The Knowledge Center contains IBM Curam Product related documents in HTML and PDF format.

Application Development Environment (ADE): The ADE allows the developer to customize the Product based one Client policy and requirement. It provides a development environment.

The application installed used most of the module from the SPM layer.
Suppose, We started entering information for one MAGI application then below module will be impacted –

  • Participant Management to register the participants
  • Outcome Management for setting the assessment
  • Evidence Broker
  • Eligibility and Entitlement
  • Decision Assist and IEG to gather data and analyze the answers by using rules.
  • Developers use the Administration Suite to configure an assessment
  • Developers might use the ADE to customize an OOTB functionality

Modules need to be customized to meet specific customer requirements. For example, legislation around the world differs greatly. Therefore, client requirements in one country might be irrelevant, or even illegal in another jurisdiction. Therefore, it is usual to customize the base application and Cúram modules.

Many aspects of IBM Cúram SPM can be configured dynamically. For example, services and payments are delivered by using products, which are associated with rules (essentially, coded legislation). Rules are executed against evidence. Products, rules, evidence, and associated data, such as rate tables can be configured dynamically, which avoids the need for coding.

IBM Cúram SPM is a distributed multi-tiered JEE application:

PRESENTATION TIER            APPLICATION TIER           PERSISTENCE TIER

 

  • The presentation tier generates the user interface
  • The application tier contains the business logic.
  • The persistence tier interacts with the backend database

Benefits of IBM Cúram SPM platform are:

  • Industry-standard technologies
  • Scalability
  • Runtime performance
  • Interoperability with external systems
  • SOA compliance
  • User interface elegance
  • Model-driven architecture
  • Maintainability and extensible

The technologies used to build IBM Cúram SPM platform are given below –

  • The platform is built using industry standard technologies and open software standards, such as JEE, UML, and XML.
  • The Stateless JavaBean(EJB 3.X) used.
  • SOA compliance – Supports web service standards.

The Presentation tier used by various below-given Clients-

  • Internet Client HTML
  • XML
  • Internet Application
  • Mobile Client

The Application Tier Layer divided into 3 part, Please find it below –

  • Remote Interface Layer (RIL)
  • Business Object Layer (BOL)
    • Facade Layer
    • Service Layer
    • Entity Layer
  • Data Access Layer (DAL)

IBM Cúram Social Program Management (SPM) consists of the following components:

  • SPM Platform –Provides technical services, business services, case management features, and tools.
  • Application Modules –Provide domain-specific features. Some modules provide fully configured solutions.

 

Goals of the Cúram ADE

  • Model-Based development
  • Platform-specific code generation.
  • Business logic focus.
  • Simplified user interface development.
  • Use of recognized architectural patterns.

The two key factors related ADE given below –

  • The model acts as the starting point for any development.
  • The generators produce the appropriate Java, XML, and SQL code for use in the various layers of the server architecture. In fact, the only thing it does not generate for you is your business logic code, which developers concentrate on.

The UIM and Application Navigation offer a lot of advantages which are given below –

  • Ease of development
  • Increase Resource Productivity
  • Promotes consistent user interface
  • Significantly reduces the number of client bugs
  • Easy to add different languages.

Generators use the model to create Server Access Beans (Text Helper Classes).

Bootstrap.properties defines how to connect to the database, that is, database name, machine address, port, and credentials for access.

Application.prx contains application-level options and environmental settings.

Server Project Structure:

  • build
  • buildlogs
  • components
  • eclipsebuild
  • model
  • project
  • .classpath
  • .project
  • build.bat
  • buildhelp.bat
  • buildhelp.sh

The components folder contains at least one folder called core, which is used by all other components

The Component folder like custom contains various folder which store folder specific files. Please find all folder name below –

  • axis: It contains web service related files.
  • clientapps: It contain application navigation related files like .tab, .nav,.app, .ssp etc.
  • codetable: It contains codetable files.
  • config: It contains Installation Configuration File.
  • CREOLE_Rule_Sets: It contains CER ruleset related files.
  • data: It contains DMX files
  • events: It contains even related class.
  • message: It contains message related files.
  • model: It Contains model files which developed through RSA. It contains emx and efx files.
  • properties: It contains application level properties files like Application.prx, adapters.properties, javadoc.properties,ShortNames.properties.
  • workflows: It contains workflow related XML files.

The standard projects are as follows:

  • CuramCDEJ.
  • CuramSDEJ.
  • Client project (default name is ‘Cúram’).
  • Server project (default name is ‘EJBServer’).

Curam build scripts expect to find development artifacts in specific folders within a fixed directory structure.

The Client Project Structure:

  • build: generated artifact during client build.
  • buildlogs: Log files generated from each build.
  • components: Contains UIM files and other source artifacts.
  • JavaSource: Contains the ApplicationConfiguration.propertiesfile.
  • WebContent: Where most of the content of our web application is created, for example, the JSP files.
  • work: Used by Tomcat to store JSP files.
  • .classpath
  • .project
  • build.bat
  • buildhelp.bat
  • buildhelp.sh
  • derby.log

 

The Client Components Folder Structure:

The client component has at least one folder. The core is a default folder and custom folder can be created with any name or as custom.

  • Action
  • ActionPlan
  • Activity
  • AddressMap
  • Application
  • Assessment
  • Attachment
  • Calendar
  • Case
  • Case Audit
  • Case Audit Configuration
  • CMIS
  • CREOLE Case Admin

The main Ant targets are as follows:

  • generated: This Ant build target extracts the model and generate all required artifact along with compiling them if required.
  • implemented: This Ant build target compile all hand crafted Java files.
  • server: This Ant build target is combination of above given generated and implemented build target.
  • database: This Ant build target use artifects generated by server and create database related data like create application and custom tables, inserting initial data etc.
  • client: This Ant build target generates a complete web client application.

IBM Cúram SPM 7.0 Enterprise Modules:

  • IBM Cúram Archiving
  • IBM Cúram Appeals
  • IBM Cúram Business Intelligence & Analytics
  • IBM Cúram Enterprise Collaboration
  • IBM Cúram Evidence Broker
  • IBM Cúram Identity Intelligence
  • IBM Cúram Life Event Management
  • IBM Cúram Outcome Management
  • IBM Cúram Provider Management
  • IBM Cúram Provider Match With Watson
  • IBM Cúram Verification
  • IBM Cúram Universal Access

New in IBM Cúram

  • IBM Cúram Intake and Assessment –Helps caseworkers to intake clients and assess needs.
  • IBM Cúram Citizen Engagement –Helps citizens to triage, screen, apply online, and manage their citizen account.
  • Service Provider Management –Helps caseworkers to manage the provider registry and the full lifecycle of the provider.
  • IBM Cúram Case Management –Helps caseworkers to manage interactions with clients.
  • IBM Cúram Assessment and Planning –Helps caseworkers to use a multi-disciplinary approach to support client needs.
  • In V7.0, the UI has been updated to comply with the principles of IBM Design Language.
  • Universal Access and IEG pages, which have a different look and feel to the rest of the application, are unchanged.
  • SPM V7.0 is supported on desktops and laptops only.
  • No change in the application navigation.

Summary of UI Improvements:

  • Increased Spaces Between Touch Targets
  • Selected States
  • Increased Font Size
  • High Contrast
  • Color Palette

In V6, the minimum recommended screen resolution for the application was 1024×768 (aspect ratio 4:3). In V7.0, the minimum recommended resolution has been increased to 1366×768 (aspect ratio 16:9), which allows the application to take advantage of the wide-screen monitors that are widely available nowadays.

In Cúram SPM V7.0, the UI provides visual feedback via a Progress Spinner icon.UI displays the progress spinner when the following events take more than three seconds:

  •  Submitting a modal
  •  Opening a new page
  •  Clicking the Next button by a user in IEG

The UI dismisses the spinner once the load request returns a result:

  •  Successful load
  •  Unsuccessful load, including application server error, page expiry error, or license error

The Application Banner in V7.0 features several changes. The Quick Search feature has been moved into the Application Banner, which enables users to perform searches directly from the application banner. In addition, users can access the Preferences, About, and Log Out features directly from a menu in the Application Banner. The currently logged-on user’s role is no longer displayed in the Application Banner.

The BIRT charts in V7.0 have been redesigned to make them easier to read. The components of the charts now consist of slimmer shapes that occupy less space and consequently reside on larger areas of whitespace. The slimmer shapes and additional whitespace make the charts more legible and the data they present quicker to grasp at a glance.

A range of UI components have benefited from the moves to high-contrast, larger fonts, and more whitespace:

  • Action menus
  • Widgets
  • Drop-down lists
  • Active text-entry fields
  • Buttons
  • Checkboxes
  • Radio buttons

 

In addition, the icons that are used throughout the SPM application have been updated to make them easier to see and use.

In V7.0, the section Shortcut Panel is aligned with the top of the page. This makes it easier to view and access the options that the Shortcut Panel contains.

All Context Panels (Photo Panels, Information Panels, Links Panels, Icons, Default Person images):

In V7.0, all context panels are redesigned to be more readable, again enabling at-a-glance use of the panel by the user. The following components of the Context Panel have been updated:

  • Photo Panel
  • Information Panel
  • Links Panel Icons
  • Default Person images

The Technical Changes on UI for V7.0

  • CSS changes that reflect the new color palette, typography, padding, and so on.
  • Changes to the banner HTML that accommodate Search and remove the user role.
  • New icons.
  • V7.0 provides a configurable Progress Spinner.

No Changes Required on UI for V7.0

  • Configuration changes were not required for UIM, application navigation, and other client artifacts.
  • The look and feel of the following items were not changed:
    • IEG –The questionnaire looks the same as it did in V6.
    • Flex Editors –Datastore Editor, Rules Editor, IEG Editor, and Mapping Editor.
    • SVG Viewer –Workflow graphical view, organization chart, and Cúram rules.

IEG questionnaires have a different look and feel. The IEG page header and buttons reflect the new look and feel. However, the questionnaires themselves do not. As mentioned, the Flex editors that developers use are unchanged. Similarly, the organization view and workflow graphical view are shown the same way by using the SVG Viewer.

The areas of the SPM application that have been enhanced by UI modernization in V7.0 are as follows:

  • UIM Infrastructure: The below things got update under UIM infrastructure –
    • Application Container
    • Form Controls
    • Login and Logout Pages
    • Clusters
    • List
    • Model
    • Wizards
  • Pod Infrastructure updated.
  • SPM Platform Pods updated.
  • The Context Panel Updated for:
    • Provider Management
    • Child Services
    • SPM Platform
  • SPM Platform Birt Chart
  • Outcome Management
  • Outcome Management and Provider Management custom widgets
  • BIRT Charts
    • Intake
    • Child Services
    • Income Support
    • HCR
  • Internal Custom Widgets
    • Context Panel Person
    • Intake
    • Child Services
    • HCR

Configuration –Progress Spinner

  • The application displays the spinner when the user performs one of the following actions
    • Submits a model page
    • Opens a new page
    • Clicks the Next button in IEG
  • The application dismisses the spinner when a page loads successfully or does not load due to error.
  • You can configure the spinner in ApplicationConfiguration.properties
    • curam.progress.widget.enabled=true
    • curam.progress.widget.threshold=2000
  • Configuration is application wide.

Windows 10 is supported for the design, development, testing, and building of the application. Support has been added for the Microsoft Edge browser to access the Universal Access application.

Support for the Adobe SVG Viewer has been discontinued. This viewer was previously required for application pages that contained a dynamic rules tree view or a workflow process view. The SVG Viewer is no longer used in the application. These views have been modified to use the native SVG rendering functionality in the various supported browsers.

As for V6.2, Java 1.8 support has been certified for the IBM Cúram SPM application, which includes the use of Java 1.8 to develop, test, build, and deploy the Cúram SPM application.

The new Enterprise Modules rely on IBM functionality that is provided outside of Cúram:

  • Identity Intelligence – Identity Intelligence contains an installer for the IBM Cúram Identity Intelligence Enterprise Module and IBM Infosphere Identity Insight V8.1, which performs identity processing.
  • Archiving – The archiving solution consists of IBM Cúram Archiving and IBM Infosphere Optim Archive Enterprise Edition V11.3.1.
  • Provider Match With Watson – The Provider Match solution consists of IBM Cúram Provider Match with Watson and Watson Tradeoff Analytics, which is hosted in the cloud.

All SPM application modules include an installer for the SPM Platform and installers for Enterprise Modules that might be required.
The following installers are provided for the other business modules:

  • IBM Cúram Single Client View: SPM Platform.
  • IBM Cúram Intake and Assessment: SPM Platform and Universal Access.
  • IBM Cúram Case Management: SPM Platform.
  • IBM Cúram Assessment and Planning: SPM Platform, Provider Management, Outcome Management, and Social Enterprise Collaboration.
  • IBM Cúram Service Provider Management: SPM Platform, Provider Management, Outcome Management, and Social Enterprise Collaboration.
  • IBM Cúram Appeals and Legal Actions: SPM Platform and Appeals.
  • IBM Cúram Audit and Investigation: SPM Platform and Appeals.
  • IBM Cúram Case Management Eligibility and Entitlement Add-On: SPM Platform.

Deprecated Functionality: There are a couple of functionalities marked as deprecated from V 7.X. The features are turned off and all artifacts marked deprecated. Alternatives are available for some of these features and IBM continues to support these functionalities but no longer plans to enhance them. These features might be removed from the future release and no support will be provided. The release notes contain more detailed information about deprecated artifacts.
Please find them below –

  • Evidence Flow
  • Legacy Employment Contribution Entities
  • Over/Underpayments Graphical View
  • Referrals
  • Health Care Reform Intake PDF Report
  • Spell Checker
  • Social Enterprise Collaboration
  • Generic Search Server
  • Non-Identical Evidence Mapping

The tnameserv port is changed from 900 to 1221.

 

 

 

3 thoughts on “IBM Cúram 7.X Certification Important Notes”

    2. Hi will you please disclose your strategy about how you prepare for this certification exam. What should be done to clear it.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *