120 likes | 273 Views
BAR: The Current Status. Charaka Palansuriya EPCC. Content. Active tasks: Updates to the BAR specification document, DJRA4.1 Updates BAR architecture WSDL and XML Schema definitions for BAR & NSAP Development of a basic prototype Further work. BAR specification document.
E N D
BAR: The Current Status Charaka Palansuriya EPCC
Content • Active tasks: • Updates to the BAR specification document, DJRA4.1 • Updates BAR architecture • WSDL and XML Schema definitions for BAR & NSAP • Development of a basic prototype • Further work EGEE-JRA4 BAR f2f -> 8 February 2005
BAR specification document • Updates to DJRA4.1: • BAR and NSAP interfaces in DJRA4.1 are updated • Added mandatory parameters (based on service classes) • Added units for parameter (not all are defined yet) • Updates are available as separate documents. • To be merged to DJRA4.1 and increase its version. EGEE-JRA4 BAR f2f -> 8 February 2005
BAR architecture • Current BAR architecture: • Requests are now based on Service Classes • E.g., Bulk Transfer (BT), Virtual Leased Line (VLL) EGEE-JRA4 BAR f2f -> 8 February 2005
BAR architecture • Operations in (conceptual) Port types: EGEE-JRA4 BAR f2f -> 8 February 2005
BAR architecture EGEE-JRA4 BAR f2f -> 8 February 2005
BAR architecture • An alternative architecture: • A separate web service for each Service Class EGEE-JRA4 BAR f2f -> 8 February 2005
BAR architecture • Should we choose this architecture ? • Pros: • Simpler interfaces and implementations • A server can just publish the web services corresponding to the Service Classes it can offer. • No changes required to NSAP • Cons: • How does a user know which component BAR web services (i.e., Service Classes) are offered by a server ? Use a registry ? • View of a single concrete BAR service is lost • Multiple web services to manage EGEE-JRA4 BAR f2f -> 8 February 2005
WSDLs and Schemas for BAR & NSAP • WSDL descriptions of BAR and NSAP web services are now available • Initial versions • Issues with generating the client stubs using the NSAP WSDL • W3C XML Schema is used to define XML elements inside SOAP body • i.e., we use document-centric (as opposed to RPC). • Note: MUST only use W3C XML schema to define types and WSDL for the web services we develop • This is to comply with WS-I Basic Profile 1.0 EGEE-JRA4 BAR f2f -> 8 February 2005
Prototype • Dummy Java prototypes for BAR and NSAP are available. • The dummy BAR service creates and sends a predefined response. • A Java client to drive the BAR service is also available. • Currently there is no communication between BAR and NSAP • Need to resolve issues with NSAP WSDL EGEE-JRA4 BAR f2f -> 8 February 2005
Software Development guide lines • A JRA4 developers guide is being produced • An important document for BAR and NSAP development • Summarises important items in the JRA1 developers guide • NOT a competing guide for JRA1’s version • Specifies the version of software/libraries be used • This should be same as the ones in JRA1 developers guide. If not, items should be highlighted and give reasons. EGEE-JRA4 BAR f2f -> 8 February 2005
Further work • Complete the basic prototype by end of February 05 • Detail design • Requirements traceability matrix • List numbered requirements and measurable tests for each of the requirement. • Test plan - Unit and System • Detailed description of deployment • Under various network configurations (scenarios) • Task breakdown and assignment • Build full prototype • Any thing else ? EGEE-JRA4 BAR f2f -> 8 February 2005