Advanced Topics

Interfacing the Information System

The gCore Framework has been designed to work independently from a IS specific Implementation. In order to let the gCF unbound from a IS, implementation both query & publishing interfaces have been designed. The gCF implements then a dynamic class loader that ( reading an implementation file that contains the mapping btw the IS interfaces and their implementations) can abstract over the IS technology.

ISQuery interface

The ISQuery interface designs the minimal query behavoiur accepted by the ISClient. The query contains the textual query expression and specify a time-to-live for their results (that can be exploited by future caching mechianism) The definition is parametric with respect the type of the exptected results. This is not required for the interface, though it may for its implementations; in addition , it allows full typing of the ISClient interface.

public interface ISQuery<RESULT> {
	   /**
	    * Returns the time-to-live of the results of the query.
	    * @return the time-to-live.
	    */
	   public long getTTL();

	   /**
	    * Sets the time-to-live of the results of the query.
	    * @param ttl the time-to-live.
	    */
	   public void setTTL(long ttl);

	   /**
	    * Returns the textual expression of the query.
	    * @return the expression.
	    */
	   public String getQueryExpression();

	   /**
	    * Sets the textual expression of the query.
	    * @param exp the expression.
	    */
	   public void setQueryExpression(String exp);
}

ISClient interface

The IS Client interface defines only two methods:

public <RESULT> List<RESULT> execute(ISQuery<RESULT> query, GCUBEScope scope,GCUBEContext ...context) throws 

ISMalformedQueryException,ISInvalidQueryException,ISException;	

The execute method takes as parameter:

• the ISQuery Object (with all parameters filled correctly otherwise the ISClient throws an ISMalformedQueryException);
• a GCUBEScope object that specifies the query scope;
• The GCUBEContext of the caller ( in case of a gCube Service the caller Context is the Service Context itself);

The return type is a List object specified as Type parameter in the related ISquery object.

In order to get the implementation of the ISClient Interface, the GHNContext exposes the static method getImplementation:

ISClient client =  GHNContext.getImplementation(ISClient.class);

The IS Client Interface predefines a list of abstract queries that model the queries used by the gCF.

In particular we have general queries over GCUBEResources:

• GCUBECollectionQuery
• GCUBECSInstanceQuery
• GCUBECSQuery
• GCUBEExternalRIQuery
• GCUBEGenericResourceQuery
• GCUBEGHNQuery
• GCUBEMCollectionQuery
• GCUBERIQuery
• GCUBEServiceQuery
• GCUBETPQuery
• GCUBEVREQuery

Queries over GCUBEWSResource:

• WSResourceQuery

Generic queries:

• GCUBEGenericQuery

In order to get the implementation specific ISQuery Object, IS Client exposes the method getQuery, that dynamically loads the ISQuery implementation of the given ISQuery interface:

public <RESULT, QUERY extends ISQuery<RESULT>> QUERY getQuery(Class<QUERY> clazz) throws ISUnsupportedQueryException;

i.e.

GCUBERIQuery queryRI = client.getQuery(GCUBERIQuery.class);

Sample usage

see [ExistClient]

ISPublisher interface

The ISPublisher interface defines methods to register/unregister/update these kind of objects on the IS:

• GCUBEResources
• GCUBEWSResources
• Topics

In particular GCUBEResources profiles are modeled as java classes inside the framework:

• GCUBEService
• GCUBERunningInstance
• GCUBEHostingNode
• GCUBECS
• GCUBECSInstance
• GCUBECollection
• GCUBEMCollection
• GCUBEVRE
• GCUBETransformationProgram
• GCUBEExternalRunningInstance
• GCUBEGenericRescource

gCUBE Client/Services can exploit the IS-Publisher to store/update/remove GCUBEResource profiles from/to the IS:

/**
 *  Register a GCUBEResource on the Information System
 *
 * @param resource The Gcube Resource to register
 * @param scope the Gcube scope to use
 * @return the Registered GCUBEResource profile
 * @throws ISPublisherException Exception
 */

public String  registerGCUBEResource(GCUBEResource resource,GCUBEScope scope, GCUBESecurityManager manager)throws 

GCUBEPublisherException;
	
/**
 * Remove a GCUBEResource from the Information System
 *
 * @param ID the ID related to the Gcube Resource to remove
 * @param the GCUBEResource type to remove
 * @param scope the registration scope
 * @param manager a GCUBESecurityManager
 * @throws ISPublisherException Exception
 */
public  void removeGCUBEResource(String ID,String type,GCUBEScope scope,GCUBESecurityManager manager) throws ISPublisherException;
	
/**
 * Update a GCUBEResource in the Information System

 * @param resource The new Gcube Resource to update 
 * @param manager a GCUBESecurityManager
 * @throws ISPublisherException Exception
 */
public void updateGCUBEResource(GCUBEResource resource,GCUBEScope scope,GCUBESecurityManager manager) throws ISPublisherException;

GCUBEWSResource class then, defines WS-Resource-Properties to publish to the IS (the publication mechanism is completely hidden by the gCF). The gCF exploits these mothods to implement the WS-Resource-Properties registration/unregistation from/to IS:

/**
 * Enables WS-resource registration on a Information System
 * 
 * @param resource The Gcube WSResouce to register
 * @param scope optional scope (overrides the scope specified by the GCUBEWSResource) 
 * @throws ISPublisherException Exception
 */
public void registerWSResource(GCUBEWSResource resource,GCUBEScope ...scope) throws ISPublisherException;
	
/**
 *  Enables WS-resource registration on a Information System( named Registration)
 * 
 * @param resource The Gcube WSResouce to register
 * @param name the name associated to the registration
 * @param scope optional scope (overrides the scope specified by the GCUBEWSResource) 
 * @throws ISPublisherException Exception
 */
public void registerWSResource(GCUBEWSResource resource, String name,GCUBEScope ...scope) throws ISPublisherException;
	
/**
 *  Removes the registration of a GCube WS-Resource from the InformationSystem
 *
 * @param resource  The Gcube WSResouce to unregister
 * @param scope optional scope (overrides the scope specified by the GCUBEWSResource) 
 * @throws ISPublisherException Exception
*/
public void removeWSResource(GCUBEWSResource resource,GCUBEScope ...scope) throws ISPublisherException;

/**
 *  Removes he registration of a GCube WS-Resource from the InformationSystem( named registration)
 *
 * @param resource The Gcube WSResouce to unregister
 * @param name the name associated to the registration
 * @param scope optional scope (overrides the scope specified by the GCUBEWSResource) 
 * @throws ISPublisherException Exception
 */
public void removeWSResource(GCUBEWSResource resource, String name,GCUBEScope ...scope) throws ISPublisherException;

As noticed, the ISPublisher methods take as parameters the GCUBEScope and the GCUBESecurityManager of the caller in order to prepare the IS Services stubs with the correct Scope and security Settings.

Sample usage

In Order to get the ISPublisher implementation object from its itnerface ( as for the ISClient), the GHNContext offers the getImplementation method:

ISPublisher publisher  =GHNContext.getImplementation(ISPublisher.class);

In order to register a GCUBEResource profile ( i.e. a GCUBEService) on the IS, this is the sample code:

FileReader fis = new FileReader (args[0]);
GCUBEService resource =GHNContext.getImplementation(GCUBEService.class);
resource.load(fis);
GCUBESecurityManagerImpl managerSec = new GCUBESecurityManagerImpl() {  public boolean isSecurityEnabled() {return true;}};
GSSCredential cred =org.diligentproject.dvos.authentication.util.ProxyUtil.loadProxyCredentials(args[1]);
managerSec.useCredentials(cred);
ISPublisher publisher  =GHNContext.getImplementation(ISPublisher.class);
publisher.registerGCUBEResource(resource, GCUBEScope.getScope("/gcube/devsec"), managerSec);

ISNotifier interface

Topics publishers can use the ISNotifier interface, to let their topics being published on the IS and subscribed for notification to.

Resource Properties as Topics

In order to publish one or more Resource Properties as Topics in the IS, one needs to override in the ws-resoure class the getTopics() method in order to provide the names of the RP that he/she wants to publish as Topics

Example:

public class DeployerResource extends GCUBEWSResource {
 
 @Override
 protected String[] getTopicNames(){
	return new String[] {"DeployedPackages"};
 }

And, that's all. GCF automatically publishes on behalf of the resource the Topics, as it does with the RP

Generic Topics

In order to publish a Topic not directly bound to a RP, the following steps must be followed: 1) Define your own Topic in your WSResource Example:

public static final String NS = "http://gcube-system.org/namespaces/vremanagement/deployer";

private SimpleTopic deployedPackagesT = new SimpleTopic(new QName(NS, “TopicName"));

… and the Topic notification message in the WSDL

<xsd:element name=" DeployedPackagesNotificationMessage" type="tns:DeployedPackagesNotificationMessageType"/>

2) Retrieve the ISNotifier implementation Example:

ISNotifier notifier = GHNContext.getImplementation(ISNotifier.class);

3) Register the Topic Example:

List <SimpleTopic> list = new ArrayList< SimpleTopic >();
list.add(deployedPackagesT );
notifier.registerISNotification(this.getEPR(), list, this.getServiceContext());

4) Send the notification whenever it is needed, according to the notification message defined in the WSDL Example:

DeployedPackagesNotificationMessageType message = new DeployedPackagesNotificationMessage ();
message.setX(…);
message.setY(…)

deployedPackagesT.notify(message);