Direct links to fixes
APAR status
Closed as program error.
Error description
UDDI API WSDL and XSD documents being synchronised multiple times resulting in duplicate documents within WSRR.
Local fix
Not applicable
Problem summary
When running the scheduled UDDI synchronization process, some WSDL and XSD documents might be loaded into WSRR more than once. This is known to occur for the UDDI API WSDL and XSD documents included in a Centrasite UDDI registry.
Problem conclusion
If the names of the entities derived from the documents loaded into WSRR do not match what is expected according to the specifications supported by the mapping process then the UDDI references will not be set correctly on those entities. As a result, when another entity is encountered in UDDI that references the same service definition documents, they will be loaded into WSRR again. We cannot support synchronization of services that do not entirely conform with the support mapping specifications so a mechanism has been implemented to allow certain document references to be blocked or ignored during the UDDI synchronization processing. You can prevent a particular document from being loaded by specifying all or part of the (overview)URL within a user configuration item called 'UDDIFilterConfiguration'. The format of the content of this configuration item is: <UDDI_CONTENT_FILTERING> <IGNORE_URL>http://sample.url/sample.wsdl</IGNORE_URL> <IGNORE_URL>http://sample2.url/sample2.wsdl</IGNORE_URL> ... </UDDI_CONTENT_FILTERING> You can use a * character as a wild card at the beginning or end of a URL string. If you specify only a * character then all URLs will be ignored. For example: <IGNORE_URL>*uddi.org*</IGNORE_URL> <IGNORE_URL>*my.url/doc.wsdl</IGNORE_URL> <IGNORE_URL>http://my.uddi.server/uddi.org*</IGNORE_URL> <IGNORE_URL>*</IGNORE_URL> The process for applying this configuration to WSRR is as follows: 1) You must first create a text file containg a list of URLs or fragments of URLs that you do not want to be loaded during UDDI synchronisation. This list must conform to the example format given previously. 2) Login to the web UI and switch to the 'Configuration' perspective before navigating to: Active Profile -> User Configurations -> Load User Configuration 3) Specify the path to the text file and enter a configuration item name of: UDDIFilterConfiguration 4) Once the configuration item has been loaded successfully it will take effect immediately. This facility is targeted for inclusion in fix pack 5 for WSRR v6.3, fix pack 6 for WSRR v7.0, fix pack 3 for WSRR v7.5 and fix pack 2 for WSRR v8.0.
Temporary fix
Comments
APAR Information
APAR number
IV23308
Reported component name
SERVICE REGISTR
Reported component ID
5724N7200
Reported release
630
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-06-20
Closed date
2012-07-20
Last modified date
2012-10-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SERVICE REGISTR
Fixed component ID
5724N7200
Applicable component levels
R630 PSY
UP
R700 PSY
UP
R750 PSY
UP
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 October 2012