A Multi-Protocol agent has common instrumentation that can be accessed through different protocols such as SNMP, TL1, HTML, CORBA, RMI, and HTTP. It is the HTTP Connector that exposes the agent information through HTTP Protocol.
This section has the following topics that discuss the various details pertaining to the HTTP Connector:
9.6.1 Creating Multi-Protocol agent with HTTP Connector
This topic leads you through the steps of registering a HTTP Connector to the Multi-Protocol agent. It also discusses how you can access and test the JMX Agent through the HTTP Connector.
9.6.2 Authentication in HTTP Connector
An option to authenticate the users, before allowing them to access the agent information using HTTP Connector, is available in AdventNet HTTP Connector. This topic describes the steps involved such as:
Enabling this feature.
Including new user names and passwords to the list of users.
Deleting user names from the list.
9.6.3 Using SSL for communication through HTTP Connector
Secure Sockets Layer (SSL) is supported in AdventNet HTTP Connector. This topic discusses the steps involved in configuring the various features required in enabling SSL support.
9.6.4 Plugging-in your own Web server
The AdventNet HTTP Connector uses Jetty Web server by default. But it is possible to plug in your own Web server too. This topic discusses the steps involved in plugging in your Web server.