Grouper Users - Open Discussion List

["chqh" <>]

Thank you sir and your advice.

For your questions:

1 .I use the quick start grouper ui, which run on the Tomcat server 5.5.23 in windows XP.

2.What kind of person registry are you running?
    I have a SQL person registry in postgres. This person source have already been defined in $GROUPER_HOME/grouper-api/conf/sources.xml.

 

My person source in sources.xml is as follows:

 

 <source adapterClass="edu.internet2.middleware.subject.provider.JDBCSourceAdapter">
    <id>qsuob</id>
    <name>QSUOB JDBC Source Adapter</name>
     <type>person</type>
     <init-param>
       <param-name>maxActive</param-name>
       <param-value>16</param-value>
     </init-param>
     <init-param>
       <param-name>maxIdle</param-name>
       <param-value>16</param-value>
     </init-param>
     <init-param>
       <param-name>maxWait</param-name>
       <param-value>-1</param-value>
     </init-param>
     <init-param>
       <param-name>dbDriver</param-name>
       <param-value>org.postgresql.Driver</param-value>
     </init-param>
     <init-param>
       <param-name>dbUrl</param-name>
 <!--<param-value>jdbc:hsqldb:C:/projects/GrouperI2MI_1-2/grouper/dist/run/grouper</param-value>-->
  <!--<param-value>jdbc:hsqldb:hsql://localhost:9001</param-value>-->
  <param-value>jdbc:postgresql://localhost:5432/grouperdb</param-value>
     </init-param>
     <init-param>
       <param-name>dbUser</param-name>
       <param-value>postgres</param-value>
     </init-param>
     <init-param>
       <param-name>dbPwd</param-name>
       <param-value>xxxx</param-value>
     </init-param>
      <init-param>
       <param-name>SubjectID_AttributeType</param-name>
       <param-value>id</param-value>
     </init-param>
     <init-param>
       <param-name>Name_AttributeType</param-name>
       <param-value>name</param-value>
     </init-param>
     <init-param>
       <param-name>Description_AttributeType</param-name>
       <param-value>description</param-value>
     </init-param>

 

     <search>
         <searchType>searchSubject</searchType>
    <param>
         <param-name>numParameters</param-name>
         <param-value>1</param-value>
        </param>
         <param>
             <param-name>sql</param-name>
             <param-value>
select
   subject.subjectid as id, subject.name as name,
   lfnamet.lfname as lfname, loginidt.loginid as loginid,
   desct.description as description
from
   subject
   left join (select subjectid, value as lfname from subjectattribute
     where name='name') as lfnamet
     on subject.subjectid=lfnamet.subjectid
   left join (select subjectid, value as loginid from subjectattribute
     where name='loginid') as loginidt
     on subject.subjectid=loginidt.subjectid
   left join (select subjectid, value as description from subjectattribute
      where name='description') as desct
     on subject.subjectid=desct.subjectid
where
   subject.subjectid = ?
             </param-value>
         </param>
     </search>
     <search>
         <searchType>searchSubjectByIdentifier</searchType>
    <param>
         <param-name>numParameters</param-name>
         <param-value>1</param-value>
        </param>
         <param>
             <param-name>sql</param-name>
             <param-value>
select
   subject.subjectid as id, subject.name as name,
   lfnamet.lfname as lfname, loginidt.loginid as loginid,
   desct.description as description
from
   subject
   left join (select subjectid, value as lfname from subjectattribute
     where name='name') as lfnamet
     on subject.subjectid=lfnamet.subjectid
   left join (select subjectid, value as loginid from subjectattribute
     where name='loginid') as loginidt
     on subject.subjectid=loginidt.subjectid
   left join (select subjectid, value as description from subjectattribute
      where name='description') as desct
     on subject.subjectid=desct.subjectid
where
   loginidt.loginid = ?
             </param-value>
         </param>
     </search>
     <search>
        <searchType>search</searchType>
   <param>
         <param-name>numParameters</param-name>
         <param-value>4</param-value>
        </param>
         <param>
             <param-name>sql</param-name>
             <param-value>
select
   subject.subjectid as id, subject.name as name,
   lfnamet.lfname as lfname, loginidt.loginid as loginid,
   desct.description as description
from
   subject
   left join (select subjectid, value as lfname from subjectattribute
     where name='name') as lfnamet
     on subject.subjectid=lfnamet.subjectid
   left join (select subjectid, value as loginid from subjectattribute
     where name='loginid') as loginidt
     on subject.subjectid=loginidt.subjectid
   left join (select subjectid, value as description from subjectattribute
      where name='description') as desct
     on subject.subjectid=desct.subjectid
where
   (lower(name) like concat('%',concat(?,'%')))
   or (lower(lfnamet.lfname) like concat('%',concat(?,'%')))
   or (lower(loginidt.loginid) like concat('%',concat(?,'%')))
   or (lower(desct.description) like concat('%',concat(?,'%')))
             </param-value>
         </param>
     </search>
   </source>

 

---

chqh

2007-07-26

---

发件人： Cramton, James

发送时间： 2007-07-25 21:26:44

收件人： chqh

抄送：

主题： RE: About the grouper initialization

 

Hello,

 

I noticed your posting to the Grouper-users list, and that is the best place to ask questions like this, because there are many more folks on the list to answer your questions. First, you should give the grouper-users list some more information about your system:

 

1. What web UI authentication method are you using? Tomcat-users.xml, or an apache/ldap configuration?

 

2.What kind of person registry are you running? LDAP? If so, what platform? SunOne, AD, Novell, etc.? Or do you have a SQL person registry in postgres? This person source will need to be defined in $GROUPER_HOME/grouper-api/conf/sources.xml.

 

3. As I understand it, you are not able to find person subjects in the UI's search form. Are you able to add person subjects to groups when you add members in the UI?  If you are not able to find person subjects in any screen of the UI, the problem probably lies in your person source adapter definition in sources.xml. Make sure you have the person source defined properly in the sources.xml file. And "properly" can be a tricky thing. I have found the search subjects form to be very reliable in returning person subjects, if Grouper can reach the person source defined in sources.xml.

 

Once you've looked over your person source configuration, you may want to send a copy of the person source adapter configuration from sources.xml (without the login name/password) to the grouper-users list so we can suggest changes.

 

James Cramton

Lead Programmer/Analyst

Brown University

401 863-7324

---

From: chqh [mailto:]
Sent: Wednesday, July 25, 2007 12:05 AM
To: Cramton, James
Subject: About the grouper initialization

Dear Sir,

         I am sorry to bother you again. But now I just get some troubles on the initializion of grouper administartion. I will appreciate your help indeed.

         Now I am working on the new grouper v1.2.

        After I finish all the configuration, I start to add root stem and wheel group by using the gsh tools. And I add some subjects and subject attributes by excuting sql script in the postgres database. Then I added one subject into the wheel group by using the gsh command "add member". So it works. And then I access the grouper administration system by login the ui. And I created stems and groups smoothly. But then the weird things happens. When I searched subjects by using the searching tool in the ui, I found nothing turning up except the groups that I have create.

 

    However, when I used the grouper qs-start hsqldb, I found it's no difficult to search subjects. Is it something wrong with my initialization steps? Could you help me, Sir?

 

    BTW, the platform I work on is windows XP. And I use tomcat 5.5.23 as the container for grouper ui.