EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

Cannot open connectors when CommunityConnectors.war is deployed in WebSphere 9.x


Jianglong Ma

Software Engineer, Principal • MicroStrategy


Users may not be able to open connectors when the CommunityConnectors.war is deployed in WebSphere 9.x. This article provides a workaround to this situation and it won't block subsequent operations.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Description


When using WebSphere 9.x, opening a connector causes two error messages to appear: 
"xxx could not be saved, because the source file could not be read. Try again later, or contact the server administrator."
"You have chosen to open a BIN file. Would you like to save this file?"

ka0PW0000001JY3YAM_0EM2R000000lZVx.jpeg

Steps to Reproduce

Prerequisite: You must be using WebSphere 9.x and have at least one connector deployed.

  1. Open a dossier and click New Data.
  2. In the Data Sources dialog, click on the Neo4j connector. The two errors appear.

 

Why is this happening?


By default, the connector URL is set to 

https://localhost:8443/CommunityConnectors/connector_name/
. If you click the Neo4j connector, the URL would be 
https://localhost:8443/CommunityConnectors/neo4j/
.
When the URL opens, the application server redirects to 
https://localhost:8443/CommunityConnectors/neo4j/index.html
, which is the actual URL of the Neo4j page. This redirect is a standard Java behavior and can be controlled by declaring welcome files. Every application server is meant to conform to Java EE specifications; however, IBM WebSphere is not. So when a user clicks the connector, the redirect does not occur and the errors appear instead.
 

Solution


This issue is currently under investigation. For an immediate solution, a workaround has been provided.
 

Workaround


To avoid the two error messages, you can edit the connector URL to use the actual URL name instead of the redirect.

How to Edit the Connector URL

  • In the Data Source dialog, hover over the connector and click Edit Connector.
ka0PW0000001JY3YAM_0EM2R000000lZXP.jpeg
  • In the Enter a URL field, add index.html to the end of the connector URL.
ka0PW0000001JY3YAM_0EM2R000000lZXU.jpeg
  • Click Save. The connector should work as expected.

Comment

0 comments

Details

Knowledge Article

Published:

August 6, 2019

Last Updated:

March 21, 2024