Posts

Since version 3 of eBiss 3.0.134, data can be retrieved from or sent to a WebDAV server.

The license-managed eBiss module contains both a WebDAV receive channel and a WebDAV transmit channel. You can use these channels to connect a directory using the WebDAV protocol.

eBiss.WebDAV uses PROPFIND and GET requests to retrieve files from the directory that was previously entered as a URL in the WebDAV receiver channel and then put them into the stored message basket.

In the opposite direction, eBiss.WebDAV transmits messages from a message basket via the WebDAV send channel to a directory in a stored URL.

Would you like more information about our WebDAV module? We are happy to advise you.

FAQs

Sorry, this entry is only available in Deutsch. For the sake of viewer convenience, the content is shown below in the alternative language. You may click the link to switch the active language.

Es folgt eine kurze Step-By-Step Erklärung wie man den Kommunikationskanal einstellt um den TSL/SSL Zugang zu eGate zu nutzen.

  1. Öffnen Sie im eBiss im Menü links unter der Gruppe Kommunikation die Kommunikationskanäle
  2. eGate Empfangs Kanal
    1. Öffnen Sie Ihren eGate Empfangskanal – Pop3 receive Channel
      In den Einstellungen ändern Sie bitte den Port auf “995” und die Authentifizierung auf “Basic”
      Bitte achten Sie darauf, dass Ihre Login-Daten für eGate richtig eingetragen sind.
    2. Öffnen Sie nun die erweiterten Einstellungen und stellen Sie das SSL Handling auf “Implizit”
  3. Wiederholen Sie diese Konfiguration auch im eGate Senden Kanal – SMTP send channel, bis auf den Port, dieser muss 25 sein.
    Achten Sie auch hier auf die korrekten Zugangsdaten für eGate
    Erweiterte Einstellungen -> SSL handling “implizit”

 

Relevant for customers who have booked one or more DataStream(s) or have several own eGate accounts.

General: Forwarding rules can be set to active/inactive.

The rule action “None” (formerly “inactive”) can now be used to exclude individual users from rules.

Example:

Account A with:

Action: None when messages are sent from/to Account B
Action: Copy, for all outgoing and incoming messages
The first rule specifically ensures that the second rule is not applied to messages with reference to account B.

Note: A prerequisite for using forwarding rules is the granting of a forwarding permission. For the above example, this means that a forwarding permission for Account A must first be granted on Account B. (With DataStreams this permission is granted by us.)

The description of the functions in eGate can be found in eGate in the menu Information/User Information or can be opened here as PDF:

eGate Anwenderinformationen

Please note the following when sending messages via eGate.

server: egate4.pranke.com (91.208.5.88)
Encrypted transmission:
Send via TLS (SMTP): Port 25 or Port 8025
Receive via TLS (POP3): Port 995
Unencrypted transmission:
Send (SMTP): Port 25 or Port 8025
Receive (POP3): Port 110 or Port 8110

If you want to make sure that the communication with eGate works over the selected ports, please proceed as follows:

By establishing a Telnet connection (via a terminal cmd.exe) you can determine whether the eGate service is accessible from the internal network.
Request: telnet eGate4.pranke.com 25
Response: 220 egate4 ESMTP server
The connection could be successfully established via the above port (25) if the server returns the response listed above.
If you receive a negative response, please check the rules in your firewall.

The administrative e-mail address is used by eGate to notify account owners about transfer errors or maintenance work. The address is not a shipping and/or receiving address for EDI data. (However, the same e-mail address may be stored as the administrative and EDI gateway address.)The administrative e-mail address should preferably not be personal, but should be e.g. edi@xyz.com .

See also: Ändern einer Gateway-Adresse , Anlegen eines Gateway-Account

When you open a message in a message folder by clicking on the ID, the message details open. There are four tabs here: General, Message, Raw Header, and Delivery Report.

message-details

In the General tab you can view various information about the message. From whom to whom did the message go, what is the subject, when did the message arrive in eGate, what is the status, how big is the message. In principle, the same information you find in the message overview.

In the Message tab, you can view and download the original message in the original format and in DAT format. If you are sending several EDI files in one message, you will always see the first one here.

In the Raw Header tab you can see the technical header details of the message.

In the DeliveryReport tab you can see the technical transmission protocol of eGate.

Situation: I am Pranke customer. My new EDI partner is not an eGate customer and told me his GLN. This does not correspond however with the GLN of its enterprise appearing in the participant search

Solution / Description:

If the GLN in the participant search is different from the GLN named by the contact person of the new EDI partner, this may be because the partner has several GLNs, but only one eGate account with an EDI communication address.

Usually, even large organizations have only one EDI communication address, where the EDI data is exchanged and then distributed within the organization. Only if several such communication addresses exist to external parties, several participant numbers must also be created. Usually it is not necessary to create further participants for the same company. It is therefore necessary to clarify with the person responsible for EDI at the new EDI partner whether an additional participant (with an additional communication address to be monitored) is necessary. The GLN appearing in the participant search is the participant’s UNB dispatch address, which is also linked to the communication address known to us.

In exceptional cases, several GLNs can also be stored with a partner, please consult our support for this.

I am a Pranke eGate customer and would like to receive a message I have already received again from eGate.

Solution / Description:

In eGate, messages that have already been fetched are moved from the inbox to the Fetched Messages directory. To retrieve a message from eGate again, please log into eGate, change to the Fetched Message directory and select the message.

Have you localized the message (e.g. by searching From contains Miller, Smith, Bernstein) ,

select this or a single message from it and select the action “move to inbox” at the bottom of the “Message Action” area.

message_action_egate1

The message can be fetched again immediately

See also: Bei eGate anmelden

I am a Pranke eGate customer, my new trading partner uses X400 as a communication channel.

Can I however exchange data with him?

Solution / Description:

Pranke is offering an extension to the eGate contract to enable data to the X400 users to be transferred. Please feel free to contact us at info@pranke.com.

You can look this up in eGate in your account after logging in yourself:

You have free analysis options if you have the traffic in your account (or accounts) displayed on eGate.

Please look in the account after logging in on the left side under “Own Account”, there under “Traffic Overview”, then wait briefly. Any further evaluations must be ordered as a special service.

traffic_overview