×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
TrueSight Orchestration Content 20.19.01 ... Base adapters Web Services adapter Adapter requests and responses for the Web Services adapter Web Services adapter request for the JAX-WS approach

Web Services adapter Make SOAP request using message mode, and response

In the Message mode, you can provide either the entire SOAP envelope or the SOAP body payload, as required by the web service.

This method supports signing SOAP messages according to the Web Services Security (WSS) specification to assure the integrity of the SOAP message and allows the use of the X.509 security token format. Signed messages also provide nonrepudiation.

This method also supports UsernameToken Profile authentication that defines how a web service consumer can supply a UsernameToken to identify the requestor using a user name and a password to authenticate that identity to the web service producer.

This method supports uploading attachments to the outgoing SOAP request and downloading attachments that are embedded in the SOAP response received from the web server.

The following table describes the elements for the Web Services adapter request for Make SOAP in the Message mode.


Element

Description

Required

<wsdl-location>

Specifies the URI (file name or URL) pointing to a XML WSDL definition

Yes

<soap-message>

Specifies the fully formatted SOAP message to transmit

Yes

<endpoint-address>

Specifies the target service endpoint address

This element can be used if the SOAP request must be invoked on an endpoint address other than the one specified in the WSDL document.

No

<service-name>

Specifies a unique name among all the services defined in the enclosing WSDL document

A service groups a set of related ports together.

No

<port-name>

Specifies a unique name among all the ports defined in the enclosing WSDL document

A port defines an individual endpoint by specifying a single address for a binding.

No

<soap-action>

Specifies the value of the SOAPAction header for the operation

No

<soap-version>

Specifies the SOAP version to use

Valid values: 1.1 (default), 1.2

No

<use-ssl-certificate>

Specifies whether to establish a secure connection

Set the value of this element to true when <wsdl location> uses HTTPS.
Set the value of this element to false or leave it blank when <wsdl location> uses HTTP.

Valid values: true, false (default)

Conditional; set <use-ssl-certificate> to true if <soap-url> specifies a secure URL (https)

<install-certificate>

Specifies whether to install certificates

Set the value of this element to true if you prefer to have security certificates installed automatically (a common practice). Set the value of this element to false if you prefer to manually export the security certificate from the specified target server and manually import it into the TrueSight Orchestration's local peer's cacerts file (a rare practice).

Valid values: true, false (default)

No

<allow-unsigned-certificate>

Specifies whether to allow unsigned certificates from trusted zones

Set the value of this element to true, if you are using self-signed SSL certificates (a common practice).

On ecommerce sites or military installations, if you need to use signed certificates such as Verisign or Thawte, set the value of this element to false (a rare practice).

Default value: false

No

<truststore-file>

Specifies the path to the truststore file containing the CAs

Default value: Java standard truststore

No

<passphrase>

Specifies the password of the truststore file

Warning

  • The value of the <passphrase> element is the passphrase for the cacerts certificate stored on the TrueSight Orchestration local peer (CDP or AP) and not the specified target host.

  • Changing the passphrase can be tricky and might destroy the cacerts security file integrity.


Verify the cacerts passphrase using the following command in UNIX or Linux:

$ /opt/bmc/ao/cdp/jvm/bin/keytool -list -keystore
/opt/bmc/ao/cdp/jvm/lib/security/cacerts

Default value: changeit

No

<keystore-file>

Specifies the path to the keystore containing the client certificate

No

<keystore-passphrase>

Specifies the path to the keystore containing the client certificate

Default value: changeit

No

<client-alias>

Specifies the alias name in the keystore that identifies the public key certificate (PKC) used by the web server to authenticate the client computer

No

<username-token>

Builds a Web Services Username Token and inserts it into the SOAP envelope

Valid values: true, false

No

<username>

Specifies the user name for authentication

Note

You can also use the <username> element for a password-protected WSDL.

No

<password>

Specifies the password for authentication

Note

You can also use the <password> element for a password-protected WSDL.

No

<password-encryption-type>

Specifies the method of encryption used to encrypt the given password

Valid values: Base64, Plain (default)

Notes

This element can contain an encryption-type attribute to indicate whether the passphrase provided is encrypted:

  • If the <password-encryption-type> element is Base64, provide a Base64 encoded value.
  • If the <password-encryption-type> element is Plain, provide value in a plain text.

No

<password-type>

Specifies the types of password supported by UsernameToken Authentication

This parameter is read-only if the value of the <username-token> element is true.

Valid values: plain-text (default), digest

No

<timestamp>

Builds a Web Services timestamp and inserts it into the SOAP envelope

Valid values: true, false (default)

No

<time-to-live>

Sets the time difference in seconds between the Created and the Expires values in the timestamp

Default value: 60 seconds

No

<nonce-validation>

Adds a nonce element to the <username-token> element

Valid values: true, false (default)

No

<created-validation>

Adds a created element to the <username-token> element

Valid values: true, false (default)

No

<sign-request>

Creates a signature according to the Web Services specification X.509 profile and adds it to the Security header

The Token Reference supported by the adapter is Binary Security Token.

Valid values: true, false (default)

No

<signature-properties>

Contains the elements used to specify the information about the X.509 certificate (public key) and the private key that are used for XML digital signature

Valid values for the mode attribute:

  • key-store (default)
  • key-files
  • key-data

No

<sign-username-token>

Signs the Web Services <username-token> element in the Security header

Valid values: true, false (default)

No

<sign-timestamp>

Signs the Web Services timestamp element in the Security header

Valid values: true, false (default)

No

<private-key-file>

Specifies the file containing the private key used to sign the SOAP message using the signing algorithm The adapter supports the following formats:

  • Base64-encoded unencrypted PEM
  • Definite Encoding Rules (DER)

Conditional; required if <signature-properties mode="key-files">

<certificate-file>

Specifies the file containing the X.509 certificate (public key)

The adapter supports the following formats:

  • Base64-encoded unencrypted PEM
  • DER

Conditional; required if <signature-properties mode="key-files">

<private-key-data>

Specifies the private key in unencrypted Base64-encoded PEM format

Conditional; required if <signature-properties mode="key-data">

<certificate-data>

Specifies the X.509 certificate (public key) in unencrypted Base64-encoded PEM format

Conditional; required if <signature-properties mode="key-data">

<keystore-file>

Configures the adapter to use the Java keystore (JKS) specified by the keystore file name

Conditional; required if <signature-properties mode="key-store">

<keystore-password>

Specifies the password of the keystore

Conditional; required if <signature-properties mode="key-store">

<alias>

Specifies the user's alias name in the keystore that identifies the private key to sign the document

Conditional; required if <signature-properties mode="key-store">

<password>

Specifies the user's password to get the private signing key from the keystore

No

<invocation-mode>

Specifies the ways in which a web service request can be invoked

Valid values:

  • synchronous (default)
  • asynchronous
  • one-way

No

<proxy-settings>

Contains the elements that define the HTTP proxy settings

No

<host>

Specifies the host name or the IP address of the host for the Web service request

Conditional; required if the <proxy-settings> element is used

<port>

Specifies the destination port for the Web service request

Conditional; required if the <proxy-settings> element is used

<user-name>

Specifies the name of the user, who requests the proxy service

Conditional; required if the <proxy-settings> element is used and authentication is enabled and necessary on the proxy server

<password>

Specifies the password for the user on the specified host

Conditional; required if <proxy-settings> is used and authentication is enabled and necessary on the proxy server

<download-attachments>

Specifies whether to download attachments that are embedded as MIME parts in the SOAP response

Valid value: true, false (default)

No

<character-set>

Specifies the supporting CharSet

Also called character set, it includes identifiers describing a series of universal characters.

No

<attachments>

Contains the <attachment> elements

No

<attachment>

Contains the <file> and <content-id> elements

No

<file>

Specifies the name and path of the file that is to be attached with the outgoing SOAP request

You can include one or more <attachment> elements in <attachments>. The file to be attached must reside on the peer that executes the adapter request.

No

<content-id>

Specifies a unique identifier for an attachment that is to be attached with the outgoing SOAP request

You can specify a unique value for the attachment, if the web server requires it. If you do not specify a value, the adapter generates a value with the format uuid-unique string.
For example: uuid-6264cbe2-0780-4235-a50b-e68537e34bfc

No

<http-request-headers>

Specifies an XML document containing the list of custom HTTP headers to be added to the outgoing SOAP request

Sample XML:
<http-request-headers>
<http-request-header>
<name></name>
<value></value>
</http-request-header>
<http-request-header>
<name></name>
<value></value>
</http-request-header>
.
.
.
</http-request-headers>

Conditional; required if the request contains the <http-request-header> element

<http-request-header>

Contains the <name> and <value> elements

Conditional; required if the request contains the <name> and <value> elements

<name>

Specifies the name of the HTTP header to be added to the outgoing SOAP request

No

<value>

Specifies the corresponding value for the HTTP header specified in the <name> element

No

<use-connection-pooling>

Specifies whether the connection pooling feature is enabled for the adapter

Valid values: true, false (default)

No

<max-connections>

If the value of <use-connection-pooling> is true, defines the maximum number of objects that can be in circulation in the pool

Valid values: Any positive integer

Valid values: Any positive integer

Default value: 10

No

<connection-ttl>

If the value of <use-connection-pooling> is true, specifies the maximum amount of time, in minutes, that a connection can remain idle in the connection pool before it is terminated

Valid values: Any positive integer

Default value: 60 minutes

No

The following figure shows an XML sample of the Web Services adapter request with the synchronous Message mode and using username-token authentication with a Base64-encoded password and X.509 digital signature authentication. Use the adapter request XML when you create a custom process by using the Call Adapter activity in TrueSight Orchestration Development Studio.

XML sample of the Web Services adapter request for Make SOAP Request in Message mode and using username-token and X.509 digital signature authentication 


 <soap-rpc-request>
    <wsdl-location>http://vm-w23-rds19:9090/atriumversions_porttype?wsdl
    </wsdl-location>
    <username-token>true</username-token>
    <username>Demo</username>
    <password encryption-type="Base64">
              IA==
    </password>
    <password-type>plain-text</password-type>
    <character-set>UTF-8</character-set>
    <nonce-validation>true</nonce-validation>
    <created-validation>true</created-validation>
    <sign-request>true</sign-request>
    <signature-properties mode="keystore">
      <sign-username-token>true</sign-username-token>
      <sign-timestamp />
      <keystore-file>C:\Security\bmcatriumwsclient_7.5.00.001.jks</keystore-file>
      <keystore-password>atrium</keystore-password>
      <alias>bmcatriumwsclient</alias>
    </signature-properties>
    <invocation-mode>synchronous</invocation-mode>
    <soap-message>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
        <soapenv:Header />
        <soapenv:Body>
          <typ:GetVersions> xmlns:typ="http://atrium.bmc.com/2009/01/versions/types">
            <appIdList>
              <list>OB00C04FA081BABZlxQAmyflAg1wEA</list>
            </appIdList>
          </typ:GetVersions>
        </soapenv:Body>
      </soapenv:Envelope>
    </soap-message>
  </soap-rpc-request>


The following figure shows an XML sample of the Web Services adapter request for Make SOAP Request with the synchronous Message mode and using a timestamp and X.509 digital signature authentication. Use the adapter request XML when you create a custom process by using the Call Adapter activity in TrueSight Orchestration Development Studio.

XML sample of the Web Services adapter request for Make SOAP Request in Message mode and using timestamp and X.509 digital signature authentication 


<soap-rpc-request>
 <wsdl-location>http://s3.amazonaws.com/ec2-downloads/2009-10-31.ec2.wsdl
 </wsdl-location>
    <timestamp>true</timestamp>
    <time-to-live>30</time-to-live>
    <sign-request>true</sign-request>
    <signature-properties mode="key-files">
      <sign-username-token />
      <sign-timestamp>true</sign-timestamp>
      <private-key-file>C:\Security\private-key.der</private-key-file>
      <certificate-file>C:\Security\certificate.der</certificate-file>
    </signature-properties>
    <invocation-mode>synchronous</invocation-mode>
    <soap-message>
      <web:DescribeSecurityGroups xmlns:web="http://ec2.amazonaws.com/doc/2009-10-31/">
        <web:securityGroupSet />
      </web:DescribeSecurityGroups>
    </soap-message>
</soap-rpc-request>


The following figure shows the Web Services adapter request for Make SOAP Request with HTTPS Client Authentication. Use the adapter request XML when you create a custom process by using the Call Adapter activity in TrueSight Orchestration Development Studio.

XML sample of the Web Services adapter request for Make SOAP Request in Message mode with HTTPS Client Authentication 


 <soap-rpc-request>
  <wsdl-location>https://vm-w23-rds87:8181/CentralDataService/CentralData?wsdl
  </wsdl-location>
  <invocation-mode>synchronous</invocation-mode>
  <use-ssl-certificate>true</use-ssl-certificate>
  <install-certificate>true</install-certificate>
  <allow-unsigned-certificate>false</allow-unsigned-certificate>
  <truststore-file>C:\Rohit\cacerts.jks</truststore-file>
  <passphrase>changeit</passphrase>
  <keystore-file>C:\keystore.jks</keystore-file>
  <keystore-passphrase>changeit</keystore-passphrase>
  <client-alias>s1as</client-alias>
  <soap-message>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://service.centraldata.com/">
      <soapenv:Header/>
      <soapenv:Body>
        <ser:findReservations>
          <lastName>Doe</lastName>
        </ser:findReservations>
      </soapenv:Body>
    </soapenv:Envelope>
  </soap-message>
</soap-rpc-request>

The following figure shows an XML sample of the adapter request that supports uploading an attachment with the outgoing SOAP request.

XML sample of the Web Services actor adapter request that supports uploading attachments 


    <soap-rpc-request>
    <wsdl-location>
     http://vm-w23-rds87:8080/SwaTestService/jaxws/SwaTest?WSDL
    </wsdl-location>
    <soap-version>1.1</soap-version>
    <use-ssl-certificate>false</use-ssl-certificate>
    <install-certificate>false</install-certificate>
    <allow-unsigned-certificate>false</allow-unsigned-certificate>
    <passphrase>changeit</passphrase>
    <download-attachments>true</download-attachments>
    <invocation-mode>synchronous</invocation-mode>
    <character-set />
    <soap-message>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://SwaTestService.org/xsd">
        <soapenv:Header />
        <soapenv:Body>
          <xsd:InputRequestPut>
            <xsd:mimeType1>text/plain</xsd:mimeType1>
            <xsd:mimeType2>text/html</xsd:mimeType2>
            <xsd:header>test</xsd:header>
          </xsd:InputRequestPut>
        </soapenv:Body>
      </soapenv:Envelope>
    </soap-message>
    <attachments>
      <attachment>
        <file>C:\Add Attachments\attach.txt</file>
        <content-id>attach1=1@localhost</content-id>
      </attachment>
      <attachment>
        <file>C:\Add Attachments\attach.html</file>
        <content-id>attach2=2@localhost</content-id>
      </attachment>
    </attachments>
  </soap-rpc-request>

The following figure shows an XML sample of the adapter request that supports downloading an attachment.

XML sample of the Web Services adapter request using Make SOAP Request in Message Mode that supports downloading attachments 


<soap-rpc-request>
            <wsdl-location>http://vm-w23-rds87:8080/SwaTestService/jaxws/SwaTest?WSDL</wsdl-location>
            <download-attachments>true</download-attachments>
            <soap-message>
                  <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://SwaTestService.org/xsd">
                     <soapenv:Header/>
                     <soapenv:Body>
                        <xsd:InputRequestGet>
                           <xsd:mimeType1>text/plain</xsd:mimeType1>
                           <xsd:mimeType2>application/vnd.openxmlformats-officedocument.wordprocessingml.document</xsd:mimeType2>
                           <xsd:url1>attach.txt</xsd:url1>
                           <xsd:url2>attach.html</xsd:url2>
                        </xsd:InputRequestGet>
                     </soapenv:Body>
                  </soapenv:Envelope>
            </soap-message>
</soap-rpc-request>


The following figure shows an XML sample of the adapter request that supports custom HTTP headers.

XML sample of the Web Services adapter request that supports custom HTTP headers 


<soap-rpc-request>
    <wsdl-location>http://www.webservicex.com/country.asmx?wsdl</wsdl-location>
    <soap-version>1.1</soap-version>
    <use-ssl-certificate>false</use-ssl-certificate>
    <install-certificate>false</install-certificate>
    <allow-unsigned-certificate>false</allow-unsigned-certificate>
    <passphrase>changeit</passphrase>
    <download-attachments>false</download-attachments>
    <invocation-mode>synchronous</invocation-mode>
    <character-set />
    <http-request-headers>
      <http-request-header>
        <name>Content-Type</name>
        <value>text/xml;charset=UTF-8</value>
      </http-request-header>
      <http-request-header>
        <name>X-Client-Version</name>
        <value>1.0-RC</value>
      </http-request-header>
      <http-request-header>
        <name>Cache-Control</name>
        <value>no-cache</value>
      </http-request-header>
      <http-request-header>
        <name>Content-Language</name>
        <value>en-US</value>
      </http-request-header>
    </http-request-headers>
    <soap-message>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:web="http://www.webserviceX.NET">
        <soapenv:Header />
        <soapenv:Body>
          <web:GetCurrencyByCountry>
            <web:CountryName>India</web:CountryName>
          </web:GetCurrencyByCountry>
        </soapenv:Body>
      </soapenv:Envelope>
    </soap-message>
  </soap-rpc-request>

The following figure shows an XML sample of the Web Services adapter request when connection pooling is enabled to connect to the remote host.

XML sample of the Web Services adapter request when connection pooling is enabled to connect to the remote host 


<soap-rpc-request>
  <timestamp>true</timestamp>
  <time-to-live>120</time-to-live>
  <sign-request>true</sign-request>
  <use-connection-pooling>true</use-connection-pooling>
  <max-connections>10</max-connections>
  <connection-ttl>60</connection-ttl>
</soap-rpc-request>

The Web Services adapter returns a SOAP response. The following figure illustrates the Web Services adapter response to a request for Make SOAP Request with synchronous Message mode and using username token and X.509 digital signature authentication.

XML sample of the Web Services adapter response to a request for Make SOAP Request in Message mode and using username token and X.509 digital signature authentication 


<soap-response>
  <metadata>
    <status>success</status>
  </metadata>
  <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SOAP-ENV:Header />
    <SOAP-ENV:Body>
      <GetVersionsOutput xmlns="http://atrium.bmc.com/2009/01/versions/types">
        <versionInfoList xmlns="">
          <list>
            <applicationId>OB00C04FA081BABZlxQAmyflAg1wEA</applicationId>
            <applicationName>BMC Atrium CMDB</applicationName>
            <maintenanceVer>0</maintenanceVer>
            <majorVer>7</majorVer>
            <minorVer>5</minorVer>
            <patchNum>3</patchNum>
            <isExist>true</isExist>
          </list>
        </versionInfoList>
        <status xmlns="" />
        <extensions xmlns="" xsi:nil="true" />
      </GetVersionsOutput>
    </SOAP-ENV:Body>
  </SOAP-ENV:Envelope>
</soap-response>


The following figure illustrates an XML sample of the adapter response for the Web Services adapter request for Make SOAP Request in Message mode and using timestamp and X.509 digital signature authentication.

XML sample of the Web Services adapter response to a request for Make SOAP Request in Message mode and using timestamp and X.509 digital signature authentication 


<soap-response>
  <metadata>
    <status>success</status>
  </metadata>
  <DescribeSecurityGroupsResponse xmlns="http://ec2.amazonaws.com/doc/2009-10-31/">
    <requestId>29b3f7ee-93ab-43e9-a7d1-4894881f2ef3</requestId>
    <securityGroupInfo>
      <item>
        <ownerId>622872856407</ownerId>
        <groupName>usersec</groupName>
        <groupDescription>first AMI</groupDescription>
        <ipPermissions>
          <item>
            <ipProtocol>tcp</ipProtocol>
            <fromPort>22</fromPort>
            <toPort>22</toPort>
            <groups />
            <ipRanges>
              <item>
                <cidrIp>0.0.0.0/0</cidrIp>
              </item>
            </ipRanges>
          </item>
          <item>
            <ipProtocol>tcp</ipProtocol>
            <fromPort>80</fromPort>
            <toPort>80</toPort>
            <groups />
            <ipRanges>
              <item>
                <cidrIp>0.0.0.0/0</cidrIp>
              </item>
            </ipRanges>
          </item>
          <item>
            <ipProtocol>tcp</ipProtocol>
            <fromPort>3389</fromPort>
            <toPort>3389</toPort>
            <groups />
            <ipRanges>
              <item>
                <cidrIp>0.0.0.0/0</cidrIp>
              </item>
            </ipRanges>
          </item>
        </ipPermissions>
      </item>
      <item>
        <ownerId>622872856407</ownerId>
        <groupName>Test Security Group - 2</groupName>
        <groupDescription>test</groupDescription>
        <ipPermissions />
      </item>
    </securityGroupInfo>
  </DescribeSecurityGroupsResponse>
</soap-response>


The following figure illustrates an XML sample of the Web Services adapter response to a request for the Make SOAP Request in Message mode with HTTPS Client Authentication.

XML sample of the Web Services adapter response to a request for Make SOAP Request in Message mode with HTTP Client Authentication 


 <metadata>
    <status>success</status>
  </metadata>
  <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Header />
    <S:Body>
      <ns2:findReservationsResponse xmlns:ns2="http://service.centraldata.com/">
        <return>
          <confNumber>0001</confNumber>
          <firstName>John</firstName>
          <lastName>Doe</lastName>
        </return>
        <return>
          <confNumber>0002</confNumber>
          <firstName>Jane</firstName>
          <lastName>Doe</lastName>
        </return>
      </ns2:findReservationsResponse>
    </S:Body>
  </S:Envelope>
</soap-response>

The following figure shows an XML sample of an adapter response to a request that supports uploading attachments.

XML sample of the Web Services adapter response to a request that supports uploading attachments 


<soap-response>
  <metadata>
    <status>success</status>
  </metadata>
  <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Header />
    <S:Body>
      <OutputResponseString xmlns="http://SwaTestService.org/xsd" xmlns:ns2="http://SwaTestService.org/wsdl">
        <myString>Expected behaviour 
  attach1 content type: text/plain
 attach1 copied to: C:\Rohit\Attachments\1307610983048_attach1
 attach2 content type: text/html
 attach2 copied to: C:\Rohit\Attachments\1307610983048_attach2</myString>
      </OutputResponseString>
    </S:Body>
  </S:Envelope>
</soap-response>

The following table describes the elements of a Web Services adapter response for Make SOAP Request in Message Mode when the adapter request supports downloading attachments.

Elements of a Web Services adapter response for Make SOAP Request in Message Mode when the adapter request supports downloading attachments

Element

Description

<attachments>

Contains the <attachment> elements

<attachment>

Contains the <download-directory> and <name> elements for each attachment that is downloaded

<download-directory>

Specifies the full path of the attachment that is downloaded

<name>

Specifies the name of the attachment that is downloaded

Note

If an attachment name is included in the SOAP response, the attachment is saved with the same name. If no name is included, the attachment is downloaded with a unique format as follows:
currentTimeInMilliseconds_attachment counter

The <Content-Type> of the attachment determines the extension.

The following figure shows an XML sample of an adapter response to a request that supports downloading an attachment.

XML sample of the Web Services adapter response to a request that supports downloading attachments 


<soap-response>
  <metadata>
    <status>success</status>
  </metadata>
  <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Header />
    <S:Body>
      <MTOMOutResponse xmlns="http://MTOMTestService.org/types">
        <docUrl1>http://localhost:8080/MTOMTestService/text.xml</docUrl1>
        <docUrl2>http://localhost:8080/MTOMTestService/application.xml</docUrl2>
        <docUrl3>http://localhost:8080/MTOMTestService/attach.html</docUrl3>
        <docUrl4>http://localhost:8080/MTOMTestService/attach.jpg</docUrl4>
        <doc1>PD94bWwgdmVyc2lvbj0....JvdmlkZXJDb25maWc+</doc1>
        <doc2>PD94bWwgdmVyc2lvbj0....FwcGxpY2F0aW9uPg==</doc2>
        <doc3>PCFET0NUWVBFIEhUTUw....Ym9keT4KPC9odG1sPgo=</doc3>
        <doc4>/9j/4AAQSkZJRgABAgA....JWBSAffBJ5/HiutxRRQwP/Z</doc4>
      </MTOMOutResponse>
    </S:Body>
  </S:Envelope>
  <attachments>
    <attachment>
      <download-directory>C:\Soap_Attachments\</download-directory>
      <name>1306763809281_1.xml</name>
    </attachment>
    <attachment>
      <download-directory>C:\Soap_Attachments\</download-directory>
      <name>1306763809296_2.xml</name>
    </attachment>
    <attachment>
      <download-directory>C:\Soap_Attachments\</download-directory>
      <name>1306763809296_3.html</name>
    </attachment>
    <attachment>
      <download-directory>C:\Soap_Attachments\</download-directory>
      <name>1306763809312_4.jpeg</name>
    </attachment>
  </attachments>
</soap-response>

The following figure shows an XML sample of an adapter response to a request that supports custom HTTP headers.

XML sample of the Web Services adapter response to a request that supports custom HTTP headers 


<soap-response>
  <metadata>
    <status>success</status>
  </metadata>
  <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soap:Header />
    <soap:Body>
      <GetCurrencyByCountryResponse xmlns="http://www.webserviceX.NET">
        <GetCurrencyByCountryResult><NewDataSet>
  <Table>
    <Name>India</Name>
    <CountryCode>in</CountryCode>
    <Currency>Rupee</Currency>
    <CurrencyCode>INR</CurrencyCode>
  </Table>
  <Table>
    <Name>India</Name>
    <CountryCode>in</CountryCode>
    <Currency>Rupee</Currency>
    <CurrencyCode>INR</CurrencyCode>
  </Table>
</NewDataSet></GetCurrencyByCountryResult>
      </GetCurrencyByCountryResponse>
    </soap:Body>
  </soap:Envelope>
</soap-response>
Was this page helpful? Yes No Submitting... Thank you
Last modified by Shilpa Gokhale on May 08, 2018
jax_ws web_services base_adapters

Comments

Log in or register to comment.

Web Services adapter Make SOAP request using payload mode, and response
Web Services adapter request and response for Poll Asynchronous Response
© Copyright 2013 - 2019 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.