You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/integration/web-services/published-web-services/expose-a-web-service.md
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ This how-to was written based on Studio Pro 9.24. All the images, names, and ste
30
30
31
31
1. Create the following **Customer** entity in your domain model (for details on how to create an entity, see [Configuring a Domain Model](/refguide/configuring-a-domain-model/)):
2. Create overview and detail pages to manage objects of the **Customer** type (for details on how to create overview and detail pages, see [How to Create Your First Two Overview and Detail Pages](/howto/front-end/create-your-first-two-overview-and-detail-pages/)).
36
36
3. Create a menu item to access the customer overview page (for details on how to create menu items, see [Setting Up Navigation](/refguide/setting-up-the-navigation-structure/)).
@@ -44,16 +44,16 @@ To create a published web service, follow these steps:
44
44
45
45
2. In the **Add Published Web Service** window, enter *CustomerWebService* for the **Name**, then click **OK**:
3. You should now see the **Published Web Service** properties window. Take note of the following tab details:
50
50
* On the **Operations** tab, you can see the available operations of the web service (currently, the list is empty, so an operation will be added in the section [Publishing a Microflow](#publish-a-microflow), below):
* On the **Settings** tab, you can configure the other settings. Do change them before publishing your web service, especially the **Target namespace** (for details on these settings, see [Published Web Service](/refguide/published-web-service/)):
@@ -64,11 +64,11 @@ To create the functionality to expose, follow these steps:
64
64
1. Create a microflow that retrieves and returns a list of customers from the database (for details on how to create a microflow, see [Triggering a Microflow From a Menu Item](/refguide/triggering-microflow-from-menu-item/)).
65
65
2. Add two input parameters to dynamically set the range settings of the retrieve action. Configure the range options of the retrieve action like this:
If you get any errors, you will need to mark the input parameters in the **Operations** > **Parameters** section of the service document as **Optional** and **Nillable** (see the following section.)
74
74
@@ -78,11 +78,11 @@ To publish a microflow, follow these steps:
78
78
79
79
1. Right-click somewhere in the background of the microflow and select **Publish as Web service operation**:
You should see the name of your web service in the list.
115
115
4. Click the "WSDL schema" URL to open the WSDL. This WSDL can be given to others so they can interact with your web service.
@@ -121,7 +121,7 @@ To change the user authentication, follow these steps:
121
121
1. Double-click the published web service in the **App Explorer**.
122
122
2. In the **Published Web Service** properties window, open the **Settings** tab. Because **No Authentication** is set, current users of the web service do not need to authenticate:
@@ -59,7 +59,7 @@ This is available when the parameter is a list, and can be used to name the obje
59
59
The `CountCarsAndHp` operation takes a non-optional list of vehicles as a parameter, which is called *VehicleList* and consists of objects called *Vehicle*. This information is based on the microflow and entity model, but can be modified.
The microflow attached to the `CountCarsAndHp` operation. It takes a list of objects of the entity Vehicle as input and returns an object that holds the number of cars and the total amount of horsepower of those cars.
65
65
@@ -76,7 +76,7 @@ If you click **Select** in the **Parameter** tab, you can select individual memb
76
76
| All nillable | Checks the Nillable box on every expanded node and visible leaf node. |
77
77
| All non-nillable | Unchecks the Nillable box on every expanded node and visible leaf node. |
Here you can select which members of the entity can be passed and/or are optional or nillable, as well as set their names. Note that checking **Optional** or **Nillable** on the root element has no effect; set these values in the operation editor.
82
82
@@ -112,6 +112,6 @@ This determines if the element in the XML is sent as nil if the return value is
4. Publish both microflows as web service operations of the **CustomerWebService** as described in [How to Expose a Web Service](/howto/integration/expose-a-web-service/).
49
49
@@ -55,10 +55,10 @@ In this section, you will create a new SOAP project.
55
55
2. Press <kbd>Ctrl</kbd> + <kbd>N</kbd> to create a new SOAP project.
@@ -137,15 +137,15 @@ In this section, you will build a TestSuite. A TestSuite contains one or more Te
137
137
Assertions are used to validate the message received by a TestStep during execution, usually by comparing parts of the message (or the entire message) to some expected value. Inthis section, you will create an assertion that validates the number of customers.
5.Enter*count(//Customer)* in the XPath Expression field.
147
147
6.In step 1.4 of the previous how-to, you added some data. Enter the number of created customers in the **ExpectedResult** field. Inthis example, four customers were created.
0 commit comments