  |
|
 |
|
 |
|||
| |||||||||||
|
|
When the NTpage Server starts it connects to the database and information is read from the ntpserve system table. The NTPAGE.LIC file is read and decrypted. Licensing information is checked. The TCP/IP thread is started (if applicable). The Named Pipes thread is started (if applicable). The TCP/IP or Named Pipes thread handles all the communications from the client. You may use the NTpage programmers API to talk directly to the server through these threads. These threads can handle multiple concurrent connections from client applications. It is designed to handle a large volume of concurrent client requests. These communications threads process specific transactions and provide reply's. For more information, please see the programming interface section. When a client request comes in, the server interacts with the queue database and updates it appropriately and triggers any necessary events. The queue table is reset in case there were any pending entries since the last shutdown. The port table is then loaded. For each TAP port, a TAP thread is started. For each TNPP port, a TNPP port is started. A single thread for the SMTP mail interface is also started (if applicable). The main thread waits for a shutdown event. In the event of shutdown, all created threads are gracefully stopped. The TAP and TNPP threads handle the bulk of the modem pooling and concurrency issues. We will describe these threads in a bit more detail. There is a thread created for each port. Depending on the database, a port may be assigned to a specific paging service, or it may be part of a pool. It can be defined as dial-up resource, leased line resource, or a dial-once stay connected resource. The behavior of the port depends on the definition. When a new message comes into the system, events are fired to wake up the protocol threads (TAP or TNPP). The threads are safe from each other using locking techniques. The queue is read and any message of type new is retrieved. Delayed messages are not selected. If new messages have all been serviced, then waiting messages past the delay time are selected. Messages are gathered together by paging services. The thread reads paging service information and user information. Each message is marked as processing and assigned to the thread. The number is dialed or connected. The messages are batched and sent on to the paging service. The queue table is updated with the status success or failure. By paging service, you can also define how many messages to batch before sending the messages. These threads handle this as well. These threads specially handle sending of numbers to numeric pagers. Each message can be routed to just e-mail, just pagers, or both. The routing is processed in these threads. NOTE: Please see the E-mail section for information on ERROR PROCESSING. |
|
