To integrate a RAML service in Kony Fabric, a RAML file or Zip (with all dependent files) must be created, which defines all the API definitions and schemas with properties in the project. When a Kony Fabric user creates a service from Kony Fabric Console, the system retrieves metadata from a RAML file and displays all APIs of a RAML file.
Kony Fabric parses a RAML file and exposes all the endpoints through the integration service.
To configure RAML service in the Integration Service Definition tab, follow these steps:
Field | Property |
---|---|
Connection Parameters | Click Upload and select a RAML file from your local machine. The system adds your main RAML file to the console. The system displays the added RAML file's name under the Connection Parameters section. |
Authentication |
Select an identity provider from the list to link your service. |
Web Service Authentication |
Select one of the following modes:
|
Field | Description |
---|---|
Custom Code |
Custom Code enables you to specify dependent JAR. To specify dependent JAR, select the JAR containing preprocessor or postprocessor libraries from the drop-down list, or click Upload New to browse the JAR file from your local system. This step allows you to further filter the data sent to the back end. Important: Make sure that you upload a custom JAR file that is built on the same JDK version used for installing Kony Fabric Integration. |
Throttling |
API throttling enables you to limit the number of request calls within a minute. If an API exceeds the throttling limit, it will not return the service response.
Note: Enable API throttling in a clustered environment by configuring the KONY_SERVER_NUMBER_OF_NODES property in the server_configuration table available in Admin database. This property indicates the number of nodes configured in the cluster. The default value is 1. |
Note: All options in the Advanced section are optional.
To enable the proxy, select the Use proxy from settings check box. By default, the check box is cleared. The Use proxy from settings check box dims when no proxy is configured under the Settings > Proxy.
The Operations List tab appears only after the service definition is saved.
Note: Click Operations List tab > Configure Operation. The Configured Operations list appears.
To create an operation, follow these steps:
Field | Description |
---|---|
Name | It is prepopulated with the operation name. You can change the name if required. |
Operation Security Level |
It specifies how a client must authenticate to invoke this operation. Select one of the following security operations in the Operation Security Level field.
|
Field | Description |
---|---|
Custom Code Invocation - Preprocessor and Postprocessor (for Java and JavaScript) | You can add pre and post processing logic to services to modify the request inputs. When you test, the services details of various stages in the service execution are presented to you for better debugging. All options in the Advanced section are optional. For more details, refer to Preprocessor and Postprocessor. |
Properties |
Additional configuration properties (timeout, cachable, unescape embedded xml in response, response encoding, number of connection retries allows you to configure service call time out cache response |
Front End API | It allows you map your endpoint/back-end URL of an operation to a front-end URL. |
Server Events | Using Server Events you can configure this service to trigger or process server side events. For detailed information, refer Server Events. |
Note: All options in the Advanced section are optional.
Note: Input and Output must be defined in the RAML file only.
Field | Description |
---|---|
Name | It Contains a Unique Identifier. Change the name if required. |
Test Value | Enter a value. A test value is used for testing the service. |
Default Value | Enter the value, if required. The default value will be used if the test value is empty. |
Scope | Select Request or Session. It is set to Request by default.
|
Data Type | Select one of the following data types.
|
Record ID | Enter an ID. |
Description | Provide a suitable description. |
To validate the operation details, click Save and Test. For more details, refer to Test a Service Operation.
Note: If you define parameters inside a record as the session, the session scope will not get reflected for the parameters.
To validate the operation details, click Save and Test. For more details, refer to Test a Service Operation.
Click SAVE OPERATION.
Note: You can view the service in the Data Panel feature of Kony Visualizer. By using the Data Panel, you can link back-end data services to your application UI elements seamlessly with low-code to no code. For more information on Data Panel, click here.
Copyright © 2020 Kony, Inc. All rights reserved. |