The samples have been built using java and WebSphere tools. Before building the Enterprise Console Feature Option 1 samples, you must first install all the prerequisite software and set up your environment for access to all of the required class libraries.
Open the file <sdk_install_dir>/samples/wsnt-was/sample-was.properties
and modify it as follows:
WAS_PATH=<was_directory> SERVICE_ADDRESS=<NotificationConsumerService_URL>
where,
Attention: You must use forward slashes
"/" as the directory separator for the
WAS_PATH
property.
For instance, if WebSphere is located under C:\Program
Files\Websphere\AppServer
, you must set the WAS_PATH
property to C:/Program Files/Websphere/AppServer
.
WebSphere provides a tool named WSDL2Java
that generates
Java classes from wsdl. These Java classes are uses as the client side
stubs for accessing Web Services from Web Services
specifications
In this example, the WSDL2Java tool is invoked through an Apache Ant script, called build.xml
.
Apache Ant is a very sophisticated scripting environment and is very
popular amongst Java developers.
The build.xml file in the samples directory of the SDK contains Apache Ant tasks for building the sample. To build the samples, perform the following steps:
cd <sdk_install_dir>\samples\wsnt-was
%WAS_HOME%\bin\ws_ant
cd <sdk_install_dir>/samples/wsnt-was
$WAS_HOME/bin/ws_ant
The Java class files will be generated from the wsdl file and placed
in the <sdk_install_dir>/samples/wsnt-was/src
directory
. They will be compiled into directory <sdk_install_dir>/samples/wsnt-was/build/classes
.
A jar file called wsnt-was-samples.jar
of the classes is
created in <sdk_install_dir>/samples/wsnt-was/build/lib
directory.
Note
During the build process, some errors and warnings will be displayed on
the screen. The generated classes that have problems are not necessary
and are deleted during the build process.
Parent topic
WebSphere Application Server samples
Related topics
WS-Notification sample
walkthrough
Running the samples