Show Table of Contents
21.4. HTTP Invoker
The HTTP Invoker is a service that provides HTTP and Remote Method Invocation (RMI) access for EJBs and the JNDI Naming service. It is secured by the
jmx-console security domain. The instructions in Task: Create jmx-console, admin-console, and http invoker user account will allow access to it.
Task: Allow access to the HTTP Invoker from remote hosts
To allow access on the the hostName myservice.example.com, add a
hostName property to invoker you wish to use; Pooled or non-Pooled. Be aware that myservice.example.com must resolve to an IP Address served by this machine.
Procedure 21.2.
- Choose the appropriate bean from the options below and copy it in your invoker:
<!-- RMI/JRMP invoker --> <bean class="org.jboss.services.binding.ServiceBindingMetadata"> <property name="serviceName">jboss:service=invoker,type=jrmp</property> <property name="port">4444</property> <property name="description">Socket for the legacy RMI/JRMP invoker</property> <property name="hostName">myservice.example.com</property> </bean>
<!-- Pooled invoker --> <bean class="org.jboss.services.binding.ServiceBindingMetadata"> <property name="serviceName">jboss:service=invoker,type=pooled</property> <property name="port">4445</property> <property name="description">Socket for the legacy Pooled invoker</property> <property name="hostName">myservice.example.com</property> </bean>
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.