Skip to Content

     Summary: – In this scenario we’ll send data to the dynamic SOAP receiver i.e. data send to the SOAP URL which we received from the sender payload. With this we can send data to different receiver system with same receiver communication channel. As this become an Asynchronous communication (instead of Synchronous communication for SOAP receiver) it avoids timeout error.

Create Function Library and pass URL and Username from sender Payload.

WSDL9.jpg

Create DynamicConfigurationKey to hold dynamically created URL and username for URL store it in TServerLocation and for username in TAuthKey.

WSDL2.jpg

In Message Mapping pass of sender data URL and Username to Function Library.

WSDL3.jpg

Give any name in Target URL field as it is obligatory field for receiver communication channel.

WSDL4.jpg

Set Variable Header as TServerLocation and username in Key field Related Passwords in Authentication Keys

WSDL5.jpg

Note: – Here we’ve multiple Key and Password fields u can give all Username Password for different system which can receive this data.

Benefits

  • Different receiver system can use same channel.
  • Less Time to develop scenario.
  • Avoid Timeout in synchronous scenario by making it Asynchronous.

Dependencies

  • As shown in fig. below as Target URL is obligatory we must enter ‘http://’ otherwise it throws error in Payload as shown in fig. below and not allow send data although dynamic URL is correct.

    WSDL6.jpg

    WSDL7.jpg

  • In Authentication keys fields Key (username) and Password which can access this system must defined as shown below.

    WSDL8.jpg

  • Username and URL fields in sender payload are obligatory to receive data.
To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply