If there is a requirement to change the
default framework pages, you will need to download the PAR(Portal
Archive Files) from the Portal and import them in NWDS and then change
the code.
Steps to download PAR Files:
1) You need to have Portal Admin Rights to download any PAR file
2) Log on to Portal as Administrator.
3) Go to System Administration -> Support
4) You will find Portal Runtime, click on it.
5) From the list of options listed below click Browse Deployment
6) On the top of the body are you will fine ROOT option, click on it.
7) Your structure will be ROOT/WEB-INF/deployment
8) Now select the PAR file you want to download and then click on download option.
Below are few PAR files listed,
Default Framework Page
com.sap.portal.layouts.framework (framework.jsp)
Innerpage
com.sap.portal.layouts.framework (WAandNavPanel.jsp)
Navigation Area
com.sap.portal.layouts.framework (dynNavArea.jsp)
Content Area
com.sap.portal.navigation.contentarea
NAVIGATION IVIEWS
Masthead
com.sap.portal.navigation.masthead
Tools Area
com.sap.portal.navigation.toolarea
(only delivered with Knowledge Management)
TLN
com.sap.portal.navigation.toplevel
Page Title Bar
com.sap.portal.navigation.pagetoolbar
DTN
com.sap.portal.navigation.detailedtree
Dynamic Navigation
com.sap.portal.navigation.dynnavarea
Drag&Relate Targets
com.sap.portal.navigation.targets
(same iView as Related Links)
See Also (Related Links)
com.sap.portal.navigation.targets
(same iView as Drag&Relate)
Portal Favorites
com.sap.km.cm
Check the below wiki where it is mentioned how to upload the par file to NWDS
https://wiki.sdn.sap.com/wiki/x/yIDLAQ
Steps to download PAR Files:
1) You need to have Portal Admin Rights to download any PAR file
2) Log on to Portal as Administrator.
3) Go to System Administration -> Support
4) You will find Portal Runtime, click on it.
5) From the list of options listed below click Browse Deployment
6) On the top of the body are you will fine ROOT option, click on it.
7) Your structure will be ROOT/WEB-INF/deployment
8) Now select the PAR file you want to download and then click on download option.
Below are few PAR files listed,
Default Framework Page
com.sap.portal.layouts.framework (framework.jsp)
Innerpage
com.sap.portal.layouts.framework (WAandNavPanel.jsp)
Navigation Area
com.sap.portal.layouts.framework (dynNavArea.jsp)
Content Area
com.sap.portal.navigation.contentarea
NAVIGATION IVIEWS
Masthead
com.sap.portal.navigation.masthead
Tools Area
com.sap.portal.navigation.toolarea
(only delivered with Knowledge Management)
TLN
com.sap.portal.navigation.toplevel
Page Title Bar
com.sap.portal.navigation.pagetoolbar
DTN
com.sap.portal.navigation.detailedtree
Dynamic Navigation
com.sap.portal.navigation.dynnavarea
Drag&Relate Targets
com.sap.portal.navigation.targets
(same iView as Related Links)
See Also (Related Links)
com.sap.portal.navigation.targets
(same iView as Drag&Relate)
Portal Favorites
com.sap.km.cm
Check the below wiki where it is mentioned how to upload the par file to NWDS
https://wiki.sdn.sap.com/wiki/x/yIDLAQ
Portal Archive (PAR) files are special container files that contain portal applications to be deployed. PAR files are normally built using NetWeaver Developer Studio (NWDS), and can be dployed using the same tool.
If you are sent a PAR file, it can be deployed using NWDS, but it is often easier to use the portal administration console.
With NetWeaver 7.0 and earlier releases, this can be launched by a portal administrator by navigating through the System Admin -> Support menu path in the portal.
In the support Desk application, use the link to Portal Runtime and then the option Administration Console. This provides a field where you can browse to the PAR file and then use the Upload option. After the upload is complete, it is possible to create an iView to start the deployed portal component, or it can be started using a URL http://portalhost:port/irj/servlet/prt/portal/prtrooot/<PAR file>.<Component>, twhere PAR file is the PAR file anme, without the .PAR extension and <Component> is the component name, as given by the developer.
No comments:
Post a Comment