Skip to main content
Skip table of contents

Configuration

Keystore used for the certificates

In order to be able to fully use the security mechanisms (encryption and signing) of AS2, it is necessary to maintain a keystore with its own key pair (private and public key) and the certificates of the partners. The AS2 module uses the CRYPT keystore. You can manage the certificates and key pairs using Webcontrol.  Keystore-Manager

The location of the CRYPT keystore can be found in the module configuration of the CRYPT module:

master data

In addition to parameterization in the commands themselves, you can also store some of the AS2 master data in the module configuration:

Default directories

After the successful installation of i-effect on your Power Systems you will find the following directory structure relevant for the *AS2 module in the directory /i-effect. These directories are the default working directories for AS2. You can change these settings in the module configuration of the AS2 module:

Directory for storing files of failed send operations and failed receive operations.

CODE
/i-effect/as2/error

Directory for storing the header files of successfully received AS2 messages.

CODE
/i-effect/as2/header/receive

Directory for storing the header files of successfully sent AS2 messages.

CODE
/i-effect/as2/header/send

Directory to store the successfully and error-free received MDN's.

CODE
/i-effect/as2/MDN/receive

Directory to store the successfully sent MDN's.

CODE
/i-effect/as2/MDN/send

Temporary working directory for storing received AS2 messages with asynchronous MDN request

CODE
/i-effect/as2/MDN/open

Temporary working directory for storing received AS2 messages with asynchronous MDN (Message Disposition Notification) request. This means that AS2 messages with an asynchronous MDN request, after they may have been decrypted and verified, are stored in this directory as an AS2 file until the asynchronously requested MDN is successfully returned to the sender of the AS2 message. When the asynchronously requested MDN has been successfully returned to the sender of the AS2 message, the files associated with the received AS2 message (file attachment, message header file, and MDN file) are stored in the associated directories. If the return of the asynchronously requested MDN fails, all the above files will be stored in /i-effect//as2/error.

Standard directory for storing the file attachments of successfully received AS2 messages.

CODE
/i-effect/as2/receive

The default IFS path from which data is selected for transmission.

CODE
/i-effect/as2/send

config.properties

New configuration setting to define the standard/notation of algorithm names in AS2 message/MDN headers.

The spelling/names can be changed from the new RFC 5751 (default) to the old RFC 3851.

In file '/i-effect/vxrxmx/as2/config.properties' this can be specified specifically for each AS2 ID.

CODE
# Enter here the AS2-IDS that should be build according to RFC3851.
as2.smime.algorithm.rfc3851name=AS2ID_1, AS2ID_2, AS2ID_3, ....

RFC 3851

RFC 5751
sha1sha-1
sha224sha-224
sha256 sha-256
sha384 sha-384
sha512sha-512

Please note that you need at least one AS2 version > 2.7.10.jar.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.