IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#TechXchangePresenter
 View Only
Expand all | Collapse all

refreshing webservice connector taking lot of time to execu

  • 1.  refreshing webservice connector taking lot of time to execu

    Posted Tue June 09, 2009 03:20 PM

    Hi ,

    i have performance issues with the WebService Connector when i am refreshing it manually.i.e.

    Step1 : com.msn.selectInboundTransactions _InBoundTran= this.getInboundTransactions();

    step2:_InBoundTran.getParameters().setInternalID(InternalID);

    step3:_InBoundTran.refresh(); :cry:

    the Step3 is taking lot of time to complete.

    is there any way to reduce the refresh time interval or is there any tuning steps to take care while manual refresh of the WSConnector.

    DB : ORACLE

    Object Type:View

    Effected rows: 700-800


    #MWS-CAF-Task-Engine
    #webMethods-BPMS
    #webMethods


  • 2.  RE: refreshing webservice connector taking lot of time to execu

    Posted Tue June 09, 2009 11:43 PM

    Take a look at the Oracle query first to make sure it is not a source of the bottleneck. E.g. it is uses correct indexes and joins. You can probably just measure execution of this JDBC service directly from IS.

    If this is not a query itself problem than likely it is simply due to the amount of data being returned via web Service, which tend to run slower with increased size of soap response. One easy thing you can try is to expose this flow service via WSD node in Intergration Server and use Doc-Liternal SOAP encoding which runs much faster than default RPC Encoded.

    If nothing helps then you may need to implement more sophisticated data loading scheme to account for user response time. Typical approach would be to have two services: the one which returns only few first records to display on the screen immediately and the second one to return all records and which would run in background and make records available for the user overtime.


    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS