Creating Dynamic NE Templates

You can use dynamic NE templates when working with large networks and if you do not want to keep an inventory of all equipment. In this scenario, the inventory system acquires the routing connection data.

To create a dynamic NE template:

  1. From the Studio menu, select Show Design Perspective.

  2. From the Studio menu, select New, then select Activation, and then select Dynamic NE Template.

    The Studio Model Entity wizard appears.

  3. Select the project and enter a name for the entity.

  4. Click Finish.

    The Dynamic NE Template editor appears. Only the global parameters are displayed in the NE Instance Properties list, as all connections have been created during runtime and a remote network element is not required. For example, if socket-based, you would add socket-based parameters only; any order that comes in with the same vendor, technology, and software load would get the global parameters from here and get the connection parameters from the order (a password or IP address, for example). A syntax on the order is set up for global parameters:

    COMM_PARAM.NE_ID.value

  5. In the NE Instance Properties area, the following fields are listed:

    • Drop Time Out (minutes): This field specifies the time in which a connection will drop in absence of activity, such as generation of new connection requests. You can change the time as per your requirement.

    • Maximum connections: This field specifies the number of connections allowed by ASAP in a connection pool. You can change the number of connections as per your requirement.

    • Spawn Threshold (AAs): If there is a request for a new connection and the number of connections in a connection pool has reached a threshold, a new connection pool is created. This field specifies the threshold value after which a new connection pool is created.

    • Kill Threshold (AAs): If the number of connections in a connection pool goes below than the number of connections specified in the kill threshold, the connection pool is dropped.

    • Retry Count: If a connection fails between ASAP and the network element, ASAP tries to establish the connection again. This field specifies the number of attempts that ASAP can do to reestablish the connection.

    • Retry Interval: This field specifies the time interval between each retry attempt by ASAP. You can change the time interval as per your requirement.

    • Throughput: This field specifies the time for network element instance to ensure that no more than specific number of transactions are sent to the network element per unit of time.

  6. Click Add to add more global parameters.

  7. Save the dynamic NE template.