# tApacheLogInput Reads the access-log file for an Apache HTTP server. To effectively manage the Apache HTTP Server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occurring. ## tApacheLogInput Standard properties These properties are used to configure tApacheLogInput running in the Standard Job framework. The Standard tApacheLogInput component belongs to the File family. The component in this framework is available in all Talend products. ## Basic settings | Properties | Description | | --- | --- | | Property type |

Either Built-in or Repository.
Built-in: No property data stored centrally.
Repository: Select the repository file where the properties are stored. The fields that follow are completed automatically using the data retrieved.

| | Schema and Edit
Schema |

A schema is a row description, it defines the number of fields to be processed and passed on to the next component. The schema is either Built-in or stored remotely in the Repository.

In the context of tApacheLogInput usage, the schema is read-only.
Built-in: You can create the schema and store it locally for this component. For more information about a component schema in its Basic settings tab, see Basic settings tab.
Repository: You have already created and stored the schema in the Repository. You can reuse it in various projects and Job flowcharts. For more information about a component schema in its Basic settings tab, see Basic settings tab.

| | File Name | Name of the file and/or the variable to be processed.

For further information about how to define and use a variable in a Job, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | | Die on error | Select this check box to stop the execution of the Job when an
error occurs. Clear the check box to skip the row on error and
complete the process for error-free rows. If needed, you can collect
the rows on error using a Row >
Reject link. | ## Advanced settings | Properties | Description | | --- | --- | | Encoding | Select the encoding type from the list or select Custom and define it manually. This field
is compulsory for DB data handling. | | tStatCatcher Statistics | Select this check box to gather the processing metadata at the Job
level as well as at each component level. | ## Global Variables | Variables | Description | | --- | --- | | Global Variables | NB\_LINE:
the number of rows processed. This is an After variable and it returns an integer.

ERROR\_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error checkbox is
cleared, if the component has this checkbox.

A Flow variable functions during the execution of a component
while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from
it.

For more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | tApacheLogInput
can be used with other components or as
a standalone component. It allows you to create a data flow using a
Row > Main connection, or to
create a reject flow to filter specified data using a Row > Reject connection. For an
example of how to use these two links, see [Procedure](https://help.qlik.com/talend/en-US/components/8.0/processing/textractxmlfield-tlogrow-tfileinputdelimited-tfileoutputdelimited-procedure-standard-component-drop). | **Related concepts** * [Reading an Apache access-log file](https://help.qlik.com/talend/en-US/components/8.0/apache-log/tapacheloginput-tlogrow-reading-apache-access-log-file-standard-component "The following scenario creates a two-component Job, which aims at reading the access-log file for an Apache HTTP server and displaying the output in the Run log console.")