Re: Web service wizard fails to bring up a service -- this time with exceptions

To add to the discussion, an article, "Unlocking IBM Integrated Web Application Server", just showed up today in the online IBM Systems magazine -

http://www.ibmsystemsmag.com/ibmi/web_application_server_J2EE/34123p1.aspx

is the title, and it seems to cover some basic stuff. Not sure if it would've helped James get started, though.

Vern

On 9/22/2010 7:20 PM, Ryan Watkins wrote:

This is definitely a Java Toolbox related error. IWS is attempting to
use method setCCSID(), however the installed Toolbox code on the system
isn't up to date so IWS is running into issues.

Ideally you should try to install the latest Java group PTF on the
customers system. If that isn't an issue at this time, then I recommend
installing one of these Java PTF's depending on what OS release you are
running.

7.1 SI40988
6.1 SI40983
5.4 SI40987

Installing the correct PTF above should resolve the issue.

Ryan Watkins



On 09/22/2010 02:11 PM, James H. H. Lampert wrote:

James H. H. Lampert wrote:

I'll know more after lunch.

I've been told by my contact in Rochester that the warning messages that
Mr. Helgren pointed out are probably not relevant.



I've just successfully externalized and called a functionally identical
program on our V6 box, accessing structurally identical files, to the
situation on the customer box, and everything worked perfectly.

The only difference is that I've been using the "Deploy new service"
wizard (accessed through the "Deploy" button on "Manage Deployed
Services"), rather than the "Create Web Services Server" wizard.

It seems to me that the most interesting bit out of that whole
peroration that was in the customer box's log was:
>
/www/WSERVICE/webservices/temp/WTWSQTHDRR_1285175825985/services/WTWSQTHDRR/iseries/programcall/base/RuntimeContext.java:217:

> cannot find symbol symbol : method setCCSID(int) location: class
> com.ibm.as400.access.AS400ConnectionPool
> toolboxConnectionPool_.setCCSID(connPoolCCSID_); ^ 1 error

Any thoughts on what could cause something that works beautifully here
to refuse to even externalize out in the real world?

--
James H. H. Lampert
Touchtone Corporation