LightWave Client FAQ

LightWave Client allows applications running on NonStop servers to securely access REST (http://blog.ticsoftware.com/index.php/what-is-rest-web-service/)Web services anywhere, on any platform or operating system

Your NonStop application simply sends a formatted interprocess message to the LightWave Client Process which handles all of the details of mapping the IPM elements to a JSON or XML message, exchanging the message with the Web service provider, and parsing the JSON or XML response into the reply IPM. The LightWave CLIENT process hides the complexity of the TCP/IP, HTTP, SSL/TLS, JSON, and XML protocols required to access REST Web services. https://static.wixstatic.com/media/undefined

LightWave Client was designed to be fully scalable using NonStop Pathway. The CLIENT process is multi-threaded and can process multiple simultaneous requests. CLIENT can also be configured as a Pathway serverclass, allowing it to scale to match demand like any other Pathway server.

LightWave Client can be used to develop any number of applications using a NonStop Server application, for example: • Use services provided by business partners to check inventory, place orders, obtain delivery schedules, etc. • Integrate NonStop applications with ERP or CRM systems • Access real-time securities pricing, currency exchange rates, and other time-sensitive data • Incorporate centralized authentication and authorization services

LightWave Client consists of two major component processes: Console and Client. Console The role of the Console process is to support the administrative and management user interface for LightWave Client. Console provides a browser interface which allows you to: • View Console status • Manage APIs • View Client diagnostic logs • View Console HTTP logs • Manage SSL/TLS Server Certificates (for Console) • Manage LightWave Client users and groups (for access to Console) Once the Console process has been started, you access the LightWave Console application using your web browser. Client The role of Client is to provide the runtime implementation of a LightWave Client service you defined earlier using Console. Although you can run one or more client processes for a given service (e.g., for load balancing), each instance of the Client process supports exactly one service. The Client process accepts an interprocess message on $RECEIVE from a client application, which it transforms into a REST web-API request and forwards to a service endpoint using HTTP over TCP/IP. When the service responds, Client transforms the response into an interprocess message which it REPLYs to the original client requester application. Each Client process is capable of supporting simultaneous requests from multiple client applications. https://static.wixstatic.com/media/undefined

LightWave provides security features to ensure that your applications and NonStop Server remain secure. Transport Security LightWave Client uses OpenSSL to provide transport security using the latest version of TLS. Client applications can take advantage of this feature by configuring the Client process' base Url parameter to use the HTTPS protocol. User Authentication LightWave Client supports HTTP Basic/Digest authentication and SSL mutual authentication with web service endpoints.

No. LightWave Client(TM) runs in the Guardian environment and can connect to applications that run in both Guardian and OSS.