Search Tips   |   Advanced Search



Extending IHS functionality with third-party plug-in modules

This section contains topics on using third-party plug-in modules with IBM HTTP Server.


Before you begin

Modules that are loaded into IHS, whether distributed by IBM or a third-party vendor, must comply with the following specifications:

You can build third-party plug-in modules (dynamic shared object modules) for execution with IHS. IHS ships as an installation image with executables that you cannot rebuild because the source does not ship with the installation image. However, IHS 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 IHS 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.



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

AIX: HP-UX: Linux: Solaris: z/OS: Build method options for dynamic modules

Windows: Considerations for building dynamic modules on Windows platforms