The http address here uses the admin server; it is so that you can connect to one port but if there are many managed servers running the admin server can find a running server to connect to. So have you enabled https to the admin server?
I would recommend not using the CLI here anyway; use the REST APIs to run jobs.
I have a limitation not to use the EDQ UI which mean I might not want to expose the \edq context root to the End user. I am not sure if this is possible if I want to use the Rest APi.
For the CLI, Can I use a workaround and specify the jmx port of the managed server in the director.properties and call the jobs using the managedserver:port ?
You can configure an SSL port for EDQ JMX in director.properties, along with settings for the certificate and key. You can then refer to this port directly in the EDQ JMX tools. Using SSL througth the admin server has not been certified for this use.
In director.properties you will need to set:
and define the keystore containing the certificate, as documented in https://docs.oracle.com/middleware/1221/edq/secure/ssl_tomcat.htm#DQSEC169
You will need at least these settings:
management.ssl.km.crt = crtfile
management.ssl.km.key = keyfile
management.ssl.km.keystore = keystorefile
management.ssl.km.storetype = storetype
management.ssl.km.storepw = storepassword
management.ssl.km.alias = alias
management.ssl.km.keypw = keypassword
These settings are added to director.properties. There is no file named ssl.properties, I am not sure why you used that.
I got the issue. I was trying to enable the jmx port by adding it to the serverstart parameters. I realized that editing the director.properties would suffice.
The ssl.properties is custom file to specify the required keystore details when I have set the 'management.ssl.clientauth' property to 'required' . I am able to execute the jobs with SSL enabled JMX as well.
Thanks for your inputs.