3 Working with the Network Resource Management Web Service

About the WSDL File

Within ZIP file, the WSDL file is located in the ora_uim_webservices/wsdl directory. The WSDL file defines several operations. Each web service operation defines a request, a response, and the possible faults that can be thrown. For example, the WSDL file defines the following for the CreateEntity operation:

• createEntityRequest

• createEntityResponse

• createEntityFault

• inventoryFault

• validationFault

The request, response, and faults each define an XML structure that is defined in the supporting schema files. The following excerpts show how an XML structure defined in the WSDL correlates to the supporting schema files.

For example, the WSDL file defines and references the invnsrm namespace (bolded):

xmlns:invnsrm="http://xmlns.oracle.com/communications/inventory/webservice/nsrm"
.
.
.
targetNamespace
.
.
.
<xsd:import
namespace="http://xmlns.oracle.com/communications/inventory/webservice/nsrm" schemaLocation="./schemas/NSRMMessages.xsd"/>
.
.
.
<wsdl:message name="CreateEntityRequest">
    <wsdl:part name="CreateEntityRequest" element="invnsrm:createEntityRequest"> 
    </wsdl:part>
</wsdl:message>
 

This tells you that the createEntityRequest XML structure is defined in the schema file that defines the specified namespace as its target namespace. A search for the specified namespace reveals that NSRMMessages.xsd defines the referenced namespace as its target namespace.

After you determine which schema file defines the XML structure that the WSDL file references, you can navigate through the schema files to determine child XML structures and elements.

About the Schema Files

Several schema files support the NRM Web Service. These schemas are categorized as reference schemas, web service schemas, and business schemas.

createEntityRequest

You must specify the type of entity to create based on the entity types defined in the schema files. Each entity type defines different elements that pertain specifically to the entity type, which you use to define the entity you are creating. Table 3-1 lists the valid entity types and the schema files in which they are defined.

<nsrm:createEntityRequest>
    <nsrm:entity xsi:type="tn:TelephoneNumberType">
        <tn:specification>
            <spec:name>usTelephoneNumber</spec:name>
        </tn:specification>
        <tn:rangeFrom>9729630001</tn:rangeFrom>
        <tn:rangeTo>9729630020</tn:rangeTo>
        <tn:description>Owned Number</tn:description>
        <tn:property>
            <prop:name>tnCountryCode</prop:name>
            <prop:value>1</prop:value>
        </tn:property>
        <tn:property>
            <prop:name>winback</prop:name>
            <prop:value>false</prop:value>
        </tn:property>
        <tn:property>
           <prop:name>responsibleProvider</prop:name>
           <prop:value>AT&T</prop:value>
        </tn:property>
        <tn:property>
            <prop:name>tnType</prop:name>
            <prop:value>OWNED</prop:value>
        </tn:property>
    </nsrm:entity>
    <nsrm:inventoryGroup>
        <ig:specification>
            <spec:name>MobileServingArea</spec:name>
        </ig:specification>
        <ig:name>North Dallas</ig:name>
    </nsrm:inventoryGroup>
    <nsrm:parameter>
        <bi:name></bi:name>
        <bi:value></bi:value>
    </nsrm:parameter>
</nsrm:createEntityRequest>

createEntityResponse

createEntityResponse returns information about the created entities. The information returned in the response is dependent upon the entity types that were created, as specified in the request.

createEntityResponse returns an error message when:

• The request specifies a specification that does not exist in UIM

• The request specifies an inventory group that does not exist in UIM

• The call to the UIM API fails

findEntityRequest

You must specify search criteria to find the entities to retrieve. You have the choice of specifying search criteria one of two ways. With either choice, you must specify the type of entity to find based on the entity types defined in the schema files. Each entity type defines different elements that pertain specifically to the entity type, which you use as search criteria to find entities. Table 3-2 lists the valid entity types and the schema files in which they are defined.

The choices are:

• <entity>

  In this search option, you specify the entity type and use the entity-specific elements to specify search criteria.

  For each entity type, the <entity> structure varies. For example, TelephoneNumberType defines <rangeFrom> and <rangeTo>, but none of the other entity types define these elements.

  Even though the <entity> structure varies per entity type, the following elements are common across most entity types:

  • specification

    The search returns entities created from the specified specification.

  • id

    The search returns the entity with the specified id. (InventoryGroupType is only entity type with no id; the inventory group name is the id.)

  • name

    The search returns entities with the specified name.

  • description

    The search returns entities with the specified description.

  • property

    The search returns entities with the data specified by property, which is an unbounded structure that provides the ability to specify the following:

    • Name of a characteristic

    • Value of specified characteristic

      Note:

      Within each EntityType structure, the property element defines name, value, and action. However, action is not used; rather, the NRM Web Service operations always assume an operand of EQUALS.

• <criteria>

  In this search option, you specify the entity type and use the following search criteria:

  • specification

    The search returns entities created from the specified specification.

  • adminState

    The search returns entities in the specified administrative state, which is defined by the following enumeration values:

    <xs:enumeration value="END_OF_LIFE"/>
    <xs:enumeration value="INSTALLED"/>
    <xs:enumeration value="PENDING_INSTALL"/>
    <xs:enumeration value="PENDING_REMOVE"/>
    <xs:enumeration value="PENDING_UNAVAILABLE"/>
    <xs:enumeration value="PENDING_AVAILABLE"/>
    <xs:enumeration value="PLANNED"/>
    <xs:enumeration value="UNAVAILABLE"/>
    <xs:enumeration value="PENDING_DISCONNECT"/>
    <xs:enumeration value="DISCONNECTED"/>
     
    

  • assignmentState

    The search returns entities in the specified assignment state, which is defined by the following enumeration values:

    <xs:enumeration value="PENDING_ASSIGN"/>
    <xs:enumeration value="ASSIGNED"/>
    <xs:enumeration value="PENDING_UNASSIGN"/>
    <xs:enumeration value="UNASSIGNED"/>
    <xs:enumeration value="DISCONNECTED"/>
    <xs:enumeration value="PENDING_AVAILABLE"/>
    <xs:enumeration value="PENDING_UNAVAILABLE"/>
    <xs:enumeration value="PORTED"/>
    <xs:enumeration value="UNAVAILABLE"/>
    <xs:enumeration value="TRANSITIONAL"/>
     
    

  • inventoryGroup

    The search returns entities associated with the specified inventory group.

    If searching for telephone number entities, you can specify the inventoryGroup geographicLocation and the search returns telephone number entities associated with inventory groups that are associated with the specified place. If searching for entities other than telephone numbers, the inventoryGroup geographicLocation is not used.

  • geographicLocation

    The search returns inventory group entities associated with the specified place. If searching for entities other than inventory groups, geographicLocation is not used.

  • quantity

    The search returns the specified quantity of entities. For example, if the search finds 1,000 entities and the criteria specifies a quantity of 50, the first 50 entities found are returned.

  • reservation

    If you specify reservation information, FindEntity also reserves any found entities. See "ReserveEntity" for more information.

  • lock

    Row locking is used to optimize concurrent resource allocation for consumable entities.

    If you specify row-locking information, FindEntity does not release locked entities; you must manually release locked entities by calling the RowLockManager.releaseLock() method, or wait for the timer to release locked entities.

    If you specify row-locking information for entities that are not consumable (Geographic Location and Inventory Group), an error is thrown.

    See Optimizing Concurrent Resource Allocation in UIM Developer's Guide for more information about row locking, and see the Javadoc for information about the RowLockManager.releaseLock() method.

  • criteriaItem

    The search returns entities based on data specified by criteriaItem, which is an unbounded structure that provides the ability to specify the following:

    • Name of a criteria item as defined by the EntitySearchCriteria class, where Entity is the name of a specific entity such as TelephoneNumber, LogicalDevice, and so forth (see "Determining Criteria Item Names")

    • Value of specified criteria item

    • Enumerated operand with which to evaluate the specified criteria item and corresponding specified value:

      <xs:enumeration value="EQUALS" />
      <xs:enumeration value="NOT_EQUALS" />
      <xs:enumeration value="BEGINS_WITH" />
      <xs:enumeration value="ENDS_WITH" />
      <xs:enumeration value="CONTAINS" />
       
      

  • property

    The search returns entities with the data specified by property, which is an unbounded structure that provides the ability to specify the following:

    • Name of a characteristic

    • Value of specified characteristic

    • Enumerated operand with which to evaluate the specified characteristic and corresponding specified value:

      <xs:enumeration value="EQUALS" />
      <xs:enumeration value="NOT_EQUALS" />
      <xs:enumeration value="BEGINS_WITH" />
      <xs:enumeration value="ENDS_WITH" />
      <xs:enumeration value="CONTAINS" />
       
      

<nsrm: findEntityRequest >
    <ent:entity xsi:type="tn:TelephoneNumberType">
        <tn:specification>
            <spec:name>usTelephoneNumber</spec:name>
        </tn:specification>
        <tn:id>9729630012</tn:id>
        <tn:name/>
        <tn:rangeFrom/>
        <tn:rangeTo/>
        <tn:description/>
        <tn:state/>
        <tn:startDate/>
        <tn:endDate/>
        <tn:property/>
            <prop:name/>
            <prop:value/>
        </tn:property>
    </ent:entity>
</nsrm: findEntityRequest >
 

<nsrm:findEntityRequest>
    <nsrm:criteria>
        <ent:entityType xsi:type="tn:TelephoneNumberType">
            <!-- tn-specific elements are not shown -->
        </ent:entityType>
        <ent:specification>
            <spec:name>usTelephoneNumber</spec:name>
        </ent:specification>
        <ent:adminState/>
        <ent:assignmentState/>
        <ent:inventoryGroup/>
            <ig:geographicPlace/>
        </ent:inventoryGroup>
        <ent:geographicPlace/>
        <ent:quantity/>
            <ent:reservation/>
        <ent:lock>
            <ent:lockAllOrNone>true</ent:lockAllOrNone>
            <ent:quantity>4</ent:quantity>
        </ent:lock>
        <ent:criteriaItem/>
        <ent:property/>
    </nsrm:criteria>        
</nsrm:findEntityRequest>

findEntityResponse

findEntityResponse returns the found entities, based on the search criteria specified in the request. The information returned in the response is dependent upon the entity types that were searched for and subsequently found.

If you specified reservation information in the request, reservation information is also returned.

findEntityResponse returns an error message when:

• The request specifies a lock policy for the non-consumable entities of Geographic Location or Group Inventory

• The request specifies a lock policy that specifies the number of resources to lock, and there are not enough resources available to lock

• The call to the UIM API fails

updateEntityRequest

You must specify the type of entity to update based on the entity types defined in the schema files. Each entity type defines different elements that pertain specifically to the entity type, which you use to specify what to update. Table 3-3 lists the valid entity types and the schema files in which they are defined.

You must specify the same entity type twice: First, within the <entityDetails> element to specify the data to update; and second, within the <entitySearchCriteria> element to find the entities to update.

<entitySearchCriteria> defines the following search criteria:

• specification

  The search returns entities created from the specified specification.

• adminState

  The search returns entities in the specified administrative state, which is defined by the following enumeration values:

  <xs:enumeration value="END_OF_LIFE"/>
  <xs:enumeration value="INSTALLED"/>
  <xs:enumeration value="PENDING_INSTALL"/>
  <xs:enumeration value="PENDING_REMOVE"/>
  <xs:enumeration value="PENDING_UNAVAILABLE"/>
  <xs:enumeration value="PENDING_AVAILABLE"/>
  <xs:enumeration value="PLANNED"/>
  <xs:enumeration value="UNAVAILABLE"/>
  <xs:enumeration value="PENDING_DISCONNECT"/>
  <xs:enumeration value="DISCONNECTED"/>
   
  

• assignmentState

  The search returns entities in the specified assignment state, which is defined by the following enumeration values:

  <xs:enumeration value="PENDING_ASSIGN"/>
  <xs:enumeration value="ASSIGNED"/>
  <xs:enumeration value="PENDING_UNASSIGN"/>
  <xs:enumeration value="UNASSIGNED"/>
  <xs:enumeration value="DISCONNECTED"/>
  <xs:enumeration value="PENDING_AVAILABLE"/>
  <xs:enumeration value="PENDING_UNAVAILABLE"/>
  <xs:enumeration value="PORTED"/>
  <xs:enumeration value="UNAVAILABLE"/>
  <xs:enumeration value="TRANSITIONAL"/>
   
  

• inventoryGroup

  The search returns entities associated with the specified inventory group.

  If searching for telephone number entities, you can specify the inventoryGroup geographicLocation and the search returns telephone number entities associated with inventory groups that are associated with the specified place. If searching for entities other than telephone numbers, the inventoryGroup geographicLocation is not used.

• geographicLocation

  The search returns inventory group entities associated with the specified place. If searching for entities other than inventory groups, geographicLocation is not used.

• quantity

  The search returns the specified quantity of entities. For example, if the search finds 1,000 entities and the criteria specifies a quantity of 50, the first 50 entities found are returned.

• reservation

  If you specify reservation information, UpdateEntity ignores it; FindEntity is the only operation that uses the reservation element. See "FindEntity" for more information.

• lock

  Row locking is used to optimize concurrent resource allocation for consumable entities.

  If you specify row-locking information, UpdateEntity releases locked entities; you do not need to manually release locked entities by calling the RowLockManager.releaseLock() method, or wait for the timer to release locked entities.

  If you specify row-locking information for entities that are not consumable (Geographic Location and Inventory Group), an error is thrown.

  See Optimizing Concurrent Resource Allocation in UIM Developer's Guide for more information about row locking.

• criteriaItem

  The search returns entities based on data specified by criteriaItem, which is an unbounded structure that provides the ability to specify the following:

  • Name of a criteria item as defined by the EntitySearchCriteria class, where Entity is the name of a specific entity such as TelephoneNumber, LogicalDevice, and so forth (see "Determining Criteria Item Names")

  • Value of specified criteria item

  • Enumerated operand with which to evaluate the specified criteria item and corresponding specified value:

    <xs:enumeration value="EQUALS" />
    <xs:enumeration value="NOT_EQUALS" />
    <xs:enumeration value="BEGINS_WITH" />
    <xs:enumeration value="ENDS_WITH" />
    <xs:enumeration value="CONTAINS" />
     
    

• property

  The search returns entities with the data specified by property, which is an unbounded structure that provides the ability to specify the following:

  • Name of characteristic

  • Value of specified characteristic

  • Enumerated operand with which to evaluate the specified characteristic and corresponding specified value:

    <xs:enumeration value="EQUALS" />
    <xs:enumeration value="NOT_EQUALS" />
    <xs:enumeration value="BEGINS_WITH" />
    <xs:enumeration value="ENDS_WITH" />
    <xs:enumeration value="CONTAINS" />
     
    

<nsrm:updateEntityRequest>
    <nsrm:entityDetails xsi:type="tn:TelephoneNumberType">
        <tn:description>Update for Testing</tn:description>
    </nsrm:entityDetails>
    <ent:entitySearchCriteria>
        <ent:entityType xsi:type="tn:TelephoneNumberType" />
        <ent:specification>
            <spec:name>usTelephoneNumber</spec:name>
        </ent:specification>
    </ent:entitySearchCriteria>
    <nsrm:parameter>
        <bi:name></bi:name>
        <bi:value></bi:value>
    </nsrm:parameter>
</nsrm:updateEntityRequest>

<nsrm:updateEntityRequest>
    <nsrm:entityDetails xsi:type="act:ActivityType">
        <act:action>complete</act:action>            
    </nsrm:entityDetails>
    <nsrm:entitySearchCriteria xsi:type="act:ActivitySearchCriteriaType">
        <ent:entityType xsi:type="act:ActivityType" >
            <act:name>Acquire Property Location</act:name>
            <act:businessInteractionId>1</act:businessInteractionId>
        </ent:entityType>
    </nsrm:entitySearchCriteria>
    <nsrm:parameter>
        <bus:name></bus:name>
        <bus:value></bus:value>
    </nsrm:parameter>
</nsrm:updateEntityRequest>

updateEntityResponse

updateEntityResponse returns information about the updated entities. The information returned in the response is dependent upon the entity types that were updated, as specified in the request.

updateEntityResponse returns an error message when:

• The request specifies two different entity types in the request entity type and the criteria entity type

• The request specifies a lock policy that specifies the number of resources to lock, and there are not enough resources available to lock

• The call to the UIM API fails

deleteEntityRequest

You must specify search criteria to search for entities to delete. You have the choice of specifying search criteria one of two ways. With either choice, you must specify the type of entity to find based on the entity types defined in the schema files. Each entity type defines different elements that pertain specifically to the entity type, which you use as search criteria to find entities to delete. Table 3-4 lists the valid entity types and the schema files in which they are defined.

The choices are:

• <entity>

  In this search option, you specify the entity type and use the entity-specific elements to specify search criteria.

  For each entity type, the <entity> structure varies. For example, TelephoneNumberType defines <rangeFrom> and <rangeTo>, but none of the other entity types define these elements.

  Even though the <entity> structure varies per entity type, the following elements are common across most entity types:

  • specification

    The search returns entities created from the specified specification.

  • id

    The search returns the entity with the specified id. (InventoryGroupType is only entity type with no id; the inventory group name is the id.)

  • name

    The search returns entities with the specified name.

  • description

    The search returns entities with the specified description.

  • property

    The search returns entities with the data specified by property, which is an unbounded structure that provides the ability to specify the following:

    • Name of a characteristic

    • Value of specified characteristic

      Note:

      Within each EntityType structure, the property element defines name, value, and action. However, action is not used; rather, the NRM Web Service operations always assume an operand of EQUALS.

• <criteria>

  In this search option, you specify the entity type and use the following search criteria:

  • specification

    The search returns entities created from the specified specification.

  • adminState

    The search returns entities in the specified administrative state, which is defined by the following enumeration values:

    <xs:enumeration value="END_OF_LIFE"/>
    <xs:enumeration value="INSTALLED"/>
    <xs:enumeration value="PENDING_INSTALL"/>
    <xs:enumeration value="PENDING_REMOVE"/>
    <xs:enumeration value="PENDING_UNAVAILABLE"/>
    <xs:enumeration value="PENDING_AVAILABLE"/>
    <xs:enumeration value="PLANNED"/>
    <xs:enumeration value="UNAVAILABLE"/>
    <xs:enumeration value="PENDING_DISCONNECT"/>
    <xs:enumeration value="DISCONNECTED"/>
     
    

  • assignmentState

    The search returns entities in the specified assignment state, which is defined by the following enumeration values:

    <xs:enumeration value="PENDING_ASSIGN"/>
    <xs:enumeration value="ASSIGNED"/>
    <xs:enumeration value="PENDING_UNASSIGN"/>
    <xs:enumeration value="UNASSIGNED"/>
    <xs:enumeration value="DISCONNECTED"/>
    <xs:enumeration value="PENDING_AVAILABLE"/>
    <xs:enumeration value="PENDING_UNAVAILABLE"/>
    <xs:enumeration value="PORTED"/>
    <xs:enumeration value="UNAVAILABLE"/>
    <xs:enumeration value="TRANSITIONAL"/>
     
    

  • inventoryGroup

    The search returns entities associated with the specified inventory group.

    If searching for telephone number entities, you can specify the inventoryGroup geographicLocation and the search returns telephone number entities associated with inventory groups that are associated with the specified place. If searching for entities other than telephone numbers, the inventoryGroup geographicLocation is not used.

  • geographicLocation

    The search returns inventory group entities associated with the specified place. If searching for entities other than inventory groups, geographicLocation is not used.

  • quantity

    The search returns the specified quantity of entities. For example, if the search finds 1,000 entities and the criteria specifies a quantity of 50, the first 50 entities found are returned.

  • reservation

    If you specify reservation information, DeleteEntity ignores it; FindEntity is the only operation that uses the reservation element. See "FindEntity" for more information.

  • lock

    Row locking is used to optimize concurrent resource allocation for consumable entities; however, DeleteEntity does not use row locking.

    If you specify row-locking information, DeleteEntity ignores it.

  • criteriaItem

    The search returns entities based on data specified by criteriaItem, which is an unbounded structure that provides the ability to specify the following:

    • Name of a criteria item as defined by the EntitySearchCriteria class, where Entity is the name of a specific entity such as TelephoneNumber, LogicalDevice, and so forth (see "Determining Criteria Item Names")

    • Value of specified criteria item

    • Enumerated operand with which to evaluate the specified criteria item and corresponding specified value:

      <xs:enumeration value="EQUALS" />
      <xs:enumeration value="NOT_EQUALS" />
      <xs:enumeration value="BEGINS_WITH" />
      <xs:enumeration value="ENDS_WITH" />
      <xs:enumeration value="CONTAINS" />
       
      

  • property

    The search returns entities with the data specified by property, which is an unbounded structure that provides the ability to specify the following:

    • Name of a characteristic

    • Value of specified characteristic

    • Enumerated operand with which to evaluate the specified characteristic and corresponding specified value:

      <xs:enumeration value="EQUALS" />
      <xs:enumeration value="NOT_EQUALS" />
      <xs:enumeration value="BEGINS_WITH" />
      <xs:enumeration value="ENDS_WITH" />
      <xs:enumeration value="CONTAINS" />
       
      

<nsrm:deleteEntityRequest>
    <ent:entity xsi:type="tn:TelephoneNumberType">
        <tn:specification>
            <spec:name>usTelephoneNumber</spec:name>
        </tn:specification>
        <tn:id>9729630014</tn:id>
    </ent:entity>
    <nsrm:parameter>
        <bi:name></bi:name>
        <bi:value></bi:value>
    </nsrm:parameter>
</nsrm:deleteEntityRequest>
 

<nsrm:deleteEntityRequest>
    <ent:criteria>
        <ent:entityType xsi:type="tn:TelephoneNumberType"/>
        <ent:specification>
            <spec:name>usTelephoneNumber</spec:name>
        </ent:specification>
        <ent:adminState>INSTALLED</ent:adminState>
        <ent:assignmentState>UNASSIGNED</ent:assignmentState>
    </ent:criteria>
    <nsrm:parameter>
        <bi:name></bi:name>
        <bi:value></bi:value>
    </nsrm:parameter>
</nsrm:deleteEntityRequest>

deleteEntityResponse

deleteEntityResponse returns information about the deleted entities. The information returned in the response is dependent upon the entity types that were deleted, as specified in the request.

deleteEntityResponse returns an error message when:

• The call to the UIM API fails

reserveEntityRequest

The request structure defines the ResourceReservationType entity type; you do not specify the entity type for the reservation.

Within the reservation-specific elements, you specify one or both of the following:

• An existing reservation number

• Reservation information with which to create a reservation, which at a minimum must include:

  • reservedFor

  • reservedForType

  • reservationType

If you specify an existing reservation number, the operation attempts to find the reservation based on the specified reservation number. If the reservation is found, additional resources are added to it. If the reservation is not found, an error is thrown.

If you specify reservation information with which to create a reservation, the operation generates a reservation number and creates a reservation using the specified information.

If you specify both a reservation number and reservation information with which to create a reservation, the operation attempts to find the reservation based on the specified reservation number. If the reservation is found, additional resources are added to it, but the reservation is not updated with the specified reservation information. If the reservation is not found, the operation creates a reservation using the specified reservation number and reservation information.

If you specify neither a reservation number nor reservation information, an error is thrown.

<nsrm:reserveEntityRequest>
    <nsrm:reservation>
        <config:state/>
        <config:reservationNumber/>
        <config:reservationType>SHORTTERM</config:reservationType>
        <config:expiry/>
        <config:reservedForType>ORDER</config:reservedForType>
        <config:reservedFor>Customer XYZ</config:reservedFor>
        <config:reason/>
    </nsrm:reservation>
    <nsrm:entityType xsi:type="ld:LogicalDeviceType"/>
    <nsrm:resources>
        <ent:entity xsi:type="ld:LogicalDeviceType">
            <ld:specification>
                <spec:name>SIMCard</spec:name>
            </ld:specification>
            <ld:id>3101500000000009901</ld:id>
        </ent:entity>
        <ent:entity xsi:type="ld:LogicalDeviceType">
            <ld:specification>
                <spec:name>SIMCard</spec:name>
            </ld:specification>
            <ld:id>3101500000000009902</ld:id>
        </ent:entity>
    </nsrm:resources>
    <nsrm:parameter>
        <bi:name></bi:name>
        <bi:value></bi:value>
    </nsrm:parameter>
</nsrm:reserveEntityRequest>

reserveEntityResponse

reserveEntityResponse returns information about the reservation and the reserved resource entities. The resource entity information returned in the response is dependent upon the resource entity types that were reserved, as specified in the request.

reserveEntityResponse returns an error message when:

• The request specifies a reservation that does not exist

• The request specifies no reservation number and no reservation information with which to create a reservation

• The request specifies a resource that does not exist

• The call to the UIM API fails

unreserveEntityRequest

The request structure defines the ResourceReservationType entity type; you do not specify the entity type.

Within the reservation-specific elements, you specify an existing reservation number. If the reservation is not found, an error is thrown.

<nsrm:unreserveEntityRequest>
    <nsrm:reservation>
        <config:reservationNumber>12345678</config:reservationNumber>
    </nsrm:reservation>
    <nsrm:resourceCriteria>
        <ent:entityType xsi:type="tn:TelephoneNumberType"/>
        <ent:specification>
            <spec:name>BATTNSpec</spec:name>
        </ent:specification>
        <ent:criteriaItem>
            <ent:name>rangeFrom</ent:name>
            <ent:value xsi:type="xs:string">8588880081</ent:value>
            <ent:operator>EQUALS</ent:operator>
        </ent:criteriaItem>
        <ent:criteriaItem>
            <ent:name>rangeTo</ent:name>
            <ent:value xsi:type="xs:string">8588880083</ent:value>
            <ent:operator>EQUALS</ent:operator>
        </ent:criteriaItem>
    </nsrm:resourceCriteria>
</nsrm:unreserveEntityRequest>

<nsrm:unreserveEntityRequest>
     <nsrm:reservation>
        <config:reservationNumber>123456789</config:reservationNumber>
    </nsrm:reservation>
    <nsrm:entityType xsi:type="tn:TelephoneNumberType"/>
    <nsrm:resources>
        <ent:entity xsi:type="tn:TelephoneNumberType">
            <tn:specification>
                <spec:name>usTelephoneNumber</spec:name>
            </tn:specification>
            <tn:id>9729630012</tn:id>
        </ent:entity>
    </nsrm:resources>
    <nsrm:parameter>
        <bi:name></bi:name>
        <bi:value></bi:value>
    </nsrm:parameter>
</nsrm:unreserveEntityRequest>

unreserveEntityResponse

unreserveEntityResponse returns information about the reservation and the unreserved resources (entities). The information returned in the response is dependent upon the resource entity types that were unreserved.

unreserveEntityResponse returns an error message when:

• The specified reservation number is not found

• The request specifies search criteria that retrieves resources not related to the specified reservation number

• The call to the UIM API fails

updateReservationRequest

The request structure defines the ResourceReservationType entity type; you do not specify the entity type.

Within the reservation-specific elements, you specify an existing reservation number and for whom the reservation is reserved, as well as any reservation information to update. If the reservation is not found, an error is thrown.

<nsrm:updateReservationRequest>
    <nsrm:reservation>
        <config:reservationNumber>12345678</config:reservationNumber>
        <config:reservationType>LONGTERM</config:reservationType>
        <config:expiry>2018-12-31T00:00:00.000-06:00</config:expiry>
        <config:reservedForType>CSR</config:reservedForType>
        <config:reservedFor>Clark Kent</config:reservedFor>
        <config:reason>Testing</config:reason>
    </nsrm:reservation>
    <nsrm:parameter>
        <bi:name></bi:name>
        <bi:value></bi:value>
    </nsrm:parameter>
</nsrm:updateReservationRequest>

updateReservationResponse

updateReservationResponse returns information about the updated reservation.

updateReservationResponse returns an error message when:

• The specified reservation number is not found

• The call to the UIM API fails

associateEntityRequest

You must specify an association type of ASSOCIATE or PAIR, which are enumeration values defined in the entity.xsd file.

An association of type ASSOCIATE indicates a one-to-many association between a single specified source entity and multiple specified target entities. An association type of PAIR indicates a one-to-one association between a source entity and a target entity; in this type of association, multiple source entities and multiple target entities can be specified, but the number of each specified must be the same.

You must specify search criteria to find existing source entities to associate; and you must specify search criteria to find existing target entities to associate. You have the choice of specifying search criteria one of two ways. With either choice, you must specify the type of source/target entity to find based on the entity types defined in the schema files. Each entity type defines different elements that pertain specifically to the entity type, which you use as search criteria to find entities. Table 3-7 lists the valid entity types and the schema files in which they are defined.

The choices are:

• <entity>

  In this search option, you specify the entity type and use the entity-specific elements to specify search criteria.

  For each entity type, the <entity> structure varies. For example, TelephoneNumberType defines <rangeFrom> and <rangeTo>, but none of the other entity types define these elements.

  Even though the <entity> structure varies per entity type, the following elements are common across most entity types:

  • specification

    The search returns entities created from the specified specification.

  • id

    The search returns the entity with the specified id. (InventoryGroupType is only entity type with no id; the inventory group name is the id.)

  • name

    The search returns entities with the specified name.

  • description

    The search returns entities with the specified description.

  • property

    The search returns entities with the data specified by property, which is an unbounded structure that provides the ability to specify the following:

    • Name of a characteristic

    • Value of specified characteristic

      Note:

      Within each EntityType structure, the property element defines name, value, and action. However, action is not used; rather, the NRM Web Service operations always assume an operand of EQUALS.

• <criteria>

  In this search option, you specify the entity type and use the following search criteria:

  • specification

    The search returns entities created from the specified specification.

  • adminState

    The search returns entities in the specified administrative state, which is defined by the following enumeration values:

    <xs:enumeration value="END_OF_LIFE"/>
    <xs:enumeration value="INSTALLED"/>
    <xs:enumeration value="PENDING_INSTALL"/>
    <xs:enumeration value="PENDING_REMOVE"/>
    <xs:enumeration value="PENDING_UNAVAILABLE"/>
    <xs:enumeration value="PENDING_AVAILABLE"/>
    <xs:enumeration value="PLANNED"/>
    <xs:enumeration value="UNAVAILABLE"/>
    <xs:enumeration value="PENDING_DISCONNECT"/>
    <xs:enumeration value="DISCONNECTED"/>
     
    

  • assignmentState

    The search returns entities in the specified assignment state, which is defined by the following enumeration values:

    <xs:enumeration value="PENDING_ASSIGN"/>
    <xs:enumeration value="ASSIGNED"/>
    <xs:enumeration value="PENDING_UNASSIGN"/>
    <xs:enumeration value="UNASSIGNED"/>
    <xs:enumeration value="DISCONNECTED"/>
    <xs:enumeration value="PENDING_AVAILABLE"/>
    <xs:enumeration value="PENDING_UNAVAILABLE"/>
    <xs:enumeration value="PORTED"/>
    <xs:enumeration value="UNAVAILABLE"/>
    <xs:enumeration value="TRANSITIONAL"/>
     
    

  • inventoryGroup

    The search returns entities associated with the specified inventory group.

    If searching for telephone number entities, you can specify the inventoryGroup geographicLocation and the search returns telephone number entities associated with inventory groups that are associated with the specified place. If searching for entities other than telephone numbers, the inventoryGroup geographicLocation is not used.

  • geographicLocation

    The search returns inventory group entities associated with the specified place. If searching for entities other than inventory groups, geographicLocation is not used.

  • quantity

    The search returns the specified quantity of entities. For example, if the search finds 1,000 entities and the criteria specifies a quantity of 50, the first 50 entities found are returned.

  • reservation

    If you specify reservation information, AssociateEntity ignores it; FindEntity is the only operation that uses the reservation element. See "FindEntity" for more information.

  • lock

    Row locking is used to optimize concurrent resource allocation for consumable entities.

    If you specify row-locking information, AssociateEntity releases locked entities; you do not need to manually release locked entities by calling the RowLockManager.releaseLock() method, or wait for the timer to release locked entities.

    If you specify row-locking information for entities that are not consumable (Geographic Location and Inventory Group), an error is thrown.

    See Optimizing Concurrent Resource Allocation in UIM Developer's Guide for more information about row locking.

  • criteriaItem

    The search returns entities based on data specified by criteriaItem, which is an unbounded structure that provides the ability to specify the following:

    • Name of a criteria item as defined by the EntitySearchCriteria class, where Entity is the name of a specific entity such as TelephoneNumber, LogicalDevice, and so forth (see "Determining Criteria Item Names")

    • Value of specified criteria item

    • Enumerated operand with which to evaluate the specified criteria item and corresponding specified value:

      <xs:enumeration value="EQUALS" />
      <xs:enumeration value="NOT_EQUALS" />
      <xs:enumeration value="BEGINS_WITH" />
      <xs:enumeration value="ENDS_WITH" />
      <xs:enumeration value="CONTAINS" />
       
      

  • property

    The search returns entities with the data specified by property, which is an unbounded structure that provides the ability to specify the following:

    • Name of a characteristic

    • Value of specified characteristic

    • Enumerated operand with which to evaluate the specified characteristic and corresponding specified value:

      <xs:enumeration value="EQUALS" />
      <xs:enumeration value="NOT_EQUALS" />
      <xs:enumeration value="BEGINS_WITH" />
      <xs:enumeration value="ENDS_WITH" />
      <xs:enumeration value="CONTAINS" />
       
      

<nsrm:associateEntityRequest>
    <nsrm:associationType>ASSOCIATE</nsrm:associationType>
    <nsrm:sourceEntities>
        <nsrm:entityType xsi:type="ig:InventoryGroupType" />
        <ent:criteria>
            <ent:entityType xsi:type="ig:InventoryGroupType" />
            <ent:specification>
                <spec:name>MobileServingArea</spec:name>
            </ent:specification>
        </ent:criteria>
    </nsrm:sourceEntities>
    <nsrm:targetEntities>
        <nsrm:entityType xsi:type="ld:LogicalDeviceType" />
        <ent:criteria>
            <ent:entityType xsi:type="ld:LogicalDeviceType" />
            <ent:specification>
                <spec:name>SIMCard</spec:name>
            </ent:specification>
            <ent:adminState>INSTALLED</ent:adminState>
            <ent:assignmentState>UNASSIGNED</ent:assignmentState>
        </ent:criteria>
    </nsrm:targetEntities>
</nsrm:associateEntityRequest>

associateEntityResponse

associateEntityResponse returns information about the associated entities. The information returned in the response is dependent upon the entity types that were associated, as specified in the request.

associateEntityResponse returns an error message when:

• The request specifies search criteria that results in no entities found to associate

• The request specifies an association type of PAIR and the number of sources and targets found is the not the same

• The call to the UIM API fails

disassociateEntityRequest

You must specify an association type of ASSOCIATE or PAIR, which are enumeration values defined in the entity.xsd file.

An association of type ASSOCIATE indicates a one-to-many association between a single specified source entity and multiple specified target entities. An association type of PAIR indicates a one-to-one association between a source entity and a target entity.

You must specify search criteria to find existing source entities to disassociate; and you must specify search criteria to find existing target entities to disassociate. You have the choice of specifying search criteria one of two ways. With either choice, you must specify the type of source/target entity to find based on the entity types defined in the schema files. Each entity type defines different elements that pertain specifically to the entity type, which you use as search criteria to find entities. Table 3-8 lists the valid entity types and the schema files in which they are defined.

The choices are:

• <entity>

  In this search option, you specify the entity type and use the entity-specific elements to specify search criteria.

  For each entity type, the <entity> structure varies. For example, TelephoneNumberType defines <rangeFrom> and <rangeTo>, but none of the other entity types define these elements.

  Even though the <entity> structure varies per entity type, the following elements are common across most entity types:

  • specification

    The search returns entities created from the specified specification.

  • id

    The search returns the entity with the specified id. (InventoryGroupType is only entity type with no id; the inventory group name is the id.)

  • name

    The search returns entities with the specified name.

  • description

    The search returns entities with the specified description.

  • property

    The search returns entities with the data specified by property, which is an unbounded structure that provides the ability to specify the following:

    • Name of a characteristic

    • Value of specified characteristic

      Note:

      Within each EntityType structure, the property element defines name, value, and action. However, action is not used; rather, the NRM Web Service operations always assume an operand of EQUALS.

• <criteria>

  In this search option, you specify the entity type and use the following search criteria:

  • specification

    The search returns entities created from the specified specification.

  • adminState

    The search returns entities in the specified administrative state, which is defined by the following enumeration values:

    <xs:enumeration value="END_OF_LIFE"/>
    <xs:enumeration value="INSTALLED"/>
    <xs:enumeration value="PENDING_INSTALL"/>
    <xs:enumeration value="PENDING_REMOVE"/>
    <xs:enumeration value="PENDING_UNAVAILABLE"/>
    <xs:enumeration value="PENDING_AVAILABLE"/>
    <xs:enumeration value="PLANNED"/>
    <xs:enumeration value="UNAVAILABLE"/>
    <xs:enumeration value="PENDING_DISCONNECT"/>
    <xs:enumeration value="DISCONNECTED"/>
     
    

  • assignmentState

    The search returns entities in the specified assignment state, which is defined by the following enumeration values:

    <xs:enumeration value="PENDING_ASSIGN"/>
    <xs:enumeration value="ASSIGNED"/>
    <xs:enumeration value="PENDING_UNASSIGN"/>
    <xs:enumeration value="UNASSIGNED"/>
    <xs:enumeration value="DISCONNECTED"/>
    <xs:enumeration value="PENDING_AVAILABLE"/>
    <xs:enumeration value="PENDING_UNAVAILABLE"/>
    <xs:enumeration value="PORTED"/>
    <xs:enumeration value="UNAVAILABLE"/>
    <xs:enumeration value="TRANSITIONAL"/>
     
    

  • inventoryGroup

    The search returns entities associated with the specified inventory group.

    If searching for telephone number entities, you can specify the inventoryGroup geographicLocation and the search returns telephone number entities associated with inventory groups that are associated with the specified place. If searching for entities other than telephone numbers, the inventoryGroup geographicLocation is not used.

  • geographicLocation

    The search returns inventory group entities associated with the specified place. If searching for entities other than inventory groups, geographicLocation is not used.

  • quantity

    The search returns the specified quantity of entities. For example, if the search finds 1,000 entities and the criteria specifies a quantity of 50, the first 50 entities found are returned.

  • reservation

    If you specify reservation information, DisassociateEntity ignores it; FindEntity is the only operation that uses the reservation element. See "FindEntity" for more information.

  • lock

    Row locking is used to optimize concurrent resource allocation for consumable entities; however, DisassociateEntity does not use row locking.

    If you specify row-locking information, DisassociateEntity ignores it.

  • criteriaItem

    The search returns entities based on data specified by criteriaItem, which is an unbounded structure that provides the ability to specify the following:

    • Name of a criteria item as defined by the EntitySearchCriteria class, where Entity is the name of a specific entity such as TelephoneNumber, LogicalDevice, and so forth (see "Determining Criteria Item Names")

    • Value of specified criteria item

    • Enumerated operand with which to evaluate the specified criteria item and corresponding specified value:

      <xs:enumeration value="EQUALS" />
      <xs:enumeration value="NOT_EQUALS" />
      <xs:enumeration value="BEGINS_WITH" />
      <xs:enumeration value="ENDS_WITH" />
      <xs:enumeration value="CONTAINS" />
       
      

  • property

    The search returns entities with the data specified by property, which is an unbounded structure that provides the ability to specify the following:

    • Name of a characteristic

    • Value of specified characteristic

    • Enumerated operand with which to evaluate the specified characteristic and corresponding specified value:

      <xs:enumeration value="EQUALS" />
      <xs:enumeration value="NOT_EQUALS" />
      <xs:enumeration value="BEGINS_WITH" />
      <xs:enumeration value="ENDS_WITH" />
      <xs:enumeration value="CONTAINS" />
       
      

<nsrm:disassociateEntityRequest>
    <nsrm:sourceEntities>
        <nsrm:entityType xsi:type="ig:InventoryGroupType" />
        <ent:criteria>
            <ent:entityType xsi:type="ig:InventoryGroupType" />
            <ent:specification>
                <spec:name>MobileServingArea</spec:name>
            </ent:specification>
        </ent:criteria>
    </nsrm:sourceEntities>
    <nsrm:targetEntities>
        <nsrm:entityType xsi:type="ld:LogicalDeviceType" />
        <ent:criteria>
            <ent:entityType xsi:type="ld:LogicalDeviceType" />
            <ent:specification>
                <spec:name>SIMCard</spec:name>
            </ent:specification>
            <ent:adminState>INSTALLED</ent:adminState>
            <ent:assignmentState>UNASSIGNED</ent:assignmentState>
        </ent:criteria>
    </nsrm:targetEntities>
</nsrm:disassociateEntityRequest>

disassociateEntityResponse

disassociateEntityResponse returns information about the disassociated entities. The information returned in the response is dependent upon the entity types that were disassociated, as specified in the request.

disassociateEntityResponse returns an error message when:

• The call to the UIM API fails

importEntityRequest

You specify a SOAP attachment that is a spreadsheet containing the entities for import. The spreadsheet must be a specific format: see "Spreadsheet Format".

For information about SOAP attachments, see the SoapUI website at:

http://www.soapui.org/SOAP-and-WSDL/adding-headers-and-attachments.html#2

<soapEnv:Envelope xmls:soapenv="http://schemas.xmlsoap.org/soap/envelope/".......>
    <soapEnv:Header/>
    <soapEnv:Body>
        <nsrm:importEntityRequest>
            <octet/>
        </nsrm:importEntityRequest>
    <soapEnv:Body/>
</soapEnv:Envelope/>

#Use import properties to customize column names for excel of ImportEntity
import.rowNumber=rowNumber
import.action=action
import.entityType=entityType
import.id=id
import.rangeFromID=rangeFromID
import.rangeToID=rangeToID
import.quantity=quantity
import.name=name
import.rangeFromName=rangeFromName
import.rangeToName=rangeToName
import.specification=specification
import.description=description
import.attribute=attribute
import.characteristic=characteristic
import.relatedRow=relatedRow

importEntityResponse

importEntityResponse returns information about the imported entities. The information returned in the response is dependent upon the entity types that were imported, as specified in the request.

importEntityResponse returns an error message when the request specifies the following. (In the list, LD is LogicalDevice, LDA is LogicalDeviceAccount, PD is PhysicalDevice, and TN is TelephoneNumber):

• A rowNumber less than zero, or duplicate row numbers

• More than 10,000 rows

• A column name that is not defined in the properties file

• No action

• The create action with no specification

• The create action with a specification that does not exist

• A quantity of zero or less than zero

• The create action for an LD, LDA, or PD, and specifies a rangeToID or rangeToName (which is used only for TN)

• No id or rangeToID for Manual ID specifications of LD, LDA, or PD

• No quantity with rangeFromID for Manual ID specifications of LD, LDA, or PD

• A rangeFromID that is not numeric for LD, LDA, or PD

• Both id and quantity LD, LDA, or PD

• Both id and rangeFromID LD, LDA, or PD

• Both id and rangeFromID for auto-generated ID specifications of LD, LDA, or PD

• Both Name and rangeFromName for LD, LDA, PD, or TN

• No name and no rangeFromName for LD, LDA, PD, or TN

• A rangeFromName that is not numeric LD, LDA, PD, or TN

• An incorrect attribute for any entity

• No rangeFromName and no rangeToName for TN

• id, rangeFromID, rangeToID, quantity, rangeFromName, or rangeToName for InventoryGroup

• More than one LD for LD-LDA association

• More than one LD for LD-PD association

• Pairing information for association when action is create in both rows does not match

• Invalid association types (For example, LD-LD, PD-LDA, and so forth)

• An unequal number of entities for LD-TN or PD-TN

• Incorrect relatedRow information (For example, relatedRow does not specify the information action)

• An InventoryGroup that does not exist

• The call to the UIM API fails

exportEntityRequest

You must specify search criteria to find existing entities to export. Search criteria is specified using the <criteria> element, which includes entity type.

You specify the type of entity to export based on the entity types defined in the schema files. Each entity type defines different elements that pertain specifically to the entity type, which you use to specify what to update. Table 3-12 lists the valid entity types and the schema files in which they are defined.

<criteria> defines the following search criteria:

• specification

  The search returns entities created from the specified specification.

• adminState

  The search returns entities in the specified administrative state, which is defined by the following enumeration values:

  <xs:enumeration value="END_OF_LIFE"/>
  <xs:enumeration value="INSTALLED"/>
  <xs:enumeration value="PENDING_INSTALL"/>
  <xs:enumeration value="PENDING_REMOVE"/>
  <xs:enumeration value="PENDING_UNAVAILABLE"/>
  <xs:enumeration value="PENDING_AVAILABLE"/>
  <xs:enumeration value="PLANNED"/>
  <xs:enumeration value="UNAVAILABLE"/>
  <xs:enumeration value="PENDING_DISCONNECT"/>
  <xs:enumeration value="DISCONNECTED"/>
   
  

• assignmentState

  The search returns entities in the specified assignment state, which is defined by the following enumeration values:

  <xs:enumeration value="PENDING_ASSIGN"/>
  <xs:enumeration value="ASSIGNED"/>
  <xs:enumeration value="PENDING_UNASSIGN"/>
  <xs:enumeration value="UNASSIGNED"/>
  <xs:enumeration value="DISCONNECTED"/>
  <xs:enumeration value="PENDING_AVAILABLE"/>
  <xs:enumeration value="PENDING_UNAVAILABLE"/>
  <xs:enumeration value="PORTED"/>
  <xs:enumeration value="UNAVAILABLE"/>
  <xs:enumeration value="TRANSITIONAL"/>
   
  

• inventoryGroup

  The search returns entities associated with the specified inventory group.

• quantity

  The search returns the specified quantity of entities. For example, if the search finds 1,000 entities and the criteria specifies a quantity of 50, the first 50 entities found are returned.

• reservation

  If you specify reservation information, ExportEntity ignores it; FindEntity is the only operation that uses the reservation element. See "FindEntity" for more information.

• lock

  Row locking is used to optimize concurrent resource allocation for consumable entities; however, ExportEntity does not use row locking.

  If you specify row-locking information, ExportEntity ignores it.

• criteriaItem

  The search returns entities based on data specified by criteriaItem, which is an unbounded structure that provides the ability to specify the following:

  • Name of a criteria item as defined by the EntitySearchCriteria class, where Entity is the name of a specific entity such as TelephoneNumber, LogicalDevice, and so forth (see "Determining Criteria Item Names")

  • Value of specified criteria item

  • Enumerated operand with which to evaluate the specified criteria item and corresponding specified value:

    <xs:enumeration value="EQUALS" />
    <xs:enumeration value="NOT_EQUALS" />
    <xs:enumeration value="BEGINS_WITH" />
    <xs:enumeration value="ENDS_WITH" />
    <xs:enumeration value="CONTAINS" />
     
    

• property

  The search returns entities with the data specified by property, which is an unbounded structure that provides the ability to specify the following:

  • Name of characteristic

  • Value of specified characteristic

  • Enumerated operand with which to evaluate the specified characteristic and corresponding specified value:

    <xs:enumeration value="EQUALS" />
    <xs:enumeration value="NOT_EQUALS" />
    <xs:enumeration value="BEGINS_WITH" />
    <xs:enumeration value="ENDS_WITH" />
    <xs:enumeration value="CONTAINS" />
     
    

<nsrm:exportEntityRequest>
    <ent:criteria>
        <ent:entityType xsi:type="ld:LogicalDeviceType" />
        <ent:specification>
            <spec:name>SIMCard</spec:name>
        </ent:specification>
        <ent:adminState>INSTALLED</ent:adminState>
        <ent:assignmentState>UNASSIGNED</ent:assignmentState>
    </ent:criteria>
</nsrm:exportEntityRequest>

exportEntityResponse

exportEntityResponse returns a spreadsheet containing the exported entities as a SOAP attachment in the response. The entities returned in the response are dependent upon the entity types that were exported, as specified in the request.

Example 3-17 shows an excerpt from the UIM_Home/config/importExport.properties file, which defines the column names for the ExportEntity spreadsheet. These column names are common across all ExportEntity-supported entity types. You can change the name of existing column names defined in this file, but you cannot add new columns to the spreadsheet by defining additional column names in this file.

#Use export properties to customize column names for excel of ExportEntity
export.slNo=serialNumber
export.entityType=entityType
export.id=ID
export.name=name
export.specification=specification
export.description=description
export.attribute=attribute
export.characteristic=characteristic

Exported entities are grouped by entity type per sheet. Example 3-18 shows an excerpt from the UIM_Home/config/importExport.properties file, which defines the sheet names. You can change the name of existing sheets, but you cannot add new sheets to the spreadsheet by defining additional sheets in this file.

#Use export properties to customize name sheets for different entities
export.sheet.telephoneNumber=TelephoneNumber
export.sheet.logicalDevice=LogicalDevice
export.sheet.logicalDeviceAccount=LogicalDeviceAccount
export.sheet.physicalDevice=PhysicalDevice

The sheets are created when entities are found for export. So, all sheets are not always returned. For example, if the specified search criteria finds only logical devices to export, only the LogicalDevice sheet is returned.

If no entities are found for export, no sheets are created, and no attachment is returned in the response.

#Use TelephoneNumber export properties for exporting attributes
tn.export.partition=true
tn.export.owner=true
tn.export.permissions=tue

#Use LogicalDevice export properties for exporting attributes
ld.export.partition=true
ld.export.owner=true
ld.export.permissions=true
ld.export.networkLocationEntityCode=true
ld.export.deviceIdentitfier=true

#Use LogicalDeviceAccount export properties for exporting attributes
lda.export.partition=true
lda.export.owner=true
lda.export.permissions=true

#Use PhysicalDevice export properties for exporting attributes
pd.export.partition=true
pd.export.owner=true
pd.export.permissions=true
pd.export.networkLocation=true
pd.export.physicalLocation=true
pd.export.physicalAddress=true
pd.export.serialNumber=true