Java file missing in par file

Hi all,
We have a par file. After importing that par file in NWDS we could see only jsp pages. No Java file exists. 
This par file is downloaded from our portal which is created by previous developer. I think previous developer did not selected "Include Source code" option while exporting par file to portal.
Now we need to changes in R/3 side and in java file. For that we need to know the Function Module or Report used in R/3. I think this data will be in java file. 
Can anybody let me know how to find the java file related to a par file?
Regards,
Swapna.

Hi Bobby/n@v!n,
Thank you for the inputs given.
But I heard that we cant get the same java file (like original) when we use the Java Decompiler. We will get the file which gives the same output with different code. I'm not sure if we can the use the file given by java decompiler.
Is there any other way to get the original java file of given par file?
Regards,
Swapna.

Similar Messages

  • Download Presenter trial in your website but when I published object scorm in zip file miss some important file such as ismmanifest.xml. In fact Moodle upload is wrong! Is it a bug or what? Thank you.

    Download Presenter trial in your website but when I published object scorm in zip file miss some important file such as ismmanifest.xml. In fact Moodle upload is wrong! Is it a bug or what? Thank you.

    You can publish Adobe Presenter Projects to your Moodle LMS (this will work for many other LMS’ too.)Please follow the steps as mentioned in the blog linked below.
    https://blogs.adobe.com/presenter/2013/08/step-by-step-how-do-i-publish-my-presenter-cours e-to-my-learning-management-system.html#more-6260
    Regards,
    Rajeev.

  • PAR file missing in PAR selection list during iView creation

    Hi Gurus
    I created a jsp file and exported it through NWDS export option. But i dont get this par while iView creation. Its present when i searched in the support desk . Can anybody tell me the steps how to create a simple jsp in NWDS and test the same in Potal as iViews.
    Thanks in advance

    Hi,
    Use NWDS wizards:
    1) File -> Mew Project -> Portal Application -> Create a Portal Application Project
    2) Right click on the project you created -> New -> Other -> Portal Application Project -> Create a new Portal Application Object
    3) Select Portal Component -> JSPDynPage
    4) Write your code ...
    5) Deploy the par file & create iview from it.
    Omri

  • How to read an XML file from embedded PAR file?

    I have an XML file that has been included in the PAR file as a means of storage (instead of hosting it to a web server).  Is there a way to read this file from within a java iView?  I have tried various methods without much luck.  (I can't seem to locate the file in the portal repository like I could with htmlb's Image class.
    Any thoughts?
    Thanks

    Hi,
    try this one:
    File myxmlFile = new File(portalRequest.getPrivateResourcePath(),"Path/to/my/file/after/PORTAL-INF/myfile.xml");

  • Class file missing from war file deployment

    I have a web application that is being deployed to a war file. I have deployed several times successfully. Then with the latest changes, there is a class file that does not get included into the war file. It does get compiled and does exist in the project directory.
    The class file is in a seperate project from the project where the war file deployment profile is; however both projects are in the same workspace.
    There are several other classes in the project that contains the missing class file that does get included in the war file. I don't see anywhere in the profile where these files are selected individually.
    I'm at a loss as to how to fix this problem other than add the file after deployment.
    Appreciate any help or ideas...
    Keith...

    Hi Keith,
    You may want to follow this thread....
    class object missing from ear file
    Brigette

  • File missing from Sender File Adapter

    Hi,
    I have got some serious issue in the production environment where the file picked up by the J2EE Sender File Adapter has disappeared and I can't see any trace in sxmb_moni, adapter engine monitoring, integration server monitoring within the Message Monitoring.
    I have tried increasing the log to 1 in the sxmb_adm-->integration server configuration, still no help.
    Can somebody please suggest where should I look at.
    TIA.
    Ranjan Koirala
    The issue was that I was using a separate queue name and somehow the queue was corrupted thats why the message was not going anywhere.
    Message was edited by: Ranjan Koirala

    Ranjan,
    Incase you are trying to find out what happened to your message, one option could be to use the JMS commands - in particular 'JMS LIST DEADMSGS'. this command i believe lists the destinations for all the dead message on the server.
    regards,
    Sapknowledge

  • Importing a PAR file ---- not able to retrieve java class files(components)

    hi all....
    i've gota .par file....which i imported into NWDS.
    i can find all da files except the component classes i.e java class files...in the corresponding packages.
    can anyone help me.....
    thanx in advance....
    regards,
    Sudheer

    Hi Sudheer,
    you do not need the NWDS to find out what's in a PAR file. Basically, PAR files are ZIP archives. Rename the the PAR file (change the suffix to ".zip") and open it with your standard archive tool (WinZip, WinRar, etc.)
    Best regard,
    Martin

  • Installation of CM fails(par files deployed but connection to database fail

    Hi,
    I have just installed CM EP6 SP2 on an old sandbox system (which has been upgrade from SP0 I believe), and I have some problems. The installation went fine untill I got the error message "CJS-00276  The upgrade failed.  The installation report file cf_installation.report does not exist.  Check the log files under the server directory and, if necessary, contact your local support center." But  I, at least now, find the file but this is probably from my installation of CM SP2 Patch4 and CM SP2 Patch4 hf8 (I was hoping the installation of them would clear the problem).
    I believe the problem is that there are missing some files under the SAPPRT share (
    server\SAPPRT\EPS1\global\config\cm), this because it was giving some error messages earlier about it. I was running the portal under localsystem user, which hasn't got the possiblity to have access to share's. (I would get an exception about access denied from the file system when starting it up, but after changing the user I don't).
    Under
    server\SAPPRT\EPS1\global\config\cm the portal has created the following folders:
    Backups
    config
    etc
    reports
    <b>Are there any one missing ?</b>
    (to resolve the problem I tried create the following folders, but still the same problem:
    system/updateQueue/events
    system/command
    system/deployment/archives
    system/deployment/upgrades
    utilities/connection_pools/db_type/default)
    The property files in \usr\sap\EPS1\j2ee\j2ee_01\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\system\cm
    look correct, and also the file under portalapps/com.sap.portal.km.application (or something).
    When I went into KM configuration in the portal, I noticed there were no JDBC connection pools, and I therefore created two as described in http://help.sap.com/saphelp_ep60sp2/helpdata/en/eb/d10ef2b6a311d5993900508b6b8b11/content.htm
    But that is something which the installer should have done for me. (and still the connection pools won't start)
    The main error message I get at startup is the following:
    Jun 28, 2005 4:45:17 PM      com.sapportals.config.queue.UpdateQueueService [System_Thread_12] Warning": There was a problem initializing the queue service for config manager : configuration plugin for queue service not found (/system/updateQueue/events)
    java.lang.RuntimeException: Failed to init. connection pool configuration: Failed to init. connection pool configuration: missing configurable /cm/utilities/connection_pools/db_type/default
         at com.sapportals.wcm.util.jdbc.connectionpool.JDBCConnectionPoolManager.initConfig(JDBCConnectionPoolManager.java:566)
         at com.sapportals.wcm.util.jdbc.connectionpool.JDBCConnectionPoolManager.getInstance(JDBCConnectionPoolManager.java:99)
         at com.sap.workflow.util.config.WorkflowProperties.initProperties(WorkflowProperties.java:188)
         at com.sap.workflow.util.config.WorkflowProperties.<init>(WorkflowProperties.java:48)
         at com.sap.workflow.util.config.WorkflowProperties.getInstance(WorkflowProperties.java:56)
         at com.sap.workflow.es.portal.WFPortalService.init(WFPortalService.java:74)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1470)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1426)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1383)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:371)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:765)
         at com.inqmy.services.servlets_jsp.server.WebApplicationStarter.run(WebApplicationStarter.java:57)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    java.lang.NullPointerException
         at javax.naming.NameImpl.<init>(NameImpl.java:250)
         at javax.naming.CompositeName.<init>(CompositeName.java:223)
         at com.inqmy.services.jndi.implclient.OffsetClientContext.parse(OffsetClientContext.java:129)
         at com.inqmy.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:200)
         at javax.naming.InitialContext.lookup(InitialContext.java:345)
         at com.sap.workflow.util.ejbfactory.EJBFactory.getUserTransaction(EJBFactory.java:282)
         at com.sap.workflow.es.portal.WFPortalService.init(WFPortalService.java:83)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1470)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1426)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1383)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:371)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:765)
         at com.inqmy.services.servlets_jsp.server.WebApplicationStarter.run(WebApplicationStarter.java:57)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    And if I go to content administration->KM content I get the following stack trace:
    java.lang.RuntimeException: Failed to init. connection pool configuration: Failed to init. connection pool configuration: missing configurable /cm/utilities/connection_pools/db_type/default
         at com.sapportals.wcm.util.jdbc.connectionpool.JDBCConnectionPoolManager.initConfig(JDBCConnectionPoolManager.java:566)
         at com.sapportals.wcm.util.jdbc.connectionpool.JDBCConnectionPoolManager.getInstance(JDBCConnectionPoolManager.java:99)
         at com.sapportals.wcm.repository.runtime.CmSystemInfo.createDBConnection(CmSystemInfo.java:221)
         at com.sapportals.wcm.repository.runtime.CmSystemInfo.checkDB(CmSystemInfo.java:138)
         at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:226)
         at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:161)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:81)
         at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:260)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:736)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:909)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1470)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1426)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1383)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:371)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:765)
         at com.inqmy.services.servlets_jsp.server.WebApplicationStarter.run(WebApplicationStarter.java:57)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    com.sapportals.wcm.repository.ResourceException: CM Startup failed: CM startup failed: Failed to init. connection pool configuration: Failed to init. connection pool configuration: missing configurable /cm/utilities/connection_pools/db_type/default
         at com.sapportals.wcm.repository.ResourceException.fillInStackTrace(ResourceException.java:401)
         at java.lang.Throwable.(Throwable.java:85)
         at java.lang.Exception.(Exception.java:33)
         at com.sapportals.wcm.WcmException.(WcmException.java:78)
         at com.sapportals.wcm.WcmException.(WcmException.java:74)
         at com.sapportals.wcm.util.content.ContentException.(ContentException.java:42)
         at com.sapportals.wcm.repository.ResourceException.(ResourceException.java:251)
         at com.sapportals.wcm.repository.runtime.CmAdapter.makeStartupResourceException(CmAdapter.java:397)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:84)
         at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:260)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:736)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:909)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1470)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1426)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1383)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:371)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:765)
         at com.inqmy.services.servlets_jsp.server.WebApplicationStarter.run(WebApplicationStarter.java:57)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    javax.servlet.ServletException: CM Startup failed: CM startup failed: Failed to init. connection pool configuration: Failed to init. connection pool configuration: missing configurable /cm/utilities/connection_pools/db_type/default
         at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:111)
         at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:300)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:190)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:209)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:576)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:300)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:190)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:669)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:209)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:532)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:832)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1245)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    I appreciate any help !
    PS sorry for the unstructured post, but I am hungry and want to go home now.

    The files under the SAPPRT share had somehow failed (some where there, but a lot of the important ones where missing).
    I found out that these files were in .configarchive files in the par files to be deployed, and manually unpacked them using these two commands
    $ for file in `ls -1 .par` ; do unzip $file ".configarchive" -d extracted >> logfile.txt ; done
    $ for file in `ls -1 *.configarchive` ; do unzip -o $file -d extracted >> logfile.txt ; done
    Afterwards I had to make some tiny customization (search for %[a-zA-Z]% , especially for the connection pools.
    Then a restart, and most of it seems to work (the system will not live much longer so that is acceptable)

  • How to get the source code in PAR file

    Hi All,
    I used the PAR migration tool to migrate from PAR to EAR file. When I imported the EAR into NWDS 7.3, I was just able to see the structure and jsp files and could not find the java source code files. I would requires the java source code to make modifications so that deprecated APIs can be replaced and to also make the code compatible with JDK 1.6.
    I think the original 7.0 PAR file itself does not contain the source code. I decided to use the "Include source code" option when exporting the 7.0 PAR.
    I have the portal application DC project in my NWDS 7.0. However, when I try to export the PAR file using Export --> PAR File -- > Next... I am unable to select any project from the list. The list appears blank with disabled Next & Finish buttons.
    I also noticed that in the portal DC application structure, there is a .sda file under /gen/default/deploy. Also there is no PAR folder under /gen/default/public.
    How do I include the source in the PAR file so that I can edit the same after migrating to EAR format ?
    Regards,
    Melwyn

    DC and PAR/EAR stuff are different formats, SC/DC is an archive type used by NWDI, if I got it right.
    How do I go about generating the PAR file (with source) ?
    In fact through including the seources while creating the PAR/EAR in NWDS, but: no need to do that, you can also depack SDA (rename it to zip). If you wanna just see the Java sources you will find them there, otherwise decompile as Vijay already sad.
    cheers

  • Write into a Par file.

    I need to create a file on the fly in my java code and store it , but I dont want to store it on the server ..
    Where would I store it in the par file?
    How would I do it?
    thanx for your help.
    rajesh

    What kind of file do you need to create and why. You won't be able to store the file in the PAR file, as once the PAR file is uploaded it no longer exists. If I knew what you wanted to do then perhaps I can advise you further
    D

  • 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

  • PAR file from NWDS

    Hello,
        I'm attempting to change a couple of the images on the log on page by adding them into the PAR file using a project in NWDS. After making the changes, which I believe I have done correctly, in order to create the new par file I've used the export PAR file option. I then rename the new file to our our existing filename and pass it to our BASIS team who have tried to deploy it using SDM. For some reason it won't load. (I have manually added the 2 JAR files so that is not the problem). Any ideas about what is wrong ? Any help would be appreciated.
    Much obliged,
         Phil.

    Hello
    Check while creating the PAR file again after uploading the images,
    is the par file created correctly or not?
    is there any custom jar files added previously when the login par has created.
    make sure all jar files added in PAR file while building PAR.
    If PAR file generated successfully then try to deploy from System Admin as mentioned by above reply.
    Cheers
    Chinmaya
    reward for Helpful answers.

  • Layout Par file name not appearing in list while creating new Layout

    Hi
    I downloaded com.sap.portal.layouts to modify the light_framework page to suit my needs, renamed it to com.mycomp.portal.layouts, modified the page, created a par file and uploaded it thru NWDS.
    When I go to the portal to create a new Layout, I do not see my custom par file in the list.
    I have even uploaded it from the portal: System Administration -> Support -> Support Desk -> Portal Runtime -> Administration Console -> Archive Uploader. Even after it was successful, I was not able to see the par file listed while creating a new Layout.
    How do I get my Layout par file listed do i can create my Layout?
    Thanks
    J

    Hi Bala
    I never had a problem with the JAR files in this par file while opening, nor did I have to manually add anything.
    I know it has been successfully uploaded in the portal, as I can see my par file in the Archive Deployment Checker.
    What could be wrong? Is there something else I have to put in the portalapp.xml to make it visible in the list?
    Thanks
    J

  • How to extract a PAR File

    Hi All,
    In the procedure of changing the Portal Logon / Logoff page ,we need to extract Par file ,modify the extracted files and then put them back,can somebody tell me how to extract a PAR file ,wt is the procedure of tat.
    Regards,
    Saumya

    Hi Saumya,
    First you need to retrieve the logon PAR file from the portal file system.The file is found in your EP instance,which is located at ..
    /usr/sap/<instance>/j2ee/j2ee_00/cluster/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/deployement/pcd
    -The file that you need is called sap.portal.runtime.logon.par.bak.
    copy this file to your local directory and rename the PAR file(for eg. my.new.logon.par).It is necessary to remove the .bak extension.
    -Next you can open the PAR file and modify the appropriate files.
    -put modified files back into PAR file
    -copy the new par file back into the deployement directory
    and restart the portal to see ur changes.
    Also look at the following threads for more info -
    <a href="https://www.sdn.sap.com/irj/sdn/message?messageID=2758339">https://www.sdn.sap.com/irj/sdn/message?messageID=2758339</a>
    <a href="https://www.sdn.sap.com/irj/sdn/message?messageID=2225096">https://www.sdn.sap.com/irj/sdn/message?messageID=2225096</a>
    Regards,
    Abhishek
    (Reward Points if useful)
    Message was edited by:
            Abhishek Mehra

  • Fetching Portal Server Time in Par file

    Hi All,
    I had a requirement where i am customizing the Masthead par file and the client wants Time on the Masthead, that should be from portal Server. I could successfully show the time on masthead using javascript but that time is from client system.
    But my client wants the time of Server.
    Please help me in this.
    Regards
    Raghu

    Hi Micheal,
    First of all thanks for replying me.
    Let me clear my requirement.
    Now i am modifying Headeriview.jsp file in Masthead par file.
    In this when i instantiate new Date(). This will fetch me client system date, but not server date.
    Can u please ellaborate your answer.
    Thanks
    Raghu

Maybe you are looking for