Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Getting grouper-ws to run

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Getting grouper-ws to run


Chronological Thread 
  • From: Scott Koranda <>
  • To: Dick Visser <>
  • Cc:
  • Subject: Re: [grouper-users] Getting grouper-ws to run
  • Date: Mon, 3 Sep 2012 08:24:33 -0500

> Hi guys
>
> I'm trying to get grouper web services to run, but i'm having trouble
> with tomcat.
> My code sits in /opt/GROUPER_2_1_BRANCH, and it looks like I need to
> be in /opt/GROUPER_2_1_BRANCH/grouper-ws/grouper-ws.
> In there I created a build.xml and ran 'ant dist', which seemed to work:
>
>
>
> root@grouper:/opt/GROUPER_2_1_BRANCH/grouper-ws/grouper-ws#
> ant dist
> .....
> BUILD SUCCESSFUL
> Total time: 16 seconds
>
>
> Now I have to add it to Tomcat.
> On my Ubuntu 12.04 box the vhosts (or whatever they're called in the
> java world) appear to sit in /etc/tomcat6/Catalina/localhost.
> This directory contains two files:
>
> grouper.xml:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <Context
> path="/grouper"
> docBase="/opt/GROUPER_2_1_BRANCH/grouper-ui/dist/grouper"
> reloadable="false"
> />
>
> ROOT.xml:
>
> <Context path="/"
> antiResourceLocking="false" />
>
>
>
> So based on this I created /etc/tomcat6/Catalina/localhost/grouper-ws.xml:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <Context
> path="/grouper-ws"
>
> docBase="/opt/GROUPER_2_1_BRANCH/grouper-ws/grouper-ws/build/dist/grouper-ws"
> reloadable="false"
> />
>
>
> After restarting tomcat I see that the grouper-ws 'vhost' is being
> 'deployed' (whatever that means), but later on only grouper-ui things
> are logged:
>
> Sep 03, 2012 10:06:43 AM
> org.apache.catalina.startup.ClassLoaderFactory validateFile
> WARNING: Problem with directory [/usr/share/tomcat6/server/classes],
> exists: [false], isDirectory: [false], canRead: [false]
> Sep 03, 2012 10:06:43 AM
> org.apache.catalina.startup.ClassLoaderFactory validateFile
> WARNING: Problem with directory [/usr/share/tomcat6/server], exists:
> [false], isDirectory: [false], canRead: [false]
> Sep 03, 2012 10:06:43 AM
> org.apache.catalina.startup.ClassLoaderFactory validateFile
> WARNING: Problem with directory [/usr/share/tomcat6/shared/classes],
> exists: [false], isDirectory: [false], canRead: [false]
> Sep 03, 2012 10:06:43 AM
> org.apache.catalina.startup.ClassLoaderFactory validateFile
> WARNING: Problem with directory [/usr/share/tomcat6/shared], exists:
> [false], isDirectory: [false], canRead: [false]
> Sep 03, 2012 10:06:43 AM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-8080
> Sep 03, 2012 10:06:43 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 511 ms
> Sep 03, 2012 10:06:43 AM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> Sep 03, 2012 10:06:43 AM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.35
> Sep 03, 2012 10:06:43 AM org.apache.catalina.startup.HostConfig
> deployDescriptor
> INFO: Deploying configuration descriptor grouper-ws.xml
> Sep 03, 2012 10:06:46 AM org.apache.catalina.startup.HostConfig
> deployDescriptor
> INFO: Deploying configuration descriptor ROOT.xml
> Sep 03, 2012 10:06:46 AM org.apache.catalina.startup.HostConfig
> deployDescriptor
> INFO: Deploying configuration descriptor grouper.xml
> Grouper starting up: version: 2.1.1, build date: 2012/08/03 15:26:40,
> env: <no label configured>
> grouper.properties read from:
> /opt/GROUPER_2_1_BRANCH/grouper-ui/dist/grouper/WEB-INF/classes/grouper.properties
> Grouper current directory is: /var/lib/tomcat6
> log4j.properties read from:
> /opt/GROUPER_2_1_BRANCH/grouper-ui/dist/grouper/WEB-INF/classes/log4j.properties
> Grouper is logging to file:
> /opt/GROUPER_2_1_BRANCH/grouper-ui/../grouper/logs/grouper_error.log,
> at min level WARN for package: edu.internet2.middleware.grouper, based
> on log4j.properties
> grouper.hibernate.properties:
> /opt/GROUPER_2_1_BRANCH/grouper-ui/dist/grouper/WEB-INF/classes/grouper.hibernate.properties
> grouper.hibernate.properties:
> grouper_user@jdbc:postgresql://ip6-localhost:5432/grouper
> sources.xml read from:
> /opt/GROUPER_2_1_BRANCH/grouper-ui/dist/grouper/WEB-INF/classes/sources.xml
> sources.xml groupersource id: g:gsa
> sources.xml groupersource id: grouperEntities
> sources.xml jdbc source id: terenaUsers:
> core_user@jdbc:postgresql://[2001:610:148:dead::8]/tnc2012?ssl=true
> Sep 03, 2012 10:06:52 AM org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on http-8080
> Sep 03, 2012 10:06:52 AM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 8869 ms
>
>
> And indeed, when I visit http://grouper.terena.org:8080/grouper-ws/, I
> get a 404.
> Any idea what I'm missing here?
>
>

Hi,

I don't think you should expect there to be a response at
/grouper-ws/. On my testbed I also get a 404 for that URL.

As a better test try using your web browser to get the WSDL
that the grouper-ws makes available:

http://FQDN:8080/grouper-ws/services/GrouperService?wsdl

You should see (after perhaps authenticating, depending on
your deployment) a somewhat large XML document that describes
the SOAP services.

Once you can see the WSDL then you know the service is running
and you can try using the web services directly to manipulate
the Grouper state. I prefer to use curl for that testing and the more
REST like service endpoints. For example to add a subject to a
group:

curl --insecure -X PUT -c /tmp/mycookies -b \
/tmp/mycookies --user some.login --location-trusted \
http://FQDN/grouper-ws/servicesRest/json/v2_1_000/groups/astem%3Aagroup/members/someSubject

Depending on your configuration you may not need --insecure,
-c, and -b. Note that the URL must be properly encoded ('%3A'
instead of ':' e.g.).

Scott K



Archive powered by MHonArc 2.6.16.

Top of Page