4 Troubleshooting Application Workflows

This topic describes the troubleshooting functional workflows applicable to Oracle Banking Virtual Account Management.

This topic contains the following subtopics:

• Oracle Banking Virtual Account Management – Subdomains List
  This topic describes about the Oracle Banking Virtual Account Management Subdomains List.
• Troubleshooting SMS Errors
  This topic describes about Troubleshooting SMS Errors.
• Oracle Banking Routing Hub Configuration
  This topic describes about Oracle Banking Routing Hub configuration.

4.1 Oracle Banking Virtual Account Management – Subdomains List

This topic describes about the Oracle Banking Virtual Account Management Subdomains List.

Figure 4-1 Composition of Oracle Banking Virtual Account Management

Description of "Figure 4-1 Composition of Oracle Banking Virtual Account Management"

On successful login, the Oracle Banking Virtual Account Management dashboard screen appears depending on the user privileges.

Figure 4-2 Oracle Banking Virtual Account Management Dashboard

Description of "Figure 4-2 Oracle Banking Virtual Account Management Dashboard"

User Role Issues

Role Profile includes access rights to the functional activities that are common to a group of users. A user can be linked to a Role Profile by which you give the user access rights to all the functional activities in the Role Profile.

1. On Home screen, click Security Management. Under Security Management, click Role.

   The Role Maintenace Screen displays.

   Figure 4-3 Role Maintenace

   
   

   
   Description of "Figure 4-3 Role Maintenace"

   
   

Only authorized users can access the system with the help of a unique User Login ID and password. The user profile of a user contains the details of the user in four sections - User details, Status, Other details and User role branches.

1. From Home screen, click Security Management. Under Security Management, click User.
   The User Maintenace Screen displays.

   Figure 4-4 User Maintenace

   
   

   
   Description of "Figure 4-4 User Maintenace"

   
   

   Note:

   Make sure that the required Role and User Applications are mapped to the user.

This topic contains the following subtopics:

• First level issues
  This topic describes the possible issues that may occur during the basic investigation.
• Call is Failing in Oracle Banking Routing Hub / Accounting Call (FCUBS)
  This topic provides the troubleshooting information about the call is Failing in Oracle Banking Routing Hub / Accounting Call (FCUBS).
• Transaction Data Verification
  This topic provides the systematic instruction to verify the transaction data.
• OBIC Call is Failing
  This topic provides the systematic instructions if OBIC call is failing.

4.1.1 First level issues

This topic describes the possible issues that may occur during the basic investigation.

Error Message not shown

If there are any improper calls, check the ERTB_MSGS table of the respective schema to understand the cause of the error.

1. Press F12 to open the Networks.
2. Check the error code in the response.

Query: SELECT * FROM ERTB_MSGS WHERE ERR_CODE=’GCS_AUTH-03’

Figure 4-5 Error Code

Description of "Figure 4-5 Error Code"

Setting Log file path

Log generation path needs to be defined in PLATO_LOGGER_PARAM_CONFIG table of PLATO schema.

Query: Select * from PLATO_LOGGER_PARAM_CONFIG;

Figure 4-6 PLATO_LOGGER_PARAM_CONFIG

Description of "Figure 4-6 PLATO_LOGGER_PARAM_CONFIG"

Dynamic log generation issues

For generating dynamic service logs, insert the data to PLATO_DEBUG_USERS table.

Query: Select * from PLATO_DEBUG_USERS;

Figure 4-7 Service Logs

Description of "Figure 4-7 Service Logs"

Figure 4-8 PLATO_DEBUG_USERS

Description of "Figure 4-8 PLATO_DEBUG_USERS"

Call is failing in Gateway

If any API call is failing in Gateway, hit the same API endpoint without passing through api-gateway via the postman.

Figure 4-9 API Gateway

Description of "Figure 4-9 API Gateway"

Note:

Restart the specific services if required.

Exact error through exception log

If there is an exact error through the exception log, log in to WINSCP and check the server logs with NIS credentials.

The path is /scratch/obvam/app_logs/UserLogs.

Figure 4-10 Exception Error Log

Description of "Figure 4-10 Exception Error Log"

Logs are not generated

If you are not getting logs, put the loggers across API, hit through postman, and test again.

Figure 4-11 Postman

Description of "Figure 4-11 Postman"

4.1.2 Call is Failing in Oracle Banking Routing Hub / Accounting Call (FCUBS)

This topic provides the troubleshooting information about the call is Failing in Oracle Banking Routing Hub / Accounting Call (FCUBS).

If any call is failing in Oracle Banking Routing Hub, open the CMC_RH_AUDIT_EVENT_LOG for getting Gateway response (SUCCESS or FAILED).

Select the following query to verify results.

Query: select * from CMC_RH_AUDIT_EVENT_LOG

Figure 4-12 CMC_RH_AUDIT_EVENT_LOG

Description of "Figure 4-12 CMC_RH_AUDIT_EVENT_LOG"

Code Error in GCS Side

If there is any error in GCS side codes, use java de-complier to debug the error.

404 Error

The possible causes for 404 error are as follows:

• Check service is not running on Eureka.
• Check service is not deployed in WebLogic.

500 Internal Error

The possible causes for 500 Internal error are as follows:

• Issue with Plato entries
• Issue with Eureka
• Issue with any peace of code

The server-side debugging is needed for the above-mentioned issues, if it is not captured in logs.

4.1.3 Transaction Data Verification

This topic provides the systematic instruction to verify the transaction data.

1. In the IN request and OUT response, make sure that all the field data is going to service side.
2. If there is any error related to SMS, check for the availability of SMS entries.
3. Validate the endpoints and data.
4. Make sure that the data entered on the screen is accurate.
   For example, the Account Number should be valid.

   Figure 4-13 Create Journal Online

   
   

   
   Description of "Figure 4-13 Create Journal Online"

   
   

4.1.4 OBIC Call is Failing

This topic provides the systematic instructions if OBIC call is failing.

1. If the OBIC call is failing, check the EIE_TB_MSG_REQ_LOG and EIE_TB_MSG_RES_LOG in EIE schema for getting the response (SUCCESS or FAILURE).
2. Select the following query to verify results.
   Query: Select * from EIE_TB_MSG_RES_LOG

   Figure 4-14 EIE Schema

   
   

   
   Description of "Figure 4-14 EIE Schema"

   
   

4.2 Troubleshooting SMS Errors

This topic describes about Troubleshooting SMS Errors.

The possible issues occur in Security Management System are mentioned below.

• Unable to login after launching the application.
• Menus are not displayed after logging in.

4.3 Oracle Banking Routing Hub Configuration

This topic describes about Oracle Banking Routing Hub configuration.

Refer to Routing Hub Configuration User Guide for the detailed explanation.