Creating NE Templates

To create NE templates:

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

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

   The NE Template Wizard appears.

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

4. Click Finish.

   The NE Template editor appears.

5. In the Connections tab, click Add.

   The Add Predefined Parameters dialog box appears.

6. 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.

7. 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.

8. 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.

9. 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.

10. In the Connection Pool Name field, enter a name (the name must be unique on the ASAP server).

Related Topics

Configuring Network Element Models

Working with Network Elements

NE Template Editor