GridShib for Globus Toolkit Installation
A lightweight alternative to installing the full Globus Toolkit is to only install the Java WS Core component of GT4, and then install GridShib for GT on top of that. In fact, this is the only option under Windows, which does not support the full Globus Toolkit, so the following "Quick Start" shows how to layer GridShib for GT on top of Java WS Core under Windows.
This page gives detailed instructions for installing Java WS Core and GridShib for GT on Windows. Software requirements include JDK 1.4.2 (or higher) and Ant 1.6 (or higher), which we assume are already installed on Windows.
- Install the binary version of Java WS Core 4.0.4
- Extract the ZIP archive to any folder on your hard drive (say, c:\globus).
- Open a Command Prompt window, change directory to the installation directory, and set the
GLOBUS_LOCATION
environment variable (which is case sensitive, even on Windows):> cd c:\globus\ws-core-4.0.4 > set GLOBUS_LOCATION=%CD% > echo %GLOBUS_LOCATION%
- As a crude test, start the container (with transport-level security disabled):
> bin\globus-start-container -nosec Starting SOAP server at: http://141.142.251.212:8080/wsrf/services/ With the following services: [1]: http://141.142.251.212:8080/wsrf/services/AdminService [2]: http://141.142.251.212:8080/wsrf/services/AuthzCalloutTestService [3]: http://141.142.251.212:8080/wsrf/services/ContainerRegistryEntryService [4]: http://141.142.251.212:8080/wsrf/services/ContainerRegistryService [5]: http://141.142.251.212:8080/wsrf/services/CounterService [6]: http://141.142.251.212:8080/wsrf/services/ManagementService [7]: http://141.142.251.212:8080/wsrf/services/NotificationConsumerFactoryService [8]: http://141.142.251.212:8080/wsrf/services/NotificationConsumerService [9]: http://141.142.251.212:8080/wsrf/services/NotificationTestService [10]: http://141.142.251.212:8080/wsrf/services/PersistenceTestSubscriptionManager [11]: http://141.142.251.212:8080/wsrf/services/SampleAuthzService [12]: http://141.142.251.212:8080/wsrf/services/SecureCounterService [13]: http://141.142.251.212:8080/wsrf/services/SecurityTestService [14]: http://141.142.251.212:8080/wsrf/services/ShutdownService [15]: http://141.142.251.212:8080/wsrf/services/SubscriptionManagerService [16]: http://141.142.251.212:8080/wsrf/services/TestAuthzService [17]: http://141.142.251.212:8080/wsrf/services/TestRPCService [18]: http://141.142.251.212:8080/wsrf/services/TestService [19]: http://141.142.251.212:8080/wsrf/services/TestServiceRequest [20]: http://141.142.251.212:8080/wsrf/services/TestServiceWrongWSDL [21]: http://141.142.251.212:8080/wsrf/services/Version [22]: http://141.142.251.212:8080/wsrf/services/WidgetNotificationService [23]: http://141.142.251.212:8080/wsrf/services/WidgetService [24]: http://141.142.251.212:8080/wsrf/services/gsi/AuthenticationService
Press Ctrl-C to abort the container.
- Obtain a user certificate and stop the container normally
- In the previous Command Prompt window, start the container again:
> echo %GLOBUS_LOCATION% > bin\globus-start-container -nosec Starting SOAP server at: http://141.142.251.212:8080/wsrf/services/ With the following services...
- Open another Command Prompt window and try to stop the container:
> cd c:\globus\ws-core-4.0.4 > set GLOBUS_LOCATION=%CD% > echo %GLOBUS_LOCATION% > bin\globus-stop-container Error: ; nested exception is: GSSException: Defective credential detected [Caused by: Proxy file (C:\DOCUME~1\TOMSCA~1\LOCALS~1\Temp\x509up_u_tom scavo) not found.]
- Press Ctrl-C to abort the container.
- Obtain a short-term X.509 end-entity credential from the GridShib CA
- In the first Command Prompt window, start the container as before.
- In the second Command Prompt window, try to stop the container again:
> bin\globus-stop-container Error: ; nested exception is: java.net.ConnectException: Connection refused: connect
- Finally, stop the container normally, authenticating at the message level using your GridShib CA-issued credential:
> bin\globus-stop-container -s http://localhost:8080/wsrf/services/ShutdownService -m msg
- In the previous Command Prompt window, start the container again:
- Start and stop a secure container
- In the first Command Prompt window, start the container:
> echo %GLOBUS_LOCATION% > bin\globus-start-container Starting SOAP server at: https://141.142.250.163:8443/wsrf/services/ With the following services...
- In the second Command Prompt window, stop the container:
> echo %GLOBUS_LOCATION% > bin\globus-stop-container
- In the first Command Prompt window, start the container:
- Request the
SecureCounterService
- In the first Command Prompt window, start the container:
> echo %GLOBUS_LOCATION% > bin\globus-start-container Starting SOAP server at: https://141.142.250.163:8443/wsrf/services/ With the following services...
- In the second Command Prompt window, request a service:
> echo %GLOBUS_LOCATION% > bin\counter-client -s https://localhost:8443/wsrf/services/SecureCounterService -m conv -z none Got notification with value: 3 Counter has value: 3 Got notification with value: 13
- Stop the container:
> %GLOBUS_LOCATION%\bin\globus-stop-container
- In the first Command Prompt window, start the container:
- Install GridShib for GT v0.6.0
- Download the GS4GT v0.6.0 source distribution (ZIP archive) from the GridShib web site. (A GZIP archive) is also available.)
- Double-click the ZIP archive and extract the source files into a folder of your choice (say, c:\gridshib).
- In the second Command Prompt window, type the following commands:
> cd c:\gridshib\gridshib-gt-0_6_0 > echo %GLOBUS_LOCATION% > ant deploy > ant deploy-echoservice
- Request the
ShibEchoService
- In the first Command Prompt window, start the container:
> echo %GLOBUS_LOCATION% > bin\globus-start-container Starting SOAP server at: https://141.142.250.163:8443/wsrf/services/ With the following services...
- In the second Command Prompt window, request a service:
> echo %GLOBUS_LOCATION% > %GLOBUS_LOCATION%\bin\shibecho -s https://localhost:8443/wsrf/services/ShibEchoService -z none
- Stop the container:
> %GLOBUS_LOCATION%\bin\globus-stop-container
- In the first Command Prompt window, start the container:
- TBA