Configuring a NIC

For demonstrations and installations with few subscribers, you can configure the VTA to use a NIC proxy stub, which explicitly defines a set of data mappings. However, for standard installation with a significant number of subscribers and multiple SAEs, you must set up a full NIC configuration.

To configure a NIC for the VTA management portals:

  1. Use the OnePopLogin configuration scenario (see Configuring the NIC (SRC CLI)).
  2. On each workstation that supports a NIC host for this NIC configuration, configure the object request broker (ORB) to recognize the Common Object Services (COS) name server. For JacORB, include the following line in the file jacorb.properties. Using NICs with the SRC-VTA 117 Chapter 8: Installing and Initially Configuring the SRC-VTA ORBInitRef.NameService=corbaloc::<host>:<port >/NameService
    • <host> is the name or IP address of the COS name server
    • <port> is the TCP port
  3. Add the NIC SAE agents to each SAE configuration as external plug-ins, as follows:
      Plugin.nic.objectref=corbaname::<host>:<port>/NameService#nicsae/saePort
      Plugin.nic.attr=PA_ROUTER_NAME,PA_SESSION_ID,PA_USER_TYPE,\
      PA_LOGIN_NAME,PA_USER_IP_ADDRESS
    • <host> is the name or IP address of the COS name server
    • <port> is the TCP port

    For information about configuring SAE plug-ins, see Configuring Tracking Plug-Ins Configuring Authentication Plug-InsConfiguring Internal Plug-Ins, and Configuring the SAE for External Plug-Ins.

  4. (Optional) Configure a NIC proxy stub. See Configuring Resolution Information for a NIC Proxy (SRC CLI) for information about configuring the NIC proxy stub.
  5. Configure a NIC proxy for the VTA. See Configuring NIC Proxies for the VTA .