Deploying Archives
Use
The recommended way to deploy archives is through the Deploy View. It is a visual interface that not only helps you deploy Java EE components, it also guides you through all life cycle phases of these components. You can manage both Java EE components developed within SAP NetWeaver Developer Studio and Java EE components developed with other development environments.
You can use the Deploy View only from within SAP NetWeaver Developer Studio.
With the Deploy 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.
Prerequisites
The Deploy View is open in Window → Show View → Other →Deploy View → Deploy View.
The Deploy View settings are set in Window → Preferences → SAP AS Java → Deploy View.
You can use the Deploy perspective that contains all deployment related views. To open it go to Window → Open Perspective → Other → Deploy.
Procedure
...
1. Open the Deploy View. On the left you see a tree with two main nodes: Workspace Deployable Archives and External Deployable Archives. After selecting one of the nodes, a pane with settings appears on the right.
2. Set the necessary settings and strategies:
○ Update 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 will fail when one of the deployments fails. This
is the default and recommended error behavior.
■
Skip deployment of archives 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.
○ Life cycle 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.
All applications that have already been deployed and started will be started at the end.
3. Add/locate the archives for deployment. You have the following options:
○ Select archives from your workspace:
You can use this option only if you have projects that contain EARs.
i. Select the node Workspace Deployable Archives.
ii.
Choose 
with the
quick info text Add element. The dialog box Add Deployable
Archives appears.
iii. Select one or more archives from the list.
iv. Choose OK. The selected archives are added to the Workspace Deployable Archives as subnodes.
○ Select external archives
i. Select the External Deployable Archives node.
ii. To select (you can use multiple select):
● A Java EE Archive, choose 
with the
quick info text Import Java EE Archive and select one or more archives from the
Choose Java EE Deployable Archive
dialog box.
● An SAP Archive, choose with the
quick info text Add element and select one or more archives that you want to
deploy from the Choose Deployable Archive dialog box. You can open different archives
as long as they contain the SAP-specific META-INF/SAP_MANIFEST.MF.
iii. Choose Open. The names of the selected archives appear in the tree under the External Deployable Archives root.
You can remove the archives from the list by
selecting them and choosing the 
button with the quick info text Remove
element.
4. You can save the set as a Deploy Template. For more information, see Deploy Templates.
5. In the tree, select one or more archives to be deployed.
If you select one of the root nodes, all archives beneath it will be deployed.
When you select a name of an archive, you can see additional information about it. When you select several archives, the settings and strategies are displayed on the right.
6.
Choose 
with
quick info text Deploy. The deployment process
for this component starts. When completed, a message appears to show the
result. The message types are:
○ Success – all applications have been deployed and started.
○ Warning – the application or some of the selected applications cannot be started.
○ Error – one or more of the selected applications were not deployed.
Java EE applications will be started according to the chosen strategy. An error message will notify you if an error occurred.
To make it easier for you, the message shows a summarized result of all operations and lists separately the results of each one.
In the Deploy View tree you can see small icon masks in front of the names of the archives that indicate the status of the last operation over them.
They are a:
○ Green tick in front of the component’s name (the deploy and start were successful)
○ Red exclamation mark - warnings during deploy (most likely the unit was successfully deployed, but could not be started)
○ Red cross (unsuccessful deploy)
For more detailed information about deployment operation, see the log messages in the Deploy View Console.
Result
You can see the applications listed in the Deploy View and in the Repository View in the respective software component branch.
More Information