If you understand how to install additional servlets in Tomcat, then it’s very simple. Also, since the url doesn’t specify the domain but only path, then the same file will work for all the xwikis, as long as you have completed step 4 correctly.
Die Umsetzung der Adresse ist atypisch und der Richtung des Aufrufes entgegengesetzt (deutsch umgekehrter Proxy). Verify.Step 3: get your apache vhosts configuration correct.To make sure your vhosts are configured correctly, I dump an index.html file in the 3 DocumentRoot directories. Weiterhin kann ein Reverse Proxy auch als offener Proxy genutzt werden, um Anfragen unter „seinem Namen“ an fremde Server zu schicken, ohne dass dies vom Betreiber so gedacht ist. Thus your urls can be as simple as:There may be a better way to do this, but this works well enough.Otherwise, the DocumentRoot setting is a non issue. Apache doesn’t care about xwiki, or where the jar files are. I think we just didn’t understood each other I need to set domain to subwiki where the domain has none text same with name of xwiki. After a typical XWiki installation XWiki will be running on http://localhost:8080/xwiki. Or do I have to have XWIKI on separate server? Search for AJP. But you will need a different apachce vhost configuration for each subdomain.Give me some time to make a working example for you.ok, turns out it’s easier than I thought… I’m writing up the details nowStep 1: Get your tomcat and subwikis running. Daher kann es empfehlenswert sein, ihn derart zu konfigurieren, dass er nur auf Anfragen an bestimmte Server antwortet. XWiki needs to be accessible via https protocol, which must be reverse proxy with http.When I load XWiki, it shows 404 for all the resources it tries to load.It seems that XWiki is not able to load any resources due to reverse-proxy setup. I really need to make sure I understand exactly what you want, otherwise the configuration I give won’t be of any use at all.Assuming that the above is correct, can you confirm that you can access the subwikis via the tomcat urls without problem, e.g.So, if I understand correctly, you have the following:Possible. So to transfer your example to my situation I need to know what instead of your example I should fill there. Do you mean…I mean the first one. And what is more I don’t understand how should I trace the subwiki in filesystem, when all I can trace is the whole xwiki farm.You don’t have to have a different document root for every subwiki vhost.The only reason I did this was to make sure that I could test my apache vhost installations to make sure they were configured properly. However, that’s beyond the scope of this explanation.Some people will say “don’t do it” and some people will say “it’s fine”. Die wahre Adresse des Zielsystems bleibt dem Client verborgen.
It only needs to know what requests to send, and where to send those requests.If you follow my steps listed above, and you test every link I ask you to test, then your configuration will work. This means: 1) Java 2) Tomcat 3) MySQL/MariaDB 4) XWiki 5) Nginx. And I don’t want to bother you more than needed.This test installation was done under Ubuntu Server 18, which is almost identical to Debian, so you shouldn’t have any trouble using this configuration.Sorry for misunderstanding, I use Ubuntu 18.04, but I used this So instead of this I should fill there the real location of war files of XWIKI?To set domain to sub-wiki only I will follow only this, right? XWiki can and does run behind reverse proxies such as Apache mod_proxy. As long as your Tomcat JVM has enough memory and CPU, there shouldn’t be an issue.I just need to have parent xwiki accessible with IP like 12.34.56.67:8080/xwiki and my subwiki in this wiki to have to be set to my domain like: 12.34.56.67:8080/xwiki/wiki/mysubwiki -> If you look at those domains/urls, that’s exactly what you want, isn’t it? Unlike a forward proxy, which is an intermediary for its associated clients to contact any server, a reverse proxy is an intermediary for its associated servers to be … In computer networks, a reverse proxy is a type of proxy server that retrieves resources on behalf of a client from one or more servers. I know that I need to have only one XWIKI on server without using virutal server or docker solution.Yes. A popular choice for a reverse-proxy web server is Nginx. It is more like: As I said, I am very grateful and I feel sorry for not solving this situation.
We have for example: domain.domainforuse.eu and we need to serve it to sub-wiki.So, if I understand correctly, you have the following:Is that correct? In the above example, we’re using this method.The mod_ajp connection is a binary protocol that is supposedly more efficient to allow tomcat and apache to communicate. The more I think about it, the more I think the question doesn’t matter.If I would follow your example, will I be able to have other apps in Tomcat next to this XWIKI settings? I don’t think this is “too complex” or just “too much”. As long as you followed the previous steps, confirmed that everything works at each step, then you will have each subwiki served by their own subdomains (And if adding /xwiki to the url is still too much, then you can make a single DocumentRoot that is identical for all vhosts and added in the following index.html:This will cause all the browsers automatically to redirect to the xwiki installation.
After I have done some number of Apache settings for PhP application I still have some deficit (probably) in Apache to Tomcat settings. I am very sorry for being confused, but I just don’t get it.After I have follwed the steps you made I just ended with:It might be easier if I logged into your server and configured it for you. I only just tested this out now and while it seems to work, I may have missed something important.After some settings to Apache I am able to reach parent wiki and its subwikis like this as I was before.I understand you are saying to set vhosts in Apache to every wiki or subwiki which is need to do like this. Usually the only thing needed is to have the x-forwarded-host http header set to the external URL and XWiki will write links correctly.