The Online Help for Intrexx Version 19.03 is currently still a work
in progress. Incomplete files have a notice informing you of missing
With the new web connector, Tomcat is now
always part of the portal service. Therefore, there is no longer a
separate service - Tomcat is started automatically whenever the portal service
is started. The Tomcat web serber no longer needs to be explicitly selected
in the setup or when creating a new portal. You can usually open your portal
in the browser with the basis URL "localhost:1337".
When operating multiple portals under one address and SSO on Windows,
IIS (for Windows) or Nginx (Linux) needs to be implemented as a reverse
proxy / load balancer from Intrexx Version 18.09 and higher.
This revision was necessary to support all current and upcoming
web standards optimally. This not only allows us to provide
performance optimizations, but also many features in the future
that will ensure the best possible user experience for your portal
users. In addition, the support of IoT and cloud scenarios in
horizontally scalable environments or in high-availability scenarios
are only made possible because of these changes. Click here
for more information.
The business logic has been
revised to benefit sustainability (flexibility, API, transparency).
Clear definitions and a clean structure provide greater flexibility
when designing applications. The responsibilities of the server code
was moved to the
There are now additional options for saving form data.
Action and response have been separated clearly.
The performance when publishing applications has been greatly improved.
Communication between the Portal Manager and other servers has been
switched to the REST API. This means portals can communicate with
other servers securely even across firewalls. The integration of
external systems and data is made even easier as a result and your
portal is one step closer to becoming a digital workplace and a
pivotal tool in your company. True to the motto: Everything in
Both the Portal Manager and Server are now based on Java Runtime
version 11. You can choose to use existing Java licenses or switch
to the open source option OpenJDK. As well as saving costs, this
also gives you the ability to choose your own personal JDK and
thus consolidate your Java systems.
The different development statuses of applications, processes and layouts
can now be versioned in two different ways:
Semantic versioning: Provide a textual version number with metadata
Version management with Git that creates a history
"Mobile first" is in focus for the new portlet framework - portlet pages are
created respsonsively. The administration now provides flexible configuration
options and smart usability. Dashboards can be constructed with content from
any application and expanded easily thanks to the dynamic parameterization.
The availability and appearance of the portlets
can be controlled deliberately. In applications, pages from other applications
can now be integrated as portlets. This also means pages can be used
multiple times. Click here
for more information.