Salesforce

Web Service Tab (Magic xpa 3.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Web Service Tab

In this tab, you can define your own class name and method names for each data source or for multiple data sources.

The Web Service tab of the Data Source Properties dialog box is available for SQL non-Local data sources.

Property

Description

Read

Operation

The class name and method name (which are defined in the Web Service provider) for the operation, for example: OrdersClient.Read.

If this property has a value, the value will be used at Runtime as the class name and operation. This enables you to use your own Web Service provider.

If not defined, at runtime, the class name will be WSGWProviderClient and the method name will be the name of the operation: Read. This behavior lets you use a simple Web Service provider and Magic xpa's DataManipulate function as the data provider.

If the Web Service was defined in the CRR, its class name and method name can be selected using auto-complete. If auto-complete is used, the word Client will be added as the suffix.

Endpoint

The entry point for the Read operation. The entry point is required if there are several Web services with the same contract.

If the Endpoint property has a value, this value will be used as the endpoint.

If the Endpoint property value is blank, the endpoint value will not be sent.

Manipulate

Operation

The class name and method name (which are defined in the Web Service provider) for the operation, for example: OrdersClient.Manipulate.

If this property has a value, the value will be used at Runtime as the class name and operation. This enables you to use your own Web Service provider.

If not defined, at runtime, the class name will be WSGWProviderClient and the method name will be the name of the operation: Manipulate. This behavior lets you use a simple Web Service provider and Magic xpa's DataManipulate function as the data provider.

If the Web Service was defined in the CRR, its class name and method name can be selected using auto-complete. If auto-complete is used, the word Client will be added as the suffix.

Endpoint

The entry point for the Manipulate operation. The entry point is required if there are several Web services with the same contract.

If the Endpoint property has a value, this value will be used as the endpoint.

If the Endpoint property value is blank, the endpoint value will not be sent.

Create member

The class member name (which is defined in the Web Service provider) for the Create operation, for example: Create.

If this property has a value, the value will be used at Runtime as the Create member under the manipulate method.

If not defined, at runtime, the name will be Create.

If the Web Service was defined in the CRR, the member name can be selected using auto-complete.

Update member

The class member name (which is defined in the Web Service provider) for the Update operation, for example: Update.

If this property has a value, the value will be used at Runtime as the Update member under the manipulate method.

If not defined, at runtime, the name will be Update.

If the Web Service was defined in the CRR, the member name can be selected using auto-complete.

Delete member

The class member name (which is defined in the Web Service provider) for the Delete operation, for example: Delete.

If this property has a value, the value will be used at Runtime as the Delete member under the manipulate method.

If not defined, at runtime, the name will be Delete.

If the Web Service was defined in the CRR, the member name can be selected using auto-complete.

General

The namespace that will be used in the Web Service Data Source Builder as the target namespace in the Web Service requests.

If the Namespace property has a value, the value will be used as the namespace in the XML requests. For example:

<ReadOrdersResponse xmlns="http://myorg/myproject/orders">

If the property is blank, no namespace is sent.

Since version: 3.2; multiple data source support – since version: 3.2a

Related Topics

Reference
Attachment 
Attachment