In FIM Metaverse, you can configure objects with immutable anchor attributes and multiple types. Native SQL views can create multiple types of groups and members, and code-less FIM Sync Service. In the first line of code, use the WITH (nolock) keyword to avoid deadlocks within FIM’s metaverse. Ensure the “member” view outputs two types of rows, a group and a member.
Configuring object deletion rules
To configure object deletion rules in the FIM metaverse, you need to be a member of the MIISAdmins security group. Once you have the necessary permissions, open the Metaverse Designer. You’ll see a list of object types, along with their respective deletion rules, and their actions. Click on the appropriate configuration option to make any necessary changes. You can then click Save. Once the changes have been made, you can close the Metaverse Designer.
Object deletion rules in the FIM metaverse enable you to decide when objects should be deleted when they’re no longer linked to their connectors. By default, metaverse objects are automatically deleted if the last connector is removed from the server. The only exception is when a user removes their connector. This triggers the deprovisioning process. However, you can customize these settings as per your preferences.
Adding new types of objets
Adding new types of objets to the FIM metaverse is quite easy. After installing the FIM metaverse, run Import/Sync. If everything went well, you should see three objects in the Metaverse: an Administrator user, a Built-In Synchronization user, and an HR Import Sync Rule. You should provision these objects as Adds in FIM MA and see the HR objects populate with data from your HR data source.
If the new type of object is a MA with multiple inbound arrows, you can create a separate MA for it. Then, use the import attribute flow to add new attributes. You can also add additional types of objects to the metaverse using the project tool. The first step involves creating the object shell. Then, modify the attributes of the object using the corresponding configuration items.
Using accountname as a unique identifier in connector space
In a FIM metaverse connector, a group object should be identifiable by its account name. Using the account name as a unique identifier is easy, but you must be sure that this identifier is not already in use. For example, if you have an object in FIM called “group,” you need to create a new group object.
A CS table contains data that is not stored in a Metaverse table. CS tables hold a variety of information, including user names, email addresses, and other data. When you’re building a metaverse connector, you’ll need to define which columns contain the same data. The account name column is one example of a table. Using accountname as a unique identifier is another example.
In the connector space, you’ll need to create separate partitions for different kinds of data. The first partition contains MIM managed objects and attributes. The second partition contains information about a person’s identity. MIM MA updates the metaverse by comparing it with the data in different connected data sources and determining whether or not any changes should be exported. You can then join and export groups in this metaverse.
Using immutable anchor attributes
Anchor attributes are the keys to uniquely identifying an object in the FIM metaverse. These attributes must be configured on all management agents. When you change a metaverse attribute, FIM treats that change as a new object. For example, if you change the employeeID of an employee object, FIM will treat that deletion as an object deletion in another connector space. Similarly, if you change a metaverse attribute manager, it will be treated as a new object in the connected space and the metaverse.
Researchers have studied the impact of interactive services and games on the global economy. They found that people are spending $100 billion per year on video games and virtual reality. While virtual reality games make up less than 10% of this, they are growing in popularity. In other words, the profit motive of metaverse services will determine their functionality and accessibility. But the questions remain open. So, what is the point of using immutable anchor attributes if people are not going to use them?