Page History

...

• WSStub instances that are configured previously can be used as they were without opening the CPS. However, if the WSStub instance is reconfigured then there will be following changes:
  • Port names are changed
    This would result in the routes leading to and from the component to disappear on closing the CPS.
  • Schemas on ports are changed
    This would mean that the already defined transformations are no longer valid and will have to be redefined.
    So it is recommended to save the transformations defined on the route externally and redefine the transformations after the component is configured.
  • Web Service name changed
    The webservice name will be the context name appended with suffix "Service" for the old WSStub components. If we deploy the same WSStub with out any configuration changes, then the web service name will be context name itself. No suffix will be appended. This will result to reconfigure the Web service consumer components configured to use this service should be reconfigured to fetch the service name.

• Whenever axis fault is thrown as in the case of username token authentication, hostname is also included in the detail as shown below:

  Code Block

  <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Server.generalException</faultcode> <faultstring>WSDoAllReceiver: Request does not contain required Security header</faultstring> <detail> <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">Dinesh-PC</ns1:hostname> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope>

  For security reasons, it is ideal to remove hostname from Axis fault. To remove the hostname, set the system property "REMOVE_HOSTNAME_IN_FAULT" to true in either of the peer server configuration files below:

  • server.conf: $Fiorano_Home\esb\server\bin
  • fps.conf file: $Fiorano_Home\esb\fps\bin