Manual of SLP Mesh Enhancement, Remote Discovery, Customization, and Global Attributes

Manual of SLP Mesh Enhancement, Remote Discovery, Customization, and Global Attributes

Release Version: 1.1.0 Date: 10/25/05

1. Introduction

This is a prototype implementation (using Java 1.4) for SLP mesh enhancement, remote discovery, customization, and global attributes. In the server side, da.java provides enhanced DA functions. In the client side, ua.java provides integrated UA/SA functions.

2. Roadmap for Source Files

Table 1. Shared Files
File Name	Functions
Const.java	Constant definitions
Util.java	Some useful utilities
slpMsgParser.java	SLPv2 message parser
slpMsgComposer.java	SLPv2 message composer
slpTcpHandler.java	TCP message handler
slpUdpHandler.java	UDP message handler

Table 2. Files for DA
File Name	Functions
da.java	Core DA code including GUI
Peer.java	Peer data structure in DA peer list
daAction.java	DA actions for different SLPv2 messages
daTcpServer.java	DA TCP server
daTcpHandler.java	DA TCP handler for each connection
daUdpServer.java	DA UDP server
bulkTrans.java	Bulk state transfer for anti-entropy
Database.java	DA database management
SelectSortExt.java	Information about Select/Sort extension
Entry.java	Entry data structure in database
SortEntry.java	Sort entries on an attribute list
Summary.java	Summary of states and DAAdvert information

Table 3. Files for UA/SA
File Name	Functions
ua.java	UA/SA implementation with GUI
uaAction.java	UA actions for different SLPv2 messages
uaFindDa.java	Thread to do DA discovery

3. Compile

cd src
make

Note: you need Java 1.4 or later version to compile the source code.

4. User Manual for DA

Start DA
java [-Dscope=da_scopes] [-Ddbase=dbase_file] [-Dsfile=summary_file] [-Dmcast=no] [-Dmesh=no] [-Dmode=complete] da
- If no -D option is specified, the DA uses default configuration
  - default service scope: Const.defaultScope
  - default database file: Const.defaultDbase
  - default summary file: Const.defaultSummary
  - default is ON for DAAdvert multicast
  - default is as a mesh-enhanced DA (DAAdvert has "mesh-enhanced" keyword)
  - default is to use selectvie anti-entropy
- Use -Dscope=da_scopes to specify the DA service scopes
  Scopes should be separated by comma, no space
- The DA's service scopes can not be changed after the DA has been started
- Use -Ddbase=dbase_file to specify the database file name
- Use -Dsfile=summary_file to specify the summary file name
- Use -Dmcast=no to turn off DAAdvert multicast
  Simulate the condition where multicast is NOT supported
- Use -Dmesh=no to turn off "mesh-enhanced" keyword in DAAdvert
  The DA works as a non-mesh-enhanced DA.
- Use -Dmode=complete to specify using complete anti-entropy
Configuration Information
Go to the menu "Setup" -> "My Configuration" to check the DA's configuration information:
- Domain name
- Port number
- Serving scopes
- Boot Timestamp
- Attribute
- Database File
- Summary File
- Multicast DAAdvert or not
- Mesh-enhanced or not
- Anti-entropy type: 1 for seletvie, 2 for complete
TCP/UDP Port
- A DA needs to bind to a predefined TCP/UDP port, so each machine can only host one DA.
- Port 427 is reserved by SLPv2. You need root privilege to use this port.
- For the testing purpose, we choose to use a port number higher than 1000.
DA Advertisement (DAAdvert)
- If multicast is ON, a DA periodically sends DAAdvert to SLP multicast address: 239.255.255.253.
- If multicast is OFF, A DA can unicast DAAdvert to any other DA:
  Give destination DA address in "To-URL"
  Then go to the menu "Setup" -> "Unicast DAAdver".
Peering State
- If a DA is configured as a "mesh-enhanced" DA, it automatically sets up peer relationships with the other DAs that share some scopes with it.
- To check peering state, go to the menu "Setup" -> "Peering State", which includes:
  - Peer URL
  - Serving Scopes
  - Enable Direct Forwarding
Registration Data
- To display the registration states, go to the menu "Operation" -> "Display Database".
- To display the registration states summary, go to the menu "Operation" -> "Display Summary".
- To display the DAAdvert information, go to the menu "Operation" -> "Display DAAdvert".
- To save the registration states to a file, go to the menu "Operation" -> "Save Data".
- To load the registration states from a file, go to the menu "Operation" -> "Load Data".
DA Status
The DA running status is displayed in the bottom window provided by a read-only Java TextArea.

5. User Manual for UA/SA

Start UA/SA
java ua
GUI Layout
- Menu Bar
- Message Composer Panel
- Extension Composer Panel
- Status Window
- Available DA List Panel
Normal Procedure
1. Use "Menu Bar" to set up configuration
2. Use "Available DA List Panel" to set up DA
3. Use "Message Composer Panel" to compose an SLP message
4. Use "Extension Composer Panel" to compose the extensions for current message
5. Send current message
6. "Status Window" displays information about the UA/SA running status.
Menu Bar
- File->Exit: exit this GUI
- Configuration
  - Transfer Mode: UDP or TCP (default is UDP)
  - SrvReg: Fresh or Incremental (default is Fresh)
Available DA List Panel
- The UA/SA uses one DA for its service registrations and queries.
- You can perform "Auto DA Discovery". All discovered DAs will be displayed in "Available DA List". The DA that was discovered first is chosen as the contacting DA for UA/SA automatically.
- You choose the contacting DA by clicking an entry in "Available DA List".
- You can also "Add New DA" or "Remove Selected DA" from "Available DA List". Remember to give both "New DA URL" and "New DA Scope" when you add a new DA.
- You can perform "Remote DA Discovery" to discover a remote DA at a given DNS domain via DNS SRV. Remember to specify a "Remote DNS Domain" before you perform "Remote DA Discovery".
Message Composer Panel
1. Choose "Message Type": SrvRqst, SrvTypeRqst, AttrRqst, SrvReg or SrvDeReg
2. Fill out the required fields for the chosen message type. Note that for AttrRqst, fill out "Service Type" field only if "URL" field is empty.
  - "Scope": service scope list, separated by comma
  - "Serive Type": can be a service type list separated by comma, or empty (for supporting global service attributes)
  - "Languange Tag"
  - "URL": service address
  - "Life Time": service lifetime
  - "Predicate": only two forms of predicates are supported, i.e., (a=1) or (&(a>1)(b<=5))
  - "Naming Authority": there two special values for naming authority: empty means IANA, -1 means all naming authorities.
  - "Tag List": tag list of attributes, separated by comma, e.g., a,b
  - "Attribute": service attributes, separated by comma, e.g., a=1,b=black
3. You can "Clear All Fields" or "Load Default Values"
4. When you have attached required extensions for current message, "Send Message".

Extension Composer Panel

You can "Append New Extension", "Remove Last Extension", or "Remove All Extensions" from current message.
At most ten extensions can be added to a message.
Currently three types of extensions are supported. Choose extension type from "Extension Name" field.
- Mesh-Forwarding Extension: it can only be attached to a SrvReg or SrvDeReg. Leave "Extension Content" empty.
- Select Extension: it can only be attached to a SrvRqst. Input an integer (<=65535) in "Extension Content".
- Sort Extension: it can only be attached to a SrvRqst. Input a sort-key-list string in "Extension Content". Note that the sort-key-list is separated by comma; and each key is in the form of "<key-name>:<type>:<order>[:<ref-val>]". The <type> is either "s" (for string) or "i" (for integer); the <order> is either "+" (for increasing order) or "-" (for decreasing order). An integer key may have an optional reference value (<ref-val>). For examples: "speed:i:-", "speed:i:+:12,load:i:+", "model:s:+".