Installation and prerequisites > Electronic Signature > Prerequisites

Prerequisites to installing Electronic Signature

The Electronic Signature product includes an embedded EBICS Client. You must install Electronic Signature if you require EBICS Client functionality. The option Electronic Signature T mode corresponds to EBICS Client standalone.

License key

Ensure you have the appropriate license key.

Software prerequisites for Electronic Signature server

Java Unrestricted Jurisdiction Policies

Due to US government export restrictions, JVM implementations are delivered with a restricted cryptographic strength that varies depending on the Java Virtual Machine vendor.

Because FEX products rely heavily on the cryptographic capabilities of the underlying JVM, there may be problems running with lower cryptographic constraints, ranging from non support of certain required key lengths, to not being able to start.

To solve this, the Java Virtual Machine must be modified to include the Java Unrestricted Jurisdiction Policies. These policies are usually shipped as a ZIP file that you use to overwrite the files local_policy.jar and US_export_policy.jar, located in the $JAVA_HOME/lib/security directory.

These policies are included with the delivered Java version of the Axway installer.

Software prerequisites for Electronic Signature client

Token support

The following token types have been tested for use with this version of Electronic Signature:

Token Type Client to use
SafeNet SafeNet Authentication Client 8.0 SP2
Certinomis Gemalto RegTool
Keynectis Gemalto RegTool
Ces@mOr SafeNet Authentication Client 8.0 SP2
Keynectis K.Sign® Sagem Launcher
SWIFT 3Skey Etoken PKI Client

Note: On the current version, only one of these token types can be used at a time.

Limitations

Bank and Customer names

When using Electronic Signature with Gateway, you must not use the underscore character '_' in Bank or Customer names. The PSR parser interprets the underscore as a separator.

Gateway

When using Electronic Signature in Gateway mode, both products must be installed on the same host computer.

Optional Features

Sentinel

In the case of integration of Electronic Signature with Gateway and Sentinel, the Sentinel Universal Agent is used as a bridge toward the Sentinel Server. This Sentinel Universal Agent must be installed on the same host computer as Electronic Signature.

DMZ integration

In order to use Electronic Signature with Gateway integration, in a DMZ environment, you can install Axway Secure Relay Router Agent (RA) inside the DMZ.

Note that the Secure Relay Master Agent (MA) is already embedded in the Electronic Signature with Gateway integration, so there is no need to install Secure Relay MA.

Alternatively another proxy can be used.

Related topics

Installing Electronic Signature

FEX installation prerequisites

Port number assignments