Get The PDF - Chrysler

EBMX SF FTP USER GGUIDE 

CHRYSLER 

INFORM MATION TE ECHNOLOG GY MANAG GEMENT 

800 CHR RYSLER DRIVE D 

AUBURN 

HILLS, MI M 48326 

CIMS 48 83-60-01

EBMX Abstract 

EBMX was built to be the premier automotive business-to-business message exchange. The Electronic 

Business Message eXchange (EBMX) allows Chrysler and its partners to exchange electronic business 

documents using standard Internet protocols. Message exchange is enabled from individual desktops or 

via highly integrated machine-to-machine communication. 

EBMX puts Chrysler and its Trading Partners in an optimum position to embrace new and developing 

systems, increase transaction speed, and promote 'just-in-time' processing. EBMX gains are realized 

through the entire supply chain!

Chrysler - EBMX SFTP User Guide 

1 Overview 

1.1 Purpose 

This document will provide information for a Trading Partner (TP) to send and receive transactions to and 

from the Electronic Business Message eXchange (EBMX), using SFTP. The following details the steps 

required for the Trading Partner to put files to the EBMX system via the internet using a VPN connection. 

1.2 Requirements 

The requirements assume the Trading Partner already has necessary software to create and send EDI 

over the Internet. The Trading Partner must provide Chrysler with the following: 

Information to setup the SFTP tunnel with a trading partner 

Setup a connection via the Chrysler VPN. Instruction can be found: 

http://itb-ebus.extra.chrysler.com 

Standards based SFTP Client and Server to communicate with. 

The EBMX system has incorporated SFTP as an add-on process; the current version of the software 

does not support the SFTP protocol. This integration has many caveats: 

1. In order to support the SFTP protocol we have attempted to integrate into the EBMX as close to a 

real-time processes as possible. Therefore when submitting files (see Section 3) there will be a 

delay of up to one minute before the file is processed. 

2. EBMX will provide a status of all processed files located in /RESULTS or /ERRORS. Please do 

not remove these log files. EBMX has taken responsibility to archive and remove result and error 

files greater than seven (7) days old. The removal and archival process will execute at 

approximately 3:00 am each day. 

3. In an attempt to prevent the removal of directories, we have secured and pre-populated the 

required directory structure that will enable you to conduct business with Chrysler. We request 

that you do not in any way change, add, or delete directories or permissions. In doing so we 

cannot guarantee the processing of your files. 

4. When placing a file on the EBMX system using SFTP you are required to put the file in /TMP, 

once the “put” is complete you must move the file to the appropriate directory path (see Section 

3). Be aware that EBMX will remove any and all files with a creation timestamp greater than 24 

hours from the /TMP directory. The cleanup process will execute at approximately 3:00 am each 

day. 

05/25/2011 1 Chrysler


1.3 Key Sharing 

In order to make a connection, Public and Private Keys must be exchanged. The following steps and 

diagrams will assist the Trading Partner (TP) with the exchange. 

1. EBMX sends public key to TP 

2. TP stores public key 

3. TP generates public/private key pairs 

4. TP sends public key to EBMX 

5. EBMX stores TP public Key 

6. EBMX initiates a session with TP to accept the host key 

7. TP initiates a session with EBMX to accept the host key 

Considerations: 

Password authentication is not allowed 

Host based authentication is not allowed 

ssh 1 is not supported 

If you are originating traffic from multiple hosts using the same user id, you are required to: 

1. Duplicate the RSA/DSA keys to each of your hosts 

or 

2. Generate and send Chrysler each of the RSA/DSA public keys. 



2 Receiving (Chrysler Sending) files via SFTP 

2.1 System Access 

2.1.1 Firewall Considerations 

If your system is connected to a firewall, you are required to allow Chrysler access through the firewall. 

Because all firewall software configurations are different, the trading partner must contact their firewall 

support staff to determine the proper configuration. The SFTP server on EBMX will use port 50322 to 

receive. 

2.2 File Placement 

2.2.1 File Placement when Chrysler sends files 

Chrysler needs to logon to the trading partner’s system in order for EBMX to send data via SFTP. 

Chrysler will require a user ID and public/private key pairs for the trading partner’s system to do this. 

When creating this logon ID, specify a home directory or file set with full read/write capability for EBMX to 

place files to. 

All files created on the trading partner's system will be of the form: 

.Annnnn 

Where: ‘DCXaaa’ defines the transaction type contained in the file. (Please see the Application ID Codes 

document on the EDI website for a list of all EDI application codes). 

A = the letter A 

nnnnn = the number 00001 through 99999 

Note: the qualifier, (Annnnn) derives the numeric portion from an EBMX internal file name and is not 

guaranteed to be unique. Over a several day period, a high volume-trading partner might see a 

recurrence of the qualifier. For this reason, any trading partner maintaining logs, audit trails, or file copies 

should take appropriate steps to ensure that confusion does not occur. A suggestion might be to rename 

the file using the date and time the file arrived as a part of the new name. In addition, the sequence 

number is not assigned by trading partner. The numbers are assigned across the entire EBMX system, 

and, therefore, an individual trading partner will see gaps in the sequence number portion of the file 

name. The trading partner should not expect to see consecutive sequence numbers on a consistent 

basis. 



3 Submitting files via SFTP 

In general; the Trading Partner will connect using a standard SFTP client and “put” the file to the EBMX 

system; we require the user to deposit the file in /TMP located under their home directory. Upon a 

successful put, you must move the file to the appropriate sub-directory. Once you move the file, the 

EBMX system has processes that will scan each sub-directory and process the file. After the file is 

processed, a result file is created in the trading pasterns /RESULTS directory. If at any time an error 

occurs during process a file, an error file is created in the /ERRORS directory. Please see each of the 

following sections for specific information pertaining to processing of each type of file. 

As mentioned above, after the put, the user must move the file to the appropriate sub-directory structure. 

As stated in the overview section, Chrysler has loosely integrated the SFTP protocol into the EBMX 

application. In order to have EBMX process the files, we have developed a directory structure that 

mirrors the Sender/Receiver/Document Type nomenclature that EBMX uses to transfer files. You will see 

located in your home directory the following structure: 

//// 

Where: 

Example: 

Sender = Trading Partner ID (not your user ID) 

Receiver = Destination 

Document Type = A predefined label used to describe the characteristics of the file. 

/TESTDOC 

/TESTDOC/LOOPTEST 

/TESTDOC/LOOPTEST/LOOPBACK 

/TMP 

/ERRORS 

/RESULTS 

EBMX will recognize two types of EDI transactions – real time and batch. Real time transactions include 

ASN/ASC (856) and STARS 214. All other EDI and VICS/VISTA transactions are batch processed. 

It should be noted that multiple types of submissions might be needed based on the nature of business 

being done with Chrysler. For example, a production supplier would normally need to send ASN's using 

the real time submission process and any other document with the batch processes. Similarly, a carrier 

who is required to send in ASC's and/or STARS 214's would do so using the real time submission 

process and other documents such as Freight Bills using the batch processes. 



3.1 File Permissions (access mode) 

In order to successfully process a file, there are is a minimum required set of file permissions. All files 

placed on the server must have read and write access at the group level. Most SFTP Client 

implementations will set the file permissions based on the local file at the time of creation. Please verify 

that any file created has the following minimum access modes: 

drwxrwxrwx 2 ecx36adm ebmx 512 Dec 8 08:57 . 

drwxrwxr-x 3 ecx36adm ebmx 512 Nov 5 10:00 .. 

-rw-rw-rw- 1 testid ebmxsshd 7209 Dec 9 10:51 

If file permissions are not correct, most SFTP clients provide the chmod command, example: 

sftp> chmod 666 

If your SFTP client does not provide a command to alter the file permissions, please contact your 

technical support for assistance. 

3.2 Results Directory 

After EBMX successfully processes the file, an entry in written to the /RESULTS, this entry is a zero 

length file with the following naming convention: 

..... 

Where: 

sender = TP sender ID 

receiver = the receiver of the file 

doctype = Document type ID 

filename = name of file that was placed on the system 

tracking ID = a unique number that identifies the submission into EBMX 

timestamp = date and time of the submission in the format YYYYMMDDHHMMSS 

An example file: 

TESTDOC.EDI.EDIX12.prod.test.4782122.20100914142201 



3.3 Submitting Initial Loop-Back Test 

This initial test will be completed by the trading partner to test network configuration and access. The 

trading partner will submit a file that is immediately sent back to test access through firewalls and ability 

for data to be delivered through EBMX. 

3.3.1 Example Session 

Trading Partner initiates an SFTP session to EBMX. (Please see Appendix A for a detailed session) 

Changes directory to /TMP: 

cd /TMP 

Transfers a file: 

put 

Moves file to Document Type directory: 

rename /TESTDOC/LOOPTEST/LOOPBACK/ 

At this time, within approximately 1 minute the file is processed and delivered to the requested 

destination and a result file is placed in the /RESULTS directory. It is recommended you monitor this 

directory. See section 3.2.1 Expected Results for a description of the results file. 

3.3.2 Expected Results 

A successful Loop-back test will result in the following: 

/RESULTS/..... 

Where: 

/RESULTS = Pre-configured directory created at sign-up. (Do Not Remove) 

Sender = TESTDOC 

Receiver = LOOPTEST 

Doc type = LOOPBACK 

Filename = Name of file from the put/move command 

Tracking ID = upon a successful submit, EBMX returns a numeric sequence number 

Timestamp = Date and time of the submit 



3.4 Submitting files via SFTP Example 


Connecting to clmsd058b.cldc.chrysler.com... 

You are accessing Chrysler Group LLC systems. 

Connected to EBMX SFTP server. 

Connection accepted. 

Access to Chrysler's computer systems is controlled. 

Chrysler authorizes use for its business purposes only. 

Unauthorized access is prohibited due to risk of irreparable harm to Chrysler. 

Chrysler management may monitor use to ensure compliance with its policies. 

Chrysler may terminate access privileges, take disciplinary action 

and/or institute civil or criminal proceedings to enforce this policy. 

If any part of this policy is unacceptable to you, please disconnect now!!! 

Thank you. 

YOUR ACCESS IS BEING LOGGED & MONITORED!!!! 

sftp> cd /TMP 

sftp> put prod.test 

Uploading prod.test to /TMP/prod.test 

prod.test 100% 103 0.1KB/s 00:00 

sftp> rename prod.test /TESTDOC/LOOPTEST/LOOPBACK/prod.test 

sftp> cd /RESULTS 

sftp> ls 

TESTDOC.LOOPTEST.LOOPBACK.prod.test.4782122.20100914142201 


sftp> bye 

3.4.2 Expected Results 

Check the /RESULTS directory 

: 

: 


sftp> ls 



sftp> bye 

: 

: 



4 Real Time Data Submission via SFTP 

4.1 Submitting ASN/ASC (856) via SFTP 

EBMX will not process ASN/ASC transactions larger than 300k. If ASN/ASC’s are larger than this they 

will need to be separated into multiple submissions smaller than 300k. In the case that an Trading 

Partner submits a large ASN/ASC, EBMX will return an error message in an 824/997 document pair. 

Note: for Freight Consolidators sending in ASCs element ISA08 should be 04000FC. This instructs the 

CHASE system to process the 856 as an ASC rather than as an ASN. This is required for Freight 

Consolidators using the EBMX directly or other VAN). 

A detailed session for Real Time ASN/ASC transactions is contained in following section: 

4.1.1 ASN/ASC (856) Parameter Description 

Application Directory Structure 

ASN/ASC /CHASE/EDIX12 

Example: 56789B/CHASE/EDIX12/ 

TP ID = EBMX Member Identifier/Account Identifier 

4.1.2 Sample Session 












Thank you. 


sftp> cd /TMP 

sftp> put chase.asn.asc 

Uploading chase.asn.asc to /TMP/prod.test 

chase.asn.asc 100% 103 0.1KB/s 00:00 

sftp> rename chase.asn.asc /56789B/CHASE/EDIX12/chase.asn.asc 


sftp> ls 

56789B.CHASE.EDIX12.chase.asn.asc.4782122.20100914142201 

sftp> bye 



4.2 Submitting STARS 214 Transaction via SFTP 

A detailed session for Real Time STARS 214 transactions is contained in following section: 

DO NOT USE THIS FEATURE UNTIL DIRECTED TO DO SO BY CHRYSLER! 

4.2.1 STARS Parameter Description 


STARS 214 /STARS/EDIX12 

Example: 56789B/STARS/EDIX12/ 


4.2.2 Sample Session 












Thank you. 


sftp> cd /TMP 

sftp> put stars.214 

Uploading stars.214 to /TMP/ stars.214 

stars.214 100% 103 0.1KB/s 00:00 

sftp> rename stars.214/56789B/CHASE/EDIX12/stars.214 


sftp> ls 

56789B.STARS.EDIX12.stars.214.4782122.20100914142201 

sftp> bye 



5 Batch Data Submission via SFTP 

EBMX will recognize two types of EDI transactions – real time and batch. Real time transactions include 

ASN/ASC (856) and STARS 214. Batch transmissions include EDI and VICS/VISTA 

5.1 Submitting Batch Transactions 

5.1.1 EBMX Submit Parameter Requirements 

The following table shows the directory structure for the respective application: 


EDI /EDI/EDIX12 

Example: 34567A/EDI/EDIX12/ 

VICS/VISTA Production 

(510, 520, 530, 540, 550, & 630) 

/VISTA/EDIX12 

Example: 34567A/VISTA/EDIX12/ 

VISTA 127 – Carrier Baying Order /VISTA/PHOLD 

Example: 76543/VISTA/PHOLD/ 

VICS 

824, 926, 928, & 997 

/VICS/EDIX12 

Example: 69832/VICS/EDIX12/ 

VICS/VISTA – Test 

(Test VISTA 510, 520, 530, 540, 550, & 630) 

/VISTT/EDIX12 

Example: 69832/VISTT/EDIX12/ 

Test VISTA 127 – Carrier Baying Order /VISTT/PHOLD 

Example: 69832/VISTT/PHOLD/ 

Test VICS 824, 926, 928, & 997 /TVICS/EDIX12 

Example: 69832/TVICS/EDIX12/ 

Modular Provider 

Tier 1 to Modular Provider Tier 2 

Modular Provider 

Tier 2 to Modular Provider Tier 1 


/< Receiver ID, prefixed with ‘MS2’>/MSEDIX12 

Example: MS99661/MS256743/MSEDIX12/ 

/< Receiver ID, prefixed with ‘MS1’>/MSEDIX12 

Example: MS99661/MS156743/MSEDIX12/ 















Thank you. 


sftp> cd /TMP 

sftp> put prod.test 

Uploading prod.test to /TMP/prod.test 

prod.test 100% 103 0.1KB/s 00:00 

sftp> rename prod.test /34567A/EDI/EDIX12/prod.test 


sftp> ls 

34567A.EDI.EDIX12.prod.test.4782122.20100914142201 

sftp> bye 



6 Retry Handling - Undeliverable Messages (Chrysler to Trading 

Partner) 

The EBMX will attempt to send (PUSH) any EDI or proprietary formatted message to a trading partner 

using SFTP PUSH as soon as the EBMX receives the messages from the source application. 

The PUSH mode assumes that the trading partner’s SFTP server will be up and running on a 7 x 24 x 

365 basis. Recognizing that this cannot always be the case, EBMX has implemented a series of 

message retry strategies. These strategies operate in such a way that whenever EBMX tries to deliver a 

message to a trading partner and is unsuccessful, EBMX will wait a configured period of time and try 

again at the end of that time period. It will try repeatedly until a certain number of retry attempts have 

been made. When the specified numbers of retry attempts have been made, the message will be 

logically copied to a directory on EBMX. 

Upon retry exhaustion, an email message is generated and sent to the trading partner in addition to all 

concerned parties at Chrysler. The email message is sent to the address that the trading partner 

specified in the EBMX subscription submission. This address can be a distribution list if the trading 

partner so desires. EBMX requests that the notification email be a generalized address for the trading 

partner’s company rather than an individual. The trading partner can change the current email address 

by submitting a request to the Help Desk and request that the ticket be routed to the EBMX. The Help 

Desk can be reached at 1-800-332-9978. When communicating with the Help Desk, please provide the 

supplier code being referenced and the email address to be used in the future. Failure to provide this 

information may result in a change not being made because the trading partner’s membership record 

cannot be found. 

The retry strategy used for each message will depend on the Chrysler priority of the message content. 

An example table is provided below: 

Priority Attempts 

Interval 

(Minutes) Example 

10 12 5 ASR (response to an ASN) 

20 24 15 862 SDS 

30 18 20 846 Pay as Built 

40 24 30 Default (e.g. 830 Release) 

50 24 60 996 transaction 

60 4 720 850 Purchase Order 

70 6 720 A quarterly proprietary file 

80 2 1 LOOPTEST file 



An example of the email that will be sent is as follows: 

Subject: EBMX Deliver Failure Notice (SFTP_Retry) 

An EBMX message destined for your server has exhausted a set of pre-defined 

retry attempts and has been archived. 

Relevant information regarding the failed transmission: 

Sender: EBMX 

Receiver: tpid 

Doctype: FTP_ACTIVE_RETRY 

Date/time: 2001-07-26:10:07:43.21 

Tracking ID: 6319 

To request a re-transmission, forward this email to ebusdesk@chrysler.com 

Messages are retained for a maximum of 14 days then removed from the system. 

If you have not requested a re-transmission during that period, it is your 

responsibility to contact the source application for the data. 

Please review your system and network to find and fix reasons the message could 

not be delivered. 

Further questions or issues should be addressed to the Chrysler Help Desk at 1- 

800-332-9978. Please have the trouble ticket routed to EBMX. 

Thank you 

Upon receipt of the email above, the trading partner must contact the EBMX support desk to have the 

message re-transmitted. EBMX support personnel will make no further attempt to ensure that the 

message is delivered to the trading partner. It is the responsibility of the trading partner to ensure 

that this message is delivered. 



Appendix A – Sample SFTP session 

Text in bold is user supplied commands/responses. 

cli007cpsd01:$ sftp -oPort=50322 testdoc@clmsd058b.cldc.chrysler.com 


You are accessing Chrysler systems. 










Thank you. 


sftp> cd TMP 

sftp> put test 

Uploading test to /TMP/test 

test 100% 8867 8.7KB/s 00:00 

sftp> rename test /TESTDOC/LOOPTEST/LOOPBACK/test 


sftp> ls -ltra 

drwxr-xr-x 7 31080 973 512 Mar 26 13:02 .. 

-rw-rw-r-- 1 31080 973 0 Mar 29 08:49 

TESTDOC.LOOPTEST.LOOPBACK.test.4427541.20100329084933 

drwxrwxr-x 2 31080 973 512 Mar 29 08:54 . 

-rw-rw-r-- 1 31080 973 0 Mar 29 08:54 

TESTDOC.LOOPTEST.LOOPBACK.test.4427553.20100329085429 

sftp> 



Appendix B – File Name Requirements 

The following rules should be adhered to when creating file names: 

All filenames must be unique within the Sender/Receiver/Document Type directory. 

Valid file names should consist of upper and lower case alphabetic characters, numbers, 

underscores and periods. 

Embedded spaces are not allowed. 

Special characters are not allowed. 

File name length should be no more than 100 characters. 



Appendix C – Documentation Version Control 

Current 

Date Author Change from Previous Version 

02/08/2010 GLC9 Initial Version 

09/14/2010 GLC9 Update per Group Review 

01/05/2011 GLC9 Added File Permissions Section

Get The PDF - Chrysler

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?