Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

A configuration file on the GEODI server determines which local folders and file types to include. This configuration may be customized by client IP, ClientUser, or ClientMachine name. So, you may target a different area for each FileServer or client.

Info

The Agents can be manually installed on FileServers or EndPoints. But if you have many EndPoints, using a tool like ManageEngine or SCCM for deployment is suggested.

GDE agent software updates are auto. It may be set to update from a local source.

GEODI Server has a monitor panel to watch EndPoints.

...

Agent Management Panel

Gliffy
imageAttachmentIdatt4336386146
macroIdc02c52c0-32db-418a-8a1e-64c4cfe9a700
baseUrlhttps://decesw.atlassian.net/wiki
nameGDE-EN
diagramAttachmentIdatt4336648300
containerId3972202552
timestamp1702733720298

...

Subject

Description

Create a new project or choose an existing project to index files.

A separate project is OK for discovery purposes, but adding PCs to an existing project is better if you have Enterprise Search.

This project URL must be accessible from the EndPoints.

The GDE recognizer(from discovery IT group), must be used in the project.

Create a token

Follow the procedure on this page to get the Token.

Generating a GEODI Token

As a best practice, we suggest you create a separate user for the Token. And token users' passwords should not be changed.

Follow the procedures for different OSs

These pages will lead you to each OS.

Child pages (Children Display)

GDE Configuration Settings

The settings determine which local folders and file types to discover. There may be a single setting for all, or you may customize it by clients.

Client Monitoring

Activate GEODI Agent Management Panel

Troubleshooting

...

Token Creation
Anchor
Token
Token

  1. Log in with a user accessing the Source A user with access to the source that GDEs will feed into logs in.

  2. Open the page: <GEODI_URL>>/API/GeodiTokenApi.html?loginWithGuest=1

  3. Select the Source's name using the AllowList.

  4. Now you are ready to create the Token.

  5. This page may be used to check if a token is valid: <GEODI_URL>/API/token_parser.html

...

  1. Alternatively, a token is used on the token interface.

    The interface on page Generating a GEODI Token is opened.

    Feed is activated. "Edit AllowList" is clicked under AllowList, and the content source to which GDE will send our files is selected from the list that appears.

    GEODI_URL and GEOD_TOKEN can be obtained by selecting Feed Source from Resources in the Project wizard. The project name must be given before adding this source.

image-20241218-152522.pngImage Added