Difference between revisions of "GCore Based Information System Installation"
From Gcube Wiki
Manuele.simi (Talk | contribs) (New page: === IS-InformationCollector === === IS-Registry === === IS-Notifier === === IS-gLiteBridge ===) |
Manuele.simi (Talk | contribs) (→IS-Registry) |
||
| Line 3: | Line 3: | ||
=== IS-Registry === | === IS-Registry === | ||
| + | ==== Configuration ==== | ||
| + | |||
| + | The configuration of an IS-Registry instance is a two-step process: | ||
| + | |||
| + | * since a IS-Registry can act in one and only one scope, its JNDI file (<em>$GLOBUS_LOCATION/etc/org.gcube.informationsystem.registry/jndi-config.xml</em>) must be configure to join only one scope. In the following example, the instance is configure to join the scope named <em>/testing/vo1</em>: | ||
| + | <pre lang="xml"> | ||
| + | <?xml version="1.0" encoding="UTF-8"?> | ||
| + | <jndiConfig xmlns="http://wsrf.globus.org/jndi/config"> | ||
| + | |||
| + | <service name="gcube/informationsystem/registry"> | ||
| + | |||
| + | <environment | ||
| + | name="configDir" | ||
| + | value="etc/org.gcube.informationsystem.registry" | ||
| + | type="java.lang.String" | ||
| + | override="false" /> | ||
| + | |||
| + | <environment | ||
| + | name="securityManagerClass" | ||
| + | value="org.gcube.common.core.security.GCUBESimpleServiceSecurityManager" | ||
| + | type="java.lang.String" | ||
| + | override="false" /> | ||
| + | |||
| + | <!-- Lifetime for temporary resources, after this period temporary resources are destroyed--> | ||
| + | <environment | ||
| + | name="temporaryResourceLifetimeInMs" | ||
| + | value="480000" | ||
| + | type="java.lang.Long" | ||
| + | override="false" /> | ||
| + | |||
| + | |||
| + | |||
| + | <environment | ||
| + | name="startScopes" | ||
| + | value=" /testing/vo1" | ||
| + | type="java.lang.String" | ||
| + | override="false" /> | ||
| + | |||
| + | </service> | ||
| + | .... | ||
| + | </pre> | ||
| + | |||
| + | * due to its role, the IS-Registry requires a special Service Map for its scope. In that map, the EPR of the RegistryFactory of itself must be reported. Let's suppose that an instance running on a node named grid5.4dsoft.hu joins the <em>/testing/vo1 scope</em>, the <em>$GLOBUS_LOCATION/config/ServiceMap_vo1.xml</em> file must be filled as follows (the EPRs are here just for the sample purposes): | ||
| + | |||
| + | <pre lang="xml"> | ||
| + | <ServiceMap> | ||
| + | <Service name ="ISICAllQueryPT" endpoint ="http://grid1.4dsoft.hu:8080/wsrf/services/diligentproject/informationservice/disic/DISICService"/> | ||
| + | <Service name ="ISICAllRegistrationPT" endpoint ="http://grid1.4dsoft.hu:8080/wsrf/services/diligentproject/informationservice/disic/DISICRegistrationService"/> | ||
| + | <Service name ="ISRegistry" endpoint="http://grid5.4dsoft.hu:8080/wsrf/services/gcube/informationsystem/registry/RegistryFactory" /> | ||
| + | </ServiceMap> | ||
| + | |||
| + | </pre> | ||
=== IS-Notifier === | === IS-Notifier === | ||
Revision as of 15:03, 16 June 2009
IS-InformationCollector
IS-Registry
Configuration
The configuration of an IS-Registry instance is a two-step process:
- since a IS-Registry can act in one and only one scope, its JNDI file ($GLOBUS_LOCATION/etc/org.gcube.informationsystem.registry/jndi-config.xml) must be configure to join only one scope. In the following example, the instance is configure to join the scope named /testing/vo1:
<?xml version="1.0" encoding="UTF-8"?>
<jndiConfig xmlns="http://wsrf.globus.org/jndi/config">
<service name="gcube/informationsystem/registry">
<environment
name="configDir"
value="etc/org.gcube.informationsystem.registry"
type="java.lang.String"
override="false" />
<environment
name="securityManagerClass"
value="org.gcube.common.core.security.GCUBESimpleServiceSecurityManager"
type="java.lang.String"
override="false" />
<!-- Lifetime for temporary resources, after this period temporary resources are destroyed-->
<environment
name="temporaryResourceLifetimeInMs"
value="480000"
type="java.lang.Long"
override="false" />
<environment
name="startScopes"
value=" /testing/vo1"
type="java.lang.String"
override="false" />
</service>
....
- due to its role, the IS-Registry requires a special Service Map for its scope. In that map, the EPR of the RegistryFactory of itself must be reported. Let's suppose that an instance running on a node named grid5.4dsoft.hu joins the /testing/vo1 scope, the $GLOBUS_LOCATION/config/ServiceMap_vo1.xml file must be filled as follows (the EPRs are here just for the sample purposes):
<ServiceMap>
<Service name ="ISICAllQueryPT" endpoint ="http://grid1.4dsoft.hu:8080/wsrf/services/diligentproject/informationservice/disic/DISICService"/>
<Service name ="ISICAllRegistrationPT" endpoint ="http://grid1.4dsoft.hu:8080/wsrf/services/diligentproject/informationservice/disic/DISICRegistrationService"/>
<Service name ="ISRegistry" endpoint="http://grid5.4dsoft.hu:8080/wsrf/services/gcube/informationsystem/registry/RegistryFactory" />
</ServiceMap>
