When configuring network element models:
Create an NE template that you can copy later to create a specific network element. See "Creating NE Templates".
Create a network element based on the NE template. See "Creating Network Elements based on an NE Template".
(Optional) If you are working with large network, create a dynamic NE template. See "Creating Dynamic NE Templates".
To create NE templates:
Select Studio, then Show Design Perspective.
Select Studio, select New, select Activation, then select NE Template.
The NE Template Wizard appears.
Select the project and enter a name for the entity.
Click Finish.
The NE Template editor appears.
In the Connections tab, click Add.
The Add Predefined Parameters dialog box appears.
Click Yes to set up a different connection pool for each required connection.
You can add the predefined Oracle Communications ASAP communication parameters as global parameters.
In the All Communication Parameters tab, depending on the network element type (Serial Port Dial-up, for example), all parameters for the type are listed by default and are displayed as Global connections. You can leave them as global connections to use the value for a parameter across all connections, or you can override parameters (a port setting, for example) for a connection.
To override a parameter, select it in the Connection Parameter Details list and click Make Local.
The parameter will then have the connection name substituted for Global in the list. For each connection, the network element first uses local parameters if available. If none are available, the global parameters are used.
In the Target Network Elements tab, create a target network element by copying the name of the network element into the Target NE Name field.
Select File, then select Save.
The network element is now ready for users to connect to it with their pools.
Note:
There is a direct link between connection handlers and network elements. When ASAP determines what network element it needs to configure (the one it is routing to), it checks the vendor, technology, and software load of the network element and then searches for a connection handler with the same vendor, technology, and software load. The parameters it sets up go into the connection handler, which gets called to establish the connection to the pools. When the connection is established, the connection handler determines which atomic action it is processing and then checks the implementation map for a matching vendor, technology, and software load to determine which action processor to use.In the Connection Pool Name field, enter a name (the name must be unique on the ASAP server).
To create a network element based on an NE template:
Select Studio, then select Show Design Perspective.
Select Studio, select New, select Activation, then select Network Element.
The Studio Model Entity wizard appears.
Select the project, enter a name for the entity, and select the NE template.
Click Finish.
The Network Element editor appears. The pool and parameter descriptions are identical to those on the NE Template editor. See "NE Template Editor" for more information on using the Network Element editor.
In the Connection Pool Name field, enter a unique name (pool values must be unique across the ASAP server).
Navigate to the Target Network Elements tab.
Create a target network element by copying the name of the network element into the Target NE Name field.
Click Save to save the network element.
The network element is now ready for users to connect to it with their pools.
Note:
There is a direct link between connection handlers and network elements. When ASAP determines what network element it needs to configure (the one it is routing to), it checks the vendor, technology, and software load of the network element and then searches for a connection handler with the same vendor, technology, and software load. The parameters it sets up go into the connection handler, which gets called to establish the connection to the pools. Once the connection is established, the connection handler determines which atomic action it is processing and then checks the implementation map for a matching vendor, technology, and software load to determine which action processor to use.For a large network it is easier to use dynamic NE templates because dynamic templates do not require that you keep an inventory of all equipment. Rather, you need only an inventory system to acquire the routing connection data.
To create a dynamic NE template:
Select Studio, then select Show Design Perspective.
Select Studio, select New, select Activation, then select Dynamic NE Template.
The Studio Model Entity wizard appears.
Select the project and enter a name for the entity.
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
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.
Click Add to add more global parameters.
Save the dynamic NE template.