Data

How is data brought into 3forge?

3forge is a flexible tool for collecting and analyzing data from several data sources and types.

Here are some of the common ways data can be transferred in and out of 3forge:

1. Datasource Adapters

   Used to connect 3forge to an external database; 3forge sends queries and receives responses. These are configured through the GUI.

   • Use Case: Pulling data from and pushing data to an Oracle database.

2. Feed Handlers

   Used to connect 3forge to external data feeds; 3forge receives data sent over the feed. These are configured through the local.properties files.

   • Use Case: Receiving data from a KDB stream.

3. Clients

   Custom clients for sending data into 3forge; 3forge receives data sent by the client and can send commands to the client. Clients are written in Java, Python or .NET.

   • Use Case: Receiving data from another application and sending instructions.

4. JDBC Connection

   A standard database connection port that other applications can use to send data into 3forge. Configured through the local.properties files.

   • Use Case: Communicating with another Java application.

5. 3forge's REST API

   A diagnostic tool containing information about 3forge and the JVM state. Accessible via the 3forge_rest endpoint. See this page for details.

   • Use Case: Getting statistics about JVM memory usage.

6. Real Time Processor

   A method of processing data directly within the Web including from external sources without needing to store information in the Center.

   • Use Case: Bloomberg BPipe or other user-specific cases where data cannot be stored in the Center.

Note

The documentation only provides guides for some of the more complex Datasource Adapters and Feed Handlers. For an exhaustive list see the Supported Software list.

Additionally, data that has been sent into 3forge before from a Feed Handler or Client can be replayed using the Replay Plugin and an AmiMessages.log file.