I am trying to run the Debugger against a web service session, but the session fails, and the session log contains an error message indicating that the workflow context is required to run the session.
If you want to debug a web service session, you must run the Debugger against the web service workflow. You cannot run the Debugger against a web service mapping or a reusable session without the workflow.
I updated the source WSDL and reimported my source and target definitions. The workflow is valid, but the service WSDL is not updated.
Changes to a mapping are not dynamically reflected in the Web Services Hub. To generate the WSDL to reflect the mapping changes, you need to edit and save the workflow. When you save the workflow, the Web Services Hub generates the WSDL for the service.
My web service workflow was valid in the Workflow Manager, but became invalid when I started the Web Services Hub.
After you start the Web Services Hub, it validates each web service workflow according to its own validation rules in addition to those of the Workflow Manager.
The Web Services Hub validates web service workflows according to the following rules:
There can be no more than one web service source definition in the mapping.
There can be no more than one web service target definition in the mapping.
If there are no web service target definitions in the mapping, the Web Services Hub treats the web service as a one-way service.
A Repository Service must be associated with the Web Services Hub.
An Integration Service must be associated with the workflow.
See the Validate tab in the Workflow Manager for Web Services Hub error messages, and correct the problem indicated by the error message.
While trying to fetch a workflow on a Web Services Hub, I received error messages indicating that there is no Integration Service specified for the service workflow and the service workflow is invalid.
I sent a request to a web service workflow that is configured to run more than one instance on the Web Services Hub. After I sent the request, I stopped the web service workflow. I received a fault response.
The Web Services Hub periodically checks the status of a workflow. It generates a fault response when it sends a request to the workflow before it registers that the workflow is not running. If a workflow is configured to run more than one instance, the Web Services Hub starts another instance of the workflow. However, since the Web Services Hub does not cache requests, it cannot resend the request to the new instance of the workflow.
I made changes to a real-time web service workflow in a versioned repository. When I ran the workflow, the changes were not in effect.
When you modify a real-time web service workflow in a versioned repository, you must check in the workflow for the changes to take effect.
For example, you modify a real-time web service workflow to associate it with a different PowerCenter Integration Service. If you check in the changes, the Web Services Hub uses the new Integration Service to run the workflow. If you do not check in the changes, the Web Services Hub does not use the new Integration Service unless you restart the Web Services Hub.