The Oracle HTTP Server (OHS) introspector plug-in for the Oracle Virtual Assembly Builder (OVAB) plug-in introspects all the available Oracle HTTP Server instances in a WebLogic Server domain. This plug-in is an extension of WebLogic Server plug-in for OVAB.
This chapter contains the following sections:
This plug-in supports version 12.1.2.
The OHS Introspector plug-in for OVAB is an extension of WebLogic Server plug-in for OVAB, thus it works with the Introspector parameters provided for the WLS plug-in.
For the parameters required by WebLogic Server, see "Using the Introspection Plug-in for Oracle Virtual Assembly Builder," in Administering Server Environments for Oracle WebLogic Server.
Multiple scalable appliances, one per Oracle HTTP Server instance.
All of WebLogic Server requirements must be satisfied. For these requirements, see "Using the Introspection Plug-in for Oracle Virtual Assembly Builder," in Administering Server Environments for Oracle WebLogic Server.
In addition to the WebLogic Server requirements, reference system implementations require that WLS and Oracle HTTP Server be installed in the same ORACLE_HOME.
Inputs are created on the Oracle HTTP Server appliance for each Listen or Port directive found in the configuration. The protocol of an Oracle HTTP Server input is set to
http unless the
Listen directive is found inside a
VirtualHost directive and the directive
SSLEngine is set to on. In that case, the protocol is
Outputs on the Oracle HTTP Server appliance are created based on various directives related to Oracle WebLogic Server in the Oracle HTTP Server configuration. The outputs indicate which inputs on an Oracle WebLogic Server assembly to connect to through the output 'description'.
All instance appliance input endpoints have one editable property,
port, and two non-editable properties,
name and a list of
protocols indicate what sort of outputs can be connected to the input. An administration server appliance will always have one secure http listener input endpoint,
port, which is editable.
All output endpoints have three non-editable properties,
protocol indicates what sort of input can be connected to the output.
Singleton indicates what sort of appliance the output can be connected to. If
singleton is true, the output can only be connected to an input on an appliance that has a scalability absolute max value of 1. Administration Server appliance do not have output endpoints.
There are no relevant Oracle HTTP Server appliance properties.
The supported template type is Oracle Enterprise Linux (OEL).
Be aware of the following plug-in limitations:
Any changes done manually to Oracle HTTP Server instance(s) on the reference system without the administration interfaces will not be introspected by the plug-in.
On the reference implementation, the OVAB Oracle HTTP Server plug-in does not introspect Oracle HTTP Server standalone deployments. It only supports WebLogic Server Oracle HTTP Server deployments.
For more information on using OVAB, see the following documents: