Or try GET HTTP method operation instead of POST just to see what happens.
Using regular expressions are tricky. I will see if I can recreate.
-----------------------------------------------
Nadir Amra
e-mail: amra@xxxxxxxxxx
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Nadir K Amra <amra@xxxxxxxxxx>
Date: Wednesday, May 7, 2025 at 11:19 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: Web Service Issue
I would try changing “Allowed input media types:” to JSON. *ALL should only be used for GET HTTP method.
-----------------------------------------------
Nadir Amra
e-mail: amra@xxxxxxxxxx
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of (WalzCraft) Jerry Forss <JForss@xxxxxxxxxxxxx>
Date: Wednesday, May 7, 2025 at 10:38 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Web Service Issue
I created a new service and just not seeing what I am doing wrong.
Is it not finding it because Resource/Parameters don't match?
What else should I be looking at?
When I do this, it says page not found (404).
I know the ip and port are correct as I use it in several other services I have created.
http://(our IP):(our port)/web/services/Contact_Maintenance/AA/780/0/ADD/Test-WOM/MAS/Master/123456789/0/456789012/testit@xxxxxxxxx<http://(our%20IP):(our%20port)/web/services/Contact_Maintenance/AA/780/0/ADD/Test-WOM/MAS/Master/123456789/0/456789012/testit@xxxxxxxxx >
Here is the setup
Resource Name:
Contact_Maintenance
Resource description:
Customer Contact Maintenance
URI path template:
/{envir:\w+}/{custno:\d+}/{seq:\d+}/{action:\w+}/{name:\w+}/{type:\w+}/{title:\w+}/{phone:\w+}/{phoneext:\w+}/{fax:\w+}/{email:\w+}
Startup type:
Service install path:
/www/WOMWEBSERV/webservices/services/Contact_Maintenance
Program:
Base resource URL:
http://(our IP):(our Port)/web/services/Contact_Maintenance
Resource information for methods [Display help for this form.] <
http://192.168.1.11:2001/HTTPA/hlp_webs_manage_installed_new.html#methods >
Procedure name:
WOMCONMNTR
HTTP request method:
POST
URI path template for method:
*NONE
HTTP response code output parameter:
*NONE
HTTP header array output parameter:
*NONE
HTTP header information:
*NONE
Error response output parameter:
Allowed input media types:
*ALL
Returned output media types:
*JSON
Identifier for input wrapper element:
WOMCONMNTRInput
Identifier for output wrapper element:
WOMCONMNTRResult
Input parameter mappings:
Parameter name
Data type
Input source
Identifier
Default Value
ENVIR
char
*PATH_PARAM
envir
*NONE
CUSTNO
packed
*PATH_PARAM
custno
*NONE
SEQ
packed
*PATH_PARAM
seq
*NONE
ACTION
char
*PATH_PARAM
action
*NONE
NAME
char
*PATH_PARAM
name
*NONE
TYPE
char
*PATH_PARAM
type
*NONE
TITLE
char
*PATH_PARAM
title
*NONE
PHONE
char
*PATH_PARAM
phone
*NONE
PHONEEXT
char
*PATH_PARAM
phoneext
*NONE
FAX
char
*PATH_PARAM
fax
*NONE
EMAIL
char
*PATH_PARAM
email
*NONE
CustNo, Seq are Input/Output.
Fail is Output.
RPG parameters
// ===================================================================================
// Input Parameters
// ===================================================================================
Dcl-pr WOMConMntR;
Envir Char(2);
CustNo Packed(8 : 0);
Seq Packed(5 : 0);
Action Char(3);
Name Char(30);
Type Char(3);
Title Char(25);
Phone Char(12);
PhoneExt Char(4);
Fax Char(12);
EMail Char(50);
Fail Char(100);
End-pr;
Dcl-pi WOMConMntR;
Envir Char(2);
CustNo Packed(8 : 0);
Seq Packed(5 : 0);
Action Char(3);
Name Char(30);
Type Char(3);
Title Char(25);
Phone Char(12);
PhoneExt Char(4);
Fax Char(12);
EMail Char(50);
Fail Char(100);
End-pi;
midrange.com
