Novell UDDI Services · Web services. UDDI Services leverages open standards such as HTTP, XML, and...

Novell

m

Manual 3/17/03103Novell Confidential front_services.fm last saved 4/7/03

w w w . n o v e l l . c o

UDDI Services

2 . 0

U
S E R G U I D E


Legal NoticesNovell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.

Copyright © 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

UDDI copyright © 2000 - 2002 by Accenture, Ariba, Inc., Commerce One, Inc. Fujitsu Limited, Hewlett-Packard Company, i2 Technologies, Inc., Intel Corporation, International Business Machines Corporation, Microsoft Corporation, Oracle Corporation, SAP AG, Sun Microsystems, Inc., and VeriSign, Inc. All Rights Reserved.

www.uddi.org

Novell, Inc.1800 South Novell PlaceProvo, UT 84606U.S.A.

www.novell.com

UDDI ServicesApril 4, 2003


Novell TrademarksNovell is a registered trademark of Novell, Inc. in the United States and other countries.eDirectory is a trademark of Novell, Inc.exteNd is a trademark of Novell, Inc.Nsure is a trademark of Novell, Inc.

Third-Party TrademarksAll third-party products are the property of their respective owners.

Novell Confidential front_services.fm last saved 4/7/03 Manual Version: 3/17/03103

4 UDDI Services

Manual 3/17/03103Novell Confidential uddi_servicesTOC.fm last saved 4/7/03

Contents

About This Guide 7

1 Understanding UDDI 9What is UDDI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9UDDI Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Business Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Business Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Binding Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10TModel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

UDDI Services for exteNd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Overview of UDDI Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Architecture of UDDI Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 Deploying UDDI Services 15

3 Configuring UDDI Services 17Setting the Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Dynamic Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Logging UDDI Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4 Accessing UDDI Services 19Accessing UDDI Services from Novell exteNd Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Publishing Business Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Publishing and Inquiring Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Accessing UDDI Services from Novell exteNd Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5 Managing Users and Credentials 25

6 Performance Tuning 27

7 Troubleshooting 29Handling Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Unsupported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

8 Upgrading to Novell Nsure UDDI 35Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Upgrading UDDI Services to Nsure UDDI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

A References 43

Contents 5

Novell Confidential uddi_servicesTOC.fm last saved 4/7/03 Manual Version: 3/17/03103

6 UDDI Services

Manual 3/17/03103Novell Confidential preface_services.fm last saved 4/7/03

About This Guide

This guide describes the basic concepts of Universal Description, Discovery and Integration (UDDI) and how to deploy and use Novell® UDDI Services on exteNdTM Application Server.

The audience for this document includes developers and administrators using Novell exteNd products.

This guide is divided into the following sections:

! Chapter 1, “Understanding UDDI,” on page 9

This section describes and explains the conceptual information for UDDI.

! Chapter 2, “Deploying UDDI Services,” on page 15

This section explains how to deploy UDDI Services.

! Chapter 3, “Configuring UDDI Services,” on page 17

This section explains how to configure UDDI Services.

! Chapter 4, “Accessing UDDI Services,” on page 19

This section explains how to access the UDDI Services.

! Chapter 5, “Managing Users and Credentials,” on page 25

This section explains how to manage users and credentials for UDDI Services.

! Chapter 6, “Performance Tuning,” on page 27

This section provides performance tuning tips.

! Chapter 7, “Troubleshooting,” on page 29

This section helps you troubleshoot UDDI Services.

! Chapter 8, “Upgrading to Novell Nsure UDDI,” on page 35

This section explains how to upgrade UDDI Services to Novell Nsure UDDI Server.

Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items within a cross-reference path.

A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.

User Comments

We want to hear your comments and suggestions about this guide. To contact us, send e-mail to [email protected].

About This Guide 7

Novell Confidential preface_services.fm last saved 4/7/03 Manual Version: 3/17/03103

8 UDDI Services

Manual (ENU) 3/17/03103Novell Confidential understanding_services.fm last saved 4/

1 Understanding UDDI

This section describes Universal Description, Discovery, and Integration (UDDI), its data structures, and UDDI Services for Novell® exteNdTM Application Server.

! “What is UDDI?” on page 9

! “UDDI Data Structures” on page 9

! “UDDI Services for exteNd” on page 11

What is UDDI?The UDDI specification provides a platform-independent way of describing services, discovering businesses, and integrating business services using the Internet. It provides a framework for describing businesses and the services offered by them by means of well-defined data structures.

UDDI can be viewed as a repository where you can publish information about your Web service and others can use it by searching for it. Therefore, the UDDI protocol is one of the major building blocks required for successful Web services. For more information about the UDDI project, see the UDDI consortium site (http://www.uddi.org).

Figure 1 UDDI Registry

UDDI provides an environment for describing and publishing Web services. Also, UDDI allows you to register in the UDDI business registry to publish business and services. These businesses and services can be discovered and integrated with other applications.

UDDI Data StructuresUDDI supports the following four core data structures:

! “Business Entity” on page 10

! “Business Service” on page 10

Service Broker

UDDI

Service Broker

UDDI

Service Broker

UDDI Invoke

Find Publish

Understanding UDDI 9

http://www.uddi.org

Novell Confidential understanding_services.fm last saved 4/ Manual Version: 3/17/03103

! “Binding Template” on page 10

! “TModel” on page 11

These data structures relate to each other as shown in the following figure:

Figure 2 UDDI Containment

Business EntityThe business entity is the topmost container in a UDDI data structure and represents a business organization providing Web services. Typically, business entities provide information that describes business organizations and the services they offer. The maximum number of business entities that can be published per user in the UDDI registry is 10.

Business ServiceA business service represents a collection of Web services offered by a business entity. This can be used to group services based on the type of Web services offered. Every business service is a child of a business entity. The maximum number of business services that can be published under a business entity is 100.

UDDI functions as a registry, similar to the Yellow Pages, where companies (Web service producers) register their services under different categories. Other companies (Web service consumers), browse the UDDI registry to locate the service and the company offering it and suitably invoke the service. The definitions inside UDDI are general enough to accommodate different kinds of services, such as:

! A faxing service

! A telephone service

! A commercial application that exposes its services using the SOAP protocol

Binding TemplateA binding template is used to bind Web services and applications by providing the necessary technical information about the Web services. A binding template represents a single Web service and provides an access point to that Web service. The maximum number of binding templates that can be published under a business service is 100.

10 UDDI Services

Manual 3/17/03103Novell Confidential understanding_services.fm last saved 4/

The access point includes routing information such as the URL, e-mail address, and telephone number to locate the service.

TModelA TModel provides technical information for a Web service. It contains the URL address of the Web service, metadata for the technical information, and a unique key for identification. They are used as:

! Identifiers for taxonomy-based classification schemes and identification systems

! Identifiers for technical specificationsNOTE: The technical information about a Web service is not stored in a UDDI registry. A TModel provides the URL address to locate the information.

The maximum number of TModels that can be published per user is 100.

UDDI Services for exteNdUDDI Services for exteNd is a UDDI v2 test registry that can be used for developing and testing Web services. UDDI Services leverages open standards such as HTTP, XML, and SOAP.

This is a light-weight edition of the Novell NsureTM UDDI Server and comes bundled with its own Light-weight Directory Access Protocol server (LDAP), also called the XLDAP server. Users can publish and inquire Web services through Novell exteNd Workbench or Novell exteNd Composer.

Developers can use UDDI Services for developing and testing their Web services before deploying them on Novell Nsure UDDI Server.

Everything you need to deploy UDDI Services is provided in the application server's UDDI subdirectory, along with install.html file available at NOVELL_EXTEND_APPSERVER_HOME/UDDI directory and the UDDI Services documentation available at the NOVELL_EXTEND_APPSERVER_HOME/UDDI/doc directory, where NOVELL_EXTEND_APPSERVER_HOME is the directory where the exteNd 5 Application Server is installed.

The UDDI subdirectory and its files are copied to your file system during the Novell exteNd Application Server install.

Overview of UDDI ServicesUDDI Services deployed as a J2EE* application runs within the Novell exteNd Application Server. Developers using Novell exteNd can write test web services applications (also called UDDI client applications) using Novell exteNd Workbench or Novell exteNd Composer and publish their identities into the UDDI registry using UDDI Services. These Web services can be accessed by querying and retrieving their identities from the UDDI registry using UDDI Services. Both publish and inquiry use the standard SOAP protocol over HTTP between the UDDI client applications and UDDI Services.



Figure 3 Overview of UDDI Services

Architecture of UDDI ServicesThe UDDI RPC Router (a Java Servlet) receives UDDI requests encapsulated in a SOAP message from Novell exteNd Composer or Workbench. The RPC Router validates UDDI requests and passes on valid UDDI messages to the UDDI Server. The invalid UDDI requests are discarded and the error is reported back to the requesting client using SOAP. The UDDI Server processes the UDDI request messages (publish/inquiry). The UDDI Server communicates with the XLDAP Server using LDAP (Light weight Directory Access Protocol) since the XLDAP Server is essentially an LDAP Server storing the UDDI objects as LDAP objects.

Novell exteNdApplication Server

UDDI Client Applications

Other Applications

Other Applications

UDDI Services

Novell exteNdWorkbench

UDDI Client Applications

Novell exteNdComposer

SO

AP o

ver H

TT

P

12 UDDI Services

Manual 3/17/03103Novell Confidential understanding_services.fm last saved 4/

Figure 4 Novell exteNd Application Server

When a request to publish business entities and business services is made, the UDDI server stores them as LDAP objects in the XLDAP repository using the XLDAP server. When a UDDI inquiry request needs to be processed, the requested UDDI objects are fetched from the XLDAP repository and passed back to the RPC router in the form of a SOAP response. This is again validated by the RPC router and returned to the calling application.

The UDDI objects are stored in the form of LDAP objects inside the XLDAP repository. These objects are accessed using the UDDI server using the XLDAP server and can be viewed as a UDDI repository.

When UDDI Services are deployed, the XLDAP server is started on a specified LDAP port number which it writes into the UDDI bootstrap file. This is picked by the UDDI server by means of the UDDI config module and used for making an LDAP connection with the XLDAP server.

The UDDI configuration information is stored in the UDDI bootstrap file and UDDI configuration files. The UDDI Config module reads the properties from the UDDI bootstrap file and the UDDI configuration files and passes the values of these properties to the UDDI Server. It is possible to alter the behavior of the UDDI server by appropriately modifying the UDDI configuration file, which is dynamically picked up by UDDI Config. This is known as dynamic reconfiguration.



14 UDDI Services

Manual (ENU) 3/17/03103Novell Confidential deploying_services.fm last saved 4/7/03

2 Deploying UDDI Services

For information regarding the deployment of UDDI Services on Novell® exteNdTM Workbench and Composer, see the install.html file located in the NOVELL_EXTEND_APPSERVER_HOME/UDDI directory.

Deploying UDDI Services 15

Novell Confidential deploying_services.fm last saved 4/7/03 Manual Version: 3/17/03103

16 UDDI Services

Manual (ENU) 3/17/03103Novell Confidential configuring_services.fm last saved 4/7/

3 Configuring UDDI Services

This section describes how to configure the parameters for UDDI Services on Novell® exteNdTM Application Server.

Setting the Configuration ParametersThe configuration information for UDDI Services are set in the following files:

! The bootstrap file located in the UDDIConfiguration/conf directory

! The uddi-file.conf file located in the UDDIConfiguration/conf directory

where UDDIConfiguration is the directory that you specify during deployment.

uddi.conf (Bootstrap File)

This file contains the following parameters:

! Hostname: Specifies the server name or the IP address of the LDAP server. This parameter cannot be edited. The default value is 127.0.0.1.

! Port: Specifies the port at which the XLDAP server is listening.

! BackendRepository: Specifies the repository where UDDI configuration is stored. By default, this is xldap.NOTE: For Novell NsureTM UDDI Server, the BackendRepository is edir, which means that the backend repository is Novell eDirectoryTM.

! ConfigRepository: Specifies the repository where UDDI configuration is stored. By default, this is file, which means that the UDDI configuration information is read from the uddi-file.conf file.

uddi-file.conf (UDDI Configuration file)

This file contains the following parameters that can be edited:

! uddiEnableLogging: Specifies whether logging is to be enabled. Values can be either True or False. The default value is True.

! uddiLogFileSize: Specifies the maximum size (in MB) of the log file. The valid range is 1 KB to 500 MB. The default value is 1 MB.

! uddiLogLevel: Specifies the level below which messages are not logged. The valid range is 0 to 7. The default level is 2. A higher number indicates that finer messages are logged.

! uddiReconfigInterval: Specifies the interval (in minutes) between two consecutive configuration reads. The valid range is 5 to 1440 minutes. The default is 5 minutes.

! uddiBaseContext: Specifies the LDAP container where the UDDI data objects are stored. By default, this is o=uddi.

Configuring UDDI Services 17

Novell Confidential configuring_services.fm last saved 4/7/ Manual Version: 3/17/03103

! uddiUserContext: Specifies the LDAP container where the UDDI user objects are stored. By default, this is o=users.

NOTE: The default values are used until explicitly overridden.

Dynamic ReconfigurationUDDI Services supports dynamic reconfiguration. Any configuration change in the server object at runtime is automatically detected and reflected in the UDDI server without the server being restarted. The frequency of such updates can be configured using the uddiReconfigInterval parameter in the uddi-file.conf file. The default value for dynamic reconfiguration is 5 minutes.

Logging UDDI EventsThe UDDI log file uddi-log-timestamp.log is created in the logs directory. This file contains the log information of the UDDI server, where timestamp is the time when the log file was generated.

Logging can be enabled by setting the value of the uddiEnableLogging parameter in the uddi-file.conf file to true. For more information, see uddiEnableLogging.

The log file is an XML file containing multiple log records in a sequence. Each log record contains:

! The date and time when the event was logged

! The sequence number

! The log level

! The log message

There are multiple log files available in the log directory with different timestamps. The server generates multiple log files, when the maximum log file size specified for the uddiLogFileSize parameter has been reached. To view the latest logging information, refer to the most recently created log file. Also, you can delete the older log files that you do not want to use.

Logger levels describe the level of importance and urgency of log messages that are permitted to be logged. When the logger is configured at a particular level, only messages of the same or higher priority are logged and other messages are discarded. The default logger level is 2. The following are the logger levels:

! Off (0): Enables you to turn logging off both at the system console and the log file.

! Severe (1): Enables only notification of critical system failures and messages that demand immediate attention.

! Warning (2): Enables to log messages of the Severe level and messages of exceptional conditions of lesser importance than Severe.

! Info (3): Enables to log routine messages of selected server operations that are used for collecting statistics.

IMPORTANT: Do not edit the uddi-log-timestamp.log.lck files that is created in the logs directory.

18 UDDI Services

Manual (ENU) 3/17/03103Novell Confidential accessing.fm last saved 4/7/03

4 Accessing UDDI Services

This section describes how to access UDDI Services for Novell® exteNdTM Workbench and Composer.

! “Accessing UDDI Services from Novell exteNd Workbench” on page 19

! “Accessing UDDI Services from Novell exteNd Composer” on page 22

Accessing UDDI Services from Novell exteNd WorkbenchIn order to use the UDDI Services from Novell exteNd Workbench, you should create a profile that points to the UDDI Services deployed on the Novell exteNd Application Server.

1 Start Workbench.

2 Select Edit > Profiles from the menu.

3 From the Profiles dialog, select the Registries tab.

4 Click New to create a new profile and enter the following values for each of the options:

Option Value

Profile name UDDI Services (or any name of your choice)

Accessing UDDI Services 19

Novell Confidential accessing.fm last saved 4/7/03 Manual Version: 3/17/03103

5 Click OK to create the new registry profile.

6 Click OK to close the registry profile dialog.

Using the newly created registry profile, you are now ready to test your Web service by publishing it against this internal UDDI test registry.

Publishing Business Entities1 Start Workbench.

2 Click the Publish organization to registry icon.

Registry type UDDI

Inquiry URL http://host:port/novelluddi/servlet/rpcrouter

where host is the hostname or IP address of the Novell exteNd 5 Application Server on which UDDI Services is deployed and port is its port number.

Publish URL http://host:port/novelluddi/servlet/rpcrouter


User name Credential None

If you want to publish a business entity later, provide a valid user name and credential. For more information, see Chapter 5, “Managing Users and Credentials,” on page 25.

Include in Registry Search Selected

Option Value

20 UDDI Services

Manual 3/17/03103Novell Confidential accessing.fm last saved 4/7/03

3 From the drop-down menu, select the registry profile you want to use.

4 Specify the name and description of the business entity you want to publish.



5 Click OK.

Publishing and Inquiring Web Services For more information about accessing UDDI registries for publishing and inquiring Web services, see the exteNd Workbench online help (Core help -> Tutorial -> lesson on Registries and WSDL for Web Services).NOTE: When you perform a publish or inquire operation for the first time, you would encounter the following message on the exteNd Application Server console. You can ignore this message.

WARNING: Value for EnforceSSLForPublish is not specified in the UDDI bootstrapfile (Please note that the parameters are case sensitive)

Accessing UDDI Services from Novell exteNd ComposerIn order to use the UDDI Services from Composer, you must create a new registry profile that points to the UDDI Service deployed on the Novell exteNd Application Server.

1 Start Composer.

2 Click Tools > Profiles to select the Registries tab.

3 Click New to create a new profile and enter the following values for each of the options:

Option Value

Profile name UDDI Services (or any name of your choice)

Registry type UDDI

Inquiry URL http://host:port/novelluddi/servlet/rpcrouter

where host is the hostname or IP address of the Novell exteNd 5 Application Server on which the UDDI Services is deployed and port is its port number.

22 UDDI Services

Manual 3/17/03103Novell Confidential accessing.fm last saved 4/7/03

4 Click OK to create the new registry profile.

5 Click OK to close the registry profile dialog.

For more information about accessing the UDDI registries for publishing and retrieving web services, refer to the Working with Registries section of the exteNd Composer online help.

Publish URL http://host:port/novelluddi/servlet/rpcrouter


User name Credential None

If you want to publish a business entity later, provide a valid user name and credential. For more information, refer Chapter 5, “Managing Users and Credentials,” on page 25.

Include in Registry Search Selected

Option Value



24 UDDI Services

Manual (ENU) 3/17/03103Novell Confidential managing_services.fm last saved 4/7/03

5 Managing Users and Credentials

Novell® UDDI Services 2.0 has 5 default user names and credentials. This release does not allow you to add more users to the UDDI registry. However, you can change the credential of the default users using any standard LDAP client.

The following user names and credentials are available:

These user names are stored in the XLDAP server within the container O=users.

In this release, only 5 users can publish business services concurrently into the UDDI registry. If you want to use UDDI Services within an enterprise with more number of users publishing and inquiring Web services concurrently, we suggest that you use Novell NsureTM UDDI Server.

User Name Credential (Case Sensitive)

uddiadmin uddiadminWarthog

uddiuser1 user1Warthog




Managing Users and Credentials 25

Novell Confidential managing_services.fm last saved 4/7/03 Manual Version: 3/17/03103

26 UDDI Services

Manual (ENU) 3/17/03103Novell Confidential performance_services.fm last saved 4/7/

6 Performance Tuning

This section describes the performance tuning tips for improved performance of Novell® UDDI Services.

The following parameters can be fine tuned for better memory utilization and performance:

To access these parameters:

1 In the Novell exteNdTM Application Server Management Console, click Advanced > Cache.

2 Select the Content Cache Enabled option and make the following changes:

Maximum size of the disk cache (in bytes)

Default value: 20,000,000

Change to: 209,715,200

Maximum size of any file that will be cached in the disk cache (in bytes)


Change to: 2,097,158 (no change, but you can try a higher value)

Maximum size of the in-memory cache (in bytes)


Change to: 33,554,432

Maximum size of any file that will be cached in the in-memory cache (in bytes)

Default value: 131,072

Change to: 10,485,760NOTE: The above numbers are used for the exteNdTM Application Server installed on Pentium* III 450 MHz with 512 MB RAM and a 20 GB hard disk. These parameters can change depending on your system configuration and the applications running.

Performance Tuning 27

Novell Confidential performance_services.fm last saved 4/7/ Manual Version: 3/17/03103

28 UDDI Services

Manual (ENU) 3/17/03103Novell Confidential troubleshooting_lite.fm last saved 4/7/03

7 Troubleshooting

This section explains the troubleshooting information and the unsupported features for Novell® UDDI Services.

! “Handling Errors” on page 29

! “Unsupported Features” on page 32

Handling Errors1. Deployment of UDDI Services on Novell® exteNdTM Application Server failed:

Solution 1: Verify that the exteNd Application Server is running. If not, start the exteNd Application Server.

Solution2: Verify the SilverCmd command line and ensure that you have provided all the required parameters as described in the install.html document.

Solution 3: If the exteNd Application Server is installed in restricted access mode, verify that you have used -U and -P switches in the SilverCmd command line and redeploy.

Solution 4: The values specified for the context parameters in the UDDI_Dep_Plan.xml deployment plan might be incorrect. Correct these values and redeploy.

2. UDDI Services are not initializing:

Description: After successfully deploying UDDI Services, the successful initialization message is not displayed on the browser. The Unable to start the UDDI Server message is displayed on the exteNd Application Server screen.

Solution 1: Check the UDDI Server status from a browser using the URL

http://hostname:port/novelluddi/servlet/rpcrouter

where hostname is the hostname or the IP address of the server running the exteNd Application Server and port is its port number.

Solution 2: Verify that the port number specified in the above URL is correct.

Solution 3: Verify that the hostname/IP address on which the exteNd Application Server is running is reachable from the client.

Solution 4: Ensure that the exteNd Application Server is running on the target server.

Solution 5: Check whether the XLDAP server has started successfully. The XLDAP server must be started for the UDDI Services to initialize.

To verify that the XLDAP server has started successfully, type the following URL from any browser window:

http://hostname:port/novelluddi/xldap/status

Troubleshooting 29

Novell Confidential troubleshooting_lite.fm last saved 4/7/03 Manual Version: 3/17/03103


If you encounter errors while starting the XLDAP server, see “Problem was encountered while starting the XLDAP server” on page 30, make the required corrections and check again whether the UDDI Server has initialized successfully.

3. Problem was encountered while starting the XLDAP server

UDDI Services will not initialize if problems are encountered while starting the XLDAP server. The XLDAP server status screen invoked from a browser window displays the problem that was encountered with one or more status messages. These messages are mostly self-explanatory and require one or more actions from you.

Solution 1: Invoke the XLDAP status screen using the URL: http://hostname:port/novelluddi/xldap/status and check the color of the star indicators. Red indicates that one or more errors have occurred while starting the XLDAP server and green indicates that the XLDAP server has started successfully.

Solution 2: Check the status messages and take required action.

Some of the commonly encountered status messages with actions required are:

! Not allowed to run on standard LDAP Ports — The user has specified a standard LDAP Port (389 or 636) in the deployment plan, which is not allowed. Edit the ldapport parameter in the UDDI_Dep_Plan.xml deployment plan and redeploy.

! Unable to read the property 'BackendRepository' — The uddi.conf file in the UDDI configuration directory does not contain the property BackendRepository. To correct this, open the uddi.conf file and edit the BackendRepository=xldap line and redeploy.

! LDAP Port address is already in use — You have probably specified a port which is being used by some other application on the server. Edit the ldapport parameter in the UDDI deployment plan and redeploy.

! Invalid LDAP Port specified — You have specified an alphanumeric value for the ldapport parameter in the UDDI deployment plan. Correct the problem by changing it to a numeric value and redeploy.

! File not found - TreeData.xld — The UDDI configuration directory does not contain the TreeData.xld file.

The XLDAP server uses this file. Copy this file from the exteNd Application Server distribution CD and redeploy.

Solution 3: Refresh the browser. It is possible that the xldap server has started successfully, but the browser is displaying a previous message from its cache.

4. The XLDAP server has started successfully, but is unable to initialize the UDDI Server:

Solution 1: Verify the exteNd Application Server Console. There could be one or more Severe/Warning messages.

Messages like SEVERE: Cannot Open XSD File uddi_v2.xsd (No such fileor directory) are displayed when the uddi_v2.xsd file is not present in the UDDI configuration directory. Copy this file from the exteNd Application Server distribution CD.

Solution 2: Check that the Port property has the correct value in the uddi.conf file located in the UDDI configuration directory. This should be the port on which the XLDAP server is listening. If not, specify the correct port number and restart the exteNd Application server.

30 UDDI Services

Manual 3/17/03103Novell Confidential troubleshooting_lite.fm last saved 4/7/03

Solution 3: Check if the property 'BackendRepository' has the value 'xldap' in the uddi.conf file present in the UDDI Configuration directory. If not, correct this value.

5. Unable to publish a business into Novell UDDI Server:

Description: Novell exteNd Workbench 4.1.1/Composer 4.1 allows you to create a business entity in the UDDI registry.

Solution 1: Ensure that you are using the correct version of Workbench/Composer. If you are using Composer 4.1, check that you have applied the UDDI v2 patch.

Solution 2: Ensure that the UDDI Services have initialized successfully.

Solution 3: Verify that the inquiry and publish URLs are specified correctly in the registry profile. To access Novell UDDI Server, both the inquiry and publish URLs should be:



It is possible that the exteNd Application Server is configured over SSL. In this case, the inquiry and publish URLs should be:

https://hostname:port/novelluddi/servlet/rpcrouter

Solution 4: Verify that the user name and credentials are specified correctly in the registry profile.

Solution 5: The Novell exteNd Application server might have been configured in restricted access mode. You cannot use Novell UDDI Services in this mode. Uncheck the Require user authentication option against the exteNd Application Server using the Application Server Management Console.

6. Unable to create more than 10 Business entities:

Description: UDDI Services on exteNd Application Server is a test registry and will not allow a user to create more than 10 business entities.

Solution 1: To create a new business entity, either delete or rename an existing business entity. This can be done using a third-party UDDI client such as JAXR Registry Browser.

7. Unable to browse the UDDI registry from Workbench/Composer:

Solution 1:Verify if you are using the correct version of Workbench/Composer. If you are using Composer 4.1, ensure that you have applied the UDDI v2 patch.

Solution 2: Ensure that the UDDI Services have initialized successfully.

Solution 3: Verify that the inquiry and publish URLs are specified correctly in the registry profile. For accessing the Novell UDDI Server, both inquiry and publish URLs should be:



Solution 4: Ensure that you have included the profile created to access UDDI Services in the registry search.

Solution 5: Use Advanced Search facility and make sure the following are done:

! You have selected Ignore Case

! You have not selected Exact Match

Troubleshooting 31


! You have selected the profile that accesses Novell UDDI Services

! You use Discover via Business Name only

Solution 6: It is possible that the exteNd Application server is configured in restricted access mode. You cannot use Novell UDDI Services in this mode. You must uncheck the Require user authentication option against the exteNd Application Server using Application Server Management Console.

Solution 7: Verify if you have provided the correct string pattern in the Starting with: option. If you are not sure what to provide here, we suggest you enter %, which retrieves all business names available in the UDDI registry.

8. The machine where the UDDI Services are deployed has high memory and CPU utilization. Thus, access to the UDDI registry is very slow:

Description: This might happen due to many reasons and is dependent on the number and type of applications deployed on the exteNd Application Server. Also, there is a possibility that a large number of Web services are published causing the UDDI Server to run out of memory. It is recommended that you upgrade to Novell Nsure UDDI Server if you want to publish a large number of Web services.

Solution 1: Delete some business entities or business services to create more space.

Solution 2: You can also recreate an empty UDDI repository without redeploying UDDI Services. To do so, stop the exteNd Application Server, copy the TreeData.xld file from the exteNd Application Server distribution CD to the UDDI configuration directory, and restart the application server. The UDDI Services now starts using the new TreeData.xld, which is currently empty. You can publish new Web services information into it.

9. UDDI Services has been upgraded to Novell Nsure UDDI. However, the XLDAP server status screen is still displayed on the browser:

Description: Upgrading to the Novell Nsure UDDI Server does not undeploy the XLDAP servlet on the exteNd Application Server. However, the XLDAP server is not started. This means that the XLDAP server is loaded in the memory, but it consumes negligible amount of memory and therefore not of much concern.

10. Inquiry and publishing takes a very long time to complete:

Description: When you try to create a business entity or business services, it takes a long time to complete this process. Similarly, the inquiry (searching) operation for business entities or business services takes a long time to complete.

Solution 1: In case of inquiry, provide the full business name instead of a partial match.

Solution 2: Many business entities and services might have been registered. You can try deleting some of them or replace the existing TreeData.xld file with an empty TreeData.xld file and store the services again.

Solution 3: Improve the server performance. For tips, see Chapter 6, “Performance Tuning,” on page 27.

Unsupported FeaturesThe following are the UDDI v2 features that are not currently supported:

! Service projections.

! Publisher assertions and related APIs.

32 UDDI Services

Manual 3/17/03103Novell Confidential troubleshooting_lite.fm last saved 4/7/03

! The caseSensitiveMatch qualifier is not supported.

! UDDI v1.0 requests are not accepted.

! Checked taxonomies for identifiers and categorizations are not supported.

! Discovery URLs are not generated for business entities published in the server.

Troubleshooting 33


34 UDDI Services

Manual (ENU) 3/17/03103Novell Confidential upgrading_services.fm last saved 4/7/03

8 Upgrading to Novell Nsure UDDI

The UDDI Services deployed against Novell® exteNdTM Application Server is not recommended for deployment in a production environment. The service is intended to target developers creating and experimenting with sample Web service applications using Novell exteNd. We recommend you to deploy Novell NsureTM UDDI Server in production environments. Novell Nsure UDDI Server uses eDirectory™ (a powerful and proven cross-platform directory service, refer Novell eDirectory (http://www.novell.com/products/edirectory)) as its Web services repository leveraging eDirectory replication, high availability, authentication and access control, centralized administration/management, scalability etc., that is required for use in production environments.

The UDDI Services running on Novell exteNd Application Server has all the capabilities of Novell Nsure UDDI Server. When you reconfigure it against eDirectory, it automatically gets upgraded to Novell Nsure UDDI Server.

! “Prerequisites” on page 35

! “Upgrading UDDI Services to Nsure UDDI Server” on page 35

Prerequisites! Novell eDirectoryTM 8.7 or higher

! Novell iManager 1.5.x

! Internet Explorer 5.5 Support Pack 2 or Netscape* Navigator 7.0 or higher

! Apache/Tomcat 4.0.x or higher

Upgrading UDDI Services to Nsure UDDI Server1 Install and configure eDirectory on the same box where UDDI Services and the exteNd

Application Server are deployed.

2 Run the Novell NsureTM UDDI Server installation wizard.

Refer the Installing Novell Nsure UDDI Server section of the Nsure UDDI administration guide to understand the prerequisites before running the installation wizard.

Accept the license agreement.

Upgrading to Novell Nsure UDDI 35

http://www.novell.com/products/edirectory

http://www.novell.com/products/edirectory

Novell Confidential upgrading_services.fm last saved 4/7/03 Manual Version: 3/17/03103

Click Next.

3 Ensure that UDDI Server and UDDI Admin/User Interface options are selected under Installable components.

Click Next.

For more information, refer to the Completing the Installation section of the Nsure UDDI administration guide.

36 UDDI Services

Manual 3/17/03103Novell Confidential upgrading_services.fm last saved 4/7/03

4 In the UDDI Server Option screen, uncheck Install UDDI Server.

Ensure that the Configure UDDI Server option is selected.

Click Next.

5 In the UDDI Management Folder screen, specify the directory where iManager is installed.

This is usually Tomcat_Home\Webapps, where Tomcat_Home is the directory that has Tomcat installed.

Click Next.



6 In the UDDI Server Input screen, specify the directory that contains the conf and logs sub-directories.

This is the UDDI Configuration directory.

Click Next.

7 Specify the port on which Novell exteNd Application Server is listening.

Click Next.

8 Specify the credentials of the eDirectory administrator or equivalent.

38 UDDI Services


These credentials are required for configuring the UDDI objects in the specified eDirectory container. Also, specify the LDAP port number on which eDirectory is listening.

Click Next.

9 Enter the UDDI configuration information and the administrator’s e-mail ID.

Click Next.

10 Review your inputs.



Click Next to start upgrading.

Upgradation in progress...

11 Ensure that the installation has completed successfully.

40 UDDI Services


12 Restart Novell exteNd Application Server for changes to take effect.NOTE: Upgrading UDDI Services to Nsure UDDI Server will not migrate the user credentials and UDDI data.



42 UDDI Services

Manual (99a) 3/17/03103Novell Confidential reference_service.fm last saved 4/7/03

A References

The following are the references for this guide:

! UDDI Version 2.0 API Specification: This specification discusses the programming interfaces exposed by UDDI.

For more information, see www.uddi.org (http://uddi.org/pubs/ProgrammersAPI-V2.04-Published-20020719.pdf) for a PDF version.

HTML version (http://uddi.org/pubs/ProgrammersAPI-V2.04-Published-20020719.htm)

! UDDI Version 2.0 Data Structure: This document discusses the details of each of the XML structures associated with the UDDI messages.

For more information, see www.uddi.org (http://uddi.org/pubs/DataStructure-V2.03-Published-20020719.pdf)

HTML version (http://uddi.org/pubs/DataStructure-V2.03-Published-20020719.htm)

References 43

http://uddi.org/pubs/ProgrammersAPI-V2.04-Published-20020719.pdf

http://uddi.org/pubs/ProgrammersAPI-V2.04-Published-20020719.htm

http://uddi.org/pubs/DataStructure-V2.03-Published-20020719.pdf

http://uddi.org/pubs/DataStructure-V2.03-Published-20020719.htm

Novell Confidential reference_service.fm last saved 4/7/03 Manual Version: 3/17/03103

44 UDDI Services

Date post:	01-Oct-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

Novell UDDI Services · Web services. UDDI Services leverages open standards such as HTTP, XML, and...

Documents