A B C D E
F G H I J
K L M N O
P Q R S T
U V W X Y
In your Intrexx portal, there is the portal menu, which you can edit
and the application menu, which you can edit on the
"Application menu" tab
in the properties of your application. It typically consists of links to
selected pages in the application.
Application Request Routing is an extension to Internet Information Services (IIS),
which enables an IIS server to function as a load balancer. Click
for more information.
The base URL is the URL used to access your portal.
It is defined in the
and is made up of the protocol (HTTPS), the DNS name of the (virtual) host, potentially the
port number, and the root directory "/" of the web application.
To avoid problems with different browsers, the DNS settings of the client, certificate
validation or the same-origin policy, we recommend entering the fully qualified host name
when accessing the portal in the browser.
The Intrexx business logic is responsible for the reading, writing and
validation of data, as well as handling default values. Furthermore,
it provides a data source abstraction layer.
Workstation computer of a user. Uses the applications or resources provided
by the server.
Displacement of IT resources (memory, software) to central servers that
are not considered to be part of the company infrastructure but rather
made available by independent third-party providers.
Teamwork between employees with the aid of functions of a software platform.
The current state of applications, layouts or processes is stored
in the corresponding Git repository
The context menu of every element can be access with the right mouse button.
Elements, for example from the Applications
and Design modules are also called
The HTML element DIV groups multiple elements
together in one area. The application element Grouping
can, for example, be defined as a DIV container.
A parameter, which is demanded by a target page, can be populated by the
caller with a value. It is also possible to string fallback values together
in this case. Based on the principle of "first match", the first fallback value
to deliver a valid value will be used at run-time. Parameter values, which
are the same for all or at least the majority of callers, can already be
predefined with values at the target page. A fallback value chain can
also be created here. If the caller does not provide a valid value for the
parameter, then the fallback value chain of the target page will be worked
through and the first valid value found will be used. If a valid value
for a required parameter cannot be identified neither from the caller nor
at the target page, then the target page cannot be viewed/used.
Foreign keys are used to identify data records which are stored in other
database tables but are related to data records from the current table.
Departments are saved in the following table.
The next table contains employee data.
|Primary key||Department||First name||Last name|
The primary key of the department is saved as the foreign key in the
Department column. This makes it very simple to
identify, for example, that Betty Miller
works in the Support department.
Git is a distributed version management system for files.
In Intrexx, Git is used for the
of applications, processes or layouts.
Earlier states can be reconstructed with it.
The documentation for Git can be found
The GUID (Globally Unique Identifier) is the unique identifier for each
individual element in Intrexx. In expert mode
the GUID of can element can be identified using the Details dialog.
Intrexx GUIDs consist of 160 random bits that are generated using a
cryptographically secure random generator. This results in hexadecimal
coded character strings with a length of 40 characters
The performance potential of an IT infrastructure can be increased
with vertical or horizontal scaling. Vertical scaling means that existing
server hardware is upgraded (CPUs, memory etc.).
Horizontal scaling means that new servers are added to increase performance.
Internet Information Services is an extensible web server created by
Microsoft. Click here
for more information.
IoT - Internet of Things
The Internet of Things is a network that consists of many intelligent
devices or systems that interact with one another via M2M (machine to machine).
In the health sector, the industrial sector and the enterprise resource
planning, objects are being equipped with intelligent sensors for this
purpose. Each intelligent object can be identified using a unique
internet address and can be addressed in the Internet of Things
Refers to your Intrexx installation directory: on Windows e.g.
C:\Program Files\intrexx and on
If the property Input required has been activated
for an element, such as here for the
, the element becomes a mandatory field. Saving a page in the
browser is only performed when all mandatory fields have been filled in. The user
will be informed about empty mandatory fields by a notification before saving
the data record.
Microsoft Office Graph
The Microsoft Office Graph is a back-end tool in Microsoft Office 365
that interconnects the searching and locating of information
in different sources of Microsoft Office 365 automatically.
This is a solution that compiles all of the important information
and documents across all repositories and Microsoft Office 365 programs.
Microsoft Office Graph possesses a uniform programming interface (API)
that servers as the access point for every type of search request.
The Connector for Microsoft Office 365
uses the Graph API to access content in Microsoft Office 365.
MQTT (Message Queuing Telemetry Transport) is a messaging protocol
based on TCP. It is open, simple and
designed to be implemented easily.
MQTT is characterized by low overheads in the communication,
but provides stable message delivery nonetheless.
With these properties, it is ideal for use in many situations
including limited environments, such as for communicating in
machine-to-machine (M2M) and Internet of Things (IoT) contexts
with low, limited or expensive network bandwidth, but where
information should be provided or consumed regularly despite this.
Practical areas of use, where MQTT is already well used, include
"Track & Trace" applications that record a wide variety of
readings (e.g. temperatures, rotations, water levels etc.).
The devices can range from monoboard computers (SoC), such
as a Rasberry Pi, which has been expanded with
the corresponding sensors, via smartphones, which provide the
corresponding values for mobile devices, through to industrial
manufacturing facilities, where the production and hardware status
should be monitored.
An MQTT client can act as a "Listener", which listens
to messages from other MQTT clients, or as a "Publisher",
which sends messages. The mapping of the messages is organized
into channels, so-called "topics", this means that in the simplest
scenarios, two MQTT clients can "talk" when the same topic is
selected for both of them. In this simple scenario, this can
be enough to receive reports about the water levels in a hydroelectric
facility on your smartphone, for example. However, as soon as
multiple clients are involved and there are various topics
available, or also in use, or access needs to be made secure
accordingly, a so-called "Broker", meaning an MQTT server,
is a good solution. This also provides the facility of
implementing additional protocols such as JMS (Java Messaging Service).
Multi-tenancy is used in information technology, when multiple tenants, meaning
customers or orderers, can be served on the same server or software system
without them being able to look into each other's data, user management etc.
A system does not become multi-tenant capable by creating an individual
instance (copy) of the system for each tenant.
A namespace is a context, within which the names are unique. Namespaces can be
hierarchical, meaning the names within each hierarchical level are unique.
- Football: Namespace is the team. The shirt number is the unique name within this.
- Telephony: Namespace is the dialing code. The connecting number is the
unique name within this.
- Domain name system (DNS): Namespace is a second-level domain. Here, the hostnames (www)
and the subdomains (dev) are unique.
- URIs (Uniform Resource Identifiers): Each URI can be regarded as name with the
superordinate resource as the namespace.
The Open Data Protocol (OData) is a standardized web protocol.
It supports the simple integration and manipulation of data and is designed in
a significantly more user-friendly way than previous web services for
developing web and mobile applications. OData is based on open web standards
like HTTP, Atom Publishing Protocol and JSON, and like the World Wide Web,
is constructed based on the REST (Representational State Transfer) architectural
style. Complex database requests can be accomplished with OData using the URL alone.
Consequently, OData is also known as ODBC for the web.
An Intrexx portal can be created
in the Portal Manager.
You can choose from various portal templates
for your new portal. The portal can then be opened and used by any number
clients directly in the browser. The new portal comes with a menu structure
and applications that can be adjusted to your specific requirements.
All files of a portal can be found in the Intrexx Portal Server in this
directory: on Windows e.g.
c:/ProgramData/intrexx/<portalname>. You can determine the
portal directory in the portal properties; this is reached from the
The portal logfile is in the portal directory /log
The Portal manager can be installed by itself or together with the Intrexx Portal Server.
It controls all of the components for developing and managing
layouts, menus and applications. The permissions for the portal users
for applications and data are also controlled here. The Portal Manager
can be started either from the program group or via the desktop
shortcut. On Linux systems, you will find
manager.sh in the installation directory client/bin/linux
You can connect to an Intrexx Portal Server and administrate the portals on the
start page of the Portal Manager
Relevant information is displayed in portlets
on a portal page.
The Intrexx Portal Server controls all of the
transactions from the portals and applications created there. It monitors
the permissions within the transactions, controls the entire business
logic and manages access to the data sources.
You can connect to an Intrexx Portal Server in the
Intrexx Portal Manager
A prefix is placed in front of the actual term. If, for example, a data field
is called STR_TITLE, TITLE is the term
and STR_ is the prefix - the so-called
data type prefix.
Primary keys are used to uniquely identify data records. In the following
example, the last name Miller and the first
name Sam occur more than once. With the
primary key, which saved in its own database column, each data
record can be identified uniquely.
|Primary key||First name||Last name|
A primary key can also be assembled from a combination of various attributes,
for example when multiple database tables are connected together in another
table. It is important here that each combination is unique, meaning it
only occurs once.
A processing context is generated in Intrexx as soon as a procedure is performed
on the Portal Server
. The processing context
contains the sharedState
or the current data record,
depending on the context. The lifetime of the processing context spans the
beginning and end of the procedure. The objects it contains are not
necessarily available from the beginning but can also be added while
the procedure is being performed. Sometimes the sharedState
is used synonymously with the processing context. Click
for more information about the interface and the interfaces derived from this.
The settings for an element are available in its properties dialog
and can be modified there. The properties dialog can be opened by
double-clicking on the element or via the context menu
A repository is a project archive where files are stored which are
managed by Git
. In Intrexx, a repository corresponds
in each case to the directory of an application, process or layout.
A repository is created in Git for each application, process or layout
as soon as an entry is created in the
Restart Intrexx services
Intrexx services can be restarted, for example, in Windows
under Control panel / Administrative tools.
You can recognize the Intrexx portal services because of the prefix
Intrexx Portal followed by the name of the
portal. The Intrexx Supervisor service
is responsible for the distribution of licenses, downloading software
updates among others. This very rarely needs to be restarted.
A request parameter is a parameter that has been transferred from a client
(typically a web browser) to the server and is provided there via the request
A self-signed certificate is a certificate that has been signed by the issuer itself and not by a Certificate Authority (CA).
Due to the missing path to a trusted root CA, browsers (clients) only trust these certificates if they have been explicitly defined as trustworthy in the browser (client).
This is normally done by adding the certificate to the certificate store of the browser (client).
Semantic values can be assigned to parameters
Semantic values are particularly helpful for commonly occurring parameters to
make it clear which context the parameter is in. For example, the semantic
value "Customer number" makes it quickly clear that a parameter with the
name "LID" refers to the ID of a customer.
For practically every procedure in Intrexx, which is performed by a user or
technical user, session objects are generated on the server by a login.
Variables can be created for these sessions objects. The values of these
can be accessed in every context where this session is in use. The value exists
from the time the variable is created until it is either modified or deleted,
or the session is logged out.
An optional global sharedState
is available in many
event sources and timers
this is defined, the same shared state is used for all events of the source.
Tagging describes the labelling of content. Tags are not predefined and can be
assigned freely. The tags are gathered together to form a so-called tag cloud
that provides information about how often a tag was assigned – the larger a
tag is shown in the cloud, the more often it has been used.
Temporary directories are used for caching files to be able to, for example,
generate them fully without other applications accessing them during the
process. Furthermore, the data is not stored in the memory during the entire
generation process in this way. You can access the temporary directory via
the environment variable
%TEMP% (Explorer or command line) in windows
The Intrexx client saves open processes in this directory, for example.
Log files from processes are stored as XML files here.
Normally, the Intrexx server uses other temporary directories, such as
the /tmp directory in the
in the Portal directory
Web services are services that provide functions and data via the internet.
Similar to a search engine, queries will be sent from a sender, which
in this case is not a person, but a software program. The web service
returns the results to the program querying it. Web services can be provided
for use either internally or externally to the company.
If you would like to, for example, find the name of a bank based on a routing
code, a web service can determine and return the desired data using an
operation. The operations are described using WSDL (Web Services Description
Language) files. The exchange of information takes place via an exchange of
XML files. In order to use a web service, the URL with which the web service
is identified must be known. With Intrexx, web service provisions can be
without requiring additional programming effort. Furthermore, you can
your own web services.