Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Stambia DI for InterSystems Caché

    Stambia Data Integration allows to work with InterSystems Caché databases to produce fully customized Integration Processes.

    The database structure can be entirely reversed in Metadata and then used in Mappings and Processes to design and adapt the business rules to meet the user's requirements.


    Prerequisites:
    • The InterSystems Caché JDBC driver must be installed in the Designer and Runtime
    • Stambia DI Designer S19.0.6 or higher

    Note:

    Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.

    If you have any question, any feature request or any issue, do not hesitate to contact us.

     

    Download

    You can find below the necessary resources to work with this Component in Stambia DI

    Name Description Download
    Component resources You can find in download section the Component resources. Component resources download

     

    Supported features

    You can find below an overview of what Stambia DI can do with InterSystems Caché databases

    Name Description
    Reverse

    The database structure can be reversed in a dedicated Metadata

    DDL /DML Operations

     

    DML/DDL operations can be performed on the database, such as: Insert, Update, Select, Delete, Create or Drop

    Integration methods
    • Append
    • Incremental Update
    Staging

    The databases can be used as a staging area to make data transformation, mutualization, ...

    The following modes are supported:

    • staging as subquery
    • staging as view
    • staging as table
    Reject

    Reject rules can be defined to filter or detect data that does not fulfill the rules during integrations.

    • Three type of rules can be created: Fatal, Warning, Reject
    • Depending on the specified type, the rejected data will not be handle the same way
    • Rejects of previous executions can also be recycled
    Replication

    Replication of databases is supported.

    The replication source can be any rdbms, Flat files or XML files.

    Subcategories

    Articles

    Suggest a new Article!