One of the frequently asked questions that we see are about the prerequisite knowledge and skills for API Connect. The answer really depends on your role and how you expect to use API Connect.
This blog post lists the skills and knowledge that you should ideally already have when you start using API Connect. This blog post does not provide a full list of everything you could possibly need to know to use every feature of API Connect.
API Connect basics
Anyone working with API Connect should have knowledge of the following:
- The client/server model. The basics of how computers communicate over a network.
- The API economy. Understand why organisations want to provide services with APIs.
- HTTP. The basic concepts of the HTTP GET, POST, PUT, DELETE operations. Query and path parameters. Request headers and body.
- REST APIs and the OpenAPI specification. Be able to make sense of a basic API YAML file.
- SOAP APIs (if your organisation uses them).
Installing and administering API Connect on-premise
API Connect consists of several subsystems that communicate with each other and external systems over a network. If you are installing API Connect, then you should be familiar with the load-balancers, firewalls, and secure communication (TLS and mTLS).
Test your knowledge with these questions:
- Under what circumstances would you want to configure SSL pass-through on your firewall?
-
What is a wildcard DNS record?
If you are installing API Connect in your own container environment, then you need to be familiar with Kubernetes administration and the operator pattern.
Test your knowledge with these questions:
- What is the difference between a PVC and a PV?
-
When would you use 'kubectl create' and when would you use 'kubectl apply'?
If you are installing API Connect on VMware, you do not need Kubernetes administration experience, but do need basic Linux skills.
Test your knowledge with these questions:
- How do you give a file execute permissions?
- What tool would you use to securely copy a file to a Linux VM?
- If you want to redirect command console output to a file, what do you append to the command?
The API Connect documentation provides all the steps for configuring the DataPower Gateway for use with API Connect, but any experience you have with the DataPower UI and console will be useful.
Defining and publishing APIs
The API Connect Manager UI guides you through defining and managing the lifecycle of your APIs, but the more familiar you are with the OpenAPI specification (and SOAP specification if used), the easier you will find it.
If your role is to be managing the publication of your APIs in the API Connect Developer Portal, then familiarity with Drupal will mean you can quickly customise your organisation's external API portal site.