LightWave Server FAQ

LightWave Server is client-server middleware that provides the bridge between client components which may be running on any platform, and server components running on HP NonStop Servers.

LightWave Server was designed to be fully scalable using the Supervisor-Worker pattern. A LightWave Server instance consists of a LightWave Server SERVER process pair and optionally one or more LightWave Server SWORKER processes. The SERVER process listens on the instance's configured TCP/IP ports, hosts the LightWave Server Console, and services new connection request from API clients. If no SWORKER processes have been configured, the Server process will also perform API request processing. Any number of LightWave Server instances may be running on a single system, as long as they are configured to use different TCP/IP ports. As application load increases, SWORKER processes may be started and attached to a SERVER process. When SWORKER processes are attached, the SERVER process will delegate new connections to the SWORKER processes in round-robin fashion. Any number of SWORKER processes may be started in any CPU, providing adequate capacity for any application. https://static.wixstatic.com/media/undefined

Client applications communicate with the LightWave Server process, which runs on HP NonStop Server under Guardian, using a TCP/IP socket connection and the HTTP protocol. Although this may sound complicated, it's the same mechanism used by web browsers to connect to web servers, and the same mechanism used by thousands of web and mobile based applications to connect to their associated back-end servers. This mechanism is simple, well understood by developers, and is used billions of times per day to connect web and mobile clients to services like Google, Facebook, and Twitter. The goal of LightWave Server is to make it as simple to connect a client to a NonStop Server application as it is to connect a client to any of these other well known services. https://static.wixstatic.com/media/undefined

LightWave Server can be used to develop any number of applications using a NonStop Server back end, for example: • Modernize SCOBOL "green screen" applications by developing new browser based user interfaces that use LightWave Server to communicate with the existing Pathway servers. • Develop a mobile application for sales reps that provides order entry and status information using LightWave Server to communicate with an existing NonStop Server order processing systems. • Provide business partners with access to existing or new NonStop Server applications through a simple RESTful API. • Replace file upload or download applications that currently use FTP protocol with equivalent functionality using the HTTP protocol.

User-defined APIs User-defined APIs are a powerful feature of LightWave Server that allow you to design your own RESTful interface to your NonStop Server applications. With a user-defined API, you dictate the form of the URI and the query parameters and HTTP headers your API will use. You can map those elements to fields in the interprocess message which is sent to your application server. Likewise, you can define how replies from the server are mapped to the response that your API client receives. User-defined APIs allow you to hide the details of your server interface from users of your API. Native APIs LightWave Server also support a set of predefined native APIs that provide raw access to underlying NonStop Kernel resource. These APIs are used in conjunction with User-defined APIs. The following native APIs are provided: • Dialog API - Manage Pathway serverclass dialogs • Transaction API - Begin, end, and abort TMF transactions. These transactions may also be used with other APIs to enlist those operations in a transaction.

LightWave Server provides a number of built in security features to ensure that your applications and NonStop Server remain secure. Transport Security LightWave Server uses OpenSSL (https://www.openssl.org/)to provide transport security using the latest version of TLS. Client applications can take advantage of this feature by simply invoking API requests using the HTTPS protocol. User Authentication LightWave Server maintains its own User and Group identity store which is managed from the LightWave Server Management Console. API clients authenticate with LightWave Server using standard HTTP Basic or Digest authentication. Rules Based Access Control Access to API services is controlled using the configuration and application of Access Control Policies. Policies can be configured to restrict API service access to specific users, groups, or client source IP addresses. Network Isolation Although not a specific feature of LightWave Server, because LightWave Server uses the HTTP protocol, it's possible to use any number of web-application network isolation techniques to isolate your NonStop Server network from client application networks. For example, if your NonStop Server is providing back end services for a mobile Intenet application, you can isolate your NonStop Server network from the Internet using a secure HTTP proxy.

No. LightWave Server runs in the Guardian environment and can connect to applications that run in both Guardian and OSS.