23.2 Deploying to the Servlet Execution Engine

To deploy to the servlet execution engine, simply start the HydraExpress Agent as usual. The rwsfserver script starts and stops the Agent and accepts a variety of options. On Windows systems, the installer places shortcuts to the scripts in the Start menu. In the installation, this script is located in your <installdir>\bin directory. For UNIX systems, run the script from the command line only.

The command below shows the sequence to stop and restart the Agent on both Windows and UNIX:

The HydraExpress Agent uses several default ports. The most common is 8090 used for HTTP requests and 8443 for HTTPS requests.

The generated makefile includes a deploy target to deploy the sample service and associated client. (See Chapter 22, "Options for Compiling," for more information on building your applications using the makefiles.) If you have compiled the service using MSVC on Windows, a deployment batch file is generated for your convenience. See Section 23.2.4.

To deploy the service, follow the steps in this section.

---

Make sure that you have set up your environment as described in Chapter 2, "Setup," in the Introduction to HydraExpress. On Windows, be sure you have set up your command window with the MSVC environment.

---

If the HydraExpress Agent is currently running, stop the container by running the rwsfserver stop command in the RWSF_HOME\bin directory, as shown below:

Run nmake (Windows) or make (UNIX or Linux) at the command prompt with the target deploy. The makefile deploys the service and client into your HydraExpress installation. The DLL or shared library for the service and client is placed in <installdir>\apps-bin on Windows and <installdir>/apps-lib on UNIX/Linux.

For example, the following command line builds the sample service and client library, and copies the web.xml service descriptor for the service into the apps\servlets directory beneath in your HydraExpress installation directory:

Restart the container to load the new service. To restart the container, run the rwsfserver start in the RWSF_HOME\bin directory, as shown below:

---

For MSVC projects, do not use nmake deploy. See Section 23.2.4.

---

For MSVC project files, you may run the deployment batch file generated in the top level code generation directory as a convenience: deployDebug.bat (for debug builds) or deployRelease.bat (for release builds). Do not use nmake deploy to deploy these projects.

The syntax of the rwsfserver script is: rwsfserver [options] [start|stop]. Options are:

• -? | -h | --help or no arguments, to display help

• -d | --debug, to start the HydraExpress Agent in debug mode (Windows only)

---

If you start the HydraExpress Agent in debug mode on Windows, it loads only services and named objects compiled in debug mode, as identified by the tag 15d in the file name.

---

The client request is automatically sent to the location defined in the WSDL file. To direct the client request to some other location, enter the location on the command line immediately after the client invocation. For example, to send the request using a secure transport to the Agent's SSL port, enter:

<prompt> MyClient https://localhost:8443/<path_to_service>

The HydraExpress examples located in your <installdir>\tutorials\webservices directory specify localhost:8090 as the service port in the WSDL file. Therefore, if you run one of the example clients without a specific path, the request is automatically routed to the default port.

© Copyright Rogue Wave Software, Inc. All Rights Reserved. All Rights Reserved. Rogue Wave is a registered trademark of Rogue Wave Software, Inc. in the United States and other countries. HydraExpress is a trademark of Rogue Wave Software, Inc. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.