Hi,

The initial problem seems to be with the HTTP server plug-in that is being
used. Not sure what the problem is there.

As for versions, that is what we are talking about. The version of the
web services server. Current there are three: 1.3, 1.5, and 2.6.



"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 12/14/2015
01:35:09 PM:

From: rob@xxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/14/2015 01:35 PM
Subject: RE: Web Service fails to start after upgrade to IBM i 7.2
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

I think that's web servers you're seeing. Not web services.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 12/14/2015 01:41 PM
Subject: RE: Web Service fails to start after upgrade to IBM i
7.2
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Rob,

From a V7R1 system, latest CUM, TR11, latest groups
Using the IBM Navigator for i
IBM I Tasks page
IBM Web Administration
Application Server Tab - All servers
Version column will show the version that was used to create the Web
Service.
I'm showing V1.3, V1.5, V2.6 for various Web Services.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, December 14, 2015 1:00 PM
To: Midrange Systems Technical Discussion
Subject: RE: Web Service fails to start after upgrade to IBM i 7.2

I also found this directory structure a little confusing. I see <snip>
http://gdihq2:10010/web/services/PRCCST1Service/PRCCST1?wsdl
</snip>
Closest I can find is
/www/WSERVICE/webservices/services/PRCCST1
In there I see:
services.xml
MANIFEST.MF
PRCCST1.wsdl

Perhaps there's some redirect somewhere?

Is this the 1.whatever?
/www/WSERVICE/webservices/services/PRCCST1/META-INF/MANIFEST.MF
....+....1....+....2....+....3....+....4....+
************Beginning of data**************
Manifest-Version: 1.0
Created-By: 1.5.1 (IBM Corporation)
************End of Data********************

The contents of /WEB are only two html files.



Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: rob@xxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/14/2015 12:30 PM
Subject: RE: Web Service fails to start after upgrade to IBM i
7.2
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I am in
WSERVICE > Manage Deployed Services > Service Properties
Service information Display help for this form.
Name: PRCCST1
Description: Return cost and price
Startup type: Automatic
Service install path: /www/WSERVICE/webservices/services/PRCCST1
Program: /QSYS.LIB/ERPLXUSRO.LIB/PRCCST1.PGM
Web service definition URL:
http://gdihq2:10010/web/services/PRCCST1Service/PRCCST1?wsdl
User ID for this service: *SERVER

Question 1: Where do I see this version 1.whatever?
Question 2: Where is this wizard to upgrade it?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>
Date: 12/14/2015 10:20 AM
Subject: RE: Web Service fails to start after upgrade to IBM i
7.2
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Rob,

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.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, December 14, 2015 9:59 AM
To: midrange-l@xxxxxxxxxxxx
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
following:
CPF1124-Job 956026/QTMHHTTP/WSERVICE started

Message . . . . : -CALL PGM(QHTTPSVR/QZHBMAIN) PARM('-S' 'WSERVICE'
'-uiMin' '10' '-uiMax' '40' '-cEAMap' '*CCSID' '-cAEMap' '*CCSID'
'-uiCCSID' '819'
'-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?




Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2019 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].