Starting and Stopping the Portal

Question

Hi all
   After deploying my PAR, I am restarting the whole <b>SAP Instance</b> in the Server.
1. Is this the right way ???
2. Is there any other easy way to restart/stop the PORTAL alone instead of touching the SAP Instance???
Thanks
Kay

Answer 1

Hi Kay,
You are right about custom login changes.But Normaly if you develop portal application and upload the PAr file ,you do not have to restart the instance.Portal runtime takes care of droping the existing copy of the PAR or replacing with newer version.
This is what i get from help
Portal Archive Files Deployment Cycle
Use
The deployment procedure for a Portal Archive (PAR) file consists of two steps:
Uploading the PAR file into the application repository
Notifying all Portal Runtime (PRT) nodes that a new version of the application is available
Activities
Uploading a PAR File to the Application Repository
There is only one application repository and all PRT nodes and PAR files on the J2EE Engine cluster share the same content. The PAR upload procedure stores the whole archive in the underlying persistence layer. It also extracts all the information that requires fast access at runtime from the portalapp.xml.
Modifying PRT Nodes
Once the upload to the application repository is completed, the upload process notifies all PRT nodes. This step updates thelocal deployment of the portal application on each server. The update of the local deployment requires runtime deployment capabilities, and that is why all portal applications can be released. A PRT node:
·        Checks if the application is already loaded and drops the corresponding instance.
This step also checks and drops all entities (applications, components and services) that depend on the current application.
·        Starts the deployment process.
This process gets the PAR file from the repository and updates the local deployment by expanding the archive content.
·        Restarts all portal applications that have been dropped.
The main purpose of the local deployment is to improve performance at runtime by providing fast access to classes and to portal application resources. The local deployment avoids additional round trips to the application repository and, in that sense, must be considered as a cache for portal applications.
Deployment Policy
The local deployment is done using the DeploymentPolicy property declared in the portalapp.xml file:
·        If this property is set to “5.0”
The deployment is backwards compatible with the EP50 version of the portal. The old folder is not removed and the deployment process simply overrides the folder with the new content.
·        If the DeploymentPolicy property is missing
A regular deployment is performed; the old deployment folder is removed and then replaced by the new one.
The deployment logic assumes that the application does not store any configuration locally; everything must be stored in the repository.
For more information about the DeploymentPolicy property, see Application-Config Element Properties.