Migrate business rules (disaster recovery)

I need a plan to be able to recover all my business rules/macros/sequences/projects/security in case of a disaster. Can some one suggest the best way to do this? I'll appreciate if some one can provide a step by step solution that can be automated.
thanks
Edited by: user507721 on Dec 2, 2010 1:14 PM

9.3. That's what we do right now. But it involves manual intervention. Since I want it for DR, I wanted to automate the export so that I don't have to kick it off regularly and have an xml from production in case of any disaster. Is there a way to automate this process?

Similar Messages

Error while migrating business rules

While trying to use the export/import option in EAS to migrate business rules, we have run into an error.
The export itself is fine. When trying to import, it says this:(even though it lets me select the proper xml file for importing)
Error while migrating business rules.
Detail: The import file specified is not a valid business rules xml file. Import will be terminated.
Detail:Exception occured. Please check your log file for details.
I am pretty sure I used the inherent format specified for exporting the business rules.
Both the old and new systems are version 11.1.2.
The LCM method also failed for the business rules migration.
Any suggetions?
Thanks,
Sujani

When you export them make sure you don't have "For Calc Mgr" checked, if you do then the import with fail.
Cheers
John
http://john-goodwin.blogspot.com/

Proper way to Migrate Business rules

Hi all.
I have a question about migrating business rules from DEV to PROD with 2 seperate Shared Services instance
I usually do an Import / Export of BR using EAS and then manually setup the projects and security. While this way seems working ok. I wonder if there is a more official way to do this.
I've seem a Migrate Repository option but am unsure what that suppose to do. I have a feeling that it's not quite what I am looking for. Any advice is greatly appreciated.

Hi,
The two methods are pretty much the same in what they do.
When you export rules it creates an xml file based on the selection you have picked, you can just log into EAS and do this you don't have knowledge about the repository, it is also useful for migrating across versions. You also have the option of changing the xml file before importing it into your target.
When you migrate the respository you have to physically connect to the database repository and have knowledge of the connection details, it is probably aimed directly at a system admin.
The options in both methods are pretty much the same, you can choose what you want to export or migrate.
You hit issues when you export/migrate for instance the location names change and need to be updated, you can update the xml file to change the locations though if you choose the migrate option you won't have that ability.
The next issue is the user/group accounts which is the biggest flaw, if the users/groups exist on the target and have the exact same SID then they will migrate otherwise they will usually get dropped.
Cheers
John
http://john-goodwin.blogspot.com/

Error in migrating business rules

Hi,
We are moving from Dev to QA. In order to migrate business rules, i exported all the rules,global variables and macros by unchecking the calc manager option. Now i replaced all the occurences of my old server name in the xml file with the new server name. Now when i try to open the business rule i get "java.lang.nullpointerexception". Is this any installation issue or i have dont migration wrongly? And i am not able to associate with the outline since i get this error.
What could be the solution?
Regards,
Ragav.

Have to clicked on the dependents while exporting the rules?
and anyways you can copy and paste the rules from one server to another.
Suggestion:
Copy export a rule first, make proper changes and import that rule, rather then going for bulk.
If ur on system 11 use LCM.

Migrate Business Rules from 9.x to 11.x

I am trying to migrate business rules from 9.21 to V11.1.1.3
I used to export the rules, then edit the XML for the correct server and location names, then import into the target server-all with 9.21
Now when I try the same process, I get this error when importing into V11.1.13
Detail:Error while importing object properties.
Detail:com.hyperion.hbr.beans.UserObjAccessFilter.setUserGroupName(java.lang.String)
I can use the migrate repository option just fine, but then I have to go in with a SQL script and update the location and server names in the relational tables. I prefer the export/import since I can do that without impacting users.
Any ideas on how to import the rules and resolve this error?
Thanks
Jeff

Hmm no luck with one rule that has no security assigned to it. and no luck with one project with no security.
Here is the xml for 1 rule that won't import:
<?xml version="1.0" encoding="UTF-8" ?>
- <HBRObjects>
- <Rules>
- <Rule>
<property class="java.lang.String" method="setBody" value="ACED00057372001E636F6D2E6879706572696F6E2E6862722E636F72652E52756C65426F6479047B4D7ABDC064F60200065A000564697274795A000B697347726170686963616C4C0007636F6D6D656E747400124C6A6176612F6C616E672F537472696E673B4C000A636F6D706F6E656E747374002C4C636F6D2F6879706572696F6E2F6862722F67726170686963616C2F47726170686963616C566563746F723B4C000872756C655465787471007E00014C000473616C3071007E000178700000740000707402192F2A4553535F4C4F43414C4520456E676C6973685F556E697465645374617465732E4C6174696E314042696E6172792A2F0A534554204147474D49535347204F4E3B0A5345542055504441544543414C4320204F46463B0A0A46495820284275646765742C20223173742050617373222C20264375727242756459722C20404C45564D4252532822506572696F64222C2030292C4072656C61746976652822546F74616C20456D706C6F79656573222C30292C4052454C41544956452822546F74616C20436F6D70616E79222C3029290A0A2043414C432044494D2028224163636F756E7422293B0A0A22456D706C6F79656520546178657322203D2022456D706C6F79656520546178205261746520496E707574222D3E224E6F20456E74697479222D3E224E6F20456D706C6F79656522202A2022546F74616C2053616C617279223B0A0A22456D706C6F7965652042656E656669747322280A0A494620282246542F505422203D3D31290A0A22456D706C6F7965652042656E6566697473223D2242656E65666974205261746520496E707574222D3E224E6F20456E74697479222D3E224E6F20456D706C6F7965652220202A2022546F74616C2053616C617279223B0A454C53450A22456D706C6F7965652042656E6566697473223D234D495353494E473B0A454E4449460A290A454E444649580A0A43414C432044494D202822456D706C6F796565222C456E74697479293B0A0A0A71007E0004" />
<property class="java.lang.String" method="setMetadataReferences" value="" />
<property class="java.lang.String" method="setDefMetaDataRepo" value="Planning/balt-hypplan/CorpBud/Eeplan" />
<property class="java.lang.String" method="setBodyAsCalcScript" value="/*ESS_LOCALE English_UnitedStates.Latin1@Binary*/ SET AGGMISSG ON; SET UPDATECALC OFF; FIX (Budget, "1st Pass", &CurrBudYr, @LEVMBRS("Period", 0),@relative("Total Employees",0),@RELATIVE("Total Company",0)) CALC DIM ("Account"); "Employee Taxes" = "Employee Tax Rate Input"->"No Entity"->"No Employee" * "Total Salary"; ENDFIX CALC DIM ("Employee",Entity);" />
<property class="java.lang.String" method="setName" value="Corp-EE Benefits & Taxes Calc" />
<property class="long" method="setLastModified" value="1211738336600" />
<property class="java.lang.String" method="setVersion" value="" />
<property class="int" method="setId" value="220" />
<property class="java.lang.String" method="setDescription" value="" />
<property class="java.lang.String" method="setOwner" value="native://DN=cn=911,ou=People,dc=css,dc=hyperion,dc=com?USER" />
<property class="int" method="setObjectType" value="1" />
<property class="boolean" method="setEditable" value="false" />
<property class="boolean" method="setLocked" value="false" />
<property class="java.lang.String" method="setLockedBy" value="0" />
<property class="java.lang.String" method="setUpperName" value="CORP-EE BENEFITS & TAXES CALC" />
<property class="java.lang.String" method="setModifiedBy" value="native://DN=cn=911,ou=People,dc=css,dc=hyperion,dc=com?USER" />
<property class="java.lang.String" method="setOpenForEditingBy" value="0" />
<property class="boolean" method="setOpenForEditing" value="false" />
</Rule>
</Rules>
<Macros />
<Variables />
<Sequences />
<Projects />
<RuleMacroLinks />
<RuleVariableLinks />
<MacroMacroLinks />
<MacroVariableLinks />
<SequenceItemLinks />
<SeqPrompts />
<ProjectItemLinks />
- <UserObjAccessFilters>
- <UserObjAccessFilter>
<property class="int" method="setObjectID" value="220" />
<property class="int" method="setObjectTypeID" value="1" />
<property class="int" method="setLocationID" value="9" />
<property class="int" method="setTaskID" value="2" />
<property class="java.lang.String" method="setUserGroupID" value="0" />
<property class="int" method="setUserGroupTypeID" value="0" />
<property class="boolean" method="setSearchNoLoc" value="false" />
<property class="boolean" method="setSearchNoUser" value="false" />
<property class="boolean" method="setSearchNoObj" value="false" />
<property class="boolean" method="setSearchNoTask" value="false" />
<property class="java.lang.String" method="setUserGroupName" value="" />
</UserObjAccessFilter>
</UserObjAccessFilters>
- <Locations>
- <Location>
<property class="int" method="setCluster" value="0" />
<property class="java.lang.String" method="setLocation" value="Planning/balt-hypplan/CorpBud/Eeplan" />
<property class="int" method="setLocID" value="9" />
<property class="java.lang.String" method="setUpperLocation" value="PLANNING/BALT-HYPPLAN/CORPBUD/EEPLAN" />
</Location>
</Locations>
</HBRObjects>
I see the setUserGroupName property class and it is empty..

How to Migrate Business rules along with access privileges

Hi All,
I migrated business rules from prod to dev using lcm. The business rules got migrated correctly, but the access privileges did not. I tried exporting from EAS and import. Even then the access privileges were not migrated.How do we migrate business rules along with access privileges? Quick help is much appreciated.
We are on hyp. planning 11.1.1.3. and we use classic planning applications.
Thanks
Lakshmi

If they are native users/groups then it may be down to the ID for the users/groups being different across environments, this has always been a problem with business rules, with planning applications then there is the updateusers utility to sync up the ID with shared services.
Cheers
John
http://john-goodwin.blogspot.com/

How to migrate business rule

I have created one Configurable business rule for Position in Development instance...
I want to Migrate business rule created in dev instance to PROD instance.
I want the steps to Migrate. Is there any FNDLOAD command available for this..???
Thanks in Advance...

i want to crate a business rule to aggregate data from level 0 to parent level for one partcula data form^^^These are oldies but goodies:
http://camerons-blog-for-essbase-hackers.blogspot.com/2009/06/why-i-hate-and-love-business-rules-part.html
http://camerons-blog-for-essbase-hackers.blogspot.com/2009/06/why-i-hate-and-love-business-rules-part_17.html
Cost per Unit = Total Revenue/Unit^^^Are you asking if it makes sense to calculate this ratio at all levels of the database or only at the top level? If you mean that it only makes sense at level zero, you could use a FIX statement to select all level zero members and then perform the calculation. Based on the formula, I would think you could get away with a dynamically calculated member formula, assuming Total Revenue is dynamically calculated as well. Generally, level zero calcs in a business rule are only required if there's a percentage involved; if the formula is valid at aggregated levels, make it dynamic unless reporting performance (I have seen dense formulas that go across many, many blocks -- bad idea) falls off a cliff.
Regards,
Cameron Lackpour

Migrate Business Rules by generating XML

Hi BRF plus experts,
for a project I am currently assigned to I am trying to find an easy way to convert business rules from a legacy systen into BRF Plus v7.
Using XML export functionality and a few simple decision tables and rules the XML structure of exported expression is clear to me. Using the legacy system I can create an Excel extract with contains the required rules characteristics. Due to the large amount of rules (600+) and the fact that the rules as part of the migration are being cleansed I am looking for an automated way of generating an XML file containing the required rules and then import these.
Using VBA is not too difficult to generate the correct XML structure and data.
A problem I am facing however is to understand the identifiers, for example
<FDTNS:APPLICATION_ID>4AA45F9249F46590E10000000A71030D</FDTNS:APPLICATION_ID>
<FDTNS:ID>4BE03E7AEBD93E36E10000000A71030D</FDTNS:ID>
<FDTNS:EXPRESSION_TYPE_ID>0000EEEE001000FFFFFFFFFFFFFFFFFF</FDTNS:EXPRESSION_TYPE_ID>
<FDTNS:RESULT_DATA_OBJECT>4AA8B5FD8800276EE10000000A71030D</FDTNS:RESULT_DATA_OBJECT>
Can somebody provide an explanation on the structure of these ID's? I am assuming there must be a type identifier and some kind of counter included.
Many thx for some support on this.
Regards
Edde Voorheijen

Hi Edde,
what version of BRFplus are you planning to use? I only can assume that "v7" refers to NW 7.0. But the important point here is the Enhancement Package you are on.
I would do it in the following way:
1. Create an XML or cvs file with a well defined structure.
2. Create an ABAP report to upload and convert the data into ABAP (there is lots of reuse available).
3. Create the rules with the BRFplus ABAP API (see package SFDT_DEMO_OBJECTS). Therefore you first should model some parts to:
- understand how the rules could look like in BRFplus
- create some parts like function and data objects that you do not need to create by API but just use
The large volume indicates that you need to use BRFplus in NW 7.0 EhP 2. There you also find a big variety of options in the ruleset that will make the upload easy.
The ID is a technical ID that is generated. Actually it is a UUID.
BR,
Carsten

Migrate Business Rules to Calculation Manager

Hi Friends,
we have Hyperion Planning v11.1.1.3 Application (Classic Application). I want to migrate from Business Rules to Calculation Manager.
Please let me know the procesure.
Thanks & Regards
Sai.

In EAS go to export, select the rules, make sure "for calc mgr" is ticked.
Import the rules into calc manager.
Cheers
John
http://john-goodwin.blogspot.com/

Business Rules Migration

Hi gurus,
I need to migrate business rules from one environment to another.
Apart from doing so in EAS, what would be the other way of migrating it?
Any suggestion would be appreciated.
I could do it with EAS, however the EAS has not been working in the target environment, so we are trying to see if we can migrate from planning/hss etc so that we could migrate and test while we are taking care of the EAS issue.
Thank you.

If EAS is not working in the target environment then I don't see much point in trying to migrate the rules, you would not be able to import them if EAS is not working.
The only options are exporting/importing through EAS, LCM (which pretty much does the same thing as EAS but can be automated), alternatively there is the option to migrate the full repository - Migrating the Repository
Cheers
John
http://john-goodwin.blogspot.com/

Upgrade Business rules with Calc Manager

Hello Gurus,
Recently performed an upgrade from 11.1.1.3 to 11.1.2.2 by replicating the Database to a new database machine.
I had Business rules in 11.1.1.3 and did not perform any steps to migrate the rules to Calculation manager in 11.1.2.2
The doubt I have is,
1. Are the business rules automatically upgraded when performing upgrade by EPM system configurator (since the database is replicated)
2. If so, how do I see the business rules in 11.1.2.2 environment? How can I use migrate feature option.
Thanks
HyperionEPM.

From 11.1.2.2 documentation:
Upgrade Wizard
If your application used Oracle Hyperion Business Rules, the Upgrade Wizard automatically converts Business Rules business rules to Oracle Hyperion Calculation Manager business rules. Release 11.1.2.2 supports onlyBusiness Rules business rules as the calculation module.
Notes:
•Classic application administration is now called Oracle Hyperion Planning application administration (versus Oracle Hyperion EPM Architect application administration).
•The Upgrade Wizard automatically upgrades applications having Oracle Hyperion Business Rules business rules, converting them to Calculation Manager business rules. However, the Upgrade Wizard does not automatically convert Release 11.1.2.1 applications having Oracle Hyperion Calculation Manager business rules. For those upgrade instructions, see the Oracle Enterprise Performance Management System Installation and Configuration Guide.
Business Rules Maintenance Release and Upgrade Installation PrerequisitesIf you are using Business Rules, you must migrate to Calculation Manager rules in Release 11.1.2.2. Before migrating business rules, you must perform prerequisite tasks. Note that these tasks are required if you are applying the maintenance release or if you are upgrading.
To prepare to migrate Business Rules, perform the following tasks in your current Business Rules environment before installing Release 11.1.2.2:
1.in Business Rules, within the Rule Editor, remove the associated outline (that is, the design time location) from each business rule. After you do this, the Associated Outline drop-down list should display the text, Select Outline.
2.On the Locations tab of the Rule Editor, ensure that each business rule has a valid launch location, which must be an absolute location. Although “All Locations” is valid in Business Rules, when you migrate business rules, you must provide the details of a specific launch location (that is, the application type---Planning or Essbase, the server name, the application name, and the database or plan type). If you want a business rule to be valid for multiple launch locations, you must provide the details for each location. The locations must be in different applications; you cannot migrate the same business rule to different plan types in the same application within Calculation Manager.
If the rule is a part of a sequence, then the launch location of the rule within the sequence must be one of the launch locations listed in the Locations tab of the rule.
3.On the Access Privileges tab of the Rule Editor, ensure that each business rule has security defined for a specific location or locations and not “All Locations.” If multiple locations are defined for a business rule on its Locations tab, you must add security for each location individually.
4.Do not modify rules in Calculation Manager until migration is completed.
5.If you are using Business Rules with Planning, as a precaution, create a backup of the rules: Use Administration Services to export the rules to XML in Business Rules format. If you are upgrading from 11.1.1.3 or 11.1.1.4, also export the rules to Calculation Manager format. EPM System Configurator exports the rules during database configuration for use during application upgrade.
6.If you are an Essbase-only Business Rules user, you must export business rules. To export the Essbase rule from Business Rules:
a.From Administration Services Console, right-click the Business Rules node and select Export.
b.Export the rules in Business Rules format and then select all of the Essbase rules in the repository. If you are upgrading from 11.1.1.3 or 11.1.1.4, also export the rules to Calculation Manager format.
c.Specify the location to save the XML file, and then click OK. If you are upgrading, the location should be a shared drive that is accessible from the upgraded environment.
Make a note of the location. You import the file later in the process.
Migrating Business Rules to Calculation Manager for use with Planning
If you applied the maintenance release to move from Planning Release 11.1.2.0 or 11.1.2.1 to Release 11.1.2.2, and you were using Business Rules rules, you must migrate the rules to Calculation Manager rules.
Before you migrate, ensure that user directories and native users with the same SID are available when you upgrade Shared Services.
Ensure that the Planning applications are upgraded to the current release and are available in Calculation Manager under SYSTEM View.
To migrate Business Rules rules to Calculation Manager rules:
1.In Calculation Manager, select the migrated Planning application, and then select Migrate.
The data that was exported during database configuration with EPM System Configurator is imported to Calculation Manager.
2.Repeat for each Planning application.
3.Deploy the rules from Calculation Manager to Planning. See the Oracle Hyperion Calculation Manager Designer's Guide.
After migrating business rules and rules security, if any of the rules had multiple launch locations and you migrated to more than one location, Calculation Manager creates a rule for the first migration, and shortcuts for all subsequent migrations. If the rule had rule-level variables, for the shortcuts that are created in the application in the new environment , its variables are moved to the Plan level. In this scenario, test rules in your environment to ensure that they work as expected.
If you still have problems, raise an SR and we can get on a call to figure out why the rules are not coming over.
-Sree

Migration of Rules from BRF to BRFPlus

Hi Folks,
Can we migrate business rules maintained in BRF in BRF+ ?

Carsten Ziegler said here that there is no such tool:
At an earlier planning stage of the BRFplus project, it was intended to offer a migration tool for migrating rules modeled in BRF to BRFplus. However, after some research and tests, we have canceled this approach. It turned out that, for technical and conceptual reasons, a 1:1 migration would not lead to a desirable result. You would not have been able to leverage the capabilities of BRFplus, and the result would not have been satisfying.
Maybe you can use the BRFplus API to make the migration easier by automation.
Best Regards,
Tobias

Business Rules migration to Calc Manager

Hi there,
We are currently in 11.1.2.1 and looking at applying the 11.1.2.2 patch. One of the pre-requisites is the HBR migration to Calc Manager. We are trying to find out if there is a better way of preparing the business rules for migration to calculation manager in a distributed environment. We have three planning servers and approx. 4-8 security groups assigned to a business rule. According to the documentation we now have to assign permissions to each planning server (location) individually and then assign each security group individually to each planning server (location). This means a single rule can have up to 27 objects that need to be assigned. When we start talking about 100’s rules & sequences this really adds up. Is there an easier way to do this in a distributed environment.
I have raised an SR with Product Support who have raised an enhancement request and referred me to consulting however this sounds more like a product issue to me.
Thanks for your help.
Regards
Seb

Hi Seb,
I think there may be a somewhat easy answer here. Have you looked at the locations under business rules? You may right click on a location and copy it to another location. I'm pretty certain it copies all security over to the second location also.
Suggest you test this in a non-prod environment if you have one available.
Regards,
John A. Booth
http://www.metavero.com

How to migrate Planning from Production to Disaster-Recovery server?

We are using Planning 11.1.1.3 Oracle repository. Presently our DR Planning Application name is different than production's name, and the DR's Windows server names are different from Production's. Otherwise, all other configuration the same.
How do we migrate Planning from Production to Disaster-Recovery server? We stopped Planning on DR server. Then we exported production planning Oracle repository and imported it to DR Planning. We restarted DR's Planning. DR planning seems to be running fine, but I am afraid to click "Refresh Planning" on DR Planning - it might update Production server. So how can I be sure DR and Production planning are disconnected ?
Is there anything we need to do? This method seems to be faster than migrating with LCM.
Edited by: Essbase Fan on Oct 18, 2010 10:11 AM

You are definitely go about it the correct way, if you are migrating the whole planning application I have to agree it is a safer and quicker route.
The connection information to essbase is stored in the planning system database/schema so as long as you have not migrated that then you should be good to refresh.
To put your mind at rest, log into the planning application and edit the datasource associated with the application then you will see where the essbase server is it is going to refresh.
Cheers
John
http://john-goodwin.blogspot.com/

Business Rules Migration from one server to other server

Hi All,
Can some body help on business rules migration from one server to other server? and also wt is the difference there in Export and import BR's and Administration repository to migrate.........i fail to understand if we export and import br's and need to change in xml target server and after import whether all users can able to see this imported BR's ?
then wt is the use of Administration option under Business Rules-->right click-->repository...connect--->need to connect oracle info....wt is this process? can some body help on this please........
thanks,
huser

Hi,
The methods are pretty much the same in what they do.
When you export rules it creates an xml file based on the selection you have picked, you can just log into EAS and do this you don't have knowledge about the repository, it is also useful for migrating across versions. You also have the option of changing the xml file before importing it into your target.
When you migrate the respository you have to physically connect to the database repository and have knowledge of the connection details, it is probably aimed directly at a system admin.
The options in both methods are pretty much the same, you can choose what you want to export or migrate.
You hit issues when you export/migrate for instance the location names change and need to be updated, you can update the xml file to change the locations though if you choose the migrate option you won't have that ability.
The next issue is the user/group accounts which is the biggest flaw, if the users/groups exist on the target and have the exact same SID then they will migrate otherwise they will usually get dropped.
Cheers
John
http://john-goodwin.blogspot.com/

Migrate business rules (disaster recovery)

Similar Messages

Maybe you are looking for