Introduction to Lobster_data
Introduction
This introduction serves to provide a general and comprehensive understanding. The descriptions of settings for specific areas of the GUI are linked directly from the current context of the GUI via the Help Mode. You can, of course, jump directly to interesting areas in the menu on the left. In some cases, the introduction also links to the GUI documentation.
You'll also find numerous context-related introductory videos in help mode.
Lobster_data is a software tool that can act as a central data hub in your company. Data from all your systems and from all your partners can be centrally bundled, processed, transformed, managed and monitored. Following the standard architecture of Lobster_data. Further possibilities can be found in the section Architecture.
The Lobster_data server component runs as an application on the Lobster Integration Server. A variety of communication services (e.g. JDBC service (database), OFTP service, Cloud service, FTP service, AS2 service, etc.), which are accessed by Lobster_data, also run on the Lobster Integration Server. As a basis for each Lobster_data installation, you must have a Java Development Kit (JDK) and a database.
The Integration Server is administered in the Admin Console. Among other things, you can set up and configure services and database connections there.
This documentation uses ./ (a dot and a slash) to specify the installation directory of the Integration Server. Please note this when configuration files are described.
Client and Users
An ordinary browser can be used as server client. Users for Lobster_data can be created in the User Administration. The default user is admin, with password admin. This password should be changed after the first login. See section User Menu. Please use the URL/IP of the computer on which the Integration Server is installed (or the DMZ server) and select _data. The default port is 80 and therefore does not have to be specified explicitly. Following the direct link. See also sections Adding an HTTPS Listener and Let's Encrypt/ACME/Certbot.
|
http(s)://<IP_of_Integration_Server_or_DMZ>/_data |
Multiple users can use the client on different machines (or the same) and connect to the same Lobster_data Integration Server. See also section Sessions. Option Release my locks is used to terminate old sessions of the same user.
Lobster_data is also capable of handling multiple clients (e. g. companies or subsidiaries) with distinctive settings.
Custom Theming/Logo
|
./webapps/root/_data_theme.properties |
General Control Elements
General GUI control elements of Lobster_data are described here. Although the GUI is designed very intuitively, a short glance will certainly not do any harm.
Glossary and Concepts
Specific explanations of technical terms and concepts used in the documentation are listed here. But you will usually find direct links in the documentation when these terms/concepts are used. So you can get familiar with them if necessary.
Data Processing in Lobster_data
As already shown, Lobster_data consists of two components. A server component where data processing is performed, and a client component (browser GUI) that allows users to perform monitoring and troubleshooting tasks, administer communication parameters for business partners, and develop, test, and maintain profiles.
A profile represents a data processing program in graphical form, without the need to program. If data is received by the Integration Server and assigned to a profile in Lobster_data, a job is created for this profile. Alternatively, a profile job can be started time-controlled or triggered by another profile or a workflow (see below). These jobs are the core units of data processing in Lobster_data.
Many of you will already have experience in dealing with profiles and will appreciate the advantages of this simple form of data processing. However, these days more and more business areas are being incorporated into the digital sphere. On the one hand, of course, this is an advantage because it offers opportunities to increase efficiency. On the other hand, it also increases the complexity of the processes that you have to model digitally. To accompany you on this path and make it as simple as usual, Lobster_data now offers a further abstraction level of data processing with the add-on module Workflow. With this module you can graphically model complex digital processes (without necessarily knowing technical details) and then fill them with technical life. These two steps can be performed by different people, providing a communication tool between your business departments and IT. This allows you to make existing processes clearer, but of course also to design new processes in a simple way, whereby you can easily integrate already existing and proven profiles, for example, but also more.
Introduction to EDI (Electronic Data Interchange) with Lobster_data
Take a look at our website The Compact Guide to EDI. Here you will find a lot of information about EDI in general and also about data formats and protocols.
Communication Partners
Maintaining the most important parameters you need to communicate with your partners is done centrally in the Partner Administration with channels. This could, for example, be the URL, login, password, etc. to an FTP server. In addition to the increased clarity that also facilitates maintenance. If the connection parameters change, you only have to adjust the data in one place and you do not forget a profile, for example.
Add-on Modules
Lobster_data provides a number of add-on modules (that are subject to licensing), which can meet extended and more specific data processing requirements.
In particular, we would like to point out the DataCockpit module (restrictable views and user rights for specialised/external users and direct data entry via HTML5 forms) and the Workflow module (simple and clear modelling and operation of complex, automated and partially automated processes). A combined use of the two modules is particularly useful. This allows you to make very complex processes available to different agents at selected points in a simplified way. Have the entire process under control and at the same time make only the necessary partial process available to each participant as easily and securely as possible.
Industry 4.0 and IoT - Data Fabric
Lobster_data offers simple but powerful concepts for your own Industry 4.0 integration. Use all your legacy systems without the need for a rigid, centralised and monolithic software. Quickly and scalably build smart networks for your individual data needs. Even for small and medium-sized companies. Take a look at section Nested and Networked Profiles (vertical and horizontal networks), but also our MQTT and Kafka support.
Lobster recommends the use of HiveMQ as MQTT server. In the logistics industry, for example, HiveMQ's IoT technology is often used to increase the efficiency of fleet operations. Telemetry information from thousands of vehicles can be integrated directly into back-end planning and routing systems and ultimately improve the overall operation of the fleet.
HiveMQ offers an integrated connection to the Kafka framework and the Confluent platform, allowing you to apply real-time data analysis (and predictions) and machine learning (AI). These possibilities shall only be hinted at here, since they are sciences in themselves, but Lobster_data opens the possibility for you to connect your existing systems to the world of big data.
In order to optimally support the concepts of vertical and horizontal networking (and the integration of your employees), Lobster_data now offers the add-on modules Workflow and DataCockpit. Take a quick look at them. It's worth it. You can find a concrete example in section Automated Workflows (→ Vertical integration with sub profiles).
Stable Operation (System Monitoring, Error Handling)
The manual monitoring of the complete data processing takes place in the Control Center. You will find all the running, finished and planned jobs there. It is also possible to restart aborted jobs after, for example, incorrect input data has been corrected or previously unavailable data sources are now available. Also take a look at section Logging in Lobster_data.
For automated monitoring you will find an overview of the possibilities in section concepts for ensuring stable operation.
REST API
Lobster_data offers a number of possibilities to be controlled and monitored via HTTP. See section System Interaction via HTTP (REST API).
Backup Concepts
See the following sections.
Password Security in Configuration Files
Since you will probably use Lobster_data to access many different systems, it is unavoidable for passwords to be stored in configuration files. To handle these safely, Lobster_data offers several mechanisms. See sections Obfuscation and Masked and Encrypted Passwords.
Docker/Kubernetes
Lobster_data can also be run in a Docker/Kubernetes environment.
In this case, it is recommended to set the following system properties.
Help and Searching in Lobster_data
Since you are reading the documentation, you have already found the help mode in the user menu. This is also the main interface of information to Lobster_data. In addition to the introduction, you will find a context help for the current GUI page and help videos. See also the GUI section Help.
In addition, there is documentation available for specific standard components via the question mark icon.
Functions are an exception. Here, class-specific documentation is opened via the context menu of a function in the function list.
When searching for documentation, if possible, always go via the context. This automatically places you in the right area of the documentation. From there, usually every relevant topic is linked and you can also navigate in the menu on the left. If this does not lead to a result, you will also find a search window in the documentation at the top right.
For search options in Lobster_data itself, please refer to section Searching in Lobster_data. In addition, you will find an expert search in many overviews.
Support
The best way to contact our support team is via the provided link in the help mode (see details there).
The link will open the email client configured in your browser with a new email. Most of the data relevant for our support team (e.g. installation ID in the subject, version, etc. in the mail text) will already be contained in this email. So in many cases your request can be processed faster , because it is no longer necessary to request this data from you.