Hello,
Could you confirm what you are doing specifically at the time that you see the issue you have reported?
- Have you added the Slack Request Node to the canvas in Toolkit?
- Have you clicked on "Launch connector discovery" and provided details of a valid Policy Project and Vault?
- Have you clicked "Launch discovery" and has a second window appeared to allow you to perform discovery for the Slack Request Node?
- This second window is the Electron process, I believe from the logs you have got to this step?
The error logs indicate some timeouts, but it is not clear what you are doing at the time - what information are you entering, have you clicked a particular button... What stage are you at in the process and what is the behaviour that you are experiencing specifically?
------------------------------
Martin Ross
IBM
------------------------------
Original Message:
Sent: Wed January 03, 2024 10:16 AM
From: Amit Kapila
Subject: Slack connector
Hi Martin,
Thanks for getting back to me. I am not running Cloud Pak for Integration or App Connect Enterprise running in containerised environment with custom images. I am running an IBM App Connect Enterprise installation in 'developer' mode on Ubuntu.
Here is some information.
$ lsb_release -a
LSB Version: core-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
------------------------------
Amit Kapila
Integration Developer
Virtusa Limited
London
UK
amitkapila@hotmail.com
+44 (0)2085707240
+44 (0)7976529902
Original Message:
Sent: Tue January 02, 2024 02:47 AM
From: Martin Ross
Subject: Slack connector
Hello Amit,
Could you please confirm the environment that you are running? Is this App Connect Enterprise Certified Containers, Cloud Pak for Integration or App Connect Enterprise running in containerised environment with custom images?
Some of the paths within the error log you attach (i.e. /home/ace12user/ace-12.0.11.0/tools/tkelectronapp/resources/) imply that you are using the Toolkit authoring experience opposed to Designer - could you confirm?
Could you confirm what you are attempting to do at the time you are seeing those errors?
------------------------------
Martin Ross
IBM
Original Message:
Sent: Mon January 01, 2024 12:05 PM
From: Amit Kapila
Subject: Slack connector
Connecting to Slack from an App Connect Designer instance in a containerized environment (local connector)
| Ibm | remove preview |
| | Connecting to Slack from an App Connect Designer instance in a containerized environment (local connector) | | If you are using an App Connect Designer instance within an installation of IBM Cloud Pak for Integration or IBM App Connect Enterprise certified container, and have enabled locally available connectors, you can choose to use a local connector to connect to your Slack account. | | View this on Ibm > |
|
|
I followed the instructions in https://www.ibm.com/docs/en/app-connect/saas?topic=slack-connecting-from-containerized-environment-local-connector#connect_container__get_access_token but I cannot connect. I have attached the log error.
$ mqsimode
BIP1802I: This IBM App Connect Enterprise installation is in 'developer' mode.
BIP8071I: Successful command completion.
./ace version
Version: '12.0.11.0'
Product: 'IBM App Connect Enterprise'
Build Number: '3785'
IB Level: 'ib000-L231213.3785_P'
Server level: 'S000-L231212.12998'
Toolkit level:'20231212-1649'
------------------------------
Amit Kapila
Integration Developer
Virtusa Limited
London
UK
amitkapila@hotmail.com
+44 (0)2085707240
+44 (0)7976529902
------------------------------