Run xServer on different Java and Tomcat

This forum deals with administrative topics such as monitoring and system setup. It is dedicated to system administrators who do not have to deal with the functions themselves but who have to establish and maintain proper environments.
Public since 15.2.2017

Run xServer on different Java and Tomcat

Postby PaulBuechs » Fri Feb 08, 2019 3:34 pm

Hi,
Our customer wants to set up the xServer in a scalable environment. For this we can’t use the xServer bundle and need to connect to a given Tomcat and Java Version. Is it possible to get the war files for the xServer to run it on a different Tomcat and Java, instead of the provided one?
For our case it’s a PaaS system, like it’s done for the xServer Internet.

Thanks,
Paul
User avatar
PaulBuechs
 
Posts: 20
Joined: Tue Mar 28, 2017 1:09 pm

Re: Run xServer on different Java and Tomcat

Postby Bernd Welter » Tue Feb 12, 2019 9:35 am

Hello Paul,

here's some infro straight from the Product Management (translated and adapted by me):
  • The reason why we deploy within a TOMCAT is because it offers to provide a web service interface (service address as entry point). The server itself then requires JAVA to process the requests and to communicate with the underlying engines.
  • If PTV provides a WAR file instead of a monolithic service this would limit us to the restrictions of WAR (sounds dramatic :lol: ) such as memory restrictions (performance!). This would also require a lot of additional efforts (e.g. extracting parts from the WAR).
  • TOMCAT and JAVA fit together but they have to be seen as two separate topics. JAVA provides the JRE which we were able to use and to provide for free in the past. For your convenience. Now ORACLE demands licenses and this will cause us to remove the JAVA runtime from the provision container. There's no significant impact on handling and performance. Just some initial admin efforts are required (installation of a licensed JRE, e.g. OpenJDK or Amazon Coretto), setting some path
    variables). The integration into an own TOMCAT is more complicated.
  • DOCKER is a container for services which can be used in a linux environment. Content has to be assembled in advance. The server is then able to run immediately within the container. One significant benefit is that the container can be used through various distributions. Maybe you could take a look at the DOCKER mechanism instead of TOMCAT (which isn't appropriate).

Best regards,
Bernd

Original statement from Daniel:

  • Wir deployen den Tomcat, damit er den xServer Web-Service bereitstellt – also die Dienstadresse/den Einstiegspunkt, der xServer selbst benötigt aber ein JAVA um die Anfragen zu bearbeiten und mit den darunterliegenden Engines zu kommunizieren. Wenn wir die xServer als WAR bereitstellen würden, wären wir aber den Beschränkungen von WAR unterlegen – was für performancekritische Services mit mehreren GB daten schwierig währe und massive Umbauten notwendig machen würde (Teile wieder aus dem WAR zu lösen, was dann wiederum nicht gekapselt wäre). Also mir fällt spontan nicht ein, wie das überhaupt funktionieren könnte.
  • 2. Tomcat und JAVA sind zwei grundlegend unterschiedliche Dinge, und ich kann das Argument „wenn ihr das eine tut, warum nicht auch das Andere“ nicht nachvollziehen. JAVA stellt ein JRE zur Verfügung, auf das wir einfach aufsetzen – wir haben das aus Gründen der Bequemlichkeit bisher mit ausgeliefert, und die kommende Änderung ist relativ trivial, da keine Änderungen am JRE selbst vorgenommen werden.
    Die Integration von Tomcat stellt aber einen in Tomcat konfigurierten Dienst dar – inclusive ein paar Tomcat WARs
  • 3. Docker ist ein Container für beliebige Dienste unter Linux – die Inhalte müssen aber vorher zusammengebaut werden. Also ein xServer wird in quasi lauffähigem Zustand komplett und scharf in diesen Conatiner deployed. Das vereinfacht die Bereitstellung unter Linux da Docker auch über viele Distributionen hinweg stabil lauffähig ist. Für mich hört es sich so an, als könnte der Kunde evtl. solch einen Container verwenden – Tomcat ist aber dafür nicht geeignet.
Bernd Welter
Manager Technical Consulting & Requirement Engineering
Senior Technical Consultant Developer Components
PTV GROUP - Germany

Bernd at Youtube
User avatar
Bernd Welter
Site Admin
 
Posts: 1295
Joined: Mon Apr 14, 2014 10:28 am

Re: Run xServer on different Java and Tomcat

Postby PaulBuechs » Fri Feb 15, 2019 12:31 pm

Hi Bernd,

thanks for the reply.
Java besides, Tomcat is the more relevant problem, we don’t want to skip it. We just want to change the Path of the location for the tomcat. The Tomcat version can stay the same. A war file is not needed specifically from our side, it was just an idea.
To not mix topics: Is it possible to change the path of the Tomcat?

Kind regards,
Paul
User avatar
PaulBuechs
 
Posts: 20
Joined: Tue Mar 28, 2017 1:09 pm

Re: Run xServer on different Java and Tomcat

Postby Bernd Welter » Tue Apr 02, 2019 12:18 pm

Hello Paul,

as discussed in the recent phonecalls:
replacing the built-in tomcat with a custom one isn't possible:
  • the xServer requires much more than just a war-file to be deployed: we need to start sub-processes and install platform specific (c++ based) backend libraries
  • such a scenario would not allow PTV support to reproduce customer issues
  • this is also the reason why a migration from TOMCAT to alternative application servers such as IBM websphere is no option

Best regards,
Bernd
Bernd Welter
Manager Technical Consulting & Requirement Engineering
Senior Technical Consultant Developer Components
PTV GROUP - Germany

Bernd at Youtube
User avatar
Bernd Welter
Site Admin
 
Posts: 1295
Joined: Mon Apr 14, 2014 10:28 am


Return to PTV xServer Administration

cron