Comments on: Problem Determination and WebSphere Integration Developer

By: dan

dan — Thu, 22 May 2008 13:59:18 +0000

The artifacts that are generated by WID and consumed by process server are UTF-8 (Unicode) encoded. You should be able to you use your Japanese character sets without issue.

If you find that you DO run into something, then open a PMR for it because everything should be i18n.

In the future, please use the newsgroups for questions. I monitor them obsessively and theres more opportunity for responses than here.

By: akkachotu

akkachotu — Thu, 22 May 2008 10:00:11 +0000

Those are nice tips on WID. Thank you. I have one question.

I use Windows XP SP2 + IBM DB2 9.1 + WID 6.1.
We have a requirement to store Japanese characters(that includes characters from Japanese language sets like Kanji, Hiragana, Katakana) + English characters in DB2. When the user enters some data (that includes Japanese characters + English characters) on the client side then that data flows through the application calls that route the data through the BPEL process and then into the database.

Say we need to do write some logic using various BPEL constructs available in WID like choice activity, receive activity, reply activity, receive choice, correlation sets etc. then will there be a problem when we use such logic using Japanese characters ? How will WID behave in cases where your BPEL constructs work on Japanese characters ? Do we have to change the codeset/codepage of WID/WebSphere for working with Japanese characters ?

Please clarify.

By: Richard

Richard — Wed, 21 May 2008 15:48:40 +0000

There’s a trick in 6.1 to quickly delete the generated J2EE projects. Right-click your module without leaving the BI view, then select Close Project. This deletes all the generated projects. Next, reopen it and they will be regenerated.