CMS to HQ Communication Connection Setups
COMMUNICATION LINE CODES FOR HQ SETUPS:
KWM - HQ1
MGK - HQ2
GFO - HQ3
SMT - HQ4
HKM - HQ5
HQ API set up:
The CMS server will be connection to the EDI HQ platform using TLS security and will need Java 8 installed. To check if it is installed run the following command from the command line:
wrklnk '/QOpenSys/QIBM/ProdData/JavaVM/jdk*'
Make sure jdk80 is present which indicates that java 8 is installed on the server. CMS to HQ Connection
Java requirements for the EDI
Next, check to ensure that the 1-EDI Source HQ program is set up to use java. Go to SUMN03 #9 and look for the 1-EDI Source HQ entry:
Place your cursor on that line and press F2 to check that the path to the correct version of java is set, if not, it can be typed in here.
Once you have ensured that the correct version of java is installed and in use, set up an EDI interface in RAMN02 # 12
Set up page 1 as normal making sure to choose interface type 8
On page 2, set up the user ID and password that will be provided by 1-EDI Source. The data presentation needs to be set to 2 to be able to use the JSON format. Also, whatever you enter in the folder name field is the folder that will be created on the HQ server that receives the uploaded files.
I have attached the API setup instructions for CMS as well as your credentials.
CMS Prod:
Client ID: 54009fd2-1826-4f42-a3fc-7fcf1d02e88d
Secret - 8qXNdnBlpmu0HolRntTZI7qUZs8mS4rNfqV9ZD2TQwHv
CMS Test:
Client ID: 16d3fda2-e9d9-438e-b4ba-25f65bb994ab
Secret - OFyCsWEi9WYCrEQzTuO+K8+Q/IOGokKjc+s/YUah2kRy
Token Endpoint: https://login.epicor.com/connect/token
Transaction Endpoint: https://api.xchange.epicor.com