Type Public
Category Configuration
Subject iAgent configuration settings/registry settings - Part 12
Rating 0% rating out of 0 vote(s).
Navigation Previous - Next - iTivity Remote Support Software - DoubleVision TTY Terminal Remote Control

iAgent configuration settings/registry settings - Part 12

#-------------------------------------------------------------------------------
# The customAppScan declares services or applications local to the iAgent
# that will be scanned by the iAgent. You can configure custom services
# or applications specific to your environment here. If the iAgent detects
# a daemon or service listening on your custom port, it will report that the
# daemon or service is available to the iManager when it connects.
#
# port=
# Processor_rc/customAppScan_#/port=80
# The "port" setting specifies the local TCP port number on which the iAgent
# will check for the presence of the application. If there is no program,
# application or daemon listening on this port, the iAgent will not report
# the availability to the iManager. If a listening program is found, then
# the application or service is reported back to the iManager for access by
# the iManager user. This setting is required.
#
# protocol=
# Processor_rc/customAppScan_#/protocol=http
# Currently supported protocols include, "http", "https", "telnet", "vnc"
# and "rdp". For web applications, the protocol should be either "http"
# or "https". This setting is required.
#
# appname=
# Processor_rc/customAppScan_#/appname=Standard Web Server
# Specifies the user readable display name of the application or service.
# This name should have a clear meaning to the iManager user. This setting
# is strongly recommended.
#
# session=[system_session_name]
# Processor_rc/customAppScan_#/session=Service
# Some operating systems have platform specific session labels. This
# setting should declare the session in which the application or service
# is running, if any. Typical session names would include, "tty0", "pts/4",
# ":4", "tcp #7", etc. This setting is optional.
#
# path=[application_path]
# Processor_rc/customAppScan_#/path=
# Specifies the path to the default page or landing page for the application.
# Typically only used for web/http applications.
#
# redirectHosts=[hostnames_redirected_to_iagent]
# Processor_rc/customAppScan_#/redirectHosts=
# Indicates zero or more comma separated hostname aliases that should be
# redirected at the iManager/remote side to the iAgent system.
#
# subService_#=[port_num,html_xml_tag,dest_ip_or_host]
# Processor_rc/customAppScan_#/subService_#=
# Subsidiary services that are also tunneled or forwarded from the iManager
# (or remote) system to the iAgent service. As shown in the example below,
# you can specify multiple subsidiary services per custom application.
# Each subsidiary service has a different line and number. At a minimum,
# you must specify a port number for the subsidiary service. If iTivity
# needs to remap a subsidiary port number at the iManager end for an HTML
# based custom application, it will update the HTML or XML page on the fly.
# You may also specify an HTML or XML tag that is used to control which
# areas of the HTML or XML configuration file are updated for this particular
# subsidiary service port number.
#
# Default:
# There are no defaults. The customAppScan is configured by the
# iTivity user.
#
# Example:
# Check for Acme Accounting Ace.
# Processor_rc/customAppScan_1/port=4242
# Processor_rc/customAppScan_1/protocol=http
# Processor_rc/customAppScan_1/appname=Acme Accounting Ace
# Processor_rc/customAppScan_1/session=Service
# Processor_rc/customAppScan_1/path=
# Processor_rc/customAppScan_1/redirectHosts=apps.acme.com,myserv01.internal
# Processor_rc/customAppScan_1/subService_1=4243,port,127.0.0.1
# Processor_rc/customAppScan_1/subService_2=4244,argument,localhost
# Processor_rc/customAppScan_1/subService_3=4245,param
# Processor_rc/customAppScan_1/subService_4=4246
#-------------------------------------------------------------------------------


#-------------------------------------------------------------------------------
# The platformAppScan declares web services or applications local to the
# iAgent that will be scanned by the iAgent. These settings represent the
# default platform application scan configuration delivered by Tridia
# Corporation. Custom web services or applications specific to a customer
# are generally configured via the customAppScan rather than here.
#
# port=
# Processor_rc/platformAppScan_#/port=80
# The "port" setting specifies the local TCP port number on which the iAgent
# will check for the presence of the application. If there is no program,
# application or daemon listening on this port, the iAgent will not report
# the availability to the iManager. If a listening program is found, then
# the application or service is reported back to the iManager for access by
# the iManager user. This setting is required.
#
# protocol=
# Processor_rc/platformAppScan_#/protocol=http
# Currently supported protocols include, "http", "https", "telnet", "vnc"
# and "rdp". For web applications, the protocol should be either "http"
# or "https". This setting is required.
#
# appname=
# Processor_rc/platformAppScan_#/appname=Standard Web Server
# Specifies the user readable display name of the application or service.
# This name should have a clear meaning to the iManager user. This setting
# is strongly recommended.
#
# session=[system_session_name]
# Processor_rc/platformAppScan_#/session=Service
# Some operating systems have platform specific session labels. This
# setting should declare the session in which the application or service
# is running, if any. Typical session names would include, "tty0", "pts/4",
# ":4", "tcp #7", etc. This setting is optional.
#
# path=[application_path]
# Processor_rc/platformAppScan_#/path=
# Specifies the path to the default page or landing page for the application.
# Typically only used for web/http applications.
#
# Default:
# There are no defaults. The platformAppScan is included with the
# iTivity iAgents.
#-------------------------------------------------------------------------------

#-------------------------------------------------------------------------------
# Linux Service Scan
# Discover services and applications specific to Linux.
#-------------------------------------------------------------------------------

# Check for on Monit on Linux.
Processor_rc/platformAppScan_1/port=2812
Processor_rc/platformAppScan_1/protocol=http
Processor_rc/platformAppScan_1/appname=Monit
Processor_rc/platformAppScan_1/session=Service
Processor_rc/platformAppScan_1/path=

# Check for on Zope App Server on Linux.
Processor_rc/platformAppScan_2/port=9673
Processor_rc/platformAppScan_2/protocol=http
Processor_rc/platformAppScan_2/appname=Zope App Server
Processor_rc/platformAppScan_2/session=Service
Processor_rc/platformAppScan_2/path=


Did this answer your question? Be heard!
5 4 3 2 1   
Yes! Getting warm Keep looking Not Really No!