This content has been marked as final. Show 2 replies
Planning 220.127.116.11 is a localized version and should display characters correctly in reports. However, the necessary fonts are only installed to:
This JRE is used by Tomcat, so if you are using Tomcat as your web application server then characters will display correctly. However, if you are using Weblogic or Websphere you will need to copy the fonts from the above location to:
After copying over the fonts, restart the Planning service before testing.
Hope this helps.
Once we had a similar problem in Arabic and this is the response we've got from Oracle support. It resolved our issue and I'm sure it can do the trick for you if you set it for your own choice of language.
Q1 What is ESSLANG on the Essbase server set to?
Q2 What is ESSLANG in the \hyperion\products\biplus\lib\fr.env file on the FR server set to?
It maybe that you have experienced BUG 8392323
If the ESSLANG on the Essbase and FR server(s) is set properly this shouldn’t be an issue, but it looks like you might be running into this bug.
In order for essbase/FR to handle dimension-names, member-names, etc which
contain special characters, the ESSLANG environment variable on the essbase
server machine needs to be set properly:
ESSLANG= Arabic - Saudi Arabia (ISO)@Binary
Also a solution to this problem would be to use the Essbase APS ADM driver rather then the Essbase Native ADM driver. The APS driver can be used by setting the UseEssbaseEDS=1 in fr_global.properties:
You also need to set the ESSLANG environment variable in the fr.env file rather then or in addition to the computers environment variables. To do this edit \hyperion\products\biplus\lib\fr.env and change the ESSLANG to:
ESSLANG=S Arabic - Saudi Arabia (ISO)@Binary
Once these changes have been made restart the services.