To update certificate in message processor as it's due to expire

[sonal2008]

Hi Team, @dchiesa1

We have to update certificate in keytsore.jks and we have 3 message processor and 3 routers instances.

I have created keystore.jks and I have decided to follow below steps to update the certificate:

1. Copy the keystore JKS file to a directory on all Message Processor server, such as /opt/apigee/customer/application
2. Change permissions and ownership of the JKS file:
   chown apigee:apigee /opt/apigee/customer/application/keystore.jks
   chmod 600 /opt/apigee/customer/application/keystore.jks
3. Set the following properties in the message-processor.properties file:
   # Enter the obfuscated keystore password below.
   conf/message-processor-communication.properties+local.http.ssl.keystore.password=OBF:obsPword
4. Stop the Message-Processors and Routers (MP1 and Router1):
   /opt/apigee/apigee-service/bin/apigee-service edge-message-processor stop
   /opt/apigee/apigee-service/bin/apigee-service edge-router stop
5. On the Router, delete any files in /opt/nginx/conf.d:
   rm -f /opt/nginx/conf.d/*
6. Start the Message-Processors and Routers:
   /opt/apigee/apigee-service/bin/apigee-service edge-message-processor start
   /opt/apigee/apigee-service/bin/apigee-service edge-router start
7. Check router and msg processor system logs

Questions:

My questions are how do we restart message processor and routers  without having zero downtime. Shall I follow sequential stop and restart like mp1 and router 1 and then mp2 and router 2 and lastly mp3 and router3?

Are the above mentioned steps correct?

How do I ensure correct certificate is being used ? Can I make a call from router to message processor that validate certificate and view the certificate via any curl command?

Thanks

Sonal

[API-Evangelist]

Interesting steps and may be used early apigee versions..

What certificate are we referring here? Is it Virtual Host certificate or in general SSL certs on the platform?

Can we not just simply follow below & certificate updates are always little interesting ( in most of versions on opdk atleast & end-up restarts)

https://docs.apigee.com/api-platform/system-administration/update-or-replace-ssl-certificate

For the sequence you have it correct but cross check  below once

https://docs.apigee.com/private-cloud/v4.19.01/starting-stopping-and-restarting-apigee-edge

For validation you can check /opt/nginx/conf.d/<<org>>_<<env>>_<<vhname>>.pem  path  to validate if it is reflected & validate using curl.