CONNECT CONNECTIVITY OPTIONS

 
 

Covisint Connect - Connectivity Solution and Requirements

HTTP(S) Mailbox:

  • Connect to the Covisint Connect messaging hub using unidirectional (to Covisint) TCP/IP link over the public Internet, VPN tunnel network.
  • Trading Partner sends (POST) and retrieves (GET) from Covisint mailbox
  • No network setup required.
  • Production URL:
    • https://messaging.covisint.com/invoke/HTTPConnector.Mailbox/post
    • https://messaging.covisint.com/invoke/HTTPConnector.Mailbox/get
  • Staging (test) URL:
    • https://messaging2.stg.covisint.com/invoke/HTTPConnector.Mailbox/post
    • https://messaging2.stg.covisint.com/invoke/HTTPConnector.Mailbox/get
  • Covisint Operations will provide username/password for both test and production.
  • Download the HTTP(S) Connector Guide
 

HTTP(S) Persistent:
  • Connect to Covisint using a unidirectional or bi-directional TCP/IP link over the public Internet, VPN tunnel network.
  • Trading Partner sends (POST) to Covisint and Covisint sends (POST) to Trading Partner.
  • Firewall must be opened for the outbound channel IP/URL on port 443 that the customer provides. Inbound access is already permitted.
  • URL:
    • https://messaging.covisint.com
  • Username/Password required on inbound channel. Outbound depends on the customer’s requirements.
  • Covisint Operations will provide username/password.
  • Download the HTTP(S) Connector Guide
 

Lower Layer Protocol – LLP:
  • Standard for transmitting HL7 messages via TCP/IP
  • Network setup required (open firewall for specific IP and port) and VPN
    • Provide IPSec VPN Tunnel application to Network team
    • Network team will provide port number to use specific to the IP address
    • Persistent connections:  Request network team to permit persistent connection for the IP address.  Network team will need to configure the IP address on the load balancer and firewall to allow this.  Otherwise, Covisint default behavior is to close idle connections after one hour.
  • Trading Partner sends to Covisint with sync ack
  • Covisint sends to Trading Partner with sync ack, if applicable.
  • Download and complete the LLP Production Application Form and attach it to the connection request.
 

Secure FTP with SSL (FTPS)
  • Network setup required (open firewall for specific IP and port)
  • Available in two methods
    • Mailbox (push-pull) - Trading Partner sends (PUT) and retrieves (GET) from Covisint mailbox
    • Persistent (push-push) - Trading Partner sends (POST) to Covisint and Covisint sends (POST) to Trading Partner
  • IP address:
    • 64.37.249.13
    • Ports 21, 990 and range 20900 thru 20999
  • Covisint Operations will provide username and password.
  • Download and complete the FTPS Production Application Form and attach it to the connection request
 

FTP (VPN):
  • With the File Transfer Protocol (FTP) Connector you can use FTP commands to exchange information with your trading partners through the Covisint Connect messaging hub.
  • To use the FTP Connector, you should have prior knowledge of FTP commands and how to use them.
  • Allows users with standard FTP client software and TCP/IP communications over VPN to execute the following actions:
    • Submit business documents to be processed by the Covisint Connect messaging hub.
    • Retrieve business documents from a Covisint Connect messaging hub mailbox.
  • Available in two methods:
    • Mailbox (push-pull) - Trading Partner sends (PUT) and retrieves (GET) from Covisint mailbox.
    • Persistent (push-push) - Trading Partner sends (POST) to Covisint and Covisint sends (POST) to Trading Partner.
  • Public Internet IP Addresses for messaging
    • 64.37.249.63
  • Firewall access required.
  • Download and complete the FTP (VPN) Production Application Form and attach it to the connection request.
  • Download the FTP (VPN) Connector Guide
 

AS2 Connector:
  • The AS2 protocol enables trading partners to securely exchange business data for XML, binary and EDI or any other data describable in MIME on HTTP or SMTP.
  • The EDI data is sent as a MIME/SMIME messages. Encryption and digital signature are both optional. Thus there are four modes of sending a message:
    • Signed and encrypted – recommended
    • Signed only
    • Encrypted only
  • No signature, No encryption – The EDI payload is sent in a MIME message. This option is not recommended for secure transmission using AS2 protocol.
  • Message Disposition Notification (MDN): The MDN is an acknowledgement receipt sent by the receiver that indicates a secure and successful receipt of the message
  • Firewall must be opened for the outbound channel IP/URL that the customer provides. Inbound access is already permitted.
  • Inbound URLs
    • https://messaging.covisint.com/invoke/AS2Connector.inbound/receive
  • AS2 Certificate Required
  • Covisint operations will provide username/password for both test and production.
  • Download and complete the AS2 Production Application Form and attach it to the connection request
  • Download the AS2 Production Cert
  • Download the AS2 Connector Guide
 

OFTP:
  • The ODETTE FTP Connector is a component of the Covisint Connect messaging hub which supports three major types of OFTP connectivity:
    • X.25 native connection over X.25 public networks
    • X.25 over ISDN connection
    • Internet-based TCP/IP connection.
  • The Odette FTP Connector allows a TP with a standard (version 1.4 compliant) OFTP software to perform the following:
    • Connect to Covisint using a public X.25 network, ISDN dial-up or TCP/IP link over the VPN tunnel network.
    • Submit messages to be processed by Covisint using OFTP-compliant software.
    • Get messages pushed by Covisint to the TP's OFTP server.
  • SSID: O0013009454COVISINT
  • Production X25 address: (0262)45690053030
  • ISDN Number for calling Covisint: 49 (0) 69 24706378
  • ISDN Number when Covisint calls Trading Partner: 49 (0) 69 24706379
  • OFTP IP: 64.37.249.40 Port: 3305
  • Download and complete the OFTP Production Application Form and attach it to the connection request
 

Web sphere MQ:
  • WebSphere MQ, is a popular system for messaging across multiple platforms, including Windows, Linux, IBM mainframe and midrange, and UNIX.
  • There are two parts to message queuing:
    • Messages are collections of binary or character (for instance ASCII or EBCDIC) data that have some meaning to a participating program. As in other communications protocols, storage, routing, and delivery information is added to the message before transmission and stripped from the message prior to delivery to the receiving application.
    • Message queues are objects that store messages in an application.
  • Production
    • mq.covisint.com
    • Internet IP:  64.37.249.29:  1414, 443
  • Firewall Access Required
  • Development work required to create inbound listeners and/or outbound handlers for communication between MQ queues and the Covisint application
  • Download and complete the MQ Production Application Form and attach it to the connection request
 

End to End testing with receiving application or trading partner

  • Covisint will work with receiving enterprise / application to communicate and confirm testing status.
  • The test messages should be copy of application production messages.
  • The objective is to test:
    • Sending/receiving production messages using the new connectivity solution
    • Confirm message processing / translation within Covisint environment
    • Confirm receiving enterprise / application can consume and process message