HP-UX IP Address and Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3

Table 1-21 Message Types (continued)
UsageAbbreviationMessage Type
SAs and DAs send this message to UAs in
response to theirAttrRqst message. This
contains the list of attributes of a requested
service.
AttrRply
Attribute Reply
SAs send this message to register their services
with DAs.
SrvReg
Service Registration
SAs send this message to DAs if they no longer
want to make a service available, causing the
advertisement to be removed from the DA
immediately.
SrvDeReg
Service Deregistration
Assigning Scopes
A scope is a cluster of services that allows the services to be associated with a set of users
administratively. A scope indicates a particular location, administrative grouping, and proximity
in a network topology or any other category. SAs and DAs are always assigned a scope string.
The UA is normally assigned a scope string, through which it discovers that particular group of
services. This allows a network administrator to provide the desired service to users. If the UA
is configured with no scope, it discovers all available scopes and allows the client application to
issue requests for any service available on the network.
There are no hard and fast rules for the assignment of scopes. They may be assigned by
geographical location or by logical or administrative groupings. For example, you can assign the
administrative scope of “Marketing” to a scanner. It is also possible for the same scanner to be
advertised within the local scope “Engineers,” if all engineers must have access to the resource
as well.
Following is an example of how to configure scopes:.
# Scopes to use for this
agent net.slp.useScopes=corp,eng
You can use scopes for the physical location of services. You can also use a physical location
attribute within a particular service with scopes.
Following is an example of expanded scope associated with a service:
# Scopes to use for
this agent net.slp.useScopes=Building-5, Building-12
This configuration allows services to be advertised to users that are in the Building-5 scope, as
well as to users that are assigned to Building-12 scope. This is a logical configuration for physically
dependent services, such as scanners or printers.
SLP APIs
Table 1-22 describes the APIs that the SLP software contains.
Table 1-22 SLP APIs
UsageAPI
Registers a service URL and associated service attributes with SLP.
SLPReg()
Deregisters a registered service.
SLPDeReg()
Finds services based on service type or attributes.
SLPFindSrvs()
Obtains a list of attributes for services registered with SLP.
SLPFindAddrs()
Obtains a list of the types of services that are registered with SLP.
SLPFindSrvTypes()
58 Overview