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

Question

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.

Answer 1

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