Show TOC

 Deploying and Testing the ProjectLocate this document in the navigation structure

Use

When you have completed the development of your component, you can deploy it to the remote portal for debugging and testing. To do this, you create and export a portal archive called a EAR file. The EAR file is a zip file that contains all the resources included in the portal project.

Procedure

Deploying the Project

To create and deploy the EAR file, you use the EAR Exportplugin in the SAP NetWeaver Developer Studio.

  1. Activate the Portal toolbar with Window  →   Open Perspective  →  Other  →   Enterprise Portal
  2. Set up a connection to the portal to enable deployment. To do this, choose Window  →   Preferences  →   SAP AS Java enter the required data. SAP NetWeaver Developer Studio asks for credentials when you start the deploy.
  3. When you deploy files, you need to enter the password for this user.
  4. On the toolbar choose  to create a portal archive (EAR file).The EAR Export plugin opens.
  5. Select the project that contains the classes you want to deploy.
  6. Choose Deploy option in the context menu of the generated EAR file.
  7. When you choose Finish the EAR file is automatically generated and exported to the selected remote portal. After deployment you must restart the Application Server Java (AS Java) of the portal to activate the new application.

Testing

Note the following restrictions for testing on the remote portal:

  • Only one person can debug and trace. Simultaneous debugging is not possible.
  • After deployment, you always restart the AS Java (or at least the portal service) to activate the deployed components. Therefore, if several developers are sharing a test portal, it is essential to coordinate deployment.
  • If several developers write code locally and then deploy on a shared remote portal, unexpected errors may occur. This happens when the version of JAR files that is used to compile locally is incompatible with the version that is used at runtime on the remote portal. Underlying dependencies between the code developed by different developers, which are not visible in the local environment, cause the errors. Local JAR files must always be kept in sync with the JAR files on the remote portal.