I am using the WebSphere v4.0 Test Environment Server Instance right now
when I get the error about UTF-8.

(I haven't added the Tomcat server instance yet.  We do have it, but I
haven't figured out how to add it yet.)

In WDS, in the Servers Perspective, on the Environment tab for my test
server, I have the client.encoding.override value set to UTF-8, like the
manual said to.  I have saved the change and restarted the server and the
application.  When I launch the Start page it brings up my 5250 screen in
the browser.  When press F3 I get the UTF-8 error.

Thank you for responding with your helpful comments.

Troy Modlin
Systems Analyst
Group Dekko Services
PO Box 2000
Kendallville, IN 46755
Phone:  260-347-3100 x70395
Cell:      260-318-2910
FAX:     260-349-2021
email:    troym@dekko.com



                    Buck Calabro
                    <Buck.Calabro@com       To:     web400@midrange.com
                    msoft.net>              cc:
                    Sent by:                Fax to:
                    web400-admin@midr       Subject:     RE: [WEB400] Re: 
webfacing first try error:
                    ange.com


                    09/13/2002 11:52
                    AM
                    Please respond to
                    web400






Please let us know if Greg's post helped; perhaps it needs to go into the
FAQ!

Here are other options to consider:

...advice from the newsgroup ibm.software.websphere.studio400 by Per
Wallhoff.

BEGIN QUOTE
I found out how to make tomcat  4.1.9 able to respond whith utf-8.

I just copied the following lines from example application together whith
the relevant folder and now it works.
(I also adjusted the param-value EUC_JP to UTF-8)

Good luck anyone trying to work whit the tomcat server.

PerW

<!-- Example filter to set character encoding on each request -->
<filter>
<filter-name>Set Character Encoding</filter-name>
<filter-class>filters.SetCharacterEncodingFilter</filter-class>
<init-param>

<param-name>encoding</param-name>
<!-- <param-value>EUC_JP</param-value> -->
<param-value>UTF-8</param-value>

</init-param>
</filter>

<!-- Example filter mapping to apply the "Set Character Encoding" filter to
*all* requests processed by this web application -->

<filter-mapping>
<filter-name>Set Character Encoding</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>

<!-- Define example application events listeners -->
<listener>
<listener-class>listeners.ContextListener</listener-class>
</listener>

<listener>
<listener-class>listeners.SessionListener</listener-class>
</listener>
END QUOTE

Harry Tian offers this advice

BEGIN QUOTE
Just disable the UTF-8 support in your WF project, because you couldn't
configure UTF-8 support in Tomcat. If your application is in English, it
should be OK. Please follow the instruction on how to setup WF project in
VAJ WTE.

There is wfapp.properties file in conf subdirectory,
1) if you are using WDT5.1+SP5:
set parmeter {WFWTE} = true
2) if you are using WDSC4.0+SP1
set parmeter {WFForce_UTF8} = true

Note, we do NOT officially support Webfaced application running in Tomact.
The application server we support is: IBM WebSphere Application Server (
V4.0 AE, V4.0 AEs, V3.5.x AE, V3.5.x SE)
END QUOTE
_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/web400
or email: WEB400-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.






As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.