Skip to Content
avatar image
Former Member

JSP based PCR on EP 7.3

Hi,

I am on 7.3 EP Portal and trying to use old JSP PCR forms on this portal. I migrated all of the standard and custom par files to ear files.  I have added PCRUtiles.jar file to the standard par file and then converted to ear file.

I have deployed following ear files on portal:

com.sap.pct.fin.isrprocessevent.ear

com.sap.pct.fin.isrstatusoverview.ear

com.sap.pct.hcm.hcm_util.ear

com.sap.pct.hcm.htmlparser.ear

com.sap.pct.hcm.isrdispatcher.ear

com.sap.pct.hcm.objectanddataprovider.ear

com.sap.pct.hcm.orgmanagementeventing.ear

com.sap.pct.hcm.pcrteamviewernew.ear

com.sap.pct.hcm.pcrutilities.ear

com.sap.pct.hcm.teamviewer.ear

But after deploying I am getting following error:

[EXCEPTION]

java.lang.ClassCastException: class com.sap.pct.hcm.util.pcrutilities.PCRBundleBean:sap.com/com.sap.pct.hcm.pcrutilities@com.sap.engine.boot.loader.ResourceMultiParentClassLoader@3a06b6b4@alive incompatible with interface com.sapportals.portal.prt.component.IPortalComponent:library:tc~epbc~prtc~api@com.sap.engine.boot.loader.ResourceMultiParentClassLoader@69ae8935@alive

at com.sap.portal.prt.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:191)

at com.sap.portal.prt.broker.PortalComponentItem.load(PortalComponentItem.java:371)

at com.sap.portal.prt.om.ObjectsManager.craeteObejctHandle(ObjectsManager.java:221)

at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:141)

at com.sap.portal.prt.broker.PortalAppBroker.getPortalComponent(PortalAppBroker.java:374)

at com.sap.portal.prt.component.PortalComponentContext.getPortalComponentApp(PortalComponentContext.java:115)

at com.sap.portal.prt.component.PortalComponentContextFactory.createPortalComponentContext(PortalComponentContextFactory.java:188)

at com.sap.portal.prt.component.PortalComponentContextFactory.getPortalComponentContext(PortalComponentContextFactory.java:82)

at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:442)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:201)

at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

Can we somehow get this deployed to EP 7.3 Portal?

Regards,

Nitesh

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Apr 23, 2013 at 01:11 PM

    Nilesh ~  Hope your NW 7.3 portal is operating smoothly. Were you able to successfully migrate JSP based PCR's to NW 7.3? What was the experience in terms of procedure / time taken etc.? We are in the process of upgrading our portal landscape to NW 7.3, and are experiencing problems running our JSP based PCR's in NW 7.3 Sandbox.

    From what I can tell, the PAR migration tool is able to migrate the pars, but when I start-up a standard / custom PCR via NWA I see an error (Implicit stopped (dependency failed). The actual logged error is pasted below. The root cause of our problems appears to be due to a utilility ear "com.sap.pct.hcm.hcm_util" which was missing after NW 7.3 upgrade. I grabbed copy of this utility from Dev and migrated / deployed it in Sandbox. The system for some reason does not recognize this util is deployed.

    Just wondering if you recall noticing this type of issue during your NW 7.3 upgrade project, and if so what you did to resolve them. Appreciate any information you can share in regards  to this issue, and other PCR related issues.

    Application sap.com/com.sap.pct.hcm.orgmanagementeventing cannot be started. Reason: it has hard reference to the following resources, which are currently not available on the system: hard to SAPPORTAL/com.sap.pct.hcm.hcm_util (public) (f=true, cl=true); .
    In order to start the application, components...
    Add comment
    10|10000 characters needed characters exceeded

    • Hi Jalpa ~ See my responses your questions below.

      1)

      Do we need to have any particular MSS business package installed on R/3 side if we are using java based MSS services , which is the correct evrsion of business package ?

      For compatibility information suggest you refer the NW 7.3X upgrade master guide. We also found the posting below helpful in deciding which version of MSS BP's are compatible with Java based services.

      http://scn.sap.com/community/netweaver-portal/blog/2012/03/30/my-experience-on-portal-73-upgrade-migration--essmss-business-packages

      2)

      Currently I am getting error similar to you in standard sap file , so do you suggest I first convert this .par file into .ear and include needed jar files and then it should work fine ? there is no need of having correct business package in R/3 system for MSS iviews to work correctly on portal 7.3?

      a) Yes, we used migration tool to convert PCR par fles to ear, included relavant jars in the ear, applied some of the lessons we learned from migrating custom HTMLB based apps to resolve JSP errors. The error you pasted is most likely because com.sap.pct.hcm.hcm_util application is not running. Check and make sure this app is running.

      One more thing I would like to add is, PCR's are not supported in NW 7.3X, so we had to try several things to get the PCR's working as an interim solution till we moved to Webdynpro ABAP based forms.

      Hope this helps

  • avatar image
    Former Member
    Aug 05, 2013 at 12:05 PM

    Hi,

    Did you do this correctly.

    http://help.sap.com/saphelp_nw73/helpdata/en/49/e5da938df228fce10000000a42189c/content.htm

    http://help.sap.com/saphelp_nwce71/helpdata/en/45/01c80ff35624dee10000000a114a6b/content.htm

    Procedure

           1.      Navigate to System Administration __MCE_ITEM__® Support __MCE_ITEM__® Support Desk, and then click Portal Runtime.

           2.      Click PAR Migration Tool.

           3.      Select the file to convert, and then click Migrate.

    The file is converted, and a link to the file is displayed. Click the link to download the file.

    You can now deploy the file using the Deploy View of the NetWeaver Developer Studio.

    Regards,

    Johan

    Add comment
    10|10000 characters needed characters exceeded