Q

Why is the Web Services Client step shown as unconfigured, with a red cross mark over it and the resource configuration is not populated after migrating the older project in the Magic xpi version 4.12?

A

One of the reasons for this error to occur could be that the step is invalid and as a result, it fails to open.

To fix the issue, delete the step which is shown as unconfigured and has a red cross mark over it. In place of it, add a new Web Services Client step and configure it. For more information on the Web Services Client step configuration, click here.

Q

Why is the Web Services Client step shown as unconfigured, and the resource configuration is not populated after migrating the older project in the Magic xpi version 4.12?

A

One of the reasons for this error to occur could be that the step is not configured correctly and as a result it fails to open.

The other reason could be the WSDL path points to an incorrect location.

In Magic xpi 4.12 , the Web Services component is re-architected and there is a change in design. After upgrading a project to Magic xpi 4.12, when the WSDL is missing or is not loading properly, the resource configuration will not be populated correctly and as a result the step is shown as unconfigured.

To fix the issue, reconfigure or recreate the step as per the required parameters or provide the valid WSDL location so that it gets loaded successfully.

Q

Why is the Web Services Client step shown as unconfigured, with a red cross mark over it and the resource configuration is not populated after migrating the older project in the Magic xpi version 4.13?

A

The old Systinet Server for Java has been replaced with Magic SOAP Server in Magic xpi 4.13. This may invalidate the step when the old project is migrated to xpi 4.13 and as a result, it may fail to open.

To fix the issue, reconfigure the Web Services Client resource to point to the new WSDL URL generated using the Magic SOAP Server and reload WSDL. After that reconfigure the step.

Q

Why do I get an error "Web Service Client invocation failed org.apache.cxf.transport.http.HTTPException: HTTP response '415: Unsupported Media Type' when communicating with Text Casing Service from DataAccess ( http://www.dataaccess.com/webservicesserver/textcasing.wso) using the Web Services Client?

A

One of the reasons for this error to occur could be the incorrect configuration of the Web Services step. To solve the issue try setting the Attachment Type in the Web Services Client resource settings to Blank, if the attachments are not to be sent.