Re: IWS installWEbService.sh & Properties

Mitch,

The script is viable way to automate things as you are doing. If you
still have problems, please send me recreate material and I can take a
look.




"WEB400" <web400-bounces@xxxxxxxxxxxx> wrote on 06/22/2017 10:04:17 AM:

From: Mitch Gallman <mgallman@xxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)" <web400@xxxxxxxxxxxx>
Date: 06/22/2017 10:04 AM
Subject: Re: [WEB400] IWS installWEbService.sh & Properties
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>

Yes, I could edit the PCML or just change it when using the web wizard.

However, the documentation says "In addition, any parameter usage
property found in the file overrides any value specified in the -
parameterUsage command option.". This would lead me to believe that
it would then also override the PCML values. However, the install
script instead aborts once it encounters the PCML with inputoutput
parameters for the REST service.

As for scripting, I like making processes easily repeatable,
consumable and easy to maintain. I'm very fast about going through
the wizard now; but I feel that my time can be better utilized if I
can just execute a single command that does everything for me (also
for some reason when setting the library lists in the wizard it
sometimes takes a minute on our system to add a library entry...not
sure if it's related to the IASP or something else).

Now, I can call my script with only specifying the name of the web
Service (optionally, providing additional parameters to override the
server name and program library...for development and QA testing in
a different location). It will un-deploy the web service if it
exists, deploy, set our normal environment and http exports and
restart the web service. I've also worked around the original issue
by adding my own custom values (embedded as comments) to the
properties file that hold the settings that are normally specified
on the command line (e.g. service Name, program library, program
Name, program Type, library List and...parameterUsage). This way I
can have one general purpose script instead of one script for each
web service.

Regards,
Mitch

-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Eric
Sent: Wednesday, June 21, 2017 3:37 AM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] IWS installWEbService.sh & Properties

Hi Mitch,

Is there a reason why it has to be done as part of the script?

As Jon pointed out, the Wizard page allows you to change them to
Input, Output or Input/Output.

Eric

On 21 June 2017 at 01:51, Nadir Amra <amra@xxxxxxxxxx> wrote:

Hi Mitch,

The field names are case sensitive (they must match what is in the

PCML).

If they do match, then please send me an example PCML file or source
code, properties file, and how you are invoking the script.





From: Mitch Gallman <mgallman@xxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
<web400@xxxxxxxxxxxx>
Date: 06/20/2017 03:14 PM
Subject: [WEB400] IWS installWEbService.sh & Properties
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>



I have a properties file setup per the IWS manual that lists my fields

indicating their usage (input/output).

e.g. ws.properties:
PROCEDURE.field1.usage=input
PROCEDURE.field2.usage=output
PROCEDURE.field3.usage=output
PROCEDURE.field4.usage=output
PROCEDURE.field5.usage=output

In my script call to installWebService.sh I am using the
-propertiesFile parameter with '/home/mgallman/ws.properties'.
However, I am still forced to add the -parameterUsage parameter

with the 'PROCEDURE:i,o,o,o,o,o'

specification. If I leave it out then it tries to deploy based on the

PCML which results in it trying to set the usage to "inputoutput"
which fails. It doesn't appear to look to the properties file at all.

Am I doing something incorrect or what would I need to do in order to
get the usage settings from the properties file to be used?

Thanks!

Mitch Gallman | U.S. Xpress, Inc.
IBM i Applications Developer

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.





--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing

list

To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.