My Oracle Support Banner

Entity Tag Not Available In Assemblers As Part Of Multi Entity Integration (Doc ID 2749290.1)

Last updated on APRIL 19, 2021

Applies to:

Oracle Banking Digital Experience - Version 20.1.0.0.0 to 20.1.0.0.0 [Release 20]
Information in this document applies to any platform.

Symptoms


Entity Tag Not available in Assemblers as part of multi entity integration

As part of multi entity integration, OBP system is expecting ENTITY tag that need to be added as part of request xml's (as part of header), currently in OBDX Payment assemblers there is no placeholder support to pass the entity id's as part of the request, which ideally should have supported in case of multi entity setup.


This issue is faced on all payment screens, and all webservice calls done from OBDX to OBPM
 

In multi-entity OBPM setup, Entity ID is mandatory.  

 

 

STEPS

-----------------------

The issue can be reproduced at will with the following steps:

1) Initiate own account transfer.(Now option)

2) So that it will fetch value date from OBPM.

3) Now fetchdate from OBPM is webservice call & in that webservice call we

are not sending ENTITY ID.

 

In multi-entity OBPM setup, Entity ID is mandatory.

 

ERROR

-----------------------

 

com.ofss.digx.infra.exceptions.Exception: System cannot process the request

currently. Please try later.

at java.lang.Thread.getStackTrace(Thread.java:1559)

at

com.ofss.digx.infra.exceptions.ExceptionTransformer.buildException(ExceptionTr

ansformer.java:457)

at

com.ofss.digx.infra.exceptions.ExceptionTransformer.build(ExceptionTransformer

.java:892)

at

com.ofss.digx.extxface.obpm144.response.AbstractResponseHandler.analyseRespons

e(AbstractResponseHandler.java:45)

at

com.ofss.digx.extxface.obpm144.impl.core.CoreApplicationServiceAdapterResponse

Handler.checkResponseCheckNextWorkingDay(CoreApplicationServiceAdapterResponse

Handler.java:100)

at

com.ofss.digx.extxface.obpm144.impl.core.CoreApplicationServiceAdapter.checkNe

xtWorkingDay(CoreApplicationServiceAdapter.java:167)

at

com.ofss.digx.domain.commonservice.core.entity.branchdates.repository.adapter.

RemoteBranchDatesDefinitionRepositoryAdapter.checkNextWorkingDay(RemoteBranchD

atesDefinitionRepositoryAdapter.java:77

 

 

 

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.