Skip to Content
0
Nov 21, 2012 at 10:21 AM

NW 7.3 custom portal application migration

80 Views

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: http://scn.sap.com/docs/DOC-22884

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/com.sap.security.core (public) (f=true, cl=false); hard to SAPPORTAL/com.sapportals.htmlb (public) (f=true, cl=false); hard to SAPPORTAL/com.sap.tc.webdynpro.services (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
  • com.sap.security.api.jar
  • com.sap.security.core.jar
  • exception.jar

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

<application-config>    <property name="SharingReference" value="usermanagement, landscape, htmlb, exportal"/>    <property name="startup" value="true"/>    <property name="PrivateSharingReference" value="SAPJ2EE::library:com.sap.security.api,com.sap.security.core,com.sap.tc.webdynpro.services,com.sapportals.htmlb,"/>  </application-config>

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

Thanks,

Jürgen