Understanding the directory and file structure for the application server
This section contains topics that list the directories and files used by the BMC Network Automation application server.
About the home and data directories
The term BCAN_HOME represents the parent directory of application server static files (executable and configuration files).
The following table lists the default location for BCAN_HOME. This directory can be changed when BMC Network Automation is being installed.
OS type | Location |
|---|---|
Linux | /opt/bmc/bca-networks |
Windows | C:\Program Files\BMC Software\BCA-Networks |
The term BCAN_DATA represents the parent directory of application server dynamic data and some configuration files.
The following table lists the default location for BCAN_DATA. This directory can be changed when BMC Network Automation is being installed.
OS type | Location |
|---|---|
Linux | /var/bca-networks-data |
Windows | C:\BCA-Networks-Data |
BCAN_HOME directory structure
The directories and files listed in the following table are located in the static installation area of the BCAN_HOME directory on the application server. Only the files that you might need to change or files that are referenced elsewhere in this document are included in the table.
These paths are shown in Linux format. The Windows directory structure is the same except for the use of the forward slash (/).
BCAN_HOME directory structure — server
Directory or file | Description |
|---|---|
/BcanInstalledConfiguration.xml | Stores selections made during the installation or upgrade process. |
/checkpoint | Libraries and binaries for interfacing with Check Point servers. |
/FileRegistry.xml | Mapping of the system files created by the installation program. |
/FileRegistry.xsd | Schema file associated with the File Registry. |
/InstallationTaskConfiguration.xsd | Schema file that defines the legal structure of installer selections XML files (such as BcanInstalledConfiguration.xml). |
/java | Libraries and binaries for running the Java virtual machine. |
/postgresql | Libraries and binaries for running a PostgreSQL database. |
/public | Files that are available to you to modify the functionality of the system or to integrate with other applications. This directory contains only copies of the various files. Changes made to files in this directory do not affect the system unless the file is moved to the appropriate directory. |
/public/bmc/bca-networks/conf | Product configuration files. Some of these files (such as global.properties) are already present in the BCAN_DATA directory and have been set up and customized based on the installation. |
/public/bmc/bca-networks/csm | See BMC Cloud Lifecycle Management blueprints and templates. |
/public/bmc/bca-networks/extras | Compiled Java classes for miscellaneous utilities and for the web services client. |
/public/bmc/bca-networks/mib | Product V1 and V2C MIB definition files. |
/public/bmc/bca-networks/rules | Default Compliance Rule import files which are loaded into the database during a new installation, and updated here during software upgrades. |
/public/bmc/bca-networks/samples | Sample .jar files. |
/public/bmc/bca-networks/scripts | Contains scripts needed for various configurations. See Understanding tools and scripts. |
| /public/bmc/bca-networks/securityVulnerabilities/Cisco | Contains a release-time snapshot of the canned security vulnerabilities that is downloaded from Cisco’s website. |
/public/bmc/bca-networks/templates | Contains miscellaneous firewall and load balancer templates suitable for import. |
/public/bmc/bca-networks/xml | Copy of the various XML configuration files used by the product. See Understanding the public XML files. |
/public/bmc/bca-networks/xsl | Copy of the various xsl scripts used by the product. See Understanding public XSL files. |
/public/bmc/beim | Files for integrating with BMC Impact Manager. |
/public/bmc/bem | Libraries and binaries for integrating with BMC Event Manager. |
/public/bmc/cmdb | Configuration files for configuring federated links in the BMC Atrium CMDB. |
/public/bmc/sim | Libraries and binaries for integrating with BMC Service Impact Manager. |
/public/entuity | Files to integrate with Entuity products. |
/public/hpnnm | Files to integrate with HP Network Node Manager, including registration files for menus and configuration files for displaying discrepancies. |
/public/ipswitch | Files to integrate with Ipswitch WhatsUp products. |
/public/syslog-ng | Configuration files for enabling syslog-ng to work with BMC Network Automation. |
/tftpd | Libraries and binaries for running a TFTP server (Windows only). |
/tomcat | Libraries and binaries for running the Tomcat web server. |
/tomcat/bin | Tomcat scripts and binary files. |
/tomcat/conf | Tomcat configuration files. For details about the main files, server.xml and catalina.properties, see Understanding property and configuration files. |
/tomcat/LICENSE | The terms and conditions of the Apache License Agreement. |
/tomcat/lib | Tomcat libraries. |
/tomcat/logs | Tomcat log files, including catalina.out. |
/tomcat/ssh_host_dsa_key | Private key for SSH2 DSS (Linux only) |
/tomcat/ssh_host_rsa_key | Private key for SSH2 RSA (Linux only) |
/tomcat/webapps | Product web application files. These include:
|
/tools | Various scripts and tools for maintaining the system. The files in this directory are discussed in Understanding tools and scripts. |
/UninstallBMCBcan | Libraries and binaries for the uninstallation program. |
/utility | The installation maintenance utility. |
BCAN_DATA directory structure
The following table lists the directories and files that are located in the dynamic installation area of BCAN_DATA. Only the files that you might need to change or files that are referenced elsewhere in this document are included in the table:
BCAN_DATA directory structure — server
Directory or file | Description |
|---|---|
/checkpoint | Directory to store certificates for Check Point connections. |
/configs | Default directory for device configuration import and export files. |
/database.properties | Java property file for connecting to the database. This file is discussed in section Understanding property and configuration files. |
/db | PostgreSQL database. |
/dbbackup | Default directory for database backup and restore files. |
/devices | Default directory for device import and export files. |
/endorsed | Default directory for external programs, scripts, and data files which can be executed from rules and templates. |
| /endorsed/lib | Location of user supplied extensions, replacements, and JDBC drivers. For HP Network Node Manager, the Solid or Microsoft SQL Server driver .jar files should be placed in this directory. For enhanced differencing, the BMSI jar file should be placed in this directory. |
/global.properties | Java property file containing general configuration data used only by the server. This file is discussed in section Understanding property and configuration files. |
/global.properties.imported | Java property file containing general configuration data used by both the server and device agents. This file is deployed to the device agents during server-agent handshaking. This file is discussed in section Understanding property and configuration files. |
/global.properties.installed | Java property file containing general configuration data used by both the server and device agents. This file is deployed to the server and device agents during installation. This file is discussed in Understanding property and configuration files. |
/java.login.config | Contains the RADIUS and TACACS authentication parameters entered by you during installation time. Typically there is no need to modify this file. |
/.keystore | Certificate for the web server. |
/log | Location of all product, PostgresSQL, TFTP, and other log files. |
/logging.properties | Java properties file for product logging levels. This file is discussed in section Understanding property and configuration files. |
/ssh_host_dsa_key.pub | (Linux only) Public key used by the SSH Proxy service. |
/ssh_host_rsa_key.pub | (Linux only) Public key used by the SSH Proxy service. |
/tmp | Location of all product, PostgresSQL, TFTP, and other temporary files. |
/_upgrade | Location of time-stamped backup files archived during upgrades of the software. |
Comments
Log in or register to comment.