WSO2 APIM v4.x | In-Memory Deployment of APIs

Hi Everyone, in this blog I am going to share about in-memory deployment process of APIs in WSO2 API Manager 4.

Deployment Process for APIs- Whenever an API is deployed via publisher portal, it generates the API Synapse artefacts and stores the same. In previous versions of WSO2 API Manager (till apim v3.2.x), the API artefacts were stored in database as well as in the file system at following location-

AM_HOME/repository/deployment/server/synapse-configs/default/api/<PROVIDER-API-Version.xml>

Changes in API Manager 4-  Starting with WSO2 APIM v4, WSO2 has changed the deployment and loading process of the APIs as-

  • API-Related Synapse artefacts were moved from the file system to the In-Memory
  • During the server startup and revision deployment, artefacts will be loaded from DB to memory

So, after this important change in WSO2 API Manager 4, the API artefacts are loaded from following database tables to In-Memory-

  • AM_GW_PUBLISHED_API_DETAILS  ;
  • AM_GW_API_ARTIFACTS;
  • AM_GW_API_DEPLOYMENTS;

Below screenshots provides more details about the above tables contents-

Table view AM_GW_PUBLISHED_API_DETAILS
Figure1- Table view AM_GW_PUBLISHED_API_DETAILS  

Table view AM_GW_API_ARTIFACTS
Figure2- Table view AM_GW_API_ARTIFACTS

Table view AM_GW_API_DEPLOYMENTS
Figure3- Table view AM_GW_API_DEPLOYMENTS

So, now you will not find the API related Synapse artefacts inside earlier synapse folder (AM_HOME/repository/deployment/server/synapse-configs/default/api), rather than loading & deployment will be done from DB to In-Memory in APIM v4.

Comments

Popular posts from this blog

Oracle SOA Suite- Implementing Email Notification

Oracle SOA Suite 12c- PKIX path building failed & unable to find valid certification path to requested target

Migration of Oracle SOA Suite Composite from 11g to 12c