This document describes how you can use scripts to integrate Java(TM) Web Services Developer Pack (Java WSDP) components into Java(TM) 2 Enterprise Edition 1.3.X SDK. This document describes each step needed to be taken and the effects of each step.

Caution : These scripts are to be used with a fresh J2EE 1.3.X SDK installation. If you have already modified any J2EE scripts then these scripts may not work. The setup step should be done only once; you should not repeat the setup step.

Note : You can execute these instructions by going to <JWSDP_HOME>/bin or by giving full path of the shell script/batch file.

1. Setting up the J2EE 1.3.X SDK environment to use Java Web Services Developer Pack components.

   Note : This step should be done only once with a fresh installation of the J2EE 1.3.X SDK.

           jwsdponj2ee.sh <J2EE_HOME> [UNIX/Linux]

           jwsdponj2ee.bat <J2EE_HOME> [Windows]

   This script copies all the required JAR files to the system/lib directory of the J2EE SDK and make required changes to the J2EE SDK configuration files.

   Caution : This setup process may take 10 to 20 minutes depending on the machine. Please DO NOT terminate the setup process in between.

2. Deploying JAXM Provider, Registry Server and all Java WSDP examples.

   Note : You should have J2EE SDK server already started for this step to be performed. You can start J2EE SDK server by executing <J2EE_HOME>/bin/j2ee -verbose.

           jwsdponj2ee.sh <J2EE_HOME> deployAll [UNIX/Linux]

           jwsdponj2ee.bat <J2EE_HOME> deployAll [Windows]

   This will deploy JAXM Provider, Registry Server and all the examples that are accessible from the Java WSDP index.html page. This also copies jwsdp.html to <J2EE_HOME>/public_html. You can access the page and click links to try out the samples by invoking

           http://localhost:8080/jwsdp.html or
           http://<hostname>:8080/jwsdp.html

3. Undeploying JAXM Provider, Registry Server and all Java WSDP examples.

   Note : You should have J2EE SDK server already started for this step to be performed. You can start the J2EE SDK server by executing <J2EE_HOME>/bin/j2ee -verbose. And, you should have Java WSDP examples already deployed.

           jwsdponj2ee.sh <J2EE_HOME> undeployAll [UNIX/Linux]

           jwsdponj2ee.bat <J2EE_HOME> undeployAll [Windows]

   This will undeploy JAXM Provider, Registry Server and all the examples that are accessible from the Java WSDP index.html page. This also removes the jwsdp.html page which was copied into <J2EE_HOME>/public_html.

Alternatively, you can deploy/undeploy individual components as follows:

• Deploying JAXM Provider and JAXM Provider admin :

          jwsdponj2ee.sh <J2EE_HOME> deploy-jaxmcontrollers [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> deploy-jaxmcontrollers [Windows]

• Deploying Registry Server :

          jwsdponj2ee.sh <J2EE_HOME> deploy-registryserver [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> deploy-registryserver [Windows]

• Deploying JAXM Samples :

          jwsdponj2ee.sh <J2EE_HOME> deploy-jaxmsamples [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> deploy-jaxmsamples [Windows]

• Deploying JSTL Examples :

          jwsdponj2ee.sh <J2EE_HOME> deploy-jstlexamples[UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> deploy-jstlexamples [Windows]

• Undeploying JAXM Provider and JAXM Provider admin :

          jwsdponj2ee.sh <J2EE_HOME> undeploy-jaxmcontrollers [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> undeploy-jaxmcontrollers [Windows]

• Undeploying Registry Server :

          jwsdponj2ee.sh <J2EE_HOME> undeploy-registryserver [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> undeploy-registryserver [Windows]

• Undeploying JAXM Samples :

          jwsdponj2ee.sh <J2EE_HOME> undeploy-jaxmsamples [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> undeploy-jaxmsamples [Windows]

• Undeploying JSTL Examples :

          jwsdponj2ee.sh <J2EE_HOME> undeploy-jstlexamples [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> undeploy-jstlexamples [Windows]

Extracting separate components

You can use the following commands to extract files needed for different technologies which are part of the Java WSDP.

• Extracting the JAXRPC component :

          jwsdponj2ee.sh <J2EE_HOME> extract-jaxrpc [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> extract-jaxrpc [Windows]

  Note : JAXRPC files would be under <JWSDP_HOME>/work/forj2ee/jaxrpc.

• Extracting the JAXR component :

          jwsdponj2ee.sh <J2EE_HOME> extract-jaxr [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> extract-jaxr [Windows]

  Note : JAXR files would be under <JWSDP_HOME>/work/forj2ee/jaxr.

• Extracting the JAXM component :

          jwsdponj2ee.sh <J2EE_HOME> extract-jaxm [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> extract-jaxm [Windows]

  Note : JAXM files would be under <JWSDP_HOME>/work/forj2ee/jaxm.

• Extracting the JAXP component :

          jwsdponj2ee.sh <J2EE_HOME> extract-jaxp [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> extract-jaxp [Windows]

  Note : JAXP files would be under <JWSDP_HOME>/work/forj2ee/jaxp.

• Extracting the Registry Server component :

          jwsdponj2ee.sh <J2EE_HOME> extract-registryserver [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> extract-registryserver [Windows]

  Note : Registry Server files would be under <JWSDP_HOME>/work/forj2ee/registryserver.

• Extracting the JSTL component :

          jwsdponj2ee.sh <J2EE_HOME> extract-jstl [UNIX/Linux]
          jwsdponj2ee.bat <J2EE_HOME> extract-jstl [Windows]

  Note : JSTL files would be under <JWSDP_HOME>/work/forj2ee/jstl.

Please send your feedback to jwsdp-feedback@sun.com.