We don't have a way to stop creating NodeJS API Proxies. However, we can disable the NodeJS feature which will cause any API Proxies that attempt to use the functionality will fail to deploy. This can be done by setting the property nodejs.enabled in nodejs.properties on all Message Processors to false as shown below:
nodejs.enabled=false
By default, this property is commented out and set to true as shown below:
#nodejs.enabled=true
You can use the below steps to uncomment and set the property to true on Message Processors :
1. Create message-processor.properties file if does not exist under /opt/apigee/customer/application
2. Add the following line to /opt/apigee/customer/application/message-processor.properties
conf/nodejs.properties+nodejs.enabled=false
3. Please run dos2unix on the message-processor.properties to make sure any dos characters are not copied over.
4. Make sure it has the correct ownership of apigee and group apigee:
chown apigee:apigee message-processor.properties
5. Restart the message processor
/opt/apigee/apigee-service/bin/apigee-service edge-message-processor restart
Please follow #1 to #5 on all message processors.
Note: If you have multiple target endpoints in an API Proxy with some having NodeJS backend servers and some having non NodeJS backend servers will also fail if we disable the above mentioned property.
LinkedIn
Twitter
