www.ironjacamar.orgCommunity Documentation
Table of Contents
The IronJacamar container is started by entering the bin/ directory
cd ironjacamar-1.2.0.Final/bin
and executing
./run.sh
on a Un*x based system or
run.bat
on Windows.
The command takes an optional -b argument to define the binding address of the naming server
./run.sh -b 192.168.0.199
Once the container has started you should see a log entry like
13:33:10,999 INFO [Main] Server started in 941ms
in the console where the command was executed.
After the container has started you can browse to
http://localhost:8080
to view the project documentation and use the administration console.
The IronJacamar container is stopped by pressing the Ctrl-C keys.
Once the container has stopped you should see a log entry like
13:35:06,752 INFO [Main] Server stopped in 29ms
in the console where the container was running.
Alternative the container can be stopped through the command line interface.
The IronJacamar container can be controlled by a command line interface.
If you are accessing a remote container you can use the -h option to
specify the host name.
You can deploy a resource adapter archive (.rar) using
java -jar fungal-cli.jar deploy <file>
where file specifies the resource adapter archive.
You can undeploy a resource adapter archive (.rar) using
java -jar fungal-cli.jar undeploy <file>
where file specifies the resource adapter archive.
The IronJacamar container can be controlled by Apache Ant tasks.
The IronJacamar container can be started by the Apache Ant task org.jboss.jca.sjc.ant.Start which takes a
home attribute to specify the home directory of the installation.
The IronJacamar container can be stopped by the Apache Ant task org.jboss.jca.sjc.ant.Stop which takes a
home attribute to specify the home directory of the installation.
Deployments to the IronJacamar container can be done by the Apache Ant task org.jboss.jca.sjc.ant.Deploy which takes a
file attribute to specify the file that should be deployed. The task takes optional host and port
attributes in order to specify the host and port where the IronJacamar container is located.
Undeploying from the IronJacamar container can be done by the Apache Ant task org.jboss.jca.sjc.ant.Undeploy which takes a
file attribute to specify the file that should be undeployed. The task takes optional host and port
attributes in order to specify the host and port where the IronJacamar container is located.
The IronJacamar container can be controlled by Apache Maven mojos.
The IronJacamar container can be started by the Apache Maven mojo org.jboss.jca.sjc.maven.Start which takes a
home element to specify the home directory of the installation.
The IronJacamar container can be stopped by the Apache Maven mojo org.jboss.jca.sjc.maven.Stop which takes a
home element to specify the home directory of the installation.
Deployments to the IronJacamar container can be done by the Apache Maven mojo org.jboss.jca.sjc.maven.Deploy which takes a
file element to specify the file that should be deployed. The mojo takes optional host and port
elements in order to specify the host and port where the IronJacamar container is located.
Undeploying from the IronJacamar container can be done by the Apache Maven mojo org.jboss.jca.sjc.maven.Undeploy which takes a
file element to specify the file that should be undeployed. The mojo takes optional host and port
elements in order to specify the host and port where the IronJacamar container is located.