Temenos Digital
R24 AMR | Min(s) read

Digital Banking Micro Apps Setup

You must set up Spotlight platform also with the following installation.

After the environment and database has been set up, the next step in the Temenos Digital set up process is to import and configure the Quantum Fabric app(s) pertaining to Micro Apps. The following steps describe the process of importing, configuring, and publishing the Quantum Fabric apps.

Download Artefacts 

To download the artefacts required for setting up Quantum Fabric, write to distribution@temenos.com for details on where and how to download.

Download the following artefacts:

  • DigitalBanking-Login_vx.x.x.zip
  • DigitalBanking-SettingsCommunications_vx.x.x.zip
  • DigitalBanking-CardSmartMoney_vx.x.x.zip
  • DigitalBanking-Corporate_vx.x.x.zip
  • DigitalBanking-Engines_App-vx.x.x.zip
  • DigitalBanking-Homepage_vx.x.x.zip
  • DigitalBanking-Payments_vx.x.x.zip
  • DigitalBanking-UserManagement_vx.x.x.zip
  • DigitalBanking-WealthManagement_vx.x.x.zip
  • DigitalBanking-Engines_App-vx.x.x.zip

See the table to determine the Quantum Fabric apps that must be set up in your system.  The Quantum Fabric application file names are suffixed with a <<major_version>>.<<fix_version>> format for every release. 

Quantum Fabric App File Description Do I have to install this? Quantum Fabric App Name Discovery Path
DbpEventManager_App_vx.x.xzip This app contains the service definitions and requisite libraries to cater to the event management and alerts functionality. This Quantum Fabric app is mandatory for the events and alerts functionality to work irrespective of which customer-facing application you are planning to deploy. DbpEventManager DigitalBanking-Engines_App-vx.x.x\DigitalBanking-Engines_App-vx.x.x\Fabric\EventManager
Authentication_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the authentication. This Quantum Fabric app is mandatory for the authentication functionality to work irrespective of which customer-facing application you are planning to deploy. Authentication DigitalBanking-Login_vx.x.x \ DigitalBanking-Login_vx.x.x \ Authentication
Content_management_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the content management functionality. This Quantum Fabric app is mandatory for the content management functionality to work irrespective of which customer-facing application you are planning to deploy. ContentManagement DigitalBanking-Login_vx.x.x \ DigitalBanking-Login_vx.x.x \ ContentManagement
Arrangements_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the arrangements functionality This Quantum Fabric app is mandatory for the Arrangements functionality to work irrespective of which customer-facing application you are planning to deploy. Arrangements DigitalBanking-Homepage_vx.x.x \ DigitalBanking-HomePage_vx.x.x \ Arrangements
AccountAgggregation_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the Account Aggregation functionality. This Quantum Fabric app is mandatory for the Account Aggregation functionality to work irrespective of which customer-facing application you are planning to deploy. AccountAggregation DigitalBanking-CardSmartMoney_vx.x.x \ DigitalBanking-CardSmartMoney_vx.x.x \ AccountAggregation
CardManagement_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the Card Management functionality. This Quantum Fabric app is mandatory for the Card Management functionality to work irrespective of which customer-facing application you are planning to deploy. CardManagement DigitalBanking-CardSmartMoney_vx.x.x \ DigitalBanking-CardSmartMoney_vx.x.x \ CardManagement
FinanceManagement_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the Finace Management functionality. This Quantum Fabric app is mandatory for the Finance Management functionality to work irrespective of which customer-facing application you are planning to deploy. FinanceManagement DigitalBanking-CardSmartMoney_vx.x.x \ DigitalBanking-CardSmartMoney_vx.x.x \ FinanceManagement
SavingsPot_vx.x.x.zip SavingsPot_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the Savings Pot functionality. This Quantum Fabric app is mandatory for the saving spot functionality to work irrespective of which customer-facing application you are planning to deploy. SavingsPot DigitalBanking-CardSmartMoney_vx.x.x \ DigitalBanking-CardSmartMoney_vx.x.x \ SavingsPot
BulkPayments_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the Bulk Payment functionality. This Quantum Fabric app is mandatory for the Bulk Payments functionality to work irrespective of which customer-facing application you are planning to deploy.    
TradeFinance_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the Trade Finance functionality. This Quantum Fabric app is mandatory to work irrespective of which customer-facing application you are planning to deploy. TradeFinance DigitalBanking-Corporate_vx.x.x \ DigitalBanking-Corporate_vx.x.x \ TradeFinance
ForeignExchange_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the Foreign Exchange functionality. This Quantum Fabric app is mandatory for the Foreign Exchange functionality to work irrespective of which customer-facing application you are planning to deploy. ForeignExchange DigitalBanking-Corporate_vx.x.x \ DigitalBanking-Corporate_vx.x.x \ ForeignExchange
ExternalUserManagement_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the External User Management functionality. This Quantum Fabric app is mandatory for the External User Management irrespective of which customer-facing application you are planning to deploy. ExternalUserManagement DigitalBanking-usermanagement_vx.x.x \ DigitalBanking-Usermanagement_vx.x.x \ Externalusermanagement
Approvals_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the approvals functionality. This Quantum Fabric app is mandatory for the approvals functionality to work irrespective of which customer-facing application you are planning to deploy. Approvals DigitalBanking-usermanagement_vx.x.x \ DigitalBanking-Usermanagement_vx.x.x \ Approvals
OrderManagement_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the order management functionality. This Quantum Fabric app is mandatory for the events and alerts functionality to work irrespective of which customer-facing application you are planning to deploy. OrderManagement DigitalBanking-WealthManagement_vx.x.x \ DigitalBanking-WealthManagment_vx.x.x \ OrderManagement
PortfolioManagment_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the portfolio management functionality. This Quantum Fabric app is mandatory for the portfolio management functionality to work irrespective of which customer-facing application you are planning to deploy. PortfolioManagement DigitalBanking-WealthManagement_vx.x.x \ DigitalBanking-WealthManagment_vx.x.x \ PortfolioManagement
SecureMessage_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the secure message functionality. This Quantum Fabric app is mandatory for the secure message functionality to work irrespective of which customer-facing application you are planning to deploy. SecureMessage DigitalBanking-SettingsCommunications_vx.x.x \ DigitalBanking-SettingsCommnications_vx.x.x \ SecureMessage
AlertsManagement_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the alerts management functionality. This Quantum Fabric app is mandatory for the alerts management functionality to work irrespective of which customer-facing application you are planning to deploy. AlertsManagement DigitalBanking-SettingsCommunications_vx.x.x \ DigitalBanking-SettingsCommnications_vx.x.x \ AlertsManagement
ConsentManagement_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the consent management functionality. This Quantum Fabric app is mandatory for the consent management to work irrespective of which customer-facing application you are planning to deploy. ConsentManagement DigitalBanking-SettingsCommunications_vx.x.x \ DigitalBanking-SettingsCommnications_vx.x.x \ ConsentManagement
Payments_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the payments functionality. This Quantum Fabric app is mandatory for the payments functionality to work irrespective of which customer-facing application you are planning to deploy. Payments DigitalBanking-Payments_vx.x.x \ DigitalBanking-Payments_vx.x.x \ Payments

CampaignEngine_App_vx.x.x.zip

This app contains the service definitions and requisite libraries to cater to the Campaign Engine functionality. This Quantum Fabric app is mandatory for the campaign functionality to work, irrespective of which customer-facing application you are planning to deploy. This app is a prerequisite to be deployed before the DigitalBanking-Composite app is deployed. CampaignEngine DigitalBanking-Login_vx.x.x\DigitalBanking-Login_vx.x.x\Fabric\CampaignEngine
TransactionLimitsEngine_App_vx.x.x.zip This app contains the service definitions and requisite libraries to cater to the Transaction Limits functionality. This is used for every transfer made. This Quantum Fabric app is mandatory for the Transfer functionality to work, irrespective of which customer-facing application you are planning to deploy. TransactionLimitsEngine DigitalBanking-Engines_App-vx.x.x\DigitalBanking-Engines_App-vx.x.x\Fabric\TransactionEngine
ServiceRequestAPI_App_vx.x.x.zip This app contains the service definitions related to order management. This Quantum Fabric application is mandatory. ServiceRequestAPI DigitalBanking-Engines_App-vx.x.x\DigitalBanking-Engines_App-vx.x.x\Fabric\ServiceRequestAPI

Digital Banking Modules and their Dependencies

Digital Banking is divided broadly into the following modules. To be able to work on each module independently, the following visualizer and fabric microApps are required.

Retail   Visualiser MicroApp Fabric Micro App

Login

 

CommonsMA,

ResourcesMA,

AuthenticationMA,

AboutUsMA,

CampaignMA

Authentication

ContentManagement

Campaign

Homepage

 

HomepageMA,

ArrangementsMA

Arrangements

Arrangements

CardSmartMoney

 

CardsMA,

FinanceManagementMA, AccAggregationMA,

SavingsPotMA

CardManagementMA

FinanceManagement

AccountAggregation

SavingsPot

 

 

 

 

Retail

 

Visualiser MicroApp

Fabric Micro App

Bulk  Payments

 

BulkPaymentsMA

BulkPayments

ForeignExchange

 

ForeignExchangeMA

ForeignExchange

TradeFinance

 

TradeFinanceMA

TradeFinanceMA

 

Payments:

 

Visualiser MicroApp

Fabric Micro App

BillPay

 

BillPayMA

Payments

DigitalTransfer

 

DigitalTransferMA

Payments

RegionalTransfer

 

RegionalTransferMA

Payments

UnifiedTransfer

 

UnifiedTransferMA

Payments

WireTransfer

 

WireTransferMA

Payments

Transfers

 

TransfersMA

Payments

 

SettingCommunications:

 

Visualiser MicroApp

Fabric Micro App

ConsentMgmt

 

ConsentMgmtMA

ConsentManagement

ManageArrangement

 

ManageArrangementsMA

Arrangements

ManageProfile

 

ManageProfileMA

ExternalUserManagement

SecureMessage

 

SecureMessageMA

SecureMessage

AlertSettings

 

AlertSettingsMA

AlertsManagement

 

WealthManagement:

 

Visualiser MicroApp

Fabric Micro App

PortfolioManagement

 

PortfolioManagementMA

WealthPortfolioManagement

WealthOrder

 

WealthOrderMA

OrderManagement

 

UserManagement:

 

Visualiser MicroApp

Fabric Micro App

ACH

 

ACHMA

ACH

ApprovalMatrix

 

ApprovalMatrixMA

Approvals

ApprovalRequest

 

ApprovalRequestMA

Approvals

UserManagement

 

UserManagementMA

ExternalUserManagement

SelfServiceEnrolment

 

SelfServiceEnrolmentMA

ExternalUserManagement

Import Quantum Fabric Application

This section describes the procedure to import and publish process for any Quantum Fabric application. Make sure that you are using the appropriate Quantum Fabric apps as described here.

The images are for representation only. The actual screen may vary depending on the Quantum Fabric app being imported. Select the appropriate application.

Sign in to Quantum Fabric

Sign in to Cloud or On-premise installation of Quantum Fabric. Use the credentials you have obtained during the environment setup process.

Import Quantum Fabric Application

  1. On successful authentication, the Dashboard page is displayed by default. 
  2. Click the Apps icon on the left pane. The Applications page is displayed.

  3. On the Applications page, click Import. The Import App dialog is displayed.

  4. Browse for Quantum Fabric app package (specified in the list earlier) or drag the app package, and click Import. You must do this for each app in the list in case you have more than one app to import.

  5. The image is for reference only. The Quantum Fabric application name varies from application to application. The following are the Quantum Fabric apps of the respective app from the Temenos Digital suite that are:
    • Order management: ServiceRequestAPI
    • Transaction Limit Engine: TransactionLimitsEngine
    • Alerts Management: dbpEventManager
    • Campaign Management: CampaignEngine

    While the apps listed above are required only to import the corresponding apps, for the following Micro Apps, in addition to importing the apps, create one composite app and link the corresponding Micro Apps:

    AccountAggregation, AlertsManagement, Approvals Arranagements, Authentication, BulkPayments, CardManagement, ConsentManagement, ContentManagement, ExternalUserManagement, FinanceManagement, ForeignExchange, OrderManagement, Payments, PortfolioManagement, SavingsPot, SecureMessage, TradeFinance.

  6. Under the Import Options, select the Import as new option, and click Import. The app is imported as a new app.
  7. The imported application is displayed on the Applications page. For detailed information on importing an app to Quantum Fabric Console, refer to Exporting and Importing an Application.

Create Composite App

This section describes the procedure to create a composite app and link the corresponding Micro Apps for any Quantum Fabric Micro App.

  • Make sure that all the corresponding dependent Fabric Micro Apps are available - as per the attached document, before linking the apps as part of the Composite App.
  • Make sure that you are using the appropriate Quantum Fabric apps as described here.
  • The images are for representation only. The actual screen may vary depending on the Quantum Fabric Micro App and standard composite app name being imported. Select the appropriate application.

To create a Composite App,

  1. Sign in to Cloud or On-premise installation of Quantum Fabric. Use the credentials you have obtained during the environment setup process.
  2. On successful authentication, the Dashboard page is displayed by default. 
  3. Click the Apps icon on the left pane. The Applications page is displayed.
  4. On the Applications page, click Add new.
  5. Use the pencil icon and name the app as a DigitalBanking-Composite as it is the standard name to represent digitalbanking.
  6. An empty composite app is created.

Link Micro App

To link Micro Apps with a Composite App,

  1. On the Applications page, select the Composite App.
  2. On the context menu (ellipsis icon), click Manage Linked Apps.

  3. On the Managed Linked Apps screen, click Add.
  4. On the Existing Apps screen, select the required Micro Apps that you want to link with the Composite App, and click Link.

  5. The selected Micro Apps are linked successfully with the Composite App.

Unlink Micro App

To unlink Micro Apps from a Composite App,

  1. On the Applications page, select the Composite App and go to the Managed Linked Apps screen.
  2. From the list of linked Micro Apps, select the required apps that you want to unlink.

  3. Click Unlink.
  4. On the Unlink Linked Apps confirmation screen, Click Close. The selected Micro Apps are unlinked from the Composite App.

Configure Identity Services

All Quantum Fabric apps available as part of Temenos Digital contain several Object, Integration, and Orchestration services. Most of these services are authenticated by Identity services. The Quantum Fabric Identity Service(s) for each Quantum Fabric app must be configured to reflect the fully qualified URL of the environment on which the service is deployed. The part of the URL occurring before the /services/<Identity Service Name> must be replaced with the environment specific values. Refer to the table below to determine the identity services to be configured.

Quantum Fabric App Identity Service Name Identity Service Type Description
  • Authentication
  • ContentManagement
  • ExternalUserManagemnt
  • Origination
  • Payments
  • SecureMessage
  • AlertsManagement
DbxUserLogin Custom Identity The identity service is used to authenticate end users against the Temenos Digital identity management system or the core identity system.
  • Authentication
  • ContentManagement
  • ExternalUserManagemnt
  • Origination
  • Payments
  • SecureMessage
DbxAPIIdentityService Custom Identity The identity service is used to authenticate server to server communication.

Update the URL in the Custom Identity Service Endpoint field in the Configure Services - Identity section for DbxUserLogin like in the following screen:

Update the URL in the Custom Identity Service Endpoint field in the Configure Services - Identity and select the check box of Restrict to Server to Server Authentication section for DbxAPIIdentityService like in the following screens:

Configure RDBMS Integration Services

Temenos Digital comes with pre-built integration to the Temenos DB whose setup is described here. The following table describes the integration and object services of type RDBMS that must be configured with the database connection parameters for your installation. 

Quantum Fabric App RDBMS Integration/Object Service Name Description
Authentication dbpRbLocalServicesdb Contains RDBMS services for various Create, Read, Update, and Delete operations on the Temenos Digital schema.
DbpEventManager EventManagerDBService Contains RDBMS services related to Alerts and Audit operations on the Temenos Digital schema.
DbpEventManager ExternalEventsDBService Contains RDBMS services related to Event Topic Configuration operation on Temenos DigitalSchema.
CampaignEngine CampaignDBService Contains RDBMS services related to Campaign operations on Temenos Digital Schema.
TransactionLimitsEngine TransactionsLimitDBService Contains RDBMS services related to TransactionLimits operations on Temenos Digital Schema.
InfinityWorkspace askManagementDBXDBService Contains RDBMS services for various Create, Read, Update, and Delete operations on the Temenos Digital schema.
SecureMessage MessageBinary Contains RDBMS services for various Create, Read, Update, and Delete operations on the Temenos Digital schema.

Navigate to the RDBMS Integration service and modify the connection parameters corresponding to your database environment.

Navigate to the Object service configuration and modify the connection parameters corresponding to your database environment.

Configure Runtime Parameters

The parameters that are specific to each deployment of the Quantum Fabric app(s) are maintained under the Configurable Parameters section of runtime Quantum Fabric environment. Follow these steps:

  • Navigate to the environment.
    • For cloud environments click App Services.

    • For on-premise environments click Server.

  • Navigate to Settings on the left hand panel. You should see the Configurable Parameters section.

The following is the list of configurable parameters for the Quantum Fabric app(s):

Parameter Description Where do I find this? Type Mandatory? Fabric App Republish Required? Sample Value
DBP_HOST_URL Base URL of Fabric run-time on which the Authentication app has been deployed.
  • Navigate to the run-time console.
  • Extract Host URL from Browser Address URL.
Server Yes No https://{baseURL}:portnumber
DBP_CUSTOMER_SESSION_URL URL to get the user attributes from identity scope of the DbxUserLogin identity service.
  • Navigate to Publish tab of Authentication Quantum Fabric Application.
  • Click on the Published indicator and retrieve the Service URL.
  • Replace the string appconfig with session/user_attributes?provider=DbxUserLogin
Server Yes No https://{baseURL}/session/user_attributes?provider=DbxUserLogin
DBP_NUO_SESSION_URL URL to get the user attributes from the identity scope of the NUOApplicantLogin identity service
  • Navigate to Publish Tab of Authentication Quantum Fabric Application.
  • Click on the Published indicator and retrieve the Service URL.
  • Replace the string appconfig with session/user_attributes?provider=NUOApplicantLogin
Server Yes No https://{baseURL}/session/user_attributes?provider=NUOApplicantLogin
DBP_AC_HOST_URL Base URL of Fabric runt-time on which Spotlight Quantum Fabric apps have been deployed
  • Navigate to the run-time console of the KonyBankingAdminConsole Fabric app
  • Extract Host URL from Browser Address URL
Server Yes No https://{baseURL}:portnumber
DBP_AC_AUTH_URL URL of the identity Service exposed by Spotlight for server to server communication
  • Navigate to Publish Tab of KonyBankingAdminConsole Quantum Fabric Application.
  • Click on the Published indicator and retrieve the Service URL.
  • Replace the string appconfig with login?provider=KonyBankingAdminConsoleAPIIdentityService
Server Yes No https://{baseURL}/login?provider=KonyBankingAdminConsoleAPIIdentityService
DBP_AC_ACCESS_TOKEN Expected access token of the Identity Service exposed by Spotlight Internal API Access Token configured during the Security Configuration of Spotlight. Server Yes No Valid access token
DBP_AC_APP_KEY App Key of the published Spotlight Fabric Application
  • Navigate to the Publish Tab of the KonyBankingAdminConsole Fabric Application.
  • Click on the Published indicator for the App-Key. 
Server Yes No Valid app key
DBP_AC_APP_SECRET App Secret of the published Spotlight Fabric Application
  • Navigate to the Publish Tab of the KonyBankingAdminConsole Fabric Application.
  • Click on the Published indicator for the App-Secret. 
Server Yes No Valid app secret
DBP_CORE_USER_GET URL to retrieve the user details from the designated core banking system. This is only presuming the standard demonstration setup where the Core Banking system is simulated Implementation specific Server Yes No https://{baseURL}:portnumber/services/data/v1/RBObjects/objects/User
DBP_CORE_APPKEY App Key of the published Core Banking Quantum Fabric Application. This is only presuming the standard demonstration setup where the Core Banking system is simulated Implementation specific Server Yes No Valid app key
DBP_CORE_SECRET App Secret Key of the published Core Banking Quantum Fabric Application. This is only presuming the standard demonstration setup where the Core Banking system is simulated Implementation specific Server Yes No Valid app secret
DBP_CUSTOMER_SECURITY_URL URL to get the security attributes from identity scope of the DbxUserLogin identity service
  • Navigate to Publish Tab of Authentication Quantum Fabric Application.
  • Click on the Published indicator and retrieve the Service URL.
  • Replace the string appconfig with session/security_attributes?provider=DbxUserLogin
Server Yes No https://{baseURL}/session/security_attributes?provider=DbxUserLogin
OTP_VALIDITY_IN_MINS OTP expiry duration in minutes Client specific Server Yes No 10
ALLOWED_OTP_ATTEMPT Number of allowed OTP attempts for same mobile number Client specific Server Yes No 3
OTP_REQUEST_LIMIT Number of allowed OTP requests Client specific Server Yes No 500
SCHEMA_NAME Schema name of Temenos Digital database Client specific Server Yes No dbxdb
DBX_DB_HOST_URL JDBC URL of the Temenos Digitaly database. For SQL Server, database name is one and schema are two. The database name must be used for SQL Server. Client specific Server Yes No jdbc:mysql://dbURL:portnumber/dbxdb
DBX_DB_USERNAME Username of the database user having read/write access  Client specific Server Yes No Valid user name
DBX_DB_PASSWORD Password of the database user having read/write access  Client specific Server Yes No Valid password
MAX_LOCK_COUNT Maximum number of Unsuccessful attempts allowed before user get locked Client specific Server Yes No 5
DBP_AI_ACCESS_BY Expected Shared Secret of the Identity Service exposed by Spotlight. Client specific Server Yes No OLB
DBP_AI_TIMEOUT_IN_MINS Spotlight service session timeout Client specific Server Yes No 10
DBX_ACTIVATION_LINK_SMALLBUSINESS URL of Business Banking Application Dashboard URL of the Business Banking application dashboard Server Yes No https://{baseURL}/apps/BusinessBanking#_frmLogin
DBP_OLB_BASE_URL URL of Online Banking Application Dashboard URL of the Online Banking application dashboard Server Yes No https://{baseURL}/apps/KonyOLB
DBX_ENROLL_LINK Enrollment URL of the Retail Banking application Navigate the Enrollment flow in the Online banking application and retrieve the URL Server Yes No https://{baseURL}/apps/KonyOLB/#_frmEnrollNow
DBP_BUSINESS_LINK Base URL of Business Banking Application Base URL of Business Banking Application Server Yes No https://{baseURL}/apps/BusinessBanking
DBP_LOANS_LINK Base URL of Consumer Lending Application Base URL of the Consumer Lending Application Server Yes No https://{baseURL}/apps/ConsumerLending
DBP_CORE_LOGIN Core Banking login URL. This is only presuming the standard demonstration setup where the Core Banking system is simulated Client specific Server Yes No https://{baseURL}/services/dbpLocalServiceslogin/login
DBP_CORE_VERIFY_USER Core Banking service URL for user verification. This is only presuming the standard demonstration setup where the Core Banking system is simulated Client specific Server Yes No https://{baseURL}/services/data/v1/RBObjects/operations/User/verifyCoreUser
DBP_CORE_VERIFY_USERNAME Core Banking service URL for username verification. This is only presuming the standard demonstration setup where the Core Banking system is simulated Client specific Server Yes No https://{baseURL}/services/data/v1/RBObjects/operations/User/verifyCoreUserName
DBP_CORE_CORPORATE_CREATE Core Banking service URL for business banking user creation. This is only presuming the standard demonstration setup where the Core Banking system is simulated Client specific Server Yes No https://{baseURL}/services/data/v1/RBObjects/objects/User
DBP_CORE_CUSTOMER_CREATE Core Banking service URL for customer creation. This is only presuming the standard demonstration setup where the Core Banking system is simulated Client specific Server Yes No https://{baseURL}/services/data/v1/RBObjects/objects/User
DBP_CORE_PROSPECT_CREATE Core Banking service URL for prospect creation. This is only presuming the standard demonstration setup where the Core Banking system is simulated Client specific Server Yes No https://{baseURL}/services/data/v1/RBObjects/objects/User
DBP_KMS_URL Base URL of the Quantum Fabric run-time on which Engagement services have been configured
  • Navigate to run-time console.
  • Extract the Host URL from the Browser Address URL
Server Yes No https://{baseURL}
DBX_KMS_USER Engagement services user subscription trigger endpoint
  • Navigate to run-time console.
  • Extract the Host URL from the Browser Address URL
  • Append /api/v1/audience to the extracted value.
Server Yes No https://{baseURL}:portnumber/api/v1/audience
DBX_KMS_EMAIL Engagement services e-Mail trigger endpoint
  • Navigate to run-time console.
  • Extract the Host URL from the Browser Address URL
  • Append /api/v1/message/email to the extracted value.
Server Yes No https://{baseURL}/api/v1/message/email
DBX_KMS_USERNAME Username to login to the Engagement Services server Client specific Server Yes No Valid user name
DBX_KMS_PASSWORD Password to login to the Engagement Services server Client specific Server Yes No Valid password
DBX_KMS_SMS Engagement services SMS trigger endpoint
  • Navigate to run-time console.
  • Extract the Host URL from the Browser Address URL
  • Append /api/v1/message/sms to the extracted value.
Server Yes No https://{baseURL}:portnumber/api/v1/message/sms
DBX_KMS_PUSH Engagement services PUSH Notification trigger endpoint
  • Navigate to run-time console.
  • Extract the Host URL from the Browser Address URL
  • Append /api/v1/message/push to the extracted value.
Server Yes No https://{baseURL}:portnumber/api/v1/message/push
DBX_KMS_API_KEY API Key of the KMS App
  • Navigate to Apps in the Engagement Services Console.
  • Click on the app.
  • Navigate to the Settings tab.
  • Navigate to the API Key and copy the API Key.
Server Yes    
DBX_KMS_APPKEY App key of Engagement service push notification app Authentication. Client specific Server Yes No Valid key
RETAIL_AND_BUSINESS_BANKING_KMS_APPKEY Retail Banking app key of Engagement service push notification app Authentication. Client specific Server Yes No Valid key
BACKGROUNDVERIFICATION_ENABLE Flag to enable or disable the background verification performed through IDology  Client specific Server Yes No true/false
MFA_TRANSACTION_TYPES_BYPASSES List of transactions to bypass MFA authentication. Client specific Server Yes No StopCheckPaymentRequest, Loan,Deposit, Cardless, CheckWithdrawal
PRIMARY_MFA_TYPE Primary MFA type Client specific Server Yes No SECURITY_QUESTIONS
QFX_INTUIT_BUILD Financial Institution branding ID Client specific Server Yes No 6157
QFX_ORG_NAME Financial Organization name Client specific Server Yes No Kony
QFX_USER_NAME QFX user name Client specific Server Yes No Valid user name
QFX_FINANCE_ID Financial Institution ID Client specific Server Yes No 6157
EMAIL_REQUEST_LIMIT Limit the number of emails can be sent per email per day Client specific Server Yes No 1000
ENABLE_EVENTS Flag to enable or disable events. Client specific Server Yes No true
T24_ALERTSUBSCRIPTION_BASEURL Base URL of T24 to call Alert subscription related APIs. Client specific Server Yes No http://<host>:<port>/irf-provider-container/api
ALERTHISTORY_ARCH_DATABASE_DRIVER Database driver name (used for Alerts Archival services) Client specific Server Yes No com.mysql.jdbc.Driver
ALERTHISTORY_ARCH_DATABASE_PASSWORD Database password (used for Alerts Archival services) Client specific Server Yes No kony1234
ALERTHISTORY_ARCH_DATABASE_URL JDBC URL for database connection (used for Alerts Archival services). Client specific Server Yes No jdbc:mysql://<host>:<port>/dbxdb
ALERTHISTORY_ARCH_DATABASE_USER Database user name with read and write access (used for Alerts Archival services). Client specific Server Yes No dbclient
ALERT_EMAIL_SENDER_NAME Sender Name from Configurable Parameter while submitting an email. Client specific Server No No  
ALERTS_DEFAULT_LANGUAGE Default Language for the message template to be picked while sending alerts to the user. Client specific Server No No en-US

BATCH_ALERT_APP_ID

AppId to be used while pushing batch alerts.

Client specific

Server

Yes

No

RETAIL_BANKING for versions before 20.4

RETAIL_AND_BUSINESS_BANKING for version 20.4

ALERTSUBSCRIBER_CORE_TYPE Core Type used. This is used by the Batch Alerts processing. Client specific

Server

Yes

No CORE
SEND_ALERTHISTORY_TO_EXTERNAL Set the Flag to true if the service related to sending Alert history to any external system has to be triggered. Client specific

Server

Yes

No false
EXTERNAL_ALERTS_CORE_TYPE To determine which backend ID must be picked up from backendidentifier table based on core type. Client specific

Server

Yes

No PARTY
REMINDER_ENGINE_BACKENDTYPE Core Type used. This is used by the Alerts Reminder Engine (Frequency). Client specific

Server

Yes

No CORE
ALERTS_CORETYPE Core Type used. This is used by the Alerts Auto Subscription service. Client specific

Server

Yes

No CORE

AUDITLOG_ARCH_DATABASE_URL

JDBC URL for database connection (used for Alerts Archival services).

Client specific

Server

Yes

No  

AUDITLOG_ARCH_DATABASE_USER

Database user name with read and write access (used for Alerts Archival services).

Client specific

Server

Yes

No  

AUDITLOG_ARCH_DATABASE_PASSWORD

Database password (used for Alerts Archival services).

Client specific Server Yes No  
AUDITLOG_ARCH_DATABASE_DRIVER Used for Alerts Archival services. Client specific Server Yes No com.mysql.jdbc.Driver
QUEUEMASTER_DATABASE_DRIVER Database driver name Client specific Server Yes No com.mysql.jdbc.Driver
QUEUEMASTER_DATABASE_PASSWORD Database password Client specific Server Yes No Valid password
QUEUEMASTER_DATABASE_URL JDBC URL for the database connection where the Events queue master is hosted. For SQL Server, database name is one and schema are two. The database name must be used for SQL Server. Client specific Server Yes No jdbc:mysql://{baseURL}:portnumber/dbxdb
QUEUEMASTER_DATABASE_USER Database user name with read and write access. Client specific Server Yes No dbclient
QUEUEMASTER_SHARED_SECRET Access token to call Service exposed by Spotlight. Client specific Server Yes No Valid secret
QUEUEMASTER_MAINTENANCE_MODE Flag to allow the admin to refresh the memory with Event Types for every consumer event management engine. This flag will be set to true and then the operation ReStart in the QueueMaster Integration Service, whenever a new set of Event Types are added/modified for a consumer event management engine. Client specific Server Yes No false

QUEUEMASTER_DATABASE_INTERNAL_CONNECTION_POOL_SIZE

Number of Database connections used for internal services.

Client specific

Server

Yes

No

7

QUEUEMASTER_DATABASE_CONNECTION_POOL_SIZE

Number of Database connections used to read requests.

Client specific

Server

Yes

No

7

DBP_ACCESS_TOKEN Encryption key used to decrypt the shared secret stored in database for verifying the same in the login flow. Client specific Server Yes No Valid access token
CAMPAIGN_FETCHTYPE This property determines the source from which Campaigns should be fetched.

Implementation specific. Values to be used as below:

  • REALTIME
  • CACHE

If nothing is mentioned, default value is REALTIME.

Server Yes No REALTIME
CAMPAIGN_CORETYPE This property is used to indicates the type of backend the user belongs to (as given in backend_identifier table).

Implementation specific

  • If user is configured for single CoreType then it is fetched automatically.
  • If user is configured for more than one backendType then user has to specify the type.

Default value is "".

Server Yes No CORE
CAMPAIGN_DC_DEFAULTUSERNAME This property expects the username of the user which has access to datacontext. If no username is provided specific to the datacontext, then this is picked by default. Implementation specific Server Yes No Valid user name
CAMPAIGN_DC_DEFAULTPASSWORD This property expects the password of the user (given above) which has access to datacontext. Implementation specific Server Yes No Valid password
CAMPAIGN_DC_<DataContextId>_USERNAME This property expects the username of the user which has access to datacontext. This must be configured for every new datacontext. Implementation specific Server Yes No Valid user name
CAMPAIGN_DC_<DataContextId>_PASSWORD This property expects the password of the user (given above) which has access to datacontext. This must be configured for every new datacontext. Implementation specific Server Yes No Valid password
CAMPAIGNS_CAROUSEL_NUMBER This property expects the number of images which can be displayed in a Carousel on screen for Campaigns. Implementation specific Server Yes No 3
CAMPAIGN_THREAD_POOL_SIZE Campaign engine serving threads size. Implementation specific Server  Yes No 2
CAMPAIGN_CACHE_EXPIRY Expiry in seconds for the Cache storage related to Campaigns. Implementation specific Server No No 86400 is the default value if this is not configured.
DBP_AC_AUTH_BASE_URL Auth URL of the Fabric Workspace on which KonyBankingAdminConsole Fabric Application has been configured.
  • Navigate to Publish tab of DigitalBanking-Composite Quantum Fabric Application.
  • Click on the Published indicator and retrieve the Service URL.
Server Yes No https://{baseURL}
DBX_RESETPASSWORD_EMAIL This property is used to generate dynamic password resent link. <<onlinebanking url>>/#_frmResetPassword Server Yes No https://{baseURL}/apps/KonyOLB/#_frmResetPassword
DBP_ENROLL_EMAIL This property is used as user communication when enrolling user does not have email id setup. Implementation specific Server No No Valid email address
DBP_ENROLL_PHONE This property is used as user communication when enrolling user does not have phone number setup. Implementation specific Server No No Valid phone number
UPGRADETOMB_ENROLL_LINK This property contains online banking URL which is sent when user upgrades from retail user to business user. Implementation specific Server Yes No https://{baseURL}/apps/KonyOLB
SAC_PREFERENCE_CRITERIA This property is used to configure display setting of communication for MFA. This property can have three values : DISPLAY_NO_VALUE, DISPLAY_ALL, and DISPLAY_PRIMARY. Server Yes No DISPLAY_NO_VALUE, DISPLAY_ALL, DISPLAY_PRIMARY
ENGAGE_URL Journey manager engagement URL. Implementation specific Server No No https://edi.pivotusengage-sandbox.com
ENGAGE_ADMIN_USER Journey manager engagement admin username. Implementation specific Server No No Valid user name
ENGAGE_ADMIN_PASSWORD Journey manager engagement admin user password. Implementation specific Server No No Valid password
LOG_SCHEMA_NAME Schema name for logging events. This is required only when party template is deployed. Implementation specific Server Yes No logschema name
PARTY_HOST_URL Party Host URL for creating party. This is required only when party template is deployed. Implementation specific Server Yes No Party_Host_URL
SERVICEKEY_EXPIRE_TIME MFA Service key expire time in seconds. Implementation specific Server Yes No 10
SAVINGSPOT_HOST_URL Savings Pot microservice URL. Implementation specific Server Yes No http://{URL}
SAVINGSPOT_ROLE_ID

To set the value for roleId parameter to be added in headers.

Note: SAVINGSPOT_DEPLOYMENT_PLATFORM and SAVINGSPOT_AUTHORIZATION_KEY parameters are mandatory when the MS application is deployed in AWS or AZURE platform. In other cases, these parameters are not mandatory.

SavingsPot MS implementation specific Server Yes No ADMIN
SAVINGSPOT_DEPLOYMENT_PLATFORM

To specify the deployment platform like AWS, Azure.

Note: SAVINGSPOT_DEPLOYMENT_PLATFORM and SAVINGSPOT_AUTHORIZATION_KEY parameters are mandatory when the MS application is deployed in AWS or AZURE platform. In other cases, these parameters are not mandatory.

SavingsPot MS implementation specific Server Yes No azure
SAVINGSPOT_AUTHORIZATION_KEY

To specify the actual x-api-key for AWS (or) x-functions-key for Azure.

Note: SAVINGSPOT_DEPLOYMENT_PLATFORM and SAVINGSPOT_AUTHORIZATION_KEY parameters are mandatory when the MS application is deployed in AWS or AZURE platform. In other cases, these parameters are not mandatory.

SavingsPot MS implementation specific Server Yes No Valid key
EFS_USERNAME This property is used to connect to EFS document management system to retrieve documents. Implementation specific Server Yes No Valid password
EFS_PASSWORD This property is used to connect to EFS document management system to retrieve documents. Implementation specific Server Yes No Valid password
EFS_ACCOUNT_NUMBER This property is used to connect to EFS document management system to retrieve documents. Implementation specific Server Yes No 110008
EFS_CUSTOMERID This property is used to connect to EFS document management system to retrieve documents. Implementation specific Server Yes No 193466
EFS_HOST_URL This property is used to connect to EFS document management system to retrieve documents. Implementation specific Server Yes No http://{baseURL}:portnumber/rest/v1
CACHE_ENABLED To determine whether cache support is enabled for all the cache related operations in the environment. Implementation specific Server Yes No
  • true - In case Cache Support Required
  • false - In case Cache Support Not Required
CACHE_REFRESHDURATION The Cached data must exist for the specified amount of time; post the mentioned time, the cache is invalidated (time in seconds). Implementation specific Server Yes No 300
IS_SCA_ENABLED This property must be set to "True" when MFA components are replaced with SCA components. Implementation specific Server Yes Yes Default value is False
AM_REQUIRE_APPROVALS_FOR_ENTITY_TYPE Approval matrix is enabled for customers belonging to Entity Type mentioned in the value of this parameter. Implementation specific Server No No Values can be – TYPE_ID_RETAIL TYPE_ID_BUSINESS TYPE_ID_RETAIL, TYPE_ID_BUSINESS Default value – TYPE_ID_BUSINESS
AM_MAX_LIMIT_NO_RULES_ALLOW_STP Value true => enables STP even if no approval matrix rule is specified for max limit. Value false => throws error if approval matrix rule is not specified for max limit. Implementation specific Server No No Values can be – true/false Default value - true
AM_DAILY_LIMIT_NO_RULES_ALLOW_STP Value true => enables STP even if no approval matrix rule is specified for daily limit. Value false => throws error if approval matrix rule is not specified for daily limit. Implementation specific Server No No Values can be – true/false Default value - true
AM_WEEKLY_LIMIT_NO_RULES_ALLOW_STP Value true => enables STP even if no approval matrix rule is specified for weekly limit. Value false => throws error if approval matrix rule is not specified for weekly limit. Implementation specific Server No No Values can be – true/false Default value - true
AM_NON_MONETORY_NO_RULES_ALLOW_STP Value true => enables STP even if no approval matrix rule is specified for non-monetary limit. Value false => throws error if approval matrix rule is not specified for non-monetary limit. Implementation specific Server No No Values can be – true/false Default value - true
AM_MODE_DEFAULT_SIGN_GROUP

For value true => default approval mode is set to Signatory group.

For false => default approval mode is set to User mode.

Implementation specific Server No No Values can be – true/false Default value - false
Wealth application run-time parameters
WEALTH_CORE This property specifies the core backend for the wealth services. Implementation specific Server Yes No refinitiv,mock
WEALTH_MKT_APPID Wealth Market provider application ID Implementation specific Server Yes No Valid app ID
WEALTH_MKT_PWRD Wealth Market provider password Implementation specific Server Yes No valid password
WEALTH_MKT_USER Wealth Market provider username Implementation specific Server Yes No Valid username
WEALTH_T24_HOST_URL Base URL of Fabric run-time on which the Wealth T24 services has been deployed. Implementation specific Server Yes No http://{baseurl}:port/irf-provider-container/api/
WEALTH_REC_ACT_DAYS Number of days configuration for wealth recent activity card. Implementation specific Server Yes No 30
WEALTH_TAP_HOST_URL Base URL of Fabric run-time on which the Wealth TAP services has been deployed. Implementation specific Server Yes No http://{baseURL}:portnumber/triplea/api/

The following is the list of configurable client parameters for the Quantum Fabric app(s):

  • MB_ENABLE_INAPP_CAMPAIGNS
  • MB_ENABLE_POPUP_CAMPAIGNS
  • OLB_ENABLE_INAPP_CAMPAIGNS
  • OLB_ENABLE_POPUP_CAMPAIGNS
  • DUAL_BALANCE
  • ADVANCED_FEATURE_SELECTION. Value is TRUE.

Update Global Throttling Configuration

  • Navigate to App Services > settings > Runtime Configuration.
  • Update the following JSON to Global Throttling Configuration.
  • [
        {
            "resourcePath": "RBObjects/DbxUser",
            "httpMethod": "verifyDbxUserName",
            "totalRateLimitPerMinute": 10000,
            "ipRateLimitPerMinute": 20
        }
    ]
    

Update Excluded Operation for HTTP Integrity

Navigate to App Services > settings > Runtime Configuration.

Update below JSON to HTTP Integrity Configuration.

            Excluded Operations
        
[
  {
    "resourcePath": "RBObjects/SecureMessaging",
    "httpMethod": "createCustomerRequest"
  },
  {
    "resourcePath": "RBObjects/SecureMessaging",
    "httpMethod": "getMessageAttachment"
  },
  {
    "resourcePath": "RBObjects/DownloadTransaction",
    "httpMethod": "GET"
  },
  {
    "resourcePath": "RBObjects/DownloadTransactionReport",
    "httpMethod": "GET"
  },
  {
    "resourcePath": "RBObjects/uploadDocuments",
    "httpMethod": "CREATE"
  },
  {
    "resourcePath": "dbpBulkWireServices/downloadFileBulkWire",
    "httpMethod": "POST"
  },
  {
    "resourcePath": "dbpBulkWireServices/downloadSampleFileBulkWire",
    "httpMethod": "POST"
  },
  {
    "resourcePath": "dbpBulkWireServices/UploadBWFile",
    "httpMethod": "POST"
  },
    
  {
    "resourcePath": "LocationObjService/LocationsUsingCSV",
    "httpMethod": "importLocations"
  },
  {
    "resourcePath": "CustomerGroupsAndEntitlObjSvc/Group",
    "httpMethod": "CustomerAssignRole"
  },
  {
    "resourcePath": "LocationObjService/LocationsUsingCSV",
    "httpMethod": "downloadLocationsCSV"
  },
  {
    "resourcePath": "DecisionManagement/decision",
    "httpMethod": "DownloadRulesFile"
  },
  {
    "resourcePath": "CustomerManagementObjService/CustomerRequest",
    "httpMethod": "downloadMessageAttachment"
  },
  {
    "resourcePath": "AuditLogsObjSvc/TransactionAndAuditLogs",
    "httpMethod": "exportAdminConsoleLogs"
  },
  {
    "resourcePath": "AuditLogsObjSvc/TransactionAndAuditLogs",
    "httpMethod": "exportTransactionalLogs"
  },
  {
    "resourcePath": "StaticContentObjService/service",
    "httpMethod": "downloadFeaturesList"
  },
  {
    "resourcePath": "RolesAndPermissionsObjService/permissions_view",
    "httpMethod": "downloadPermissionsList"
  },
  {
    "resourcePath": "ReportsObjService/MessagesReport",
    "httpMethod": "exportMessagesReport"
  },
  {
    "resourcePath": "StaticContentObjService/service",
    "httpMethod": "downloadServicesList"
  },
  {
    "resourcePath": "RolesAndPermissionsObjService/role_view",
    "httpMethod": "downloadRolesList"
  },
  {
    "resourcePath": "CustomerGroupsAndEntitlObjSvc/Group",
    "httpMethod": "downloadGroupsList"
  },
  {
    "resourcePath": "InternalusersObjService/internalUsers_view",
    "httpMethod": "downloadUsersList"
  }
]

Publish the Application

Publish the Quantum Fabric App(s) as per the procedure described here. After a successful publish, the status of an application shows as below. Once publish is done, restart the server to reflect throttling configuration.

To publish the composite app, first publish the corresponding Micro Apps and then only publish the composite app to avoid sync issue.

 

Copyright © 2020- Temenos Headquarters SA

Published on :
Thursday, May 30, 2024 11:42:24 AM IST