Show TOC Start of Content Area

Procedure documentation Deploying and Testing the Project  Locate the document in its SAP Library 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 PAR file. The PAR file is a zip file that contains all the resources included in the portal project.

Procedure

Deploying the Project

To create and deploy the PAR file, you use the PAR Export plugin 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 Enterprise Portal. enter the required data. For login, specify a portal user that has the authorization for the deployment of PAR files in the portal. For example, a user with the system_admin_role has this authorization.

When you deploy files, you need to enter the password for this user.

       3.      In the toolbar, select the icon with the quick info text Export Par File.
The PAR Export plugin opens.

       4.      Select the project that contains the classes you want to deploy.

       5.      Specify a name for the PAR file. Select the remote portal where the PAR file must be deployed. Make sure you select the option Deploy PAR file.

       6.      When you choose Finish the PAR file is automatically generated and exported to the selected remote portal. After deployment you must restart the J2EE Engine 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 J2EE Engine (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.

End of Content Area