Namespace Migration – Pre-Engagement Checklist The purpose of this memo is to gather key information use for pricing related to namespace migration. This document is the initial in-take document that serves as a means of clarification and to set client expectations. Background For clients with Cognos 8 or 10, moving off of the Series 7 namespace to another target namespace generally involves conversion in three areas: migrating users and groups from one namespace to another, converting security in existing models, and converting security in the Content Store. The high level work breakdown structure is shown below. The remainder of this document specifies questions that are relevant for pricing of a namespace migration effort. Motio Namespace Migration Checklist Page 1 of 13
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Namespace Migration – Pre-Engagement Checklist
The purpose of this memo is to gather key information use for pricing related to namespace migration. This document is the initial in-take document that serves as a means of clarification and to set client expectations.
BackgroundFor clients with Cognos 8 or 10, moving off of the Series 7 namespace to another target namespace generally involves conversion in three areas: migrating users and groups from one namespace to another, converting security in existing models, and converting security in the Content Store.
The high level work breakdown structure is shown below.
The remainder of this document specifies questions that are relevant for pricing of a namespace migration effort.
Motio Namespace Migration Checklist Page 1 of 11
Environments to be convertedEnvironment type Environment must be convertedDevelopment Yes No
UAT Yes No
Production Yes No
Are there any other environments that need to be converted?
If yes, please specify
Motio Namespace Migration Checklist Page 2 of 11
NamespaceThis section requests information about the Source namespace, Target namespace, and mapping method to be used.
Source Manager Namespace – Access ManagerWhich architectural diagram best characterizes your current environment?
Current ArchitectureType I -- A single Access Manager namespace exists that supports multiple Cognos environments.
Type II -- Each environment has its own Access Manager Namespace.
Type III -- If neither of the above diagrams describes your environment, please attach a separate architecture diagram.
Motio Namespace Migration Checklist Page 3 of 11
Additional QuestionsUsers – How many users exist in the Access Manager namespace?
User Classes – Approximately how many user classes exist in the Access Manager namespace?
OS Signons – Are OS Signons used for single signon into Active Directory?
Yes
User classes in target environment.Have User Classes been created in the target environment?
Yes NoIf no, will FirstQuarter perform this as part of the migration? Yes
Memberships in target environmentHave memberships be created in the target environment?
Yes NoIf no, will FirstQuarter perform this as part of the migration? YES
Motio Namespace Migration Checklist Page 4 of 11
Target NamespacePlease indicate the architecture that will be in place following the migration.
Future ArchitectureType I -- A single Target namespace will exist that supports multiple Cognos environments.
Type II – Multiple target namespaces will exist that supports multiple Cognos environments.
Type III -- If neither of the above diagrams describes your environment, please attach a separate architecture diagram.
Motio Namespace Migration Checklist Page 5 of 11
Namespace Mapping MethodPlease indicate which mapping method you will use following the migration.
Direct Yes NoParallel Yes NoOther Yes No
Mapping Method DescriptionsDirect Mapping – In a direct mapping scenario the following applies:
1. Series 7 user classes are converted into roles in the Cognos namespace2. User memberships from the new, target namespace are mapped directly into the related
Cognos namespace groups.3. This approach provides the BI team with a high degree of control/autonomy that they have
been used to with Series7 Access Manager.
Parallel Mapping – In a parallel mapping scenario the following applies:1. Series 7 user classes are converted into groups in the target namespace2. For each group created in the target namespace, a corresponding group is created in the Cognos
namespace.3. Group-to-group mappings are created.4. User memberships are performed in target namespace.5. This approach typical provides the BI team with less control because the corporate LDAP team
usually controls access and memberships to the target namespace.
Motio Namespace Migration Checklist Page 6 of 11
Other -- If neither of the above diagrams describes your environment, please attach a separate diagram that describes the approach that you will use.