Integration

There are different ways to integrate code based on how you intend to use the API. This document explains integration and deployment requirements based on the functionality being used

In-process Integration

In-process integration means that your code that uses the API runs in the same app domain as the Temenos Lifecycle Management Suite. In this integration scenario, the Temenos Lifecycle Management Suite will instantiate your code directly. In other words, this is a "push" integration. The Temenos Lifecycle Management Suite will push actions/requests/data to your code. Certain functionality of the API is only available using the in-process integration:

  • UI integration
  • Events

Out-of-process Integration

Out-of-process integration means that the API dlls run inside the app domain of your own application. In this integration scenario, your code will instantiate the API directly. In other words, this is a "pull" integration. Your code will initiate actions/requests/data from the API.

.NET Framework

The Temenos Lifecycle Management Suite is a .NET application compiled using the 4.0 CLR. Your code must use .NET 4.0 or .NET 4.5.