![]() |
|
ECGridOS Developer Development related posts. |
![]() |
|
Thread Tools | Display Modes |
#1
|
||||
|
||||
![]()
This question was submitted by e-mail from an existing customer who is moving to ECGridOS. We will use this thread as the predecessor to a formal Interconnect Setup FAQ.
Quote:
GXS - 212 is the main GXS VAN. 215 is the old IBM system, you will not be adding any QIDs here, only use this if you find the QID is already on this. 600 is now off-line. SPS Commerce, you will not be able to add a QID to these Networks, so you will only be able to set up interconnects with QIDs that are already in our routing table. If you need to interconnect with an SPS QID that does not exist, send an e-mail to NetOps. 104 - I think you meant the Loop Test for Chrysler which is actually 509. This shows up as a Mailbox rather than a VAN on our system. Go ahead and set up the Interconnect, traffic will not route until the Loop Test is complete. Once you set up the Interconnect, send an e-mail to NetOps requesting the Loop Test. I will work with Crystal to complete a table for everyone to refer to. Thanks for a great question. -=tg=- |
#2
|
|||
|
|||
![]()
Hi all,
1. How can I start posting new threads? I saw it yesterday but I could not find it again. 2 I have question on this command ECGridOSNewQID <user> <password> ZZ*COVTEST1 "Covalent ECGridOS Test1" When I use this command the QID will be registered to VAN. Do I need to use paramerter NetworkID at the end so it can belong to my NetworkID? |
#3
|
||||
|
||||
![]()
Bruce, you are referring to the Sample Code example. If you do not include the [NetworkID] parameter, the system will automatically default to your own network.
-=tg=- |
#4
|
||||
|
||||
![]() Quote:
Using TPAddVAN works great for setting up IDs (e.g. 5790000260973:14) on Networks where we have an established Interconnect. You would look up the NetworkID and then use TPAddVAN to add the ECGridID to that VAN then InterconnectAdd() to make sure the proper request is placed with that VAN through our expert engine. In this case we do not yet have an established Interconnect with Evenex. In that case, you would send a request to NetOps@ecgrid.com with all the information you have about the VAN/Network including contacts, your customer and ID, their customer and ID. We will then approach the VAN, make an introduction and create the Interconnect. Once that is in place, we will let you know. As each VAN operates differently, this is largely a manual process (could end up being FTP, SFTP, IPSec VPN, AS2, X.400, etc.). Once established, future trading partners on that VAN can be automated with TPAddVAN() and InterconnectAdd() functions. There is a learning curve to the operational side of this. We are doing our best to minimize this; however, the lack of standardization between VANs at this time does add to the complexity of setting up new relationships. We hope to eliminate most of the need for InterconnectAdd() by automating that process based on ID alone in the near future. -=tg=- Last edited by Todd Gould; 06-17-2011 at 11:45 AM. |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|