Using Info*Engine Web Services Tooling
This is a basic overview of how the Info*Engine tooling for web services is organized. After reviewing this section, you should be able to locate tools and understand their purpose. The actual use of the tools is discussed in greater depth later.
The supplied tooling is enabled using Apache Ant, located in:
<Windchill>/ant
(where <Windchill> is the Info*Engine installation directory).
The tooling is intended to be run from a windchill shell, in which case the ant command is already in your path.
The directory that contains the Apache Ant build tools for deploying a web service is located in <Windchill>/bin/adminTools/WebServices and contains the following:
build.xml
The primary Apache Ant build script used to deploy web services and associate those services with security policies.
security.properties
A properties file containing the security-related configuration information used when deploying a web service. This file contains the security policy to use, the server-side truststore and keystore configurations, and any additional policy-specific configuration (if necessary) that is to be used at deployment time.
new-project.xml
An Apache Ant build script used to generate new Apache Ant projects, which are then used to build or deploy new web services or web service clients.
xslt/
A subdirectory containing XSL documents used during the web service deployment by build.xml.
client/
A subdirectory containing client-side security configuration properties.
client/security.properties
The client-side security configuration (truststore and keystore configuration information).
* 
The paths specified to the truststore and keystore must be specific to the corresponding location where those files reside on the client machine. These paths are included in security deployment descriptors and are not configurable.
common/
A subdirectory containing the common Apache Ant framework for web service projects.
Of these build tools, you should edit the security.properties files to specify your security configuration for client and server. If desired, you can make copies of these files for each client/server pair you decide to write.
To identify the changes needed, you can use the examples provided in the <Windchill>/prog_examples/jws directory, the root of the web service example projects. Each project is generated and developed using the new-project.xml script. This directory also contains the jws-stores.xml Apache Ant build script that can be used to generate client/server keystore and truststore pairs. The jws-stores.xml script uses OpenSSO to generate self-signed certificates for the client and server, and is intended as an example of how you can build your own truststores and keystores.
* 
You should use your own certificates rather than the generated self-signed certificates.
Est-ce que cela a été utile ?