Community client

The Community Client area is for setting creating a variety of Delegates for other components to call web service methods on a community server interface. These delegates are helper classes for other components to more easily communicate with the web service on the server, with stubbs already generated and setup. Look into the Resolver area for classes that need to deal with interaction with the Registry or using Community Acocunt identifiers to perform tasks with the delegates, this Resolver area is what will normally be used for obtaining delegates.

Obtaining Delegates

A component or client may instantiate a Soap type delegate manually if they know the url to the endpoint of a community service, but normally it is best to look at the Resolver area. The Resolver classes allows a client to get a delegate via the Registry by using a identifier for a community, or even a community identifier for an account or group.

Setting up a Client

In the Administratin manager you need to setup a Environment variable or JNDI property for "org.astrogrid.registry.query.endpoint" setting it to a known registry that will have communities (normally a full registry). Or you may place it in a file called astrogrid.properties on your classpath. Jars needed for community as a client:

  • astrogrid-community-client.jar
  • astrogrid-community-common.jar
  • astrogrid-community-resolver.jar
  • astrogrid-community-resolver.jar
  • astrogrid-common.jar
  • astrogrid-registry-cleint-lite.jar
  • astrogrid-registry-common.jar
  • astrogrid-registry-cleint-lite.jar
  • commons-logging.jar
  • log4j.jar
  • axis.jar (jars related for axis calls and client)

Types of Delegates/Interfaces

Here is a brief discussion of the main SOAP delegates on the client (normally for other testing and quicker setup Mock delegates are also supplied):

First a statement that normally delegates are interface classes and normally one SOAP type delegate is used for these interfaces.

policy.manager -- The most commonly used package

PolicyManagerSoapDelegate implements the PolicyManagerDelegate interface in the policy.manager package; hence all a component/user needs is the interface to the PolicyManagerDelegate to use the others such as Accounts, Groups, etc...

Interfaces:

  • PolicyManagerDelegate -- MAIN INTERFACE THAT CAN REACH ALL OTHER DELEGATES.
  • AccountManagerDelegate -- manages accounts
  • CommunityManagerDelegate -- not really in use anymore
  • GroupManagerDelegate -- manages groups
  • GroupMemberManagerDelegate -- manages members of groups.
  • ResourceManagerDelegate -- manages resources.
  • PermissionManagerDelegate -- manages permissions for groups/accounts for a resources

policy.service

PolicyServiceSoapDelegate implements the PolicyServiceDelegate.

Interfaces:

  • PolicyServiceDelegate -- checks Permissions are valid and Memberships to groups are valid.
security.manager

SecurityManagerSoapDelegate implements the SecurityManagerDelegate.

Interfaces:

  • SecurityManagerDelegate -- a seperate interface for setting passwords.

security.service

SecurityServiceSoapDelegate implements the SecurityServiceDelegate.

Interfaces:

  • SecurityServiceDelegate -- main security interface, checks tokens, splits tokens, and checks passwords.