Deploying problems for portal sample

Hallo, I've just installed WebLogic Platform 7.0 with all components. I'm using
the tutorial to install the portal sample with BEA Portal.
I've created the new domain and the portalServer accordingly as the tutorial says.
When I'm trying to deploy the NewPortalWebApp to the portalApp enterprise application
I receive the following message:
UNABLE TO ADD MODULE: NewPortalWebApp TO APPLICATION DESCRIPTOR FOR: portalApp.
I had a look to the logs for the deployment and I noticed it adds several files
to the correct folders then it attempts sync and suceeds, it searches the portalApp
application descriptor, finds it but then it stops to continue deploying.
Where is the error?
Thanks for your nice support!
MarcoC

Quite likely the server on which you are deploying the application does not have
access to the internet. The application.xml descriptor file references the dtd
at java.sun.com.
Work around for this is to copy the dtd locally and change the reference in the
descriptor e.g,. application_1_3.dtd
file:///home/yourHomedir/dtds/application.dtd
"MarcoC" <[email protected]> wrote:
>
Hallo, I've just installed WebLogic Platform 7.0 with all components.
I'm using
the tutorial to install the portal sample with BEA Portal.
I've created the new domain and the portalServer accordingly as the tutorial
says.
When I'm trying to deploy the NewPortalWebApp to the portalApp enterprise
application
I receive the following message:
UNABLE TO ADD MODULE: NewPortalWebApp TO APPLICATION DESCRIPTOR FOR:
portalApp.
I had a look to the logs for the deployment and I noticed it adds several
files
to the correct folders then it attempts sync and suceeds, it searches
the portalApp
application descriptor, finds it but then it stops to continue deploying.
Where is the error?
Thanks for your nice support!
MarcoC

Similar Messages

  • Deploy questions for portal 7

    Hi, BEA portal gurus,
    I have several questions about Portal web application deployment.
    1. If I try to manually deploy a new portal web application(not using the
    wizard hot deployment), it seems that I have to take the following steps to
    make it work. First in the console, I need to modify the application
    descriptor and add a new web module. Second, I need to undeploy the whole
    enterprise application and redeploly the whole application. Is there any
    other easier way to do it? The redeployment of the whole application takes a
    long time.
    2. In http://edocs.bea.com/wls/docs70/webapp/deployment.html#139318, it
    explains a lot about web application deployment in weblogic server. In the
    secion "reploying a web application in exploded directory format", it says:
    ****You can redeploy a Web Application deployed in exploded directory format
    when using auto-deployment by modifying a special file called REDEPLOY, or
    you can use the Administration Console, or you can cause a partial redeploy
    by copying a new version of a class file over an old in the WEB-INF/classes
    directory.*****
    I am more confused than I was before I read this document. I think the first
    approach --- modify the REDEPLOY is not necessary, because when I modify a
    jsp or html in my portal web application, the server can pick it up right
    away. Of course, I change the jsp check interval setting. Besides, I never
    get the third appoach to work. Whenever I modify the classes and copy it to
    the WEB-INF/classes, the server can not do auto-redeployment for me. I have
    to restart the server, or redeploy the web application module in the console
    to make it work.
    Can anyone explain it to me? Thanks a lot in advance.
    Surge.

    Hi Kathleen,
    Please check message server settings on
    <u><i>visual admin tool:</i></u><b>server->kernel->cluster manager</b> and check <b>ms.host</b> and <b>ms.port</b> values from the table. At my first try, I thought the port number was 50000 since it was J2EE message port, after checking it in visual admin tool I realized that, it was the same port you use for local which was 3601.
    If this is still not working either then do it manually as follows:
    Copy your applicationName.ear file into your sever. The directory that you can find the .ear file is <b>C:\documents and settings\admin\documents\SAP\workspace\filename.ear</b>
    **Start your visual admin tool
    server->services->deploy
    on the right hand side you will see <b>server</b>->webdynpro
    ***On the right panel click on <b>deploy&start</b>
    I hope this will work for you,and please do not forget reward points if I could help you a little.
    Cheers,
    Serkan

  • IPv6 deployment problem for multiple site

    Dear Expert,
    I have a question about the deployment of IPv6 on two different site and the requirement is that client may need to auto switchover to another site while one of the ASR1002 is failure. I have using two different prefix on two sites with IPv6 stateless autoconfig like above diagram. Different prefix used for each site due to each site should use there own IPv6 prefix for Firewall Stateful(Default gateway point to local site firewall only). Client will retrieved two IPv6 addresses at the same time and it seems workable on Vista PC and Mac(Mac haven't select the High DRP one but work fine) and I haven’t try for other mobile device (have WiFi device for vlan100). Is it a valid solution? Any other solution for multiple site deploy IPv6 with Firewall no NAT enabled?
    Thank you very much!
    Regards,
    Kawaii

    One option would be to tweak the OS prefix policy table to prefer v4 to v6.  On Linux this is in /etc/gai.conf; on windows you'd run "netsh interface ipv6 set prefixpolicies ...".  The side effect would be that you'd only do v6 with the v6-only sites, not with the dual-stack sites.

  • EJB Deployment Problem for Stateless Session with Multiple ejbCreate

    In weblogic server if I use multiple ejbCreate with different parameters it is found
    to raise error with error message :
    <Error deploying application cart:
    Unable to deploy EJB: cart.jar from cart.jar:
         In EJB CartBean, the stateless session bean class must define a single ejbCreate
    method that takes no parameters.
         at weblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:256)
         at weblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:220)
         at weblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:453)
         at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:410)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:203)
         at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
         at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:676)
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:843)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.addComponent(Application.java:160)
         at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
         at ......
    Code example...
    public void ejbCreate() throws CreateException {}
    public void ejbCreate(String person) throws CreateException {
    // code here
    public void ejbCreate(String person, String id) throws CreateException {
    // code here
    the code above is found ok in J2ee Ref. Implementation and able to deploy. Why this
    is not deployable in Weblogic(tried in 6.1).is it a required condition for stateless
    session bean
    to have only single ejbcreate with no parameters ?
    Can somebody explain? and is there a way out to overcome this constraint if so in
    weblogic
    with regards
    Ganeshan Kalembeth

    Stateless session beans may define only a single create() method with no
    suffix
    and no arguments.
    Michael Jouravlev wrote:
    "Ganeshan Kalembeth" <[email protected]> wrote in message
    news:3ce28a88$[email protected]..
    In weblogic server if I use multiple ejbCreate with different parametersit is found
    to raise error with error message :
    <Error deploying application cart:
    Unable to deploy EJB: cart.jar from cart.jar:
    In EJB CartBean, the stateless session bean class must define a singleejbCreate
    method that takes no parameters.
    atweblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChecker.ja
    va:256)
    atweblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBCompli
    anceChecker.java:220)
    atweblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:453)
    at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:410)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:203)
    at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
    at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:676)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:843)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at ......
    Code example...
    public void ejbCreate() throws CreateException {}
    public void ejbCreate(String person) throws CreateException {
    // code here
    public void ejbCreate(String person, String id) throws CreateException {
    // code here
    the code above is found ok in J2ee Ref. Implementation and able to deploy.Why this
    is not deployable in Weblogic(tried in 6.1).is it a required condition forstateless
    session bean
    to have only single ejbcreate with no parameters ?
    Can somebody explain? and is there a way out to overcome this constraintif so in
    weblogic
    with regards
    Ganeshan KalembethRTFM EJB 2.0 Spec, chapter 7.8

  • Sample Adapter Deployment problem

    HI All,
                We have developed a Sample Adapter  in XI for a client requirement. Its working fine except a one problem that sometimes it does not work but when we re-deploy the same sample.sda file  through SDM , it starts working.  It's a weird behaviour of Sample Adapter.
               Sometimes it happens very frequently and when i re-deploy it , starts working.
               Does anyone face the similar problem before?
               And what might be the problem for this behaviour.
               I will be grateful to your replies.
    Regards,
    Anurag Garg

    Hi,
    Could you please let me know the process how to develop the Customized adapter?
    Thanks..

  • Deployment issues for WebService from DC problem

    I created a WebService from DC, deployed to NetWeaver successfully, but I canu2019t find the WebService from the WS Navigator.
    Here is my step-by-step procedure:
    1. Create an EJB Project from DC
    2. Create a Stateless Session Bean
    3. Create a WebService from the EJB
    4. Crate an Enterprise Application Project from DC and assign the EJB project into it.
    5. Deploy EAR file after building EJB and EAR
    6. After deploying the EAR file, I can find the EAR in Visual Administrator, but I didnu2019t find the WebService in WS the Navigator.
    7. Then I deployed again, I got the error message shown below.
    What should I do to make my WebService listed in the WS Navigator?
    2008/7/18 下午 12:06:21 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [ThreadDeploy Thread,5,main] ERROR:
    004Deployment aborted
    Settings
    SDM host : EADDEV01
    SDM port : 50018
    URL to deploy : file:/D:/DOCUME1/y_hungsy/LOCALS1/Temp/temp20894com.tsmcenginfosvcdemo1.ear
    Result
    deployment aborted : file:/D:/DOCUME1/y_hungsy/LOCALS1/Temp/temp20894com.tsmcenginfosvcdemo1.ear
    Aborted: development component 'enginfosvc/demo1'/'com.tsmc'/'IS2_APPL3_D'/'20080718120608'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application com.tsmc/enginfosvcdemo1.. Reason: Webservices common deployment exception! The reason is: Error occurred, trying to update web services for application com.tsmc/enginfosvcdemo1. . Additional info: none; nested exception is: java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to update web services for application com.tsmc/enginfosvc~demo1. . Additional info: none
    at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
    at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
    at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
    at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
    at com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate(WSDeployer.java:274)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
    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(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices deployment exception! The reason is: Error occurred, trying to generate web services deployment files for application com.tsmc/enginfosvc~demo1. . The error refers to application: none, jar: , web service: .
    at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
    at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
    at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
    ... 21 more
    Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, parsing com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application com.tsmc/enginfosvcdemo1, web service testDemo, location message: type: jar file, location: D:\usr\sap\IS2\JC00\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1216353976686\com.tsmcenginfosvc~demo1_ejb.jar . . Additional info:
    at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
    at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
    at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
    at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
    ... 23 more
    Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to parse documentation for web service testDemo. . Additional info:
    at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1590)
    at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDAndDocumentation(WSDefinitionFactory.java:1564)
    at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:814)
    ... 26 more
    Caused by: java.io.FileNotFoundException: .\temp\webservices\deploy\com.tsmc_enginfosvc_demo1\webservices\com1\com\tsmc\testDemoWsd.wsdef (The system cannot find the path specified)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    at com.sap.engine.lib.jar.JarExtractor.extractFile(JarExtractor.java:232)
    at com.sap.engine.services.webservices.server.deploy.ws.WSArchiveFilesLocationHandler.getWsdInputStream(WSArchiveFilesLocationHandler.java:184)
    at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1574)
    ... 28 more
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted

    As the log describes there is already an WS with the same name. Undeploy the ear whcih contains the WS and then deploy the new definition and you're on the way ...
    Regards,
    Daniel

  • Could not deploy policy for resource: type= url , application=MySecurex,

    Hi
    My situation :
    I have 2 managed weblogic portal 10.3.0 managed servers in a cluster and 1 admin server. All are running as a service.
    Deployments of new versions of applications are submitted by an automated script.
    The steps in the script are :
    - stop the services of the managed servers
    - undeploy the previous version by using ant task
    <target name="undeploy_old" description="undeploy old application" depends="downloadFiles">
                   <java classname="weblogic.Deployer" output="./temp/${buildProject}_${deployEnv}/${buildVersion}/undeploy.txt" fork="yes">
                        <arg value="-adminurl" /> <arg value="${adminurl}" />
                        <arg value="-username" /> <arg value="${weblogic_user}" />
                        <arg value="-password" /> <arg value="${weblogic_pwd}" />
                        <arg value="-undeploy" />
                        <arg value="-name" />
                        <arg value="${buildProject}" />
                        <arg value="-verbose" />
                        <classpath refid="project.class.path"/>
                   </java>     - deploy the new version by using ant task
         <java classname="weblogic.Deployer"
                   output="./temp/${buildProject}_${deployEnv}/${buildVersion}/deploy.txt"
                   fork="yes"
                   maxmemory="512m"
                   inputstring="" >
             <arg value="-adminurl" /> <arg value="${adminurl}" />
             <arg value="-username" /> <arg value="${weblogic_user}" />
             <arg value="-password" /> <arg value="${weblogic_pwd}" />
             <arg value="-stage" />
             <arg value="-verbose" />
              <arg value="-upload" />
             <arg value="-deploy" />
             <arg value="-name" /> <arg value="${buildProject}" />
             <arg value="-source" /> <arg value="./temp/${buildProject}_${deployEnv}/${buildVersion}/${buildProject}.ear" />
             <arg value="-targets" /> <arg value="${deploytargetinstances}" />
              <classpath refid="project.class.path"/>
         </java>- start the services of the managed servers
    Problem:
    When the managed servers are restarting and the new version is going to prepared status, an error occurs for the new version of the application :
    ####<27-dec-2011 13.42 u. CET> <Info> <Deployer> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758076> <BEA-149059> <Module MySecurexEarAdmin of application MySecurex is transitioning from STATE_NEW to STATE_PREPARED on server s40beaportacc1p9106.>
    ####<27-dec-2011 13.42 u. CET> <Error> <Security> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758779> <BEA-090064> <The DeployableAuthorizer "myrealm_weblogic.security.providers.xacml.authorization.XACMLAuthorizationProviderImpl" returned an error: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource.>
    ####<27-dec-2011 13.42 u. CET> <Error> <HTTP> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758779> <BEA-101199> <Could not deploy policy for resource: type=<url>, application=MySecurex, contextPath=/MySecurexEarAdmin, uri=/campaigns/emails/*.
    weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
         at com.bea.common.security.internal.service.PolicyDeploymentServiceImpl$DeploymentHandlerImpl.deployPolicy(PolicyDeploymentServiceImpl.java:173)
         at weblogic.security.service.WLSPolicyDeploymentServiceWrapper$DeploymentHandlerImpl.deployPolicy(Unknown Source)
         at weblogic.security.service.AuthorizationManager$HandlerAdaptor.deployPolicy(Unknown Source)
         at weblogic.security.service.AuthorizationManager.deployPolicy(Unknown Source)
         at weblogic.servlet.security.internal.ResourceConstraint.deploy(ResourceConstraint.java:108)
         at weblogic.servlet.security.internal.WebAppSecurityWLS.deployPolicies(WebAppSecurityWLS.java:253)
         at weblogic.servlet.security.internal.WebAppSecurity.registerSecurityConstraints(WebAppSecurity.java:140)
         at weblogic.servlet.internal.WebAppServletContext.prepareFromDescriptors(WebAppServletContext.java:1189)
         at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1121)
         at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:449)
         at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:424)
         at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910)
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
         at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
         at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:119)
         at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:162)
         at weblogic.security.providers.xacml.authorization.XACMLAuthorizationProviderImpl.deployPolicy(XACMLAuthorizationProviderImpl.java:281)
    weblogic.management.utils.CreateException:
         at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:241)
         at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:165)
         at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:112)
    com.bea.security.xacml.PolicyStoreException: <openjpa-1.1.0-r422266:657916 fatal store error> kodo.jdo.FatalDataStoreException: The transaction has been rolled back.  See the nested exceptions for details on the errors that occurred.
         at com.bea.security.providers.xacml.store.BasePolicyStore.setPolicy(BasePolicyStore.java:684)
         at com.bea.security.providers.xacml.store.BasePolicyStore.setPolicy(BasePolicyStore.java:576)
         at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:222)
         at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:165)
    <openjpa-1.1.0-r422266:657916 nonfatal store error> kodo.jdo.ObjectNotFoundException: The instance "netscape.ldap.LDAPException: error result (32)" does not exist in the data store.
    FailedObject: netscape.ldap.LDAPException: error result (32)
         at com.bea.common.ldap.LDAPStoreManager.flush(LDAPStoreManager.java:370)
         at org.apache.openjpa.abstractstore.AbstractStoreManager.flush(AbstractStoreManager.java:277)
         at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
         at org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:554)
         at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
         at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2007)
    ....>
    My workaround:
    Delete the <domain>\servers\s40beaportacc1p9106\data\ldap directory on the managed servers and restart
    Does anyone knows what causes the error and how to solve it?
    The goal is to be able to deploy our application by automation.

    You must use not the original bean that you coded. You must use the bean generated by axis-wsdl2java.
    The bean generated by axis-wsdl2java is:
    - in the first beanMapping: MSPCSService.SMSMO
    - in the second beanMapping: MSPCSService.SMSMOResponse
    As you can see, the bean the axis-wsdl2java will generate is build with the namespace + "." + qname. If you use an domain like java.sun.com in namespace, then the package name you will use is inverted (in the sample, com.sun.java). Look at the code generated.
    You client must use this beans, not the original coded by you.
    This must work, worked for me :)

  • VC Deployment problem

    Hi Experts,
    I am new to the VC. I am using VC 7.0 . I am trying to create a sample content that is using one BAPI and disply its contents in a table.
    What i did is ,
    I created a model
    ---> I doubble click on it
    ---> I dragged the packages and put a name for that
    ---> I doubble click on it
    > I dragged a page to the package
    > I doubble click on it.
    > I dragged an iview on to it.
    > I double click on it.
    Data service
    > I click on Find Data
    ---> I found my BAPI and dragged it on to the storyboard.
    ---> I dragged a table to storyboard and mapped table to DataService.
    Compile
    ---> When i am compiling , i am getting erro as "Element "<BAPI Name> is not in use
    Deploy
    > When i deploy the model, It is deploying and opeing portal window. but ! ia m unable to find the data.
    That is my problem
    Can anyone help me what is the procedure to deploy the model in VC ?
    Thanks in advance
    Suresh..

    Hi,
    Did you given any Input to the data service to get the data in Table if not drag a form view form the data service input Port and then in run time after enetering the dta you will get the output t=data in the table.
    or Add Strat point operator so that it wil give you data in runtime directly.
    Proceudre to Deploy the model.
    Selcet the deployOption on Right side panel then slect the Deploy entire model Check box then clcikc on the Deploy button after that clcik on the Links you get to see the Run time bhehaviour
    Regards,
    Govindu

  • RE: [iPlanet-JATO] Re: Deployment problem

    Chidu,
    I think that you are mired in the very common confusion of the default
    behavior of the ApplicationServletBase.parsePathInfo() which will determine
    the controlling/handling ViewBean via a URL design pattern. Lets take a look
    at the URL
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
    is decomposed as follows:
    /NASApp -> well, this is long story but is absolutely necessary, welcome to
    iAS
    /MigtoolboxSampleAppWar -> is the web application name, taken as the name of
    the WAR file when there is no EAR file (this allows the Servlet/JSP
    container to deferences the web application root under
    <ias>/APPS/modules/MigtoolboxSampleAppWar) I think this part of the URL is
    called th Context Path
    /MigtoolboxSample -> is the Servlet Path, and will either directly reference
    or match a Servlet Mapping
    for instance
    <servlet-mapping>
    <servlet-name>MigtoolboxSampleServlet</servlet-name>
    <url-pattern>/MigtoolboxSample/*</url-pattern>
    </servlet-mapping>
    tells the Servlet Container that the Servlet Path
    /MigtoolboxSample
    maps to the Module Servlet MigtoolboxSampleServlet
    This is how EVERY request makes its way to the "front controller" pattern in
    JATO. It is fundamental to JATO Applicatioan that every request pass
    through the ModuleServlet.
    every else on the URL past the Servlet Path is the PATH INFO. Based on this
    understanding, you will see why the
    ApplicationServletBase.parsePathInfo()
    is so important. In parsePathInfo() the PATH INFO is compared to the design
    pattern
    /VIEWBEANNAME*
    to determine the handling ViewBean from the first String Token in the path
    info. For instance, the starting URL of the Sample Application is
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage
    The PATH INFO is [IndexPage]
    and IndexPage[ViewBean] is the handling ViewBean. Therefore, any simiarl
    URL like
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.matt
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.mike
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.chidu
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.XXX
    will all result in the same handling View Bean
    IndexPageViewBean
    It is very important to understand that you CANNOT hit the JATO JSPs
    directly. You must hit the "front controller" ModuleServlet which will
    always delegate control to the handling ViewBean (a la, the "service to
    workers" pattern)
    You can attempt to hit the JSP directly but you need the right J2EE URL
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSampleApp/MigtoolboxSample/IndexPag
    e.jsp
    this URL will directly hit the JSP. However, you will recieve an error
    because the JATO framework quickly determines that there is no
    RequestContext in the HttpRequest attributes and assumes that the "front
    controller" was bypassed. Try it. You will get ERROR.
    Lets go back to what you are trying to do, place Models and Viewbeans in
    separate directories. I recommend that you move the Models. Models are
    ONLY referenced by TYPE via the ModelManager, the compiler will ensure that
    your code is correct and matches the packages, file locations, import
    statements, etc. ViewBeans, on the other hand are related to the
    ModuleServlet their are contained in and are loaded via type names according
    to a design pattern.
    if you want to separate models and Viewbean then simply move the Model and
    make sure everything compiles.
    you cannot move the ViewBeans
    if you do want to move the JSP peers of the Viewbeans, then you can put them
    anywhere in the web application doc root. When you do, update the
    DEFAULT_DISPLAY_URL as Mike suggested
    matt
    -----Original Message-----
    From: Mike Frisino [mailto:<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217193234150166091061">Michael.Frisino@S...</a>]
    Sent: Thursday, July 26, 2001 10:48 PM
    Subject: Re: [iPlanet-JATO] Re: Deployment problem
    Chidu,
    Did you have it running fine in the original default configuration, before
    you started changing things around? The URL should not access the .jsp
    directly. The URL should look more like this
    "/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage", without the
    .jsp.
    Also, please read the "Migration Tech Notes" document that is
    linked to the
    main doc index page. There is some information in there related
    to trying to
    run the sample application under iAS (see Tech Note 4 in
    particular, "Note
    on running the iMT "MigtoolboxSample" in iPlanet Application Server )
    ----- Original Message -----
    From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164140244063078048234051197">chidusv@y...</a>>
    Sent: Thursday, July 26, 2001 7:27 PM
    Subject: [iPlanet-JATO] Re: Deployment problem
    Hi Mike,
    I tried changing the url in all the viewbeans to reflect the new sub-
    directory for the viewbeans(I have placed the jsps and viewbeans in
    a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
    still not able to get access to the jsps. I basically see the
    message "GX Error Socket Error Code missing!!" error on the browser
    thrown by iPlanet, but the log doesn't tell me anything. Does the url
    which I give to access the jsp change accordingly, i.e., should I
    give something other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
    If I try to use any other url other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
    see the FileNotFoundException in the log.
    I guess I'm still missing something.
    Thanks for your help.
    --Chidu.
    --- In <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166136158139046209">iPlanet-JATO@y...</a>, "Mike Frisino" <<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217130152150">Michael.Frisino@S...</a>> wrote:
    Chidu.
    Did you also adjust the following member in each of the ViewBeans?
    public static final String DEFAULT_DISPLAY_URL=
    "/jatosample/module1/Index.jsp";
    Try adjusting this to be consistent with your new hierarchy.
    Also, if you still have problems, send us the error message thatyou recieve
    when you try to access the page. That would help.
    ----- Original Message -----
    From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164036129208">chidusv@y...</a>>
    Sent: Thursday, July 26, 2001 4:48 PM
    Subject: [iPlanet-JATO] Deployment problem
    Hi,
    We have a requirement to seperate the models and viewbeans and
    keep
    them in seperate directories. Is it possible to seperate the
    viewbeans and models not be in the same directory?
    I tried seperating the two in the MigtoolboxSampleApp application
    provided by JATO. I changed the package and import statements
    accordingly in the viewbeans, jsps and the models. But when I
    deployed the application, I'm not able to access the Index page or
    any of the jsps. Does the ApplicationServletBase always look forthe
    viewbean in the same path as that of the module servlet?
    Any help will be appreciated.
    Thanks,
    Chidu.
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>

    Hi Mike,
    I tried changing the url in all the viewbeans to reflect the new sub-
    directory for the viewbeans(I have placed the jsps and viewbeans in
    a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
    still not able to get access to the jsps. I basically see the
    message "GX Error Socket Error Code missing!!" error on the browser
    thrown by iPlanet, but the log doesn't tell me anything. Does the url
    which I give to access the jsp change accordingly, i.e., should I
    give something other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
    If I try to use any other url other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
    see the FileNotFoundException in the log.
    I guess I'm still missing something.
    Thanks for your help.
    --Chidu.
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    >
    Chidu.
    Did you also adjust the following member in each of the ViewBeans?
    public static final String DEFAULT_DISPLAY_URL=
    "/jatosample/module1/Index.jsp";
    Try adjusting this to be consistent with your new hierarchy.
    Also, if you still have problems, send us the error message that you recieve
    when you try to access the page. That would help.
    ----- Original Message -----
    From: <chidusv@y...>
    Sent: Thursday, July 26, 2001 4:48 PM
    Subject: [iPlanet-JATO] Deployment problem
    Hi,
    We have a requirement to seperate the models and viewbeans and
    keep
    them in seperate directories. Is it possible to seperate the
    viewbeans and models not be in the same directory?
    I tried seperating the two in the MigtoolboxSampleApp application
    provided by JATO. I changed the package and import statements
    accordingly in the viewbeans, jsps and the models. But when I
    deployed the application, I'm not able to access the Index page or
    any of the jsps. Does the ApplicationServletBase always look for the
    viewbean in the same path as that of the module servlet?
    Any help will be appreciated.
    Thanks,
    Chidu.
    [email protected]

  • Deploying ADF Mobile Browser Sample App in JDeveloper 11.1.2.3

    Hi,
    I had problem in deploying the sample app for ADF Mobile Browser in JDeveloper 11.1.2.3.
    I had tried every solution such as replacing web.xml for the Sample App with web.xml created in JDeveloper 11.1.2.3.
    I could not find the Jar file for the oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler in the web also.
    Please help to solve this problem as I had tried for many days.
    Thank you very much! =)
    ADF Mobile Browser Sample App URL:
    [ADF Mobile Browser Sample App|http://www.oracle.com/technetwork/developer-tools/adf/adf-mobile-browser-1864237.html]
    Error Log:_
    *<ConfigureListener> <contextInitialized> Critical error during deployment:*
    com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
         at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: java.lang.ClassNotFoundException: oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
         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)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
         at com.sun.faces.util.Util.loadClass(Util.java:303)
         at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
         at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processHandlerClass(FaceletTaglibConfigProcessor.java:420)
         at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTags(FaceletTaglibConfigProcessor.java:371)
         at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTagLibrary(FaceletTaglibConfigProcessor.java:314)
         at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:263)
         at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:340)
         ... 38 more
    <Dec 10, 2012 12:20:15 PM IST> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler.
    java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:293)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
         Truncated. see log file for complete stacktrace
    Caused By: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
         at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
         Truncated. see log file for complete stacktrace
    >
    <FactoryFinder$FactoryManager> <getFactory> Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup.
    <ConfigureListener> <contextDestroyed> Unexpected exception when attempting to tear down the Mojarra runtime
    java.lang.IllegalStateException: Could not find backup for factory javax.faces.application.ApplicationFactory.
         at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:996)
         at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:331)
         at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:131)
         at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:329)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
         at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3224)
         at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:247)
         at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
         at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1535)
         at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:507)
         at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
         at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
         at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
         at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
         at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:642)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    <Dec 10, 2012 12:20:15 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1355122207762' for task '3'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
         Truncated. see log file for complete stacktrace
    >
    Edited by: 975879 on Dec 9, 2012 10:56 PM

    Hi Frank,
    Thanks for the fast response.
    Based on your advice, I had try to comment out all usage of graph in jsp, web.xml, and data binding file.
    But even after perform these, I still facing the same problem.
    For your information, RichSeriesSetHandler does not exist in the oracle.adfinternal.view.faces.bi.facelets.
    I suspecting RichSeriesSetHandler is configured in the app and it occur this error as it could not find the class.
    I had try to search this usage of this class in the app but there is no results found.

  • HTTP 500 Internal Server Error for developer sample page

    Hi All,
    Getting the HTTP 500 Internal Server Error Page when I click on Developer Sample link on http://10.4.80.238:8080/portal/dt page.
    Find the below error log for more details:
    [#|2009-07-29T10:25:36.767+0530|FINEST|SJS Portal Server|debug.com.sun.portal.desktop.context|ThreadID=19; ClassName=com.sun.portal.desktop.context.PSContainerProviderContext; MethodName=getContent; |PSDT_CSPDC0028 : PSContainerProviderContext.getContent(): getting fresh content for channel: JSPTabContainer|#]
    [#|2009-07-29T10:25:36.768+0530|FINE|SJS Portal Server|debug.com.sun.portal.desktop.context|ThreadID=19; ClassName=com.sun.portal.desktop.context.AuthlessSessionContext; MethodName=getCookieSupportMode; |PSDT_CSPDC0002 : Cookie support mode = 0|#]
    [#|2009-07-29T10:25:36.768+0530|SEVERE|SJS Portal Server|debug.com.sun.portal.desktop|ThreadID=19; ClassName=com.sun.portal.desktop.DesktopServlet; MethodName=handleException; |PSDT_CSPD0022: Internal server error null root cause is java.lang.NullPointerException|#]
    [#|2009-07-29T10:25:36.768+0530|SEVERE|SJS Portal Server|debug.com.sun.portal.desktop|ThreadID=19; ClassName=com.sun.portal.desktop.DesktopServlet; MethodName=handleException; |PSDT_CSPD0023: Primary Exception
    java.lang.ClassCastException: java.lang.NullPointerException
         at com.sun.portal.providers.error.ErrorProvider.getContent(Unknown Source)
         at com.sun.portal.desktop.DesktopServlet.handleException(Unknown Source)
         at com.sun.portal.desktop.DesktopServlet.doGetPost(Unknown Source)
         at com.sun.portal.desktop.DesktopServlet.handleNoSessionRequest(Unknown Source)
         at com.sun.portal.desktop.DesktopServlet.service(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
         at sun.reflect.GeneratedMethodAccessor159.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
         at com.sun.enterprise.web.connector.httpservice.HttpServiceProcessor.process(HttpServiceProcessor.java:235)
         at com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2114)
    |#]
    [#|2009-07-29T10:25:36.769+0530|SEVERE|SJS Portal Server|debug.com.sun.portal.desktop|ThreadID=19; ClassName=com.sun.portal.desktop.DesktopServlet; MethodName=handleException; |PSDT_CSPD0024: Root cause
    java.lang.NullPointerException
         at com.sun.portal.providers.containers.jsp.tab.util.Tab.create(Unknown Source)
         at com.sun.portal.providers.containers.jsp.tab.util.Tab.<init>(Unknown Source)
         at com.sun.portal.providers.containers.jsp.tab.util.TabFactory.createUnmodifiable(Unknown Source)
         at com.sun.portal.providers.containers.jsp.tab.util.TabData.getAvailableTabs(Unknown Source)
         at com.sun.portal.providers.containers.jsp.tab.JSPTabContainerProvider.getSelectedTab(Unknown Source)
         at com.sun.portal.desktop.context.PSContainerProviderContext.createVisiblePortletsList(Unknown Source)
         at com.sun.portal.desktop.context.PSContainerProviderContext.getContent(Unknown Source)
         at com.sun.portal.desktop.context.PSDesktopContext.getContent(Unknown Source)
         at com.sun.portal.desktop.DesktopServlet.doGetPost(Unknown Source)
         at com.sun.portal.desktop.DesktopServlet.handleNoSessionRequest(Unknown Source)
         at com.sun.portal.desktop.DesktopServlet.service(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
         at sun.reflect.GeneratedMethodAccessor159.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
         at com.sun.enterprise.web.connector.httpservice.HttpServiceProcessor.process(HttpServiceProcessor.java:235)
         at com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2114)
    |#]
    [#|2009-07-29T10:25:36.770+0530|SEVERE|SJS Portal Server|debug.com.sun.portal.desktop.mfwk|ThreadID=19; ClassName=com.sun.portal.desktop.mfwk.MfwkPSServiceAdaptor; MethodName=stopTransaction; |PSDT_CSPDMF0003: Mfwk Stop transaction error: Invalid transition for this transaction|#]
    Please provide me the solution to solve it.
    Thanks in advance.

    By the wat what version of application server are you running and how is your portal deployed, i.e portal deployed on seprate machine and access manager on another?
    To disable security login into your application server console e.g https://localhost:4848
    -> Click configurations on the left to expand it
    -> click arrow on the server instance configuration to expand it (this is the instance you used to deploy portal server e.g "server" )
    -> click JVM Settings on the right you will see four tabs
    -> click JVM options, a list of values is displayed
    -> tick "-Djava.security.manager" and "-Djava.security.policy=${com.sun.aas.instanceRoot}/config/server.policy" and click delete
    -> restart the server and try accessing the developer sample.
    Send me the error message if any after doing this and If this does not wok, add back the values.
    regards

  • HELP PLS -exception in deploy transformation for "0ANALYSIS_PATTERN"

    Hi All,
    I have a serious problem here. Please help me here...thanks
    We have recently upgraded our BI 7.0 system from BI ABAP - 10 to
    Support Package Stack - 16, which includes BI ABAP - 18 and BI JAVA -
    16. After the upgrade we are facing problems running any query on the
    portal. We get the same consistent error throughout. The portal error
    message is enclosed. I tried installing 0Analysis_Pattern many times
    but it didn't work.
    Secondly when that didn't work I tried running RSPOR_SETUP, in step 2 I
    get the error message, Different ABAP and JAVA support package.
    SAP came back with a reply saying to do BI JAVA config using template installer. We did that, all looks fine. We also ran the Netweaver Diagnostic tool and all looks fine there as well except the ADS is not configured( I doubt this error is anything to do with ADS as we are not using abode export)
    We went through all these notes, 917950, 937697 and 983156 for the configuration.
    But again when we run the RSPOR_SETUP we get the same error message: Different ABAP and JAVA support package
    Also I ran queries using RSRT ....when I execute using the ABAP Web works fine but opens in port 8000, but when I execute using JAVA web it throws the same error message again as below using port 50000. Also I get the same error message when I open 0ANALYSIS_PATTERN using WAD and try to execute it.
    Has anyone faced this problem before?
    Error message below
    500 Internal Server Error
      BEx Web Application
    To avoid this exception see the steps below. To help SAP better investigate this issue, you will need to provide the diagnostic information from these steps.
    1. Most likely, the issue you are experiencing has already been corrected. Please make sure that the most recent patch level is deployed on your system according to notes 1033246 and 1011241. Starting with Support Package Stack 16 patch level 30, BI Java is delivered according to the synchronized delivery process described in the note 1033246.
    2. Please ensure that NetWeaver Business Intelligence Diagnostics & Support Desktop Tool  does not report any issues on your server according to note 937697. You can start it by clicking here (administrator permissions are required).
    3. When opening any customer message on this issue, please attach:
    Support Desktop Tool support info ZIP  file according to note 937697,
    Required information for reproduction  according to note 948490.
    Error Summary
    Exception occured while processing the current request; this exception cannot be handled by the application or framework
    If the information on this page does not help you locate and correct the cause of the problem, contact your system administrator
    To facilitate analysis of the problem, keep a copy of this error page Hint: Most Web browsers allow you to select all content, and copy and paste it into an empty document (such as in an email or simple text file)
    Root Cause
    The initial exception that caused the request to fail was:
    General exception in deploy transformation for object "0ANALYSIS_PATTERN"
    com.sap.ip.bi.base.exception.BIBaseRuntimeException: General exception in deploy transformation for object "0ANALYSIS_PATTERN"
    at com.sap.ip.bi.deploytime.BISP2Jsp.convert(BISP2Jsp.java:555)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.service.template.PortalTemplateAccessService.getTemplateContent(PortalTemplateAccessService.java:90)
    at com.sap.ip.bi.webapplications.runtime.preprocessor.Preprocessor.parseTemplate(Preprocessor.java:163)
    at com.sap.ip.bi.webapplications.runtime.xml.XmlTemplateAssembler.doInit(XmlTemplateAssembler.java:79)
    at com.sap.ip.bi.webapplications.runtime.template.TemplateAssembler.init(TemplateAssembler.java:128)
    Log ID 0017A4AB12A7006B00000395000016180004605B78DEE173
    Details: Full Exception Chain
    System Environment
    Server
    BI Java Release: 7 - Patch level: 0000000016 - Description: BI Web Applications Java - Additional info:  - Production mode: true
    BI ABAP Release: 700 - Patch level: 0018 - Description: SAP NetWeaver BI 7.0 (GBDCLNT100) - Additional info:  - Production mode: true
    Java Virtual Machine Java HotSpot(TM) 64-Bit Server VM - Sun Microsystems Inc. - 1.4.2_15-b02
    Operating System Windows 2003 - ia64 - 5.2
    Context
    ACCESSIBLE false
    CACHE true
    CONTENT_PADDING true
    COUNTRY 
    DEBUG false
    DEBUG_LEVEL 0
    DEBUG_MESSAGES false
    DEBUG_TEXTS false
    DEFAULT_FONT 
    DISPLAY_STACK_TRACE_IN_ERROR_PAGES true
    LANGUAGE en
    Master System Alias GBDCLNT100
    NAVIGATION_NODE_ACTIVE_IVIEW pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/iViews/com.sap.ip.bi.bex
    PROFILING false
    Query String (Initial Browser Request) QUERY=TEST30
    RTL false
    Request URL
    SAP_BW_IVIEW_ID pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/iViews/com.sap.ip.bi.bex
    SERVER_URL_PREFIX
    THEME_NAME sap_tradeshow
    TRACE false
    TRAY_TYPE PLAIN
    Time Tue Jan 13 11:24:52 GMT 2009
    USE_HTTPS_FOR_ADS false
    USE_SAP_EXPORT_LIB false
    User SERCOWNKN (USER.R3_DATASOURCE.SERCOWNKN)
    VALIDATION_DATA false
    Deployed SCAs
    SCA Version SP Patch Compiled Deployed
    ADSSAP 7.00 16 0 2008-06-10 11:48:09 BST 2008-12-29 12:21:02 GMT
    BASETABLES 7.00 16 0 2008-06-10 12:02:26 BST 2008-12-29 12:02:50 GMT
    BI-BASE-S 7.00 17 23 2008-12-24 10:27:08 GMT 2009-01-07 11:53:24 GMT
    BI-IBC 7.00 16 0 2008-06-10 17:29:06 BST 2008-12-29 12:45:13 GMT
    BI-REPPLAN 7.00 16 0 2008-06-10 18:46:18 BST 2008-12-29 12:59:08 GMT
    BI-WDALV 7.00 16 0 2008-06-10 18:46:28 BST 2008-12-29 12:57:58 GMT
    BIWEBAPP 7.00 17 23 2008-12-24 10:27:42 GMT 2009-01-07 11:52:59 GMT
    BI_MMR 7.00 16 0 2008-06-10 12:03:07 BST 2008-12-29 12:21:38 GMT
    BI_UDI 7.00 16 0 2008-06-10 12:03:25 BST 2008-12-29 12:30:20 GMT
    CAF 7.00 16 0 2008-06-10 19:14:45 BST 2008-12-29 12:34:53 GMT
    CAF-KM 7.00 16 0 2008-06-10 18:52:06 BST 2008-12-29 13:12:43 GMT
    CAF-UM 7.00 16 0 2008-06-10 19:14:53 BST 2008-12-29 12:22:26 GMT
    CORE-TOOLS 7.00 16 0 2008-06-10 12:06:18 BST 2008-12-29 12:03:19 GMT
    EP-PSERV 7.00 16 0 2008-06-10 17:37:42 BST 2008-12-29 13:00:07 GMT
    EP-WDC 7.00 16 0 2008-06-10 15:20:00 BST 2008-12-29 13:01:10 GMT
    EPBC 7.00 16 0 2008-06-10 17:36:02 BST 2008-12-29 12:23:03 GMT
    EPBC2 7.00 16 0 2008-06-10 17:36:14 BST 2008-12-29 13:01:15 GMT
    EP_BUILDT 7.00 10 0 2006-10-24 18:44:00 BST 2007-10-03 17:16:57 BST
    JLOGVIEW 7.00 16 0 2008-06-10 11:07:00 BST 2008-12-29 12:03:55 GMT
    JSPM 7.00 16 0 2008-06-10 11:07:00 BST 2008-12-19 11:42:33 GMT
    KM-KW_JIKS 7.00 16 0 2008-06-10 12:09:28 BST 2008-12-29 12:23:19 GMT
    KMC-BC 7.00 16 0 2008-06-10 17:38:03 BST 2008-12-29 13:02:33 GMT
    KMC-CM 7.00 16 0 2008-06-10 17:38:59 BST 2008-12-29 13:03:37 GMT
    KMC-COLL 7.00 16 0 2008-06-10 17:39:23 BST 2008-12-29 13:04:00 GMT
    LM-PORTAL 7.00 16 0 2008-06-10 18:55:57 BST 2008-12-29 13:04:05 GMT
    LM-TOOLS 7.00 16 0 2008-06-10 19:19:13 BST 2008-12-29 12:40:40 GMT
    NET-PDK 7.00 16 0 2008-06-10 17:39:31 BST 2008-12-29 12:53:38 GMT
    RTC 7.00 16 0 2008-06-10 17:39:47 BST 2008-12-29 12:53:44 GMT
    RTC-STREAM 7.00 16 0 2008-06-10 17:39:48 BST 2008-12-29 12:44:16 GMT
    SAP-EU 7.00 16 0 2008-06-10 18:57:14 BST 2008-12-29 13:11:27 GMT
    SAP-JEE 7.00 16 0 2008-06-10 12:14:29 BST 2008-12-29 12:04:52 GMT
    SAP-JEECOR 7.00 16 0 2008-06-10 12:16:00 BST 2008-12-29 12:08:11 GMT
    SAP_BUILDT 7.00 10 0 2006-10-21 20:06:00 BST 2007-10-03 17:17:12 BST
    SAP_JTECHF 7.00 16 0 2008-06-10 12:17:05 BST 2008-12-29 12:09:31 GMT
    SAP_JTECHS 7.00 16 0 2008-06-10 12:24:43 BST 2008-12-29 12:29:00 GMT
    UMEADMIN 7.00 16 0 2008-06-10 19:27:45 BST 2008-12-29 12:41:03 GMT
    UWLJWF 7.00 16 0 2008-06-10 17:40:28 BST 2008-12-29 13:04:23 GMT
    VCBASE 7.00 16 0 2008-06-10 17:40:33 BST 2008-12-29 13:13:00 GMT
    VCFLEX 7.00 16 0 2008-06-10 17:41:04 BST 2008-12-29 12:55:50 GMT
    VCFRAMEWORK 7.00 16 0 2008-06-10 17:41:13 BST 2008-12-29 12:56:00 GMT
    VCKITBI 7.00 16 0 2008-06-10 17:34:47 BST 2008-12-29 12:44:17 GMT
    VCKITGP 7.00 16 0 2008-06-10 17:41:13 BST 2008-12-29 12:44:20 GMT
    VCKITXX 7.00 16 0 2008-06-10 17:41:13 BST 2008-12-29 12:44:21 GMT
    WDEXTENSIONS 7.00 16 0 2008-06-10 18:58:51 BST 2008-12-29 13:13:18 GMT
    Full Exception Chain
    Log ID 0017A4AB12A7006B00000395000016180004605B78DEE173
    com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error during conversion of the Web template "0ANALYSIS_PATTERN from the master system     at com.sap.ip.bi.webapplications.runtime.jsp.portal.service.template.PortalTemplateAccessService.getTemplateContent(PortalTemplateAccessService.java:95)     at com.sap.ip.bi.webapplications.runtime.preprocessor.Preprocessor.parseTemplate(Preprocessor.java:163)     at com.sap.ip.bi.webapplications.runtime.xml.XmlTemplateAssembler.doInit(XmlTemplateAssembler.java:79)     at com.sap.ip.bi.webapplications.runtime.template.TemplateAssembler.init(TemplateAssembler.java:128)     at com.sap.ip.bi.webapplications.runtime.base.Template.doInit(Template.java:113)     at com.sap.ip.bi.webapplications.runtime.base.PageObject.doInit(PageObject.java:286)     at com.sap.ip.bi.webapplications.runtime.base.PageObject.init(PageObject.java:261)     at com.sap.ip.bi.webapplications.runtime.base.ItemRenderer.init(ItemRenderer.java:39)     at com.sap.ip.bi.webapplications.runtime.impl.Page.initPageObject(Page.java:4995)     at com.sap.ip.bi.webapplications.runtime.impl.Page.createPageObject(Page.java:5342)     at com.sap.ip.bi.webapplications.runtime.impl.Page.setTemplate(Page.java:6537)     at com.sap.ip.bi.webapplications.runtime.impl.Page.doSetTemplateCommand(Page.java:6249)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:324)     at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:101)     at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:415)     at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:330)     at com.sap.ip.bi.webapplications.runtime.base.CommunicationProcessor.processCommand(CommunicationProcessor.java:175)     at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandSuper(Page.java:1821)     at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandInternal(Page.java:1787)     at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandSequence(Page.java:2497)     at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:4018)     at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:3021)     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2864)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:994)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:883)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:860)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:362)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:279)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)     at java.security.AccessController.doPrivileged(Native Method)     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)     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(Native Method)     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: General exception in deploy transformation for object "0ANALYSIS_PATTERN"     at com.sap.ip.bi.deploytime.BISP2Jsp.convert(BISP2Jsp.java:555)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.service.template.PortalTemplateAccessService.getTemplateContent(PortalTemplateAccessService.java:90)     ... 63 more

    Hi,
    Please help.
    How did you manage to resolve this. I have similar issues.
    I have SAP_ALL and can run the reports without problems but users have error message
    general exception in deploy transformation for object "WEB_TEMPLATE"
    thanks

  • Bpel deployment fails for all processes that have revision other than 1.0.

    Using: Release *10.1.3.3.1*
    Hello All,
    Bpel deployment fails for all processes that have revision other than *1.0*.
    We have been attempting to deploy several BPEL projects via ANT script to a target environment and are encountering failures to deploy for every project which isn’t a (revision 1.0). We are getting the following error whenever we try to deploy a process with a revision other than 1.0:
    D:\TJ_AutoDeploy\BPEL_AutoDeploy_BETA\build.xml:65: BPEL archive doesnt exist in directory "{0}"
         at com.collaxa.cube.ant.taskdefs.DeployRemote.getJarFile(DeployRemote.java:254)
         at com.collaxa.cube.ant.taskdefs.DeployRemote.deployProcess(DeployRemote.java:409)
         at com.collaxa.cube.ant.taskdefs.DeployRemote.execute(DeployRemote.java:211)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
         at org.apache.tools.ant.Task.perform(Task.java:364)
         at org.apache.tools.ant.Target.execute(Target.java:341)
         at org.apache.tools.ant.Target.performTasks(Target.java:369)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
         at org.apache.tools.ant.Main.runBuild(Main.java:668)
         at org.apache.tools.ant.Main.startAnt(Main.java:187)
         at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
         at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
    The structure of our automated deployment script is as follows:
    First, a batch script calls (Jdeveloper_BPEL_Prompt.bat) in order to set all necessary environment variables i.e. ORACLE_HOME, BPEL_HOME, ANT_HOME, etc for ant.
    Next, the script lists every .jar file within the directory to an .ini file called BPEL_List.ini. Furthermore, BPEL_DIR, ADMIN_USER and ADMIN_PSWD variables are set and initialized respectively to:
    -     “.” – point to directory where script is running from because all the BPEL processes are located here
    -     “oc4jadmin”
    -     “*********” (whatever the password for out environment is)
    We’ve developed a method to have the script prompt the user to select the target environment to deploy to. Once the user selects the appropriate environment, the script goes through the BPEL_List.ini files and a loop tells it that for every BPEL process listed:
    DO ant
    -Dprocess.name=%%b
    -Drev= !Rev!
    -Dpath=%BPEL_DIR%
    -Ddomain=default
    -Dadmin.user=%ADMIN_USER%
    -Dadmin.password=%ADMIN_PWD%
    -Dhttp.hostname=%HOST%
    -Dhttp.port=%PORT%
    -Dverbose=true
    (What’s happening is that the variables in the batch file are being passed on to the ANT script where *%%b* is the process name, !rev! is revision #, and so on…)
    The loop goes through each line in the BPEL_List.ini and tokenizes the BPEL process into 3 parts *(%%a, %%b, and %%c)* but we only extract 2 parts: *%%b* (process name) and *%%c* which becomes !Rev! (revision number).
    Example:
    Sample BPEL process:
    bpel_ThisIsProcess1_1.0.jar
    bpel_ThisIsProcess2_SOAv2.19.0.001B.jar
    After tokenizing:
    %%a     %%b     %%c
    bpel     ThisIsProcess1     1.0.jar
    bpel     ThisIsProcess2     SOAv2.19.0.001B.jar
    *!Rev!* and not *%%c* because *%%c* will return whatever the revision number is + the “.jar” file extension as illustrated above. So to circumvent this, we parse *%%c* so that the last 4 characters are stripped. Such is done like this:
    set RevN=%%c
    set RevN=!RevN:~0,-4!
    Hence, the usage of !Rev!.
    Below is a screenshot post of the ANT build.xml that goes with our script:
    <!--<?xml version="1.0"?>-->
    <!--BUILD.XML-->
    <project name="bpel.deploy" default="deployProcess" basedir=".">
         <!--
         This ant build file was generated by JDev to deploy the BPEL process.
         DONOT EDIT THIS JDEV GENERATED FILE. Any customization should be done
         in default target in user created pre-build.xml or post-build.xml
         -->
         <property name="process.dir" value="${basedir}" />
              <!-- Set BPEL process name -->
              <!--
              <xmlproperty file="${process.dir}/bpel/bpel.xml"/>
              <property name="process.name" value="${BPELSuitcase.BPELProcess(id)}"/>
              <property name="rev" value="${BPELSuitcase(rev)}"/>
              -->
         <property environment="env"/>
         <!-- Set bpel.home from developer prompt's environment variable BPEL_HOME -->
              <condition property="bpel.home" value="${env.BPEL_HOME}">
                   <available file="${env.BPEL_HOME}/utilities/ant-orabpel.xml" />
              </condition>
         <!-- show that both bpel and oracle.home are located (TESTING purposes ONLY) -->
         <!-- <echo>HERE:${env.BPEL_HOME} ${env.ORACLE_HOME}</echo> -->
         <!-- END TESTING -->
         <!--If bpel.home is not yet using env.BPEL_HOME, set it for JDev -->
         <property name="oracle.home" value="${env.ORACLE_HOME}" />
         <property name="bpel.home" value="${oracle.home}/bpel" />
         <!--First override from build.properties in process.dir, if available-->
         <property file="${process.dir}/build.properties"/>
         <!--import custom ant tasks for the BPEL PM-->
         <import file="${bpel.home}/utilities/ant-orabpel.xml" />
         <!--Use deployment related default properties-->
         <property file="${bpel.home}/utilities/ant-orabpel.properties" />
         <!-- *************************************************************************************** -->
         <target name="deployProcess">
              <tstamp>
                   <format property="timestamp" pattern="MM-dd-yyyy HH:mm:ss" />
              </tstamp>
              <!-- WRITE TO LOG FILE #tjas -->
              <record name="build_verbose.log" loglevel="verbose" append="true" />
              <record name="build_debug.log" loglevel="debug" append="true" />
              <echo></echo>
              <echo>####################################################################</echo>
              <echo>BPEL_AutoDeploy initiated @ ${timestamp}</echo>
              <echo>--------------------------------------------------------------------</echo>
              <echo>Deploying ${process.name} on ${http.hostname} port ${http.port} </echo>
              <echo>--------------------------------------------------------------------</echo>
              <deployProcess
                   user="${admin.user}"
                   password="${admin.password}"
                   domain="${domain}"
                   process="${process.name}"
                   rev="${rev}"
                   dir="${process.dir}/${path}"
                   hostname="${http.hostname}"
                   httpport="${http.port}"
                   verbose="${verbose}" />
              <sleep seconds="30" />
              <!--<echo message="${process.name} deployment logged to ${build_verbose.log}"/>
              <echo message="${process.name} deployment logged to ${build.log}"/> -->
         </target>
         <!-- *************************************************************************************** -->
    </project>
    SUMMARY OF ISSUE AT HAND:
    ~ Every bpel process w/ 1.0 revision deploys with no problems
    ~ At first I would get an invalid character error most likely due to the “!” preceding “Rev”, but then I decided to set rev=”false” in the build.xml file. That didn’t work quite well. In another attempt, I decided to leave the –Drev= attribute within the batch script blank. That still led to 1.0s going through. My next thought was deploying something other than a 1.0, such as 1.2 or 2.0 and that’s when I realized that if it wasn’t a 1.0, it refused to go through.
    QUESTIONS:
    1.     IS THERE A WAY TO HAVE ANT LOOK INTO THE BPEL PROCESS AND PULL THE REVISION ID?
    2.     WHAT ARE WE DOING WRONG? ARE WE MISSING ANYTHING?
    3.     DID WE GO TOO FAR? MEANING, IS THERE A MUCH EASIER WAY WE OVERLOOKED/FORGOT/OR DON’T KNOW ABOUT THAT EXISTS?
    Edited by: 793292 on Jul 28, 2011 12:38 PM

    Only thing i can think of is instead of using a MAC ACL , u cud jus use the default class
    Policy Map Test
    class class-default
    police 56000 8000 exceed-action drop
    Class Map match-any class-default (id 0)
    Match any
    You would be saving a MAC-ACL ;-).

  • Terracotta: application deploy problem (WLP 9.2)

    hi,
    when i try to deploy a Portal application on a bea weblogic server (9.2.1), that is enabled for terracotta (added the java startup arguments to the bea server and the client is visible in the Terracotta Administrator Console), the deployment fails and a lot of compile errors are shown concerning bea classes (from netuix.jar and content.jar, see bottom for snippet). for some reason bea wants to compile these classes on deployment.
    has anybody seen this same problem and does anybody have a solution or workaround for this problem? must the classes be compiled on the fly during development?
    regards,
    erik
    log snippet:
    ####<Oct 4, 2007 6:48:49 PM CEST> <Error> <Deployer> <opteron-w2k3> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1191516529616> <BEA-149205> <Failed to initialize the application 'ps' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
    Unable to deploy EJB: netuix.jar from netuix.jar:
    There are 1 nested errors:
    java.io.IOException: Compiler failed executable.exec:
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\wsrp\services\persistence\internal\ProducerPersistenceManager_7vyoe8_Impl.java:11: com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Intf
    public final class ProducerPersistenceManager_7vyoe8_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\BookDefinitionManager_1xzrxc_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Intf
    public final class BookDefinitionManager_1xzrxc_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortletCategoryManager_uhkdka_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Intf
    public final class PortletCategoryManager_uhkdka_Impl
    [MORE CLASSES HERE]
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortalDefinitionManager_d875a8_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Intf
    public final class PortalDefinitionManager_d875a8_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PageDefinitionManager_c4el9c_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Intf
    public final class PageDefinitionManager_c4el9c_Impl
    ^
    Note: Some input files use or override a deprecated API.
    Note: Recompile with -Xlint:deprecation for details.
    Note: Some input files use unchecked or unsafe operations.
    Note: Recompile with -Xlint:unchecked for details.
    25 errors
         at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
         at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
         at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
         at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
         at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
         at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
         at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    the deployment problem is solved by putting the bea packages in the exclude section of the Terracotta configuration file.

  • KM Problem in Portal 7.3  JSF References

    Hi Everyone,
    I'm having trouble with references in my JSF applications.
    The application has been developed for Portal 7.0 but later on we decided to deploy it on Portal 7.3 . Our application uses KM for some stuff and at that point we are facing Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory problem
    There is another thread which is similar to our problem at JSF 1.2 KM reference error
    but that thread is not helpfull anymore because necessary ticket has been removed or something else happened.
    here we have application-j2ee-engine.xml references which causes problem.
    <reference reference-type="weak">
    <reference-target target-type="application" provider-name="sap.com">
    com.sap.km.application
    </reference-target>
    </reference>
    How can we define application-j2ee-engine.xml in another way to fix it?
    Thanks in advance

    Hello,
    you can download SP7 here: https://nwds.sap.com/swdc/downloads/updates/netweaver/nwds/nw/730/doc/auto_latest_distributions.html
    anyway, thanks for your suggestion. As I probably need to download the jar files, can you suggest where I find them in SWDC?
    edit: oh I see, I might have to pull them from the portal server
    Many thanks
    Stefan
    Edited by: Stefan Ernst on Mar 8, 2012 2:18 PM

Maybe you are looking for