Types of MDM entity services
There are two different types of MDM entity services: Anonymous and Named.
Anonymous MDM entity services
Anonymous MDM entity services are MDM entity services that cannot be shared by other processes or multiple instances of a service.
- Usage
- These entity services can be used with the MDM Tree coach view,
the MDM Diagram coach view, and the Get MDM Entity integration service.
Anonymous MDM entity services are intended to be used for a finite time and then deleted.
One advantage of using anonymous entity services is that you can create a separate entity service for each user and run each process instance for a different user.
Note: After the anonymous MDM entity service is no longer required, you must delete the entity service. - Creating anonymous entity services
- To create an anonymous MDM entity Service, you use the Obtain
MDM Entity Service integration service. The value that is returned
from the Obtain MDM Entity Service integration service is a service
token.
The service token is used in the service variable for the MDM Tree coach view or MDM Diagram coach view.
- Data mappings
- The input mappings for the Obtain MDM Entity Service integration
service are name, connection,
and adaptorConfig.
With anonymous entity services, you specify an empty String for the name mapping. For example:
name(String): " ". - Output mapping
- The output mapping for the Obtain MDM Entity Service integration service is service.
- Implementation
- You use the Obtain MDM Entity Service integration service.
Named MDM entity services
Named MDM Entity Services are MDM entity services that are shared by multiple instances of the same process or human service instance. With named MDM entity services, the underlying resources are also shared.
- Usage
- These entity services can be used with the MDM Tree coach view,
the MDM Diagram coach view, and the Get MDM Entity integration service.
Named MDM entity services are designed to be shared. One advantage over anonymous MDM entity services, is that a process can reuse the already created service. This reuse avoids having to create and delete anonymous MDM entity services constantly.
Depending on how you create these named services and how long you want their services to be available, you might not want to delete them.
Named MDM entity services do not persist across a restart of the IBM® BPM Process Server.
Important: If you have multiple processes that are using a named service, then it is harder to determine when the service is safe to delete. Deleting a named MDM entity service might impact other users. For example, you have two or more users who run the same human service or process. If the human service or process deletes the MDM entity service, the MDM entity service is deleted for all of the users that are running that process or human service. Users might still need the MDM entity service for their interaction with the MDM Tree or MDM Diagram coach views. - Creating named entity services
- To create a named MDM entity Service, you use the Obtain MDM Entity
Service integration service. The value that is returned from the Obtain
MDM Entity Service integration service is a service token.
The service token is used in the service variable for the MDM Tree coach view or MDM Diagram coach view.
- Data mappings
- The input mappings for the Obtain MDM Entity Service integration
service are name, connection,
and adaptorConfig.
With named entity services, you specify a value the name mapping. For example:
name(String): "mdm_rel_tree" - Output mapping
- The output mapping for the Obtain MDM Entity Service integration service is service.
- Implementation
- You use the Obtain MDM Entity Service integration service.