Hi, I'm new to Knowage,
I just downloaded Knowage CE 6.3.1 and installed it on my desktop so I can learn about it.
The idea is that if it works out we would install it on a server for internal use within the non-profit I work for.
It hasn't been that straight forward, first the documentation link on
https://www.knowage-suite.com/portal/group/guest/community-area points to
http://knowage-suite.readthedocs.io/en/latest which does not exist. I did find a manual at
https://release.ow2.org/knowage/Knowage_6.x_CE_Manual.pdf which I hope is up to date.
I could not find a good "getting started" document, but found some logins with google searches that got me in.
I was able to eventually get some company data to display under the "demo_admin" login.
Once I had basic access working, I decided to try and make it more realistic for my environment, and that's where the rough edges started showing.
First, I created a user with "demo_admin". It was accepted, but I couldn't log into it, and when I logged back into "demo_admin" it wasn't there. I tried to create it again, thinking I had messed it up somehow only to be told it already existed. Eventually I tried the "biadmin" user which I had seen references to in various places but hadn't used before, and that did show the user I had created was there. So apparently there is a hole in the process where new accounts created under "demo_admin" are not created in a way that they are part of the same environment.
The "biadmin" also showed none to the data sources, data sets or the cockpit document I had created under the "demo_admin" user. That was not a surprise, in fact the environment was basically empty which was a good place to start building a better example for my company anyway.
I changed the role of the new login to admin, (in general we try not to use shared logins so we know who does what) and logged in as this new user.
Then I tried to create a new JNDI type data source to connect to the server, but for this user the JNDI options were grayed out and were not selectable.
I went back to the "biadmin" user, and was able to create the JNDI based data source for the server, but I had to select a different name than I had used under the "demo_admin" account, even though what I had created before was not visible.
This shows two issues, first although my new login and the "biadmin" login look almost exactly alike (different name and email), they do not act the same.
Second, there can be collisions between data source names even though you cannot see the existing ones.
Does anyone know of a good "getting started" type document?
Why does the admin role not give the same capability as the "biadmin" login has?
Why do names (of data sources at least) collide when you can't see the existing datasource?
Thanks.
Dave.
