CONTENTS     

Deploy Service

This is a core service. It manages the deployment of J2EE applications on the corresponding containers across the cluster. It controls all actions that can be performed on containers to obtain information about deployed applications, or to modify them. It also keeps all deployed applications in the cluster homogeneous and up to date.

Visual Administrator

Runtime Control

Runtime control for Deploy Service can be performed on server nodes only. It is designed to manage deployment of applications at runtime, indicate status of the deployed applications, provide information about the application components, remove applications and change the application status. This can be accomplished using the following options:

• Deploy – when this option is used, the name of the EAR file to be deployed must be entered. The service decides where to deploy this component according to the component type.
• Get Client Jar - when deploying EJBeans, there are required classes to enable you to use Java client-specific remote support. These classes can be obtained as a JAR file with this option. It is copied to a directory specified by the user.
• Remove – removes a deployed application. Removing the whole application is recommended, although you can remove only some of its components.
• Update – when this option is used, only the last-changed application components are redeployed. If the application for update is not deployed, this command deploys it.  denotes that the application is updating. 
• Start Application – this command activates the application or starts a previously deployed one that is in stopped mode. The  icon in front of the application name denotes that the application is starting.  indicates that the application has started.
• Stop Application – this command stops a deployed application that has started. Use this if the application is not used at present, or it needs a restart. During update, the applications are stopped, and then updated and started again. The  icon in front of the application name denotes that the application is stopping.  indicates that the application has stopped.

Note 1: Do not restart EJB or Web Container while deploying, removing, updating, starting, or stopping applications.

Note 2: Restart running applications after either EJB or Web Container reboot.

In addition, there are three ways to view a list of deployed components in the “Deployed Components” box. These options rearrange the view of the tree to suit your needs:

• “Server” – displays all deployed components starting on each server
• “Application” – displays a general list of all deployed components and subtrees with the deployed servers and containers
• “Container” – displays all components by the type of container on which they are deployed

Properties

There are no service-specific properties to be set by the system administrator.

Console Administrator

Deploy Service can be administered using the Shell commands from the DEPLOY command group as well.

Note: For information on DEPLOY shell commands, refer to the Shell  Commands Reference section.

Property Files

../cluster/server/services/deploy /properties
This file does not contain any properties to be set by the system administrator.