|
1 | | -# Connections |
| 1 | +# Connections UI |
2 | 2 |
|
3 | | -This guide covers both how to configure Graph Explorer with different graph |
4 | | -database engines and how to manage connections within the application. |
5 | | - |
6 | | -## Database Configuration |
7 | | - |
8 | | -This section contains detailed instructions that help when configuring Graph |
9 | | -Explorer with different graph database engines. |
10 | | - |
11 | | -### Connecting to Neptune |
12 | | - |
13 | | -- Ensure that Graph Explorer has access to the Neptune instance by being in the |
14 | | - same VPC or VPC peering. |
15 | | -- If authentication is enabled, read query privileges are needed (See |
16 | | - [ReadDataViaQuery managed policy](https://docs.aws.amazon.com/neptune/latest/userguide/iam-data-access-examples.html#iam-auth-data-policy-example-read-query)). |
17 | | - |
18 | | -### Connecting to Gremlin-Server |
19 | | - |
20 | | -If you are using the default Gremlin Server docker image, you can get the server |
21 | | -running with the following commands: |
22 | | - |
23 | | -``` |
24 | | -docker pull tinkerpop/gremlin-server:latest |
25 | | -docker run -p 8182:8182 \ |
26 | | - tinkerpop/gremlin-server:latest \ |
27 | | - conf/gremlin-server-rest-modern.yaml |
28 | | -``` |
29 | | - |
30 | | -#### Enable REST |
31 | | - |
32 | | -Graph Explorer only supports HTTP(S) connections. When connecting to |
33 | | -Gremlin-Server, ensure it is configured with a channelizer that supports HTTP(S) |
34 | | -(i.e. |
35 | | -[Channelizer Documentation](https://tinkerpop.apache.org/javadocs/current/full/org/apache/tinkerpop/gremlin/server/Channelizer.html)). |
36 | | - |
37 | | -<!-- prettier-ignore --> |
38 | | -> [!TIP] |
39 | | -> The Gremlin Server configuration can be usually found at: |
40 | | -> |
41 | | -> ``` |
42 | | -> /conf/gremlin-server.yaml |
43 | | -> ``` |
44 | | -
|
45 | | -#### Versions Prior to 3.7 |
46 | | -
|
47 | | -If you have a version of Gremlin Server prior to 3.7, you will need to make the |
48 | | -following changes: |
49 | | -
|
50 | | -- **Enable property returns** - Remove |
51 | | - ".withStrategies(ReferenceElementStrategy)" from |
52 | | - `/scripts/generate-modern.groovy` so that properties are returned. |
53 | | -- **Enable string IDs** - Change `gremlin.tinkergraph.vertexIdManager` and |
54 | | - `gremlin.tinkergraph.edgeIdManager` in `/conf/tinkergraph-empty.properties` to |
55 | | - support string ids. You can use `ANY`. |
56 | | -- Build and run the Docker container as normal. |
57 | | -
|
58 | | -### Connecting to BlazeGraph |
59 | | -
|
60 | | -- Build and run the Docker container as normal and connect the proxy-server to |
61 | | - BlazeGraph and your workbench to the proxy-server. |
62 | | -- If using Docker, ensure that the container running the workbench can properly |
63 | | - access the container running BlazeGraph. You can find documentation on how to |
64 | | - connect containers via [Docker networks](https://docs.docker.com/network/). |
65 | | -
|
66 | | -## Connections UI |
| 3 | +This guide covers how to manage connections within the Graph Explorer |
| 4 | +application. For information on configuring different graph database engines, |
| 5 | +see the [First Connection](../getting-started/first-connection.md) guide. |
67 | 6 |
|
68 | 7 | You can create and manage connections to graph databases using this feature. |
69 | 8 | Connections is accessible as the first screen after deploying the application, |
|
0 commit comments