Welcome to our tutorial, with the help of which you can create a new EDI partner in our eBiss converter by yourself in the future. The process will be illustrated on the basis of Pranke eBiss 3. What we will do: We will search for the desired participant on the Pranke homepage, download its associated ini-file and integrate it into the EDI converter. Afterwards we will show you how to check your partner’s data.

Enable subtitles to see the English captions!

Enter in the internet browser of your choice.
Arrived there, we navigate by means of the “participant search” – button to the participant – search mask.

In the opened form you have the possibility to search for names, parts of names or even GLNs.

Attention: if an inexperienced employee of the future EDI partner has given you the GLN of one of his subordinate locations, it could be that the participant cannot be found via the GLN. So it is not possible to find every branch of a participant. As a rule, you can find only the main or technical GLN of a subscriber.
This will appear later in the first line, the header data, i.e. in the UNB segment of the EDI messages, as the target GLN.

In this example we are looking for the participant “sample company”. After we have found the desired participant, we now want to download its ini-file (or configuration file). This is done by clicking on “Download”. The file will be saved in a directory of our choice or in the preset download directory.

In the next step you open your eBiss and select on the left in the menu area first the partner administration and then the subcategory “trading partner”,

Info: Under trading partners you will find the list of already created EDI partners. In this test system there is no EDI partner yet, but this will hardly occur in reality.

In any case, the list should now be open. Then we click on the button “import” and navigate in the opening window to our just downloaded ini-file. The filter in the file selector is preset to *.ini files, so other files will not be displayed.

If you have general questions or problems, you can always have a look at our help under XY.

Once we have found the desired file, we select it and import it into the converter by clicking on “open”.
A window should pop up confirming that the import has been completed successfully.
You can see the newly created EDI partner directly in the list of trading partners.
You can view the exact communication data of the partner by double-clicking on the partner, using “Communication address”.

You now have the possibility to exchange data with the new EDI partner, provided that this partner can send and receive EDI FACT data.

If other data is to be exchanged, we recommend that you contact Pranke Support by phone or e-mail.


The task Could not rotate file ‘LogManager.log’ always occurs when a CleanUp job is running that uses the JobObject eBiss.ClassLib.Jobs.LogRotator while an eBiss Client is active.
The eBiss client has an open file handler on the log files, therefore they cannot be closed and moved.
Remedy is to make sure that all eBiss CLients are closed when a CleanUp job is running.


eBiss offers send and receive channels with which inter-node communication and other integrations can be mapped.

To receive something with eBiss via Http receive channel it also needs a so called Http port listener, which listens on a defined URL or IP address and port and opens a corresponding job with Http receive channel when the event occurs.


eBiss offers global and partner specific solutions with the remapping.

The use of eBiss own tables is not recommended, because otherwise the integrity may not be guaranteed.


Problem: In eGate there are messages that are supposedly sent twice.
Recipient and subject, however, are different.


The recipient claims a so-called data stream with us.

His incoming messages are forwarded as a copy to our server,
converted into “BTE” format and processed by Advarics.

Important: This action does not lead to additional traffic!


eGate is generally to be considered as a closed community network. Therefore, when picking up messages with a SMTP Channel in eBiss, we want to use the Sender identification mandatory. This means that all possible sender eGate email addresses of my trading partners must be known in my eBiss system. This also applies to (third party) poviders who forward EDI messages on behalf of their customers. So if an eGate participant is offered in the participant search not only with a CUSTOMER.INI file but also with a SENDER .INI FILE I have to make sure that the eGate participant of the provider (or SENDER) exists as trading partner in my eBiss. If not, then I need to import the SENDER .INI file.

Example of an eGate participant with provider affiliation:

Name Tnr GLN/UNB-ID Customer .ini File Sender .ini File
Muster GmbH, München (DE) 1234567890 1234567890123 Download Provider

If messages remain unprocessed in your INBOX and with an unknown partner, the reason may be that the validation in the receive channel was not successful.

Pranke eGate Access if You’re Not a Pranke eGate Customer

To enable you to exchange messages with a Pranke eGate customer, a communication channel must be set up for you. This communication channel might be through email forwarding, x.400 with A=viaT and C=DE, or AS2.

eGate receives your message for another subscriber via this communication channel and makes it available to the recipient via their communication channel – and vice versa.

Read more


With an AS2 channel your local system or network is connected to the Pranke eGate VAN. To end up with a successful and failure-free message exchange, the rules listed here should be followed during setup and operation.


Participants in eGate are bound to fixed communication channels. Because of this, and to ensure clear message routing, parallel connections between servers or networks should not be set up. Therefore, please check if there is already a connection to the Pranke AS2 service on your system. Please look for connections to one of the following URLs (http/https):

  • or

Please also watch out for AS2 IDs like:

  • “Pranke”,
  • “PrankeTest”,
  • “PrankeAS2” or
  • “PrankeAS2Test”,

If a connection to the Pranke AS2 service already exists, this connection should also be used for communication with any other eGate participant instead of setting up a new connection.

If no existing connection could be found, and a new channel needs to be set up, please use the parameters from the current datasheet and the provided certificate. Before you start setting up the endpoint on your server, please contact us (support(at) and provide the necessary data for setting up the endpoint on our system:

  • the URL of your AS2 service,
  • your AS2 ID,
  • the preferred MDN mode (synchronous/asynchronous),
  • Signature and encryption algorithm,
  • your certificate, and
  • a contact address for administrative notifications (operational failures, certificate replacement, etc.)

We identify the sender and recipient of a message submitted via AS2 by evaluation of the interchange segment of the respective message. (e.g. EDIFACT UNB or ANSI.x12 ISA). Only IDs that have been previously made known to us and that have been created in eGate as participants may be used. If an ID is replaced or an additional ID needs to be introduced, please contact us to arrange the necessary configuration.

In case of planned service interruptions, changes in communication, certificate renewal and corresponding occasions please inform support(at)



In this download you will find our data sheet for new AS2 connections and the current certificate:

Download “” – 326.69 KB


See also

How to Communicate with a Pranke Egate Customer

  1. Do you have an eGate customer account? If so, please check the access information by logging in at
  2. Is your account still valid or was it cancelled? In case of doubt, please ask the customer support.
  3. If you have not picked up any messages for a long time, it is possible that some old messages have already been archived. This means that messages can no longer be retrieved. Log in to your eGate account and identify the archived messages (indicated by the grayed out message IDs) and delete them from your inbox first. After that the retrieval via communication channel should work again.