We had a lot to do!

The current i‑effect^® version 2.8

i‑effect^® Build	2.8.10
MapGui Build	8.2
WebControl Build	3.28.14

All new features and improvements in detail

New functions

Improvements

Customer feedback

Splitting of log files

The internal log files, which are now located in /home/ieffect/internal/, will no longer exceed a maximum file size of 100 MB. As soon as a log file reaches its maximum size, a new file will be created in which logging will continue.

Database

All database objects of i‑effect^® (tables, views, indexes, triggers, contracts) are now in their own database schema (library). During the installation the name of the library can be chosen freely. The default name is IEFFECTDB. When the database is disconnected, future update and upgrade installations will only need to make the necessary changes to the database. There is no need to restore and copy existing database contents. This significantly reduces the time required for an installation. If an object in the database is lost or damaged, a new function in i‑effect^® can be used to automatically repair missing or defective objects in the i‑effect^® database.

Data conversion in *MAPPER

New tasks added to calculate and check the check digit of EAN13 and GLN.

User interface WebControl

New user and rights management to control page access via freely definable user roles. Users can additionally be activated and deactivated.

Monitor Jobs in *SERVER

Monitor groups can be defined. A monitor group collects files until either a specified number of files is reached or a specified time period is exceeded. If one of the two conditions is fulfilled, all collected files are processed in one job. This leads to a reduction in the number of jobs transferred.

New features and functions

Optimization and care

Customer feedback

General

The command DSPEFFINF now shows the current i‑effect^® database library and the date of creation of the build.
The module *OFTP is discontinued.
The module *TELEBOX is discontinued.
All customer specific files or configuration files, are uniformly located below /home/ieffect/. This also includes the standardized archiving directories of all i‑effect^® modules.
All i‑effect^® specific (program) files are still located below /i-effect/VxRyMz/.

Subsystem Jobs

The naming of subsystem jobs in i‑effect^® subsystems has been unified. JVMs (JAVA virtual machines) can be identified by their function name ("JVM-cccccccc").
If jobs are missing in a subsystem, for example because a JAVA program has terminated, these jobs can now be restarted. There is no need to shut down and restart the whole subsystem.

Installation

Through optimization within product development, the size of the i‑effect^® installation image could be reduced by more than 60%. This significantly reduces the time required for an installation.
During the installation, the result of the system check now shows all license program IDs completely. If a product is missing, a standardized description of the product is displayed.

Adjustment of library name and IASP/SYSBAS installation location

With the help of a new script you can change the name of the used database, system or IASP library on an already existing i‑effect^® installation. It is also possible to move the installation back and forth between an IASP and the *SYSBAS. It is also possible to make copies of the data library and switch between different existing database copies.

Division of log files

Log messages are shortened in the prefix, because the date contained there already exists in the file name. This reduces the file size and improves the clarity.
Each module creates its own STDOUT and STDERR file.

FTP Server & SFTP Server

Certificates for users inside SFTP can be assigned more easily.
Increased security and performance by updating the libraries used.
Write and read permissions for the FTP and SFTP server can be stored for each user in the form of file and folder permissions.
The SFTP server can now be bound to one or more IP addresses. In addition, processing steps are documented more precisely in the log files, making it easier to keep track of all processes on the server.

Data conversion in *MAPPER

Transfer and return values of the type double are replaced by BigDecimal, thus avoiding rounding errors.
XSD definition files may contain blanks in the file name and are no longer invalidated by them.
If there is no database connection during the execution of a mapping, the connection setup is tried again and the mapping does not terminate immediately.

User interface WebControl

Enhanced login with status bar for displaying the individual steps. By querying the i‑effect^® version via environment variables instead of program calls, the login is much faster. Log files will be opened directly from the login screen.
Updates are delivered as a ZIP file and therefore have only 1/5 of the size of the previously used SAVF files.
As in 2.7, logbook filters can now also be loaded onto the dashboard.

Keystore can be used as directory

The keystore can still be managed as a single keystore file or as a directory in which all key pairs and certificates are available as individual files. Splitting the keystore into several files reduces the possible risk of corruption of the entire keystore by simultaneous access.

Communication *AS2

During a retransmission, the message ID remains the same, making it easier to identify the retransmissions.
Order of ciphers changed to prefer elliptical curves.
Use subject as file name when receiving: *NO, *YES (dropped in config.xml; now in partner master).
AS2 Receive profile and partner entry may be marked as TEST. Received data is not stored in the partner directory but in a test directory.

Communication *OFTP2

SSL Renegotiation switched off, to increase safety. Clients connecting to the OFTP2 server are not allowed to renegotiate the SSL connection.

Service REST-Api

Previously occurring bugs have been fixed. Among other things, the session state can now be changed without any comment.

Security

For the encryption of the passwords in all communication profiles a new algorithm is used, which increases the protection against reading.

ZUGFEeRD 2.0

Invoicing in the new ZUGFeRD 2.0 format (including update 2.0.1) is now possible. Invoices can be created in the profiles BASIC, EN 16931 (COMFORT) and EXTENDED, whereby BASIC does not correspond to the complete ISO standard and only from the COMFORT profile onwards all necessary core information of the EN 16931-1 standard is displayed. Furthermore, the implementation of the current version 2.1, which is now fully compliant with the French format Fractur-X, is in progress.

We had a lot to do!

The current i‑effect^® version 2.8

All new features and improvements in detail

Splitting of log files

Database

Data conversion in *MAPPER

User interface WebControl

Monitor Jobs in *SERVER

General

Subsystem Jobs

Installation

Adjustment of library name and IASP/SYSBAS installation location

Division of log files

FTP Server & SFTP Server

Data conversion in *MAPPER

User interface WebControl

Keystore can be used as directory

Communication *AS2

Communication *OFTP2

Service REST-Api

Security

ZUGFEeRD 2.0

Release Notes

We will be happy to advise you!

We had a lot to do!

The current i‑effect® version 2.8

All new features and improvements in detail

Splitting of log files

Database

Data conversion in *MAPPER

User interface WebControl

Monitor Jobs in *SERVER

General

Subsystem Jobs

Installation

Adjustment of library name and IASP/SYSBAS installation location

Division of log files

FTP Server & SFTP Server

Data conversion in *MAPPER

User interface WebControl

Keystore can be used as directory

Communication *AS2

Communication *OFTP2

Service REST-Api

Security

ZUGFEeRD 2.0

Release Notes

We will be happy to advise you!

The current i‑effect^® version 2.8