diff --git a/en/docs/assets/img/integrate/connectors/copy-libs-via-vscode.png b/en/docs/assets/img/integrate/connectors/copy-libs-via-vscode.png new file mode 100644 index 000000000..2b1b20840 Binary files /dev/null and b/en/docs/assets/img/integrate/connectors/copy-libs-via-vscode.png differ diff --git a/en/docs/assets/img/integrate/connectors/smpp-config-endpoint-1.png b/en/docs/assets/img/integrate/connectors/smpp-config-endpoint-1.png index a1b152ae9..629ca9037 100644 Binary files a/en/docs/assets/img/integrate/connectors/smpp-config-endpoint-1.png and b/en/docs/assets/img/integrate/connectors/smpp-config-endpoint-1.png differ diff --git a/en/docs/assets/img/integrate/connectors/smpp-create-new-inbound-endpoint.png b/en/docs/assets/img/integrate/connectors/smpp-create-new-inbound-endpoint.png index 2b61d2bdf..8b068b443 100644 Binary files a/en/docs/assets/img/integrate/connectors/smpp-create-new-inbound-endpoint.png and b/en/docs/assets/img/integrate/connectors/smpp-create-new-inbound-endpoint.png differ diff --git a/en/docs/assets/img/integrate/connectors/smpp-injecting-and-error-sequence.png b/en/docs/assets/img/integrate/connectors/smpp-injecting-and-error-sequence.png new file mode 100644 index 000000000..ccca21780 Binary files /dev/null and b/en/docs/assets/img/integrate/connectors/smpp-injecting-and-error-sequence.png differ diff --git a/en/docs/reference/connectors/smpp-connector/smpp-inbound-endpoint-example.md b/en/docs/reference/connectors/smpp-connector/smpp-inbound-endpoint-example.md index 45cca45a2..77cafd456 100644 --- a/en/docs/reference/connectors/smpp-connector/smpp-inbound-endpoint-example.md +++ b/en/docs/reference/connectors/smpp-connector/smpp-inbound-endpoint-example.md @@ -18,72 +18,80 @@ The following diagram shows the overall solution we are going to build. The SMSC 2. Create a sequence to process the message. In this example, we will just log the message for simplicity, but in a real-world use case, this can be any message mediation. - ```xml - - - - - - - - - - - - - ``` -3. Click `+` button next to `Inbound Endpoints` and select `Custom` to add a new **custom inbound endpoint**. - Creating custom inbound endpoint -
-4. Configure the custom inbound endpoint as shown below and click `Create`. - Configure custom inbound endpoint 1 - Configure custom inbound endpoint 2 - - The source view of the created inbound endpoint is shown below. - ```xml - - - - eventBased - true - true - 2775 - UNKNOWN - localhost - 3000 - UNKNOWN - CPT - -1 - BIND_RX - null - kasun - kasun - 5 - 10000 - - - ``` + ```xml + + + + + + + + + + + + + ``` -> **Note**: To configure the `systemId` and `password` parameter value, please use the steps given under the topic `Configure the SMSC (Short Message Service Center) simulator` in the [Setting up the SMPP Connector ]({{base_path}}/reference/connectors/smpp-connector/smpp-connector-configuration/) documentation. -> - **systemId** : username to access the SMSC -> - **password** : password to access the SMSC +3. Click `+` button next to `Inbound Endpoints` and select `SMPP` to add a new **SMPP inbound endpoint**. + + Creating smpp inbound endpoint +
+ +4. Configure the SMPP inbound endpoint as shown below and click `Create`. + + Configure SMPP inbound endpoint 1 +
+ + !!! Note + When creating the SMPP inbound endpoint you have two options in defining the injecting sequence and error sequence. +
- **Automatic** : Click the checkbox *Automatically generate sequence* +
- **Manual** : You can select already defined sequences as injecting and error sequences. + + Configure SMPP inbound endpoint Injecting and Error Sequences + + The source view of the created inbound endpoint is shown below. + + ```xml + + + + eventBased + true + true + localhost + 2775 + pavel + wpsd + BIND_RX + UNKNOWN + UNKNOWN + 10000 + 200 + 1000 + 3 + 5 + 10000 + + + ``` + +!!! Note + To configure the `systemId` and `password` parameter value, please use the steps given under the topic `Configure the SMSC (Short Message Service Center) simulator` in the [Setting up the SMPP Connector ]({{base_path}}/reference/connectors/smpp-connector/smpp-connector-configuration/) documentation. +
- **systemId** : username to access the SMSC +
- **password** : password to access the SMSC ## Export integration logic as a CApp @@ -105,7 +113,12 @@ You can download the ZIP file and extract the contents to get the project code. 1. Navigate to the [connector store](https://store.wso2.com/store/assets/esbconnector/list) and search for `SMPP Connector`. Click on `SMPP Inbound Endpoint` and download the .jar file by clicking on `Download Inbound Endpoint`. Copy this .jar file into **PRODUCT-HOME/lib** folder. 2. Download [jsmpp-2.1.0-RELEASE.jar](https://mvnrepository.com/artifact/com.googlecode.jsmpp/jsmpp/2.1.0-RELEASE) and [asyncretry-jdk7-0.0.6.jar](https://mvnrepository.com/artifact/com.nurkiewicz.asyncretry/asyncretry-jdk7/0.0.6) copy inside **PRODUCT-HOME/lib** folder. - + + !!! Tip + Alternatively for deployment step 1 and 2, MI for VS Code has provided the capability of copying jars to **PRODUCT-HOME/lib** folder while exporting the capp. You can copy necessary jars to **deployment/libs** folder under project explorer view. + + Copy libs with VS Code + 3. Copy the exported carbon application to the **PRODUCT-HOME/repository/deployment/server/carbonapps** folder. 4. [Start the integration server]({{base_path}}/get-started/quick-start-guide/#start-the-micro-integrator).