Disable API Gateway from primary Integration Server instance

Hello,

Can I get some help to disable APIgateway from primary IS instance. I followed Tips and Tricks of API Gateway(Tips and Tricks of API Gateway) but I am getting below error

  • Attempt to login with technical user failed: javax.ws.rs.ProcessingException: java.net.ConnectException: Connection refused: connect

Also if I disable APIGateway package in primary IS, on service restart I am not able to login with to IS.
Any help can i get on this please.

@sachin.shetty API Gateway and MSR are considered as two different offerings though the underlying base server is Integration Server. If you want typical IS, go with MSR or normal IS, whereas if you want Gateway functionalities, then install the API Gateway version. Precisely what @Stephane.TAILLAND_emp explained.

Hello @Senthilkumar_G ,

Thank you for sharing the info. Is there any way to disable apigateway package from IS instance?

I am getting below error message and if I disable the package, after restart of the service unable to login with Administrator user.

  • Attempt to login with technical user failed: javax.ws.rs.ProcessingException: java.net.ConnectException: Connection refused: connect

API Gateway components includes API Gateway user interface, the API Gateway package running in webMethods Integration Server, and an API Data Store instance for storing assets.

I don’t think you can disable WmAPIGateway package in API Gateway installation.

Why do you want to disable? I don’t think it will become a standalone IS when you disable that package. Even if you manage to disable it, like manually deleting the package, I am pretty sure you will break it. If you need an IS, do an IS installation, don’t try to salvage API gateway.

2 Likes

We have by mistakenly enabled the APIGATEWAY components in primary instance of IS. We have another instance for APIGATEWAY.

We would like to disable the APIGATEWAY as it is causing multiple login failure messages.

Attempt to login with technical user failed: javax.ws.rs.ProcessingException: java.net.ConnectException: Connection refused: connect
java.io.IOException: javax.ws.rs.ProcessingException: java.net.ConnectException: Connection refused: connect

You cannot mistakenly enable the API gateway. You’ve just installed the wrong product.
API Gateway and IS are two separate products which share the same technical backbone, but they have separate binaries and installation procedures.

If you want to use the IS, then you download and install the IS, and this IS does not contain the API GW packages.
If you want to use the API GW, they you download and install the API GW (and yes, it does bundle an IS, but this IS is solely meant to be used by the API GW.)

In the SAG installer, these are separate products and separate items.
Same in containers.softwareag.com (for the container images.)

No, you cannot and shouldn’t disable the API GW package and try to use the runtime like a genuine IS.
if you try to do that, then your deployment might not be supported by the vendor.

I believe for on premise installation it comes in a single installation file. As explained in Tips and Tricks of API Gateway(Tips and Tricks of API Gateway we installed API gateway but facing challenges now to disable it from primary IS instance.

Is there any way to disable the APIGATEWAY from primary instance to avoid the repeated technicauser auth error or do we need to rebuild the entire instance of IS?

I am afraid this isn’t the case. I am a webMethods presales and I believe I know these products very well.
The Tech Community article you’re referring to is 7 year old!

If you choose “API gateway” in the installer, then you get an API GW that embeds an IS and this IS needs to be used together with the API GW.
If you choose just the IS, then you get a runtime that does not include the API GW features.

See by yourself in this installer screenshot:

Hi Stephane,

but you can select both of them in the installer, when you are licensed for both (via different license files obviously).

In this case this is just a question to apply the proper license file for the each of the installation.
And not to select the API Gateway parts for the regular IS/TN installation, of course.

Regards,
Holger