Software Directory Structure

The following components are stored in the base code directory structure:

• Runtimes for Components – All the runtime executables for the base software.

• Business Object Binaries – All the binaries that contain the business logic.

• Configuration Files – All the configuration files for the business objects and runtimes.

• Scripts – Any administration or runtime scripts that are supplied to the customer.

• Supported Plug-ins – Source and executable for supplied plug-ins.

The following table outlines the typical contents of these directories:

Directory	Contents
bin	Utilities and commands for operations and configuration.
etc	A set of directories holding configuration files used in Oracle Utilities Work and Asset Management as well as template files and base libraries used to generate the configuration files.
java	Location of temporary files for Java execution.
ks	Location of Key Stores.
oem	Application Management Suite for Oracle Utilities generated files. Note: Files in this directory are generated by the discovery process used with the Oracle Application Management Pack for Oracle Utilities.
logs	Location of Oracle Utilities Work and Asset Management specific log files.
osbapp	Oracle Service Bus integration (optional).
product	Directories containing any bundled software with the product.
scripts	Directory containing any implementation specific scripts.
soaapp	Oracle SOA integration (optional).
splapp	Directories containing the JEE web applications (see Software (splapp) Directory).
structures	Internal structures used for configuration utilities.
templates	Base templates used to build configuration files.
tmp	Directory used to hold intermediary files used for the deployment process.
tools	Location of service pack, single fix and group fix utilities (see Tools Directory).
updates	Location of installed_fixes.txt Note: The updates directory only exists after at least one patch has been installed. If the directory does not exist, then no patches have been installed on this environment.

Software (splapp) Directory

Under the splapp subdirectory for each environment there are several subdirectories:

Directory	Contents
applications	Location of the web application product files.
billView	Location of the online bill viewing files (products supporting bill view only).
businessapp	Location of the business application product files.
certs	Location of security certificates.
config	Location of temporary configuration files.
iws	Location of native web services.
ohelpsource	Oracle Help engine source location.
pending	Internal use only.
standalone	Location of common Java libraries and the batch component of the product.
tpw	Location of threadpool worker specific files.
xmlMetaInfo	Location of the service definitions for the product.

Warning: Under no circumstances should files be manually altered in these directories unless instructed by Oracle Support. The Oracle Utilities SDK will deposit files in the relevant locations in this structure using the Packaging component of the SDK or using the Development tools directly.

Tools Directory

Note: In past releases the utilities to install patches were included in each patch. This is not the case anymore as they are centralized as part of the installation.

Note: These utilities are not usually executed manually but are part of general installations and automation from Application Management Pack for Oracle Utilities

The tools directory is used for deployment and patching tools used by Application Management Pack for Oracle Utilities and the internal patching utilities. The directories are in the following structure:

Directory	Contents
bin	General Software patching utilities.
bin/db	Database Patching utilities.
bin/db/bin	Binaries for patching.
bin/db/config	Logging configuration for patching utilities.
bin/db/lib	Java Libraries for patching utilities.
domaintemplates	Oracle WebLogic Domain Templates for product.

Directory Permissions

The directories within Oracle Utilities Work and Asset Management are controlled by the operating system security relating to the administration user assigned to the product. The table below outlines the permissions under the $SPLEBASE location:

Directory/files	Owner	Group	Other
etc	rwx	r-x	---
Individual files	rw-	r--	---
logs	rwx	rwx	---
logs/system	rwx	rwx	---
Individual log files	rw-	r--	---
Oracle WebLogic Configuration Files	rw-	r--	---
Oracle WebLogic shell scripts (.sh)	rwx	r-x	---
product	rwx	r-x	---
product/apache-ant/bin/ant	rwx	r-x	---
scripts, tools, updates	rwx	r-x	---
Shell scripts (.sh) in bin	rwx	r-x	---
osbapp, soaapp, splapp	rwx	r-x	---
structures	rwx	r-x	---
templates	rwx	r-x	---
tmp	rwx	r-x	---

Legend:

• r – Read Only

• rw – Read Write

• rwx – Read/Write/Execute

• rx – Read/Execute

• blank – no permissions.

These permissions are set by the setpermissions.sh utility which is executed as outlined in the Installation Guide.