Miscellaneous
LeasePak Documentation Suite NETSOL website
Miscellaneous

LeasePak Server Configuration and Maintenance

Miscellaneous

License and Activation

Top Registration Codes and License Internet Services System Restart

  

Registration Codes
Topics
  • Hosts
    • application host
  • LeasePak
    • LeasePak license
      • registration code
    • LeasePak driver
      • lpadriver.exe
        • lease alias
      • driver options
        • /ver
  • General
    • shell
      • command prompt
This command may be run by any user with shell access on the application host.

Obtaining License and Activation Information

Use the /ver option of the lease command to obtain license information and activation codes:
lease /ver

Here is an example of using lease /ver:

[lpuser:~] lease /ver

and part of its output:

  [lpuser:~]  lease /ver
	LEASEPAK UX
	Copyright (c) 1995-2014, NetSol Technologies, Inc.
	------------------------------------------------------------
	Version                : 6.6a-
	Build date             : 08-Aug-15 00:53
	Client name            : Your Leasing Company
	Client code            : YL
	User License           : 99999
	Report License         : 99999
	Partial License        : 99999
	Add'l Lease charges    : 00020
	Add'l Asset charges    : 00010
	Add'l Recurring charges: 00020
	
	Registration Codes
	------------------------------------------------------------
	dx Generation   : SER-########-XXX-??????
	Print Spy       : SER-########-XXX-??????
	FormPak         : SER-########-XXX-??????
	Eop Monitor     : SER-########-XXX-??????
	LeasePak EC     : SER-########-XXX-?????? 

Click here to see the full output of lease /ver.

Internet Services

Top Registration Codes and License Internet Services System Restart

  

leasepakd and mPowerd
Topics
  • Environments
    • visitor environment
      • host environment
  • Hosts
    • application host
  • LeasePak
    • LeasePak instance
      • LeasePak release
        • leasepak_version
    • SETUP
      • SYSINSTALLFLAGS
    • LeasePak client
      • LeasePak API
    • LeasePak Internet services
      • leasepakd service
        • LEASEPAKD_PORT
        • LPKDPORT_INSTYPE
        • LPKDPORT_TO_REPL
        • LPKD_SVC_ID
      • mPowerd service
        • MPOWERD_PORT
        • MPWDPORT_INSTYPE
        • MPWDPORT_TO_REPL
        • MPWD_SVC_ID
  • General
    • pathname
      • image
    • environment variable
    • internet service
      • TCP port
      • request for service
        • service id
      • protocol
      • (x)inetd
    • OS
      • OS version
        • HP-UX
        • Solaris
        • Linux
  • Users and Roles
    • system administrator
About Internet Services

This section covers the files and entries created by the SETUP program to handle requests for services.

The form, location, purpose, and contents of the files and entries is explained; how to create them is not, as that is the properly the task of SETUP.

The specific items covered are:

leasepakd service request

The leasepakd service is an Internet service available on certain exposed TCP ports of the application host.

The leasepakd service requires entries in two locations:

  • /etc/services requires a single-line entry
  • (x)inetd configuration
    • HP-UX & Solaris – the file /etc/inetd.conf requires a single-line entry
    • Linux – a file named with the service name is required in the /etc/xinetd.d directory

These entries are created using the following values from SETUP:

  • $leasepak_version – the LeasePak release version
  • $LEASEPAKD_PORT – the port to use for leasepakd
  • $LPKDPORT_INSTYPE – whether to install new entries or to replace them
  • $LPKDPORT_TO_REPL – if replacing a port, which one
  • $SYSINSTALLFLAGS – position 5:
    Y = install nst_lp77a${INST_ID}_7700
    N = do not install nst_lp77a${INST_ID}_7700
  • $LPKD_SVC_ID – the service ID being installed for leasepakd, of the form nst_lp77a${INST_ID}_7700.
leasepakd service request - entry #1
/etc/services:
nst_lp77a${INST_ID}_7700 7700/tcp # ${INST_ID_CMT} LeasePak v77a leasepakd /opt/nst/v77a

where:

  • nst_lp77a${INST_ID}_7700 – the service name or service ID. When a potential client desires this service, it searches for the service ID in order to obtain the port
  • 7700/tcp – the port and protocol should be unique within /etc/services as should the service ID. The port and protocol tell the potential client where (port) and how (protocol) to obtain this service on this host.
  • # ${INST_ID_CMT} LeasePak v77a leasepakd /opt/nst/v77a – a comment that details which LeasePak release version is connected to this entry, and where that LeasePak instance is located.
The port number is more or less arbitrary. It is prompted for during SETUP with the prompt TCP port assignment for leasepakd inet daemon [7700]:. The administrator should accept the default, 7700, unless he or she knows that this will create conflicts. The number entered must be more than 1023 and less than 65536. The port is available to all LeasePak-configured processes through the environment variable $LEASEPAKD_PORT.
That being said, there is a relationship between the port number chosen and the LeasePak release version. Briefly, ports 6400, 6500, and 6600, relate precisely to LeasePak versions v64a, v65a and v66a. If the administrator needs to assign different numbers, it may be useful to find a way to fit into the pattern. The mPowerd service, discussed below, uses by default the leasepakd port plus 6, so mPowerd will default to 7706 in v77a.
NetSol is recommending that for the Shared User module that the hosted ports be equal to the dedicated ports just described, plus 3, so the shared ports would be 7703 and 7709, respectively.
The precise format of this entry is important, including the comment. When SETUP looks to see if a port selected by the administrator is available, it can detect whether or not an existing entry is one that was created by SETUP at some earlier point and so make appropriate modifications including allowing the port to be reassigned, but only if the format is exactly what is expected.
[lpuser:~] grep nst_lp /etc/services
  nst_lp77a${INST_ID}_7700 	7700/tcp	  # ${INST_ID_CMT} LeasePak v77a leasepakd /opt/nst/v77a  
mPowerd service request – entry #1

The mPowerd service is an Internet service available on certain exposed TCP ports of the application host.

In configuration, it is identical to leasepakd in every respect, except that its service ID is nst_mp77a${INST_ID}_7706 and its default port 7706, prompted for in SETUP by the prompt TCP port assignment for mPowerd inet daemon [**], and its value is available through the environment variable $MPOWERD_PORT.

These entries are created using the following values from SETUP:

  • $leasepak_version – the LeasePak release version
  • $MPOWERD_PORT – the port to use for mPowerd
  • $MPWDPORT_INSTYPE – whether to install a new entries or to replace them
  • $MPWDPORT_TO_REPL – if replacing a port, which one
  • $SYSINSTALLFLAGS – position 6:
    Y = install nst_mp77a${INST_ID}_7706
    N = do not install nst_mp77a${INST_ID}_7706
  • $MPWD_SVC_ID – the service ID being installed for mPowerd, of the form mpwrsvc.
[lpuser:~] grep nst_mp /etc/services
	  nst_mp77a${INST_ID}_7706	7706/tcp    # ${INST_ID_CMT} LeasePak v77a mPowerd /opt/nst/v77a  
leasepakd service request – HP-UX & Solaris – entry #2

/etc/inetd.conf:

[lpuser:~] grep nst_mp /etc/inetd.conf
		nst_mp77a${INST_ID}_7706 stream tcp nowait root \
		/opt/nst/v77a/live/bin/leasepakd \
		leasepakd –d /opt/nst/v77a \
		–l /opt/nst/v77a/log/leasepakd.log \
		–f /opt/nst/v77a/etc/${HOST}_v77a_rt.lpkd 

where:

  • nst_mp77a${INST_ID}_7706 – the service ID which connects this entry to entry #1 on /etc/services
  • stream tcp nowait root – these provide detailed information about the protocol in use
  • /opt/nst/v77a/live/bin/leasepakd – the full pathname of the image invoked to handle requests for this service
  • leasepakd –d /opt/nst/v77a –l /opt/nst/v77a/log/leasepakd.log \ –f /opt/nst/v77a/etc/${HOST}_v77a_rt.lpkd &nfash; the full command line for the service
[lpuser:~] grep leasepakd /etc/inetd.conf
	  nst_lp77a${INST_ID}_7700 stream tcp nowait root \
		/opt/nst/v77a/live/bin/leasepakd leasepakd \
		–d /opt/nst/v77a –l /opt/nst/v77a/log/leasepakd.log \
		–f /opt/nst/v77a/etc/${HOST}_v77a_rt.lpkd  
mPowerd service request – HP-UX & Solaris – entry #2

In configuration, mPowerd's second entry it is identical to that of leasepakd in every respect, except that its service ID is nst_mp77a${INST_ID}_7706 and the path components which of course reflect mPowerd.

[lpuser:~] grep mPowerd /etc/inetd.conf
	  nst_mp77a${INST_ID}_7706 stream tcp nowait root \
		/opt/nst/v77a/live/bin/mPowerd mPowerd \
		–d /opt/nst/v77a  –l /opt/nst/v77a/log/mPowerd.log \
		–f /opt/nst/v77a/etc/${HOST}_v77a_rt.lpkd  
leasepakd service request – Linux – entry #2

/etc/xinetd.d/nst_lp77a${INST_ID}_7700:

[lpuser:~] cat nst_lp*
# default: off
# description: leasepakd allows connections to
# ${INST_ID_CMT} LeasePak v77a leasepakd /opt/nst/v77a
service nst_lp77a${INST_ID}_7700{
	disable         = no
	id              = nst_lp77a${INST_ID}_7700	socket_type     = stream
	user            = root
	server          = /opt/nst/v77a/live/bin/leasepakd
	wait            = no
	protocol        = tcp
	port            = 7700
server_args = –d /opt/nst/v77a –l /opt/nst/v77a/log/leasepakd.log \ –f /opt/nst/v77a/etc/${HOST}_v77a_rt.lpkd }

where:

  • # ${INST_ID_CMT} LeasePak v77a leasepakd /opt/nst/v77a – service comment as in /etc/services
  • disable = no – service is enabled
  • id = nst_lp77a${INST_ID}_7700 – the service ID which connects this entry to entry #1 in /etc/services
  • socket_type = stream
    protocol = tcp
    wait = no
    – these provide detailed information about the protocol in use
  • server = /opt/nst/v77a/live/bin/leasepakd – the full pathname of the image invoked to handle requests for this service
  • port = 7700 – the port associated with this service as in /etc/services
  • server_args = –d /opt/nst/v77a –l /opt/nst/v77a/log/leasepakd.log \ –f /opt/nst/v77a/etc/${HOST}_v77a_rt.lpkd – the command line arguments for the service
mPowerd service request – Linux – entry #2

In configuration, mPowerd's second entry it is identical to that of leasepakd in every respect, except that its service ID is nst_mp77a${INST_ID}_7706 and the path components which of course reflect mPowerd.

In that light, there is little reason to display /etc/xinetd.d/nst_mp77a${INST_ID}_7706.

xinetd.conf Access Restriction Defaults

Include the following in /etc/inetd.conf:

	#Define access restriction defaults
	#
	#	no_access =
	#	only_from =
	#	max_load = 0
	cps = 50 10
	instances = 50
	per_source = UNLIMITED
					

System Restart

Top Registration Codes and License Internet Services System Restart

  

Restarting DBMS Servers and Queue Manager
Topics
  • LLDB
    • database system
      • Oracle
        • ORADIR
        • INSTANCES_LIST
        • Oracle instance
      • Sybase
        • SYBDIR
        • SYBSRV
        • SYBBKSRV
        • Sybase dataserver
  • Hosts
    • application host
  • LeasePak
    • LeasePak instance
      • LeasePak release
        • leasepak_version
    • SETUP
      • SYSINSTALLFLAGS
    • init service
      • nst_qm_${INST_ID}$RELS3
  • General
    • OS
      • system restart
  • Users & Roles
    • System Administrator
  • Queue Manager
    • Queues
      • Queue Environment
        • QMDIR
    • queue start and stop
      • service script
About System Restart

This section covers the files and entries created by the SETUP program in $INITDIR and links in the sibling rc?.d directories to handle system restart.

The form, location, purpose, and contents of the files and entries is explained; how to create them is not, as that is properly the task of SETUP.

The administrator may well already have put into place the proper init services for the DBMS, if so, then the sections below relating to DBMS start-ups are superfluous. The service for the Queue Manager is less likely to have been preinstalled, but if it has, then the administrator needs only to conpare his scripts to NetSol's to insure that all necessary points are covered.

The specific items covered are:
  • Queue Manager restart
  • Sybase restart
  • Oracle restart
Oracle Restart

The Oracle instance is restarted by the service script nst_dbora .

The service script is located in application host's init.d directory. See About the service Command.

The service script (nst_dbora) is built on the template $live/lib/dbora.tmplt, and uses the following values from SETUP:

The nst_dbora service script uses $DBMS_INSTANCES_LIST, or /etc/netsol_dbms_instances, which lists the instance names of any Oracle instances that are to be controlled by nst_dbora. This list is installed by SETUP, but the administrator must enter the names of the instances after the installation.

Sybase Restart

The Sybase dataserver is restarted by the service script nst_sbsyb.

The service script is located in the application host's init.d directory. See About the service Command.

The service script is built on the template $live/lib/sybase12, and uses the following values from SETUP:

Top Registration Codes and License Internet Services System Restart