Version 9.6 SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT
 —  Access via UDDI  —

Configuring the UDDI Environment

This section describes various configuration options for your UDDI environment.

Configuration Properties

In CentraSite the UDDI registry reflects its behavior in terms of JAXR objects stored in the CentraSite Registry/Repository. This representation can be used to parameterize the behavior.

The behavior of the UDDI processing in CentraSite can be configured using global and local properties.

UDDI in a Multi-CAST Environment

CentraSite supports a multi-CAST (CentraSite Application Server Tier) UDDI registry environment. In this environment, multiple CASTs are running against a single CentraSite Registry/Repository. Each CAST comes with its own UDDI Registry web application. In addition, several pure JAXR-based clients interact with the Registry/Repository.

In such an environment the Registry/Repository represents a single UDDI registry node, albeit multiple UDDI Registries are involved. Each UDDI Registry provides its own endpoints for the UDDI services. Due to the multi-CAST scenario, two different sets of properties are needed:

CAST Registration/Deregistration

You can register/deregister CASTs (and retrieve a list of CASTs) by executing the following commands in the command line interface CentraSiteCommand.cmd (Windows) or CentraSiteCommand.sh (UNIX) of Command Central. The tool is located in <CentraSiteInstallDir>/utilities.

If you start this command line tool with no parameters, you receive a help text summarizing the required input parameters.

The parameters of the command are case-sensitive, so for example the parameter "-url" must be specified as shown and not as "-URL".

Retrieving List of Available CASTs

To retrieve the list of available CASTs, use a command of the following form:

CentraSiteCommand list CAST [-url <CENTRASITE-URL>] -user <USER-ID> -password
<PASSWORD>

The following table describes the complete set of input parameters that you can use with the list CAST utility:

Parameter Description 
-url
 The fully qualified URL (http://localhost:53307/CentraSite/CentraSite) for the CentraSite registry/repository. 
-user
 The user ID of a user who has the "CentraSite Administrator" role. 
-password
 The password of the user identified by the parameter "-user".

For example:

CentraSiteCommand list CAST [-url "http://localhost:53307/CentraSite/CentraSite"] -user "Administrator" -password
"manage"

Registering a CAST

To register a CAST, use a command of the following form:

CentraSiteCommand add CAST [-url <CENTRASITE-URL>] -user <USER-ID> -password
<PASSWORD>

The following table describes the complete set of input parameters that you can use with the add CAST utility:

Parameter Description 
-url
 The fully qualified URL (http://localhost:53307/CentraSite/CentraSite) for the CentraSite registry/repository. 
-user
 The user ID of a user who has the "CentraSite Administrator" role. 
-password
 The password of the user identified by the parameter "-user".

For example:

CentraSiteCommand add CAST [-url "http://localhost:53307/CentraSite/CentraSite"] -user "Administrator" -password
"manage"

Deregistering a CAST

To deregister a CAST, use a command of the following form:

CentraSiteCommand remove CAST [-url <CENTRASITE-URL>] -user <USER-ID> -password
<PASSWORD>

The following table describes the complete set of input parameters that you can use with the remove CAST utility:

Parameter Description 
-url
 The fully qualified URL (http://localhost:53307/CentraSite/CentraSite) for the CentraSite registry/repository. 
-user
 The user ID of a user who has the "CentraSite Administrator" role. 
-password
 The password of the user identified by the parameter "-user".

For example:

CentraSiteCommand remove CAST [-url "http://localhost:53307/CentraSite/CentraSite"] -user "Administrator" -password
"manage"

Deployment Descriptors

In addition to the local and global properties that are stored in the registry, the web application needs a minimum of information to contact the CentraSite Registry/Repository. These parameters are:

The credentials are for the unauthenticated read access. Usually the guest account is used here.

If you wish to change the password of the guest account, or if you wish to use another user account instead of the guest account, proceed as follows:

Start of instruction setTo change the user ID/password of the web application login account

  1. In the file <CentraSiteInstallDir>\cast\cswebapps\UddiRegistry\WEB-INF\web.xml, specify the user ID and password in com.centrasite.uddi.store.dbUserId and com.centrasite.uddi.store.dbUserPasswordHandle.

    If your configuration includes more than one CAST, you must make this change on each CAST.

  2. Update the corresponding user ID/password information that is stored in the CentraSite Registry Repository. Do this by following the instructions given in the section Users, Groups, Roles and Permissions > Changing Passwords of Predefined Users and Login Users of the CentraSite documentation.

  3. Restart CentraSite.

Setting Global and Local UDDI Properties

You can set the global and local UDDI properties by executing the following command in the command line interface CentraSiteCommand.cmd (Windows) or CentraSiteCommand.sh (UNIX) of Command Central. The tool is located in <CentraSiteInstallDir>/utilities.

If you start this command line tool with no parameters, you receive a help text summarizing the required input parameters.

The parameters of the command are case-sensitive, so for example the parameter "-url" must be specified as shown and not as "-URL".

Start of instruction setTo set global properties

  1. Create an XML configuration file that contains the following predefined UDDI properties. This file should be in Java XML properties format. For example: 

    <?xml version="1.0" encoding="UTF-8" ?> 
  <!DOCTYPE properties (View Source for full doctype...)> 
- <properties version="1.0">
  <comment>Test UDDI Global Configuration XML</comment> 
  <entry key="com.centrasite.uddi.UDDIOperatorName">CentraSite</entry> 
  <entry key="com.centrasite.uddi.UDDIDefaultLanguage">en_US</entry> 
  <entry key="com.centrasite.uddi.UDDIValueValidation">false</entry> 
  <entry key="com.centrasite.uddi.UDDIKeyGeneratorChecks">true</entry> 
  <entry key="com.centrasite.uddi.UDDIDiscoveryURLGeneration">false</entry> 
  <entry key="com.centrasite.uddi.UDDIEncoding">utf-8</entry> 
  <entry key="com.centrasite.uddi.UDDISubscriptionDuration">P1M</entry>
  <entry key="com.centrasite.uddi.UDDIAuthTokenExpiration">P1D</entry> 
  <entry key="com.centrasite.uddi.UDDITransferTokenExpiration">P1D</entry> 
  <entry key="com.centrasite.uddi.UDDIV2Inquiry">true</entry> 
  <entry key="com.centrasite.uddi.UDDIV2Publish">true</entry> 
  <entry key="com.centrasite.uddi.UDDISendEmptyWebServiceNotifications">false</entry> 
  <entry key="com.centrasite.uddi.UDDISendEmptyEmailNotifications">true</entry> 
  <entry key="com.centrasite.uddi.UDDIMinimalNotificationInterval">P0Y0M0DT0H0M30S</entry> 
  <entry key="com.centrasite.uddi.UDDINumberOfRetries">3</entry> 
  <entry key="com.centrasite.uddi.UDDIMaxSubscriptionThreads">5</entry> 
  </properties>

    Descriptions of these properties are as follows:

    Global Property Description
    UDDIOperatorName

    Sets the operator attribute in UDDI V2 replies. The default value is "CentraSite".

    UDDIDefaultLanguage

    Sets the default language. All valid language identifiers are allowed. The default value is “en-US”.

    UDDIValueValidation

    Activates or deactivates internal value validation. Valid values: "true" or "false" (default). For more information, see Checked Value Set Validation.

    UDDIKeyGeneratorChecks

    Activates or deactivates the enforcement of keyGenerator tModels for publisher assigned keys. Valid values: "true" (default) or "false".

    UDDIDiscoveryURLGeneration

    Activates or deactivates the generation of discoveryURL. Valid values: "true" or "false" (default).

    UDDIEncoding

    Specifies the XML encoding of the UDDI responses. Valid values: "utf-8" (default) or "utf-16".

    UDDISubscriptionDuration

    The duration of a registry subscription. You can specify a default subscription expiration period for each UDDI web application separately.

    The subscription duration is specified via an xs:duration instance. It specifies a duration in terms of years, months, days, hours, minutes and seconds.

    The default value is 1 month (xs:duration(“P1M”)).

    How a string holding an xs:duration instance is generated is specified by the following section of the XML Schema (Part 2) specification.

    For example, to specify a duration of 1 year, 2 months, 3 days, 10 hours and 30 minutes, specify: P1Y2M3DT10H30M. You can also indicate a duration of minus 120 days as: -P120D. Reduced precision and truncated representations of this format are allowed provided they conform to the following: If the number of years, months, days, hours, minutes, or seconds in any expression equals zero, the number and its corresponding designator may be omitted. However, at least one number and its designator must be present. The seconds part may have a decimal fraction. The designator ‘T’ shall be absent if all of the time items are absent. The designator ‘P’ must always be present.

    For example, P1347Y, P1347M and P1Y2MT2H are all allowed; P0Y1347M and P0Y1347M0D are allowed. P-1347M is not allowed although –P1347M is allowed. P1Y2MT is not allowed.

    Note:
    A UDDI subscription survives an application server restart.

    UDDIAuthTokenExpiration

    The duration of an authorization token.

    This duration is specified via an xs:duration instance. It specifies a duration in terms of years (either 0 or 1), months, days, hours, minutes and seconds.

    The default value is 1 day (xs:duration(“P1D”)).
    UDDITransferTokenExpiration

    The duration of a transfer token.

    This duration is specified via an xs:duration instance. It specifies a duration in terms of years (either 0 or 1), months, days, hours, minutes and seconds.

    The default value is 1 day (xs:duration(“P1D”)).
    UDDIV2Inquiry

    Enables UDDI V2 Inquiry support. Valid values: "true" (default) or "false".

    UDDIV2Publish

    Enables UDDI V2 Publish support. Valid values: "true" (default) or "false".

    UDDISendEmptyWebServiceNotifications

    Specifies whether to allow Web service notifications to be sent even when no changes have occurred. Valid values: "true" (default) or "false".

    UDDISendEmptyEmailNotifications

    Specifies whether to allow email notifications to be sent even when no changes have occurred. Valid values: "true" or "false" (default).

    UDDIMinimalNotificationInterval

    The minimum time interval at which to send notifications to subscribers.

    This duration is specified via an xs:duration instance. It specifies a duration in terms of years (either 0 or 1), months, days, hours, minutes and seconds.

    The default value is 30 seconds (xs:duration(“P30S”)). The minimal resolution is 10 seconds (as well as the minimal possible value).

    UDDINumberOfRetries

    The maximum number of times to try to send Web service notifications to subscribers. Valid values: 0 through 10. Default: 3. The value 0 turns off this property (i.e., allows for unlimited retries).

    Note:
    This property applies only to Web service notifications, not to email notifications.

    UDDIMaxSubscriptionThreads

    The maximum number of threads for subscriptions. Default: 5.

  2. Execute the following command in this format:

    CentraSiteCommand set UDDI [-url <CENTRASITE-URL>] -user <USER-ID>
-password <PASSWORD> -file <CONFIG-FILE>

    The following table describes the complete set of input parameters that you can use with the set UDDI utility:

    Parameter Description 
    -url
    		 The fully qualified URL (http://localhost:53307/CentraSite/CentraSite) for the CentraSite registry/repository. 
    -user
    		 The user ID of a user who has the "CentraSite Administrator" role. 
    -password
    		 The password of the user identified by the parameter "-user". 
    -file
    		 The URI (file: or http:) of the configuration file.

    For example:

    CentraSiteCommand set UDDI [-url "http://localhost:53307/CentraSite/CentraSite"] -user "Administrator"
-password "manage" -file "config.xml"

Start of instruction setTo set local properties

  1. Create an XML configuration file that contains the following predefined UDDI properties. This file should be in Java XML properties format. For example: 

    <?xml version="1.0" encoding="UTF-8" ?> 
  <!DOCTYPE properties (View Source for full doctype...)> 
- <properties version="1.0">
  <comment>Test UDDI Local Configuration XML</comment> 
  <entry key="com.centrasite.uddi.UDDIMaxResultSize">*</entry> 
  <entry key="com.centrasite.uddi.UDDIMaxSearchKeys">*</entry> 
  <entry key="com.centrasite.uddi.UDDIMaxSearchNames">*</entry> 
  <entry key="com.centrasite.uddi.UDDIHTTPGetServicesUrl">http://localhost:53307/UddiRegistry</entry> 
  <entry key="com.centrasite.uddi.UDDIResponseValidation">false</entry> 
  <entry key="com.centrasite.uddi.UDDIRequestValidation">false</entry> 
  </properties>

    Descriptions of these properties are as follows:

    Local Property Description
    UDDIMaxResultSize

    Specifies the maximum inquiry result size. Default: An unlimited size (denoted by *).

    UDDIMaxSearchKeys

    Specifies the maximum number of search keys returned by an inquiry. Default: An unlimited number (denoted by *).

    UDDIMaxSearchNames

    Specifies the maximum number of search names returned by an inquiry. Default: An unlimited number (denoted by *).

    UDDIHTTPGetServicesUrl

    Holds the URI for the HTTP Get calls to retrieve UDDI objects from the registry. Default value: http://localhost:53307/UddiRegistry.

    UDDIResponseValidation

    Enables schema validation on UDDI V2 and V3 responses. Valid values: "true" or "false" (default).

    Note:
    The appropriate schema file should be stored in the CentraSite repository, in the /projects/uddi folder.

    UDDIRequestValidation

    Enables schema validation on incoming UDDI V2 and V3 requests. Valid values: "true" or "false" (default).

    Note:
    The appropriate schema file should be stored in the CentraSite repository, in the /projects/uddi folder.

  2. Execute the following command in this format:

    CentraSiteCommand set UDDI [-url <CENTRASITE-URL>] -user <USER-ID>
-password <PASSWORD> -file <CONFIG-FILE>

    The following table describes the complete set of input parameters that you can use with the set UDDI utility:

    Parameter Description 
    -url
    		 The fully qualified URL (http://localhost:53307/CentraSite/CentraSite) for the CentraSite registry/repository. 
    -user
    		 The user ID of a user who has the "CentraSite Administrator" role. 
    -password
    		 The password of the user identified by the parameter "-user". 
    -file
    		 The URI (file: or http:) of the configuration file.

    For example:

    CentraSiteCommand set UDDI [-url "http://localhost:53307/CentraSite/CentraSite"] -user "Administrator"
-password "manage" -file "config.xml"

Note:
The UDDI representation of local properties is based on the general approach of mapping jaxr:Slots to UDDI.

Getting Global and Local UDDI Properties

You can retrieve the global and local UDDI properties by executing the following command in the command line interface CentraSiteCommand.cmd (Windows) or CentraSiteCommand.sh (UNIX) of Command Central. The tool is located in <CentraSiteInstallDir>/utilities.

If you start this command line tool with no parameters, you receive a help text summarizing the required input parameters.

The parameters of the command are case-sensitive, so for example the parameter "-url" must be specified as shown and not as "-URL". 

CentraSiteCommand get UDDI [-url <CENTRASITE-URL>] -user <USER-ID>
-password <PASSWORD>

The following table describes the complete set of input parameters that you can use with the get UDDI utility:

Parameter Description 
-url
 The fully qualified URL (http://localhost:53307/CentraSite/CentraSite) for the CentraSite registry/repository. 
-user
 The user ID of a user who has the "CentraSite Administrator" role. 
-password
 The password of the user identified by the parameter "-user".

For example:

CentraSiteCommand get UDDI [-url "http://localhost:53307/CentraSite/CentraSite"] -user "Administrator"
-password "manage"

Executing the above CentraSite Command will print the UDDI global and local configurations accordingly.

Top of page

Schema Validation of UDDI Requests

All incoming UDDI V3 requests are validated against the XML schemas for UDDI requests, as defined in the OASIS UDDI specification. Invalid requests are rejected. The schema files are stored in the CentraSite repository in the folder /projects/uddi.

The validation can be activated or deactivated by the local configuration properties Request Validation and Response Validation (see Setting Global and Local Properties for details).

Top of page

Checked Value Set Validation

CentraSite offers the internal validation of checked value sets. If a keyedReference object is published that points to a checked value set, CentraSite checks if the keyValue belongs to the value set. UDDI 3.0.2 specifies checked value sets specified by value set taxonomies and value sets that have a validation algorithm. All value sets are represented in UDDI by a tModel. The validation of keyedReference objects can be switched off. For this purpose, the global configuration property Internal Value Set Validation can be used. To set this property, see Setting Global and Local Properties.

If the property is set to "false", no checking is performed but keyedReference objects pointing to an existing taxonomy are still mapped to a jaxr:internal classification. Invalid references are mapped to external classifications. This means that even a keyedReference object with an invalid value that points to a classificationScheme with a concept taxonomy is not rejected but mapped to an external classification. If the property is set to "yes", keyedReference objects pointing to checked value sets are checked. Invalid keyedReference objects are rejected with the error E_invalidValue.

Top of page

 www.softwareag.com  Copyright © 2005-2014 Software AG, Darmstadt, Germany.   SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT