Alteryx to Collibra Integration
Working on setting up the new Alteryx integration (https://marketplace.collibra.com/listings/alteryx-to-collibra-integration/) but running into errors triggering the sync. The main issue seems to be, “Request method ‘GET’ not supported” when triggering from localhost:8080/api/sync. Is there any workaround for this issue?
Benjamin Brendle
Posted 4 years ago · Edited 1 year ago·Last reply 2 years ago
30 comments
Benjamin Brendle
OP2 years ago · Edited@spring-team.collibra.com is there support or specific properties that need to be adjusted to support OAuth2. We had previously used OAuth1 and were successful, but have not had success with OAuth2.
santoshkumarreddybadugula
·3 years ago · Edited@spring-team.collibra.com Facing an issue while executing the project below is the error can any one please help me out. with below error
`2023-03-21 08:23:50,273 [main] INFO org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext - Root WebApplicationContext: initialization completed in 2336 ms
2023-03-21 08:23:50,509 [main] INFO com.collibra.marketplace.library.integration.InternalSharedLibraryConnection - Authenticating with the Collibra Platform…
2023-03-21 08:23:50,515 [main] WARN org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘entryPointController’ defined in file [C:\Users\santoshreddy.badugul\eclipse-workspace\Outputmodule\sbi-alteryx-1.0.1\target\classes\com\collibra\marketplace\alteryx\controller\EntryPointController.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘integrationProcessorService’ defined in file [C:\Users\santoshreddy.badugul\eclipse-workspace\Outputmodule\sbi-alteryx-1.0.1\target\classes\com\collibra\marketplace\alteryx\service\IntegrationProcessorService.class]: Unsatisfied dependency expressed through constructor parameter 2; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘collibraImportApiHelper’ defined in URL [jar:file:/C:/Users/santoshreddy.badugul/.m2/repository/com/collibra/marketplace/collibra-integration-library/1.3.0/collibra-integration-library-1.3.0.jar!/com/collibra/marketplace/library/integration/CollibraImportApiHelper.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘internalSharedLibraryConnection’: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/apache/http/ssl/TrustStrategy
2023-03-21 08:23:50,521 [main] INFO org.apache.catalina.core.StandardService - Stopping service [Tomcat]
2023-03-21 08:23:50,548 [main] INFO org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener -
Error starting ApplicationContext. To display the conditions report re-run your application with ‘debug’ enabled.
2023-03-21 08:23:50,572 [main] ERROR org.springframework.boot.SpringApplication - Application run failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘entryPointController’ defined in file [C:\Users\santoshreddy.badugul\eclipse-workspace\Outputmodule\sbi-alteryx-1.0.1\target\classes\com\collibra\marketplace\alteryx\controller\EntryPointController.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘integrationProcessorService’ defined in file [C:\Users\santoshreddy.badugul\eclipse-workspace\Outputmodule\sbi-alteryx-1.0.1\target\classes\com\collibra\marketplace\alteryx\service\IntegrationProcessorService.class]: Unsatisfied dependency expressed through constructor parameter 2; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘collibraImportApiHelper’ defined in URL [jar:file:/C:/Users/santoshreddy.badugul/.m2/repository/com/collibra/marketplace/collibra-integration-library/1.3.0/collibra-integration-library-1.3.0.jar!/com/collibra/marketplace/library/integration/CollibraImportApiHelper.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘internalSharedLibraryConnection’: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/apache/http/ssl/TrustStrategy`
santoshkumarreddybadugula
·3 years ago · Editedfacing below error on collibra alteryx integration while running the maven build can any one help me on this .
Error starting ApplicationContext. To display the conditions report re-run your application with ‘debug’ enabled.
2023-03-27 14:18:30,165 [main] ERROR org.springframework.boot.SpringApplication - Application run failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘collibraCoreApiHelper’ defined in URL [jar:file:/C:/Users/santoshreddy.badugul/.m2/repository/com/collibra/marketplace/collibra-integration-library/1.3.0/collibra-integration-library-1.3.0.jar!/com/collibra/marketplace/library/integration/CollibraCoreApiHelper.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘apiClient’ defined in class path resource [com/collibra/marketplace/library/integration/InternalApiClientConfig.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.collibra.marketplace.library.generated.core.ApiClient]: Factory method ‘apiClient’ threw exception; nested exception is java.lang.NoClassDefFoundError: feign/slf4j/Slf4jLogger
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:800) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:229) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1372) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1222) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:582) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:955) ~[spring-beans-5.3.23.jar:5.3.23]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) ~[spring-context-5.3.23.jar:5.3.23]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583) ~[spring-context-5.3.23.jar:5.3.23]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:147) ~[spring-boot-2.7.5.jar:2.7.5]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:734) ~[spring-boot-2.7.5.jar:2.7.5]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:408) ~[spring-boot-2.7.5.jar:2.7.5]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:308) ~[spring-boot-2.7.5.jar:2.7.5]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1306) ~[spring-boot-2.7.5.jar:2.7.5]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1295) ~[spring-boot-2.7.5.jar:2.7.5]
at com.collibra.marketplace.alteryx.Application.main(Application.java:38) ~[classes/:?]
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘apiClient’ defined in class path resource [com/collibra/marketplace/library/integration/InternalApiClientConfig.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.collibra.marketplace.library.generated.core.ApiClient]: Factory method ‘apiClient’ threw exception; nested exception is java.lang.NoClassDefFoundError: feign/slf4j/Slf4jLogger
Benjamin Brendle
OP3 years ago · EditedWe were able to solve the previous issue by switching to htttps. We are now facing 3 new issues.
Display name too long - “ERROR”,“message”:"{\“conflicts\”:{\“Line 7,310 contains the following errors:\”:[\“The asset name must have between 1 and 2000 characters, but had 2787 characters.\”,\“The asset display name must have between 1 and 2000 characters, but had 2735 characters.\”]},\“type\”:\“CONFLICT\”,\“message\”:\“The input validation did not complete successfully.\”}",“result”:“FAILURE”}"}
Altx DB Output asset not found - “ERROR”,“message”:"{\“type\”:\“MESSAGE\”,\“message\”:\“The relation ‘has output ALTX DB Output’ could not be made to ‘Alteryx-System > RAW_Tables.yxzp > RAW_Tables.yxmd > aka:6127e1e9979xxx’. This asset was not found in the taxonomy of ‘ALTX DB Output’.\”}",“result”:“FAILURE”}"}
500 error “get workflow by ID” - 500 Internal Server Error from GET https://alteryx-test…com:443/gallery/api/admin/v1/5f7f5xxx/package/?oauth_nonce=xxx&oauth_signature=xxx&oauth_consumer_key=>>>NOT-DISPLAYED<<<&oauth_timestamp=1673366903&oauth_signature_method=HMAC-SHA1&oauth_version=1.0
Errors 1 & 2 cause the integration to fail so they are a priority to resolve. Error 3 we saw in the past and the work around allows the integration to complete successfully, however the customer would like to better understand why the errors are being thrown.
Thanks for all the help!
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Investigating the error messages you sent us, an asset on your Alteryx instance contains a name with too many characters for the integration to ingest it to Collibra. You can analyse the logs further to find which asset is not being created. You can also change the log level by opening the log4j2.xml file and change
<Root level="INFO">to<Root level="DEBUG">and attach the logs.For more information on how the names are generated, please view the section ‘Name format for the different “Inputs” and “Outputs” asset types’ in the documentation. If you still cannot identify the asset, please send us the logs and ensure that there is no sensitive information in these logs.
The second error is likely due to the missing asset that was not imported due to the long name. To confirm this, were these two errors from the same run or were they separate?
The third is an internal server error after sending a request to Alteryx. To investigate this, please send us the full logs and ensure that there is no sensitive information.
Thanks
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Unfortunately we need some assistance from a person who will be back next week. Will keep you updated.
In the meantime, could you please try running the integration again to check if the issue is still present or whether it was just a temporary network issue? Thanks
Benjamin Brendle
OP3 years ago · EditedThank you. We have gotten past the previous error and are now seeing the below:
022-12-22 16:44:20,916 [Thread-2] INFO com.collibra.marketplace.alteryx.service.IntegrationProcessorService - Started synchronizing the metadata
2022-12-22 16:46:26,077 [reactor-http-epoll-2] WARN reactor.netty.http.client.HttpClientConnect - [933bcfb3-1, - R:alteryx-xxxxx-.com/] The connection observed an error, the request cannot be retried as the headers/body were sent
io.netty.channel.unix.Errors$NativeIoException: recvAddress(…) failed: Connection reset by peer
2022-12-22 16:46:26,093 [Thread-2] ERROR com.collibra.marketplace.alteryx.service.IntegrationProcessorService - The integration returned the following error:
org.springframework.web.reactive.function.client.WebClientRequestException: recvAddress(…) failed: Connection reset by peer; nested exception is io.netty.channel.unix.Errors$NativeIoException: recvAddress(…) failed: Connection reset by peer
at org.springframework.web.reactive.function.client.ExchangeFunctions$DefaultExchangeFunction.lambda$wrapException$9(ExchangeFunctions.java:141) ~[spring-webflux-5.3.23.jar!/:5.3.23]
Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Error has been observed at the following site(s):
*__checkpoint ⇢ Request to GET http://alteryx-xxx.com/wokflows/all [DefaultWebClient]
Original Stack Trace:
at org.springframework.web.reactive.function.client.ExchangeFunctions$DefaultExchangeFunction.lambda$wrapException$9(ExchangeFunctions.java:141) ~[spring-webflux-5.3.23.jar!/:5.3.23]
Benjamin Brendle
OP3 years ago · EditedHi @spring-team.collibra.com,
Have you had a chance to investigate the latest error that we are running in to using the Alteryx integration?
Thanks,
Ben
Benjamin Brendle
OP3 years ago · EditedJave version: openjdk version “11.0.17” 2022-10-18 LTS
OpenJDK Runtime Environment (Red_Hat-11.0.17.0.8-2.el8_6) (build 11.0.17+8-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-11.0.17.0.8-2.el8_6) (build 11.0.17+8-LTS, mixed mode, sharing)
Integration Libraries:Manifest-Version: 1.0
Created-By: Maven JAR Plugin 3.2.2
Build-Jdk-Spec: 11
Implementation-Title: alteryx-integration
Implementation-Version: 1.0.1-SNAPSHOT
Main-Class: org.springframework.boot.loader.JarLauncher
Start-Class: com.collibra.marketplace.alteryx.Application
Spring-Boot-Version: 2.5.14
pom.xml
<java.version>1.8</java.version>
com.collibra.marketplace.alteryx.Application
<collibra.integration.library.version>1.1.10</collibra.integration.library.version>
<jasypt.spring.boot.version>3.0.4</jasypt.spring.boot.version>
<springfox.boot.starter.version>3.0.0</springfox.boot.starter.version>
<license.maven.plugin.version>4.1</license.maven.plugin.version>
<org.dom4j.version>2.1.3</org.dom4j.version>
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Please update to the latest version of the Alteryx integration currently available on Marketplace, which is version 1.0.1.
Version 1.0.1-SNAPSHOT of the Alteryx integration was created with some changes specifically for a particular client to test. All these changes are now included in version 1.0.1. Moreover, version 1.0.1-SNAPSHOT works with integration-library v1.1.7, whereas version 1.0.1 uses integration-library v1.1.10. The use of integration library v1.1.10 should resolve certain errors that are occurring when library v1.1.7 is used.
Please note that version 1.0.1 includes a new property boolean flag named alteryx.gallery.use-workflows-all-endpoint . This indicates whether the integration will use the endpoint GET /admin/v1/workflows/all/ when accessing the Alteryx API to get the workflows list.
If ‘true’ it will be used: GET /admin/v1/workflows/all/
If ‘false’ will be used: GET /admin/v1/workflows/
Please review the documentation v1.0.1 on Marketplace for more details.
Benjamin Brendle
OP3 years ago · EditedAfter the update we thought that the integration was working. We are able to kick off the sync and see syncid assets in the catalog. The syncs are empty and we see the following error:
ERROR com.collibra.marketplace.alteryx.service.IntegrationProcessorService - The integration returned the following error: java.lang.IllegalStateException: No suitable default ClientHttpConnector found
at org.springframework.web.reactive.function.client.DefaultWebClientBuilder.initConnector(DefaultWebClientBuilder.java:297) ~[spring-webflux-5.3.20.jar:5.3.20].
Any ideas on what might be throwing this error?
Thanks,
Ben
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Could you please let us know what java version you have installed, what version of the Alteryx integration you are using and whether you have updated to the latest version of the integration library?
Thanks
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Thanks for the above.
It seems that the issue might be since the latest version of the Collibra Integration Library is not being used.
Can you please confirm whether you are using v1.1.10 of the Collibra Integration Library? Thanks
Benjamin Brendle
OP3 years ago · EditedApologies for the lack of detail. Hopefully this error message is a bit more helpful. I am also working on getting logs and scrubbing sensitive information.
{
“message”:“Internal error during execution.”,
“exceptionMessage”:"{“message”:“An unexpected error occurred during execution.”,“details”:“Error reading entity from input stream.”,“cause”:“Unrecognized field \“result\” (class com.collibra.internal.api.model.output.Job), not marked as ignorable (17 known properties: \“userId\”, \“createdOn\”, \“resourceType\”, \“endDate\”, \“name\”, \“system\”, \“startDate\”, \“state\”, \“visibility\”, \“cancelable\”, \“lastModifiedBy\”, \“type\”, \“id\”, \“lastModifiedOn\”, \“createdBy\”, \“progressPercentage\”, \“message\”])\n at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 376] (through reference chain: com.collibra.internal.api.model.output.Job[\“result\”])”}"
}
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Thanks for the update.
The current information is very limited to determine what the issue might be. Therefore, can you please provide the following:
Thanks
Benjamin Brendle
OP3 years ago · EditedWe made it through the proxy issue! Thanks for the help. Now seeing error on the Collibra side:
File (undefined) not found.trueundefined
Value not allowed File (undefined) not found. true undefined ... ...This XML file does not appear to have any style information associated with it. The document tree is shown below.
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Thanks for the update.
Since there is a proxy server between where the Alteryx integration is deployed and Collibra, the following proxy properties should be set in the integration application.properties file for the Integration Library to be able to establish the connection:
For more information on these properties and other properties that can be set, you can refer to the Collibra Integration Library documentation, “Full List” section.
Spring Boot Integration Library - Collibra Marketplace
Java classes to facilitate access to Collibra APIs.
After doing so, please restart the Alteryx integration and then try triggering it using Postman.
In case it fails, it might be ideal to check whether there are any logs after the Alteryx integration is started.
Thanks
Benjamin Brendle
OP3 years ago · EditedThe proxy is configured between the linux machine (curl POST command and the Alteryx integration are running) and Collibra/Alteryx. server.ssl.enabled=false. The basic auth credentials are set in the properties file.
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Thanks for the update.
Just to confirm, is the proxy configured between the machine where the curl POST command is being executed and the Alteryx integration or between the Alteryx integration and Collibra/Alteryx?
In case it is the former one (i.e. between where the curl POST command is being executed and the Alteryx integration), can you please try using
http://instead ofhttps://?You may also try triggering the integration using Postman – https://www.postman.com/
Regarding the application properties, can you please advise whether SSL is enabled –
server.ssl.enabled?Also, when triggering the integration, the basic authentication details according to
trigger.api.usernameandtrigger.api.passworddefined in the properties file should be set. ThanksBenjamin Brendle
OP3 years ago · EditedGetting even closer on their server install. The application is running and saying that it is accepting traffic. We are getting error “SSL routines:ssl3_get_record:wrong version number” -curl POST command to start metadata sync. They do have a proxy configured. Is there anything else that we need to add to the post command or application properties file to ensure we trigger the Alteryx API call successfully?
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Thanks for the update.
The above error was fixed in a previous version of the Collibra Integration Library. Therefore, can you please try using the latest version of the library – v1.1.10?
Spring Boot Integration Library - Collibra Marketplace
Java classes to facilitate access to Collibra APIs.
To do so please refer to section “Updating the Library JAR File” of the library documentation. Thanks
Benjamin Brendle
OP3 years ago · EditedHopefully getting closer now. They were able to get the integration started, but are getting an error thrown by the api:
Caused by: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field “result” (class com.collibra.internal.api.model.output.Job), not marked as ignorable (17 known properties: “userId”, “createdOn”, “resourceType”, “endDate”, “name”, “system”, “startDate”, “state”, “visibility”, “cancelable”, “lastModifiedBy”, “type”, “id”, “lastModifiedOn”, “createdBy”, “progressPercentage”, “message”])
at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 376] (through reference chain: com.collibra.internal.api.model.output.Job[“result”])
Could this be due to an api update on the Collibra side? Any ideas on how to resolve
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Thanks for the update.
Can you please confirm that in their Spring Boot integration they have the following annotation which includes
com.collibra? Thanksspringboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Can you please confirm whether the following Maven command was used to generate the package that is being tested on a server?
By doing so, it should create a JAR file inside the integration
targetdirectory. This can then be deployed/started as explained in the Alteryx to Collibra integration documentation. Thanks(Also, just to let you know that soon a new version of the Collibra Integration Library – v1.1.10 – would be released to address a recent vulnerability in one of the dependencies used.)
Alteryx to Collibra Integration - Collibra Marketplace
A Spring Boot integration that retrieves metadata about the existing workflows in an Alteryx Gallery instance, then this information is transformed and ingested on the Collibra Platform as assets and relations.
Benjamin Brendle
OP3 years ago · Edited@spring-team.collibra.com according to the customer that command to generate the package. Is there anything else that could be causing the error?
Benjamin Brendle
OP3 years ago · EditedWe have run into another issue when standing up the integration on a server vs. running through eclipse. The error is:
no main manifest attribute, in /opt/collibra/spring-boot/sbi-alteryx-feature-workflows-all-endpoint-test/collibra-integration-library-1.1.7.jar
When taking a look at the pom.xml of the jar file it appears to be correctly populated. Any thoughts on what might be causing the error.
springboot_team
·3 years ago · EditedHi @ben.brendle.collibra.com,
Thanks for the update.
Since in the above error, the integration library is being mentioned, can you please confirm that they are trying to run the Alteryx JAR file please?
Also, would it be possible to provide the logs (as a private message, without any sensitive information) when trying to deploy the Alteryx integration?
Just to note that it might be ideal to also upgrade to the latest version of the Collibra Integration Library (v1.1.10 that addresses a recent vulnerability will be made available soon.) or try to install it again on the server in case it was not installed correctly.
Note: As mentioned in the documentation, it should be installed using the following Maven command:
To do so, please follow section “Updating the Library JAR File” of the library documentation.
Spring Boot Integration Library - Collibra Marketplace
Java classes to facilitate access to Collibra APIs.
Once the Collibra Integration Library has been re-installed on the server, using the above command, the following should be done from the Alteryx directory (i.e. whether the Alteryx integration pom.xml file is located):
mvn clean packagejava -jar <jar-file-name>.jar --jasypt.encryptor.password=<decryption_key> --spring.config.location=<properties-file>where:
<jar-file-name>should be replaced with the name of the packaged Alteryx integration JAR file and its location.<decryption_key>should be replaced with the decryption key.<properties-file>should be replaced with the location of an external properties file, in case an external file is used.More information is also available in the Alteryx documentation.
It would be helpful to confirm whether any modifications were made to the Alteryx integration code. Thanks
Benjamin Brendle
OP3 years ago · EditedI provided the steps listed and it seems to have gotten the customer passed the initial issue. They are now running into a new error. The error is caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘collibraImportApiHelper’ defined in URL.
Unfortunately for this customer I am not able to shared detailed logs on this thread. Let me know if you have any initial thoughts on this message and steps to resolve.
springboot_team
·4 years ago · EditedHi @ben.brendle.collibra.com,
You are receiving that warning because you are sending the request using the wrong HTTP Method, i.e. GET. To trigger the integration, you have to use the POST method.
To send such a request, you can either use tools like Postman/Curl, or you can send the request using the browser by visiting the swagger endpoint URL located under API_HOST:API_PORT/swagger-ui/
Thanks
Alexandra Jorgenson
Admin4 years ago · EditedMoving this to the INTERNAL P2P Integrations forum. @spring-team.collibra.com, might you be able to help @ben.brendle.collibra.com and if so, would you mind posting the Q&A (problem/solution) proactively to the external forum so customers/partners could benefit from this intel as well?