Hi,
As APIGW used default package for IS, however in case user have API Gateway Advance Edition, but while click on license detail few features appearing as disabled, is it normal behaviour using license or pertain with configuration ?
Additionally, inside separeate IS server all features are enable and only Microservice appearing as disabled. Is it license concern or we can ignore it.
webMethod Products:
Hi Asghar,
most likely, this is related to license restrictions.
You can verify this by opening the license xml file in a plain text editor and there should be a section with the components licensed when using this file.
Regards,
Holger
My take is this is normal. API GW does not support pub/sub (Broker nor UM) nor adapters nor guaranteed delivery – those are aspects of IS running “normally” as IS or MSR. But for API GW, IS is merely a “host” of sorts. Indeed, there are times I question why API GW is hosted on IS at all.
I’m thinking it’s due to business model, in case if all license enabled inside the APIGW internal IS then the beauty of standalone IS doesn’t exist.
Actully, when i checked in standalone IS microservices appearing as disabled and license type is MTR.
The IS license never includes microservices.
But you can configure a MSR license with an IS, which activates properties based configuration, prometheus metrics and health endpoints.
I believe the reason why microservices are enabled at API gateway level is precisely to have these features activated.
Hi i applied microservice license on top of IS license, after that microservices enabled but Enterprise Gateway now appearing as disabled.
You have a comparison IS / MSR here:
https://documentation.softwareag.com/webmethods/integration_server/pie10-15/webhelp/pie-webhelp/#page/pie-webhelp%2Fto-msr_vs_is_2.html%23
If you want to implement an Enterprise Gateway, you will do it using a separate and dedicated component that resides in the DMZ. The documentation says: Install Enterprise Gateway on its own host Integration Server. Do not install other products on an Integration Server that hosts Enterprise Gateway.
Your integrations will stay in the internal network. Having EG disabled in the runtimes running these integrations is not a problem.
However, there are other situations where the replacement of the IS license with the MSR license can cause issues: for instance when the IS is used with Trading Networks.
Such a replacement should be studied with the vendor if you want to be 100% on the safe side.
3 posts were split to a new topic: Disable API Gateway from primary Integration Server instance
Let me come back to one of my favorite questions 
What is then use-case or goal behind this discussion? Perhaps I overlooked something, but so far it seems somewhat abstract to me.
Dear @jahntech.cj , Related to the subjected discussion i got anoter license but after applying enterprise gateway appearing as down and microservices now appearing as enabled.
What is the background for this license change and are the license files for the same product?
What functionality did you have before the license change? Was the license update done to change/extend that functionality? If you wanted to change functionality, what was the expected result vs. what you are seeing now?
Is the new license correct in that it covers the correct product?
@jahntech.cj , yes license are new, there are two queries;
For 1,
for understanding purpose is it normal behaviour like when we install standalone IS so microservices appears as disabled or it’s happening due to license.
For 2,
As APIGW Advance Edition license applied so under APIGW’s IS it’s showing few options are disabled as in attached screenshot.
So just want to understand if it’s normal behaviour of the product or something need to check.
I know it is confusing but Api gateway and Enterprise gateway are also different products. Without making it more complicated can you tell us what you are trying to accomplish? This is called XY problem. You are asking for an answer for your attempted solution. Please try to explain your requirements. Under normal circumstances, changing the built in packages and the license are usually done at the beginning right after the first installation, unless license expires of course. If license expires, you need to update it with the same type of license.
Here’s the license I’ve got for the API Gateway Advanced edition, from which I have removed the sensitive information.
<?xml version="1.0" encoding="US-ASCII"?>
<SoftwareAG_License>
<Component Id="SalesInfo">
<SerialNumber></SerialNumber>
<LicenseKey></LicenseKey>
<CustomerID></CustomerID>
<CustomerName></CustomerName>
<ContractDetails></ContractDetails>
<ContractPosNumber></ContractPosNumber>
<LicenseTypeDetails></LicenseTypeDetails>
<AutoCallHome>
</AutoCallHome>
</Component>
<Component Id="ProductInfo">
<ExpirationDate></ExpirationDate>
<OS>any</OS>
<ProductCode>YAIAA</ProductCode>
<ProductID/>
<ProductName>API Gateway Advanced Edition</ProductName>
<ProductVersion>10.7</ProductVersion>
<Usage>Internal2024</Usage>
<RenewalDate/>
<HigherLevPosNr>
</HigherLevPosNr>
<HigherLevProdCode>
</HigherLevProdCode>
<HigherLevProdName>
</HigherLevProdName>
</Component>
<Component Id="Integration Server">
<ProductCode>YAI</ProductCode>
<ProductVersion>10.7</ProductVersion>
<ConcurrentSessions>Unlimited</ConcurrentSessions>
<Clustering>yes</Clustering>
<PubSub>no</PubSub>
<ART>no</ART>
<RemoteInvoke>yes</RemoteInvoke>
<GuaranteedDelivery>no</GuaranteedDelivery>
<SecurityAuditing>yes</SecurityAuditing>
<DistributedCache>yes</DistributedCache>
<EnterpriseGateway>yes</EnterpriseGateway>
<Microservices>yes</Microservices>
</Component>
<Component Id="APIGateway">
<PolicyManagementThreatProtection>yes</PolicyManagementThreatProtection>
<PolicyManagementGateway>yes</PolicyManagementGateway>
<ApplicationManagement>yes</ApplicationManagement>
<APIManagement>yes</APIManagement>
<AppMesh>yes</AppMesh>
</Component>
<Component Id="LicenseInfo">
<PriceUnit>CoreD</PriceUnit>
<PriceQuantity>16</PriceQuantity>
<TypeOfInstallation>Internal2024</TypeOfInstallation>
<LicenseType/>
<ExtendedRights>
</ExtendedRights>
<LicenseVersion>1.2</LicenseVersion>
<Metering>
</Metering>
</Component>
</SoftwareAG_License>
If there’s anything you’re not sure of regarding your licenses, you should contact your SAG sales team.
For APIGW
For APIGW’s IS which appeard as following options disabled using APIGW license, it’s a product behaviour as confirmed by SAG team.
Publish / Subscribe
Adapter Runtime
Guaranteed Delivery
For Mocroservices:
Microservices Runtime is a superset of Integration Server. In general, this means that Microservices Runtime includes features that are not part of a standard Integration Server. However, some of the features available on a standard Integration Server are not installed by default on Microservices Runtime and must be selected specifically during the installation of Microservices Runtime.
Additionally, because Microservices Runtime is optimized for running in a Docker container, Microservices Runtime does not include all of the behavior available on an Integration Server, such as running multiple instances on the same host machine or the use of Command Central. However an Integration Server equipped with a Microservices license provides all of the functionality of Integration Server and Microservices Runtime without the size and speed optimizations made for a Microservices Runtime.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.