Knowledge Article
How to set a specific SOAP version by default used by a Web Service - Remedy AR System Server
In BMC Remedy AR System Server the way webservice version is called is different in 9.1 and does not act like it did in older versions
Remedy Action Request System
AR System
Remedy AR System Server v9.1.02 or newer SOAP Web service consumption
How to set a specific SOAP version by default used by a Web service call (Remedy filter). |
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. In BMC Remedy 9.1.02, the way it is designed to call the SOAP version (SOAP 1.1 vs 1.2) is now called in the order of SOAP 1.2 and then if the proper response header is not provided the server makes a second call using SOAP 1.1. This design change was made because of the increase of customers utilizing SOAP 1.2 instead of SOAP 1.1. For remedy AR server 9.1.02 with latest AR server Hot Fix, the specific SOAP version can be configured in the AR System Configuration Generic UI only for component: com.bmc.arsys.server.extension.webserver.. The defect SW00523414 provides a configuration option to choose the sequence for calling WebServices with a different SOAP version. To create a Configuration Setting in the AR System Configuration Generic UI, do the following: 1. ARS version 9.1.02 needs to be installed. 2. Apply the latest Hot Fix containing this configuration option. The Hot Fix can be found accessing the below FTP address: ftp://ftp.bmc.com/pub/ARRecommendedFixes/Server/9.1.02/ or apply the Service Pack 3 (SP3) or higher. 3. To apply the required configuration setting in the application follow these steps: a) Go to Applications > AR System Administration > AR System Administration Console b) Select System > General > Centralized Configuration c) In the Centralized Configuration console select the component "com.bmc.arsys.server.extension.webservice" with picking the appropriate server name. d) Press the Add button to create a new parameter record. e) In the new created record enter the following settings: - Setting name - "soapsequence". - Setting value - the Following values are permitted/valid - Soap11Only - Web service will be tried with Soap1.1 only Soap12Only - Web service will be tried with Soap1.2 only Soap12First - Web service will be tried with Soap1.2 first and if error comes will be tried with Soap1.1 and this is default Soap11First - Web service will be tried with Soap1.1 first and if error comes will be tried with Soap1.2 f) Apply the changes. Note: You need to restart the AR Server services for setting soapsequence changes done from Centralized Configuration. This is related to Defect SW00555237. Alternate instructions to establish the setting when the com.bmc.arsys.server.extension.webservice component is not present. 1. Open the AR System Configuration Component Setting form. 2. Create a new record. 3. Enter the following: - Component Name: <your_server_name> - Component Type: com.bmc.arsys.server.extension.webservice - Setting name: "soapsequence". - Setting value: the Following values are permitted/valid - Soap11Only - Web service will be tried with Soap1.1 only Soap12Only - Web service will be tried with Soap1.2 only Soap12First - Web service will be tried with Soap1.2 first and if error comes will be tried with Soap1.1 and this is default Soap11First - Web service will be tried with Soap1.1 first and if error comes will be tried with Soap1.2 4. Save the record and the needed GUIDs will be generated. As per the example above it sets the soapsequence to try the SOAP 1.1 request first and then if that fails, try a SOAP 1.2 request. Note: the setting is implemented for all SOAP WebService calls. Additional Notes: If the setting does not seem to be recognized, there are a few settings in the ar.conf/ar.cfg of the ARServer that may need to be adjusted, the below entries needs to match with the server name you have in the component name under Centralized Configuration.
|
Attachment(s):