Click on the Deploy new package subnode of the Deployment tree node of the Administration Console. This loads the Deploy New Package form.

Specify the target context of the package. You can either choose an existing context from the menu or enter a new context in the text field (please see Contexts).

If you want to enforce the setup of security mechanisms, check the Disable Service Instances box. This sets the state of all service instances in the newly deployed package to 'disabled' (please see Web Service Lifecycle).

Specify the package to deploy. You can browse your system for the package name.

Click the Deploy button (or the Cancel button if you have made a mistake).

Click on the Deployment tree node of the Administration Console. This loads the Deployment View. (Please see Figure 16.) Or you can find a deployed Package by its context as a subnode in the Deployment - Server Packages tree node.

Find the package you wish to undeploy in the List of Packages. To the right of the list are a number of buttons for each package. Press the second button to undeploy the package. This button loads the Undeploy Package form.

Figure 17. The Undeploy Button

The Undeploy Package form gives the details of the package you have chosen to undeploy. There is a box to check if you want to force undeployment of a package regardless of dependencies. Click the Undeploy button to undeploy this package, or the Cancel button if you have made a mistake.

Click on the Deployment tree node of the Administration Console. This loads the Deployment View. (Please see Figure 16.) Or you can find a deployed Package by its context as a subnode in the Deployment - Server Packages tree node.

Find the package you wish to clone in the List of Packages. At the right side of the list are a number of buttons for each package. Press the Clone button to clone the package. This loads the Clone Package form.

Figure 18. The Clone Button

The Clone Package form gives the details on the package you have chosen to clone. Here you must specify the security domain, server name and context name of the server on which you will deploy the clone. Press the Clone button to clone the package to the destination you have specified, or the Cancel button if you have made a mistake.

Click on the Deployment tree node of the Administration Console. This loads the Deployment View. (Please see Figure 16.) Or you can find a deployed Package by its context as a subnode in the Deployment - Server Packages tree node.

Find the package you wish to migrate in the List of Packages. At the right side of the list are a number of buttons for each package. Press the Migrate button to migrate the package (see Figure 19). This button loads the Migrate Package form.

Figure 19. The Migrate Button

The Migrate Package form gives the details on the package you have chosen to migrate. Here you must specify the security domain, server name and context name of the server to which you will migrate the package. Check the Force box to migrate the package regardless of dependencies. Press the Migrate button to migrate the package to the destination you have specified, or the Cancel button if you have made a mistake.

Click on the Deployment tree node of the Administration Console. This loads the Deployment View. (Please see Figure 16.) Or you can find a deployed Package by its context as a subnode in the Deployment - Server Packages tree node.

Find the package in which you are interested in the List of Packages. At the right side of the list are a number of buttons for each package. The second to last button downloads the package's deployment descriptor. The last button downloads the package's JAR file.