How and where to add language properties file for hindi in 7.3

[Former Member]

Hi,

I want to add Hindi as a language in SAP NetWeaver Portal 7.3. I am unable to drill down to file where the language properties are kept.

I want to know which file to modify, the path to the file and how to go about adding hindi as a language.

I couldn't find anything in accordance with SAP NetWeaver Portal 7.3; although 7.1 options are there, but 7.3 is different.

Please guide.

[Former Member · Accepted solution]

Hi,

Take a look at the following links:

[http://help.sap.com/saphelp_nw73/helpdata/en/49/dba57d5dba551de10000000a42189c/frameset.htm]

[http://help.sap.com/saphelp_nw73/helpdata/en/45/fff338e19134dde10000000a1553f7/frameset.htm]

Regards,

Alex

[Former Member · Accepted solution]

Hi,

I couldn't find the language properties under sap.com_tcsec_umeuseradmin.war

file where hindi properties file can be added,

I changed the com.sap.portal.admin.wizardframework.war file to add hindi properties to the file and added hi for

hindi in the locale list service

Then,I changed the com.sap.portal.navigation.masthead.war to add headeriView_nls_hi.properties file for hindi.

After that, I deployed the two war files by specifying a different context roots for them, they were deployed

successfully. Ideally, hindi should be displayed in the masthead.

Yet it is not showing. Actually looks like the original components are still active and have not been overwritten, any idea what could have gone wrong??

[Former Member · Accepted solution]

I found that original components have not been overwritten, instead the ear files have been deployed and a new folder name has

been created (example.com) in the server which was provided as the provider name in application j2ee engine.xml.

the folder has been created in the server

/usr/sap/EP1/J05/j2ee/cluster/server0/temp/tc_jewebservices~srv/apps/example.com name of the folder

Ideally since I am modifying the standard 7.3 war files, the original war files should be replaced. But while deploying, if I deploy

with the same context root as that of the standard, it doesn't allow me to deploy stating already same context root is present on the server. But a different context root doesn't serve my purpose. So I am unable to achieve the objective of war files modification.

Any inputs on the above would be helpful..