Skip to main content
Skip table of contents

SOAPam Server Compatibility in LightWave Server

As you review the documentation and explore the software, please keep the following in mind:

  • Alpha Stage: This is an alpha release, which means it's an early version that's likely to undergo significant changes. The product is still in development, and some features may be incomplete or subject to revision.

  • Dynamic Documentation and Code: The documentation and code you're accessing are part of a work in progress. They are subject to frequent updates as we refine and expand the product. We recommend checking back regularly for the latest information.

  • Your Input Matters: As an alpha tester, your feedback is invaluable to us. We welcome your insights on bugs, usability, and any suggestions for improvement. Your input will be instrumental in shaping the final product.

  • Forward-Looking Development: We are committed to evolving and enhancing this product. As part of this journey, we appreciate your understanding and patience with the iterative nature of an alpha release.

Thank you for participating in this early stage of our product's development. We are looking forward to quickly advancing to the next phase of release, and your involvement is essential for our success. If you have problems, questions, or suggestions, please send them to support@nuwavetech.com.

Preview Documentation

These pages describe the SOAPam Compatibility feature in LightWave Server and will ultimately be integrated into the LightWave Server documentation.

Software Download

Release Notes

1.2.0-alpha.2 - 15 May 2024

What’s Available

  • Import of Service Definition Files (SDFs) into LightWave Server using LWSCOM

  • Support for SOAP message exchange with services imported from SDFs.

  • Support for SOAPam Server compliant Server and Client Transaction Control.

  • Support for the SOAPam Server Transaction Control Service.

  • SOAPam Server compatible Process Statistics Collection.

  • SDF Initializers are now imported by the SDF import process.

  • The LightWave Control API Tester now supports SOAP requests.

What We're Working On

  • The API Editor has limited ability to edit API definitions imported from SDFs. In this release editing imported APIs should be avoided.

  • WSDL generation from an API definition is not yet supported.

  • IP Address restrictions for accessing the LightWave Server Console.

1.2.0-alpha.1 - 01 May 2024

What’s Available

  • Import of Service Definition Files (SDFs) into LightWave Server using LWSCOM

  • Support for SOAP message exchange with services imported from SDFs.

  • Support for SOAPam Server compliant Server and Client Transaction Control.

  • Support for the SOAPam Server Transaction Control Service.

  • SOAPam Server compatible Process Statistics Collection.

What We're Working On

  • SDF Initializers are not imported by the SDF import process.

  • The API Editor has limited ability to edit API definitions imported from SDFs. In this release editing imported APIs should be avoided.

  • WSDL generation from an API definition is not yet supported.

  • IP Address restrictions for accessing the LightWave Server Console.

  • The LightWave Control API Tester does not yet support SOAP requests. The Tester currently shows JSON messages for SOAPam compatible APIs.

What We’re Not Planning on Supporting

LightWave Server does not support the following SOAPam Server features:

  • Connection Security - SOAPam Server allowed services to be configured to require an SSL/TLS connection. This can be managed in LightWave Server using appropriate service port configuration. In addition, TLS connections for modern web services is the norm.

  • User Impersonation - SOAPam Server allowed services to be configured to invoke serverclass I/O while impersonating a specified Guardian user. We are not aware of any customers using this feature. This ability is currently on the LightWave Server roadmap.

If you have a need for these features, please contact NuWave support.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.