CA Layer 7 API Gateway Administrator at a computer software company with 10,001+ employees
MSP
Top 20
2023-08-28T07:18:59Z
Aug 28, 2023
We have more than 50 applications in the backend. We monitor the infrastructure through a database monitoring tool. Our daily tasks involve working on P1 incidents, managing change requests, conducting patching updates, working on P2 tickets, backend server certificate renewals, etc.
Presales Consultant for CA Southern Africa at Hyperion Holding Pty Ltd
Real User
Top 5
2023-05-12T08:32:00Z
May 12, 2023
The solution secures your API/Service/Application in a matter of minutes. It also provides the capability for translating services from one format to another (SOAP to REST, REST to SOAP, GraphQL - API, and vice versa). Broadcom API Gateway would provide you 1000+ out-of-the-box assertions and certain custom assertions to meet your development and integration requirements. Rather than building an application in hours through coding the Drag and Drop capability, allows you to create APIs in minutes. The runtime setup allows coding and testing at a faster pace without the need to deploy and redeploy applications for every version build published. Failure if any the code could be rolled back in a matter of seconds and activated. So it provides a good framework that is tried and tested over the years and provided a Robust OOB Security and Implementation interfaces.
The primary use case for Layer7 API Management is patient services, such as patient care and health care services, where patients would like to check appointment details and reports on mobile applications. Another use case for the product is sharing the data with external organizations related to healthcare.
Layer7 API Management can be deployed on the cloud and on-premise. We are using Layer7 API Management to expose APIs and to do security checks, which is similar to a reverse proxy.
We use this solution for security as well as for monetization. I'm a certified CA API management professional and a user of this solution. We are vendors of Layer7.
Senior System Engineer at a tech services company with 51-200 employees
Real User
2021-02-04T14:33:00Z
Feb 4, 2021
We primarily use Layer7 API Management to monitor stuff. I'm the one who installs it. They sent me a TAR file, I unloaded it to TAR, brought it up, and made everything work. I gave it the three different network configurations to talk to the three different domains, and then I turn it over to the guys, and they do what they got to do with it.
We use Layer7 API Management for digital banking: for signing, validation, transactions, etc. We are a partner, so there are roughly 40 people inside my company working with Layer7.
We had a test version, which was more of an on-prem version, and we also had some on the Docker for a live API creator. We are a security service company, and we provide a lot of solutions in that space. We were just trying to have a frictionless authentication product, so we were working on that. We were looking for a Gateway that can serve in an API, and we've already got an open-source solution.
IT / Enterprise Architect, IT Consultant at a consultancy with 11-50 employees
Consultant
2020-09-01T05:25:09Z
Sep 1, 2020
We are using it for controlling all web services, traffic, or API traffic. All connections are going through the Layer7 API gateway. That is done for the purpose of security, management, and governance.
I am an Enterprise API architect and we are one of the biggest conglomerate organizations in Dubai. We have a lot of retail businesses, automotive businesses, and other interests. What we are doing is using the API Management to build out a proper, consistent API layer for our legacy systems and microservices as well. That will enable us to expand our reach in digital channels. We are already using Dell Boomi in our organization for ESB purposes and are more focused on that development right now and hope to do more with Layer7 in the future.
We started off exposing REST APIs to other business units and our external partners by doing legacy integration. The Gateway is a security control point and a way to drive standardisation. Live API Creator is used very successfully by one of our businesses to run all their APIs. Other BUs use the Live API Creator to create the easy, "quick win" APIs, which do not make sense to host on the ESB or where resources are not available to do it quickly. We handle some SOAP services where we are only interested in adding additional security and metrics on top of the SOAP services. We even transform JSON REST to SOAP where legacy internal ESB systems are not able to use REST. We have seen a huge uptake in routing messaging services, like SMS and WhatsApp. The Gateway currently serves to standardise these into a single API view with multiple channels.
Consultor de segurança at a tech company with 1-10 employees
Real User
2019-04-25T11:03:00Z
Apr 25, 2019
In my company, we use CA API Management for banks in the financial markets. Our primary use case is for the basic protection of the APIs. We also use the authentication feature.
Software Engineer at a tech vendor with 501-1,000 employees
Real User
2019-01-31T08:49:00Z
Jan 31, 2019
Previously, we don't have a security for our web or mobile applications. In a scenario where I have an application that gives APIs to everyone in the world, they can directly access that particular application. However, this allows for different types of attacks on that particular application too. This becomes a problem if a number of users access it, whether they are valid or invalid users, they will see performance issues. If a number of attacks are happening on a particular application, it goes down. So, from a security perspective, CA API Management acts like a reserve proxy. It makes the end user feel like it is a real system. It does not show the back-end and what the API tool does. CA API management will not let people know that there is an original server running behind the tool. That is the security point of it. For use cases, there are databases that some people have to query on. With the help of CA API Management tool, we can give APIs to the end user, and with the help of those APIs, they can access the data instead of the database.
I have used this tool for my customers, as I am a service provider, not an end user. I have dealt with implementations and configurations for CA API Management. We implemented the API versioning for software services and REST services.
Lead Architect at a energy/utilities company with 1,001-5,000 employees
Real User
2019-01-28T12:30:00Z
Jan 28, 2019
We use it as a gateway for protecting some of our critical infrastructure out on the grid. We have six data centers and it is implemented in each one of them, protecting our grid. We have several applications that talk to the grid, and they pass through that gateway to get out there, ensuring that we terminate connections from the lower security environment and reestablish credentials for the higher security environment.
Our primary use case is basic encryption/decryption using symmetric assertions and then, gradually, SOAP signatures, SOAP encryption, non-SOAP XML encryption, and signing that. In the last six months or so, I have been working on JWT (JSON Web Tokens).
We've been using it to program intermittently. There's a problem with one version, which saves pretty slowly. Now it's good. Then we found that this is cheaper. The advantages include the coding, as well as getting emails and alerts from them.
GM - Head of Digital Transformation at a financial services firm with 10,001+ employees
Real User
2019-01-23T11:26:00Z
Jan 23, 2019
Our primary use case for this solution is opening up our APIs to the development community so they can help us innovate some of our banking products. We've demoed CA API Management and we've done one proof of concept with it, but we are not using it on an ongoing basis.
Sr. Systems Engineer at a hospitality company with 1,001-5,000 employees
Real User
2018-11-18T07:31:00Z
Nov 18, 2018
We use CA API Management for our brand mobile app and our outbound traffic. Our brand mobile apps are for Olive Garden, Capital Grill and LongHorn Steak House. We also use API Management to modernize legacy systems via microservices. We have our internet application, which is connected to PeopleSoft and other tools so we can export through API gateway. So we have a custom mobile app built for our internal application, where people can check their paychecks, benefits, and other perks, such as gift cards.
Business Development - Alliances and Partnerships at a tech services company with 10,001+ employees
Reseller
2018-06-04T11:26:00Z
Jun 4, 2018
My company is a CA partner. We do implementations for end-customers, using CA API Management. So my company doesn't use the product, but we install, configure, and implement the product for our end-customers. Primary use for the solution is to have access to APIs that are generally difficult and not available. An example would be critical APIs that should be available 24/7 but they are not available most of the time, because of one or another constraint. That is where the API Management solution is used to the maximum by end-customers.
Our primary use case is as an API gateway for authentication and authorization, and then lightweight transformation or lightweight mediation. But it's mostly, authentication and authorization, mostly security-based.
Arquitecto de Soluciones at Puntos Colombia S.A.S.
Real User
2018-05-23T20:02:00Z
May 23, 2018
Administration and configuration of the platform API management version 9.2. SaaS, security configuration, design, and implementation of APIs, which are exposed to partners of the company for the execution of business flows. All this is done quickly and easily with minimal effort.
Technical Consultant at a computer software company with 501-1,000 employees
Real User
2016-10-19T06:50:00Z
Oct 19, 2016
* Digitalization * API Life Cycle Management CA API Management powers the next generation of mobile and Internet of Things (IoT) applications by providing reliable connectivity between data, people, apps and devices. You can aggregate and orchestrate data from multiple data sources into modern REST APIs almost instantly. Whether your data is in legacy systems, disparate databases, or the cloud, you will be able to bring it all together to power new digital initiatives at scale in modern apps or SaaS applications.
Layer7 API Management is a comprehensive solution that enables organizations to securely expose, manage, and monetize their APIs.
It provides features such as API gateway, developer portal, analytics, and security to ensure seamless integration and control over API traffic.
With Layer7 API Management, businesses can streamline their API operations and drive innovation.
I use the solution since I work for many different kinds of domains and different kinds of organizations, including the banking and financial sectors.
It serves our development purposes, enabling the connection of both external and internal clients, for example.
We use Layer7 API Management to manage API gateway and customize policy scripts.
We have more than 50 applications in the backend. We monitor the infrastructure through a database monitoring tool. Our daily tasks involve working on P1 incidents, managing change requests, conducting patching updates, working on P2 tickets, backend server certificate renewals, etc.
The solution secures your API/Service/Application in a matter of minutes. It also provides the capability for translating services from one format to another (SOAP to REST, REST to SOAP, GraphQL - API, and vice versa). Broadcom API Gateway would provide you 1000+ out-of-the-box assertions and certain custom assertions to meet your development and integration requirements. Rather than building an application in hours through coding the Drag and Drop capability, allows you to create APIs in minutes. The runtime setup allows coding and testing at a faster pace without the need to deploy and redeploy applications for every version build published. Failure if any the code could be rolled back in a matter of seconds and activated. So it provides a good framework that is tried and tested over the years and provided a Robust OOB Security and Implementation interfaces.
The primary use case for Layer7 API Management is patient services, such as patient care and health care services, where patients would like to check appointment details and reports on mobile applications. Another use case for the product is sharing the data with external organizations related to healthcare.
Layer7 API Management can be deployed on the cloud and on-premise. We are using Layer7 API Management to expose APIs and to do security checks, which is similar to a reverse proxy.
We use this solution for security as well as for monetization. I'm a certified CA API management professional and a user of this solution. We are vendors of Layer7.
I sell this solution to a variety of clients in digital banking, insurance, and health care.
We are using Layer7 API Management as an enterprise service bus, ESB, and B2B security gateway.
In my organization the main use cases for Layer7 API Management were to cover our 3 fold API Strategy:
1) Improved Developer Experience.
2) API Governance
3) Business Adoption.
And now, I can positively say that we were able to achieve all 3 above.
Our clients use the solution for a secured layer to protect their API. Most of them have two kinds of API, the frontend, and backend.
We primarily use Layer7 API Management to monitor stuff. I'm the one who installs it. They sent me a TAR file, I unloaded it to TAR, brought it up, and made everything work. I gave it the three different network configurations to talk to the three different domains, and then I turn it over to the guys, and they do what they got to do with it.
We use Layer7 API Management for digital banking: for signing, validation, transactions, etc. We are a partner, so there are roughly 40 people inside my company working with Layer7.
We had a test version, which was more of an on-prem version, and we also had some on the Docker for a live API creator. We are a security service company, and we provide a lot of solutions in that space. We were just trying to have a frictionless authentication product, so we were working on that. We were looking for a Gateway that can serve in an API, and we've already got an open-source solution.
This product is used to expose some internal APIs to help us automate different activities.
We are using it for controlling all web services, traffic, or API traffic. All connections are going through the Layer7 API gateway. That is done for the purpose of security, management, and governance.
I am an Enterprise API architect and we are one of the biggest conglomerate organizations in Dubai. We have a lot of retail businesses, automotive businesses, and other interests. What we are doing is using the API Management to build out a proper, consistent API layer for our legacy systems and microservices as well. That will enable us to expand our reach in digital channels. We are already using Dell Boomi in our organization for ESB purposes and are more focused on that development right now and hope to do more with Layer7 in the future.
We started off exposing REST APIs to other business units and our external partners by doing legacy integration. The Gateway is a security control point and a way to drive standardisation. Live API Creator is used very successfully by one of our businesses to run all their APIs. Other BUs use the Live API Creator to create the easy, "quick win" APIs, which do not make sense to host on the ESB or where resources are not available to do it quickly. We handle some SOAP services where we are only interested in adding additional security and metrics on top of the SOAP services. We even transform JSON REST to SOAP where legacy internal ESB systems are not able to use REST. We have seen a huge uptake in routing messaging services, like SMS and WhatsApp. The Gateway currently serves to standardise these into a single API view with multiple channels.
In my company, we use CA API Management for banks in the financial markets. Our primary use case is for the basic protection of the APIs. We also use the authentication feature.
Previously, we don't have a security for our web or mobile applications. In a scenario where I have an application that gives APIs to everyone in the world, they can directly access that particular application. However, this allows for different types of attacks on that particular application too. This becomes a problem if a number of users access it, whether they are valid or invalid users, they will see performance issues. If a number of attacks are happening on a particular application, it goes down. So, from a security perspective, CA API Management acts like a reserve proxy. It makes the end user feel like it is a real system. It does not show the back-end and what the API tool does. CA API management will not let people know that there is an original server running behind the tool. That is the security point of it. For use cases, there are databases that some people have to query on. With the help of CA API Management tool, we can give APIs to the end user, and with the help of those APIs, they can access the data instead of the database.
I have used this tool for my customers, as I am a service provider, not an end user. I have dealt with implementations and configurations for CA API Management. We implemented the API versioning for software services and REST services.
We use it as a gateway for protecting some of our critical infrastructure out on the grid. We have six data centers and it is implemented in each one of them, protecting our grid. We have several applications that talk to the grid, and they pass through that gateway to get out there, ensuring that we terminate connections from the lower security environment and reestablish credentials for the higher security environment.
Our primary use case is basic encryption/decryption using symmetric assertions and then, gradually, SOAP signatures, SOAP encryption, non-SOAP XML encryption, and signing that. In the last six months or so, I have been working on JWT (JSON Web Tokens).
We've been using it to program intermittently. There's a problem with one version, which saves pretty slowly. Now it's good. Then we found that this is cheaper. The advantages include the coding, as well as getting emails and alerts from them.
Our primary use case for this solution is opening up our APIs to the development community so they can help us innovate some of our banking products. We've demoed CA API Management and we've done one proof of concept with it, but we are not using it on an ongoing basis.
We use CA API Management for our brand mobile app and our outbound traffic. Our brand mobile apps are for Olive Garden, Capital Grill and LongHorn Steak House. We also use API Management to modernize legacy systems via microservices. We have our internet application, which is connected to PeopleSoft and other tools so we can export through API gateway. So we have a custom mobile app built for our internal application, where people can check their paychecks, benefits, and other perks, such as gift cards.
The security checking authentication is our primary use case for this solution.
RESTful API implementation and exposure.
We use CA API Management to publish APIs for secure and fast integration with customers and partners.
API security and API onboarding. We have on-premise deployment with legacy backends.
We use it primary for API management in my data center, for mobile applications and application-to-application integration.
We use it for public API security.
Managing all of our APIs and the security around them.
My company is a CA partner. We do implementations for end-customers, using CA API Management. So my company doesn't use the product, but we install, configure, and implement the product for our end-customers. Primary use for the solution is to have access to APIs that are generally difficult and not available. An example would be critical APIs that should be available 24/7 but they are not available most of the time, because of one or another constraint. That is where the API Management solution is used to the maximum by end-customers.
API management, for security.
API security, API management, OAuth security, microservices, mobile app security.
Our primary use case is as an API gateway for authentication and authorization, and then lightweight transformation or lightweight mediation. But it's mostly, authentication and authorization, mostly security-based.
API gateway.
Administration and configuration of the platform API management version 9.2. SaaS, security configuration, design, and implementation of APIs, which are exposed to partners of the company for the execution of business flows. All this is done quickly and easily with minimal effort.
* Digitalization * API Life Cycle Management CA API Management powers the next generation of mobile and Internet of Things (IoT) applications by providing reliable connectivity between data, people, apps and devices. You can aggregate and orchestrate data from multiple data sources into modern REST APIs almost instantly. Whether your data is in legacy systems, disparate databases, or the cloud, you will be able to bring it all together to power new digital initiatives at scale in modern apps or SaaS applications.