konnexionsgmbh / dderl

DDErl: Data Discovery Tool.

Table of Contents

Features
Start Console
Certificates
Building DDErl

---

Features

1. Browse mnesia and oracle tables in the browser
2. Add and update data
3. Import and Export data
4. Send and receive data from one desitination to other on the same session
5. SQL support for queries
6. Filter, Sort, Distinct and Statistics on data
7. Multifactor authentication support (SMS, SAML and username/password)
8. JSON parsing with SQL
9. Tailing of tables
10. Log table rotation and purging
11. Snapshot and restore table
12. Cluster backup and restore
13. Configuration encryption for ssl certificates and passwords
14. D3 graph support to plot graphs
15. Save views of tables
16. Query history support
17. Connect to other imem server over TCP with SSL
18. CSV file parsing

Start Console

1. rebar3 shell or ESCRIPT_EMULATOR=werl rebar3 shell (for GUI in windows) or ERL_FLAGS="-proto_dist imem_inet_tcp" rebar3 shell (to start with imem_inet_tcp as proto_dist)
2. go to https://127.0.0.1:8443/dderl in your browser

Certificates

DDErl runs on SSL. A default certificate/key pair is supplied. This, however can be changed either by replacing these files at installation or modifying configuration in ddConfig table ([{dderl,dderl,dderlSslOpts}]). A sample configuration is given below:

[{cert,<<48,...,107>>},
 {key,{'RSAPrivateKey',<<48,...,192>>}},
 {versions,['tlsv1.2','tlsv1.1',tlsv1]}]

erlang:ssl describes all possible options above. To convert a PEM crt/key files to DER (accepted by erlang SSL binary certificate/key option above) public_key:pem_decode/1 may be used as follows to obtain the DER binary of the PEM certificate files:

> {ok, PemCrt} = file:read_file("server.crt").
{ok,<<"-----BEGIN CERTIFICATE-----\nMIICyTC"...>>}
> public_key:pem_decode(PemCrt).
[{'Certificate',<<48,130,2,201,48,130,2,50,2,9,0,241,25,...>>,not_encrypted}]
> {ok, PemKey} = file:read_file("server.key").
{ok,<<"-----BEGIN RSA PRIVATE KEY-----\nMIICXAI"...>>}
> public_key:pem_decode(PemKey).              
[{'RSAPrivateKey',<<48,130,2,92,2,1,0,2,129,129,0,160,95,...>>,not_encrypted}]

dderl's Issues

upgrade esaml to latest from hex

Check support for data type 8

This is using the OCI driver. To be compared to new odpi solution.

This turns out to be a relevant an important query (hidden and invisible columns in 12c).

SELECT
table_name, column_name, data_type, data_length, column_id, default_length,
data_default
FROM
user_tab_cols
WHERE
table_name = 'CONTRACT'

[ocistmt::execute:706] unsupporetd type 8

BLOB/CLOB are not working

Displaying data that contains BLOB/CLOBs is not working currently.

BEGIN-END issue with pong function

Using oranif for

BEGIN
:VARCHAR2_OUT_RESULT := pong(:VARCHAR2_IN_PING);
END;

returns

{error,function_clause}

whereas using oci for

BEGIN
:SQLT_CHR_OUT_RESULT := pong(:SQLT_CHR_IN_PING);
END;

returns

ORA-06550: Zeile 2, Spalte 29: PLS-00201: Bezeichner 'PONG' muss deklariert werden ORA-06550: Zeile 2, Spalte 1: PL/SQL: Statement ignored

Note: after creating the PONG function, it properly works for oci:

CREATE OR REPLACE
FUNCTION PONG (
p_ping in Varchar2
) Return VARCHAR2
Is
Begin
RETURN p_ping;
End;
/

but not for odpi (no response, no error message).

SLAVE-DOWN Issue on joins

For odpi I get on sbs1

for

SELECT
CON_ID, CON_CODE, CON_OPKEY, CIOT_IWDID, CIOT_TRCTID, CIOT_CURID
FROM
contract,
CONIOT
WHERE
CIOT_TRCTID = 'SMS'
AND CIOT_CONID = CON_ID
AND CON_ESID = 'A'
AND NOT (CON_ESID IN ('R', 'D'))
AND con_etid = 'TOC'

where this is the result for oci