EPM 11.1.2.x deployment to single managed server

Hi Gurus,
I have 2 questions:
1) If we install some applications on single port number:9000(deploy to single managed server), after that if we deploy some applications to individual ports. is this installation work?
2) for example we have installed and configured all applications to single managed server:9000. Now can we change this to individual port numbers??
I mean can we configure all application to individual port numbers??
Just asking with curiosity to know about this scenarios.
Thanks,
mady

Hi Pablo,
Hope you are doing good. In Starting of Carrer on Hyperion, JohnGoodwin and Your replies on the Forum was very helpful to me. Nowadays,you are busy i think, and we are not getting more responses from you .
Pablo wrote:
If what you're trying to do is deploy everything to 9000, test that and then deploy everything to its own managed server, the answer is yes you can but you need to re-run the OHS configuration at the end everytime as it will need to update the mod_wl_ohs.conf file to update the ports/# of managed servers.
Pablo
In the response, Can we get any conflict between services if we do reconfigure to the Own managed server.?
(why i am asking this question is, at the time of configuration to single managed server, we get EPM Server Service, then some more services only. But if we do reconfigure to the Own managed server, we will get more services in Services.msc)
I didn't test this yet, just i got this doubt if we do like this what will happens. is it work or not?
Thanks for your valuable time Pablo.
Thanks,
mady

Similar Messages

Deploy to single managed server checked and greyed out while performing upgrade to EPM 11.1.2.4

Hi Gurus,
We are trying to upgrade EPM from 11.1.2.2 to EPM 11.1.2.4 and have applied the maintenance release successfully.
Issue:
When we are trying to configure EPM 11.1.2.4 and are providing the same Shared Service database details, at the summary screen, we are not able to uncheck the option "Deploy to Single Managed server" which is checked and is greyed out.
We have tried the following:
1. We updated the HSS_COMPONENT_PROPERTY_VALUE table and updated the PROPERTY_NAME "isCompact" to false.
2. Modified the config.xml file located at EPMSystem/config and epmsystem1/config to remove the property for compactState.
We are still having the issue where we are not able to uncheck the option for Compact Deployment. Any help would be appreciated.
Thanks in advance.

As it is a maintenance release and it deployed as a single managed server then you will not be able to change the deployment type when applying the maintenance release.
There is a procedure to change a deployment type from compact to single managed server that I created as an internal document.
you may want to give it a go but you would need to test this first as this was an in house test that I carried out.
Hyperion Planning - Version 11.1.2.2.300 and later
Information in this document applies to any platform.
Goal
The scenario:
EPM system 11.1.2.3 was configured and deployed as a single managed server compact deployment so that only one JVM was used for all products EPMServer0.
Later on, due to performance issues, the decision was made to go for using a JVM for each product and get rid of the compact deployment.
The administrator went ahead and redeployed the application servers individually into their own JVM.
However everytime the webserver is reconfigured, the weblogicCluster entry in the OHS file mod_wl_ohs has 2 servers, one for EPMSserver running on port 9000 and another server running on the product default port (as if it was being load balanced)
The aim:
It is clear that initial compact deployment has not been cleared from the EPM environment and the aim in this exercise is to clear the registry and the file system so that the compact deployment is removed fromthe EPMenvironment and we are left with the desired configuration Single JVM deployment for earch web application.
Solution
Caution:
Make sure that you take a backup of the following:
- TheFoundation Services database schema backup
- Take a backup of the following folders:
\Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
\Oracle\Middleware\user_projects\domains\EPMSystem\servers
\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
Disclaimer:
This was tested in House and it worked for this specific environment and it may not work for your environment. So the suggestion is to test first in a development environment and make sure that you take the appropriate backups in case it does not go according to plan.
Use at your own discretion.
Procedure:
1- Run the epmsys_registry to generate the Registry report
2- Search through the report for the word applicationServerDeployment with a corresponding value of configured and take the ObjectID number down for any entry of applicationServerDeployment that has a value of Configured
i.e:
Instance Tasks Configuration (INSTANCE_TASKS_CONFIGURATION)
Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7adf
3- use the object ID of each entry you have taken down throughout the Registry HTML Report to manually set it back to Pending using the following procedure:
                Start a command prompt and set the working directory to
                 \Oracle\Middleware\user_projects\epmsystem1\bin
                run the command:
                 epmsys_registry.bat updateproperty #e4b3a86a82c26941S32ef81a1455fe48473S7adf/@applicationServerDeployment=Pending
                Repeat this command for each ObjectID that has its applicationServerDeployment
                 property set to Configured
4- rerun the epmsys_registry.bat to generate the Registry HTML report and search for applicationServerDeployment in the newly generated report to make sure that they are all set to Pending and there none missed (very Important).
5- Search the registry HTML report this time for EPMServer0 which is the default serverName given to the single managed server deployment (there will be multiple entries)
Take note of the first ObjectID entry in the section header: for example
WORKSPACE_WEBAPP (WORKSPACE_WEBAPP)
Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7bd3
- Start a command prompt and set the working directory to
                 \Oracle\Middleware\user_projects\epmsystem1\bin
- run the command:
                 epmsys_registry.bat view #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
-Note the Parents ID in the output:
For example:
Parent 1
NAME - WORKSPACE_LWA
ID - e4b3a86a82c26941S32ef81a1455fe48473S7bd0
TYPE - LOGICAL_WEB_APP
Parent 2
NAME - HOST:BACHVMPS3TR
ID - e4b3a86a82c26941S32ef81a1455fe48473S7ffe
TYPE - HOST
- Note the single child ID:
For Example:
Child 1
NAME - WebLogic 10
ID - e4b3a86a82c26941S32ef81a1455fe48473S7fd6
TYPE - APP_SERVER
Now run the following command to remove the Link between Parent and child:
epmsys_registry removelink #parentObjectID #childObjectID
In this example that would translate to:
To remove the single child1 link to the WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ):
epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd3 #e4b3a86a82c26941S32ef81a1455fe48473S7fd6
And do the following To remove the link between WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ) and Parent1 and Parent2:
epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
#e4b3a86a82c26941S32ef81a1455fe48473S7bd3
epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7ffe
#e4b3a86a82c26941S32ef81a1455fe48473S7bd3
- Now that the link has been removed, delete the WORKSPACE_WEBAPP component using its ObjectID :
epmsys_registry deletecomponent #parentObjectID
In this example:
epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
- Delete also the Parent representing the WORKSPACE_LWA
epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
Note:So we have now deleted the WEBAPP and LWA for workspace.
6- Repeat steps in section No 5 for every WEBAPP with EPMServer0
7- Start the Weblogic admin console and login
Then go to the left panel and Expand Environment -> Server
Click on Lock & Edit -> Select EPMServer0 -> click on Delete and confirm
Activate Changes and Log off
8- Stop the weblogic admin console server
9- Go to the following location and delete the folder EPMServer0:
\Oracle\Middleware\user_projects\domains\EPMSystem\servers
Delete also EPMServer0 from the following location:
\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
10- Start a command prompt and delete the Windows service that was created for EPMServer0 (if using Microsoft Windows Operating System):
Right click on the service 'OracleHyperion EPM Server - Java Web Application (epmssystem1)' and get its service name i.e: HyS9EPMServer_FOUNDATION1
Run the following command: sc delete HyS9EPMServer_FOUNDATION1
11- Launch the EPMSystem configurator and redeploy the web application server to their own JVM
12- Go to the following location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component and rename the file mod_wl_ohs.conf to mod_wl_ohs.conf.old.
13- Copy the unconfigured mod_wl_ohs.conf file from the location C:\Oracle\Middleware\ohs\ohs\conf to the location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
14- Run the EPM System Configurator again and configure the WebServer to reconfigure the OHS configuration file mod_wl_ohs.conf.
Once done then open the mod_wl_ohs.conf file and make sure that there are no servers configured with Port 9000.
15- Start the services and test the workspace

EPM single Managed Server for all applicatoins vs EPM multiple managed servers

Hi Guys
There are two options of setting my managed serves in weblogic
1 - All application comes under single managed server.
2 - Every application have it's own managed server.
(Please correct me if there are other ways to other than this.)
What are the advantages and disadvantages of both?
Regards

Actually the purpose of these purely lies in your usage and env capacity ..
Suppose I have a test env where in I frequently suppose to restart the services , then I will better go for single managed option as I would not like wasting my time in stopping and starting of services .
Note this will have high RAM burden as you would be starting all the service even if you don't need that .
If you are constantly bringing services up and down you want the control of being able to choose what you are restarting. Lets say in your Test environment you want to change the deployment settings of JVM, change the Planning properties, change Essbase Server settings, you hose FDMEE and need to restart.... this list can easily go on ... you want to be able to restart the individual component rather than everything. You cannot accurately test patches in Test, because they don't simulate Prod - so you have to bank on having another pre-prod environment to do all of this in. You cannot tune accurately, because you have no control over the individual web apps.
As Dattatray said " 2. as there is only one window service, RAM and processor consumption will be less"
as JohnGoodwin said "I am not a fan of the single managed server unless it is for low resourced machine, e.g. laptop or POC, it is more trouble than it is worth."
The RAM usage is going to be lower, not higher.

Deploy() and undeploy() for a single managed server do not work properly

i tried undeploying an application using the following command undeploy('app_name','managed_server1') which in the WebLogic documentation states that this can undeploy the application from the single managed server, but this untargets the application from ALL managed servers.
Is the command being invoked properly for a single managed server deployment?
For the deploy() command, the same issue exists but for deployments. It either deploys to a single vm but cannot be later updated to be re-targeted.

hi,
Is managed servers are in cluster or stand-alone servers? pls check it properly,if so there is no chance to undeploy the application from all servers even if try to undeploy from onr server.
regards,
abhi

ODI - Multiple Java EE Agents on Single Managed Server

Hello All,
Can we configure more than 1 Java EE Agent on single managed server in ODI? I have configured 1 Java EE agent successfully.
Kindly suggest, if this is possible?
Cheers,
Andy.

A default JEE agent is created when you create domain, which is named as OracleDIAgent.
1. In Studio, duplicate the agent, change its name to genAgent, change the web application context to genagent.
2: Go to datasource of genAgent, drop all datasources.
3: Generate server template. put the jar file under odi\common\templates\wls
4: Deploy this template by update the existing domain. Bring up the config.cmd, choose update existing domain.
5: Update the domain using the template that just generated.
Go through the Configuration wizard. (I did not modify anything or configure anything here).
6: The wizard will give information says the deployment was successful.
7: Bring up the admin server and ODI_server1.

Error 401--Unauthorized when deployed on WL Managed server (10.3.3)

Hi,
I created & started a WL-Managed server on my window desktop machine. I deployed to this Managed server, an application which is running without problem on Admin Server. (The managed server is created in the same Domain as that of Admin Server)
However, when I log on to the application on Managed server & enter the UID & PW I get the Error 401--Unauthorized page. The same security works perfectly well for Admin Server.
Any clues what could be going wrong.
Thanks in advance.
Edited by: Prakash Chavan on Feb 28, 2011 4:57 PM

Thanks Faisal,
Here is the log after I add the 2 flags
<Mar 1, 2011 8:59:30 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to RUNNING>
<Mar 1, 2011 8:59:30 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server star
ted in RUNNING mode>
Mar 1, 2011 9:13:27 AM oracle.jbo.uicli.mom.CpxUtils$Visitor logMainApplicationC
px
INFO: zip:C:/JDev11g/Middleware/user_projects/domains/base_domain/servers/Svr0/t
mp/_WL_user/TestTrackApp_V2.0/77qs7f/war/WEB-INF/lib/_wl_cls_gen.jar!/view/DataB
indings.cpx
[JpsAuth] Check Permission
PolicyContext: [TestTrackApp#V2.0]
Resource/Target: [view.pageDefs.ttsPageDef]
Action: [view]
Permission Class: [oracle.adf.share.security.authorization.RegionP
ermission]
Result: [FAILED]
For more information on this failure, please set -Djps.auth.debug.verb
ose=true
I have emailed you the requested log & the config files.
Edited by: Prakash Chavan on Mar 1, 2011 9:35 AM

Deploying application on managed server

Hi All,
I am using Weblogic 6.1sp1 on windows 2000.
I have 2 servers
server name type port
myserver - admin server 7001
vijay - managed server 19001
when i start myserver & then vijay(managed server) It starts ok works fine.But
if try to deploy application on managed server & then try to restart both my managed
server just hangs by giving message.
Starting WebLogic Server ....
Connecting to http://localhost:7001...
<Jan 24, 2002 12:18:04 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Managed
Server "vijay" for domain "mydomain">
It doesn't throw any exceptions but it just hangs.
so will u able to guide me on this.
Thanx
Vijay

Vijay,
are you using the node manager and starting the server from the admin console?
The node manager starts this as a process and sometimes the process is not getting
killed. try to kill the previously started process and it should work fine
ANIL
"vijay" <[email protected]> wrote:
>
Hi All,
I am using Weblogic 6.1sp1 on windows 2000.
I have 2 servers
server name type port
myserver - admin server 7001
vijay - managed server 19001
when i start myserver & then vijay(managed server) It starts ok works
fine.But
if try to deploy application on managed server & then try to restart
both my managed
server just hangs by giving message.
Starting WebLogic Server ....
Connecting to http://localhost:7001...
<Jan 24, 2002 12:18:04 PM EST> <Notice> <WebLogicServer> <Starting WebLogic
Managed
Server "vijay" for domain "mydomain">
It doesn't throw any exceptions but it just hangs.
so will u able to guide me on this.
Thanx
Vijay

Auto-Deployment and Restarting Managed Server

Hi,
We are using WebLogic Server 7.0 SP2 on Solaris 8. Yesterday, a developer copied
over a new WAR file into the applications directory. Then he ried to restart the
managed server. This appeared to hang, so he tried restarting the admin. server,
which also failed. Looking at the log, it looks like the admin. server is trying
to deploy apps. from the applications/backup directory.
After I removed the backup directory and edited config.xml to remove all references
to this directory, I was able to startup the Admin. server (though there were
still some errors; see later) and the managed server.
The servers are actually running in "developemnt" mode and have the Aut-Deploy
feature enabled, so my theory is that the auto-deployment was conflicting with
the managed server restart. He shouldn't have had to restart the managed server
since Auto-Deploy is enabled, right?
I'm also wondering about these errors I got when I the Admin. server finally started:
Starting WebLogic Server...
<May 4, 2004 11:41:04 AM MDT> <Notice> <Management> <140005> <Loading configuration
/wlsapp/prod/ivrprod/./config.xml>
<May 4, 2004 11:41:14 AM MDT> <Notice> <Security> <090082> <Security initializing
using realm myrealm.>
<May 4, 2004 11:41:14 AM MDT> <Notice> <WebLogicServer> <000327> <Starting WebLogic
Admin Server "admin" for domain "ivrprod">
<May 4, 2004 11:41:44 AM MDT> <Notice> <Application Poller> <149400> <Activating
application: appsdirbackup_dir>
<May 4, 2004 11:41:49 AM MDT> <Notice> <Application Poller> <149404> <Activate
application appsdirbackup_dir on admin - Running>
<May 4, 2004 11:41:51 AM MDT> <Notice> <Application Poller> <149404> <Activate
application appsdirbackup_dir on admin - Completed>
<May 4, 2004 11:41:54 AM MDT> <Notice> <Management> <141052> <Application Poller
started for development server.>
<May 4, 2004 11:41:54 AM MDT> <Notice> <Application Poller> <149400> <Activating
application: appsdirbackup_dir-0>
<May 4, 2004 11:41:57 AM MDT> <Notice> <Application Poller> <149404> <Activate
application appsdirbackup_dir-0 on admin - Running>
<May 4, 2004 11:41:59 AM MDT> <Notice> <Application Poller> <149404> <Activate
application appsdirbackup_dir-0 on admin - Running>
<May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000365> <Server state
changed to RUNNING>
<May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000360> <Server started
in RUNNING mode>
<May 4, 2004 11:42:13 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=2268781,name=InternetTroubleshooting,context-path=/backup/
InternetTroubleshooting)] failed to compile /dialogs/ADSLDisambig.jsp, compiler
errors:
/wlsapp/prod/ivrprod/./admin/.wlnotdelete/_appsdir_backup_dir_InternetTroubleshooting_2268781/jsp_servlet/_dialogs/__ADSLDisambig.ja
va:17: package com.nuance.ps.telus does not exist
<May 4, 2004 11:42:20 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=1642582,name=ReportAPayment,context-path=/backup/ReportAPa
yment)] translation of /dialogs/GetStatus.jsp failed: weblogic.servlet.jsp.JspException:
(line 7): class 'com.nuance.ps.telus.Shared
Storage' could not be loaded>
<May 4, 2004 11:42:20 AM MDT> <Notice> <Application Poller> <149404> <Activate
application appsdirbackup_dir-0 on admin - Running>
<May 4, 2004 11:42:22 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=3439810,name=TelusLogin,context-path=/backup/TelusLogin)]
translation of /conf/ClearOldKeys.jsp failed: weblogic.servlet.jsp.JspException:
(line 2): class 'com.nuance.ps.telus.SharedStorage'
could not be loaded>
<May 4, 2004 11:42:22 AM MDT> <Error> <Deployer> <149201> <The Slave Deployer
failed to complete the deployment task with id 16 for
the application appsdirbackup_dir.
weblogic.management.ApplicationException: Prepare failed. Task Id = 16
Thanks,
Paul

The short answer to your question is that auto-deployment and multiple
servers don't mix.
If you have a single-server domain and choose to use auto-deployment,
that'll work fine.
Once you have separate admin/managed servers, you need to use
weblogic.Deployer, the wldeploy ant task (8.1), or the console to deploy
applications.
-- Rob
Paul wrote:
Hi,
We are using WebLogic Server 7.0 SP2 on Solaris 8. Yesterday, a developer copied
over a new WAR file into the applications directory. Then he ried to restart the
managed server. This appeared to hang, so he tried restarting the admin. server,
which also failed. Looking at the log, it looks like the admin. server is trying
to deploy apps. from the applications/backup directory.
After I removed the backup directory and edited config.xml to remove all references
to this directory, I was able to startup the Admin. server (though there were
still some errors; see later) and the managed server.
The servers are actually running in "developemnt" mode and have the Aut-Deploy
feature enabled, so my theory is that the auto-deployment was conflicting with
the managed server restart. He shouldn't have had to restart the managed server
since Auto-Deploy is enabled, right?
I'm also wondering about these errors I got when I the Admin. server finally started:
Starting WebLogic Server...
<May 4, 2004 11:41:04 AM MDT> <Notice> <Management> <140005> <Loading configuration
/wlsapp/prod/ivrprod/./config.xml>
<May 4, 2004 11:41:14 AM MDT> <Notice> <Security> <090082> <Security initializing
using realm myrealm.>
<May 4, 2004 11:41:14 AM MDT> <Notice> <WebLogicServer> <000327> <Starting WebLogic
Admin Server "admin" for domain "ivrprod">
<May 4, 2004 11:41:44 AM MDT> <Notice> <Application Poller> <149400> <Activating
application: appsdirbackup_dir>
<May 4, 2004 11:41:49 AM MDT> <Notice> <Application Poller> <149404> <Activate
application appsdirbackup_dir on admin - Running>
<May 4, 2004 11:41:51 AM MDT> <Notice> <Application Poller> <149404> <Activate
application appsdirbackup_dir on admin - Completed>
<May 4, 2004 11:41:54 AM MDT> <Notice> <Management> <141052> <Application Poller
started for development server.>
<May 4, 2004 11:41:54 AM MDT> <Notice> <Application Poller> <149400> <Activating
application: appsdirbackup_dir-0>
<May 4, 2004 11:41:57 AM MDT> <Notice> <Application Poller> <149404> <Activate
application appsdirbackup_dir-0 on admin - Running>
<May 4, 2004 11:41:59 AM MDT> <Notice> <Application Poller> <149404> <Activate
application appsdirbackup_dir-0 on admin - Running>
<May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000365> <Server state
changed to RUNNING>
<May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000360> <Server started
in RUNNING mode>
<May 4, 2004 11:42:13 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=2268781,name=InternetTroubleshooting,context-path=/backup/
InternetTroubleshooting)] failed to compile /dialogs/ADSLDisambig.jsp, compiler
errors:
/wlsapp/prod/ivrprod/./admin/.wlnotdelete/_appsdir_backup_dir_InternetTroubleshooting_2268781/jsp_servlet/_dialogs/__ADSLDisambig.ja
va:17: package com.nuance.ps.telus does not exist
<May 4, 2004 11:42:20 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=1642582,name=ReportAPayment,context-path=/backup/ReportAPa
yment)] translation of /dialogs/GetStatus.jsp failed: weblogic.servlet.jsp.JspException:
(line 7): class 'com.nuance.ps.telus.Shared
Storage' could not be loaded>
<May 4, 2004 11:42:20 AM MDT> <Notice> <Application Poller> <149404> <Activate
application appsdirbackup_dir-0 on admin - Running>
<May 4, 2004 11:42:22 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=3439810,name=TelusLogin,context-path=/backup/TelusLogin)]
translation of /conf/ClearOldKeys.jsp failed: weblogic.servlet.jsp.JspException:
(line 2): class 'com.nuance.ps.telus.SharedStorage'
could not be loaded>
<May 4, 2004 11:42:22 AM MDT> <Error> <Deployer> <149201> <The Slave Deployer
failed to complete the deployment task with id 16 for
the application appsdirbackup_dir.
weblogic.management.ApplicationException: Prepare failed. Task Id = 16
Thanks,
Paul

How to use jspx deployed in different managed server from bpm work space

Hi,
I have created and deployed my view project having all the jspx files and managed beans into a different managed server(created a new server,not into the soa server).
I have created a bpm process and now I want to use the jspx page(deployed into the new managed server) in my bpm wrokspace.
Can anyone help me how I can do it.
thanks in advance.
Regards,
Tukuna

Hi ,
I tried with the below url and still i am not able to open the jspx page deployed into the admin server.
http://docs.oracle.com/cd/E21764_01/integration.1111/e10224/bp_designtf.htm#BDCFBJIE
28.8.4 How To Deploy a Task Form to a non-SOA Oracle WebLogic Server
Any help on this is appreciatable.
Many thanks
Tuku

Error while deploying to Production Managed Server

My setup is one Domain, one AdminServer, one Managed Server all running in Production Mode.. The AdminServer:7001 and ManagedServer:7003 are on the same box.
I can deploy my app and hit it via a web service on AdminServer:7001 but I can't hit is on the ManagedServer:7003.
What happens is I tell the ODSI Admin Console to target the application to either ManagedServer or ManagedServer and AdminServer. Doing this put's the ManagedServer into an Admin STANDBY mode, lists the following error, and remains in an UNKNOWN state. I eventually have to shut the ManagedServer down and start it again.
The server is running on the latest version of Oracle Mission Control 3.1.0 with the version of JRockit that's in there (1.6.0_11 R27.6.3).
I mean, I'd rather not run the application on the AdminServer. Does anyone have any suggestions on what to look into to try to trouble shoot this issue??
####<Sep 16, 2009 10:02:46 AM EDT> <Error> <Deployer> <computername> <XYZ_ManagedServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1253109766565> <BEA-149231> <Unable to set the activation state to true for the application 'OraclePackage2_request_handlers'.
java.lang.IllegalArgumentException: Session: null does not exist.
 at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:118)
 at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:73)
 at com.bea.dsp.management.activation.ActivationService.dataSpaceAlreadyExists(ActivationService.java:342)
 at com.bea.dsp.management.activation.ActivationService.setRequestHandlerClassLoader(ActivationService.java:206)
 at com.bea.ld.server.bootstrap.RequestHandlerListener.postStart(RequestHandlerListener.java:46)
 at weblogic.application.internal.flow.BaseLifecycleFlow$PostStartAction.run(BaseLifecycleFlow.java:292)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:194)
 at weblogic.application.internal.flow.BaseLifecycleFlow.postStart(BaseLifecycleFlow.java:66)
 at weblogic.application.internal.flow.TailLifecycleFlow.activate(TailLifecycleFlow.java:33)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
 at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
 at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
 at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
 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:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.lang.IllegalArgumentException: Session: null does not exist.
 at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:118)
 at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:73)
 at com.bea.dsp.management.activation.ActivationService.dataSpaceAlreadyExists(ActivationService.java:342)
 at com.bea.dsp.management.activation.ActivationService.setRequestHandlerClassLoader(ActivationService.java:206)
 at com.bea.ld.server.bootstrap.RequestHandlerListener.postStart(RequestHandlerListener.java:46)
 at weblogic.application.internal.flow.BaseLifecycleFlow$PostStartAction.run(BaseLifecycleFlow.java:292)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:194)
 at weblogic.application.internal.flow.BaseLifecycleFlow.postStart(BaseLifecycleFlow.java:66)
 at weblogic.application.internal.flow.TailLifecycleFlow.activate(TailLifecycleFlow.java:33)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
 at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
 at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
 at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
 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:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>

Hey ,Can you please help me?can you tell me how you resolved this issue.Our production is down due to
java.lang.IllegalArgumentException: Session: null does not exist.
 at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:118)
 at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:73)
 at com.bea.dsp.management.activation.ActivationService.dataSpaceAlreadyExists(ActivationService.java:342)
 at com.bea.dsp.management.activation.ActivationService.setRequestHandlerClassLoader(ActivationService.java:206)
 at com.bea.ld.server.bootstrap.RequestHandlerListener.postStart(RequestHandlerListener.java:46)
 Truncated. see log file for complete stacktrace.
Its urgent plz

SOA OSB Single Managed Server Why?

I am trying to understand why the option exists to run OSB and SOA in the same managed server (same jvm). Can someone answer this question for me please? I inherited a SOA/OSB server and the previous administrator has taken this approach. I have not been able to find any documentation on the subject, it is briefly mentioned in the OSB install guide but with out explanation as to why someone would want to do this http://docs.oracle.com/cd/E23943_01/doc.1111/e15017/configure_osb.htm#BGBDGGBE
Thanks

Troubleshooting Interoperability Between OSB and SOA Suite 10g and 11gR1 [ID 1267207.1]
Should OSB and SOA Suite Run in one single JVM?
To run OSB and SOA Suite in one single JVM, i.e. one single WebLogic Server instance, is very handsome for scenarios that only have low load and low memory requirements. For these development or test systems, OSB and SOA Suite can be set up to run in one of the following topologies:
Both OSB and SOA Suite in one single Admin Server (supported in 11.1.1.4 and upwards).
In a domain with one Admin Server and one single, non-clustered managed server to run OSB and SOA Suite on it (supported in 11.1.1.3 and upwards).
However, this is only recommended and supported for development or test environments.

Deployment problem in managed server environment

 I have a problem deploying a connector as a .rar-file. The file contains the two deployment
 descriptors and a .jar-file containing the connector classes. If I deploy the connector
 in a non-managed server (for instance the admin server), there is not a problem at
 all. But if I deploy the connector to a server that is managed I get an exception
 indicating that the resource manager could not find my javax.resource.spi.ManagedConnectionFactory
 implementation.
 If I put the .jar-file containing my connector implementation classes into the system
 classpath when booting the managed server, the problem is solved. The problem is
 that I don't want this .jar-file in the system classpath.
 Is this a known bug with any workarounds?
 Environment:
 Windows 2000
 WLS 6.1 SP 3
 JDK 1.3.1


 Hi Leif,
 I believe that there is a patch that resolves this problem. Could you please ask
 BEA Support for the 6.1 SP2 patch called CR078437_61sp2.jar. You would need to
 put this .jar on the front of your WLS classpath. This patch was created for 6.1
 SP2 but I believe should work for SP3 as well.
 Deb
 >As I wrote:
 >WLS 6.1 SP 3
 >
 >"Jim Gish" <[email protected]> wrote:
 >>What version (including service pack number) of Weblogic Server are
 >you
 >>using?
 >>
 >>"Leif Kristian Vadseth" <[email protected]> wrote in message
 >>news:[email protected]...
 >>>
 >>> I have a problem deploying a connector as a .rar-file. The file contains
 >>the two deployment
 >>> descriptors and a .jar-file containing the connector classes. If I
 >>deploy
 >>the connector
 >>> in a non-managed server (for instance the admin server), there is
 >not
 >>a
 >>problem at
 >>> all. But if I deploy the connector to a server that is managed I get
 >>an
 >>exception
 >>> indicating that the resource manager could not find my
 >>javax.resource.spi.ManagedConnectionFactory
 >>> implementation.
 >>>
 >>> If I put the .jar-file containing my connector implementation classes
 >>into
 >>the system
 >>> classpath when booting the managed server, the problem is solved.
 >The
 >>problem is
 >>> that I don't want this .jar-file in the system classpath.
 >>>
 >>> Is this a known bug with any workarounds?
 >>>
 >>> Environment:
 >>> Windows 2000
 >>> WLS 6.1 SP 3
 >>> JDK 1.3.1
 >>>
 >>
 >>
 >

Exception while to deploy ear at managed server

I have a wli cluster version 8.1 sp3. It has two nodes. The node that is hosted in a machine different machine from admin server displayes a message
 javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/MY_DOMAIN/./adminServer/upload/xxx/xxx.ear
 whenever it starts. But the application seems to starts correctly.
 This node has different path than the other.
 It is /appl/webdbus/bea/user_projects/
 I can not find anything relating in newsgroups. Can anyone explain me why this happens.

Hi,
 My suspicion about the exception is the it's caused by the different directory structure of the two nodes. As you can see at bold words, weblogic tries to create ear at a directory that does not exist at this node. It finds the latter webbus from the path of admin server at the other machine. My question is straightforwad, Can we have different paths at cluster nodes ? In this case, Should we deploy ear (webservice application) in a different way ?
 <Feb 22, 2005 12:33:26 PM EET> <Info> <Deployer> <BEA-149060> <Module faxManWeb of application faxManAppl successfully transitioned from prepared to active on server wliBusServerPatmosDevel.>
 javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/adminServerDevel/upload/faxManAppl/faxManAppl.ear
 at weblogic.management.internal.BootStrap.apply(BootStrap.java:580)
 at weblogic.management.internal.BootStrap.apply(BootStrap.java:474)
 at weblogic.management.mbeans.custom.Application.getFullPath2(Application.java:3476)
 at weblogic.management.mbeans.custom.Application.getFullPath(Application.java:3055)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
 at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
 at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java(Compiled Code))
 at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java(Compiled Code))
 at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Compiled Code))
 at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Inlined Compiled Code))
 at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java(Compiled Code))
 at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java(Compiled Code))
 at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java(Compiled Code))
 at weblogic.management.configuration.ApplicationMBean_Stub.getFullPath(ApplicationMBean_Stub.java:543)
 at com.bea.wli.broker.manifest.ApplicationManager.load(ApplicationManager.java:71)
 at com.bea.wli.broker.MessageBroker.registerApplication(MessageBroker.java:999)
 at com.bea.wli.management.WLIAppListener$1.run(WLIAppListener.java:294)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at com.bea.wli.management.WLIAppListener.applicationInitialized(WLIAppListener.java:290)
 at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:46)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721)
 at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2201)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2094)
 at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:2976)
 at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751)
 at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359)
 at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
 at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
 at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
 at weblogic.Server.main(Server.java:32)
 --------------- nested within: ------------------
 weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
 [javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/adminServerDevel/upload/faxManAppl/faxManAppl.ear]
 at weblogic.management.mbeans.custom.Application.getFullPath2(Application.java:3479)
 at weblogic.management.mbeans.custom.Application.getFullPath(Application.java:3055)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
 at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
 at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java(Compiled Code))
 at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java(Compiled Code))
 at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Compiled Code))
 at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Inlined Compiled Code))
 at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java(Compiled Code))
 at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java(Compiled Code))
 at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java(Compiled Code))
 at weblogic.management.configuration.ApplicationMBean_Stub.getFullPath(ApplicationMBean_Stub.java:543)
 at com.bea.wli.broker.manifest.ApplicationManager.load(ApplicationManager.java:71)
 at com.bea.wli.broker.MessageBroker.registerApplication(MessageBroker.java:999)
 at com.bea.wli.management.WLIAppListener$1.run(WLIAppListener.java:294)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at com.bea.wli.management.WLIAppListener.applicationInitialized(WLIAppListener.java:290)
 at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:46)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721)
 at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2201)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2094)
 at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:2976)
 at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751)
 at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359)
 at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
 at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
 at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
 at weblogic.Server.main(Server.java:32)

Weblogic deployment ( admin and managed server)

I have one AdminServer and One ManageServer running on the same IP Address with
different ports,
AdminServer and ManagedServer is coming up without any errors, I able to access
the index.jsp using the following URLs
http://hostname:7001/index.jsp (Admin Server)
http://hostname:8001/index.jsp (Managed Server)
my index.jsp I have several other hperlinks ( say contacts, help etc)
Once my servers ( admin and managed ) are started successfully, I'm able to browse
thru my application using the first URL.
but if I accessed the application using the second URL the index.jsp is coming
from port no (8001), which I observed thru the access.log and if I click any other
links(contacts, help) in the index.jsp, it is access the jsps from (7001) instead
of 8001.
I think in my Jsp I'm using a wrong mechanism to read the URL, what is the proper
way to read the correct URL?
Please help me to sort out this issue

Tested and got it worked.

Deployment on managed server

Problem deploying app on managed server:
testEAR.ear is built using wlpackage ant task, but it still causes the exception
while deploying
on managed server:
Exception:weblogic.management.ApplicationException: Application testEAR is packaged
using
the WebLogic Split Development Directory structure. The Split Development Directory
structure
can only be used in development environments with a single WebLogic Server. If
you wish to
deploy this application to a separate managed server or cluster, use the wlpackage
ant task to
create an exploded or archived EAR.
build.xml part:
<taskdef name="wlpackage" classname="weblogic.ant.taskdefs.build.WLPackageTask"
classpathref="task.classpath"/>
<target name = "package" description = "Create exploded or arhived AER" depends
= "build">
<wlpackage srcdir="test" destdir="." toFile="testEAR.ear"/>
</target>
Ant doesn't alerts any errros.
What is the problem?

Can you show me the output of jar tvf testEAR.ear?
Also, please show me the Application snippet from your config.xml
-- Rob
vinni wrote:
Problem deploying app on managed server:
testEAR.ear is built using wlpackage ant task, but it still causes the exception
while deploying
on managed server:
Exception:weblogic.management.ApplicationException: Application testEAR is packaged
using
the WebLogic Split Development Directory structure. The Split Development Directory
structure
can only be used in development environments with a single WebLogic Server. If
you wish to
deploy this application to a separate managed server or cluster, use the wlpackage
ant task to
create an exploded or archived EAR.
build.xml part:
<taskdef name="wlpackage" classname="weblogic.ant.taskdefs.build.WLPackageTask"
classpathref="task.classpath"/>
<target name = "package" description = "Create exploded or arhived AER" depends
= "build">
<wlpackage srcdir="test" destdir="." toFile="testEAR.ear"/>
</target>
Ant doesn't alerts any errros.
What is the problem?

EPM 11.1.2.x deployment to single managed server

Similar Messages

Maybe you are looking for