Project

General

Profile

Actions

Support #9276

closed

Database for TwitterMonitor

Added by Salvatore Minutoli almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Category:
Application
Start date:
Jul 14, 2017
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Production

Description

For the TwitterMonitor application a database is needed in order to track the status of crawler process launched.
The structure of the database is in the following file:
http://data.d4science.org/ajBxeWNNOU5FckZSLzcybU4zRmJoQkpHOTlpeEJ1OFhHbWJQNStIS0N6Yz0

The database can be located on the VM with the TwitterMonitor SmartExecutor plugins, or any other node in the SoBigData infrastructure.

Then a Service Endpoint should be created with the name "TwitterMonitorDatabase".

Actions #1

Updated by Pasquale Pagano almost 8 years ago

Please create the DB on the database cluster and then @roberto.cirillo@isti.cnr.it will configure the SE on the IS for the application.

Actions #3

Updated by Andrea Dell'Amico almost 8 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 80

The database is already available, see #7180. I just imported the schema.

Actions #4

Updated by Salvatore Minutoli almost 8 years ago

Is the Service Endpoint, with the name "TwitterMonitorDatabase", also available?

Actions #5

Updated by Roberto Cirillo almost 8 years ago

  • Status changed from Feedback to In Progress
  • Assignee changed from _InfraScience Systems Engineer to Roberto Cirillo

I'm going to create the ServiceEndpoint resource

Actions #6

Updated by Roberto Cirillo almost 8 years ago

  • Status changed from In Progress to Feedback
  • Assignee changed from Roberto Cirillo to Salvatore Minutoli
  • % Done changed from 80 to 100

I've added the new ServiceEndpoint to the SoBigDataLab VRE.
I've also notice that the related ServiceEndpoint in development environment has the following entry name: "postgress":

         <Interface>
            <Endpoint EntryName="postgress">jdbc:postgresql://wafi.iit.cnr.it:5433/twmon</Endpoint>
         </Interface>

In the new resource created in production I've set the following entry name: "postgres":

 <Interface>
            <Endpoint EntryName="postgres">jdbc:postgresql://postgresql-srv.d4science.org:5433/twittermon</Endpoint>
 </Interface>

Is it OK for you?
If you want, I could change the entry name in "postgress".

Actions #7

Updated by Salvatore Minutoli almost 8 years ago

Since I already loaded the DataMiner algorithm using "postgress" as the entry name I would prefer, for the moment, to keep it unchanged: so "postgress" would be better for me. Thanks.

Actions #8

Updated by Roberto Cirillo over 7 years ago

I've changed the name in "postgress" as requested. Please, @salvatore.minutoli@iit.cnr.it could you check and close the ticket if all is ok for you now?

Actions #9

Updated by Salvatore Minutoli over 7 years ago

@roberto.cirillo@isti.cnr.it Is the port number correct (5433) for the current DB server on postgresql-srv.d4science.org ?

Actions #10

Updated by Roberto Cirillo over 7 years ago

Salvatore Minutoli wrote:

@roberto.cirillo@isti.cnr.it Is the port number correct (5433) for the current DB server on postgresql-srv.d4science.org ?

The correct one is the 5432 port. I'm sorry for this. I've just updated the ServiceEndpoint with the right port number. Please @salvatore.minutoli@iit.cnr.it could you re-check now?

Actions #11

Updated by Salvatore Minutoli over 7 years ago

  • Status changed from Feedback to Closed

The ServiceEndpoint works correctly. Thanks.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)