Yes, you should keep the config files for the loader in all your deployments. Does the query return 5 members? What is the issue?
You can ignore those GSH warnings
On Behalf Of Wayne Hall
Sent: Friday, September 25, 2015 10:32 AM
Subject: [grouper-users] grouper-loader help
video as a guide to setup a test case grouper loader, for the most part seems to work. However I am experiencing some issues provisioning members to our employees grouper-loader group.
In our setup we will query from a remote mssql db, and it seems the query is working. From the NewUI I can use the "Run loader process to sync group" on the employee group, and get a Success message as follows:
Success: the group was updated via loader Loader ran successfully, inserted 0 memberships, deleted 0 memberships, total membership count: 5.
However running gsh -loader gives a Warning & Error as follows:
Grouper warning: jarfile mismatch, expecting name: 'subject.jar' size: 260483 manifest version: 2.2.1. However the jar detected is: /path/to/grouper.apiBinary-2.2.1/lib/grouper/subject.jar, name: subject.jar size:
259419 manifest version: 2.2.1 Error: Cannot properly read UTF string from resource: grouperUtf8.txt: 'ٹٺٻټكلل'
And after running those methods, no member changes are made to the employees grouper-loader group verified under AdminUI.
The three grouper.hibernate.properties files (api, ui, ws) are as follows:
hibernate.connection.url = "jdbc:mysql://localhost:3306/grouper
hibernate.connection.username = grouper
hibernate.connection.password = /path/to/key.txt
And the three grouper-loader.properties files (api, ui, ws) are as follows:
db.dbname.user = dbusername
db.dbname.pass = /path/to/key.txt
db.dbname.url = "jdbc:sqlserver://remote_mssql.edu
Questions: do all three (api, ui, and ws) hibernate and loader files need to be edited (are they all used/needed)? In terms of managing the employees group using the grouper-loader, is there something obvious
I am missing in trying to add members?