Chapter 6: Deploying The Globus Toolkit 4.0.x
Starting the Container
With the container certificate and key available and with RFT configured, we are now ready to start the Globus container and the grid services that will run in it. As user globus make sure that your environment is set up as usual. Also make sure that the java tools are in your PATH:
[globus@nodeB ~]$ export JAVA_HOME=/opt/jdk1.5.0_06
[globus@nodeB ~]$ export PATH=$JAVA_HOME/bin:$PATH
[globus@nodeB ~]$ which java
/opt/jdk1.5.0_06/bin/java
It is best to run the container with more then the default memory used by the java virtual machine. This is accomplished by setting an environment variable:
[globus@nodeB ~]$ export GLOBUS_OPTIONS=-Xmx512M
Now use 'globus-start-container' to start the container and the default grid services:
[globus@nodeB ~]$ $GLOBUS_LOCATION/bin/globus-start-container
If everything is properly configured you should see after a few seconds the following output:
Starting SOAP server at: https://192.168.31.40:8443/wsrf/services/
With the following services:
[1]: https://192.168.31.40:8443/wsrf/services/TriggerFactoryService
[2]: https://192.168.31.40:8443/wsrf/services/DelegationTestService
[3]: https://192.168.31.40:8443/wsrf/services/SecureCounterService
[4]: https://192.168.31.40:8443/wsrf/services/IndexServiceEntry
[5]: https://192.168.31.40:8443/wsrf/services/DelegationService
[6]: https://192.168.31.40:8443/wsrf/services/InMemoryServiceGroupFactory
[7]: https://192.168.31.40:8443/wsrf/services/mds/test/execsource/IndexService
[8]: https://192.168.31.40:8443/wsrf/services/mds/test/subsource/IndexService
[9]: https://192.168.31.40:8443/wsrf/services/SubscriptionManagerService
[10]: https://192.168.31.40:8443/wsrf/services/TestServiceWrongWSDL
[11]: https://192.168.31.40:8443/wsrf/services/SampleAuthzService
[12]: https://192.168.31.40:8443/wsrf/services/WidgetNotificationService
[13]: https://192.168.31.40:8443/wsrf/services/AdminService
[14]: https://192.168.31.40:8443/wsrf/services/DefaultIndexServiceEntry
[15]: https://192.168.31.40:8443/wsrf/services/CounterService
[16]: https://192.168.31.40:8443/wsrf/services/TestService
[17]: https://192.168.31.40:8443/wsrf/services/InMemoryServiceGroup
[18]: https://192.168.31.40:8443/wsrf/services/SecurityTestService
[19]: https://192.168.31.40:8443/wsrf/services/ContainerRegistryEntryService
[20]: https://192.168.31.40:8443/wsrf/services/NotificationConsumerFactoryService
[21]: https://192.168.31.40:8443/wsrf/services/TestServiceRequest
[22]: https://192.168.31.40:8443/wsrf/services/IndexFactoryService
[23]: https://192.168.31.40:8443/wsrf/services/ReliableFileTransferService
[24]: https://192.168.31.40:8443/wsrf/services/mds/test/subsource/IndexServiceEntry
[25]: https://192.168.31.40:8443/wsrf/services/Version
[26]: https://192.168.31.40:8443/wsrf/services/NotificationConsumerService
[27]: https://192.168.31.40:8443/wsrf/services/IndexService
[28]: https://192.168.31.40:8443/wsrf/services/NotificationTestService
[29]: https://192.168.31.40:8443/wsrf/services/ReliableFileTransferFactoryService
[30]: https://192.168.31.40:8443/wsrf/services/DefaultTriggerServiceEntry
[31]: https://192.168.31.40:8443/wsrf/services/TriggerServiceEntry
[32]: https://192.168.31.40:8443/wsrf/services/PersistenceTestSubscriptionManager
[33]: https://192.168.31.40:8443/wsrf/services/mds/test/execsource/IndexServiceEntry
[34]: https://192.168.31.40:8443/wsrf/services/DefaultTriggerService
[35]: https://192.168.31.40:8443/wsrf/services/TriggerService
[36]: https://192.168.31.40:8443/wsrf/services/gsi/AuthenticationService
[37]: https://192.168.31.40:8443/wsrf/services/TestRPCService
[38]: https://192.168.31.40:8443/wsrf/services/ManagedMultiJobService
[39]: https://192.168.31.40:8443/wsrf/services/RendezvousFactoryService
[40]: https://192.168.31.40:8443/wsrf/services/WidgetService
[41]: https://192.168.31.40:8443/wsrf/services/ManagementService
[42]: https://192.168.31.40:8443/wsrf/services/ManagedExecutableJobService
[43]: https://192.168.31.40:8443/wsrf/services/InMemoryServiceGroupEntry
[44]: https://192.168.31.40:8443/wsrf/services/AuthzCalloutTestService
[45]: https://192.168.31.40:8443/wsrf/services/DelegationFactoryService
[46]: https://192.168.31.40:8443/wsrf/services/DefaultIndexService
[47]: https://192.168.31.40:8443/wsrf/services/ShutdownService
[48]: https://192.168.31.40:8443/wsrf/services/ContainerRegistryService
[49]: https://192.168.31.40:8443/wsrf/services/TestAuthzService
[50]: https://192.168.31.40:8443/wsrf/services/CASService
[51]: https://192.168.31.40:8443/wsrf/services/ManagedJobFactoryService
Not all those services will be exercised in this tutorial, but they are deployed by default and there is no harm in letting them all run.
Now that we are sure the container is running correctly, use Ctrl+c to stop it. After a few seconds the container will stop:
Stopped SOAP Axis server at: https://192.168.31.40:8443/wsrf/services/
Start the container again but this time run it in the background and send the output and error to a file for logging:
[globus@nodeB ~]$ /opt/globus-4.0.1/bin/globus-start-container > $HOME/container.out 2>&1 &
|
