As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I had a need to convert Unicode Hex string to corresponding characters in a report. For example, the Unicode Hex string "738B 514B 52E4" will be converted to Chinese characters "王克勤".
I would be happy to hear any suggestions.This message has been edited. Last edited by: FP Mod Chuck,
Can anyone tell me if I can use "Alpha variables in bytes - Unicode only" as the DBMS/Source data type in the master file for hexadecimal string?
If yes, what's the right data format? i.e, "738B 514B 52E4" or "\u738B\u514B\u52E4"?
In addition, I find that WebFocus provides a function called UFMT for the purpose of converting character strings to "hex" but I'm looking for opposite way of this data conversion.This message has been edited. Last edited by: yehf,
Pop those characters into flat file with the proper encoding (utf8 should be sufficient). Create a master file with a codepage of 65001. You should be able to query it at that point.
Here is the kicker: You will have to change the default encoding of your server to 65001 (utf8) if you intend on having the output show the proper character encoding. If you change the server codepage to 65001, then you will not have to add the codepage setting to your master, as it will always use the default.
You will then have to change the codepage for both the WF client web application, and for your application server as well. If you don't have everyone on the same encoding, then strange things can happen to your output.
You should probably verify this with IB Customer Support.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
Yes, we did all necessary configurations to support UTF-8 on WebFocus client and report server.
The problem lies with the data in hexadecimal format. If WebFocus doesn't provide functions to convert data from hexadecimal to unicode string, I may have to use Oracle UNISTR('string') function to convert the data first.