Get the Node working first, Integration-server should be similar, and you could share the keystore and use the same ssl certificate between the two unless you want them separate.

1) Do you have a keystore created as either a jks or p12 with a valid self-signed or signed certificate where a proper .cnf parms file was used with the openssl commands to create the .csr where it allows the proper commonName=*.yourdomain.com for example.

2) In your node.conf.yaml do you have the HTTPSConnector section correct with a

ListenerPort: 7083

KeystoreFile: /var/mqsi/your-jks-or-p12 # jks or p12

KeystorePassword: keystorepwd::sslpwd ::# from mqsisetdbparms or vault command mqsisetdbparms NODEName -n keystorepwd::sslpwd -u dummy -p keystorepassword

KeystoreType: JKS or P12

Are you getting any errors in the broker log?

What platform are you on? Unix or Windows

Hello Robert,

We are using Linux OS and currently we have deployed IIB to docker swarm and now we have a plan to update IIB to ACE 12. All other things are solved, but still HTTPSConnector does not work.

Juha

Get the Node working first, Integration-server should be similar, and you could share the keystore and use the same ssl certificate between the two unless you want them separate.

1) Do you have a keystore created as either a jks or p12 with a valid self-signed or signed certificate where a proper .cnf parms file was used with the openssl commands to create the .csr where it allows the proper commonName=*.yourdomain.com for example.

2) In your node.conf.yaml do you have the HTTPSConnector section correct with a

ListenerPort: 7083

KeystoreFile: /var/mqsi/your-jks-or-p12 # jks or p12

KeystorePassword: keystorepwd::sslpwd ::# from mqsisetdbparms or vault command mqsisetdbparms NODEName -n keystorepwd::sslpwd -u dummy -p keystorepassword

KeystoreType: JKS or P12

Are you getting any errors in the broker log?

What platform are you on? Unix or Windows