Deploying the execute Interface Methods

The execute interface methods (located in the com/rdta/fc/facade/FlashConnect.class contained within fcss.jar file) must be deployed.

Preparing for Deployment, Preparing

Axis is a servlet that is run by a servlet server (for example, jrun or Apache Tomcat). Therefore, all class paths or shared library paths required by Axis must be set up before starting the servlet server. Any web applications deployed by Axis must be set up as well.

To prepare for deployment:

Add the location of the libFCServlet.so file (typically, /usr/lib/tigerlogic) to the UNIX LD_LIBRARY_PATH environment variable.
Add the fcss.jar file (contains the FlashConnect java interface) and any other jar files required by Axis to the CLASSPATH environment variable.
Ensure that the fcss.jar file is located in the Tomcat directory structure (required by Apache Tomcat servlet server).

Creating and Running a Deployment wsdd

Create a wsdd for deploying various handlers, chains, and services. There are two methods for accomplishing this:

java org.apache.axis.client.AdminClient deploy.wsdd after the Axis server is running.
java org.apache.axis.utils.Admin client|server deploy.wsdd from the same directory where the Axis engine runs.

The deploy method essentially informs the SOAP server that FlashConnect is available for connection.

To create and run the deployment wsdd:

Insert the wsdd code. For example:

<deployment name="FlashConnect" xmlns="http://xml.apache.org/axis/wsdd/"

xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">

</service>

</deployment>

Run the deployment. For example:

java org.apache.axis.client.AdminClient deploy.wsdd

NOTE

In case of failures, you may need to create and run a wsdd to undeploy the application. For example:

undeploy.wsdd

</undeployment>

java org.apache.axis.client.AdminClient undeploy.wsdd