Manual

[idirizzo]

Hello. Can you write short manual in english, please?

[neolithos]

Hello,
thank you for your interest. Currently, we have no real documentation for this project (not even in german). Still in progress. But we should do one and also form a "product", because it works really smooth at our customers.

This project is a module for the twdes/des, that runs the oftp2 protocol. The processing has to be done in lua scripts or you own modul for the des-service. There is a lot of coding to do, because the base system knows nothing.

A simple configuration for the des-service is https://github.com/twdes/odette/blob/master/DEModette/Configs/OftpTest.xml. The xsd-file is the best doc, currently.

Hope that helps a little.

[idirizzo]

Thx for your answer! We are creating a new project for connection with our partner in Germany. And we are trying to find something open source for make connection via oftp. We found yours app. Can we use it or this app is under construction? We have only SSID and IP address of our partner. We bought a new server for make connection via oftp. We don't have any documentation about how to connect servers each other. We are trying to make it cheaper bacause mendelson (as a service) very expensive for us. May be you can help us ? Best regards, Dmitry

[neolithos]

The application will be always under construction. But it is stable to use it in real life. All our customers do there oftp stuff with this code.

SSID you mean the OFTP Identification Number or Odette Id?

It is our bussiness to implement such solutions. But in this case, I do not know were to start, because that is a big area and Oftp is only the smallest part (It descripes only the transport protocol). There is also content (e.g. VDA packets) and security (Certification).
Btw. you will run in the same problems with the mendelson server/client. It only transports the messages, and it will not parse the content for you.

Do you want to make it official to our company?

[idirizzo]

Is it not the same SSID? If not the same, i think it's will be OFTP Identification Number. Our partner gave us this SSID and it's all. We are trying to find information about connection and we have it just a little information from different sources about how to connect to them and what we need for it.

What do you mean "Do you want to make it official to our company?" -- we help you or we should official request help from your company ? Best regards, Dmitry

[neolithos]

It is the best, when I can see the information you got. So, I can see if this solution fits to your problem.

You should get from your partner, the OID, a certificate, a host and port, the transport and format parameter, file ids, ... .

And I do not believe that you want to post them in public. It is may be the best you are going to sent us/me an email. Via our contact page or to our "service" email "@tecware-gmbh.de".

[idirizzo]

Of course, I will not send this information here. My first question is what i should take from my partner for organize work with my server and can i use your app like "from box" for connection?

I think this information interesting not only for me. this is why I asked you about manual for get information how to use your app. Best regards, Dmitry

[neolithos]

What the application has to do depends hard on the organization you want to communicate with. So it is hard to create a out of the box application to fit all needs.
The file transport is very easy to manage, maybe I will create a "how to" some times for this part. But this has currently no priority and is not the whole steak.

I can give you instructions to your specific problem. And you can do an generell "how to"? Documentation is always hard to create.

First step might be to communication with e.g. the mendelson client. The configuration file, I linked ^^, does this task.

This file needs to be loaded from the twdes/des service.

Here is a less complex file, that should work, with comments

<?xml version="1.0" encoding="utf-8" ?>
<des xmlns="http://tecware-gmbh.de/dev/des/2014" 
		 xmlns:o="http://tecware-gmbh.de/dev/des/2014/odette"
		 version="330">
	<server logpath="Log">
		<resolve>..\bin\Debug</resolve>
<!-- load the odette module -->
		<load>DEM.Odette</load>
	</server>

	<http threads="1">
	</http>
	<cron />
	<luaengine>
	</luaengine>
	<serverTcp />

	<o:oftp name="oftp" displayname="Odette File Protocol" odetteId="DES" odettePassword="TEST">
<! -- creates a connection service to the host and port every 1 minute-->
		<o:connectTcp name="connectTest" addr="127.0.0.1" port="3305" allowSecureAuthentification="false" bound="1,*" />

		<o:ofileservice name="test" destination="TEST" in="D:\Temp\OFTP\In" out="D:\Temp\OFTP\Out">
		</o:ofileservice>
	</o:oftp>
</des>

Run with
DEServer.exe run -v oftp.xml

A WebServer should show up under http://localhost:8080/des.html.

[idirizzo]

Thank you so much, I will try to do it with my co-workers. Best regards, Dmitry

[idirizzo]

Hello neolithos, today we are trying to connect your server with mendelson. We were test mendelson with mendelson and its working perfect. But when we trying to connect your app to mendelson - we have error
Session terminated [customer - ServiceOftp] ("Invalid password", internal code 4)
How we can resolve it?

Another question, our partner working with old OFTP 1.0 vpn via tcp/ip. Will your app working with OFTP1.0 ?
thx for your help

[neolithos]

Invalid password means that you have to check the password properties.

Check passwordHash of the ofileservice and odettePassword of oftp.
Best is to clear all password fields for a first test, also in mendelson.

It is also a good point to find problems is to open http://localhost:8080/des.html, to view the DES logs. And there is also a debug option, where you can see detailed informations about what is happen.

Oftp 1.0 is not supported anymore, it was design to work over ISDN and this network will be shut down to the end of 2018 (e.g. in my area there is no ISDN anymore). That is the reason why we did not implement this old protocol in this new implementation.

This program only supports 2.0 (and maybe 1.3).

Btw. most of our clients that told us, that they support 1.0 over tcp/ip only, spoke 2.0.

I am not sure, but I thing the free mendelson client also did not support 1.0?

[idirizzo]

We started your server and connected it with mendelson. Connection created and closed. What is command we should to use for receive and transmit files through the servers ?

Yes, you are right, medelson too doesn't work with OFTP 1.0 either. I will ask my partner if is really he wants to use OFTP 1.0. But what are you mean when writing about Oftp 1.0 is not supported anymore -- OFTP 1.0 can be through tcp/ip and vpn? May be you mean about ISDN? i agree with you - its already not supported connection. OFTP 1.0 and OFTP1.3 its not a same protocols ?

[neolithos]

Your OFTP session are working :). Good work.

Now, you can send files with mendelson to the des-client. And the file should be saved in the "In"-Folder.
FileNameFormat (ORIGINATOR#VIRTUALNAME#TIMESTAMP.STATE)
State
- new: New file
- recv: File received and validated
- se2e: You can set this, to send the e2e.
- done: e2e send.
There is also a xml file with extended information, and you can set the content for the e2e.

The out-folder is nearly the same.
FileNameFormat (ORIGINATOR#VIRTUALNAME#TIMESTAMP.STATE)
State
- new: file gets prepared (your state)
- sent: File is ready to send (set to start the send)
- we2e: File sent, wait for e2e
- re2e: e2e received.
- done: your state

[idirizzo]

Thx for your answer. But what should I do to send files from your DES client to Mendelssohn? Can there be some commands to start sending a file or something else? Can you send some examples of command and files(or if it is possible - video)?

And what about the second part of the question: is there really a big difference between the protocols OFTP1.0 and OFTP1.3? May be you know?

[neolithos]

For sending, copy a file to the "Out"-Folder. And rename it to:
[OID]#TEST.TXT#201705081415450001.sent
Oid: is the Id from the mendelson client.

Sry, I have no equip to take a video.

There is no real command to send a file. It is done during the communication session (you scheduled every minute). You can force a session with the "Start" link in the web-browser.

Oftp 1.0 does not have any public informationen, so I have no idea what the protocol looks like (but it should be nearly equal). And all partners of our clients switched to 2.0 last year.

[idirizzo]

we have good news from our partner, he said what we can use OFTP1.3

"OFTP 1.2, 1.3 and 1.4 but not 2.0 !!! OFTP 1.3 is OK."

Maybe I'll help you a bit in the future, sometimes I use this powerful video application from my desktop.
Http://www.faststone.org/FSCaptureDetail.htm is a cheap and good desktop video application

[neolithos]

Did you get files transfered?

So, you will be the first one who tests the 1.3 stuff. I only implemented them from the rfc, but we got never tested it in real life scenarios.

[idirizzo]

We will try it today. How we can switch between OFTP 1.3 and OFTP 2.0 on your DES servers ? We want to test only on OFTP1.3 transmission and receive

[neolithos]

It is negotiated during the connection phase, there is no option for it.

Warning:
OFTP 1.3 does not support "Negative End To End" responses, but sometime the outer implementations already have the OFTP 2.0 protocol headers. This was also for confusing us.

[idirizzo]

We transmitted file from your DES to Mendelson. But when we receiving file from Mendelson to DES have error EERP

I found why ---

File encryption No

No file signing

EERP signing No ---- how you think, it's needed for FTP 1.3 ?

Use as a gateway No

[neolithos]

This is no error, this is a correct behaviour. Normally, an EERP is needed.

To generate the EERP rename in the "in"-folder the extension of the file from ".recv" to ".se2e". What will be sent in the EERP is defined the ".xml"-file.

[idirizzo]

Hello neolithos,
Really thx for your support! You helped us to understood this protocol and how it works.
We found another free product with all the feachers and it's already works. But your are open source, we are planning to use as backup for problems. Thank you so much!
Best regards!

Here is a small instruction, what we made for our collegues, who tested your app.

Run the application directory from the command line. Before running, you need to configure the file oftp.xml
In one side your should start
deserver.exe run -v -c oftp.xml -n oftpServer
and Mendelson from another PC

Setting oftp.xml
OdetteId = "O014939841518621" - replace with your own
Addr = "192.168.1.15" - replace with the recipient's ip file
Destination = "192168110" - enter the odette ID of the recipient of the files
In = "D: \ Temp \ OFTP \ In" out = "D: \ Temp \ OFTP \ Out"> - create folders for file transfer (Out - files to send to the partner)

To send a transaction from Mendelssohn to the service. Select file and send - will come in the directory in the form
FileNameFormat (ORIGINATOR # VIRTUALNAME # TIMESTAMP.STATE)
state

• new: new file
• recv: File received and verified
• se2e: you can set it, send e2e.
• done: e2e send.
  There is also an xml-file with extended information, and you can install content for e2e.

To send a transaction from the service to the Mendelssohn. Put in the output file format
FileNameFormat (ORIGINATOR # VIRTUALNAME # TIMESTAMP.STATE)
state

• new: the file is being prepared (your status)
• sent: the file is ready to be sent (to start sending)
• we2e: The file is sent, wait for e2e

[93Kamuran]

Hello, I want to use your project for my customer is working with VW /Audi in Germany. they want to communicate with the oftp2 protocol. My customer has got Odette ID and certificate. They told me that we send application form to VW/Audi then they send an email to us such as
" I have now set up a new station for you with the station identifier SID = PDC.
Please make sure that your OFTP2 service is available and reports with a valid certificate.
We are currently rejecting you
Opening connection to ...:*
from ...

java.net.ConnectException: Connection refused

"

I Downloaded your project as zip file and tried to change some codes to run the app. So I could not run it. Could you give some advice me, please?

[Atmaca25]

We have an error "CS2001 Source file 'C:\ProjeStudio2017\OdetteFTP\des-master\SimpleDbg..\Common\AssemblyInfoServer.cs' could not be found. SimpleDbg C:\ProjeStudio2017\OdetteFTP\des-master\SimpleDbg\CSC"

Would you help me?