Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED] Switching Adapter to UNICODE - Thoughts?

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] Switching Adapter to UNICODE - Thoughts?
 Login/Join
 
Member
posted
Received word that our adapter will be changing to support a Unicode environment (we are ASCII today). Looking for input from those with experience in this type of change and how it impacted WebFOCUS report code, functions, report caster (bursting), etc. Specifically targeting discussions on An > AnV format changes, though interested in any other gotcha's or areas to pay special attention to.

PS: In Focus for 6+ years. First Forum post. Woo.

This message has been edited. Last edited by: Tamra,


WF 8.0.09. Report Caster. All Outputs. MS Win10/Ofc 13. IE 11.713
 
Posts: 2 | Registered: February 06, 2017Report This Post
Virtuoso
posted Hide Post
In a nutshell, no biggie.

For a little more detail, you are probably going to want to use UTF8 as the default encoding type for Unicode characters. For WF, that means changing the default code pages of: WFRS, RC, WF Client and Tomcat (or whatever app server you are using). If you miss one of those, then things can get pretty confusing.

For flat file sources, you are going to want to add the CODEPAGE=XXX to the masters. Otherwise it will use the WFRS default. You also may have to rebuild flat file master files, as you may have to define your strings as byte based (e.g. An => AnB, and AnV => AnBV or something like that).

Your functions (like SUBSTR and POSIT) should remain unchanged, as they are character based and not byte based.

Things that may bite you in the arse are -READ and ON TABLE HOLD FORMAT ALPHA. I believe it was fixed for your release, but some versions of the server did byte based -READ rather than character based. Change those to -READFILE and problem solved. For hold files, ALPHA based holds multiply string by 3 when assigning space for the file. This is to accommodate potential multi byte characters. So hold files could increase space usage by a factor of 3. Use a deliminator based hold and that problem will also go away as well.

Hope this helps


"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
 
Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004Report This Post
Guru
posted Hide Post
Tina,

Welcome to Focal Point!

I hope you find the forum a great resource, we have a lot of very knowledgeable contributors.

If you found Darryl's post helpful please let us know either way. We also encourage you to then mark the subject line - Tag your topic with keywords

Feel free to assist others as well too - Big Grin

Thank you for participating in the Focal Point Forum!
Tamra Colangelo
Focal Point Moderator
Information Builders


WebFOCUS 8x - BI Portal, Developer Studio, App Studio, Excel, PDF, Active Formats and HTML5
 
Posts: 487 | Location: Toronto | Registered: June 23, 2009Report This Post
Virtuoso
posted Hide Post
quote:
For hold files, ALPHA based holds multiply string by 3 when assigning space for the file. This is to accommodate potential multi byte characters. So hold files could increase space usage by a factor of 3. Use a deliminator based hold and that problem will also go away as well.


A result of the above can be that HOLD-files of type FOCUS that barely stay within their size/width limits in your ASCII-based environment will break, because they will exceed those limits with UNICODE encoding.
Format XFOCUS is better at handling that, but not all operations are compatible with XFOCUS (DB_INFILE for example).

Also, long An/AnV columns can exceed the limit that FOCUS can handle. For example, an A4000V column will now require up to 12000 bytes, acting as if it were an A12000V column in ASCII land.


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED] Switching Adapter to UNICODE - Thoughts?

Copyright © 1996-2020 Information Builders