When setting up a new trading partner or business integration process, thinking through the process beforehand can greatly decrease the implementation time and help minimize problems. Many integration projects can come to a grinding halt in the middle of implementation if it’s only later realized that required data is not configured in your backend application, or if your system doesn’t support the particular communication protocol your new trading partner intends to use. “Looking before leaping” will help alleviate potential problems later.
Prior to any new trading partner implementation, you should first determine and assess the required communications protocol. In other words, how will your trading partner send and receive data to and from you? If your system cannot support your trading partner’s intended protocol, it may be necessary to ask them if an alternative form of communication could be used. For example, your trading partner requires a direct AS2 connection, but you don’t support AS2 communication. However, you do support VAN communication via FTP. You might request that your trading partner consider an AS2 connection with your VAN.
The following list represents common communication methods and general questions for consideration when implementing that method (the information necessary to communicate using this protocol that may affect the communications method to be implemented):
- FTP – (File Transfer Protocol)
- Is the FTP “secured” and, if so, what are the encryption requirements?
- What are the address, username, and password?
- What directories should you send and retrieve data from?
- Is there a specific filename and format that needs to be used?
- Will you ‘GET’ the data from the partner’s system or will your partner ‘PUT’ the data on your system?
- Who is responsible for clean-up/archive procedures? What is needed?
- Is this to be in ‘ACTIVE’ or ‘PASSIVE’ mode?
- Is this to be “Plain”, “Explicit”, or “Implicit” FTP?
- VAN – (Value Added Network)
- What is your trading partner’s ISA (Interchange) ID/Address?
- What is your trading partner’s VAN?
- If separate VANs, is there an Interconnect charge and, if so, who pays?
- Do you and/or your trading partner use a test mailbox?
- What are the kilo-character charges?
- Does your VAN have a separate mailbox charge?
- AS2 – (Applicability Statement 2)
- How will you generate/obtain your company AS2 certificate?
- Did you and your trading partner exchange certificates and AS2 IDs?
- When will the certificates expire?
- What is the IP Address your trading partner is sending from?
- Is this IP Address open on your firewall?
- What IP Address and Port are you sending to?
- Does your partner have your outbound IP Address open on their firewall?
- WEB SERVICE
- Who is the “Consumer” and who is the “Provider”?
- Have you obtained the WSDL (Web Services Description Language) does it contain everything needed to set up the integration process?
- What is the URL where the data is being sent-to/received-from?
- What are the email addresses of all your trading partners and recipients?
- Do they want the data in the body of the email or sent as an attachment?
Once the communications portion of a trading partner is configured, the next step is to test the connection by sharing test data. Depending on the communications method, there might be an automated acknowledgment sent back to verify the connection was good (such as an MDN for AS2 or a ‘Delivered’ notification in your mailbox for VAN). Otherwise, it may require that you contact your trading partner to verify communication results.
Part 2 of this blog and topic will cover how to configure your translation process for the data you will be receiving and sending to and from your trading partner.