We have some Web Services.
I've found that the Web Service continues to use the version of software at the time it was generated.
So when enhancements are made to the Web Service engine, I had to do the same thing, blow it away and recreate.
I also had a Web Service break that was secured by SSL, when something changed with SSL, the Web Service broke.
Bottom line, web Services do not like change.
From V7R2 MTU
Integrated web services server changes
Newly created integrated web services servers are based on IAS version 8.5 and include a new web
services engine. Existing web services servers will continue to run if the version of the web services
server engine is 1.5. Web services servers that are running with version 1.3 of the web services engine
must be upgraded to version 1.5 by using the upgrade wizard that is part of the IBM Web Administration
for i GUI. The wizard is shown in the navigation bar if the server is eligible to be upgraded.
It is highly encouraged that customers transition to the new server as soon as they are able to since the
old server runtime and web services engine will be removed in a future release.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, December 14, 2015 9:59 AM
Subject: Web Service fails to start after upgrade to IBM i 7.2
We have this web service we built for consumption by our Domino team.
It fails to start after upgrading from 7.1 to 7.2. Joblog contains the
CPF1124-Job 956026/QTMHHTTP/WSERVICE started
Message . . . . : -CALL PGM(QHTTPSVR/QZHBMAIN) PARM('-S' 'WSERVICE'
'-uiMin' '10' '-uiMax' '40' '-cEAMap' '*CCSID' '-cAEMap' '*CCSID'
'-apache' '-d' '/www/WSERVICE' '-f' 'conf/httpd.conf')
MCH4433-Program import invalid.
Cause . . . . . : The calling program QSVTAP22LF references the item
with export id of X'000000BE' from service program QZSRCORE. The calling program expects the export type of this item to be 1. The actual export type of the item is 2. The export type codes and their meanings are as follows:
0001 - an external procedure, 0002 - an external data item, 0003 - an external thread-local data item. The service program has changed in an incompatible manner since the time the calling program was created.
Technical description . . . . . . . . : Either recreate the calling
program or recreate the service program after checking the export source for the following conditions. If the service program was created with the
LVLCHK(*NO) option then ensure that the order and export type of exported items agrees with previous versions of the service program. If the service program was created with one or more PGMLVL(*PREVIOUS) sections, then ensure that the order and export type of items in each section agree with those in the PGMLVL(*CURRENT) section.
HTP8014-The specified HTTP Server module cannot be added with LoadModule.
The HTTP Server module /QSYS.LIB/QHTTPSVR.LIB/QSVTAP22LF.SRVPGM specified on the LoadModule directive cannot be added into the server. The module name may be misspelled or another error may have occured while attempting to load the module. For more information, see the previous messages in the job log.
Recovery . . . : This message may be a result of attempting to load a
module that is not compatible with the version of the HTTP Server (powered by Apache) currently running on the system. The version of the HTTP Server (powered by Apache) is 20120211 . Contact the provider of the module for service.
Technical description . . . . . . . . : If you are the developer of the
module, look at member AP_RELEASE in file QHTTPSVR/H on the system the module was built on. The AP_RELEASE member contains the version number used by the module. If the version number does not match the version of the HTTP Server (powered by Apache), rebuild the module with the appropriate version of the header file. After performing the appropriate recovery, start the server again.
HTP8008-HTTP Server Instance WSERVICE failed during start-up.
Cause . . . . . : HTTP Server instance WSERVICE failed because of a
configuration error on line 16 in configuration file /www/WSERVICE/conf/httpd.conf. Note: If the specified directive is either a container directive (e.g. <Directory>), or a directive within a container, the line number identified above may not be correct. In that case, you will need to verify that all directives in the container, and the container itself do not have configuration errors. Recovery . . . :
See previous job log messages. Correct the problem and start the server again.
CPC1224-Job ended abnormally.
Line 16 of /www/WSERVICE/conf/httpd.conf LoadModule was_ap20_module /QSYS.LIB/QHTTPSVR.LIB/QSVTAP22LF.SRVPGM
The resolution was <snip>to blow away the web service and recreate it.</snip>
Is there something I missed in the "Memo To Users" or something which would have warned me? Why was this necessary?