One, the native debugging Gateway Engine 1, Service registration Center
2, service provider release (remote Tomcat8.5.15): http://10.110.17.20:7070/SvcApp/index.jsp2.1, Svcapp.war configuration
2.2. Publish Catalogue 10.110.17.20/opt/tomcat8.5.15/webapps
Publish Svcapp.war to this directory
2.3. Start the application
Cd/opt/tomcat8.5.15/bin
./startup.sh
2.4. Verify the Application
http://10.110.17.20:7070/SvcApp/index.jsp
2.5, if Svcapp.war is a oauth-server, need to publish its client svccli.war2.5.1, server Svcapp.war database configuration
2.5.2, client configuration files
2.5.3, verifying svccli access Svcapp get Access_token
Http://10.110.17.20:7070/SvcCli/client_credentials
3. Gateway engine (native Eclipse+jetty): http://localhost:9000/api-gateway-engine/client_details3.1, config file
Database
Redis Configuration
3.2. Start the application
3.3. Verify the Application
Http://localhost:9000/api-gateway-engine/client_details
4, Developer application release (this machine: tomcat8.5.15)
4.1. Configuration Files
4.2, Rundevapp.bat
del/q%tomcat_home%\webapps\devapp.war
RMDIR/Q/S%tomcat_home%\webapps\devapp
Copy D:\workspace_apigw_iop\DevApp\target\DevApp.war%tomcat_home%\webapps\devapp.war
%tomcat_home%\bin\startup.bat
4.3. Verification effect Devapp and Api-gateway-engine connectivity test:: Application Gateway Token:http://localhost:8080/devapp/client_credentials
Devapp, Api-gateway-engine, and Svcapp connectivity tests:: Invoking a remote service:
Api-gateway Practice (14) new service Gateway-demo Environment Setup