Portal Application Standalone is grayout

Hi Expert,
I want to create the Portal Application Standalone type project but this option is grayed out..
Please find the screen shot ..
I have added the the required SCA file to SC and imported into Track.
Please find the list of sca that i added and please help what is missing..
Regards,
Nitin

Please look into the following SCs as well..
COMP_BUILDT
ECM-CORE
ENGFACADE
ENGINEAPI
ESCONF_BUILDT
FRAMEWORK
MOIN_BUILDT
SAP_BUILDT
WD-RUNTIME
EP_BUILDT
EP-BASIS
EP-BASIS-API
EP-RUNTIME
WD-RUNTIME-EXT
EP-CONNECTIVITY
FRAMEWORK-EXT
WDEXTENSIONS

Similar Messages

No automatic deployment for Portal Application Standalone DC?

Hi Experts,
     I created a Portal Application Standalone DC under NWDI track.
     I checked in the code and activate my request, the log showed that this DC had beed sucessfully built. BUT, I can not find this portal application had beed deployed. it seems that EP DC can not be deployed automatically
    I searched SDN and there are some topics about this problem, it seems that EP DC can not be deployed automatically, we need to deploy the DC manually, is it right?
   Thanks!
segement of my build log:
[pppacker] WARNING: Could not determine correct package of package folder for entity (portalapplication-api/Class, src.api/)
[pppacker] Packed   0 files for entity (portalapplication-api/Class, src.api/)
[pppacker] Packed   3 files for entity (portalapplication-core/Class, src.core/)
     [timer] Portal Application libraries packaging finished in 0.389 seconds
createApplication:
      [echo] create PAR..
       [jar] Building jar: /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/t/80B8A4CDC19F36C272AD330774CF8FF0/com.hcm.isr.newtemplate.par
createPublicParts:
      [echo] Public Part: API
[pppacker] Packing public part 'API'
[pppacker] Packed   0 files for entity Portal API (Portal API)
[pppacker] Packed 1 entity for public part 'API'
     [timer] Public part packaging finished in 0.114 seconds
createDeployArchive:
      [echo] Creating portalapp-dd.xml
       [cda] Preparing archive for deploy unit "default"
       [cda]   deployment type: "J2EE"
       [cda]   explicit modules:
       [cda]     /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/t/80B8A4CDC19F36C272AD330774CF8FF0/com.hcm.isr.newtemplate.par
       [cda]
       [cda] Creating Ant build file: /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/DCs/test/isrformtemp/_comp/gen/default/logs/buildDeployArchive.xml
       [cda]
       [cda]
       [cda] Creating descriptor META-INF/application.xml ...
       [cda]
       [cda] Creating descriptor META-INF/application-j2ee-engine.xml ...
       [cda] Adding module "com.hcm.isr.newtemplate.par" with container type "PortalRuntimeContainer".
       [cda]
       [cda] Collecting modules...
       [cda] Adding module 'com.hcm.isr.newtemplate.par' from current development component
       [cda] Ant build file creation finished in 0.119 seconds
packDeployArchive:
[srcpacker] Creating source archive
[srcpacker] No sources available for packing, no archive will be created.
     [timer] Source archive creation finished in 0.008 seconds
    [dcinfo] Creating deploy archive info
    [jarsap] Info: JarSAP version 20060908.1630
    [jarsap] Info: JarSAPProcessing version 20070423.1630 / JarSL version 20070906.1830
    [jarsap] Building: /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/DCs/test/isrformtemp/_comp/gen/default/deploy/test~isrformtemp.sda with compression
     [timer] JarSAP finished in 0.461 seconds

The Standalone DC has a deployable result (opposed to the Module DC) and should thus be deployed when an activity is successfully activated. Is automatic deployment perhaps disabled?

Deployment of Portal Appln Standalone DC

Hi All,
I've created a DC of type 'Portal Application Standalone'. I also created a DC of type 'External Library' for use by the former DC. Upon building the former DC, I see that the sda file is created with the par file within it.
Under Development configuration tab in NWDS, I checked in both the above-mentioned DCs and activated them.Shouldn't this have deployed the DC to the Dev server? I've verified that there are runtime systems configured in NWDI with deploy option checked.
I tried to locate my application from System Administration ->Support>Portal Runtime>Browse Deployment/Admin Console etc..but don't see it there.
Do I have to release the activity for it to deploy?
Also, I tried to right click and deploy the DC myself from the Dev Config perspective in NWDS. but i got an error saying 'sdm host is empty'. I've already set the host under Windows>Preferences>SAP EP. The port i set here is not the sdm port, but 500xx where xx is the instance no.
I was able to create a portal app and deploy it using the 'deploy par' option with the above settings. Am I missing any additional config configuration for DC deployment (am sure we hv to set the sdm port etc somewhere).
I'll appreciate if someone can help guide me on this.
Thanks!

Hi,
if you are using the track from the same server that u have the EP set up, then u dont have to release the activity. just activating it would deploy it in the server.
and the sdm host has to configured in the "windows-> preferences-> SAP J2EE Engine" option.
Hope this helps.
Prabu J.

Configuring Standalone Proxy with Enterprise Portal Application

Hi All,
I am attempting to set up a standalone proxy DC for use inside of an enterprise portal application DC (deployable). I successfully created the standalone proxy and I created an API public part as well as an SDA public part, both of which contain all of the classes from the standalone proxy. In my deployable portal application, I have included both of these public parts in the Used DCs. At compilation, everything is fine, and NWDS recognizes the API and does not give any errors with references to the proxy classes while coding or building the application. However, after deploying and running the application, I receive a NoClassDefFound error for the proxy classes at runtime. I have worked with using APIs/SDAs a lot in other types of DCs (EARs, WebDynpro, etc.), and simply including the SDA as part of the used DCs has always worked fairly simply, however I am still relatively new to using Portal Application DCs, so I am not sure if I am doing something incorrectly in this situation. Any light you could shed on the situation would be a great help. Thanks.

Hello-
I believe you need to do the following. In your standalone DC, create two public parts, one for compiliationand one for assembly (the two radio buttons on the first screen when you create public part wizard).
Then in your PAR Standalone DC, reference both public parts as used DCs. The jar file from the Standalone Proxy DC will be packaged into the EP Build results and deployed with the PAR file.
Let me know if this works for you.
Thanks,
Marty

Consume an existing WebService over an SAP Portal Application

Hi all,
I would like to consume an existing Web service, which has been implemented under AXIS 4 1 and deployed to a tomcat 4.1 installation.
I've developed an SAP Portal application with NWDS (Dynpage-Structure), which has to call this web service. For this, I've generated a standalone proxy client over WSDL of this WebServie under WebServiceWizard of NWDS and called it from my Portal Application, without success :(. But when i call it (proxy) from a standalone java client (Class with main-Method), it function.
Can anybody help me, for calling this WebService
Regards
Ahmet Büyükyilmaz

Hi Ahmet,
open a browser on your portal server (or try telnet) to check if you can access your axis server. Seems like you have some firewall or routing probs.
Just enter your web service uri in address bar of the browser to see if you can get a connection. If you do not have a browser, try:
'telnet <axis-server-name> 80'
from command line. Does anybody listen?
Is your web service designed to be used by anybody? Or do you have some kind of authorization issues?
HTH,
Carsten

Packaging portal application

How to package a portal application into a single file and deploy in Weblogic Portal
in 7.0.

The Standalone DC has a deployable result (opposed to the Module DC) and should thus be deployed when an activity is successfully activated. Is automatic deployment perhaps disabled?

Error while Creating a basic portal application using JDeveloper

Hi,
I am trying to build a portal application using the following tutorial on JDeveloper 11.1.1.5.0 on Windows XP.
[http://download.oracle.com/docs/cd/E17904_01/webcenter.1111/e10273/createapp.htm#CCHEGDIC|http://download.oracle.com/docs/cd/E17904_01/webcenter.1111/e10273/createapp.htm#CCHEGDIC]
I have configured all the prereqs for this tutorial. When i run the application, following message appears on the log file.
Target Portal.jpr is not runnable, using default target index.html.
and the webpage contains following error
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
+10.4.5 404 Not Found+
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
Following is the WLS log for the application run.
+[12:53:24 PM] ---- Deployment started. ----+
+[12:53:24 PM] Target platform is (Weblogic 10.3).+
+[12:53:24 PM] Retrieving existing application information+
+[12:53:24 PM] Running dependency analysis...+
+[12:53:24 PM] Deploying 3 profiles...+
+[12:53:28 PM] Wrote MAR file to C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\NTSL_PORTAL\AutoGeneratedMar+
+[12:53:31 PM] Wrote Web Application Module to C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\NTSL_PORTAL\NTSL_PortalWebApp.war+
+[12:53:32 PM] Info: Namespace '/oracle/adf/share/prefs' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/lifecycle/importexport' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/lock' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/rc' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/persdef' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/shared/oracle/wcps' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/xliffBundles' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/search/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/framework/scope/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/page/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/pageDefs' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/adf/portlet' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/adf/portletappscope' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/doclib/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/portalapp' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/security/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/siteresources/shared' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Namespace '/oracle/webcenter/quicklinks/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[12:53:32 PM] Info: Any customizations created while running the application will be written to 'C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.mds.dt\adrs\NTSL_PORTAL\AutoGeneratedMar\mds_adrs_writedir'.+
+[12:53:35 PM] Wrote Enterprise Application Module to C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\NTSL_PORTAL+
+[12:53:35 PM] Deploying Application...+
+<Jul 25, 2011 12:53:44 PM GMT+05:00> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.apps.common.resource, referenced from: C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\tmp\_WL_user\oracle.webcenter.framework\owur7d]. Make sure the referenced optional package has been deployed as a library.>+
+<Jul 25, 2011 12:53:53 PM GMT+05:00> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-app in the deployment descriptor in C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\tmp\_WL_user\jaxrs-framework-web-lib\829i9k\WEB-INF\web.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>+
+<ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.+
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
+<EclipseLinkLogger> <basicLog> 2011-07-25 12:54:27.409--ServerSession(28900695)--PersistenceUnitInfo ServiceFrameworkPUnit has transactionType RESOURCE_LOCAL and therefore jtaDataSource will be ignored+
+<ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.+
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
+<LoggerHelper> <log> Cannot map nonserializable type "interface oracle.adf.mbean.share.config.runtime.resourcebundle.BundleListType" to Open MBean Type for mbean interface oracle.adf.mbean.share.config.runtime.resourcebundle.AdfResourceBundleConfigMXBean, attribute BundleList.+
+[12:54:48 PM] Application Deployed Successfully.+
+[12:54:48 PM] Elapsed time for deployment: 1 minute, 24 seconds+
+[12:54:48 PM] ---- Deployment finished. ----+
Run startup time: 84155 ms.
+[Application NTSL_PORTAL deployed to Server Instance IntegratedWebLogicServer]+
Target URL -- http://127.0.0.1:7101/mytutorial/index.html
+<JUApplicationDefImpl> <logDefaultDynamicPageMapPattern> The definition at NTSL.portal.portal.DataBindings.cpx, uses a pagemap pattern match that hides other cpx files.+
+<NavigationCatalogException> <<init>> oracle.adf.rc.exception.DefinitionNotFoundException: cannot find resource catalog using MDS reference /oracle/webcenter/portalapp/navigations/default-navigation-model.xml Root Cause=[MDS-00013: no metadata found for metadata object "/oracle/webcenter/portalapp/navigations/default-navigation-model.xml"] [Root exception is oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/oracle/webcenter/portalapp/navigations/default-navigation-model.xml"]+
+<SkinFactoryImpl> <getSkin> Cannot find a skin that matches family portal and version v1.1. We will use the skin portal.desktop.+
+<Logger> <error> ServletContainerAdapter manager not initialized correctly.+
+[Application termination requested. Undeploying application NTSL_PORTAL.]+
+[01:04:42 PM] ---- Deployment started. ----+
+[01:04:42 PM] Target platform is (Weblogic 10.3).+
+[01:04:42 PM] Undeploying Application...+
+<Jul 25, 2011 1:04:42 PM GMT+05:00> <Warning> <Deployer> <BEA-149085> <No application version was specified for application 'NTSL_PORTAL'. The undeploy operation will be performed against the currently active version 'V2.0'.>+
INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
+<BPELConnectionUtil> <getWorklistConnections> The Worklist service does not have a ConnectionName configuration entry in adf-config.xml that maps to a BPELConnection in connections.xml, therefore the Worklist service was not configured for this application.+
+<NotificationSenderFactory> <getSender> Notification sender is not configured+
+<ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.+
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
+[01:04:48 PM] Application Undeployed Successfully.+
+[01:04:48 PM] Elapsed time for deployment: 6 seconds+
+[01:04:48 PM] ---- Deployment finished. ----+
+[Application NTSL_PORTAL stopped and undeployed from Server Instance IntegratedWebLogicServer]+
+[Running application NTSL_PORTAL on Server Instance IntegratedWebLogicServer...]+
+[01:05:40 PM] ---- Deployment started. ----+
+[01:05:40 PM] Target platform is (Weblogic 10.3).+
+[01:05:40 PM] Retrieving existing application information+
+[01:05:40 PM] Running dependency analysis...+
+[01:05:41 PM] Deploying 3 profiles...+
+[01:05:42 PM] Wrote MAR file to C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\NTSL_PORTAL\AutoGeneratedMar+
+[01:05:44 PM] Wrote Web Application Module to C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\NTSL_PORTAL\NTSL_PortalWebApp.war+
+[01:05:45 PM] Info: Namespace '/oracle/adf/share/prefs' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/lifecycle/importexport' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/lock' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/rc' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/persdef' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/shared/oracle/wcps' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/xliffBundles' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/search/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/framework/scope/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/page/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/pageDefs' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/adf/portlet' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/adf/portletappscope' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/doclib/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/portalapp' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/security/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/siteresources/shared' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Namespace '/oracle/webcenter/quicklinks/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.+
+[01:05:45 PM] Info: Any customizations created while running the application will be written to 'C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.mds.dt\adrs\NTSL_PORTAL\AutoGeneratedMar\mds_adrs_writedir'.+
+[01:05:47 PM] Wrote Enterprise Application Module to C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\NTSL_PORTAL+
+[01:05:47 PM] Deploying Application...+
+<Jul 25, 2011 1:05:52 PM GMT+05:00> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.apps.common.resource, referenced from: C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\tmp\_WL_user\oracle.webcenter.framework\owur7d]. Make sure the referenced optional package has been deployed as a library.>+
+<Jul 25, 2011 1:05:54 PM GMT+05:00> <Notice> <LoggingService> <BEA-320400> <The log file C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>+
+<Jul 25, 2011 1:05:54 PM GMT+05:00> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00003. Log messages will continue to be logged in C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>+
+<Jul 25, 2011 1:06:01 PM GMT+05:00> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-app in the deployment descriptor in C:\Documents and Settings\ahmedh\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\tmp\_WL_user\jaxrs-framework-web-lib\829i9k\WEB-INF\web.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>+
+<ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.+
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
+<EclipseLinkLogger> <basicLog> 2011-07-25 13:06:36.117--ServerSession(28713857)--PersistenceUnitInfo ServiceFrameworkPUnit has transactionType RESOURCE_LOCAL and therefore jtaDataSource will be ignored+
+<ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.+
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST
+<LoggerHelper> <log> Cannot map nonserializable type "interface oracle.adf.mbean.share.config.runtime.resourcebundle.BundleListType" to Open MBean Type for mbean interface oracle.adf.mbean.share.config.runtime.resourcebundle.AdfResourceBundleConfigMXBean, attribute BundleList.+
+[01:06:54 PM] Application Deployed Successfully.+
+[01:06:54 PM] Elapsed time for deployment: 1 minute, 14 seconds+
+[01:06:54 PM] ---- Deployment finished. ----+
Run startup time: 73985 ms.
+[Application NTSL_PORTAL deployed to Server Instance IntegratedWebLogicServer]+
Target URL -- http://127.0.0.1:7101/mytutorial/index.html
+<JUApplicationDefImpl> <logDefaultDynamicPageMapPattern> The definition at NTSL.portal.portal.DataBindings.cpx, uses a pagemap pattern match that hides other cpx files.+
+<NavigationCatalogException> <<init>> oracle.adf.rc.exception.DefinitionNotFoundException: cannot find resource catalog using MDS reference /oracle/webcenter/portalapp/navigations/default-navigation-model.xml Root Cause=[MDS-00013: no metadata found for metadata object "/oracle/webcenter/portalapp/navigations/default-navigation-model.xml"] [Root exception is oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/oracle/webcenter/portalapp/navigations/default-navigation-model.xml"]+
+<SkinFactoryImpl> <getSkin> Cannot find a skin that matches family portal and version v1.1. We will use the skin portal.desktop.+
+<Jul 25, 2011 1:11:04 PM GMT+05:00> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=DeploymentTaskSummaryPage&DeploymentTaskSummaryPortlethandle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DADTR-0%2CType%3DDeploymentTaskRuntime%2CDeployerRuntime%3DDeployerRuntime%22%29.>+

The below message comes when you don't specify any default file for your webcenter portal application and this should not be any problem.
Target Portal.jpr is not runnable, using default target index.html.
Can you answer to my questions:
1. Did you just created a new wcp application in jdev and ran it with out doing any changes? If you have done what are the changes?
2. How did you ran your application? (right clicking a particular page or right clicking your portal project and selected "run" option?

Portal application connecting backend SAP R/3 system

Hi All,
 I am developing one portal application through NWDS. It's JSPDYNPage component.The applications functionality is basicaly is to connect it to backend SAP R/3 system & fetch some data in aparticular table & display that data in a tableview format on one JSP& also when i click any row of the tableview then details of that row should get displayed on the next JSP. So i reached till develpoing a code that connnects to Backend SAP R/3.(Basicaly coding of connection part is done). Now i need to test this code, to check whether it is fine or not? NWDS doesnt give nay error, not compile also or not runtime error also. It simply shows the output as a blank page, where it is supposed to display one line of text in textview(i coded this in my JSP).But as i said it displays a blank page. i tried to debug the application , but debugging also not worked.I performed the debugging twice in right way. The code was not debugged, it run the same way as it normally runs when debugging is off & shown the blank page. I also have done all the the settings or prerequisites for debugging properly. I am stuck at this point now.search many documents , but no relevant help has been received. Can anyonehlep me with this. i am putting below the code for JSP, JSPDYNPAGE component as well as portalapp.xml. Can anyone guide me with this, whhere i am making mistake? what should i change in this?
JSPDYNPAGE code
package com.lti.portal;
//import java.util.ArrayList;
import com.sapportals.htmlb.*;
import com.sapportals.htmlb.enum.*;
import com.sapportals.htmlb.event.*;
import com.sapportals.htmlb.page.*;
import com.sapportals.portal.htmlb.page.*;
import com.sapportals.portal.prt.component.*;
import java.util.ArrayList;
import com.sap.mw.jco.IFunctionTemplate;
import com.sap.mw.jco.JCO;
import com.sun.corba.se.internal.core.Response;
public class Connection_R3 extends PageProcessorComponent {
public DynPage getPage(){
return new Connection_R3DynPage();
public static class Connection_R3DynPage extends JSPDynPage{
private Conn_R3 myBean = null;
public JCO.Client mConnection;
public JCO.Repository mRepository;
public ArrayList al = new ArrayList();
public String output;
public String Ans;
public static String BEAN_KEY="myBean";
public void doInitialization(){
IPortalComponentRequest request =(IPortalComponentRequest) this.getRequest();
IPortalComponentContext context = request.getComponentContext();
IPortalComponentProfile profile = context.getProfile();
//create & initialize the bean.
Conn_R3 test_bean= new Conn_R3();
test_bean.setans("3");
// put the bean into application context.
context.putValue(BEAN_KEY,test_bean);
conn();
//IPortalComponentResponse res = (IPortalComponentResponse)this.getResponse();
//for(int i=0;i<al.size();i++)
//res.write(" "+al.get(i).toString());
public void doProcessAfterInput() throws PageException {
public void doProcessBeforeOutput() throws PageException {
this.setJspName("Connection_R3.jsp");
public ArrayList conn() {
IPortalComponentRequest request =(IPortalComponentRequest) this.getRequest();
IPortalComponentContext context = request.getComponentContext();
IPortalComponentProfile profile = context.getProfile();
Conn_R3 sample_bean = new Conn_R3();
sample_bean.setans("5");
//context.putValue(BEAN_KEY, sample_bean);
//r3-accessing
//connect_to_r3();
try {
// Change the logon information to your own system/user
mConnection = JCO.createClient("800", // SAP client
"********", // userid
"******", // password
null, // language
"*******", // application server host name
"**"); // system number
mConnection.connect();
//System.out.println(mConnection.getAttributes());
mRepository = new JCO.Repository("ABC", mConnection);
} catch (Exception ex) {
ex.printStackTrace();
System.exit(1);
JCO.Function function = null;
JCO.Table codes = null;
try {
function = this.createFunction("ZSAMPLE");
if (function == null) {
System.out.println("ZSAMPLE" + " not found in SAP.");
System.exit(1);
String num1 = "7";
String num2 = "9";
//String ans;
function.getImportParameterList().setValue(num1,"My_import");
function.getImportParameterList().setValue(num2, "My_Import");
mConnection.execute(function);
Object name =function.getExportParameterList().getValue(Ans);
output=name.toString();
sample_bean.setans(output);
//sample_bean.setans(output)
//al.add(name);
//store values into strings
//pushing of values we get from r3 into awt
} catch (Exception ex) {
ex.printStackTrace();
System.exit(1);
disconnect_r3();
return al;
public void connect_to_r3() {
public JCO.Function createFunction(String name) throws Exception {
try {
IFunctionTemplate ft =
mRepository.getFunctionTemplate(name.toUpperCase());
if (ft == null)
return null;
return ft.getFunction();
} catch (Exception ex) {
throw new Exception("Problem retrieving JCO.Function object.");
public void disconnect_r3() {
mConnection.disconnect();
//**********************Code for BEAN****************************
package com.lti.portal;
import java.io.Serializable;
public class Conn_R3 implements Serializable {
public String answer;
public void setans(String a)
answer=a;
public String getans()
return answer;
///////////////////////Code for JSP*****************************
><%@ taglib uri= "tagLib" prefix= "hbj" %>
<jsp:useBean id="myBean" scope="application" class="com.lti.portal.Conn_R3" />
<hbj:content id="myContext" >
<hbj:page title="PageTitle">
<hbj:form id="myFormId" >
<hbj:textView
id="Welcome_message"
text="<%=myBean.getans()%>"
design="STANDARD" >
</hbj:textView>
</hbj:form>
</hbj:page>
</hbj:content>
/////////////////////////////////Portalapp.xml*****************************************
application>
<application-config>
 <property name="PrivateSharingReference" value="com.sap.portal.htmlb"/>
</application-config>
<components>
 <component name="Address_comp">
 <component-config>
 <property name="ClassName" value="com.lti.portal.Address_comp"/>
 </component-config>
 <component-profile>
 <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
 </component-profile>
 </component>
</components>
<services/>
</application>

Hi,
 Do onething, please refer this <a href="http://www.i-barile.it/SDN/JCoTutorial.pdf">JCo Tutorial</a> as well as <a href="http://www.apentia-forum.de/viewtopic.php?t=1962&sid=9ac1506bdb153c14edaf891300bfde25">Link</a> also.
Regards,
Venkatesh. K
/* Points are Welcome */

Runtime Error in Portal Application

Can any body help me in resolving the following runtime error in portal application, (Netweaver Version : 7.0)
Full Message Text
03:21_21/09/11_0002_6275851
[EXCEPTION]
java.lang.NoClassDefFoundError: org.apache.commons.httpclient.methods.RequestEntity
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:69)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:131)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:152)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:540)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.httpclient.methods.RequestEntity
Found in negative cache

Hi,
this exception seems caused by a missing interface org.apache.commons.httpclient.methods.RequestEntity. Please the following ones:
http://www.jarfinder.com/index.php/java/info/org.apache.commons.httpclient.methods.RequestEntity
Br,
Javier

Fetching data in R/3 via portal application(JSPDYNPage)

Hello Everyone,
I want to fetch data in R/3 server via portal application(JSPDYNPAGE) & display that data as an output of the portal application in TABLEVIEW format. Can anyone guide me on this (I:e-How to connect to R/3 server via portal component & fetch data & display the same). any similar application developed for a reference will be of great help.
Thanks,
Chetan

Hi Chetan,
I hope you know how to create a JSP Dyn Page, anyway I will explain it briefly.
Open NWDS->File->New->Create a portal application project->Specify the project name
right click on the project->New->Create a new portal application object->Portal component->Select JSP dyn page-(By default it creates class and all)->this is available under description on the right column-
Now goto the Java page->see the functions->attach zip and jar files(HTMLB plugin)
->Right click on the project->goto properties->Java build path->Add external jars->Select com.sap.portal.htmlbbridge.zip and htmlb.jar
This is how JSP page is created.
Now we want to do establish connection with R/3. That I will discuss in the next session.
Award points if this was helpful......
All the best for you
Regards,
Arun Jacob.

SSO between Portal Application and Portal Admin Tool

Hi All,
We have a requirement for implementing SSO between a Portal application and
Portal admin tool.
We are using WL Portal 8.1 SP4.
Here is the reason for this requirement -
A user logged-into Portal Application needs to login to Portal Admin tool to
do some admin activity. We want to provide a link in the portal application
using which the user can directly login to the Portal Admin tool without
having to enter the credentials again.
If someone has any info on how to implement this, can you please point me in
the right direction.
Thanks,
~Deepak

Hi,
When creating PP you have 2 options
PP used for compiling and PP used for Building
You create PP with all the libraries into Developing/Compiling Other DCs
And another PP with all the libraries into can be packaged into other build results (SDAs).
Once you have these 2 PP in place you add the DC as used DC.
And this should resolve the issue.
Hope this helps.
Cheers-
Pramod

Portal application can't read request info

hi all,
i use portal application for change portal user's infos.but when i sent request info,
request.getServletRequest().getInputStream() method is cutting my sending line after 90. character.
in R3 side i use HTTP_POST function and fill request info (table paramater).
i tried to send 2 line(less than 90 character) in request info, but i can't read second line in java code.
Is IPortalComponentRequest accept only 90 character ?
how can i solve this problem , any idea ?
my code is below, variable "str" is filling only first 90 character;
     protected void doOnNodeReady(
               IPortalComponentRequest request,
               IEvent event) {
     String str = "";
     try {
          InputStream is = request.getServletRequest().getInputStream();
          InputStreamReader isr = new InputStreamReader(is);
          int c;
          while ((c = isr.read()) > -1) {
          str = str + (char) c;
            } catch (java.io.IOException ex) {
             str = "Error accessing input stream";
thanks

New discovery...If I shut down all instances of IE on my machine, then reopen my test form, it works. Once. The second time I try it I get the same peculiar behavior again, until I again shut down all instances of IE.

Access to Entity Service from Portal Application

Hi Experts,
I have a hybrid application which will be making use of both Web Dynpro and Portal Applications. I decided to use Entity Services to store my back-end data and can access it fine from the Web Dynpro project. I have included the public part of my CAF project into the Used DCs of my Portal project and while I am able to call the methods of the Entity Service at compile time, at runtime I receive an error message on the page:
An exception occurred while processing a request
I know in order to get this to work for Web Dynpro I had to include sap.com/tccolapi.sap.com/cafruntimeuicouplingapilib as a Library Reference and a few Used DCs, but while I have added the Used DCs to the Portal project, I am unsure of how to add the Library Reference. I assume this has to be added to portalapp.xml, but I don't know the syntax.
Could somehow please reply with how to do this and whether this is all that is required in order to call Entity Service methods from Portal applications?
Thanks,
JP

Hi Smith,
Write click on the Project then goto the Properties=>Webdynpro References=>Library references
add
caf/eu/gp/api
sap.com/cafruntimeuicouplingapilib
And add the following DC in your project.
1> External in caf/eu/gp/api (CAF domain)
2> caf/eu/gp/api/wd (CAF domain)
3> com.sap.security.api.sda (SAP-JEE)
portalapp.xml
<?xml version="1.0" encoding="utf-8"?>
<application>
<application-config>
<property name="SharingReference" value="usermanagement, knowledgemanagement, landscape, htmlb, exportalJCOclient, exportal, SAPJ2EE::library:cafeugp~api"/>
</application-config>
<components/>
Check this thread .
Using CAF GP API in Portal Application project
Regards,
Mithu

Portal Search doesn't work in Portal Applications forum.

Portal Search doesn't work in Portal Applications forum.

Hi,
Can you mention what exactly is not working?
Thanks,
Vanathi

Code generate report in excel format from portal(Application Server)

Hi all
Please give some solution with code generate report in excel format from
oracle portal(Application Server).

Not feasible.
Why? Because "the Excel format" is a binary and proprietary Microsoft file format. And writing a generator to generate Excel files will be complex, and resource expensive. In the vast majority of cases this will not be justified.
As an alternative the very basic Microsoft XML office format can be used. But note that this is not a a ISO standard (it has been shot down in flames) - and effort and resources for that would be better spend on the Open Document XML standard (which very likely will be ratified as the ISO standard instead).
Of course, you could have meant a CSV file - in which case, you need to play close attention to details. CSV is not an Excel format. A software designers and developers, our success is determined by attention to technical detail. In which case you are not paying any attention to technical detail by confusing CSV with Excel.

Portal Application Standalone is grayout

Similar Messages

Maybe you are looking for