I Have a Apache https 2.4 server on a Windows Server.
I would like to implement Kerberos authentification. For linux, it seems the solution is to use
mod_auth_gssapi https://github.com/gssapi/mod_auth_gssapi
But for Windows, there no module available.
Do you think it is possible to compile this module for windows ? is there another way maybe a proxy ?
With NGINX, it is the same problematic, no module kerberos. Maybe I need to use IIS ?
Thanks
If the server is an Active Directory domain member, use mod_auth_sspi instead, which uses the Windows-provided SSPI interface to implement Kerberos/Negotiate (and technically also NTLM).
There does not seem to be an NGINX equivalent that would use SSPI.
Compiling GSSAPI-based modules (for both Apache and NGINX) may be possible, but you would need to have an GSSAPI library first – MIT "Kerberos for Windows" and Heimdal are the two options available. (Note that they would not be able to use Windows AD machine credentials directly; they would need a keytab to be issued, just like on Linux.)
Some years ago we deployed several OSGi-based Spring Integration (SI) applications in Virgo. However, apparently SI has moved away from OSGi. So, in absence of Virgo container, what is best way to run an SI app in production now? Say, a simple app that monitors a file system location & loads file data into Oracle? Is it just java -jar?
Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". You can run a small production applications on it, you can consider using Spring Cloud then.
If you are looking for a container then think about SpringSource Tc Server - based on Pivotal Tc Server (an enterprise version of Apache Tomcat) as a platform. This is the drop-in replacement for Apache Tomcat that's optimized for Spring.
I'm looking at using hawtio for our app as a support console. We're not currently using camel or the like, but I am impressed by the ability to connect to remote JVM's via Jolokia/JMX and the logging features and was wondering:
Our use case would be that we have a weblogic server hosting our web app and my thought would be to include hawtio as a war alongside it. In addition to monitoring the web app, we have a number other JVMs running on different servers.
Is it possible to create a dashboard using values from the local JVM, as well as some of the remote JVMs?
Or must one always manually connect to the instance to see the dashboard for that particular JVM?
The current dashboard and JMX plugin does not support that.
Though there is works planned to support gathering statistics from remote JMVs etc. And there is also work on elastichsarch with a kibana web ui.
Does anybody know of a way to do http session replication between web apps running in distributed apache karaf OSGi containers?
In this post, http://karaf.922171.n3.nabble.com/Pax-web-failover-LoadBalancing-td4029552.html, Jean-Baptiste Onofré says it's not available in apache cellar yet. Is this capability available anywhere yet?
I've been googling all day and haven't found any options -- Thanks for any help.
Steve
Karaf does not have it for pax-web as confirmed by JB in the above post. I am also waiting for him to provide us.
If you are in a hurry
You can use Hazelcast (already with Cellar) for session replication.
Hazelcast supports it and provide HazelcastWM for the same purpose.
Jetty does provide session replication and we use jetty as
servlet-container.You have to check possibility with it.
Try on forum for putting Tomcat instead of Jetty.
I want to know what's the main difference between XAMPP or WAMP Server & IIS Server?
WAMP is an acronym for Windows (OS), Apache (web-server), MySQL (database), PHP (language).
XAMPP and WampServer are both free packages of WAMP, with additional applications/tools, put together by different people. There are also other WAMPs such as UniformServer. And there are commercial WAMPs such as WampDeveloper (what I use).
Their differences are in the format/structure of the package, the configurations, and the included management applications.
IIS is a web-server application just like Apache is, except it's made by Microsoft and is Windows only (Apache runs on both Windows and Linux). IIS is also more geared towards using ASP.NET (vs. PHP) and "SQL Server" (vs. MySQL), though it can use PHP and MySQL too.
WAMP: acronym for Windows Operating System, Apache(Web server), MySQL Database and PHP Language.
XAMPP: acronym for X (any Operating System), Apache (Web server), MySQL Database, PHP Language and PERL.
XAMPP and WampServer are both free packages of WAMP, with additional applications/tools, put together by different people.
Their differences are in the format/structure of the package, the configurations, and the included management applications.
In short: XAMPP supports more OSes and includes more features
WAMP [ Windows, Apache, Mysql, Php]
XAMPP [X-os, Apache, Mysql, Php , Perl ] (x-os : it can be used on any OS )
Both can be used to easily run and test websites and web applications locally.
WAMP cannot be run parallel with XAMPP because with default installation XAMPP gets priority and it takes up ports.
WAMP easy to setup configuration in.
WAMPServer has a graphical user interface to switch on or off individual component softwares while it is running.
WAMPServer provide an option to switch among many versions of Apache, many versions of PHP and many versions of MySQL all installed which provide more flexibility towards developing while XAMPPServer doesn't have such an option.
If you want to use Perl with WAMP you can configure Perl with WAMPServer http://phpflow.com/perl/how-to-configure-perl-on-wamp/ but it is better to go with XAMPP.
XAMPP is easy to use than WAMP.
XAMPP is more powerful.
XAMPP has a control panel from that you can start and stop individual components (such as MySQL,Apache etc.).
XAMPP is more resource consuming than WAMP because of heavy amount of internal component softwares like Tomcat , FileZilla FTP server, Webalizer, Mercury Mail etc.So if you donot need high features better to go with WAMP.
XAMPP also has SSL feature which WAMP doesn't.(Secure Sockets Layer (SSL) is a networking protocol that manages server authentication, client authentication and encrypted communication between servers and clients. )
IIS acronym for Internet Information Server also an extensible web server initiated as a research project for for Microsoft NT.IIS can be used for making Web applications, search engines, and Web-based applications that access databases such as SQL Server within Microsoft OSs. .
IIS supports HTTP, HTTPS, FTP, FTPS, SMTP and NNTP.
In addition to the above, WAMP supports 64 bit PHP on Windows systems while XAMPP only offers 32 bit versions. This actually made me switch to WAMP on my Windows machine since you need 64 bit PHP 7 to get bigint numbers correctly from MySQL
XAMPP is more powerful and resource taking than WAMP.
WAMP provides support for MySQL and PHP.
XAMPP provides support for MYSQL, PHP and PERL
XAMPP also has SSL feature while WAMP doesnt.
If your applications need to deal with native web apps only, Go for WAMP.
If you need advanced features as stated above, go for XAMPP.
As of priority, you cant run both together with default installation as XAMPP gets a higher priority and it takes up ports. So WAMP cant be run in parallel with XAMPP.
WAMP stands for Windows,Apache,Mysql,Php
XAMPP stands for X-os,Apache,Mysql,Php,Perl.
(x-os means it can use for any operating system)
Advantages of XAMPP:
It is cross-platform software
It possesses many other essential modules such as phpMyAdmin, OpenSSL, MediaWiki, WordPress, Joomla and more.
it is easy to configure and use.
Advantages of WAMP:
It is easy to Use. (Changing Configuration)
WAMP is Available for both 64 bit and 32-bit system.
if you are running projects which have specific version requirements
WAMP is better choice because you can switch between multiple
versions. for example 7x and PHP 5x or Magento2.2.4 won't work on
php7.2 but Magento2.3.needs php7.2 or up to work.
i suggest using laragon :
Laragon works out of the box with not only MySQL/MariaDB but also PostgreSQL & MongoDB. With Laragon, they are portable & reliable so you can focus on what matters
Laragon is a portable, isolated, fast & powerful universal development environment for PHP, Node.js, Python, Java, Go, Ruby. It is fast, lightweight, easy-to-use and easy-to-extend.
Laragon is great for building and managing modern web applications. It is focused on performance - designed around stability, simplicity, flexibility and freedom.
Laragon is very lightweight and will stay as lean as possible. The core binary itself is less than 2MB and uses less than 4MB RAM when running.
Laragon doesn’t use Windows services. It has its own service orchestration which manages services asynchronously and non-blocking so you’ll find things run fast & smoothly with Laragon.
Advantages of Laragon:
Pretty URLs
Use app.test instead of localhost/app.
Portable
You can move Laragon folder around (to another disks, to another laptops, sync to Cloud,…) without any worries.
Isolated
Laragon has an isolated environment with your OS - it will keep your system clean.
Easy Operation
Unlike others which pre-config for you, Laragon auto-configsall the complicated things. That why you can add another versions of PHP, Python, Ruby, Java, Go, Apache, Nginx, MySQL, PostgreSQL, MongoDB,… effortlessly.
Modern & Powerful
Laragon comes with modern architect which is suitable to build modern web apps. You can work with both Apache & Nginx as they are fully-managed.
Also, Laragon makes things a lot easier:Wanna have a Wordpress CMS? Just 1 click.Wanna show your local project to customers? Just 1 click.Wanna enable/disable a PHP extension? Just 1 click.
XAMPP and WAMP are both web server applications for PHP and MYSQL with the apache server. When we consider IIS, it also a web-server like apache runs on windows only.
XWAMPP/WAMP - Windows,Apache,Mysql,PHP
IIS - Apache,SQL Server, ASP.NET
If you like to read more about XWAMPP vs WAMP
WAMP: acronym for Windows OS, Apache(Web server), MySQL (Database) and PHP.
XAMPP: acronym for X (any OS), Apache (Web server), MySQL (Database), PHP/PERL.
One of their differences are in the format/structure of the package, the configurations, and the included management applications, In short: XAMPP supports more OSes and includes more features. XAMPP is easy to use than WAMP. XAMPP is more powerful. XAMPP has a control panel from that you can start and stop individual components (such as MySQL,Apache etc.). XAMPP is more resource consuming than WAMP because of heavy amount of internal component software