LinQ2 P-Series Database Integration Channel

LinQ2 P-Series Database Integration Channel

Data base Integration

1.1 Introduction

LinQ2 application has a database monitor component to pull messages from database other then linQ2 database. LinQ2 database monitor can pull message information from the database table and send it to appropriate recipients.

 

1.2 Configuration

Authorized user can configure database parameters from configuration >LinQ2 resources > database- add> page. Form this page authorized user can make settings for database host, driver, URL, user and password etc.

Ref: - Screen 6 – LinQ2 add database Resources Configuration.

Screen 7 – LinQ2 database Resources Configuration.

 

 

 Screen 6 – LinQ2 add database Resources Configuration.

 

 

Screen 7 – LinQ2 database Resources Configuration

 

 

1.2.1 Configuration parameter description

Backend Object Name           Name of the backend object.

Host                                      - IP address of database server

Driver                                    - Name of the driver.

Url                                         - Connection Url to database with database name

User name                             - Name of the database user

Password                               - Password for this user

Table name                            - Name of the table to monitor by linq2 db monitor.

Record count                         - Number of Record can processed in one time.    

Pooling interval                      -Time duration between two monitoring iterations.

 

1.3 Structure

Typical remote database fields will look like this: -
 

Field

Description

UNIQUE_ID

 

Message index.

 

APPLN_ID

 

Application id (application name should be configured in Enumeration interface). 

 

SMS_RECIPIENT

 

Recipient’s mobile number.

 

SMS_LANGUAGE

Indicates language of the message. The possible values for SMS_LANGUAGE are:

 (0) for English Message and 

 (1) for Arabic Message

Based on type, appropriate field should be looked for to receive the message.

 

SMS_TYPE

This field will be used to identify, if the message coming from Database is a template message or normal message.

0 – Normal Message

1 - Template message

SMS_STATUS

 

This field indicates the status of a message. During the process a message goes through following statuses:

(0) Message is newly put in the database and should be picked up for sending (New).

(1) Message is picked up by LinQ2 and the SMS_PICKUPDATE field has been updated (Processed).

(2)     Message is expired (SMS_TIMEANDDATE + VALIDITY_TIME < current time)

(3)  Message is invalid current time

SMS_MESSAGE

 

Message text

 

PRIORITY_LEVEL

 

Every message is sent with a priority indicator. The messages with high priority are sent with higher number in the PRIORITY_LEVEL field. LinQ2 picks up messages based on their priority and also maintains priority internally between database messages and bulk messages.

 

SCHEDULED_DATE

 

The system shall schedule the delivery of message by the time specified by this field of the message table. The message shall be delivered to customer on this time only. LinQ2 will pick up the messages directly, and then the scheduling will be handled by LinQ2 internally.

 

CONFIRM_REQD

 

The delivery confirmation is indicated by the CONFIRM_REQD field of the message table. If delivery confirmation is requested, system will capture the details of message delivery to the customer. This functionality will be supported only if the delivery confirmation is send by the STC for SMPP messages.

 

Values:

0: No SMSC Delivery Receipt requested (default) 

1: SMSC Delivery Receipt requested for delivery success or failure 

2: SMSC Delivery Receipt requested for delivery failure 

 

VALIDITY_TIME

 

This field indicates till how much time messages are valid. It is specified in seconds. Only messages for which (SMS_TIMEANDDATE +VALIDITY_TIME > current time) will be processed, other messages will be marked as expired.

(86400) valid for one day 24 hours

 

SMS_TIMEANDDATE

 

This field indicates originating time of messages.

 

SMS_PICKUPDATE

 

This field indicates the time of picking up a message by LinQ2 from the table.

PROVIDER_ID

Provider id

SMS_AUTHOR

Sender ID



1.4 Monitoring and Control 

1.4.1 Overview 

Default Database Handler service is available in services list. Authorized user can login in to LinQ2 system and can monitor the current status of Default Database Handler service and recent errors and warning from status monitor section. User can also start and stop the Default Database Handler service from this section.

 Ref: - Screen 8 – LinQ2 database handler

 Ref: - Screen 9 – LinQ2 database Handler Error monitoring

 

Screen 8 – LinQ2 database handler

 

 

Screen 9 – LinQ2 database Handler Error monitoring

 

 

1.4.2 Before You Apply Test

For samples and full structure details of LinQ2 XML format please take a look at “LINQ2 XML STRUCTURE” document.

 

1.5 Test Cases

1.5.1 Test1 – message content set directory in SMS_MESSAGE field

 

Test-1

 Content of message is entered

Interface

 

Pre-conditions

  • If new record is inserted in table which default database monitoring for  (from other backend)

 

query

The fields in table  which default database monitoring for should be fill as the following value:-

UNIQUE_ID:  1

SMS_STATUS:  0

APPLN_ID: 1

SMS_RECIPIENT: 9988776655

SMS_TYPE: 0

SMS_MESSAGE: Dear customer your account is 12223177832772

PRIORITY_LEVEL: 0

SCHEDULED_DATE: 

CONFIRM_REQD: 0

SMS_AUTHOR: 1

VALIDITY_TIME: 99999999

SMS_TIMEANDDATE: 8/6/2008 12:00:00 AM

SMS_PICKUPDATE: 

ORG_ID:  1

SMS_LANGUAGE: 0

PROVIDER_ID: 1

Expected Result

  • Message will be sent and will be showing in message report
  • The original record in table which database monitoring for

Will updated which SMS_STATUS will be set 1

And SMS_PICKUPDATE will fill with current date

 

Actual Result

 

 

 

 

 

 

 

1.5.2 Test 2- message content template and parameter in xml format 

 

Test-2

Extract template name and his parameter from xml content 

Interface

 

Pre-conditions

  • If new record is inserted in table which default database monitoring for  (from other backend)
  • You should create tow templates  name(ACCOUNT_OPENED_TPL)

One Arabic and onother English 

  • This template must be have tow parameter one  should be named (custName)

Another  should be named (accountNumber)

Request

1-The fields in table  which default database monitoring for should be fill as the following value:-

UNIQUE_ID:  1

SMS_STATUS:  0

APPLN_ID: 1

SMS_RECIPIENT: 9988776655

SMS_TYPE: 1

SMS_MESSAGE: Check doc LinQ2 XML Structure Description for samples.

 

PRIORITY_LEVEL: 0

SCHEDULED_DATE: 

CONFIRM_REQD: 0

SMS_AUTHOR: 1

VALIDITY_TIME: 99999999

SMS_TIMEANDDATE: 8/6/2008 12:00:00 AM

SMS_PICKUPDATE: 

ORG_ID:  1

SMS_LANGUAGE: 1

PROVIDER_ID: 1

Expected Result

  • Message will be sent and will be showing in message report.

The actual message is the specific template which take his parameter from xml format 

  • The original record in table which database monitoring for

Will updated which SMS_STATUS will be set 1

And SMS_PICKUPDATE will fill with current date

Actual Result

 

 

 

1.5.3 Test 3- Arabic message

 

Test-3

Extract message and his parameter from xml content 

Interface

 

Pre-conditions

  • If new record is inserted in table which default database monitoring for  (from other backend)

 

Request

1-The fields in table  which default database monitoring for should be fill as the following value:-

UNIQUE_ID:  1

SMS_STATUS:  0

APPLN_ID: null

SMS_RECIPIENT: null

SMS_TYPE: 4

SMS_MESSAGE: Check doc LinQ2 XML Structure Description for samples.

 

PRIORITY_LEVEL: 1

SCHEDULED_DATE: 

CONFIRM_REQD: 0

SMS_AUTHOR: 1

VALIDITY_TIME: 99999999

SMS_TIMEANDDATE: 8/6/2008 12:00:00 AM

SMS_PICKUPDATE: 

ORG_ID:  null

SMS_LANGUAGE: default

PROVIDER_ID: null

 

Expected Result

  • Message will be sent and will be showing in message report.
  • The original record in table which database monitoring for

Will updated which SMS_STATUS will be set 1

And SMS_PICKUPDATE will fill with current date

Actual Result

 

 

 

 

 

1.5.4 Test 4- Unicode message

Test-4

Extract message and his parameter from xml content 

Interface

 

Pre-conditions

  • If new record is inserted in table which default database monitoring for  (from other backend)

 

Request

1-The fields in table  which default database monitoring for should be fill as the following value:-

UNIQUE_ID:  1

SMS_STATUS:  0

APPLN_ID: null

SMS_RECIPIENT: null

SMS_TYPE: 3

SMS_MESSAGE: Check doc LinQ2 XML Structure Description for samples.

 

PRIORITY_LEVEL: 0

SCHEDULED_DATE: 

CONFIRM_REQD: 0

SMS_AUTHOR: 1

VALIDITY_TIME: 99999999

SMS_TIMEANDDATE: 8/6/2008 12:00:00 AM

SMS_PICKUPDATE: 

ORG_ID:  null

SMS_LANGUAGE: default

PROVIDER_ID: null

 

Expected Result

  • Message will be sent and will be showing in message report.
  • The original record in table which database monitoring for

Will updated which SMS_STATUS will be set 1

And SMS_PICKUPDATE will fill with current date

Actual Result

 

 

 

 

© 2024 Cerebra All Copyrights Reserved

    • Related Articles

    • LinQ2 P-Series Push Notifications Integration Channel v1.1

      Push Notification Integration 1.1 Introduction Linq2 is integrated with Push Providers (PushWoosh/OneSignal/Google FCM) by using following approach. Push notification can be requested in the XML or Rest request by MQ or WebService integration ...

    • LinQ2 P-Series Voice Integration Channel v1.0

      Voice Integration Introduction Now Linq2 P Series supports automated voice calling feature through standard SIP providers e.g. FreePBX. Linq2 P Series is integrated with SIP Providers by using the following approach/steps. Configure SIP account ...

    • LinQ2 P-Series Xml File Integration Channel

      XML File Integration 1.1 Introduction This interface allows sending requests to LinQ2 through xml file saved in UTF 8 format. Linq2 application will read this file from already defined source directory. In case of successful processing this file will ...

    • Release Note - Voice Module [P-Series - V 4.1.0] - Internal

      LinQ2 P-Series Voice Release Notes This release contains Voice module & integration in LinQ2 P-Series: Introduction: Now Linq2 P Series supports automated voice calling feature through standard SIP providers e.g. FreePBX. Linq2 P Series is integrated ...

    • LinQ2 P-Series Excel File Integration Channel and Test Cases

      1. Introduction This interface allows sending requests to LinQ2 through Excel file either “.xls” or “.xslx” formats. Linq2 application will read this file from already defined source directory .In case of successful processing this file will be move ...