I am using WebLogic 10.3.6 we try to use FortiClient VPN to access our applications and use FortiClient VPN SSO (we configure application URL as a bookmark forticlient) it works fine for other .net applications but our oracle portal application makes a full redirect in a new tap.
Other application URLs are wrapped like this https://VPN_URL/proxy/11693587/https/APP_URL
but the oracle portal app opens in its original URL.
Any advice
I'm deploying an application on Glassfish Server on a Windows10 machine via a remote Desktop connection. What would happen if another user deploys another version of the application on the same Glassfish Server ( the same port obviously) while the other session is still active ?
You can keep the session alvive during deployments if you check the corresponding checkbox in the admin application.
If do not check this option active sessions will be destroyed.
Learning Lucee for the first time. What is the difference between the Server and Web admin pages? (Does the 'Server' page handle config for the app server, and web for the web server?)
And how do they relate to the Tomcat Apache server I was supposed to install with it?
The server admin lets you set settings at a global level, like the Adobe ColdFusion admin, however the web admin lets you set settings for one particular web site, so for example I always configure data sources at the web level so that only the site that needs access to that data source has access to it.
Web settings have precedence over server settings, so if you have it set to setting A in the server admin but setting B in the web admin for one site it will use setting B for that website but setting A for all other sites.
With regards to Tomcat that is the Java servlet container in which Lucee runs (https://en.wikipedia.org/wiki/Web_container). If you used the installer then Tomcat will have been installed automatically for you.
I have a Windows 2012 Server via VPS hosting.
I installed IIS and MySQL last week.
I have no way to remotely access the MySQL db, so thought I'd try to set things up so that I can access it remotely.
I have installed XAMPP this evening, and installed Apache and PHP onto the server.
My domain name. e.g. mysite.com is linked to the VPS hosting, so that I can go to e.g. localhost/index.html and also mysite.com/index.html and see the same page.
I had to configure apache so that I could connect to it at the same time as running IIS, so access it via localhost:8080/phpMyAdmin/index.php. When connected via remote desktop connection, I can also access that via mysite.com:8080/phpMyAdmin/index.php.
However, if I disconnect the remote desktop connection and try again to get to mysite.com:8080/phpMyAdmin/index.php I get a timeout error.
I seem to only be able to access that URL when on the actual server that the site runs from, even though I can use the full external URL.
I wondered if there any way around this?
I read somewhere that a web application consists of a web server, application server and a database server. What is the difference between these three ?
I asked this question because I remember when I hosted a website, all I had was a https login to the control panel of the website, in which I put all my files in htdocs folder. There were no three separate things like the web server, application server and the database server.
This often gets confusing.
Firstly - "Server" can refer to a physical thing (a computer), or a logical thing (a piece of software).
Web, application and database server software can all run on the same physical server machine, or be distributed across multiple physical machines. Most large websites have multiple machines; most "consumer" hosting packages run on a single box.
The logical separation is as follows.
The Web server deals with HTTP(S) requests, and passes these requests on to "handlers". They have built-in handlers for file requests - HTML pages, images, CSS, JavaScript etc. You can add additional handlers for requests that they cannot manage - e.g. dynamic pages delivered by the application server. Web servers implement the HTTP specification, and know how to manage request and response headers.
The application server handles requests which create dynamic pages. So instead of serving an HTML page that is stored on the hard drive, they dynamically generate the HTML sent to the end user. Common languages/frameworks for this are Java/JSP, .Net (aspx), PHP, Ruby (on Rails or not), Python etc. Most of the time, this application server software is running on the same physical server machine as the web server.
The database server software is where the application stores its structured information. Typically, this means custom software which allows the application server to ask questions like "how many items does user x have in their basket?", using a programming language. Examples are MySQL, SQL Server, Oracle (all "relational databases"), and MongoDB, Redis and CouchDB ("NoSQL" solutions).
The database software can run on the same physical machine as the web server, but it's usually the first thing that gets hosted on separate physical hardware when the site needs to scale.
Web Server -
Server on which your website is hosted. This server will have installed web servers such as IIS, apache, etc.
Application Server -
Server on which your created applications which are utilizing your database, web service, etc.
This application server will host business layer (wrapped with web services), scheduled jobs, windows services, etc.
Database Server -
Database server will have your one or more database hosted such as Oracle, Sql Server, MySql, etc.
If you are referring to htdocs then it is a Web Server. The database you are using is must be installed on different server which is your Database server. Application server can also be installed on the same web server machine.
Reference - Deployment Patterns
Web Server: The server on which all your HTTP requests are handled is known as a web server
where as
Application Server: Including the services of web server i.e responding to the HTTP requests it also responds to the business logic thus not just limited to the HTTP protocol
Eg. gaming servers, chat rooms etc.