Start a portal application

How could I start a portal application within a DynPage ?
Thanks for any feedback or/and help
Regards.
Altafin

Hi Altafin,
even if the part "launching the other iview within the same portal application" does not really makes sense (did you mean: launching the other iview within the same place?), I think I get closer.
Do you have to implement the logic on client or server side? If it's enough to do all checks on client side, use for the button onClientClick. Within the called method, you can redirect to a NavigationTarget. Maybe these threads help: How to open another iView in the same window and/or URL of the current portal page loaded using Javascript ?
If you have to do some calculation on the server side, you could also use onClientClick, but this time call an AbstractPortalComponent and implement the logic in doOnNodeReady, then redirect (IPortalComponentRequest.redirect(String URI)).
Hope it helps
Detlev

Similar Messages

  • Error while starting the Portal application server

    Hi ,
    We are running EP 7 on SP12 on HP-UX1 1.31 with Oracle.
    this a strange problem that we are facing.When we try to restart the Application sever it never starts up until we take a restart of the CI as well.
    The default trace writes
    m.sap.engine.core.Framework#######Thread[Thread-1,5,main]
    ##0#0#Fatal#1#/System/Server#Plain###Critic
    al shutdown was invoked. Reason is: Error getting confirmation reply
    during attach to cluster.#
    #1.#0019BBEBBF0E00000000001E00002348000442F5B31BE7CE#1199522946212#com.sap.engine.core.Framework##co
    m.sap.engine.core.Framework#######Thread[Thread-1,5,main]
    ##0#0#Fatal#1#/System/Server#Plain###Critic
    al shutdown was invoked. Reason is: Error getting confirmation reply
    during attach to cluster.#
    #1.#0019BBEBBF0E00000000001700002885000442F61C903BE6#1199524715444#com.sap.engine.core.service630.co
    ntainer.LoadContainer##com.sap.engine.core.service630.container.LoadContainer#######Thread[Thread-1,
    5,main]##0#0#Error#1#/System/Server#Plain###interface
    tclmctcculinterface_sda - null jars, incor
    Has anyone come across same error??
    If we restart the CI then everything starts up well.
    Regards,
    rohit

    Hi,
    We are facing the same problem.
    Can you help me out with this??
    Thanks & Regards,
    Arpita Saini

  • 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?

  • Message bean does not start automatically during application server startup

    I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
    Thanks,
    Bill
    #1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
    #1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
    #1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
    #1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
    #1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
    #1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
    #1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
    #1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
    #1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    ... 12 more
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
    Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
    #1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
    #1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
    java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                    at java.lang.Class.getDeclaredConstructors0(Native Method)
                    at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                    at java.lang.Class.getConstructor0(Class.java:1930)
                    at java.lang.Class.newInstance0(Class.java:278)
                    at java.lang.Class.newInstance(Class.java:261)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                    at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                    at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at javax.security.auth.Subject.doAs(Subject.java:379)
                    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
    I've could change that yes, but the startup script doesn't seemed to have this mind.
    Regards,
    Sve

  • Error in executing new webcenter portal application

    Hi
    i am getting error in executing new webcenter portal application, even while executing existing webcenter portal application.Installed all necessary bundles.And my installation is under OR_MW_1 folder.
    [Running application SmartSystems on Server Instance IntegratedWebLogicServer...]
    [11:29:32 AM] ---- Deployment started. ----
    [11:29:32 AM] Target platform is (Weblogic 10.3).
    [11:29:33 AM] Retrieving existing application information
    [11:29:33 AM] Running dependency analysis...
    [11:29:33 AM] Deploying 3 profiles...
    [11:29:33 AM] Wrote MAR file to C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\SmartSystems\AutoGeneratedMar
    [11:29:34 AM] Wrote Web Application Module to C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\SmartSystems\PortalWebApp.war
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] 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.
    [11:29:34 AM] Info: Any customizations created while running the application will be written to 'C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.mds.dt\adrs\SmartSystems\AutoGeneratedMar\mds_adrs_writedir'.
    [11:29:35 AM] Wrote Enterprise Application Module to C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\SmartSystems
    [11:29:35 AM] Deploying Application...
    <May 6, 2013 11:29:36 AM IST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.apps.common.resource, referenced from: C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\tmp\_WL_user\oracle.webcenter.framework\owur7d]. Make sure the referenced optional package has been deployed as a library.>
    <May 6, 2013 11:29:37 AM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1367819975651' for task '2'. Error is: 'weblogic.management.DeploymentException: '
    weblogic.management.DeploymentException:
         at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
         at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.webcenter.lifecycle.listener.FeatureMetricApplicationListener
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
         at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
         Truncated. see log file for complete stacktrace
    >
    <May 6, 2013 11:29:37 AM IST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\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.>
    <May 6, 2013 11:29:37 AM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00003. Log messages will continue to be logged in C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
    <May 6, 2013 11:29:37 AM IST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'SmartSystems [Version=V2.0]'.>
    <May 6, 2013 11:29:37 AM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.management.DeploymentException:
         at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
         at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.webcenter.lifecycle.listener.FeatureMetricApplicationListener
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
         at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
         Truncated. see log file for complete stacktrace
    >
    [11:29:37 AM] #### Deployment incomplete. ####
    [11:29:37 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    #### Cannot run application SmartSystems due to error deploying to IntegratedWebLogicServer.
    [Application SmartSystems stopped and undeployed from Server Instance IntegratedWebLogicServer]

    Have you included libraries for this ?
    java.lang.ClassNotFoundException: oracle.webcenter.lifecycle.listener.FeatureMetricApplicationListener

  • Error while running the portal application

    Hi All,
    I have made one sample portal application in Sun Java Studio Enterprise 8.When I build this application it is successfully build.Now when I start the server of Sun Java Studio Enterprise 8 and try to run the project ,the browser opens and gives the following error::
    HTTP Status 404 - /portlet/
    type Status report
    message /portlet/
    description The requested resource (/portlet/) is not available.
    Sun-Java-System/Application-Server
    If anyone having idea about this problem then please let me know.All suggestions are welcome.
    Thanx and Regards,
    Chirag.

    OK, so they are not in the mood for posting on the forum today :-)
    They suggest three things.
    1) Restart the server. Deploying a portlet requires some configuration changes, which will take effect only after the server is restarted. Thus if it failed to restart due to some reason...
    2) Try deleting the JSE userdir and trying again.
    3) If the above two items do not help. Start the studio with the following command:runide.exe -J-Dcom.sun.tools.ide.portletbuilder.log=log,info try the deployment and either post here or email the output which will be output to the console.
    HTH,
    Kirill

  • Portal application connecting to backend R/3 system

    Hi All,
               i am developing one portal application through NDS(Netweaver Developer Studio) that connects to backend SAP R/3 system & fetches some data in R/3 system. I started working on it & developed some code, which i want to test whether it is working fine or not.I:e- code to connect to SAP R/3, but when i run the application it doesnt give any error but also it doesnt show any output which it should display(value of output parameter of RFC). Below is the code for component, code for JSP & code for bean. Can any one tell me what is the error in this? or why i am not getting the output i desired. All the connection parameters supplied in the coding are correct. Now below i mentioned these parameters as *, bt in actual i have mentioned them correct. I checked them twice, they are fine.
    Code for Component
    [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>

    Hi Chetan,
    Connection to R/3 systems through Portal can be done in many ways. Since you have mentioned that you are using jspdynpage then its better that you use JCo for connecting to R/3 system.
    U can write the JCo code using the jspdynpage component. I hope you have pdfs related to JCO. Incase u dont have then give me you mail id. OK
    Another approach could be developing a web dynpro java application that access a r/3 table using a BAPI. You can a dynpro model to easily connect to R/3 system.
    Just develop an iview based on this web dynpro application. And finally navigate to this iview through your jspdynpage.
    I hope this helps you in some way
    Regards,
    Prasanna

  • Error in portal application for sending email.

    Hi experts,
    I am trying an portal application which sends email .
    I took the the reference from the following blog,
    [Sending attachments in mails|Sending attachments in mails]
    While running the application the program is terminating with
    an error in the   Transport.send(message);   statement in the above blog
    I have put the mail.jar and activation.jar files in the private lib under portal inf
    Please provide me with any suggestions or any relevant documents.
    Fruitful solutions will be rewarded
    Thanks

    You can use this code for Achiving Sending of mail,
    import java.io.*;
    import java.util.*;
    import sun.net.smtp.SmtpClient;
    public class SMTP extends Thread{
         public String whoto;
         public String username;
         public String whofrom;
    /* our constructor */
    public SMTP(String whoto, String username, String whofrom){
              this.whoto = whoto;
              this.username = username;
              this.whofrom = whofrom;
    /* run method for multithreading */
         public void run(){
              doGet();
         public void doGet( )
         try {
              SmtpClient smtp =
                               new SmtpClient("yourdomain.com");
              smtp.from(whofrom);
              //Pass the email address of the recipient of the
              // message to the next method.
              smtp.to(whoto);
           //Get an output stream for the message
              PrintStream msg = smtp.startMessage();
              //Write the message header in the output stream.
              msg.println("To: "+whoto);
              msg.println("Subject: New Email");
              msg.println();
              //Write the text of the message in the output
              // stream
              msg.println("An event has happened.");
              msg.println("Please do not reply to this automated email.");
           //Close the stream and send the message
              smtp.closeServer();
         }catch( Exception e ) {
           e.printStackTrace();
    This method is called by:
    IUser loggedOnUser = (IUser) request.getUser().getUser()
    SMTP mysmtp = new SMTP(whoto, loggedOnUser.getName(), whofrom);
    mysmtp.start(); // starts the thread
    Cheers!!
    SJ

  • How to create custom template for webcenter portal application

    Hi,
    I created webcenter portal application in my jdev using the webcenter portal application template provided by the webcenter framework.
    I tried to create custom template for my application by following steps:
    1. Created new application using webcenter portal application template with all default package structure.
    2. Right click pagetemplates folder under webcontent package and select new option.
    3. New gallery opens up.
    4. Selected JSF under webtier and JSF Page Template under items in the right hand side and clicked Ok button.
    5. New wizard opens up for creating new JSF page template.
    6. Gave template name(file name) and Page Template Name(template def name).
    7. Selected checkbox staing start a Quick Start Layout and selected three column layout and selected Ok.
    8. Selected checkbox for Create Associated ADFm Page Defination(so that page templates can be changes at run time).
    9. Created some Facet Definations (header, footer, content1, content2, LHN, RHN).
    10. Clicked Ok button which will create custom template.
    11. Added some Panel Group Layout component from Component Palette.
    12. Created new page (.jspx) with this template.
    Now when I try to add producer portlets created using Producer Portlet application template and connected to the above application using WSRP2.0, I'm facing problem.
    The prolem is that I'm not able to add more than one portlet in one single page?
    Kindly let me know whether the steps followed by me is wrong some where and needs to corrected and let me know how I can add more than one portlet to page?
    Basically I cant see more than one placeholders in my page to add portlets.

    Thanks Yannick.
    In the step 9 I had mentioned that I created various facet definations (header, footer, content, content1 RHN and LHN).
    Is this is not facet you are talking about or should I drop facet ref from the resource palette?
    Can't I add moer than one portlet to my page at design time itself?
    Annoying since in weblogic portal we do this at design time(.portal).

  • Howto deploy content via portal application

    Hi all,
    currently i'm integrating some external web apps into my EP6.0 SP2. Therefore I use the application integrator plus some iview und system templates.
    I've developed the templates as components in a portal application in the portalapp.xml.
    But now I'm searching for a way to deploy not only the templates but also real content, e.g. instances of my templates with a portalapp.xml.
    At this time I must make the concrete iviews based on my templates by hand.
    Is there any doc outside the targets this approach? What I've found is the Portal Runtime Guide, whith an overview of portalapp.xml structure, but nothing concrete.
    Regards
        Steffen...

    Thanks for the reply ... here is the answer to your questions along with an update to some more information after trying something different
    Did you deploy the WebCenter Managed server from Jdeveloper
    I am deploying the application to the WebCenter Managed server from JDeveloper.
    What managed server did you deploy it to - a custom server that you created?
    Yes this is a custom Managed Server (called MindFlow). At the time of your response the only two servers up and running on WebCenter was the AdminServer and MindFlow.
    Did the deployment go through?
    Yes
    Are there any errors in the managed server log when you access the page?
    Yes these where the errors showing that it could not connect with the metadata via the repositories.
    Now for the update:
    I went ahead and started up the WLS_Portlet managed server that comes with WebCenter. When I did this I got the following error:
    WSM-04509: cannot initialize the connection to the data store
    I then deployed the Portlet Producer Application to the WLS_Portlet from JDeveloper. I then grabbed the url for the newly created portlet producer and updated the connection on the Portal application. After doing this and updating the portal.jspx file, I then deployed the Portal application to the MindFlow managed web server. I then brought up the portal.jspx page via a browser and was able to bring back results. The only issue now is that while doing this I got multiple MDS errors (including the initialize error above) and not sure if I can ignore these or not. One of the errors received was as follows:
    oracle.mds.exception.MDSException: MDS-01258: The value @MDS_CLASS for property class-name is invalid.

  • Starting a Web Application out of WAD from menue "Query/Execute" ...

    Dear colleagues,
    starting a Web Application (let's say its the template "BTMP_001") out of the Web Application Designer from menu "Query/Execute" starts the Web Query Analyzer instead of the Template "BTMP_001".
    The URL looks like: http://<xxxxx>.<yyyyyy>.<zzzzzz>.com:<Port>/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.pct!2fplatform_add_ons!2fcom.sap.ip.bi!2fiViews!2fcom.sap.ip.bi.bex?TEMPLATE=BTMP_001&DUMMY=0
    Does somebody have any hint? Why I allways get the Web Query Analyzer althoug the end of the URL shows the technical name of my web application?
    Thanks for any help!
    op

    Problem solved!

  • Tree structure of portal application in NWDS

    Hi all,
    Im new to portal applications and I did not under stand the tree structure that appears after we start portal application in ep perspective in NWDS. Especially the PORTAL-INF and src.code in the tree structure .If any body has any relevant information or document about it please send me.

    portal applications are same as the Web applications developed in Java, JSP ....
    PORTAL-INF is same as the WEB-INF in normal web application structure.
    in Web application we create .war file whereas here we create as .par file.
    in web application we have web.xml inside WEB-INF folder where as here we have portalapp.xml.
    src.core and src.api is used as the source code folder.
    You can check this in "Java Build path" if u go to the project properties.
    Hope this give u a small idea on portal files structure.
    cheers.
    Chinmaya
    Reward points for hellpful answers.

  • How to start default portal  in ECC 6.0

    Hi Experts ,
    I have installed ECC 6.0 (Netweaver 7.0) in my system, i want to use portal in that.
    How to start the portal or login to that ?
    Thanks
    Aisurya

    Hi,
    ECC is different and Netweaver is different. After installation,
    Create your WD ABAP application, and you have to integrate this into portal to open your WD application
    in portal.
    Web Dynpro for ABAP provides portal integration API. It allows to navigate from a Web Dynpro iView to any other iView. Below codesnip can be used to navigate to an SAP transaction iView and pass a parameter to one dynpro field.
    WE have different portal events to navigate to portal, we ahve to use them.
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/e4/f86f4132f15c58e10000000a1550b0/content.htm
    For portal Integration.. follow this..
    Web Dynpro for ABAP Portal Integration [original link is broken]
    Cheers,
    Kris.

  • How to stop and start (restart) portal services programmatically?

    Hi experts,
    I develop a portal service IMaintenanceService extending IService.
    The new service has some profile properties (start date, end end, etc.).
    I wrote another portal application MaintenanceManager which can change these profile properties.
    However, to activate the changes I have to restart the portal service.
    Does anyone know how I can restart the portal service IMaintenanceService from my portal application MaintenanceManager?
    Thanks for help.
    Edited by: Daniel Fötsch on Nov 21, 2011 8:24 AM

    please see the metalink note
    How to Start/Stop MWA Services Using Control Scripts adstrtal.sh/adstpall.sh? [ID 731320.1]
    This is how i startup and shutdown WMA
    for stopping :
    1) login to Applications tier
    2) To see if the MWA (telnet) server is running use:
    ps -ef|grep DPID
    3) cd $MWA_TOP/bin
    3) ./mwactl.sh -login sysadmin/xxxxx stop_force 10200;
    4) check the wma process from OS level
    ps -ef|grep mwa
    for starting
    1) login to Applications tier
    2) cd $MWA_TOP/bin
    3) ./mwactl.sh -login sysadmin/xxxxx start _force 10200;
    4) check the wma process from OS level
    ps -ef|grep mwa

  • Connection to R/3 system from a portal application

    hi
    I am trying to connect to the R/3 system through a portal application developed in Netweaver Developer Studio.
    Please tell what all are the prerequisites for that.
    I have created an alias in the portal for the R/3 system and named it as FIN, even though my program is not working.
    Are there any setting to be done in the portal
    kindly let me know.
    thanks
    kris

    hi Vadim
    Thanks for ur fast reply, I have implemented the same code that u have mentioned.herewith I am sending u the code that I have written.
    package com.keane.connection;
    import javax.resource.ResourceException;
    import com.sapportals.connector.connection.IConnection;
    import com.sapportals.portal.ivs.cg.IConnectorGatewayService;
    import com.sapportals.portal.ivs.cg.IConnectorService;
    import com.sapportals.portal.prt.component.AbstractPortalComponent;
    import com.sapportals.portal.prt.component.IPortalComponentContext;
    import com.sapportals.portal.prt.component.IPortalComponentProfile;
    import com.sapportals.portal.prt.component.IPortalComponentRequest;
    import com.sapportals.portal.prt.component.IPortalComponentResponse;
    import com.sapportals.portal.prt.logger.ILogger;
    import com.sapportals.portal.prt.runtime.PortalRuntime;
    public class SimpleSapConnection extends AbstractPortalComponent {
      public void doContent(IPortalComponentRequest request, IPortalComponentResponse response) {
         IPortalComponentContext myContext = request.getComponentContext();
         IPortalComponentProfile myProfile = myContext.getProfile();
         // get the default_logger
         ILogger logger = request.getLogger();
         logger.info("SimpleSapConnection: default logger initialized");
         String sapsystem = myProfile.getProperty("SystemIdentifier");
         response.write("SimpleSapConnection: the SystemIdentifier is: " + sapsystem + "<br>");
         IConnection connection = null;
         logger.info("Start to get a Connection to R/3");
         try {
           // get the Connector Gateway Service
           IConnectorGatewayService cgService = (IConnectorGatewayService) PortalRuntime.getRuntimeResources().getService(IConnectorService.KEY);
           if (cgService == null) {
              logger.severe("SimpleSapConnection: Error in get Connector Gateway Service");
              response.write("Error in get Connector Gateway Service <br>");
           try {
              connection = cgService.getConnection(sapsystem, request);
           } catch (Exception e) {
              logger.severe("SimpleSapConnection: Connection to SAP system failed");
              response.write("Connection to SAP system failed <br>");
           } finally {
              // !!!!Important! Connection pooling will not work if the connection object is not closed!!!
              // Next statement needs to be inlcuded in your coding always,
              // otherwise connections won't be reused.
              if (connection != null) {
                try {
                   connection.close();
                } catch (ResourceException e) {
                   e.printStackTrace();
           if (connection == null) {
              logger.warning("SimpleSapConnection: Connection is null");
              response.write("Connection is null <br>");
           } else {
              logger.info("SimpleSapConnection: Connection succesful");
              response.write("Connection succesful");
         } catch (Exception e) {
           logger.severe("SimpleSapConnection: Exception thrown" + e);
           response.write("Exception thrown" + e);
    I have created an R/3 system in the portal and named it as FIN with the same alias name as FIN.
    U please tell me what are the other things that we have to do in respect to get connection to R/3, how to configure the R/3 system in the portal and also in the NWDS.
    And also the portalapp.xml file i have created
    <?xml version="1.0" encoding="utf-8"?>
    <application>
      <!THIS FILE IS A COPY OF THE ORIGINAL VERSION STORED IN THE PCD. PLEASE DO NOT CHANGE IT!>
      <application-config>
        <property name="SharingReference" value="com.sap.portal.htmlb,      com.sap.portal.ivs.connectorservice, com.sap.portal.usermanagement,       com.sap.portal.usermapping, landscape"/>
        <property name="releasable" value="true"/>
      </application-config>
      <components>
        <component name="SimpleSapConnection">
          <component-config>
            <property name="ClassName" value="com.keane.connection.SimpleSapConnection"/>
            <property name="SafetyLevel" value="no_safety"/>
          </component-config>
          <component-profile>
            <property name="SystemIdentifier" value="FIN"/>
          </component-profile>
        </component>
      </components>
      <services/>
    </application>
    what I feel is that there is something wrong with the system I have created in the portal
    thanks
    krish

Maybe you are looking for

  • Is there a way to change the color of the Commenting indicator?

    Our company is utilizing the commenting feature more now in Adobe Acrobat X Pro.  This is an attempt to reduce printing on paper.  In one of our processes, people will use the comments listed in the Comments Panel to keep track of each note.  They ma

  • Why can't I log in app store? But I can log in my itune store~

    Same apple id. But I can only log in itune store. As much as I know they can use same apple id~

  • Exporting several projects at once

    Is there  a way to export multiple projects at once, or to create an export list such that it'll automatically export every project on that list sequencially?

  • Quicktime 4.7 file type association hijacking

    I've got a really annoying little problem after upgrading to 7.6: The update also updated quicktime ( to 4.7) with ALL file types associations active. Arrogant to say the least, but just a nuisance nothing more. Problem is that I can't change them ba

  • JHeadstart & MDA

    JHeadstart Team, Just wondering if you have considered taking an Model Driven Architecture (MDA) to building tools that facilitate generation of JHS applications. As it stands today, you have to use the Application Structure editor. In order to be ab