Samples

Ex12 - Login work orders using simplugin

The example ex12 using the configpath "simloginconf" demonstrates Login work orders using simplugin poolInstance. In this example the LoginWOName is configured at the type level. The login WO is executed immediately after the session is connected.

The files from ex00 are first copied to the $NODE/conf directory and then the ex12 files are copied and may overwrite some files from the following directory: 

kpsasample/ex12/generic/simloginconf

Ex12 - Login/Logout work orders using simplugin

The example ex12 using the configpath "simconf" demonstrates Login/Logout work orders using simplugin poolInstance. In this sample the LoginWOName and LogoutWOName is configured at the type level. The login WO is executed immediately after the session is connected and logout WO is executed before the session is disconnected.

The files from ex00 are first copied to the $NODE/conf directory and then the ex12 files are copied and may overwrite some files from the following directory: 

kpsasample/ex12/generic/simconf

Ex12 - Logout work order using simplugin

The example ex12 using the configpath "simlogoutconf" demonstrates Logout work order using simplugin poolInstance. In this sample the LogoutWOName is configured at the type level. The login WO is executed just before the session is disconnected from NE.

The files from ex00 are first copied to the $NODE/conf directory and then the ex12 files are copied and may overwrite some files from the following directory: 

kpsasample/ex12/generic/simlogoutconf

Ex12 - Logout work orders using telnet

The example ex12 using the configpath "tellogoutconf" demonstrates Logout work orders using telnet poolInstance. In this sample the LogoutWOName is configured at the type level. The logout WO is executed to exit from the connected system.

The files from ex00 are first copied to the $NODE/conf directory and then the ex12 files are copied and may overwrite some files from the following directory: 

kpsasample/ex12/generic/tellogoutconf

Ex12 - Login work orders using telnet

The example ex12 using the configpath "telloginconf" demonstrates Login work orders using telnet poolInstance. In this sample the LoginWOName is configured at the type level. The login WO is executed to log in to the system which is configured with the Hostname using the Port number in the instance configuration.

The files from ex00 are first copied to the $NODE/conf directory and then the ex12 files are copied and may overwrite some files from the following directory: 

kpsasample/ex12/generic/telloginconf

Ex12 - Login/Logout work orders using telnet

The example ex12 using the configpath "telconf" demonstrates Login/Logout work orders using telnet poolInstance. In this sample the LoginWOName and LogoutWOName are configured at the type level. The login WO is executed to log in to the system which is configured has the Hostname using the Port number in the instance configuration and logout WO is executed exit from the remote system.

Note:

PLEASE NOTE - Example requires the SOO product.

The files from ex00 are first copied to the $NODE/conf directory and then the ex12 files are copied and may overwrite some files from the following directory: 

kpsasample/ex12/generic/telconf

Ex13 - logconf Dynamic Cartridge

The example ex13 using the configpath "logconf" demonstrates Dynamic Cartridge. In this example the DynamicInstance is used to create the telnet cartridge. An additional entry using the CartridgeDynamic KES file is added in the Fulfillment Provisioning.kds file. Hostname and Port are declared as GetSessionMandatoryParameters, and Login and Password are declared as GetSessionOptionalParameters. A login WorkOrder is configured.

Note:

This example requires the CARTDYN product.

The files from ex00 are first copied to the $NODE/conf directory and then the ex13 files are copied and may overwrite some files from the following directory: 

kpsasample/ex13/generic/logconf

Ex20 - Using the cartridge Network Element configuration with cartdyn to store NE information.

This example demonstrates how to use the NE configuration file to centralize login / password for NE accessed through cartdyn.

The files from ex00 are first copied to the $NODE/conf directory and then the ex20 files are copied and may overwrite some files from the following directory: 

kpsasample/ex20/generic/conf

The following provadmin command is also executed before starting the drivers: 

provadmin loadNEConfig cart nodename=[nodename]