Problem Undeploying a PAR file

Hi,
Let me first give the history of this problem.
I wrote a small portal application and created a par file named RoyaltiesService.par and tried to deploy it from NWDS, but NWDS got stuck and i was not able to deploy the par file. I also realised that my portal server stopped and my efforts to start the server have gone in vain. Please see the details of that problem at <Re: Problem with protal server>
So after trying to solve the problem for few days I reformatted my machine and reinstalled the portal now. I was able to deploy other par files and everthing worked fine, but now I tried to deploy the same par file RoyaltiesService.par (the one that i tried to deploy when the problem occurred for the first time) and the same problem reoccurred i.e., my NWDS got stuck, portal server stopped and i am unable to start it. I am wondering whether my par file has something to do with this. I thought of undeploying the par file from the SDM console but i am not able to find that RoyaltiesService.par file. Then i did a search for the par file in my c:usrsap and found the following results. (File/Folder name - location)
-> RoyaltiesService - C:usrsapJ2EJC00j2eeclusterserver0appssap.comirjservlet_jspirj
ootWEB-INFportalportalapps
-> RoyaltiesService.revision - C:usrsapJ2EJC00j2eeclusterserver0appssap.comirjservlet_jspirj
ootWEB-INFportalsystem
evisions
-> RoyaltiesService.par.bak - C:usrsapJ2EJC00j2eeclusterserver0appssap.comirjservlet_jspirj
ootWEB-INFdeployment emp
-> RoyaltiesServiceapi.jar - C:usrsapJ2EJC00j2eeclusterserver0appssap.comirjservlet_jspirj
ootWEB-INFportalportalappsRoyaltiesServicelib
-> RoyaltiesServicecore.jar - C:usrsapJ2EJC00j2eeclusterserver0appssap.comirjservlet_jspirj
ootWEB-INFportalportalappsRoyaltiesServiceprivatelib
Now i want to remove this par file from the deployment. Can anyone suggest me how to do it ??
Any help will be very very helpful to me.
Thanks & Regards,
Sudhir

Hi,
You cannot remove from the file system, because the application is deployed to the PCD (Application Repository), which then replicates the application to all the cluster nodes.
You have to use the Archive Remover tool. Did you try?
Even if you cannot get the portal interface, if you can log in and create a session, you can navigate to the archive remove and remove the application.
Hope this helps.
Daniel

Similar Messages

Problems with the par file of Browse Deployment

Hi,
I had an error message with the com.sap.portal.support.browse.default in Browse deployment, that this iView is not found.
Fortunately I had a file with the same name, so I uploaded it, but it was the wrong one (Why do they all have the same file name?). I uploaded the par file of the masthead, so every time i click on the browse deployment link I get the masthead and now I have no chance to download other par files.
Do I still have the right iView on the Server or in the Portal? If yes, where? Or can anybody send me the right par file?
e-Mail: Ulli_Arndt(at)gmx.de
Thanks in advance!
greetings,
Ulrike

Hello Ulrike,
Most companies use different servers for development and Production. The Browse Deployment Option should be used only with the development server. If you're going to use it with the Production server, there could be problems, as the two servers have a different architecture.
Once you sign in to the DEVELOPMENT SERVER using your user id, ensure that you have the Systems Administration Role and click on the tab corresponding to the same.
Then select Support.
Select Portal Runtime.
Select Browse Deployment.
Once you do this, you'll see a filepath on top of the page just below the top level navigation area. Here's where most people commonly make a mistake.
Ensure that the breadcrumb is EXACTLy as follows:
ROOT/WEB-INF/deployment/temp
If this is not the case, clcik on ROOT in the filepath displayed on your screen and navigate along the filepath above so you reach the correct iView.
You should now see a list of files with the extension .par.bak.
Upon downloading any of these files, the downloaded .rar file for most of the files with have the same filename. Once you unzip this file once or twice, you'll get a .par.bak file with the same filename as the one you downloaded. Rename the extracted .par.bak file by removing the .bak extension. You'll be left with a .par extension now.
You can now import this file in NWDS and work on it as required.
I hope this helps. Let me know if you have anyfurther questions. Screenshots are alsways helpful, especially of the filepath on the top of your screen.
Regards,
Farsheed

Problem with importing par file in portal server 6.2

Hi everyone,
I got the following error when trying to import IFRAME provider into portal server 6.2.
Operation failed.
ERROR: provider element has no version attribute
Below is the command I used. I run it as a file - I supply the password at the command line.
/opt/SUNWps/bin/par import verbose overwrite runasdn uid="amAdmin,ou=People,dc=accesscollier,dc=com" password $1 IFRAMEProvider.par dc=accesscollier,dc=com provider=IFRAMEProvider.
This used to work in Portal Server 6.0. I looked through the Portal Server 6.2 Desktop Customization Guide and the Developer guide for portal 6.2 but did not find any reference to version number.
Thanks.
Klara Hribkova
I

Hi Ulf,
here is the command + options. It is in a file, I supply the password on the command line. This used to work fine with PortalServer 6.0.
!/bin/ksh
echo "----------------------------------"
echo "USE: import_providers.sh password "
echo "----------------------------------"
#echo "Importing IFRAMEProvider ..."
#/opt/SUNWps/bin/par import verbose overwrite runasdn uid="amAdmin,ou=People,dc=accesscolier,dc=com" password $1 IFRAMEProvider.par
dc=accesscollier,dc=com provider=IFRAMEProvider
echo "Importing IFRAMECalendarProvider ..."
/opt/SUNWps/bin/par import verbose overwrite runasdn uid="amAdmin,ou=People,dc=accesscollier,dc=com" password $1 IFRAMECalendarProvi
der.par dc=accesscollier,dc=com provider=IFRAMECalenderProvider
echo "Importing IFRAMEMailProvider ..."
/opt/SUNWps/bin/par import verbose overwrite runasdn uid="amAdmin,ou=People,dc=accesscollier, dc=com" password $1 IFRAMEMailProvider
.par dc=accesscollier,dc=com provider=IFRAMEMailProvider
echo "Importing JSPWebAppProvider ..."
/opt/SUNWps/bin/par import verbose overwrite runasdn uid="amAdmin,ou=People,dc=accesscollier, dc=com" password $1 JSPWebAppProvider.
par dc=accesscollier,dc=com provider=JSPWebAppProvider
These are the errors I get:
# ./import_providers1.sh solurute
./import_providers1.sh: !/bin/ksh: not found
USE: import_providers.sh password
Importing IFRAMECalendarProvider ...
AUTHENTICATING
uid=amAdmin,ou=People,dc=accesscollier,dc=com
solurute
AUTHENTICATED - Setting DN - dc=accesscollier,dc=com.
Initializing for operation - dpnode=dc%3Daccesscollier%2Cdc%3Dcom,provider=IFRAMECalenderProvider.
Operation failed.
ERROR: provider element has no version attribute.
Importing IFRAMEMailProvider ...
AUTHENTICATING
uid=amAdmin,ou=People,dc=accesscollier, dc=com
solurute
AUTHENTICATED - Setting DN - dc=accesscollier,dc=com.
Initializing for operation - dpnode=dc%3Daccesscollier%2Cdc%3Dcom,provider=IFRAMEMailProvider.
Operation failed.
ERROR: provider element has no version attribute.
Importing JSPWebAppProvider ...
AUTHENTICATING
uid=amAdmin,ou=People,dc=accesscollier, dc=com
solurute
AUTHENTICATED - Setting DN - dc=accesscollier,dc=com.
Initializing for operation - dpnode=dc%3Daccesscollier%2Cdc%3Dcom,provider=JSPWebAppProvider.
Operation failed.
ERROR: provider element has no version attribute.
This is the build_par.xml file:
<?xml version="1.0"?>
<project name="Provider" default="all" basedir=".">
<property name="par.dir" value="./pars"/>
<property name="iframe.dir" value="iframeprovider"/>
<property name="iframecalendar.dir" value="iframecalendarprovider"/>
<property name="iframemail.dir" value="iframemailprovider"/>
<target name="iframe">
     <jar jarfile="${par.dir}/IFRAMEProvider.par"
          basedir="${iframe.dir}"
          includes="**/*">
          <manifest>
          <attribute name="PS-Version" value="1"/>
               <attribute name="PS-DefaultEntry" value="IFRAMEProvider"/>
               <attribute name="PS-PBFileRoot" value="pbfiles"/>
               <attribute name="PS-StaticRoot" value="static"/>
               <attribute name="PS-DPRoot" value="dp"/>
               <section name="dp/IFRAMEProvider.xml">
                    <attribute name="PS-EntryName" value="IFRAMEProvider"/>
                    <attribute name="PS-Include" value="pbfiles/providerClassBaseDir/k20portal.properties(1),com/hangingvalley/sunportal/util/K20PortalProperties.class(1),com/hangingvalley/sunportal/util/OrgProperties.class(1),pbfiles/templateBaseDir/default/IFRAMEProvider/iframecontent.jsp(1),pbfiles/templateBaseDir/default/IFRAMEProvider/iframedoedit.jsp(1),pbfiles/templateBaseDir/default/IFRAMEProvider/iframeedit.jsp(1)"/>
               </section>
          </manifest>
     </jar>
</target>
<target name="iframecalendar">
     <jar jarfile="${par.dir}/IFRAMECalendarProvider.par"
          basedir="${iframecalendar.dir}"
          includes="**/*">
          <manifest>
               <attribute name="PS-Version" value="1"/>
               <attribute name="PS-DefaultEntry" value="IFRAMECalendarProvider"/>
               <attribute name="PS-PBFileRoot" value="pbfiles"/>
               <attribute name="PS-StaticRoot" value="static"/>
               <attribute name="PS-DPRoot" value="dp"/>
               <section name="dp/IFRAMECalendarProvider.xml">
                    <attribute name="PS-EntryName" value="IFRAMECalendarProvider"/>
                    <attribute name="PS-Include" value="pbfiles/templateBaseDir/default/IFRAMECalendarProvider/iframecontent.jsp(1),pbfiles/templateBaseDir/default/IFRAMECalendarProvider/iframedoedit.jsp(1),pbfiles/templateBaseDir/default/IFRAMECalendarProvider/iframeedit.jsp(1)"/>
               </section>
          </manifest>
     </jar>
</target>
<target name="iframemail">
     <jar jarfile="${par.dir}/IFRAMEMailProvider.par"
          basedir="${iframemail.dir}"
          includes="**/*">
          <manifest>
               <attribute name="PS-Version" value="1"/>
               <attribute name="PS-DefaultEntry" value="IFRAMEMailProvider"/>
               <attribute name="PS-PBFileRoot" value="pbfiles"/>
               <attribute name="PS-StaticRoot" value="static"/>
               <attribute name="PS-DPRoot" value="dp"/>
          <section name="dp/IFRAMEMailProvider.xml">
                    <attribute name="PS-EntryName" value="IFRAMEMailProvider"/>
                    <attribute name="PS-Include" value="pbfiles/templateBaseDir/default/IFRAMEMailProvider/iframecontent.jsp(1),pbfiles/templateBaseDir/default/IFRAMEMailProvider/iframedoedit.jsp(1),pbfiles/templateBaseDir/default/IFRAMEMailProvider/iframeedit.jsp(1)"/>
               </section>
          </manifest>
     </jar>
</target>
<target name="all" depends="iframe,iframecalendar,iframemail"/>
</project>
Thank you very much for your assistance and for your time.
Klara

Problem uploading a PAR file from NWDS

I am having trouble uploading to one of my portal servers- I have always been able to upload to this server until last week when a database conversion and a change to the way SSO works (they implemented the spnego method of authentication) and now I can't upload to this server any longer. Here is the log from the sap-plugin.log file. Any ideas would be greatly appreciated.
Thanks,
Dana
[12.02.07 / 10:25] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > No privateArchive.properties file is defined.
[12.02.07 / 10:25] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > Missing file plugin.header.properties in /UMERefresh/src.config/install/meta/expanded/cm/services/schedulertasks
[12.02.07 / 10:25] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > Config archive successfully created (time to export 1266 ms)
[12.02.07 / 10:49] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > No privateArchive.properties file is defined.
[12.02.07 / 10:49] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > Missing file plugin.header.properties in /UMERefresh/src.config/install/meta/expanded/cm/services/schedulertasks
[12.02.07 / 10:49] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > Config archive successfully created (time to export 1016 ms)
[12.02.07 / 10:50] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.IOException: Server returned HTTP response code: 401 for URL: http://tewk-eptst.global.avidww.com:54200/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.archiveuploader?login_submit=on&j_user=dboisver&j_password=newman12&j_authscheme=default&uidpasswordlogon=log%20on
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:800)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:404)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:338)
     at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:519)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
     at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
     at org.eclipse.jface.window.Window.open(Window.java:563)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.invokeWizardInANewDialog(WizardInvokeAction.java:185)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.run(WizardInvokeAction.java:86)
     at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
     at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
     at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
     at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
     at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
     at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
     at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:286)
     at com.sap.ide.eclipse.startup.Main.run(Main.java:795)
     at com.sap.ide.eclipse.startup.Main.main(Main.java:602)

Hi Dana,
Try opening the url in the error trace directly and see what happens:
http://tewk-eptst.global.avidww.com:54200/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.archiveuploader?login_submit=on&j_user=dboisver&j_password=newman12&j_authscheme=default&uidpasswordlogon=log%20on
You can see from the url that it tries to call the archiveuploader application directly, and that it passes your logon credentials (maybe you should change your password now ) and uses "default" authentication. The spnego authentication you mentioned, is it the default authentication method for the portal?
Johan

Problem in importing .par file in sun portal 6.0

hi every one ..
i have written a message of the day jspprovider channel using portlet builder 1.0 in sun one studio ..now when i m importing the .par in sun one portal ..it is not giving any error but the new channel is not getting displayed in amconsole ..
can any one suggest me how to import a channel in portal server 6.0 and what post configuration one has to do to view the channel in sun one portal ..
thanks
san

By the way ...
How did you run the par command....
I imported like this...
par import -o -r "uid=amAdmin,ou=People,o=test.flowsystems.se,o=isp" -p password -d -v SMSPortlet.par global provider=SMSPortlet,channel=SMSPortletChannel
I forgot the last arguments the first time. And if I remember it right I did not see the portlet in the gui.
/Peo

Problems deploying par file via Netweaver Developer Studio

Hello,
I have problems deploying a par file using the SAP Netweaver Developer Studio.
In the SNWDS i configure the following:
Window -> Preferences -> SAP Enterprise Portal
Alias: IEP
Host: khz059
Port: 52900
Login: Administrator
Description: Testportal
The logon Url of the portal is http://khz059:5290052900/irj/portal
If i try to upload a par file via "Quick PAR Upload" i get the error messages:
"Unable to connect to the portal
Operation failed: Please make sure the server 'IEP' (khz059:52900) is running or check the log (sap-plugin.log) for more detail."
Am I using the proper settings? Am I using the wrong port?
I don't know whats wrong.
Can anyone help me?
The logfile shows:
[12.09.05 / 14:53] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.IOException: Error writing to server
     at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:302)
     at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:314)
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:634)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:361)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:433)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:220)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:404)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:338)
     at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:519)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
     at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
     at org.eclipse.jface.window.Window.open(Window.java:563)
     at com.sap.portal.developmentTools.general.uploader.QuickPARUploader.run(QuickPARUploader.java:146)
     at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
     at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
     at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
     at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
     at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
     at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
     at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
     at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Best regards,
Nils Kloth

Hi Nils,
I think you must have selected the defualt checkbox (Try and uncheck that). Also uncheck the checkbox for "<i>Yes, I want to remeber the password for deployment</i>" if it is also selected. When you deploy the par file now enter the password and try to deploy. I think this will solve your problem.
Apart from this, try this methos of deploying the Par file.
1) Save you project. Right click it and "Quick par Upload".
2) On your browser type
"http://<your_server_name>:50000/irj/servlet/prt/portal/"
Your case:
<i>http://khz059:52900/irj/servlet/prt/portal/</i>
or same page you can get by navigating:
System Administration-> Support-> Portal Runtime-> Administration Console.
3) At the option "Please specify a Portal Archive file (PAR) and press "upload" to store it into the PCD." Deploy your par file by giving the path.
Now you file is deployed on the server. If you want to create an Iview from this deployed .par file then :
1) On your portal. Follow the path: Content Administrator-> Portal Content -> Portal Content(sub-option). Right click -> New from par ->iView.
2) Here in the list you will find the par file which you have uploaded. Proceed as said.
3) You will finally have an iView. Right click it and preview it.
I hope this solves your problem.
Regards
Pravesh
PS: Please consider rewarding points if helpful.

Problem while deploying new logon screen par file via NWDS

hi
i have a problem with deploying .par files out of the NWDS.
i want to change the look of the logon screen in our EP Portal (SAP NetWeaver 2004s).
when i just import the (working one) par file into NWDS and deploy it without ANY changes i get then an error when trying to call the portal:
instead of the logonscreen i get some IView error (like IView: N/A).
if i just copy the par file, and put it back to the pcd, everything works fine.
my problem seems to be the "compiling/deploying" via NWDS.
any suggestions?
i followed the guide:
http://help.sap.com/saphelp_nw04/helpdata/en/23/c0e240beb0702ae10000000a155106/frameset.htm
i followed also the BLOG:
Modifying The Logon Par(or customising the Logon Screen)
and the help:
http://help.sap.com/saphelp_nw04/helpdata/en/23/c0e240beb0702ae10000000a155106/content.htm
thanks for your help.
markus

Markus,
If you import the par file using NWDS, most likely you wouldn't import the associated jar files (I think 2 jars) that are originally part of the par file. So, when you make changes and update your custom jar, it would lack the two jars and your application would fail. Try downloading the par file using System Administration -> Support -> PCD Administration -> Browse Deployment..
Save the jar file on desktop and then import it to NWDS.
Hope this helps,
Kiran

Deployed PAR file webservices are not displayed in SOAP admin

Hi,
we were facing the problem with customized PAR file deployment and
associated webservices.We have deployed the the PAR file on two
different versions of EP as given below.
EP6.0(WAS620)-SP2(J2EE and Portal versions are identical)
EP6.0(WAS640)-SP13(J2EE and Portal versions are identical)
The problem was the webservices has been shown in the case of
EP6.0(WAS620)-SP2 under SOAP Administration and not shown in case
of EP6.0(WAS640)-SP13.Is there any specific version made PAR files are
required for each of above portal versions or any other way to
check the webservcies in EP6.0(SP13).
Kindly help us to resolve this issue.

Hi Swetha ,
in Bypass scenario if you are fetching a flat file from source to target some time you are not able to view the file in payload .However it does not make any difference as you are simply tunnling the file not doing any transformation with it .
If it is a flat file in sender CC just make 1 .file type as bin or 2 . file type as text and encoding as UTF-8 and then check you can view the file content or not .check with both bin and text ( one by one ) .might be you will able to view payload in MONI with any one of that setting in sender CC .
Regards,
Saurabh

Cannot find components in the par file

Hi All,
I have a problem with a par file. I created a new project by importing an existing par file from portal. This par file has 2 components. I could find the names of two components in portalapp.xml but could not find the .java classes (or any code) for those components. When I run the components I get a error message - "iView not found : ComponentA" (Component A is the name of my component). Am I missing something here? The security zone of these components is set to
"high_safety". Does this have any impact.
Where exactly are these components created ? (I mean which folder in the project structure? )
Thanks in advance.

Hello,
If u imported SAP component(name space starts with com.sap) in to NWDS, sap did't provided source code of PAR file , thats why u u r unable to find those java files in NWDS, but we can see component names in xml file, still if u wanna see the code. open u r par with the help of WINRAR, u can find a class name with the COMPONENT name, by using DJ decompiler we can see code.
if it is a custom component and imported to NWDS still u r unable to see those java files means when previous developer uploaded into portal system didn't checked the option "include source code".
Regards
malli......

Problem during uploading of .par file in Portal

Hi,
I am downloading a properly working .par file from portal in my local system. But whenever I am uploading the same par file back into the portal through NWDS, the .par file is not running properly and its Giving error.
Here is the error:
"Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.tmobile.compSumm.CompSumm of Portal Component com.tmobile.CompSumm.CompSumm because: Could not find implementation class "
Any Idea what is the problem?????

Hi,
I have unzipped the .jar file from the .par file. Then I imported the .par file into NWDS. After that I have added the extacted .jar file as external jar into the project(Proerties->Java Build Path->Libraries->Add External Jars). After that I had uploaded the project into the portal.
But still its showing the same error:
"Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.ibm.test of Portal Component testing.test because: Could not find implementation class"
Any solution.....
Message was edited by: Debasish Sarkar

Problems redeploying portal logon par file

Hi,
We customized the portal logon page within a custom par file and modified the authschemes.xml to make it work.
Once it worked on our DEV portal we moved the par file to the QA environment.
At this point the par file is having problems and doesn't execute. When we change the Authschemes.xml the portal even crashes because it tries to execute the custom par file and it fills up the log files.
The only difference in the deployement I could get from the log files it that it doesn't create a "work" directory during the deployement in QA while it does in DEV.
Any reasons why the par file would work in DEV and not in QA?
the portal releases and patch levels are exactly the same.
Thanks,
Johnny

Hi,
1. create ur custom parfile
2. change all occurences of the the old par file name with the new custom parfile name in authschemes.xml.
3. <b>delete or rename com.sap.portal.navigation.masthead.par.bak</b>
3. move the new custom parfile to the PCD location
4. <b>delete the .bak file of new parfile or old parfiles if any</b>
5. restart the portal.
check whether there are any discrepancies in authschemes.xml while changing the name of old parfile.
Hope this helps
Thanks,
Praveen
PS. Dont forget to reward point if useful/solved.

Problem with KM Scheduler par file

Hi,
I created a KM Scheduler project and uploaded the par file. It was making use of few jar files.
I have just uplaoded the par file and still not set the scheduler time. When I see the default trace logs, I am able to see that
the below info is getting printed repeatedly..say within an interval of half an hour.
#1.5 #12B0F00110060019000000500021505E000478929759A3E8#1258470906635#com.sapportals.wcm.crt.CrtClassLoaderRegistry#sap.com/irj#com.sapportals.wcm.crt.CrtClassLoaderRegistry#Guest#0##n/a##de131140d38b11decc1112b0f0011006#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/Applications/KMC/CRT#Plain###loader was already registered -> replacement: oldLoader = com.sapportals.portal.prt.util.ApplicationClassLoader~18281828~com.sapportals.portal.prt.util.ApplicationClassLoader~18281828(/usr/sap/PN3/JC44/j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/portal/portalapps/5_MailServiceScheduler/lib/sqljdbc.jar;/usr/sap/PN3/JC44/j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/portal/portalapps/5_MailServiceScheduler/lib/MailServiceSchedulerapi.jar;/usr/sap/PN3/JC44/j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/portal/portalapps/5_MailServiceScheduler/lib/com.sap.portal.runtime.system.clusterinformation_api.jar;) -> newLoader = com.sapportals.portal.prt.util.ApplicationClassLoader~2dc12dc1~Com.sapportals.portal.prt.util.ApplicationClassLoader~2dc12dc1(/usr/sap/PN3/JC44/j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/portal/portalapps/MailServiceScheduler/lib/sqljdbc.jar;/usr/sap/PN3/JC44/j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/portal/portalapps/MailServiceScheduler/lib/MailServiceSchedulerapi.jar;/usr/sap/PN3/JC44/j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/portal/portalapps/MailServiceScheduler/lib/com.sap.portal.runtime.system.clusterinformation_api.jar;)#
My guess is that in the above line it is just picking up the jar files. But I want to know why it is trying repeatedly to pick up the jar files??
Kindly help me out of this.
Regards,
Shilpa B.V
PS: Please note that in the above code pasted, I have replaced @ with ~ as it was giving soem trouble

Hi Detlev,
Thanks for your help.
But I did not rename the par from "5_MailServiceScheduler" to "MailServiceScheduler, I am confused now.
And I completely agree on your statement that portal has to be restarted as KM does not support hot deployment. BUt my doubt is even before the KM went down, the message got printed in the log file several times..Why this strange behaviour??
Also, could you please let me know how to reference the jar files via portalapp.xml.
Regards,
Shilpa B.V

Problem Deploying PAR file to EP 6.0 SP2

I downloaded the latest SAP .Net PDK and I am trying to deploy the PAR file to EP 6.0 (SP2 patch 4 hotfix 5 running on HP11). The error message that I'm getting isn't telling me a whole lot. Has anyone else had trouble deploying from a windows system to the portal running on UNIX?
Message from the VS2003 output window.
Build...
Build PDKTest : Done -
Creating temporary directory...
Create Temp dir at C:\Documents and Settings\User\Application Data\SAP Portal\ep_deploy_6182e22f-c7e8-4e88-862d-44ac1ab27822
Copy file c:\User\_Net\SAPPDKTest\PDKTest\bin\PDKTest.dll
Copy file c:\User\_Net\SAPPDKTest\PDKTest\bin\PDKTest.pdb
Copy file C:\Documents and Settings\User\Application Data\SAP Portal\ep_deploy_6182e22f-c7e8-4e88-862d-44ac1ab27822\PORTAL-INF
PortalComponent1.ascx
Handle Ascx File ...
Handle Ascx File C:\Documents and Settings\User\Application Data\SAP Portal\ep_deploy_6182e22f-c7e8-4e88-862d-44ac1ab27822\PORTAL-INF\PortalComponent1.ascx
Handle Ascx File : Done -
Creating portalapp.xml ...
ComponentName = PortalComponent1
AscxName = PortalComponent1.ascx
Properties Added :
Creating portalapp.xml : Done -
Creating par zip file ...
Creating par zip file C:\Documents and Settings\User\Application Data\SAP Portal\ep_deploy_6182e22f-c7e8-4e88-862d-44ac1ab27822\PDKTest.par
Deploy to portal...
Portal: DEV Portal
Host: dev
Port: 50000
UserName: Administrator
Upload failed. Check details and try again.
Delete C:\Documents and Settings\User\Application Data\SAP Portal\ep_deploy_6182e22f-c7e8-4e88-862d-44ac1ab27822
Delete temporary directory : Done -
Deployment failed.------
Message from the event log.
General Information
Additional Info:
1) Exception Information
Exception Type: SAP.Portal.Design.Settings.PortalException
Message: Upload failed. Check details and try again.
CallingDeployEngine: SAP.Portal.Design.Settings.PortalEngine
TargetComponent: C:\Documents and Settings\User\Application Data\SAP Portal\ep_deploy_97af9999-7efe-403b-aef3-083cdf6be082\PDKTest.par
TargetSite: Void UploadPar(System.IO.FileInfo)
HelpLink: NULL
Source: SAP.Portal.Design
StackTrace Information
   at SAP.Portal.Design.Settings.PortalEngine.UploadPar(FileInfo parFile)
   at SAP.Portal.Design.Settings.PortalEngine.Deploy(FileInfo parFile)
   at SAP.Portal.Design.Settings.PortalEngine.Deploy(String filePath)
   at SAP.Portal.Design.Deployment.DeployManager.DeployToPortal(String parPath)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Thank you for the reply.
I was hoping that wasn't the case, because now I will have to wait until we deploy SP9, which could be quite a while.
In the meantime will the old PDK for .Net (Pre-SP1) work with the older Service Packs? I couldn't find it out on the SAP site. The only one I could find was the SP1 version of the SAP .Net PDK.
-pt

PAR file import problem in NWDS

Hello All,
Some time back we had developed a custome masthead component for our portal (EP 6, SP 21).
It has been deployed into the portal and its running fine.
now, we need to change some thing in that and so we have downloaded the par file and imported in nwds for code modification.
once we do that we get the masthead.jsp file but unable to get the class files and the beans.
what we doubt is while deploying the par the code was not deployed in the portal.
do you have any idea how can we get the code base out of that ?
p.s we dont have any other code base.
Thanks
Anirban

Hi Anirban,
If you uncheck and deploy the PAR file, later you can download it from portal. But the source code will not be available i.e src.api and scr.core will not be available.
1.unzip the jar file in portalINF/lib.
2. Run the java decompiler tool on each unzipped folder.
3. create another folder and move .java files and rename it.
Hope this might be helpful.
Thanks,
Subashini.

Problem in JNDI Lookup of Deployable Proxy from the logon par file

Hi,
I have customized the Logon par file and have a functionality to call a webservice when the Password Reset happens.
<b>from the ResetPassword.jsp , SAPMLogonLogic.java is getting called ,and there is a method called performResetPassword().</b>
I am calling a Deployable Proxy in that method by using the below code,
<b>Gateway objGateway=(SMSGateway)ctx.lookup("java:comp/env/MailProxy");
MailGatewayViDocument objSMSGatewayViDocument=(MailGatewayViDocument )objGateway.getLogicalPort("wsPort_Document",MailGatewayViDocument.class);
objMailGatewayViDocument.sendMail(...);</b>
I am getting the Exception,
<b>com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/MailProxy.</b>
I have deployed the Deployable Proxy in the J2EE Engine and add this API Jar as the External Library (Project >Properties>Java Build Path ---> Add External jars...Added the .jar file generated in the Proxy Project).
<b>Please let me know the possible solutions where i can call a deployable proxy inside the logon par file</b>.
Thanks and Regards,
Sekar

Hi,
I have fixed this error by changing the lookup as follows.
InitialContext ctx=new InitialContext();
Gateway objGateway=(Gateway)ctx.lookup("wsclients/proxies/sap.com/GatewayProxy/com.ms.sap..GatewayProxy");
Just open Visual Administrator and look for the path under wsclients for proper naming.
Thanks and Regards,
Sekar
Edited by: Sekar M on Jan 16, 2008 6:10 PM

Problem Undeploying a PAR file

Similar Messages

Maybe you are looking for