Showing results for 
Search instead for 
Did you mean: 

NW 7.3 custom portal application migration

0 Kudos

Hello Experts,

I'm currently trying to migrate some custom portal applications to NW Portal 7.3. Since I'm completely new to SAP NW Portal developement, I tried to follow this SAP How-To:

Deploying the newly created EAR file works, but when the application is started I get the following warning:

Application XYZ cannot be started. Reason: it has hard reference to the following resources, which are currently not available on the system: hard to SAPPORTAL/ (public) (f=true, cl=false); hard to SAPPORTAL/com.sapportals.htmlb (public) (f=true, cl=false); hard to SAPPORTAL/ (public) (f=true, cl=false);

I needed a bunch of different JAR files for the applications, which I added to the build path. But I don't really understand how to add those references to the portalapp.xml file. The jars I need in this case are

  • tc~je~usermanagement~api.jar
  • _webdynpro_services.jar
  • bc.rf.framework_api.jar
  • bc.sf.service.scheduler_api.jar
  • bc.util.public_api.jar
  • exception.jar

The <application-config> part of my portalapp.xml looks like this:


    <property name="SharingReference" value="usermanagement, landscape, htmlb, exportal"/>

    <property name="startup" value="true"/>

    <property name="PrivateSharingReference" value=",,,com.sapportals.htmlb,"/>


I don't really know what to do here, so any help would be greatly appreciated!



Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos
As it turned out, the problem we had did not come from wrong references, but from using a class that is not part of NW 7.3 anymore. By changing the implementation and using instead of we were able to resolve the issue.

Answers (1)

Answers (1)

Active Contributor
0 Kudos

you can find these jars in the following location depending on where u installed ur NWDS

C:\Program Files\SAP\IDE\IDE70\eclipse\plugins

0 Kudos

Thanks for your reply. I already found the JARs I need and added them, but my problem is how I have to reference them in the portalapp.xml file so that they can be found at run time.