Difference between revisions of "Developing a Service"

From Gcube Wiki
Jump to: navigation, search
(Service files and rules)
(Integrating the Security)
Line 26: Line 26:
  
 
== Integrating the Security ==
 
== Integrating the Security ==
Obtain valid credentials
+
=== Obtain valid credentials ===
Identify your DL
+
=== Identify your DL ===
 +
* when the Security is enabled
 +
* when the Security is not enabled

Revision as of 12:53, 19 March 2007

How to develop a WSRF service that works in DILIGENT

Preliminary definitions

Service files and rules

A DILIGENT service is primarly a WSRF service runnable on Java WS Core v4.0.4, therefore it must follow the packaging rules to build a GT4 Deployable GAR file. In addition to such rules, others are required by the Collective Layer to correctly manage the services.

WSDD files

A service could be deployed in a secure or a non secure DL. In the latter case, the CL layer deploys the service without the security enabled on its operation. In order to do that, two Web Service Deployment Descriptor (WSDD) files must be provided, one that declares the Security Descriptor and another one without such a declaration. These two files must per placed in the root folder included in the GAR and must be named as follows:

  • deploy-server.wsdd (security enabled)
  • deploy-server.wsdd_NOSEC (security disabled)

For further details about how to declare the Security Descriptor in the WSDD file, see ...

Service Stubs

The service stub classes have to be placed in a separate JAR file, not included in the GAR file. This is because of the CL layer needs a full controll on the undeploy the stubs bu assuring that they are undeployed only if and when they are no longer used by other services.

Service profile

Putting all together: the service Archive on ETICS

Integrating DHN's Collective Layer components

DIS-HLSClient DIS-IP DILIGENTProvider NAL

Integrating the Security

Obtain valid credentials

Identify your DL

  • when the Security is enabled
  • when the Security is not enabled