Direct links to fixes
APAR status
Closed as program error.
Error description
In the case of WSDLs using SOAP1.2 binding, When the WSDL related toeach environment, for ex: ( DEV, TEST, INT, PROD), are published in theGOV WSRR, unlike the SOAP Endpoints, the Extension SOAP Endpoints areoverwritten. There is only one Extension SOAP Endpoint object is shownin the WSRR, which represents the latest published WSDL. This causes problems while promoting the endpoint to different environments.
Local fix
N/A
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere Service Registry and Repository V8.0 who are loading WSDL documents containing SOAP 1.2 elements. **************************************************************** PROBLEM SUMMARY: When loading WSDL documents, SOAP 1.1 and 1.2 elements are parsed differently and generate different logical and correlated objects in WSRR. In particular, SOAP address locations translate to SOAPServiceEndpoint objects for SOAP 1.1 elements and ExtensionServiceEndpoint objects for SOAP 1.2 elements. This means that different queries are required to retrieve all SOAP endpoints: http://pic.dhe.ibm.com/infocenter/sr/v8r0/topic/com.ibm.sr.doc/c wsr_SOAPendpoints.html. It also means that SOAP 1.2 endpoints cannot be individually Environment classified for promotion to different runtimes.
Problem conclusion
This APAR introduces the ability for WSDL documents containing SOAP 1.2 elements to generate the same logical and correlated objects in WSRR as those which are generated for SOAP 1.1 elements. If a certain property is set, then both SOAP 1.1 and SOAP 1.2 style objects will be created for SOAP 1.2 elements. This will allow the SOAP 1.1 style query for endpoints to return all SOAP endpoints. It will also generate SOAPServiceEndpoint objects for each unique SOAP 1.2 address element, which can then be Environment classified to make use of Promotion filtering. Reference page on querying for SOAP endpoints: http://pic.dhe.ibm.com/infocenter/sr/v8r0/topic/com.ibm.sr.doc/c wsr_SOAPendpoints.html To achieve this behaviour a User Configuration item named 'SOAP12_LOAD_MODE' must be added to the WSRR Configuration Profile. This file should contain a single property as follows: soap12LoadMode=createSOAPObjects Reference page on adding User Configurations: http://pic.dhe.ibm.com/infocenter/sr/v8r0/topic/com.ibm.sr.webui .doc/html/config_admin_user_configuration.html Turning this setting on is recommended as a 1-time only operation, which should be performed before any WSDL documents have been loaded to WSRR. Once it is set, it is recommended that it should remain set, to avoid creating a mix of object types. This setting is designed to be 'sticky' to avoid it being accidentally unset. If the User Configuration is deleted or another profile is activated which does not contain it, the behaviour will remain as whatever the soap12LoadMode was last set to. Therefore once set, the only way to turn this behaviour off is to explicitly set it as follows: soap12LoadMode=noSOAPObjects This APAR is targeted at WSRR V8.0.0.3.
Temporary fix
Comments
APAR Information
APAR number
IV50318
Reported component name
SERVICE REGISTR
Reported component ID
5724N7200
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-10-03
Closed date
2014-01-27
Last modified date
2014-01-27
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
R750 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":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
27 January 2014