Adding Interface Entity Maps

The Interface Entity Maps menu option maps the name of an entity in the SEC database to a specific type of interface - SH, REST, SOAP, etc.

An interface entity mapping makes an entity available on the related interface. For example, in the case of a REST interface, the data type seen within the URL of a REST request is mapped to the entity. The example uses of interface entity maps:

Sh Interface Entity Map - mapping a data entity to the Sh interface makes the entity available to the Policy Management server.

REST Interface Entity Map - mapping a data entity to the REST interface makes the entity available to the provisioning systems

To add an interface entity map:

1. 1. From the main menu, select UDR.
2. 2. Select Subscriber Entity Configuration.
3. 3. Select Interface Entity Map.
   The Interface Entity Map page appears. The list of existing interface entity maps is displayed.

   Note:

   To change the order of the records in a column (from descending to ascending or vice versa), click the header of that column.
4. Click Insert.
5. Enter an Interface Entity Name to map to a specific type of interface and entity. If needed, the same Interface Entity Name can be used for more than one Interface Name. See Interface Entity Map elements for more information on each field.
6. Select a type of interface from the Interface Name drop-down list.
7. Select an existing entity name to associate with this interface from the Entity Name pulldown list.
8. Perform one of the following:
   • Click OK to save the permissions and return to the Interface Entity Map page.
   • Click Apply to save the permissions and remain on the Insert page.
   • Click Cancel to return to the Interface Entity Map page without saving the changes.
   If OK or Apply is clicked and any of the following exist, an error message appears:

   • Any required field is empty; no value was entered or selected
   • The entry in any field is not valid (wrong data type or out of the valid range)
   • The interface entity name is not unique; it already exists in the interface entity map list