How to use Login Information Parser Plugin?

Can you prefix "java:" to your data source name and try it once "java:/jdbc/pocTestingOracleDS"

@brindas I tried it on on-premise environment and it is working fine for me. I think there is issue with your datasource name . Just try "java:/jdbc/pocTestingOracleDS" or "/jdbc/pocTestingOracleDS" once

And one more thing, make sure while publishing data store mapping should be done properly. It means when you create cdt from table(17.1 version) make sure you make linenumber as primary key and auto generated then configure in your data store and publish the data store

No. It's empty again. I am using Oracle SQL developer. For "logins" table, I have used the following fields and data types:
COLUMN_NAME DATA_TYPE NULLABLE
loginpk NUMBER(10,0) No
date DATE Yes
time TIMESTAMP(6) Yes
lineNumber NUMBER(10,0) Yes
isValidLogin NUMBER(10,0) Yes
username VARCHAR2(255 CHAR) Yes
ipaddress VARCHAR2(255 CHAR) Yes

Am I going wrong in the above definition?

I think you should not add any extra column just use the definition as given in shared component.

As you have added an extra column loginpk, do not add any extra column.

CREATE TABLE IF NOT EXISTS `logins` (
`date` date NOT NULL,
`time` time NOT NULL,
`lineNumber` int(11) NOT NULL,
`isValidLogin` tinyint(1) NOT NULL,
`username` varchar(100) NOT NULL,
`ipaddress` varchar(20) NOT NULL,
UNIQUE KEY `unique` (`date`,`lineNumber`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

modify the above script as per the oracle syntax as you are using oracle as backend.
Once this is done create CDT as Appian has provided feature to create CDT from table in 17.1 version (If you are working on 17.1 version), otherwise create CDT manually and make sure you make linenumber as primary key and autogenerated. add entity in your datastore and publish the datastore. make sure the mapping should be done properly and provide datasource name either "java:/jdbc/pocTestingOracleDS" or "/jdbc/pocTestingOracleDS" then try it once.

@mayureshs I tried giving the datasource name in both the ways, but "logins" table is empty.

I used the same "Login Information Parser" plugin earlier in "My SQL" . It was working fine. I don't know why the "logins" table in empty when I use it in "Oracle" DS.

Have you changed your script?

Ya I have changed my script. I am using only the fields and the respective data types mentioned.