Re: Different approaches to expose RPG program outside of ibmi

[Raul Alberto Jager Weiler <raul.jager@xxxxxxxxx>]

Go for option 1. It is widely used, well known, and reliable.
Over HTTPS your communication is encrypted, and depending on your needs you
can use basic authentication or go for a sophisticated key interchange, or
something in between.

The option 2 will be a pain in the *** for the client, not everybody uses
client access...

On Fri, Apr 11, 2025 at 4:57 AM Mahesh Angadi via RPG400-L <
rpg400-l@xxxxxxxxxxxxxxxxxx> wrote:

>   Hi,
> We areconsidering two different approaches to expose our RPG program as an
> API andwould like to gather insights from IBM i experts before deciding:
>
>    - Solution#1 -- Utilizing the IBM i HTTP Apache server to expose the
> RPG program as an API. We are aware that various products leverage this
> method to build APIs.
>
>    - Solution#2 -- Developing an API within the .NET environment and
> directly invoking the RPG program from .NET using cwbx.dll (provided by IBM
> i Access Client Solutions). We have already built a framework using
> cwbx.dll to support our needs.
>
>  We are uncertain about which solution to choose and would greatly
> appreciate expert opinions on both approaches from a long-term perspective,
> including any real-world challenges that you may be encountered during
> implementation and usage.
>
>
> Thanks,
>
> Mahesh Angadi
>
> --
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.