File Locations

The software includes several groups of files used for installation, configuration, and administration. These groups are implemented differently in USS and PDS deployments:

• Supplied files (EDAHOME), which contains programs and related files. For more information, see Supplied Files Location (EDAHOME).
• Configuration (EDACONF), which contains the files that control the behavior of each configured instance. For more information, see Configuration Files Location (EDACONF).
• Applications (APPROOT), which is the default location for storing applications. For more information, see Application Files Location (APPROOT).
• Profiles, which contains user and group profiles. For more information, see Profile Files Location.
• Administration, which includes a file that specifies server administrators. For more information, see Administration Files Location.

Supplied Files Location (EDAHOME)

The programs and related files are stored in a location referred to as EDAHOME. The installation process copies the software into EDAHOME.

• In PDS deployment, EDAHOME defaults to the following partitioned data sets:

  high_level_qualifier.P.HOME.component_type

  where:

  high_level_qualifier

  Is the high-level qualifier for HOME.DATA and for all other data sets that the installation procedure allocates. We recommend that the high-level qualifier reflect the release of the software (for example, IADMIN.SRV93). However, you can use any site-specific value.

  component_type

  Designates the type of server component. The values are:

  Component Type	Description
  ETC	Script and text files.
  BIN	Binary-based object files.
  ACX	Server Access Files.
  MAS	Server Master Files.
  FEX	Server procedure (FOCEXEC) files.
  ERR	Error files.
  LOAD	Load library.

Configuration Files Location (EDACONF)

The configuration files are stored in a location referred to as EDACONF. Each configured instance has its own EDACONF, which controls the behavior of that instance.

• In PDS deployment, EDACONF defaults to the following partitioned data sets:

  high_level_qualifier.WFS.CONF.config_type

  where:

  high_level_qualifier

  Is the high-level qualifier for HOME.DATA and for all other data sets that the installation procedure allocates. We recommend that the high-level qualifier reflect the release of the software (for example, IADMIN.SRV9293). However, you can use any site-specific value.

  config_type

  Designates the type of configuration file.

  The primary configuration file is CFG.

  The WebFOCUS Reporting Server deferred execution configuration files are DEL, RPE, RPF, RPO, RQD, RQF, RQO, and RQP.

Profile Files Location

Server profiles are stored in the following location:

• In PDS deployment, the location is the following partitioned data set

  high_level_qualifier.WFS.CONF.PRF

  where:

  high_level_qualifier

  Is the high-level qualifier for HOME.DATA and for all other data sets that the installation procedure allocates. We recommend that the high-level qualifier reflect the release of the software (for example, IADMIN.SRV93). However, you can use any site-specific value.

  This PDS is allocated in ddname EDAPROF in the server JCL.

Administration Files Location

The file that specifies server administrators is located in:

• In PDS deployment, the location is member ADMIN of the following partitioned data set

  high_level_qualifier.WFS.CONF.CFG

  where:

  high_level_qualifier

  Is the high-level qualifier for HOME.DATA and for all other data sets that the installation procedure allocates. We recommend that the high-level qualifier reflect the release of the software (for example, IADMIN.SRV93). However, you can use any site-specific value.

  This PDS is allocated to ddname EDACFG in the server JCL.

Application Files Location (APPROOT)

The server application files are stored in a location referred to as APPROOT. APPROOT might be shared by multiple applications.

• In PDS deployment, APPROOT defaults to the following partitioned data sets:

  approot.appname.type.DATA

  where:

  approot

  Designates the root qualifier for the server applications.

  appname

  Designates the name of the application. There is one appname qualifier for each application.

  type

  Designates the type of application component. The values are:

  Type	Description
  ACCESS	Access Files.
  ETG	ibi Data Migrator flow information.
  FOCEXEC	Procedure files.
  FTM	Temporary files.
  GIF	Image files (both GIF and JPG).
  HTML	HTML files.
  MAINTAIN	Maintain files.
  MASTER	Master Files.
  WINFORMS	Forms.
  DTD	XML DTD files.
  FOCCOMP	FOCCOMP files.
  FOCSTYLE	Stylesheet files.
  SQL	SQL files.
  XML	XML files.
  XSD	XML XSD files.
  FOCUS	FOCUS data files.

Two applications are generated automatically during installation: IBISAMP and BASEAPP, a default application space.