neo4j-bloom

Neo4j Insight

Master	Build	Cross Version Tests

Development setup

1. Clone this repo
2. Install yarn globally (not required but recommended): npm install -g yarn
3. Install project dependencies: yarn

Development server

yarn start and point your web browser to http://localhost:8085.

Setting up Neo4j Desktop

The Bloom running locally needs to connect to Neo4j Desktop (where the Neo4j DBMS lives). To do this, start Neo4j Desktop.

Once this is set up, start a DBMS in Desktop - Desktop will expose this active DBMS to the default port bolt://localhost:7687,and Bloom will use that default port for connecting to the instance.

The login credentials on the Bloom page is the same as the login credentials of the DBMS (note - the default username is neo4j, the password can be reset for that DBMS in Desktop)

Setting up Neo4j Aura

Neo4j Aura is the Neo4j database running in the cloud. In order to test Bloom against Aura, perform the following steps:

1. Log in into Aura and create a free database
2. Install the cerificate neo4j-insight/openssl/bloom-fake.neo4j.io.crt in your system (on Mac, open keychain access, drag and drop the certificate, double click it and choose "Always trust")
3. In a terminal, go to /etc/hosts file and add 127.0.0.1 bloom-fake.neo4j.io to a new line
4. Run yarn startSSL
5. Connect via https://bloom-fake.neo4j.io:8085?connectURL=neo4j%2Bs://{aura_dbms_id}.databases.neo4j.io:7687 where 'aura_dbms_id' can be found in the Connection URI in ur newly created Aura database (note: in Chrome, type thisisunsafe in order to bypass the ssl checks).

Testing a release against Aura

Peform the same steps as above for installing the certificate and editing the hosts file. Then Bloom can be hosted using serve with the below command: npx serve -l tcp://bloom-fake.neo4j.io --ssl-cert={path_to_bloom}/neo4j-insight/openssl/bloom-fake.neo4j.io.crt --ssl-key={path_to_bloom}/neo4j-insight/openssl/bloom-fake.neo4j.io.key assets

Setting up Neo4j Enterprise

Please have a look at this doc for setup instructions.

Testing

• yarn test to run a single unit test run. A linter will run first.
• yarn dev to have continous unit testing on every file change.
• yarn run e2e {browserNames} to run end-to-end tests with TestCafe (you can specify the browsers to run in a comma-separated list or type all. More info is available in the TestCafe documentation and our testcafe README).
• video record: by default failed test will have screenshot and video as artifacts, if you don't want to get video, simply add this behind your command: --video "" --video-options "" (for example: yarn e2e chrome testcafe/legend.test.js --video "" --video-options "") Under different OS, dependency package for video might be different, if test hanging due to wrong ffmpegPath under testcaferc.json, go to ./node_modules/@ffmpeg-installer/ find out the correct path.

Logging

The logging library loglevel is being applied under the hood, refer to the docs to see for further information or details if required.

To see all logging options, such as setting log levels, printing the logs or downloading log files, open the web browser's console and type bloom_help() and hit enter. A list of options is presented.

All available levels and loggers are printed when entering bloom_help() in the web browser's console.

Available loggers: ROOT, NEVADA, DRIVER, SSO, PERF

Available levels: trace, debug, info, warn, error, silent

There are also URL query parameters available to set the log levels of individual or all loggers.

• The parameter LOGS_LEVEL=<level> will set the logging level to level for all loggers
• The parameter <LOGGER>_LEVEL=<level> will set the logging level to level for the logger <LOGGER>

Examples:

http://localhost:8085?ROOT_LEVEL=warn set the logging level warn for the logger ROOT (the application logs)

http://localhost:8085?LOGS_LEVEL=debug set the logging level debug for the all loggers

http://localhost:8085?LOGS_LEVEL=error&DRIVER_LEVEL=debug&NEVADA_LEVEL=info set the logging level error for all loggers yet for the DRIVER logger the level is set to debug and for the NEVADA logger the level is set to info

You are able to download all log files via the Experimental drawer or via a command outlined in bloom_help().

URL query parameters

Meant for users:

URL query parameter	Example	Description
discoveryURL=url	discoveryURL=https://localhost:8083/discovery.json	See Bloom docs
connectURL=url	connectURL=bolt://localhost:7687	See Bloom docs
search=term	search=Tom Hanks	See Bloom docs
perspective=perspectiveName	perspective=perspective 12	See Bloom docs
run=boolean	run=true	See Bloom docs
sso_redirect=idp_id	sso_redirect=keycloak-oidc	Use for the auto-redirect to a SSO provider login page
LOGS_LEVEL=level	LOGS_LEVEL=warn	Set the logging level to level for all loggers
LOGGER_LEVEL=level	DRIVER_LEVEL=debug	Set the logging level to level for the logger LOGGER

Meant only for developers and application development:

URL query parameter	Example	Description
logout_timeout=seconds	logout_timeout=200	Sets the logout timeout to seconds, meant only for E2E tests
grid_layout=boolean	grid_layout=true	Sets the visualization layout type to a grid layout, meant only for E2E tests, Default: false
ntid=uuid	ntid=jdsf-342-sdf-dfsdf	Tracking ID provided by Aura when launching Bloom from within the Aura console
auth_flow_step=arg	auth_flow_step=redirect_uri	SSO: If the user arrives back to the client application with the URL param auth_flow_step=redirect_uri we know it's time to proceed in the SSO auth process
idp_id=idp_id	idp_id=keycloak-oidc	SSO: The user should arrive with a URL param named idp_id that we can map to the information in the discovery data to figure out how to proceed

Devtools

Download these two chrome extensions:

• React devtools