Salesforce

Web Services (Magic xpi 4.13)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Web Services (Magic xpi 4.13)

If you want to provide a Web service, you need to first define the Web Service Provider in the Settings dialog box's Resources section and the Web service parameters in the Settings dialog box's Services section. Later on, when you drag the Web Services trigger to the flow's Trigger area, you can configure this component to work with these parameters.

Web services as a trigger contain the following parameters (parameters in bold are mandatory):

Parameter

Description

Web Service Provider

Select the required Web services provider resource from the list of resources that you created in the Settings dialog box's Resources section.

Web Service Name

The name of the service .jar file.

Service Namespace

The Service Namespace identifier. The value in this read-only field is taken from the Web Service Deployment dialog box, described here.

SOAP Version

The SOAP protocol to use for this WSDL file. Select one of the following from the drop-down list:

  • SOAP 1.1

  • SOAP 1.2

Operation Type

The SOAP Binding/Encoding type. Select one of the following from the drop-down list:

  • Document/Literal

  • Document/Wrapped

  • RPC/Literal (Note that Magic xpi does not support RPC with complex types.)

Attachment Type

Determines how the service-level attachments, which are not sent as arguments, will be wrapped around the SOAP request. Select one of the following from the drop-down list:

  • MIME (default)

  • DIME

Web services as a service also give you the following buttons:

Button

Description

Operations

Click this button to open the Web Services Operations dialog box. Here, you need to define operations and operation parameters for this service. Click here for more details.

Management

Click this button to open the Web Service Deployment dialog box. Here, you can deploy and undeploy the Web service. Click here for more details.

You must deploy to the Magic SOAP server to ensure that the server will work.

Related Topic

Magic SOAP Server

Reference
Attachment 
Attachment