Winsock And Discovery Is Netware Only; Uddi And Discovery; Cimom And Discovery; Slp - Novell OPEN ENTERPRISE SERVER 2 SP2 - PLANING AND IMPLEMENTATION GUIDE 11-10-2009 Implementation Manual

Starting with NetWare 5 and pure TCP/IP, the Service Location Protocol was adopted as the default,
though optional, discovery mechanism. SLP was chosen because it was the TCP/IP-based protocol
most like SAP in its automatic nature and dynamic refresh capabilities.
For more information, see

12.4.2 WinSock and Discovery Is NetWare only

There is no WinSock equivalent in the Linux environment. BSDSock provides for transport only,
not name resolution. Therefore, services that leveraged WinSock on NetWare use other service-
discovery mechanisms on OES 2.

12.4.3 UDDI and Discovery

UDDI is an open source, platform-independent registry that lets you provide a discovery service on
the World Wide Web to easily locate, integrate, and manage businesses and services.
For NetWare 6.5, Novell developed a directory-enabled UDDI server for use with the exteNd
J2EE Application Server. Starting with NetWare 6.5 SP3, the UDDI server component was
TM
removed from the list of products that could be installed.
The Novell UDDI server has been released as open source software and is available for download on
the Novell Forge Web site (http://forge.novell.com/modules/xfmod/project/
showfiles.php?group_id=1025).

12.4.4 CIMOM and Discovery

The current OpenWBEM implementation of the Common Information Model Object Manager
(CIMOM) lists SLP as an optional discovery provider. If SLP is to be used with CIMOM, it must be
in compliance with the SLP API specification (RFC 2614). The default discovery vehicle for
CIMOM is the statically configured URI. For more information, see the CIMOM specification at the
Desktop Management Task Force (DMTF) Web site

12.5 SLP

The OpenSLP services on OES 2 are compatible with NetWare SLP services.
This section discusses the following topics:
Section 12.5.1, "Why SLP Is Needed," on page 113
Section 12.5.2, "Comparing Novell SLP and OpenSLP," on page 114
Section 12.5.3, "Setting Up OpenSLP on OES 2 Networks," on page 115
Section 12.5.4, "Using Novell SLP on OES 2 Networks," on page 119

12.5.1 Why SLP Is Needed

NetWare: Although many other applications and server types rely on SLP for service discovery,
NetWare services are actually integrated with eDirectory, and if eDirectory is configured correctly,
the services work without SLP. However, SLP is automatically provided on NetWare for other
services that might be installed.
Section 12.5, "SLP," on page 113.
(http://www.dmtf.org).
TM
Network Services 113