This content has been marked as final. Show 5 replies
There should be no harm in leaving it deployed to WebLogic and you will just not be starting it.1 person found this helpful
Usually it would create a service on windows once a web application is deployed in compact mode, if it doesn't exist and you are not using the compact deployment then there shouldnt be anything to worry about.
It is possible to delete the server from WebLogic though if you are not sure on how to do it and it is not causing any problems it should be safe just to leave it.
Alternatively you can wipe out the domain and the shared services registry and start the config again for it to be clean.
If you just want to delete the service just do on a windows command prompt "sc delete SERVICE_NAME".1 person found this helpful
Thank you John and Pablo!
But now I am unsure about whether it is working with compact mode or not. I generate the deployment report and I can see all the services with their original port while at the same time with 19000 port... Is this normal? Should I upload my deployment report so it would be clearer of what I'm saying?
Though the EPM is now working, it is quite unstable as my EPMA dimension library hangs some times. I wonder whether it is related to the mess of my deployment...
Thanks in advance for any replies!
Edited by: FinFu on Feb 3, 2013 7:52 PM
If you are starting the Weblogic managed server EPMServer or the windows service "Hyperion EPM Server - Web Application" then you will be running a compact deployment of some form, the web apps running in it will depend on what was deployed to it.1 person found this helpful
If you are not and the system is working then it will not be running in a compact deployment.
For EPMA issue,you check the epma web logs to see if there are any errors when the hang occurs.
If this is going to be an important env like Prod or QA my suggestion would be to remove the not required deployments.You can delete the same through epmsys_registry file after finding the corresponding component ID.
Also you can remove EPMServer0(compact deployment) through weblogic admin console and ensure that all the individual Deployments is targeted to the correct server.
I have not tried the above scenario myself...
Hope this helps