0% found this document useful (0 votes)
224 views3 pages

Finacle Support Connect - Vol 7

This newsletter summarizes articles in the July 2020 edition of the Finacle Support Connect Knowledge Series. The articles discuss how to generate menu trees in Finacle based on user application IDs, best practices for disabling directory browsing on application servers, and an overview of the benefits of Finacle Assure for monitoring applications and reducing downtime.

Uploaded by

Aastha Yadav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
224 views3 pages

Finacle Support Connect - Vol 7

This newsletter summarizes articles in the July 2020 edition of the Finacle Support Connect Knowledge Series. The articles discuss how to generate menu trees in Finacle based on user application IDs, best practices for disabling directory browsing on application servers, and an overview of the benefits of Finacle Assure for monitoring applications and reducing downtime.

Uploaded by

Aastha Yadav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Finacle Support Connect | Knowledge Series July 2020 | Vol.

Welcome to the seventh edition of the Finacle Support Connect Knowledge Series, published every fortnight. The articles in this newsletter
are aimed to help you get a deeper understanding of Finacle functionalities. In this edition, we have covered the following articles:
 Did You Know? Menu Tree Generation and Mapping with Application ID
 Best Practices: Disabling Directory Browsing
 Showcase: Finacle Assure
So let’s start reading!

Did You Know?


Menu Tree Generation and Mapping with Application ID
Product: Finacle Core Version 10.x
In the Finacle Core Banking Solution home page, every user is shown the Menu Tree.
The users can invoke the Menu Tree from any screen by clicking the Menu tab on the
top of the Finacle page. The menus that are displayed to each user depends on the list
of menus linked to the Application ID mapped to the user. By modifying the list of
menus linked to the user’s Application ID, the bank can control the display of the Menu
tree structure. In addition, Finacle has the option to group menus under user-defined
headings for easier understanding and access by the end user.
HRRCDM: This is used to create the Application ID. The details are maintained in the RCT table.
HMOPM: This is used for Menu or Menu ID creation and linking the Application ID with the root menu.
HUPM: This helps to create users and attach the Application ID to the User Profile. The details are maintained in the UPR table

Steps to create Menu Tree Structure:

1. Create a two-digit Application ID in HRRCDM menu with the reference type as USER_APPL_NAME
2. Create the “Root Menu” in HMOPM menu. The combination of the user’s Application ID and the Root Menu is unique
3. Link the Application ID to the Root Menu under the General tab in the field Application ID
4. Create the Menu ID through HMOPM and link it to the Root Menu under the Parent Menu tab
5. Link this Menu ID created to the User Menus through the HMOPM under the Parent Menu tab
6. A single menu can be linked to a maximum of 99 Menu IDs
7. Link the Application ID to the User Profile through HUPM
8. Tables involved in this process are AMT, MNO, MNP, MOD, MOD_TXT, OAT, RCT, and UPR

Menu Tree Generation Logic:

1. The menu tree related files are present in the [Link]/mtree folder in the J2EE server
2. Menu tree info is created in the path specified above during user login and the same is retained and referred to for future logins
3. For any menu tree related changes from the front end, the mtree folder contents are cleared and the app server should be restarted

Page 1 of 3
Finacle Support Connect | Knowledge Series July 2020 | Vol. 7

Best Practices
Disabling Directory Browsing
Directory listing is a function that displays files and directories that are present on a server. An
adversary may get access to the application files if the directory listing is not disabled.
To prevent such fallacies, it is advisable to disable the directory browsing at the server level.
The settings indicated below should be implemented both at webserver and application servers.
The details are as follows:
1. WebSphere
 Ensure that the parameter <directoryBrowsingEnabled="false"> is present in [Link]
 Location of the [Link] file
<profile_root>/config/cells/<cell_name>/applications/<EAR name>/deployments/<EAR name>/<WAR name>/WEB-INF/ibm-web-
[Link]
<profile_root>/InstalledApps/<cell_name>/<EAR name>/<WAR name>/WEB-INF/[Link]
2. WebLogic
 Add the below entry in [Link] file:
<container-descriptor>
<index-directory-enabled>false</index-directory-enabled>
</container-descriptor>
 [Link] is located under /WEB-INF directory of application
3. JBOSS(7.x)
 Change the entry as below in both standalone*.xml and [Link] depending on the mode
<servlet-container name="default" directory-listing="false">
 Locations of standalone*.xml and [Link] file are
<JBoss-home>/standalone/configuration/standalone*.xml
<JBoss-home>/domain/configuration/[Link]
4. Oracle HTTP Server
 Open the [Link] file and make the following changes:
o Disable the mod_autoindex module defined in the [Link] file by commenting the following line using '#'
E.g. #LoadModule autoindex_module modules/mod_autoindex.so
o Comment out all the tags that use mod_autoindex module and modify the default directory access permission and set the
Options Indexes to Options None
 Location of the [Link] file is <ORACLE_HOME>\ohs\conf\[Link]
5. IBM HTTP Server
 Open the [Link] file and search for the option Indexes
 Replace the word Indexes with -Indexes, or remove the word Indexes in this line
 Location of the [Link] file is <IBM HTTP Server>\conf\[Link]

Showcase: Finacle Assure


Why should banks go for Finacle Assure?

In today’s world, banks operate in complex IT environments which have too many
applications, multi-tiered architecture, a mesh of modern and legacy platforms,
and numerous interfaces. Customers are connected 24x7 and have a zero
tolerance for service downtime. The IT focus should change from the reactive
mode of MTTR (Mean Time To Repair) to the predictive mode of early warnings
and MTTP (Mean Time To Prevent). Finacle Assure, with its round-the-clock
monitoring capability and predictive Analytics tool, helps the bank in achieving the
high application availability and better customer satisfaction.

Page 2 of 3
Finacle Support Connect | Knowledge Series July 2020 | Vol. 7

Benefits of Finacle Assure

1. 24x7 application monitoring services from the state-of-the-art Infosys Finacle Command Center at Bengaluru, India, assuring smooth
performance of Finacle Suite of applications with minimum unplanned downtime

2. Qualified Command Centre team and subject matter expertise adept at handling critical calls, thereby reducing TAT for root cause
identification and resolution

3. Leverages the capabilities of the internal teams leading to a faster response on alerts, quicker analysis, and restoration

To know more about the case studies, click here.

For a demo on Finacle Assure, please write in to finaclesupport@[Link]

Hope you like this edition. Is there anything that you’d like to see in the forthcoming series? Do let us know!
Write to us at finaclesupport@[Link]
External – Confidential Finacle Digital Communication Services Copyright © 2020 EdgeVerve Systems Limited
To unsubscribe, please click here

Page 3 of 3

You might also like