7.6. Configuring a Remote Service Invoker
You do not need to configure anything to use the ServiceInvoker from within ESB actions: it will work "out of the box." However, to use it from a remote JVM, such as from a standalone Java application, a servlet or an EJB, you will need to make the following JAR files available:
commons-codec-1.3.jar |
commons-collections.jar |
commons-configuration-1.5.jar |
commons-lang-2.4.jar |
commons-logging.jar |
concurrent.jar |
hornetq-core-client.jar |
hornetq-jms.jar |
javassist.jar |
jboss-aop-client.jar |
jboss-common-core.jar |
jboss-javaee.jar |
jboss-logging-spi.jar |
jboss-mdr.jar |
jboss-remoting.jar |
jbossall-client.jar |
jbossesb-config-model-1.0.1.jar |
jbossesb-config-model-1.1.0.jar |
jbossesb-config-model-1.2.0.jar |
jbossesb-config-model-1.3.0.jar |
jbossesb-config-model-1.3.1.jar |
jbossesb-registry.jar |
jbossesb-rosetta.jar |
jbossjmx-ant.jar |
jbossts-common.jar |
juddi-client-3.1.3.jar |
log4j.jar |
netty.jar |
scout-1.2.6.jar |
serializer.jar |
trove.jar |
uddi-ws-3.1.3.jar |
Note
These files are found in the
$SOA_HOME/jboss-as/client/, $SOA_HOME/jboss-as/common/lib/ and $SOA_HOME/jboss-as/server/$SOA_CONF/deployers/esb.deployer/lib/ directories.
The following configuration file is also required to be available on the classpath:
jbossesb-properties.xmlMETA-INF/uddi.xml
