Module 17 Administration

Introduction to Informatica Cloud Administration

This section introduces the basics of administration in Informatica Cloud, covering user management, security configurations, and organizational hierarchy.

Understanding Security in Informatica Cloud

• Security in Informatica Cloud involves roles, user groups, and object-level permissions to secure data and objects within the organization.

• Roles define general tasks users can perform (e.g., admin role for user management), user groups specify objects and tasks a user can work with, and object-level permissions control access to individual objects.

• User roles are sets of privileges determining functionality and menu access; roles include Admin (full access), Designer (limited access), and Service Consumer (viewing and running tasks).

Managing User Groups

• User groups allow fine-grained control over tasks users can perform on objects within the organization.

• Configuring user groups involves creating a group, assigning permissions by object type (read, update, delete, execute), and assigning users to the group.

Object-Level Permissions

• Object-level permissions enable configuring specific permissions for individual objects like connections or task flows.

Actions Menu and Asset Permissions

This section demonstrates how to assign permissions at both the user level and user group level for assets within an organization.

Asset Permissions Assignment

• The Actions menu dropdown of an asset allows users to select permissions.

• The asset permissions window appears, enabling the assignment of permissions at the user level and user group level.

• Configuring security for the organization is essential before creating users.

User Configuration and Role Assignment

User creation process involves configuring user properties, details, and assigning roles within the organization.

User Creation Process

• When creating a new user, configure user properties like username, password, and log retry attempts.

• User details such as first name, last name, job title, phone number are included during user setup.

• Each user must be assigned a role within the organization.

Managing Users in Organization Hierarchy

Demonstrates viewing/editing existing users' details and adding new users within an organization's hierarchy.

Managing Users

• Access Informatica Intelligent Cloud Services as an administrator to view/edit existing users or add new ones.

• Navigate to the Users section from the navigation pane to manage users effectively.

• Assign necessary settings including user groups and roles for each user account.

Organization Hierarchy Setup

Explains the concept of an organization hierarchy with parent and sub organizations in Informatica Cloud Services.

Organization Hierarchy Structure

• An organization hierarchy comprises a parent organization with one or more sub organizations.

• Parent organizations need org hierarchy licenses to create/manage organizations within the hierarchy.

• Users require individual accounts for each org in the hierarchy; cross-org login requires specific accounts per org.

Suborganization Creation and Management

Details on creating suborganizations linked to parent organizations in Informatica Cloud Services.

Suborganization Creation

• Suborganizations inherit licenses from parent orgs but cannot act as parents themselves or join other hierarchies.

• Maximum supported suborganizations limit can be adjusted by contacting support for increased capacity.

• New suborgs require separate security configurations and user accounts for operational tasks.

Migrating Assets and Tasks in IICS

The transcript discusses the process of migrating assets and tasks within Informatica Intelligent Cloud Services (IICS), highlighting considerations such as security, connection migration, and asset naming conventions.

Migrating Task Flows and Connections

• When migrating task flows, all tasks within the flow along with their connections are migrated. However, schedule information is not transferred, necessitating reassignment post-migration.

• Connections are migrated without passwords for security reasons, including Salesforce connections and security tokens. Users must update and verify all connections in the target organization after migration.

• Migrated assets must have unique names to avoid conflicts with existing assets in the target organization. Versioning assets by assigning version numbers is recommended to prevent errors during migration.

Asset Migration Process

• Asset migration involves using the export and import feature of IICS. This process can be performed at the project or asset level.

• To export assets, navigate to the explore page of the data integration service, select the project or asset to be exported, specify details such as job name, and complete the export process.

• All associated components of an asset are migrated during export, including mappings and task connection details. Connection passwords are not migrated; they need updating before use in the target organization.

• To import exported assets into the destination organization, log into the target org's data integration service explore page, select the file exported from the source org, specify import job details, review connections and runtime environment settings before confirming import.

Conclusion

• The demo concludes by emphasizing how users can create and manage users, configure user groups within IICS for effective asset management.