Background of Installation:
We are configuring Edge Micro Gateway(2.1.0) to our On-premise Edge ( 4.15.07)
Micro is installed on Red Hat Enterprise Linux Server release 6.6 Virtual machine ,and Edge components are also deployed on similar RHEL 6.6 VMs.
1. edgemicro configuration completed
2. Verification completed succesfully;
3. Edge Micro Started successfully
4. edgemicro token get also worked as expected
[root@vmapigeedev06 edgemicro]# edgemicro configure -o org -e performancetest -u dev@org.com -p P@55w0rd -d
current nodejs version is v4.6.0
file doesn't exist, setting up
listdeployments: {"organization":"org","environment":"performancetest","baseuri":"https://api.enterprise.apigee.com","username":"dev@org.com","password":{},"debug":true,"asyncLimit":4}
Going to invoke "https://api.enterprise.apigee.com/v1/o/org/e/performancetest/deployments"
[Error: HTTP error 401]
As seen above the configuration script is somewhere pointing to api.enterprise.apigee.com.
As recommended in some other forum answers, verified the call out policy properties in edgemicro_internal proxy and it reflects the correct on Premise Message Processor destination ip address. Please suggest if this is fix available for addressing this.
LinkedIn
Twitter
