Previous Topic: C.3.1.1 Configuration File Global Information

Next Topic: C.4 WLE Load Utility Messages

C.3.1.2 Configuration File Server Information


Before running the Web Log Extractor certain parameters must
be defined.  This section describes the server parameters
that must be defined and those that are optional.

Note:  The following parameters are case sensitive and errors
       may occur if they are not entered correctly.  Every
       attempt is made by the utility program to correct CASE
       sensitive errors before the program aborts.

Note:  A site may have more than one server.  Certain
       parameters must be specified for each server targeted
       by the Web Log Extractor.

An example of a Configuration File Server Information
parameter specification is shown below.  A detailed
explanation of each parameter follows.

ServerName ABCD
ServerRoot /u/users/webserver/pathname
HostName user_defined_name
PortNo 1234
AccessLog /u/users/mics/humresc/logs/httpd-log
FRCAaccessLog /u/users/mics/humresc/logs/httpd-logfrca
ProxyLog /u/users/mics/humresc/logs/httpd-proxy
FRCAproxyLog /u/users/mics/humresc/logs/httpd-frcaproxy
AgentLog /u/users/mics/humresc/logs/Agent
RefererLog /u/users/mics/humresc/logs/referer-log
ErrorLog /u/users/mics/humresc/logs/httpd-errors

o   ServerName: Server Name

       Required: Yes

       Default : None

       The name you want to assign to this Server's log file
       records.  This name must be coded in upper case since
       this is eventually assigned to part of the COMPT field
       used in checkpoint file during DAY051 processing.

       The length can be a maximum of four characters.  There
       is no default name.  The ServerName 4-byte value
       defined here is assigned to WEBSNAME (Web Server Short
       Name) if one is not assigned in
       prefix.MICS.PARMS(WEBSLIST).

       ******************************************************
       * WARNING ! WARNING ! WARNING ! WARNING ! WARNING !  *
       *                                                    *
       * NOTE: The following words must not be used for     *
       * ServerName.  They are reserved for CA MICS use     *
       * only:                                              *
       *                                                    *
       *    WAS  WebSphere Application Server               *
       *    HTTP HTTP Web Server                            *
       *    WLG  HTTP Web Server Log Data Information Area  *
       *    WEB  SMF Data Information Area                  *
       *    WLE  HTTP Web Server Log Extractor Utility      *
       *    SMF  System Management Facility                 *
       *                                                    *
       * WARNING ! WARNING ! WARNING ! WARNING ! WARNING !  *
       ******************************************************

o   Orgsysid: Original System Identification

       Required: Yes. Must contain upper case letters only.

       Default : None

       The ORGSYSID value corresponds to a default system
       where the Web Server executes.  The actual system
       where the server executed is not provided in the
       measurement log data, thus the specified value you
       provide is required.  CA MICS employs the ORGSYSID
       value to set SYSID (Logical System) a common key
       sequence element.  The value can be a maximum of four
       characters.  There is no default name. The WLE utility
       will not execute successfully if Orgsysid is left
       blank. All Orgsysids in the input stream are required
       in prefix.MICS.PARMS(SYSID).

       Additionally, if the system where the WLE utility
       executes is different from any of the systems whose
       Web Servers are coded in the
       prefix.MICS.PARMS(WLECONF) file, then an entry for
       this system in prefix.MICS.PARMS(SYSID) is required as
       well.

       IMPORTANT CONSIDERATIONS
       ------------------------
       Since the log records do not identify the executing
       system, your specification represents a "static" map
       of the "expected" or "normal" relationship.  In some
       sites, certain servers have a definitive and accurate
       relationship (server x always runs on TSO2).  In other
       situations the relationship cannot be accurate as the
       server executes on different systems over time.

       A unique value for ORGSYSID can be specified for each
       server.  This will result in each server having a
       unique SYSID value.

       You can, however, specify the same ORGSYSID value for
       two or more servers.  This allows the log data for
       multiple servers to represent a "business entity"
       without attempting to define a relationship to an
       execution system where execution location is dynamic.

       Because SYSID is present in virtually all CA MICS
       files, and analysts typically merge files from
       multiple CA MICS components to generate reports and
       graphs, it is important to avoid misrepresentation of
       metrics in cases where the executing SYSID is not
       explicitly known.

       One method to avoid misrepresentation of metrics is to
       map servers to a single ORGSYSID such as "ANYW".  ANYW
       then can be mapped to a unique SYSID such as a PWEB
       (an imaginary system).


       ******************************************************
       * WARNING ! WARNING ! WARNING ! WARNING ! WARNING !  *
       *                                                    *
       * The Orgsysid value is assigned to ORGSYSID, and    *
       * then used to lookup logical SYSID.   You must      *
       * define each Orgsysid value (including the Orgsysid *
       * of the system where the WLE utility executes) in   *
       * prefix.MICS.PARMS(SYSID) member.                   *
       *                                                    *
       * Your DAILY job step DAY052 will abend with U310    *
       * error code if the any of the Orgsysid mentioned    *
       * above in not defined in prefix.MICS.PARMS(SYSID).  *
       *                                                    *
       * WARNING ! WARNING ! WARNING ! WARNING ! WARNING !  *
       ******************************************************

o   ServerRoot: Server Root Directory Name

       Required: No

       Default : No

       The name you want to assign to this Server's Root
       Directory. This can be found in web server's
       HTTPD.CONF file.  If this field is left blank, the
       CA MICS element WEBSRVRT in files (WLGSAL, WLGAPS, and
       WLGCFG) also reflects blank values. This information
       is helpful to determine the path for resources
       accessed on the web server.  The length can be up to
       48 characters long.  There is no default name.

o   HostName - Host Name

       Required: Yes

       Default : None

       A user-defined name assigned to this web server.  You
       should use a meaningful name that can easily identify
       the web server in reports and CA MICS Web Analyzer WEB
       Log Files Information Area (WLG) files.  The length
       can be a maximum of 20 characters.  There is no
       default name.


o   PortNo - Port Number

       Required: Yes

       Default : no

       The Port Number this server listens on for requests.
       There is no default value.

NOTE:  To turn on the log file processing, enter the path and
       first node of the filename for the server's log file.
       The WLELOAD program appends the appropriate file name
       suffix.  This applies for all of the log files listed
       below.

o   AccessLog - Access Log

       Required: Yes

       Default : no

    This parameter specifies whether or not you want to
    turn on the Access Log file.  The default value is NO.

o   FRCAaccessLog - FRCA Access Log

       Required: Yes

       Default : no

    This parameter specifies whether or not you want to
    turn on the FRCA Access Log file.  The default value is
    NO.

o   ProxyLog - Proxy Log

       Required: Yes

       Default : no

    This parameter specifies whether or not you want to
    turn on the Proxy Log File.  The default value is NO.

o   FRCAproxyLog - FRCA Proxy Log

       Required: Yes

       Default : no

    This parameter specifies whether or not you want to
    turn on the FRCA Proxy Log File.  The default value is
    NO.

o   AgentLog - Agent Log

       Required: Yes

       Default : no

    This parameter specifies whether or not you want to
    turn on the Agent Log File.  The default value is NO.

o   RefererLog - Referer Log

       Required: Yes

       Default : no

    This parameter specifies whether or not you want to
    turn on the Referer Log File.  The default value is NO.

o   ErrorLog - Error Log

       Required: Yes

       Default : no

    This parameter specifies whether or not you want to
    turn on the Error Log File.  The default value is NO.