Accenture MDR Quick Start Guide for GreenPlum DatabaseĀ®

This quick start guide will help Accenture MDR customers configure GreenPlum DatabaseĀ® (DB) to allow log collection from the Log Collection Platform (LCP).

Ā 

The document includes the following topics:

Supported Versions

A list of supported versions is available in the Accenture MDR Supported Products List document

(Accenture_MDR_Supported_Products_List.xlsx) which can be found in

Accenture MDR portal - https://mss.accenture.com/PortalNextGen/Reports/Documents

Port Requirements

Table 1-1: Port requirements for LCP communication.

Source

Destination

Port

Description

LCP

GreenPlum Database

5432 (TCP)

Default port

Configuring GreenPlum DB

Note: Greenplum DB stores its events in a database. To read these event logs, the LCP requires a read- only user account.

Follow the instructions below to create a read-only account, and then configure the Greenplum DB to use PostgreSQL to store events.

To configure Greenplum DB with PostgreSQL as the database, follow the steps below.

  1. To create a read-only database user account for the PostgreSQL server, follow the steps below.

  • Connect to the Postgresql database server.

  • At the SQL prompt, type the following commands:

CREATE ROLE gpdbreadonly LOGIN ENCRYPTED PASSWORD 'UGFzc3dvcmQ=' RESOURCE

QUEUE pg_default;

GRANT SELECT on gp_toolkit.gp_log_system to gpdbreadonly;

  • After creating a read-only user, we can retrieve the required logs from the Greenplum DB.

2. To enable logging of connection and disconnection, follow the steps below.

  • Login to the Greenplum DB via the gpadmin user.

  • Execute following commands:

a. gpconfig -c log_connections -v on;

b. gpconfig -c log_disconnections -v on;

3. To download the PostgreSQL JDBC driver, follow the steps below.

Note: If you have the latest version of the driver, rename it as: postgresql-9.4-1201.jdbc4.jar

  • Place the postgresql-9.4-1201.jdbc4.jar file in the following path:

a. LCP On box - /opt/Symantec/simserver/collectors/drivers/postgresql-9.4-1201-jdbc4/

b. Linux Off box - /opt/Symantec/simserver/collectors/drivers/postgresql-9.4-1201-jdbc4/

c. Windows Off box - C:\Program Files\PostgresqlJDBCDriver\ The event structure is as follows:

Logtime

Event date

loguser

User name

logdatabase

The accessed database

logpid

Process id

logthread

Thread number

loghost

Source Host

logport

Source Port

logsessiontime

Session timestamp

logtransaction

Transaction id

logsession

Session id

logcmdcount

Command count

logsegment

Segment Number

logslice

Slice number

logdistxact

Distributed transaction

loglocalxact

Local transaction

logsubxact

Subtransaction

logseverity

Vendor Severity

logstate

State

logmessage

Event Description

logdetail

Detailed message

loghint

Hint info

logquery

Executed query

logquerypos

Query position

logcontext

Context info

logdebug

Debug

logcursorpos

Cursor position

logfunction

Function info

logfile

Source code file

logline

Source code line

logstack

Stack trace

LCP Configuration Parameters

Table 1-2: The Greenplum DB event collector (DB -3793) properties to be configured by MDR are shown in the table.

Property

Default Value

Description

Database URL

jdbc:postgresql://<IP address or hostname>:5432/<databasename>

The database URL string that needs to be configured on the collector by MDR.

IP Address or Hostname - Hostname or IP address of the database.

Database name - The name of the database in which the Greenplum DB events are stored.

5432 (TCP port) - The default port number for DB connectivity.

Note: If the database is configured to use a different port number, please advise the MDR onboarding team.

User Name

Custom Value

The username for the database account mentioned in the Pre-Installation Questionnaire (PIQ).

Password

Custom Value

The password for the database account mentioned in the PIQ.

Ā 

Legal Notice

Copyright Ā© 2021 Accenture. All rights reserved.

Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.