SSM 7.0 documentation

Hi, is there any documentaiton for ssm 7.0, some documentation for developing Thanks for advice

Hi Pavel,
Here is the SSM7.0 documentation.
Regards
Pravin
https://websmp210.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000085365&_SCENARIO=01100035870000000112

Similar Messages

  • SAP SSM 7.0 documentation

    Hi, is there any documentaiton for ssm 7.0, some documentation for developing. some link. Thanks for advice

    Pavel,
    Documentation for SSM 7.0 will be at the online help
    http://help.sap.com > SAP Business Users > EPM Solutions > SAP Strategy Management > SAP Strategy Management 7.0
    and there is other important information about configuration at
    http://service.sap.com/instguidesCPM-STM > SAP Strategy Management 7.0
    Regards,
    Bob

  • Error While Starting WebLogic Console after SSM Configuration

    Hi,
    I have installed Oracle Entitlement Server 10.1.4.3, and have Admin Server and WebLogic SSM running in separate homes on Windows XP Pro machine.
    Have followed standard documentation and completed the steps for Configuring SSMs using ConfigTool (http://download.oracle.com/docs/cd/E12890_01/ales/docs32/installssms/SSM_Configs.html).
    Followed by that while securing the WebLogic Server as per documentation - http://download.oracle.com/docs/cd/E12890_01/ales/docs32/integrateappenviron/configWLS.html, am unable to access the Console app. WebLogic domain is startingup properly, but unable to access the Console.
    Following is the error stack in Admin server log:
    ####<24-Nov-2010 14:43:42 o'clock GMT> <Info> <Health> <ldndwm291637> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1290609822769> <BEA-310002> <85% of the total memory in the server is free>
    ####<24-Nov-2010 14:48:55 o'clock GMT> <Info> <WorkManager> <ldndwm291637> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290610135628> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
    ####<24-Nov-2010 14:48:59 o'clock GMT> <Error> <HTTP> <ldndwm291637> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290610139535> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
    java.lang.IllegalAccessError: tried to access method com.bea.utils.misc.ProcessManager.vloadProcess(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/util/Vector; from class com.bea.utils.misc.ProcessUtil
         at com.bea.utils.misc.ProcessUtil.getPropValues(Unknown Source)
         at com.bea.p13n.license.LicenseHelper.getLicensePropertyValues(LicenseHelper.java:259)
         at com.bea.netuix.servlets.services.LightNetUIxServices.getRestrictedPortalLimit(LightNetUIxServices.java:140)
         at com.bea.netuix.servlets.manager.UIServlet.reinitInternal(UIServlet.java:177)
         at com.bea.netuix.servlets.manager.UIServlet.initInternal(UIServlet.java:164)
         at com.bea.netuix.servlets.manager.UIServlet.access$100(UIServlet.java:60)
         at com.bea.netuix.servlets.manager.UIServlet$ServletLifecycleListenerImpl.init(UIServlet.java:555)
         at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
         at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
         at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:182)
         at com.bea.netuix.servlets.manager.UIServlet.init(UIServlet.java:131)
         at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:75)
         at javax.servlet.GenericServlet.init(GenericServlet.java:241)
         at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.init(MBeanUtilsInitSingleFileServlet.java:36)
         at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:100)
         at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         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:83)
         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:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
         at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
         at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
         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)
    >
    ####<24-Nov-2010 14:48:59 o'clock GMT> <Error> <J2EE> <ldndwm291637> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290610139550> <BEA-160001> <Error deploying Internal Application: weblogic.application.ModuleException: [HTTP:101216]Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
    java.lang.IllegalAccessError: tried to access method com.bea.utils.misc.ProcessManager.vloadProcess(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/util/Vector; from class com.bea.utils.misc.ProcessUtil
         at com.bea.utils.misc.ProcessUtil.getPropValues(Unknown Source)
         at com.bea.p13n.license.LicenseHelper.getLicensePropertyValues(LicenseHelper.java:259)
         at com.bea.netuix.servlets.services.LightNetUIxServices.getRestrictedPortalLimit(LightNetUIxServices.java:140)
         at com.bea.netuix.servlets.manager.UIServlet.reinitInternal(UIServlet.java:177)
         at com.bea.netuix.servlets.manager.UIServlet.initInternal(UIServlet.java:164)
         at com.bea.netuix.servlets.manager.UIServlet.access$100(UIServlet.java:60)
         at com.bea.netuix.servlets.manager.UIServlet$ServletLifecycleListenerImpl.init(UIServlet.java:555)
         at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
         at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
         at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:182)
         at com.bea.netuix.servlets.manager.UIServlet.init(UIServlet.java:131)
         at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:75)
         at javax.servlet.GenericServlet.init(GenericServlet.java:241)
         at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.init(MBeanUtilsInitSingleFileServlet.java:36)
         at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:100)
         at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         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:83)
         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:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
         at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
         at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
         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.application.utils.StateChangeException: weblogic.application.ModuleException: [HTTP:101216]Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
    java.lang.IllegalAccessError: tried to access method com.bea.utils.misc.ProcessManager.vloadProcess(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/util/Vector; from class com.bea.utils.misc.ProcessUtil
         at com.bea.utils.misc.ProcessUtil.getPropValues(Unknown Source)
         at com.bea.p13n.license.LicenseHelper.getLicensePropertyValues(LicenseHelper.java:259)
         at com.bea.netuix.servlets.services.LightNetUIxServices.getRestrictedPortalLimit(LightNetUIxServices.java:140)
         at com.bea.netuix.servlets.manager.UIServlet.reinitInternal(UIServlet.java:177)
         at com.bea.netuix.servlets.manager.UIServlet.initInternal(UIServlet.java:164)
         at com.bea.netuix.servlets.manager.UIServlet.access$100(UIServlet.java:60)
         at com.bea.netuix.servlets.manager.UIServlet$ServletLifecycleListenerImpl.init(UIServlet.java:555)
         at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
         at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
         at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:182)
         at com.bea.netuix.servlets.manager.UIServlet.init(UIServlet.java:131)
         at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:75)
         at javax.servlet.GenericServlet.init(GenericServlet.java:241)
         at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.init(MBeanUtilsInitSingleFileServlet.java:36)
         at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:100)
         at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         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:83)
         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:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
         at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
         at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
         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)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:109)
         at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
         at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
         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)
    Caused By: weblogic.application.ModuleException: [HTTP:101216]Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
    java.lang.IllegalAccessError: tried to access method com.bea.utils.misc.ProcessManager.vloadProcess(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/util/Vector; from class com.bea.utils.misc.ProcessUtil
         at com.bea.utils.misc.ProcessUtil.getPropValues(Unknown Source)
         at com.bea.p13n.license.LicenseHelper.getLicensePropertyValues(LicenseHelper.java:259)
         at com.bea.netuix.servlets.services.LightNetUIxServices.getRestrictedPortalLimit(LightNetUIxServices.java:140)
         at com.bea.netuix.servlets.manager.UIServlet.reinitInternal(UIServlet.java:177)
         at com.bea.netuix.servlets.manager.UIServlet.initInternal(UIServlet.java:164)
         at com.bea.netuix.servlets.manager.UIServlet.access$100(UIServlet.java:60)
         at com.bea.netuix.servlets.manager.UIServlet$ServletLifecycleListenerImpl.init(UIServlet.java:555)
         at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
         at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
         at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:182)
         at com.bea.netuix.servlets.manager.UIServlet.init(UIServlet.java:131)
         at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:75)
         at javax.servlet.GenericServlet.init(GenericServlet.java:241)
         at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.init(MBeanUtilsInitSingleFileServlet.java:36)
         at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:100)
         at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         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:83)
         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:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
         at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
         at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
         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)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1399)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         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:83)
         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:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
         at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
         at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
         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)

    Did you ever find a resolution for this? I have run into the same issue while upgrading from 10.3.1 to 10.3.3.
    ####<Jan 17, 2011 8:14:40 PM EST> <Error> <HTTP> --<SERVER-NAME>-- <AdminServer> <ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1295313280200> <BEA-101093> <Problem occurred while dispatching servlet request.
    weblogic.management.DeploymentException:
         at weblogic.application.internal.BackgroundDeploymentService.OnDemandURIAccessed(BackgroundDeploymentService.java:166)
         at weblogic.servlet.internal.OnDemandManager.loadOnDemandURI(OnDemandManager.java:106)
         at weblogic.servlet.internal.MuxableSocketHTTP.dispatch(MuxableSocketHTTP.java:327)
         at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:177)
         at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:901)
         at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
         at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:215)
         at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:177)
         at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    Caused By: java.lang.IllegalAccessError: tried to access method com/bea/utils/misc/ProcessManager.vloadProcess(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/util/Vector; from class com/bea/utils/misc/ProcessUtil
         at com.bea.utils.misc.ProcessUtil.getPropValues(Unknown Source)
         at com.bea.p13n.license.LicenseHelper.getLicensePropertyValues(LicenseHelper.java:259)
         at com.bea.netuix.servlets.services.LightNetUIxServices.getRestrictedPortalLimit(LightNetUIxServices.java:140)
         at com.bea.netuix.servlets.manager.UIServlet.reinitInternal(UIServlet.java:177)
         at com.bea.netuix.servlets.manager.UIServlet.initInternal(UIServlet.java:164)
         at com.bea.netuix.servlets.manager.UIServlet.access$100(UIServlet.java:60)
         at com.bea.netuix.servlets.manager.UIServlet$ServletLifecycleListenerImpl.init(UIServlet.java:555)
         at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
         at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
         at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:183)
         at com.bea.netuix.servlets.manager.UIServlet.init(UIServlet.java:135)
         at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:77)
         at javax.servlet.GenericServlet.init(GenericServlet.java:242)
         at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.init(MBeanUtilsInitSingleFileServlet.java:37)
         at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:100)
         at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:84)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3127)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:489)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:374)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
         at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    Edited by: user13712701 on Jan 18, 2011 1:46 PM

  • How to use HTML Cube builder in SSM 7.0 SP4

    Hi,
    I've just installed SSM 7.0 SP4 (with hotfix 5, 6)
    A blank page is opened when I open cube builder page for building cube/PAS model.
    My configuration settings are below:
    1. Add a new database through the link "Add a new database" in the Strategy Management application tools page.
    2. Create Link ID in PAS
    3. Create model connection in the Strategy Management administration page.
    4. Open cube builder page
    "http://<nwce>:<port>/strategy/cubebuilder/cube_builder.htm"
    Please, let me know if my configuration settings are incomplete or incorrect.
    Or, where can I get information (or document) of it?
    Have a nice day!
    - System environment
    OS: Windows 2003 Server Enterprise Edition R2 SP2 64bit.
    DB: MS SQL Server 2005 Enterprise Edition
    Netweaver CE 7.1 SP6
    SSM 7.0 SP4 (Hot fix 5, 6)

    Santiago,
    Cube Builder is designed to build simple cubes without using PAS. Until very recently Cube Builder was only available to internal or consultants during the Ramp Up process. Now that Strategy Management is out of Ramp Up it has been made available.
    I know that Cube Builder is covered in the training courses for Strategy Management, but not aware of any courses scheduled until next year. Advise you to use the documentation with Cube Builder Help.
    Regards,
    Bob

  • How can I customize E-mail in SSM?

    Hi,
    I´m new person in SAP and this is my first project. I'm with a problem to customize the e-mail in SSM (Sap Strategic Management). Every time that I try to send an e-mail a message box appear with this message:
    "To e-mail this document, select Email tool in Acrobat Reader and send this PDF as an attachment ", but I already did this in Acrobat Reader.
    Somebody knows if I need do to something else?Or Somebody has a documentation about this theme?
    Thanks in advance,
    Adriana

    Adriana,
    Here is what you will need to do within Netweaver CE to allow email to be sent.
    1. (Optional) Work with your IT department to set up an email alias for SAP Strategy Management called ssm@<mycompany>.com or whatever name you prefer.
    2. Make sure each user of SAP Strategy Management has an associated email address.
    3. Start the SAP NetWeaver Administrator.
    4. Log in as administrator with the global password you provided when you installed NetWeaver CE.
    5. Click Configuration Management.
    6. Click the Infrastructure tab.
    7. Select Java System Properties.
    8. Click the Applications tab.
    9. Filter on the SAP Strategy Management application.
    10. Find the mail.smtp.host property and modify it to specify a mail server that can relay mail internally. Use your company's name in place of <mycompany>.
    Here are some sample values, where <mycompany> is the name of your company:
    smtp.<mycompany>.com
    internet.<mycompany>.com
    mail.<mycompany>.com
    11. Find the mail.from property and modify it to specify the email alias. For example,
    ssm@<mycompany>.com. If you did not set up an ssm@<mycompany>.com email alias,
    then modify the property to specify the email address of the user who will be sending the notification.
    12. Find the mail.domain property and modify it to use your company's name. Use the following format for the value: <mycompany>.com
    If you have problems with email alerts, make sure the mail server allows relaying. If you have blocked mail relaying for security reasons, you must allow it at least on the SAP NetWeaver CE server where SAP Strategy Management application
    components are installed.
    Regards,
    Bob

  • SAP SSM Standard vs SAP SSM Enterprise

    Hi Everyone,
    We would like to utilize SAP Strategy Management, however, we are still in the process of reviewing the functionality. Right now we are tangled between SSM Standard and SSM Enterprise. Can anyone give us an idea what's the difference between the two? And we were advised that SSM Enterprise has integration templates available; how can we get those templates? In a cost standpoint, what will be the recommended of the two?
    Thank you very much for sharing your thoughts on this.
    PS. Were can we get a detailed documentation of the functionality of the two.
    Rally

    Rally,
    SSM uses Contexts as a way of cascading strategy throughout an organization. Each Context within SSM can have different goal diagrams as well as having more specific objectives. Think of a Context as how an organization looks at their business. A Context can be regions, it can be functional areas - finance, HR, manufacturing, marketing, etc., it can be lines of business - gas delivery, electrical delivery, customer service, or combinations of those.
    Since individual users are accessing SSM, the administrator could designate which Contexts they have access to. That way the Southeast Region's salespeople could see their objectives and KPIs for the Southeast, but for no other region. A sales manager could have access to several of the regions they were responsible for.
    A multidimensional Model is associated with Contexts and it, as well, can be used to provide the appropriate data and metrics for users. A Model is what is constructed to define the type of data, its dimensions, measures, and KPIs.
    As far as functionality and features goes, there is no difference between Edge and Enterprise. Edge has all of the same tabs available: Home, Strategy, Scorecards, Dashboards, Initiatives, and Reports. It allows Operational Reviews, Comments, Alerts, and the same individual perference settings as Enterprise. The limitations for Edge should still meet the needs of small or medium sized organizations.
    EPM is the suite of applications of which SSM is a part. For the difference between 7.0 and 7.5, each of the individual products will have their own enhancements as well as additional integration with other products in the suite. The 7.5 versions of EPM products are still in the Ramp Up process, while I believe the 7.0 versions are in general availability. SSM is available as an individual application or can be purchased as part of the EPM suite.
    Regards,
    Bob

  • PAS and SSM 10.1 Connection

    Hi SSM Experts,
    I have already installed PAS and Strategy in the server, I also have PAS locally in a virtual machine, I have already configured de lsserver.ini document in the server:
    [192.168.2.212]
    tcp_protocol=winsock
    username=pipadmin
    Password=?
    PROTOCOL=TCP
    SERVICE=PILOT
    CURSOR=LSSCMPTR
    [windows]
    NCSLOG=INFO
    Version=940
    the SAP SM Listener service is started.
    the server is Windows Server 2008 R2 Standard.
    tha DB is SQL Server.
    I have already checked this error in forums and all solutions given for this same error has not worked for me.
    when I try to login to PAS, I get this error:
    COM013: The attempt to connect to the server failed. The call to function connect received the WINSOCK error code -  WSAECONNREFUSED: Connection refused. This usually indicates that the Pilot Analysis server TCP/IP listener is not active on the server machine. Check to make sure the server is ready to accept connections from this Analysis Server client. Also make sure that the port number you are connecting to is the correct port. Consult the WINSOCK documentation or winsock.h file from your WINSOCK vendor for additional details.
    Thanks for your help.

    Hi,
    Did you try PAS locally on the server, is working fine? Regarding the LSServer.ini, those server settings should be present in the LSServer.ini files that exist locally in each PAS client installation. Also regarding those settings, I notice that you are using PIPADMIN as the user account, but normally PIPADMIN is a NetWeaver UME user, to use in the PAS connection, should be a local user account in the server where PAS is installed.
    Pedro

  • Best practices for using Normalizer in ASA and in AIP-SSM

    Both PIX OS 7.x and IPS 5.x software have a concept of "traffic normalization". PIX OS on ASA can do virtual reassembly, IPS on SSM (so far as I know) can do physical reassembly and fragmentation of IP packets. Also, both ASA and SSM can do TCP normalization. For example, they both can "check inconsistent retransmissions" and protect against "TTL evasion attacks". I realize that PIX OS has only basic normalization functions and the SSM is much more configurable.
    The question is: what are the best practices here? Is it better to disable some IP/TCP PIX OS checks / IPS signatures on ASA and/or SSM? Is it better to use just SSM for traffic normalization? Does anybody has personal experience here?
    Also, there is a BugID CSCsd04327 - "ASA all out of order packets are dropped when sending to ssm"
    "When ips ssm is inline slowness is reported. show service-policy shows that the number of out of order packets reported match exactly the number of no buffer drops (even with queue-limit option). Performance hit is not the result of tcp normalization (on IPS 5.x ssm) in this case, but rather an issue with asa normalizer."
    To me it seems to be more logical to have normalization function on the firewall, but there may be drawbacks in doing this.
    So, those who're using ASA with SSM, please share your experience.
    Thx.

    Yes, this is almost correct ;)
    TCP SRP (Stream Reassemly Processor) is turned OFF on the SSM and cannot be enabled, contrary to 4200 appliances, but IP FRP (Fragmentation Reassembly Processor) is functioning on the SSM.
    The testing of 7.2(1) shows the following:
    When you configure "policy-map" to send packets to the SSM the "tcp-map" parameter "queue-limit", which has the value of zero by default, is set to an X (the X is unknown). This means that the ASA now only accepts the TCP segments which are sent in the correct order. More specifically, the gaps in SEQs are not allowed anymore. When for example, the ASA receives a TCP segment which has a SEQ within the window, but the previous TCP segment has been lost, it sends an ACK to the sender to enforce retransmition of the lost segment. As a result the sender retransmits both segments. Only after that the ASA forwards both segments to the SSM. This basically means that SSM always sees in-order TCP segments. That it is why SRP is not needed on the SSM.
    There are at least two problems however.
    The first problem is the performance impact.
    ASA now acts almost like a proxy. And, so far as I know, it doesn't support SACK (Selective ACKs). First, when the ASA does TCP SEQ randomization it doesn't change SEQ values within the SACK TCP Option. This simply breakes SACK. Second, even if you turn randomization mechanism OFF, then, I believe, the ASA will not selectively ACK the lost TCP segments, as it simply doesn't support this mechanism.
    The second problem is THE SECURITY HOLE.
    By default the ASA doesn't check TCP checksums. The 4200 appliances do check by default. But as we now know the SRP is turned OFF on the SSM... So, this means that SSM module can easily be evaded. The hacker only needs to mix attacking traffic with the random TCP segments that have bad TCP checksum. The SSM module will see the mixture of the two and will not recognize the attack. The target host will drop TCP segments with the bad checksums and see only attacking traffic... This has been successfully verified in the lab.
    Of course, this security hole can be closed with the "tcp-map" parameter "checksum-verification", but it will definitely has performance impact.
    The last note: All of the above has never been documented by Cisco. So, use at your own risk, etc.
    I hope, you will read this message, Marcoa. All of this MUST be documented. Once again, the default behaviour of the ASA opens up a big security hole.
    Regards,
    Oleg Tipisov,
    REDCENTER,
    Moscow

  • Will the AIP-SSM for the ASA stop this?

    I have a client emailed me today that someone did a script injection attack on one of their web servers. It ran a backdoor Trojan virus on their web server. I know the AIP-SSM will stop the Trojan, but will it stop someone from doing the script injection attack. If so, is it documented and can you point me to the document.
    Thanks.
    Dan

    Hi,
    If you know exactly which of the various script injection attacks was used you can simply look it up here:
    http://tools.cisco.com/security/center/home.x
    If you don't know exactly which one then it's slightly harded to know whether it would have been stopped, but searching on "script injection" or similar should narrow down the candidates and give you an idea on whether it would have been stopped or not.
    Remember that an IPS isn't perfect, but it *will* significantly lower your risk if setup and maintained properly.
    HTH
    Andrew.

  • RE: Documentation with the help of ARIS or Solution manager ?

    Good day to all,
    We have a documentation requirement from one of our client.
    The current situation is :
    The client had implemented SAP about 5 years back but has no Documentation for the any of the Transactions, or any of the Zprogram that were created.
    Now the requirement is to create documentations as well as need to relate it with a business Flow..
    Currently their organization has ARIS as well as Solution manager.
    How do we go about it ?. Any suggestions ?
    Do they need XI to integrate it with ARIS ?
    Please help me out on this one....
    Many thanks in advance

    The first thing to find out if the SSM is connected to ARIS (ARIS4Netweaver). This enables you to have the processlogic in ARIS and the implementation documentation in the SSM. This data can be synchronized so that the documentation can be called upon in ARIS.
    For the evaluation regarding the usage of transactions etc, this can be done via ARIS redocumentation. This gives a complete overview of all transaction used in relation to the existing (or sap reference) database in ARIS. it is not restricted to standard SAP transaction, but also custom build transactions/programs are taken into account.
    SAP Xi is not necessarry forthe integration between ARIS and SSM.

  • Does anyone know error SSFCOMPOSER150 when sending a mail in SSM??

    Hi,
    With all action creating a email in the SSM system, the system gives error SSFCOMPOSER150. Also the system gives an error that the function module of the smart form gave an error.
    The exact error is:
    <i>Previous output request was not finished.
    Message no. SSFCOMPOSER150
    Diagnosis
    A previous output request has not been finished. Therefore you are not allowed to start a new output request.
    System Response
    The system issues an error message.
    Procedure
    Check the sequence in which you call the function modules SSFCOMP_OPEN and SSFCOMP_CLOSE.</i>
    Does anybody know how to solve this. Please let me know, also on my email account
    Thanks in advanced,
    Bas van Trier
    [email protected]

    Dear Bas van Trier,
    The error message "SFFCOMPOSER 150: Previous output request was not
    finisched" seems to indicate that an error occured during the processing
    of the former action.
    So, several actions are performed during the batch process. Processing a
    SMART FORM has to execute the functions SSFCOMP_OPEN, SSFCOMP_PROCESS
    and SSFCOMP_CLOSE in this specific order. Now, the former actions fails
    with an exception raising. This will stop the processing and the last
    command SSFCOMP_CLOSE is never reached.
    Now, the next action is started. During the call of SSFCOMP_OPEN the
    system will notice that the former action has not finished sucessfully
    and stops the processing at once.
    So, during a SMART FORM processing raising clauses are not allowed (see
    Online Documentation: Error processing (Smart Forms, Maintain form with
    Form Builder, Check and test a Smart Forms, Section EXCEPTIONS at the
    end).
    The effected SMART FORM is function module /1BCDWB/SF00000015.
    Also, I was not able to find a raising clause in the function module, I
    have seen that some other function modules are called, which do raise
    some exceptions. Example: funcion module ZVM_CONTRACT_GETITEMDETAILS is
    calling CRM_ORDER_READ. Function CRM_ORDER_READ can raise exception
    DOCUMENT_LOCKED if the application object is currently locked by a
    processor. The raised exception is not handled in your Z-function module
    and therefore processing the SMART FORMS will fail.
    So, from my point of view this is the most likely configuration.
    A former action fails, because the application object is currently
    locked; the next action will fail due to the improper call of
    SSFCOMP_OPEN.
    Regards
    Amit Devale

  • SSM 10.1 Cascaded Scorecard

    Hi SSM 10.1 Experts,
    for people who have had the opportunity to work SSM 10.1, I want to ask you a question related to
    the impact of cascading the scorecard, which is mentioned in the documentation as a new possibility.
    Thanks a lot.

    Ingrid,
    What do you want to know about cascading?
    You can cascade the contexts within SSM so that they stretch from the Corporate level to the departmental or business unit level. The relevant filters placed on dimensions will ensure that the data matches that level of the organisation.
    Within SSM you can also cascade Objectives and Initiatives. When cascading Objectives you are saying that Objective A is supported by Objective B in the context of a lower level and an Objective B may support that same Objective in another context on that lower level.
    Similarly you can cascaade Initiatives so that the initiative in Context A is 'copied' into the contexts at the lower levels and you can reassign responsibilities and budgets.
    Does this help?
    Regards
    Colin

  • Entitlements Server - Configuring SSM to run without an SCM

    I am using the ConfigTool to create java-ssm instances. What do I need to specify to create an SSM that doesn't use an SCM? Or, how do I update the configuration of an existing ssm to shut off the need for an SCM (though the documentation says you can't switch from XML to SCM once the instance is created so I'm assuming the reverse is also true).
    There are instructions for doing this from the "wizard" at [http://download.oracle.com/docs/cd/E12890_01/ales/docs32/installssms/No_SCM.html#wp1087976], however, my wizard never presents the checkbox mentioned, and the figure (10-1) appears to be missing from the documentation.
    Edited by: user10437255 on Sep 3, 2009 5:14 AM

    Hi
    I've found on Oracle Documentation a special how-to perform the weblogic configuration to integrate with OID.
    Take a look at: http://www.oracle.com/technology/products/jdev/tips/fnimphius/oidconfig/index.html.
    But it's for WebLogic Server 10g Release 3.
    user10510828

  • SSMS for SQL Server 2012 Express on Windows Embedded 8 Standard

    Hello,
    I have installed SQL Server 2012 Express with Advanced Tools (SQLEXPRADV_x64_ENU.exe, downloaded from MS website) on Windows Embedded 8 Standard 64-bit. But, when I try to find SQL Server Management Studio, I realized it's not installed (same installation
    package works fine on my Windows 8.1 Pro 64-bit laptop, where SSMS gets installed). How do I fix this? And any other ways for trouble-shooting DBs on Windows Embedded 8 Standard?
    Thanks,
    Jay

    Below is the content of a summary file for the installation. BTW, I also try to find its ConfigurationFile.ini file for future installation on other computers, but it's not in the folder specified in the summary file either (see below).
    Thanks.
    Overall summary:
      Final result:                  Passed
      Exit code (Decimal):           0
      Start time:                    2014-04-15 13:57:59
      End time:                      2014-04-15 14:13:29
      Requested action:              Install
    Machine Properties:
      Machine name:                  AIMB-584
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   Microsoft SQL Server 2012 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         c:\e089c9dde791653620\x64\setup\
      Installation edition:          Express
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Disabled
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    true
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS, BIDS, BOL, SSMS, SNAC_SDK, LOCALDB
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  false
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SQLEXPRESS
      INSTANCENAME:                  SQLEXPRESS
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SQLEXPRESS
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           AIMB-584\User
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140415_135512\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Basic
      Status:                        Passed
      Feature:                       SQL Server Data Tools
      Status:                        Passed
      Feature:                       Reporting Services - Native
      Status:                        Passed
      Feature:                       Database Engine Services
      Status:                        Passed
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Passed
      Feature:                       SQL Server Replication
      Status:                        Passed
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       LocalDB
      Status:                        Passed
      Feature:                       SQL Client Connectivity
      Status:                        Passed
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140415_135512\SystemConfigurationCheck_Report.htm

  • SSM-AIP 7.0(1) Global Correlation config nightmare!

    Thanks, Cisco, for creating a Management nightmare with your "Global Correlation" option in version 7.0...
    Lets start with the SSM-AIP-20 Management interface...
    We have an OOB Management network, with a single POI into this through a separate PIX515E appliance. Both the ASA5540 AND the SSM-AIP-20 reside on this network.
    The first issue was in Routing, since the ASA sees the Management network as "directly attached", and we ROUTE the traffic through the PIX for updates on the SSM module, we had to add translation entries in the PIX515E for the SSM module (10.x.x.x Management, 172.x.x.x translated).
    This was not a big issue, but here is where the nightmare begins...
    First a note: We have the Management network locked down TIGHT, only a couple of Network Management stations allowed into that network to access these devices.
    I enabled Global Correlation in test mode, but it was "failed" every time it tried to update.. Reading other posts, I created ACL and Static NAT in the PIX515E for these IP's:
    204.15.82.17 (IP listed in the IME Global Correlation update server)
    97.65.135.170 and .137 (from another post in these forums)
    207.15.82.17 (IP found in a trace)
    Still no updates. Looking in the PIX logs, I found "no translation" entries for the following addresses:
    198.133.219.25
    209.107.213.40
    208.90.57.73
    I put these in, and it started updating! FIXED? NOT!
    This morning, it was again failing... Looked in the PIX logs again, and found these:
    77.67.85.33
    77.67.85.9
    Entered them, and the SSM is happy again. How long? Who knows?
    So, now I have NINE holes in my "secure" network, and who knows when Cisco will change or add new IP addresses to this list.
    Cisco, if you are listening - ALL access to/from the Global correlation through a single IP? PLEASE?
    (use the one listed in the IME - 204.15.82.17, for the URL "update-manifests.ironport.com")

    A few of the addresses belong to Cisco (originally ironport.com addresses from the ironport aquisition) and are used as manifest servers to provide the sensor a list of files to download.
    The sensor then downloads those files from Akamai servers. Akamai has a large number of servers across the world. Cisco sends the update to Akamai and they replicate it across their servers. When sensors try to connect to the Akamai server it does a DNS query and by controlling the DNS response it can direct sensors to an Akamai server located nearer to the sensor. This allows for better load balancing, response times, and download speeds.
    However, Akamai has a large number of servers (in the thousands I think) world wide, and you can't predict which server your specific sensor will be directed to.
    Sensor connections to the cisco servers for the manifest (file list) is on port 443, and usually to update-manifests.ironport.com URLs.
    Sensor connections to the Akamai servers for the actual file downloads are on port 80 and usually to updates.ironport.com URLs.
    The above is all based on my limited understanding of how the updates work. I may have gotten a few details wrong, but should at least give you a general idea.
    I will be working with development to get this better documented in Release Notes and Readme with the next IPS software release.

Maybe you are looking for

  • Issue in GP

    Hello Guru's, We're implementing LWE's in our client and we are stuck with an issue in GP's We have created a custom Web Dynpro ABAP application for creating/modifying/deleting 378 record (Adjustment Reason) and the application is working fine. For i

  • How to use a digital booklet?

    I'm using iTunes v8. I've downloaded a few ditigal booklets, but cannot seem to do anything with them. When I try to open one, Adobe Reader opens with an error message "invalid path." I cannot view them on my iPod Classic either. I asked Apple Suppor

  • "Essential" Tiger fonts

    I was having a font display issue with certain types of html emails using Entourage and thought it might be a font related issue, so I did an archive and install and then checked the system/library/fonts folder and the main library/fonts folder again

  • Recommendations for reporting tools for Ora Payroll

    Hi My client has installed Oracle PAY as a vanilla solution (Fast Forward) to a old Rebus legacy system. I'm currently putting together a fit gap analysis on reporting requirements. Many of the standard payroll reports are replicated by oracle. But t

  • Ipad shut down in middle of an app and wont turn back on or charge. what can i do?

    While using my ipad watching a video on youtube, it just shut down and went black. i have tried to charge it and it doesnt even show that it is connected. Ive tried turning it on from different buttons and still nothing. Does anyone have an idea of w