English German Spanish
Support|Education|Careers|Contact Us

What changes need to be made as a result of the DINET Internet migration?

Article ID: 1085
Date Created: 14/10/2009 09:46:39
Date Modified: 19/10/2009 10:43:46
Applies To: DARWIN 3
ODEX Professional
ODEX Enterprise
ODEX Plus
More Information:

There are 4 products affected by the DINET Internet migration:

  • DARWIN 3
  • ODEX Professional
  • ODEX Enterprise
  • ODEX Plus

The following article explains how to:

  • Check how they connect to DINET
  • Check what IP address/hostname is being used
  • Change the hostname to be oftp.dinet.co.uk or 212.140.163.240
  • How to test the connection
DARWIN3

In DARWIN Administrator, go to the entry for DINET under Communications. On the Overview page for the connection you will see the IP host address being used to connect to DINET. This address should be set to oftp.dinet.co.uk, or 212.140.163.240 if your network/firewall requires you to connect to a numeric IP address.

To test the connection to DINET, use the Send and Receive option in DARWIN Order Processing or DARWIN Invoices to display the communications dialog. Make sure DINET is the selected network and click the Connect button. This will initiate a call to DINET which should end with the message "Normal session termination".

ODEX Professional

In the ODEX user directory, select the entry for DINET and click Update. Check the Access Profile. If this is not set to use a TCP/IP profile then you do not need to make any changes. If you are using TCP/IP to connect to DINET then you need to make sure that the Called Address is set to either oftp.dinet.co.uk or 212.140.163.240

Once you have made this change you can test the new connection details by using the Call Trading Partner option to make a manual call to DINET. This call should end with the message "Normal Session Termination".

ODEX Enterprise

In ODEX Administrator, select DINET from the list of Clearing Centre Networks. On the overview page you will see the sub-system that you are using to connect to DINET. If this is not TCP/IP then you do not need to make any changes. If the sub-system is TCP/IP check the IP host address. This needs to be set to oftp.dinet.co.uk or 212.140.163.240

Once you have made this change, save it and go to the Status page. Click the Test Call button. This will initiate a test call to DINET. If you have the ODEX Communications Monitor open at the same time then you will be able to see the call in progress. Otherwise clicking the Refresh button once the call is complete will update the Status page with the call details. In a successful call the ESID code will be "00 - Normal session termination".

ODEX Plus

Run odexdir to bring up the ODEX user directory and find the entry for DINET. Use the option "S" to edit the entry and check the address specified on the second line below the SSID code. The address should be 212.140.163.240, if it is not then change it and save the change.

Once you have returned to the user directory, use the "C" option to make a call to DINET in order to test the new connection details. You can check the last call details by using the "S" option to view the details again. The OFTP error code should read "Normal Session Termination".

Keywords:



Rate this article

12345

Current rating: 0
1 star = Poor, 5 stars = Perfect)

Feedback

Did this information solve your problem?
 
What can we do to improve this information?
 
Please provide an email address so that we can obtain
further information if necessary (optional):




User Logon
Username/Password:
CONTACT US

UK: +44 (0) 1733 371 311
ES: +34 91 268 66 29
SE: +46 (0) 322 935 25
DE: +49 (0) 40 31112 374


sales@di-international.com
Terms and Conditions | Copyright Data Interchange Plc 2012