Highlighted
ratclma Absent Member.
Absent Member.
553 views

NAM rule to access a web service


Hi,
We want to use NAM to act as a reverse proxy for APIGEE. The developers
want to access the web service
/ws/pathtowebservice/ordermanagement_webservicename_WSD_Port as
https://api.company.com/order/v1/orderstatus
Not having setup a proxy for a webservice am I being simplistic in
thinking I do the following:
create proxy service for the reverse proxy https://api.company.com
pointing to the webservice port of the web server with path /ws
create protected resource for
/ws/pathtowebservice/ordermanagement_webservicename_WSD_Port
create redirect rule to redirect to
https://api.company.com/order/v1/orderstatus

Thanks
Mark


--
ratclma
------------------------------------------------------------------------
ratclma's Profile: https://forums.netiq.com/member.php?userid=7886
View this thread: https://forums.netiq.com/showthread.php?t=57262

0 Likes
2 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: NAM rule to access a web service

On 1/27/2017 9:23 PM, ratclma wrote:
>
> Hi,
> We want to use NAM to act as a reverse proxy for APIGEE. The developers
> want to access the web service
> /ws/pathtowebservice/ordermanagement_webservicename_WSD_Port as
> https://api.company.com/order/v1/orderstatus
> Not having setup a proxy for a webservice am I being simplistic in
> thinking I do the following:
> create proxy service for the reverse proxy https://api.company.com
> pointing to the webservice port of the web server with path /ws
> create protected resource for
> /ws/pathtowebservice/ordermanagement_webservicename_WSD_Port
> create redirect rule to redirect to
> https://api.company.com/order/v1/orderstatus


That sounds doable i reckon

--
Cheers,
Edward
0 Likes
EVCIS Contributor.
Contributor.

Re: NAM rule to access a web service


ratclma;274340 Wrote:
> Hi,
> We want to use NAM to act as a reverse proxy for APIGEE. The developers
> want to access the web service
> /ws/pathtowebservice/ordermanagement_webservicename_WSD_Port as
> https://api.company.com/order/v1/orderstatus
> Not having setup a proxy for a webservice am I being simplistic in
> thinking I do the following:
> create proxy service for the reverse proxy https://api.company.com
> pointing to the webservice port of the web server with path /ws
> create protected resource for
> /ws/pathtowebservice/ordermanagement_webservicename_WSD_Port
> create redirect rule to redirect to
> https://api.company.com/order/v1/orderstatus
>
> Thanks
> Mark

Domain looks good, it will become tricky with the path though. I don't
think it will work properly the way I'm understanding what you
described.

If you create a reverse proxy https://api.company.com with path /ws
and you protect
/ws/pathtowebservice/ordermanagement_webservicename_WSD_Port,
then redirect to https://api.company.com/order/v1/orderstatus
you won't be able to access anything at http://tinyurl.com/gkpbr4g cause
you'll be redirected immediately.
Most likely nothing at https://api.company.com/order/v1/orderstatus

Are you trying to turn http://tinyurl.com/gkpbr4g into
https://api.company.com/order/v1/orderstatus through NAM?


--
EVCIS
------------------------------------------------------------------------
EVCIS's Profile: https://forums.netiq.com/member.php?userid=9553
View this thread: https://forums.netiq.com/showthread.php?t=57262

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.