Wiki source code of WebserviceCOM
Version 12.1 by Assala Chmiti on 2022/11/04 15:54
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | = __**Definition:**__ = | ||
| 2 | |||
| 3 | Webservice is a connector used to send data with other web applications. | ||
| 4 | |||
| 5 | = __**Icon:**__ = | ||
| 6 | |||
| 7 | |||
| 8 | [[image:1667487132740-653.png]] | ||
| 9 | |||
| 10 | = __**Configuration:**__ = | ||
| 11 | |||
| 12 | There is 2 parts in configuring of the webservice connector: | ||
| 13 | |||
| 14 | * ((( | ||
| 15 | ===== **Configuring the Webservice in the ConfigurationCOM menu:** ===== | ||
| 16 | ))) | ||
| 17 | |||
| 18 | [[image:1667487261988-482.png]] | ||
| 19 | |||
| 20 | |||
| 21 | In order to use the Webservice, you have first to configure it in the ConfigurationCOM menu in the portal in the distant tab. This configuration is unique to the environment, and cannot be reused in another environment. | ||
| 22 | |||
| 23 | |||
| 24 | [[image:1667487553991-372.png]] | ||
| 25 | |||
| 26 | |||
| 27 | There are so many parameters to configure for the WebService connector: | ||
| 28 | |||
| 29 | ((( | ||
| 30 | * __**Name**__: The name of the distant Webservice used | ||
| 31 | * __**IP/host**__: The domain name of the servor or the IP address used | ||
| 32 | * __**URI**__: The path in the IP/host used to send the files | ||
| 33 | * __**Method**__: signifies the method used to get the data( GET, POST, PUT, DELETE) | ||
| 34 | * __**Port**__: The port of the listening | ||
| 35 | * __**Protocol**__: HTTP ou HTTPS | ||
| 36 | * __**Authentification Mode**__: There is 2 different ways for the authentification mode | ||
| 37 | |||
| 38 | 1. __**Basic**__: is a mode that needs 3 attributes(**header**: the header'name, **user **encoded in base64, **password **encoded in base64) | ||
| 39 | 1. __**Token**__: is a mode that consists on putting a token in the header. This mode uses 2 parameters: The **header** and the **token** is an encoded and encrypted data with a unique key using the HASHMAC algorithm. | ||
| 40 | |||
| 41 | * __**Timeout**__: is the max time acceptable to connect to the WS and get the result. | ||
| 42 | * __**Charset**__: is the encodage of the json file that will be sent to WS and of the result file | ||
| 43 | |||
| 44 | |||
| 45 | * ((( | ||
| 46 | ===== **Configuring the Webservice connector in the scenario:** ===== | ||
| 47 | ))) | ||
| 48 | |||
| 49 | Second, you have to configure the connector in the Scenario menu. | ||
| 50 | |||
| 51 | [[image:1667492134946-717.png]] | ||
| 52 | |||
| 53 | |||
| 54 | For this configuration, you have to fill these parameters: | ||
| 55 | |||
| 56 | * __**Destinataire**__: The environment where the distant configuration exists | ||
| 57 | * __**Config**__: The name of the distant configuration in the chosen environment | ||
| 58 | * __**Dyn.enveloppe**__: is a Yes or No value that mentions if the enveloppe is dynamic | ||
| 59 | * __**Enveloppe**__:if the enveloppe is not dynamic, this parameter is for uploading the file of the enveloppe or the connector's name that contains the file for the enveloppe. | ||
| 60 | * __**Data**__:the connector's name ythat contains the data | ||
| 61 | * __**Output FileName**__: The output file name | ||
| 62 | |||
| 63 | |||
| 64 | ==== __**Elements of the WS:**__ ==== | ||
| 65 | |||
| 66 | * ((( | ||
| 67 | ====== __**The enveloppe:**__ ====== | ||
| 68 | ))) | ||
| 69 | ))) | ||
| 70 | |||
| 71 |