IV23266: DOCUMENTS NOT BEING SYNCHRONISED INTO WSRR FROM UDDI DUE TO MULTIPLE OVERVIEWURL REFERENCES WITHIN A SINGLE TMODEL.

8.0.0.3-WS-WSRR-ZOS-IFIV65487_IV79085_IV87422_IV87429_IV89477
8.0.0.3-WS-WSRR-MultiOS-IFIV65487_IV79085_IV87422_IV87429_IV89477
WebSphere Service Registry and Repository V8.0 Fix Pack 2

APAR status

• Closed as program error.

Error description

• Documents not being synchronised into WSRR from a Centrasite
  UDDI due to multiple overviewDoc/overviewURL references within a
  single tModel.
  

Local fix

• Not applicable
  

Problem summary

• TN202 services in UDDI might not be pulled into WSRR correctly
  during the synchronization process. The logs indicate a problem
  during mapping and might also indicate that WSRR has attempted
  to load service definition documents from URLs pointing to HTML
  documents. When using a Centrasite UDDI, this is known to be a
  URL pointing to the public TN202 specification documentation.
  

Problem conclusion

• The UDDI synchronization code did not handle tModels in UDDI
  where the first overviewURL did not point to the WSDL document.
  In some UDDI registries, such as Centrasite, the first
  overviewURL has a 'text' useType and points to a human readable
  HTML document that WSRR would attempt and fail to load as a WSDL
  document.
  
  The UDDI synchronization code has now been modified to check for
  all available overviewURLs and ignore any where the useType is
  'text'.
  
  This fix 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 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