Extend IBM HTTP Server functionality with third-party plug-in modules

+

Search Tips   |   Advanced Search

 

Overview

We can build third-party plug-in modules (dynamic shared object modules) for execution with IBM HTTP Server. IBM HTTP Server ships as an installation image with executables that we cannot rebuild because the source does not ship with the installation image. However, IBM HTTP Server does ship the header files necessary to compile and build third-party plug-in modules that execute as an IBM HTTP Server module.

The use of third-party plug-in modules does not prevent IBM HTTP Server from being supported, but IBM cannot support the third-party plug-in module itself. If a problem occurs when the third-party plug-in module is loaded, IBM support might ask for the problem to be reproduced without the third-party plug-in module loaded, in order to determine if the problem is specific to the configuration with the third-party plug-in module. If a problem is specific to the configuration with the third-party plug-in module, the provider of that module might need to help determine the cause of the problem. IBM cannot resolve such problems without the involvement of the provider of the module, as this requires understanding of the implementation of the module, particularly with regard to its use of the Apache APIs.

 

Procedure

• Identify viable compilers. Apache and third-party plug-in module testing incorporated the compilers and compiler levels that are listed in this topic.

• Determine the method to use to build the dynamic modules. Two common options for building dynamic modules are described in this topic.

• Considerations for building dynamic modules. Restrictions apply when building a module to run with IBM HTTP Server. This topic describes the restrictions.

---

 

Sub-topics

Viable compilers for Apache and third-party plug-in modules

Build method options for dynamic modules

Considerations for building dynamic modules on Windows platforms