Try OpenEdge Now
skip to main content
Getting Started
Setting Up Secure Communications : Using the procertm utility

Using the procertm utility

If you are using HTTPS for communications with a remote OpenEdge Management Trend Database, you use the demo keystore — — to validate secure communication from the OpenEdge Management installations that are trending to a remote management console (the location of the OpenEdge Management Trend Database). The Digital Certificate that identifies the Certificate Authority who issued the remote management console's digital certificate must be in the for the validation to succeed.
The file contains a number of trusted root digital certificates for an OpenEdge Management demo and common, public Certificate Authorities. It is not typically necessary for you to modify the file; however, the file contains neither the digital certificate for every public Certificate Authority nor certificates for any privately run company Certificate Authority.
You can obtain the distributed list of certificates by running the procertm utility and listing the contents of the file certificate store. You can also use the procertm utility to add any Certificate Authority's root certificate to the, if not already there.
When the remote management console's issuing Certificate Authority is not already present, you must do the following:
1. Contact the CA who issued the management console's digital certificate and obtain the CA's trusted Root Digital Certificate. This may be returned in either PEM (.0, .txt, or .pem) or DER (.cer or .crt) format.
2. If the CA root digital certificate is in a PEM format (with a file extension of .0, .txt, or .pem), use the procertm tool to convert it to DER format (identified with a.cer file extension).
3. Use the procertm tool to import the DER-formatted CA digital certificate into the certificate store.
* Managing the trust keystore with procertm
* Converting digital certificates with procertm