web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Tools Overview Tools Overview Steps to build, deploy, and run the examples 1 Build. You can build all of the examples simultaneously or build each one individually. To build them all simultaneously, navigate to the: /examples/webservices/ directory and execute the Ant command. For example: C:/BDP/examples/webservices>Ant builds all the examples. To build an individual example, navigate to its specific directory and execute the Ant command. For example: C:/BDP/examples/webservices/java>Ant builds only the Java Provider example. 2 Deploy. You deploy the examples to a running instance of BES. You can use the ant deploy target, or any of the following to deploy your WAR and JAR: ■ ■ iastool command-line utility, for more information go to “iastool command-line utility” on page 293. Deployment Wizard, for more information go to the Management Console User's Guide. 3 Run. To run an example, navigate to its directory and use the ant run-client command. For example, to run the Java Provider client: C:/BDP/examples/webservices/java>Ant run-client Apache Axis Web Service samples The Apache Axis web service samples are already deployed in the axis-samples.war file present in the Borland Partition. Since these are already pre-deployed, you do not need to use the Apache Axis deploy commands suggested in the Apache Axis User's Guide. The Apache Axis User's Guide is also provided with the BES installation and is located in: /doc/axis/user-guide.html or refer to the Axis User Guide located in /doc/axis/user-guide.html. These samples illustrate the capabilities of Axis. They are unmodified from the original Apache Axis implementation and are not guaranteed to run. This section describes the various tools used in examples. Apache ANT tool The Apache ANT utility is a platform-independent, java-based build tool used to build the examples. The XML build script build.xml is used to drive the tool. This build.xml file describes the various targets available for a project and the commands executed in response to those targets. The Borland Enterprise Server conveniently provides all necessary JARs and scripts to run the Apache Ant tool. Chapter 9: Borland Enterprise Server Web Services 81
Tools Overview Java2WSDL tool Note The Java2WSDL is an Apache Axis utility class that generates WSDL corresponding to a Java class. This class can accept a number of command line arguments. You can get the full usage help by running this utility without arguments as follows: java org.apache.axis.wsdl.Java2WSDL You must set your CLASSPATH to include all jar files in the \lib\axis directory, before you run the following command. WSDL2Java tool Note The WSDL2Java is an Apache Axis utility class that generates Java classes from a WSDL file. This tool can generate java stubs (used on the client side), or java skeletons (used on the server side). The generated files make it easy to develop your client or server for a given WSDL. This class can accept a number of command line arguments. You can get the full usage help by running this utility without arguments as follows: java org.apache.axis.wsdl.WSDL2Java You must set your CLASSPATH to include all jar files in the \lib\axis directory, before you run the following command. Axis Admin tool Note The Apache Axis Admin tool is a utility class that generates WAR level global configuration files based on deployment information specific to some web services. The input to this utility is a XML file (typically named deploy.wsdd) containing deployment information about one or more web services. The Apache Axis Admin utility adds some global definitions that are necessary and writes an output file. Use this tool as follows: java org.apache.axis.utils.Admin server|client deployment-file You must set your CLASSPATH to include all jar files in the \lib\axis directory, before you run the command. This tool generates server-config.wsdd or client-config.wsdd based on what option you choose. 82 BES Developer’s Guide
- Page 41 and 42: Apache web server implementation Fo
- Page 43 and 44: Borland web container implementatio
- Page 45 and 46: Borland web container implementatio
- Page 47 and 48: Borland web container implementatio
- Page 49 and 50: Smart Agent implementation Smart Ag
- Page 51 and 52: 40 BES Developer’s Guide
- Page 53 and 54: Apache web server to Borland web co
- Page 55 and 56: Apache web server to Borland web co
- Page 57 and 58: Apache web server to Borland web co
- Page 59 and 60: Large data transfer Downloading lar
- Page 61 and 62: Large data transfer Uploading large
- Page 63 and 64: IIS web server to Borland web conta
- Page 65 and 66: IIS web server to Borland web conta
- Page 67 and 68: IIS web server to Borland web conta
- Page 69 and 70: Session management with JSS If an i
- Page 71 and 72: Managing and configuring the JSS Co
- Page 73 and 74: The Borland IIOP connector BES supp
- Page 75 and 76: Setting up your web container with
- Page 77 and 78: 66 BES Developer’s Guide
- Page 79 and 80: Web-enabling your CORBA server Impo
- Page 81 and 82: Configuring your Apache web server
- Page 83 and 84: Configuring your Apache web server
- Page 85 and 86: Web Services and Partitions ■ ■
- Page 87 and 88: Web Service providers Java:RPC prov
- Page 89 and 90: How Borland Web Services work
- Page 91: Packaging Web Service Application A
- Page 95 and 96: 84 BES Developer’s Guide
- Page 97 and 98: Client view of an enterprise bean L
- Page 99 and 100: Client view of an enterprise bean E
- Page 101 and 102: Managing transactions Managing tran
- Page 103 and 104: Support for JNDI Support for JNDI T
- Page 105 and 106: EJB to CORBA mapping A CORBA progra
- Page 107 and 108: 96 BES Developer’s Guide
- Page 109 and 110: Application Client architecture Pac
- Page 111 and 112: Document Type Definitions (DTDs) my
- Page 113 and 114: Support of references and links The
- Page 115 and 116: Use of Manifest files Use of Manife
- Page 117 and 118: 106 BES Developer’s Guide
- Page 119 and 120: Sessions in secondary storage If yo
- Page 121 and 122: 110 BES Developer’s Guide
- Page 123 and 124: Container-managed persistence and R
- Page 125 and 126: Implementing an entity bean Generat
- Page 127 and 128: Container-Managed Persistence in Bo
- Page 129 and 130: Container-Managed Persistence in Bo
- Page 131 and 132: Setting Properties Setting Properti
- Page 133 and 134: Setting Properties into a BLOB. The
- Page 135 and 136: Setting Properties Automatic table
- Page 137 and 138: 126 BES Developer’s Guide
- Page 139 and 140: Container-managed persistence and R
- Page 141 and 142: Container-Managed Persistence in Bo
Tools Overview<br />
Java2WSDL tool<br />
Note<br />
The Java2WSDL is an Apache Axis utility class that generates WSDL corresponding to<br />
a Java class. This class can accept a number of command line arguments. You can get<br />
the full usage help by running this utility without arguments as follows:<br />
java org.apache.axis.wsdl.Java2WSDL<br />
You must set your CLASSPATH to include all jar files in the \lib\axis<br />
directory, before you run the following command.<br />
WSDL2Java tool<br />
Note<br />
The WSDL2Java is an Apache Axis utility class that generates Java classes from a<br />
WSDL file. This tool can generate java stubs (used on the client side), or java skeletons<br />
(used on the <strong>server</strong> side). The generated files make it easy to develop your client or<br />
<strong>server</strong> for a given WSDL.<br />
This class can accept a number of command line arguments. You can get the full<br />
usage help by running this utility without arguments as follows:<br />
java org.apache.axis.wsdl.WSDL2Java<br />
You must set your CLASSPATH to include all jar files in the \lib\axis<br />
directory, before you run the following command.<br />
Axis Admin tool<br />
Note<br />
The Apache Axis Admin tool is a utility class that generates WAR level global<br />
configuration files based on deployment information specific to some <strong>web</strong> services.<br />
The input to this utility is a XML file (typically named deploy.wsdd) containing<br />
deployment information about one or more <strong>web</strong> services. The Apache Axis Admin<br />
utility adds some global definitions that are necessary and writes an output file. Use<br />
this tool as follows:<br />
java org.apache.axis.utils.Admin <strong>server</strong>|client deployment-file<br />
You must set your CLASSPATH to include all jar files in the \lib\axis<br />
directory, before you run the command.<br />
This tool generates <strong>server</strong>-config.wsdd or client-config.wsdd based on what option<br />
you choose.<br />
82 BES Developer’s Guide
Change language