- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 68 Insurance
- 536.8K On-Premises Infrastructure
- 138.5K Analytics Software
- 38.6K Application Development Software
- 5.9K Cloud Platform
- 109.5K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.2K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
22.214.171.124-126.96.36.199 BR->Calcmgr Folder doesn't exist after migration
We are running through an upgrade from 188.8.131.52-< 184.108.40.206 and running into several problems with the business rules migration.
We ran the prerequisite steps to the migration according to the indications in the whitepaper on BR->Calmgr migration and the prerequisite steps in the maintenance section of the installation manual:
So far I am running into 2 issues in unrelated apps:
Issue 1: Project not imported as folder/security isn't complete.
1. An app ran the migration in Calcmgr without errores and I validated the rules, sequences, and macros against their counterparts which appear correct.
2.. Deployed to rules to planning as per instructions
3. I imported the security as per instructions (it ran as far as I can see without errors.
However after the import I don't see a folder for the project that existed in Business Rules. I only see a single person with access to one rule, the rest of the rules are not visible in the business rules security functionality. The hbrRules.xml is from the exact same environment so the native user ids (also the unique id) are the same. Any bids as to why the folder is missing?
Issue 2: Errors in calcmgr migration step from HBR
In a different app I ran into errors in the import. Part of the rules were imported but for a subset I saw errors like these:
Error:None of the launch locations defined for the rule <rulename> match the location the rule was migrated to.
RuleSet <sequence_name>. Some of the sequences got imported by went into several different apps.
I know that the rules at least were left with no outline association as indicated in the documentation, and the location was specified carefully and the access tab was checked to ensure it matched the location. No all locations and at least one location and one security declaration was left in each rule. (I did thid myself).
However the sequences launch variables were left as associated with the locations of the rules but some were left empty. Could this be provoking my problem? The empty ones were usually because the sequence had multiple execution database declarations not compatible with the rules participating in it and we weren't sure how to handle the fact that the subset rules weren't always pointing to the same location.
Anyone know how to fix this? I am stuck with a database and an XML as I no longer have HBR in the easconsole after the upgrade so I image I'd have to change this by hand?
Really pressed for time on this upgrade so your help is very appreciated.
Message was edited by: Agnete