- This topic has 1 reply, 2 voices, and was last updated 4 years, 11 months ago by
.
Viewing 1 reply thread
Viewing 1 reply thread
- You must be logged in to reply to this topic.
Tagged: webserver smartservices
kimbomadsen.
moctesHi,
Let me describe the situation :
1. I have an existing kbmMW server working for some years in an LAN without problems
2. I’m adding smartservices to this server so they can be consumed by a browser using Javascript on a single page application, so far, so good.
3. There are locations where they have qualified personnel who can setup NGINX/IIS to serve the web application and configure a reverse proxy to send the /api calls to the kbmMW smartservices API server, but there are others locations which doesn’t have that kind of workforce.
So what I am looking for ?
Having an all in one server for the latter customers.
AFAIU ( never did this ) I can make a traditional web server with kbm using a transport with AJAX StreamFormat and then create an Event operated Web Server service with the wizard and setup the locations for HTML, assets, etc.
If I’m going this way lets say using simple HTTP protocol then:
The WebServer will be listening on port 80, this server will just attend requests to / ( index.html ),
In addition there is also the SmartServices API server, which will be attending requests from /api also using port 80, Here I have doubts is it possible to have this setup ?
I can have the WebServer listening on port 80 and the api server on another port and let the Web app make the calls to the api using the right TCP port, but If I need later ( which surely would be needed ) to use SSL then I’m not sure I could have web server on 443 and api server on XXXX port.
So, can I build an all in one server with kbmMW ?
What do you think? Any advice is welcome
kimbomadsenHi,
I generally recommend you to use the REST transport stream format rather than the AJAX one.
You can easily have one kbmMW based application server that have multiple interfaces, like REST / web server functionality on port 80, SSL ditto on port 443, native kbmMW client side support on port say 3000 etc.
All you need to do is add a server side transport for each of those, and configure them accordingly.