App Connect

 View Only
  • 1.  App Connect Enterprise 12

    Posted 22 days ago

    Hi all,

    I am struggling with App Connect Enterprise 12 and I have not found proper instruction how to setup ACE 12 TLS configuration, integration-node, port 7083,  and integration-server, port 7843. I have followed instructions, but no success. It shouldn't be complex task. Could someone share proper instructions how I can configure TLS, including keystore, truststore etc.



    ------------------------------
    Juha Mikkonen
    ------------------------------


  • 2.  RE: App Connect Enterprise 12

    Posted 22 days ago

    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



    ------------------------------
    Robert Rehms
    ------------------------------



  • 3.  RE: App Connect Enterprise 12

    Posted 22 days ago

    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



    ------------------------------
    Juha Mikkonen
    ------------------------------



  • 4.  RE: App Connect Enterprise 12

    Posted 22 days ago

    Sorry you're having this issue.  There is not enough information to help you here.  I would open a case with IBM support if you have not already done so.



    ------------------------------
    Robert Rehms
    ------------------------------