The ENDPOINT_TYPE refers to things such as HTTP Endpoint or WSDL Endpoint, etc. which we supported in C4. But I dont knowhow this applies to C5.
On 15 November 2016 at 16:37, Abimaran Kugathasan <[email protected]> wrote: > HI Uvindra > > On Tue, Nov 15, 2016 at 4:27 PM, Uvindra Dias Jayasinha <[email protected]> > wrote: > >> >> >> On 15 November 2016 at 16:20, Abimaran Kugathasan <[email protected]> >> wrote: >> >>> Hi Uvindra, >>> >>> What could be the possible values for ENVIRONMENT_CATEGORY column? >>> >> >> This could be Production or Sandbox >> > > I hope, values for ENDPOINT_TYPE should be Production or Sandbox. IMO, > Production or Sandbox aren't Environments but a Endpoint types or category. > > >> >> >>> Also, at a time, only one environment will be supported by the APIM, Do >>> we really need AM_API_ENVIRONMENTS table? >>> >> >> Yes in this case there would be no use for it. Also had a chat with >> NuwanD and he mentioned that we may not have a requirement for storing env >> information separately in C5, since we will be supporting a CLI to help >> exchange APIs created between different deployment environments. >> >> >>> On Tue, Nov 15, 2016 at 3:46 PM, Uvindra Dias Jayasinha < >>> [email protected]> wrote: >>> >>>> As part of the C5 effort we need to evaluate how we are to persist API >>>> Endpoint and API Environment information. Here is a brief introduction of >>>> what each of these are. >>>> >>>> *API Endpoint* >>>> The actual backend endpoint that a API created in APIM fronts. In C4 >>>> these were defined as Production and Sandbox endpoints. So at DB table >>>> level we could represent this as follows, >>>> >>>> CREATE TABLE `AM_API_ENDPOINTS` ( >>>> `API_ID` INTEGER, >>>> `ENVIRONMENT_CATEGORY` VARCHAR(30), >>>> `ENDPOINT_TYPE` VARCHAR(30), >>>> `IS_ENDPOINT_SECURED` BOOLEAN, >>>> `TPS` INTEGER, >>>> `AUTH_DIGEST` VARCHAR(30), >>>> `USERNAME` VARCHAR(255), >>>> `PASSWORD` VARCHAR(255) >>>> ); >>>> >>>> This naturally maps to our current concepts that already exist in C4. >>>> >>>> *API Environment* >>>> This represents different gateway environments across which a given API >>>> can be deployed on such as Dev, QA, Production. So at DB table level we >>>> could represent this as follows, >>>> >>>> CREATE TABLE `AM_API_ENVIRONMENTS` ( >>>> `API_ID` INTEGER, >>>> `ENV_NAME` VARCHAR(255), >>>> `HTTP_URL` VARCHAR(255), >>>> `HTTPS_URL` VARCHAR(255), >>>> `APPEND_CONTEXT` BOOLEAN >>>> ); >>>> >>>> >>>> Is there an overlap between these two concepts in the way we are >>>> representing them here? >>>> >>>> Please give your feedback. >>>> >>>> -- >>>> Regards, >>>> Uvindra >>>> >>>> Mobile: 777733962 >>>> >>> >>> >>> >>> -- >>> Thanks >>> Abimaran Kugathasan >>> Senior Software Engineer - API Technologies >>> >>> Email : [email protected] >>> Mobile : +94 773922820 >>> >>> <http://stackoverflow.com/users/515034> >>> <http://lk.linkedin.com/in/abimaran> >>> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> >>> <https://twitter.com/abimaran> >>> >>> >> >> >> -- >> Regards, >> Uvindra >> >> Mobile: 777733962 >> > > > > -- > Thanks > Abimaran Kugathasan > Senior Software Engineer - API Technologies > > Email : [email protected] > Mobile : +94 773922820 > > <http://stackoverflow.com/users/515034> > <http://lk.linkedin.com/in/abimaran> > <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> > <https://twitter.com/abimaran> > > -- Regards, Uvindra Mobile: 777733962
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
