- Project tools
-
-
- How do I...
-
| Category |
Featured projects |
| scm |
Subversion,
Subclipse,
TortoiseSVN,
RapidSVN
|
| issuetrack |
Scarab |
| requirements |
xmlbasedsrs |
| design |
ArgoUML |
| techcomm |
SubEtha,
eyebrowse,
midgard,
cowiki |
| construction |
antelope,
scons,
frameworx,
build-interceptor,
propel,
phing
|
| testing |
maxq,
aut
|
| deployment |
current |
| process |
ReadySET |
| libraries |
GEF,
Axion,
Style,
SSTree
|
| Over 500 more tools... |
|
The Tigris site will receive a major upgrade the evening of Monday, December 1, beginning at 8:30 pm PST. Downtime is projected to be about ten hours.
Further details in the announcement
Prior to install the WPS Spring Plug-In, JDK 1.5.x and Tomcat 5.x must be installed.
You can find the latest WPS Spring Plug-In from the Tigris Web Site. The project name is WPSINT Project
Steps:
1) Click on the link above;
2) Expand the folder name packages;
3) Click on the latest version link (0.0.1 for now);
4) You have to make a decision either the no dependencies package or with dependencies package
- No dependencies is the smallest package (~6MB). More work, see below
- With dependencies is the biggest package (~25MB). Environment ready, see below
5) Click one of the two and save it to your 'temporary' folder
see below for following instructions
Why 'No dependencies'? It takes less time to download because this installation contains WPS Spring Plug-In Jar Files only.
You will be able to use your own Jar Files you might already downloaded or to experiment WPS Spring Plug-In with new dependencies releases (see 2.4 WPS Plug-In Jar Files dependencies to know
all Jar Files required prior to get the environmenent working and ready). Building your own environment it at your own risk, testing will be required in order to get the result expected.
Steps: (continued)
6) From the 'temporary' folder, extract all underneath;
'docs' folder contains the Javadoc for all individual packages
'eclipe_plugins' folder contains a jar file for Eclipse
'src' folder contains the sources for all individual packages
'war' folder contains two files: 'WPS040SimpleWebGenericClient.war' and 'wps_ws_spring.war'
7) STOP TOMCAT INSTANCE!
8) Under the 'war' folder, copy the file 'WPS040SimpleWebGenericClient.war' and drop it to the Tomcat 'webapps' folder;
9) Under the 'war' folder, copy the file 'wps_ws_spring.war' and drop it to the Tomcat 'webapps' folder;
10) From the Tomcat 'webapps' folder, extract the war file 'WPS040SimpleWebGenericClient.war' to 'WPS040SimpleWebGenericClient' folder;
Underneath of 'WPS040SimpleWebGenericClient/WEB-INF', follow the instruction contained in the file 'readme_first.txt'
11) From the Tomcat 'webapps' folder, extract the war file 'wps_ws_spring.war' to 'wps_ws_spring' folder;
Underneath of 'wps_ws_spring/WEB-INF', follow the instruction contained in the file 'readme_first.txt'
12) If you have Eclipse installed, under the 'eclipe_plugins' folder, copy the jar file in your Eclipse 'plugins' folder;
After that point, you CANNOT start Tomcat, it will fail on 'WPS040SimpleWebGenericClient' and 'wps_ws_spring' because of missing dependencies.
Please read the file 'readme_jar_dependencies_to_download.txt' underneath of 'WEB-INF'
Why 'With dependencies'? It takes more time to download because this installation contains WPS Spring Plug-In Jar Files and all dependencies Jar Files.
You will NOT be required to download any other packages. The WPS Spring Plug-In has been tested with this environment and it should work properly.
The installation and configuration are minimum and ready to work for you. You will then ready to build to WPS Operations and publish them.
Steps: (continued)
6) From the 'temporary' folder, extract all underneath;
'docs' folder contains the Javadoc for all individual packages
'eclipe_plugins' folder contains a jar file for Eclipse
'src' folder contains the sources for all individual packages
'war' folder contains two files: 'WPS040SimpleWebGenericClient.war' and 'wps_ws_spring.war'
7) STOP TOMCAT INSTANCE!
8) Under the 'war' folder, copy the file 'WPS040SimpleWebGenericClient.war' and drop it to the Tomcat 'webapps' folder;
9) Under the 'war' folder, copy the file 'wps_ws_spring.war' and drop it to the Tomcat 'webapps' folder;
10) From the Tomcat 'webapps' folder, extract the war file 'WPS040SimpleWebGenericClient.war' to 'WPS040SimpleWebGenericClient' folder;
Underneath of 'WPS040SimpleWebGenericClient/WEB-INF', follow the instruction contained in the file 'readme_first.txt'
11) From the Tomcat 'webapps' folder, extract the war file 'wps_ws_spring.war' to 'wps_ws_spring' folder;
Underneath of 'wps_ws_spring/WEB-INF', follow the instruction contained in the file 'readme_first.txt'
12) If you have Eclipse installed, under the 'eclipe_plugins' folder, copy the jar file in your Eclipse 'plugins' folder;
13) START TOMCAT INSTANCE!
After that point, you are ready!
All packages are coming with a 'WPS Echoing Operation' service that will allow to hit our Web Service, also
a web application which called 'WPS Simple Web Generic Client' that will provide a GUI to test in deep any 'WPS Operation'.
NB: 1) In assuming the localhost Tomcat port is 8080.
2) The term 'Browser' could be IE5+, NS6+ or FireFox 1.5+
a) To know if the WPS Spring is running properly, if could request the status:
Response expected:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows" version="0.3.20" language="EN">
<ows:Exception locator="Server" exceptionCode="Application">
<ows:ExceptionText>Framework is running now. Here is the summary: Service name 'WPS' version '0.4.0' : WPS Spring PlugIn intercepts internet calls and process it.
1 operation(s) found:
1)Echoing=This is an example to send a string and then receive an echo
</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>
If you get this message, please keep going your testing.
If anything else shows up, read the error and fix the problem until you get this status message.
b) To know if the WPS Echoing Operation service is running properly:
Response expected:
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<wps:Capabilities version="0.4.0" updateSequence="1.0.0" xmlns:wps="http://www.opengeospatial.net/wps" xmlns:ows="http://www.opengeospatial.net/ows" xmlns:xlink="http://www.w3.org/1999/xlink">
...
</wps:Capabilities>
Again, if you get this message, please keep going your testing.
If anything else shows up, read the error and fix the problem until you get this status message.
c) To know if the WPS/SOAP Echoing Operation service is running properly:
Response expected:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="Echoing" targetNamespace="http://wpsint.tigris.org/soap/Echoing" xmlns:tns="http://wpsint.tigris.org/soap/Echoing" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
...
</wsdl:definitions>
Again, if you get this message, please keep going your testing.
If anything else shows up, read the error and fix the problem until you get this status message.
a) To know if the WPS Simple Web Generic Client is running properly:
Response expected:
If you get this screenshot, please keep going your testing.
If anything else shows up, read the error and fix the problem until you get this status message.
b) To know if the WPS Echoing Operation service is running properly throught this Interface
Enter "http://localhost:8080/wps_ws_spring/Echoing/service.wps" in the field name 'Server Name' and click the button 'Discover WPS Information'
Response expected:
If you get this screenshot, please keep going your testing.
If anything else shows up, read the error and fix the problem until you get this status message.
Congratulation! You succesfully installed WPS Spring Plug-In. You are ready to develop your own WPS Operation.
|
