8.4 Jar Deployment in Weblogic
This topic provides the systematic instructions to the Jar Deployment in Weblogic.
Below screen shows the Jar Deployment in weblogic.
Response:
{
"data": {
"addDtls": {
"signatureVerifyIndicator": "Y",
"hostStatus": null,
"hostMultiTripId": null,
"txnBranchCcy": "GBP",
"txnBranchDate": "2020-03-25T18:30:00.000+0000",
"txnType": "C",
"cashInOutIndicator": "I",
"ejLoggingRequired": null,
"ejTxnAmtMapping": "TO",
"ejTxnCcyMapping": "TO",
"adviceName": null,
"orchestratorId": null,
"rsp": null,
"isReversal": "N",
"crossCcyEnabled": null,
"isTotChargesReq": null
},
"txnDtls": {
"functionCode": "9999",
"txnBranchCode": null,
"txnBranchCcy": null,
"txnBranchDate": null,
"requestStatus": "COMPLETED",
"assignmentMode": null,
"txnId": "71a08a0f-ee2a-405b-a1e3-b77ca9e59b6e",
"txnRefNumber": "0002008600007160",
"tellerSeqNumber": null,
"overrideConfirmFlag": "N",
"supervisorId": null,
"onlineOfflineTxn": null,
"userComments": null,
"authoriserComments": null,
"eventCode": null,
"accountType": "UBS"
},
"dataPayload": {
"datasegment": null,
"fromAccountAmt": 100,
"fromAccountCcy": "GBP",
"toAccountCcy": "GBP",
"beneficiaryName": null,
"beneficiaryAddress1": null,
"beneficiaryAddress2": null,
"beneficiaryAddress3": null,
"beneficiaryAddress4": null,
"identificationType": null,
"identificationNumber": null,
"exchangeRate": 1,
"recievedAccountCcy": null,
"recievedAccountAmt": null,
"totalCha
rges":
null,
"cashAm
ount":
null,
"netAccountCcy": null,
"netAccountAmt": null,
"narrative": "Cash Deposit",
"txnControllerRefNo": null,
"recordId": "bd40562d-06b4-4f95-95fe-
e66fa6eb7f13", "cashAmtCcy": null,
"cashAmt":
null,
"chequeDate": null,
"chequeNumber": null,
"eventCode": null,
"ejId": null,
"emailId": null,
"fromAccountBranch": "000",
"fromAccountNumber": null,
"mobileNumber": null,
"orginalExchangeRate": null,
"payee": null,
"productCode": null,
"reversalDate": null,
"stationId": null,
"toAccountBranch": "000",
"toAccountNumber": "00000008010010",
"toAccountAmt": 100,
"txnBranchCode": "000",
"functionCode": null,
"txnCustomer": null,
"tellerId": null,
"txnDate": 1585161000000,
"txnRefNumber": "0002008600007160",
"txnSeqNumber": null,
"uniqueIdentifierNumber": null,
"uniqueIdentifierType": null,
"userRefNumber": null,
"valueDate": null,
"versionNumber": null,
"referenceNumber": null,
"createdBy": null,
"createdTs": null,
"updatedBy": null,
"updatedTs": null,
"demDtls": null,
"fxInDemDtls": null,
"fxOutDemDtls": null,
"prcDtls": null,
"addDtls": null,
"txnDtls": null,
"overrideDtls": null,
"batchTableDetails": null
},
"extDetails": null,
"warDtls": [],
"authoriserDtls": []
},
"errors": null,
"warnings": null,
"informations": null,
"authorizations": null,
"paging": ""
}
Figure 8-8 Common Core Additional Attributes
- In the debug, the extensible code is used, which is present in the extension jar (obremo-srv-ext-commontxn.jar). Instead stempImpl onCashSubmitTillAcc, FC9999 onCashSubmitTillAcc will be called, where you can add code that is required for the new dataSegment added or to achieve different functionality of charging, accounting, till updates, etc
Parent topic: Extensibility Use Cases for OBBRN Servicing