Deploying Archives

The recommended way to deploy archives is through the Deployment Job view. You can manage both Java EE components developed within SAP NetWeaver Developer Studio and Java EE components developed with other development environments.

With the Deploy ment Job view, you can deploy:

• SAP component archives

• Java EE archives located either in your workspace or anywhere else in your file system. Each of them is automatically transformed to an SAP specific component archive file (an SDA) when added to the Deploy View list.

For each new system added to the SAP NetWeaver Developer Studio, a new Deployment Job is added to the Deployment perspective. You can distinguish them by the suffix added to the name of the Deployment Job view.

The Deployment perspective is open from  Window  Open Perspective   Other   Deployment .

1. In the Repository Explorer view, choose the system on which you want to deploy.

2. Set the necessary settings and strategies in the Settings part of the corresponding Deployment Job view:

   • Deployment Strategy

     • Update deployed archives that have lower component versions than the selected ones.

     • Update deployed archives that have the same or lower component versions than the selected archives

     • Update deployed archives that have any version.

       This option is most suitable when you deploy Java EE archives since they do not have versions.

   • Error strategy

     • Stop when the first error occurs The whole deployment process fails when one of the deployments fails. This is the default and recommended error behavior.

     • Skip deployment of archive s depending on the erroneous deployment If the deployment of one of the components fails, all depending components are skipped and not deployed. The process continues with the next component in the deployment queue that does not depend on the failed component.

   • Lifecycle strategy

     • Bulk This is the recommended strategy for most of the scenarios. The Deploy Controller first delivers the components to the containers, and once all the components are delivered, they are started in the same order they were delivered.

     • Sequential The Deploy Controller sequentially delivers a component to the containers and then starts it. This strategy should not be used under normal circumstances. It is kept for backward compatibility only.

     • Sequential state dependent Applications are only deployed without any attempt to start them.

       Note

       All applications that have already been deployed and started will be started at the end.

3. To add the archives for deployment, in the Deployment List part of the Deployment Job view choose Import .

4. You have two options:

   • Select archives from your workspace:

     Note

     You can use this option only if you have projects that contain EARs.

     1. Select Workspace .

     2. Choose Next .

     3. Select one or more archives from the list.

     4. Choose Finish .

   • Select external archives:

     1. Select File System .

     2. Choose Finish .

     3. Select the archives.

     4. Choose Open .

        Note

        You can remove the archives from the list by selecting them and choosing the Remove.

   You can save the set as a Deploy Template . For more information, see Deploy Templates .

5. Choose Start . The deployment process starts. When completed, a message appears to show the result.

   Note

   For additional information about deployment operation, see the log messages in the Deployment View Console view.