The JSP Web Service Proxy wizard adds a TLD and a JAR file containing TLD classes to JSP target subdirectories. When you deploy the JSP target, these files are deployed along with the other target files. Table 8-7 lists the files created by the JSP Web Service Proxy wizard.
File added by wizard |
Description |
|---|---|
tlds\Service_Name.tld |
A default file name is provided by the Web service WSDL, but the JSP Web Services Proxy wizard lets you rename the TLD file that it adds to the target |
lib\Service_Name.jar |
A default file name is provided by the Web service WSDL, but the JSP Web Services Proxy wizard lets you rename the JAR file that it adds to the target |
Files created on a full build of your JSP target
When you build a JSP target for the first time, PowerBuilder
creates Jaguar.properties and Database.properties files
in the target’s WEB-INF\Class directory.
These files contain connection information from your current PowerBuilder
database and EAServer profiles.
If you modify these profiles before you deploy a JSP target, you
should perform a full build to make sure the Jaguar.properties and Database.properties files
contain up-to-date connection information.
For information about performing a full build, see “Building Web targets”.
At runtime, the JSP server where you deploy your target must have additional files in its class path for a Web service to work:
axis.jar
commons-discovery.jar
commons-httpclient.jar
commons-logging.jar
dom.jar
jaxrpc.jar
log4j-1.2.8.jar
pbwst105.jar
saaj.jar
sybasewst.jar
wsdl4j.jar
xercesImpl-2.1.0.jar
xml-apis.jar
These files are not deployed with your JSP target. If your server does not have these files in its class path, you can copy them to a directory in the server class path from the Sybase\Shared\PowerBuilder\WEB-INF\lib directory. For Tomcat, you should copy them to the Tomcat Shared\Lib directory.
For HTTPS connections over SSL, you also need to copy the following files to your JSP server class path:
jcert.jar
jnet.jar
jsse.jar
